Date: Mon, 29 Nov 1999 20:58:28 -0500 From: Greg Lehey <grog@mojave.sitaranetworks.com> To: Chris Dahler <chris.dahler@gte.net>, freebsd-mobile@FreeBSD.ORG Subject: Re: Question about sio Message-ID: <19991129205828.13924@mojave.sitaranetworks.com> In-Reply-To: <00ca01bf3ab3$384890e0$b109173f@laptop>; from Chris Dahler on Mon, Nov 29, 1999 at 03:40:34PM -0600 References: <00ca01bf3ab3$384890e0$b109173f@laptop>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 29 November 1999 at 15:40:34 -0600, Chris Dahler wrote: > When I do a warm reboot from Win98 to FreeBSD-3.3R-PAO on my Presario > laptop, FreeBSD is unable to locate sio3. When I do a cold reboot, FreeBSD > initially reports sio3 as not found, but then (usually the last line in > dmesg), it seems to change its mind and reports sio3 as a 16550A. > > My two questions are: why would FreeBSD have a problem with this port after > a warm reboot (Linux seems to be able to detect this port all the time, > regardless of the type of reboot)? Obviously your sio3 is a PCMCIA card. They're controlled by the PC Card daemon (pccardd), which takes a while (probably too long) to get started. This code is currently under review, and in 4.1 or so you can expect things to work more smoothly. > Also, when it *can* find the port, why would FreeBSD initially say > sio3 was not found, and then later on in the boot process have a > change of heart and tell me it is there? The first time round, the ISA bus routines go looking for the port, and they don't find it. When pccardd comes along, it finds it. Yes, this is tacky. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991129205828.13924>