Bug 83671

Summary:	Can't get comconsole to work properly on Supermicro X5DPR-IG2+/X5DPR-8G2+
Product:	Base System	Reporter:	Marc Olzheim <marcolz>
Component:	kern	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	5.4-STABLE
Hardware:	Any
OS:	Any

Description Marc Olzheim 2005-07-18 15:40:27 UTC

	After the loader and the kernel startup with sio0 as comconsole, the
	kernel detects sio0 at port 0x2f8-0x2ff irq 3 instead of 3f8 irq 4.
	Consequently userland's comconsole is at sio1, while the kernel's
	comconsole remains at the original unnamed 3f8/irq4 port.

	I've tried all combinations of ACPI settings in the BIOS and the
	loader, but haven't found a single working setting in which both
	use the same port.

Comment 1 John-Mark Gurney freebsd_committer

2005-07-19 20:54:42 UTC

State Changed
From-To: open->feedback

have you tried to add the following commands in loader.conf: 
hint.sio.0.port="0x2F8" 
hint.sio.0.irq="3" 
hint.sio.0.flags="0x0" 
hint.sio.1.port="0x3F8" 
hint.sio.1.irq="4" 
hint.sio.1.flags="0x10" 

We have similar problems on our consoles, and this gets them both 
to the same port...  though now you have to make sure your second unnamed 
port is turned on...  Our sio dmesg: 
sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 
sio0: type 16550A 
sio1: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 
sio1: type 16550A, console

Comment 2 Marc Olzheim 2005-07-20 15:52:27 UTC

That still doesn't do it for me. I only get

sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio0: type 16550A

and no sio1

Comment 3 gurney_j 2005-07-20 17:06:34 UTC

Marc Olzheim wrote this message on Wed, Jul 20, 2005 at 16:52 +0200:
> That still doesn't do it for me. I only get
> 
> sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
> sio0: type 16550A
> 
> and no sio1

So, it looks like your other bug is that acpi isn't enumerating sio1..
You could always dump your AML using acpidump and see if it's there..
Someone else with acpi foo should help you...

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."

Comment 4 Marc Olzheim 2008-02-29 12:39:03 UTC

As I don't have any of the said boxes running FreeBSD 5 or up anymore, I
cannot test anything regarding this problem anymore. It can be closed as
far as I am concerned.

Comment 5 Mark Linimon freebsd_committer

2008-03-01 19:52:24 UTC

State Changed
From-To: feedback->closed

Submitter no longer has access to the hardware.