Date: Fri, 25 Jul 2008 15:26:02 -0700 From: Marcel Moolenaar <xcllnt@mac.com> To: Mike Tancsa <mike@sentex.net> Cc: freebsd-current@freebsd.org Subject: Re: PUC rewrite Message-ID: <2F58935E-6439-45A1-9CB3-894FC577ECF2@mac.com> In-Reply-To: <200807252129.m6PLTwhs021540@lava.sentex.ca> References: <200806061259.m56CxhdR045603@lava.sentex.ca> <018816ED-8FF3-4834-AD17-59637C87D30D@mac.com> <200807252129.m6PLTwhs021540@lava.sentex.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jul 25, 2008, at 2:30 PM, Mike Tancsa wrote: ... > uart0: <Non-standard ns8250 class UART with FIFOs> port > 0xe500-0xe507 irq 10 at device 14.0 on pci0 > uart0: [FILTER] ... > uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0 > uart1: [FILTER] ... There's no uart device found (i.e. probed and attached) at port 0x3f8. So, there's no uart that can be associated with the console and you won't have a /dev/cuau that is opened for/by init(8). > How can I force the PCI modem *not* to be uart0 so that the onboard > com ports show up? uart(4) deals with the fact that the console may not be associated with uart0, so the real problem is not having a uart driver for the serial port at 0x3f8. > uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 on > isa0 > uart0: [FILTER] > uart0: console (9600,n,8,1) > uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 on isa0 > uart1: [FILTER] Odd.. Is the 3com configured to take over COM1 or something? -- Marcel Moolenaar xcllnt@mac.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2F58935E-6439-45A1-9CB3-894FC577ECF2>