Date: Sat, 21 Apr 2007 09:42:52 -0700 From: Marcel Moolenaar <xcllnt@mac.com> To: Stefan Lambrev <stefan.lambrev@sun-fish.com> Cc: Jeremy Chadwick <koitsu@FreeBSD.org>, freebsd-stable@FreeBSD.org Subject: Re: sio0: port may not be enabled Message-ID: <E6593559-F258-456E-8EBC-38B1EB76AA05@mac.com> In-Reply-To: <4629C650.2030607@sun-fish.com> References: <4628D63A.3050909@sun-fish.com> <20070420152329.GA16702@icarus.home.lan> <049954BE-364B-4897-87C3-342D0A824C00@mac.com> <4629C650.2030607@sun-fish.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 21, 2007, at 1:07 AM, Stefan Lambrev wrote: >>> Some systems apparently tie the serial port to ACPI functionality >>> in a >>> different way. For example, I have a couple boxes which have sio0 >>> attached to acpi0 that work fine. In some other cases, I have ones >>> which result in a non-working serial port unless I disable ACPI >>> (thus >>> sio0 shows up as being attached to isa0). >> >> 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. > This did the trick: > > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0 > > ports are swapped but this is probably because I swap them in bios, > but this is ok. > Serial is working and now I can start working on the main problem :) > So it's not acpi problem, but instead problem with sio? So it appears. -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E6593559-F258-456E-8EBC-38B1EB76AA05>