From owner-freebsd-mobile Mon Nov 29 13:44:20 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtppop3.gte.net (smtppop3.gte.net [207.115.153.22]) by hub.freebsd.org (Postfix) with ESMTP id 908C71541E for ; Mon, 29 Nov 1999 13:44:13 -0800 (PST) (envelope-from chris.dahler@gte.net) Received: from laptop (1Cust177.tnt3.sfo3.da.uu.net [63.23.9.177]) by smtppop3.gte.net with SMTP for ; id PAA7884639 Mon, 29 Nov 1999 15:43:34 -0600 (CST) Message-ID: <00ca01bf3ab3$384890e0$b109173f@laptop> From: "Chris Dahler" To: Subject: Question about sio Date: Mon, 29 Nov 1999 15:40:34 -0600 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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