Date: Fri, 20 Apr 2007 18:25:56 +0100 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: freebsd-stable@FreeBSD.org Cc: Stefan Lambrev <stefan.lambrev@sun-fish.com> Subject: Re: sio0: port may not be enabled Message-ID: <4628F7A4.3060503@dial.pipex.com> In-Reply-To: <049954BE-364B-4897-87C3-342D0A824C00@mac.com> References: <4628D63A.3050909@sun-fish.com> <20070420152329.GA16702@icarus.home.lan> <049954BE-364B-4897-87C3-342D0A824C00@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar wrote: > > On Apr 20, 2007, at 8:23 AM, Jeremy Chadwick wrote: > >> Look closely at the dmesg line, note what device sio0 is claiming to be >> associated with (acpi0, not isa0): >> >>> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags >>> 0x10 on acpi0 >> >> >> This is one of the drawbacks to using ACPI. > > > Could you try uart(4) instead. It seems quite excessive to have to > disable ACPI just to get a serial port working. I'd like to know > if this is related to the sio(4) driver or something else. Just a note that I get exactly the same issues with my BIOS/ACPI but *my serial port works*. I have not needed to disable ACPI nor to use uart(4). The sio0 line has an IRQ associated with it (4) and I think if there were really a problem there would be no IRQ here. IIRC, the issue is something to do with ACPI presenting the serial ports backwards wrt the BIOS. I know I got concerned about this when I first encountered it, and tried stuff to swap the two ports I have over, but nothing I did made the initial "ACPI probed irqs" error go away so I just tried the serial port and it worked. --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4628F7A4.3060503>