From owner-freebsd-mobile Mon Nov 29 16:55:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mbs.valinet.com (mbs.valinet.com [206.98.218.24]) by hub.freebsd.org (Postfix) with ESMTP id EA4C815611 for ; Mon, 29 Nov 1999 16:55:31 -0800 (PST) (envelope-from coreya@mbs.valinet.com) Received: from localhost (coreya@localhost) by mbs.valinet.com (8.8.8/8.7.1) with SMTP id TAA17332; Mon, 29 Nov 1999 19:55:28 -0500 (EST) Date: Mon, 29 Nov 1999 19:55:28 -0500 (EST) From: Alan Corey Reply-To: Alan Corey To: Chris Dahler Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Question about sio In-Reply-To: <00ca01bf3ab3$384890e0$b109173f@laptop> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I see the same "not found" on my (by coincidence) Presario 1610 with my network card on ed0, so I've had time to think about it. FeeeBSD's trying to initialize my ed0 before the pccard stuff loads. It doesn't find it because it has no interface to it. When the pccardd loads near the end of the boot it then finds the card and all is fine. It may be possible to change the order here but I haven't worried about it. I don't know about the warm boot problem, except that Win98 can screw anything up. :-) I run Win95 and I've had no problems. Seriously, it sounds like something in your modem needs more of a reset than FreeBSD's warm boot gives it. Pccard support is not one of FreeBSD's stronger areas yet. I almost went back to Linux for that reason and did briefly load Slackware 7 on one machine. I got fed up with that after an evening and put FreeBSD 3.3-RELEASE on instead. Now I've got FreeBSD on 4 machines with common uptimes of over a week on my SETI machine. Linux is fashionable, FreeBSD is more solid and careful. Alan Corey --------------------------------------------------------------- Make your computer part of the largest computer in the world See http://www.seti-inst.edu/setiathome.html or http://setiathome.ssl.berkeley.edu/ for more info On Mon, 29 Nov 1999, 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)? 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? > > Chris Dahler > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message