From owner-freebsd-questions Tue Sep 19 22:04:46 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA17435 for questions-outgoing; Tue, 19 Sep 1995 22:04:46 -0700 Received: from megasoft.tic.ab.ca (root@megasoft.tic.ab.ca [198.161.220.180]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA17428 for ; Tue, 19 Sep 1995 22:04:42 -0700 Received: (from root@localhost) by megasoft.tic.ab.ca (8.6.11/8.6.9) id XAA01966 for questions@freebsd.org; Tue, 19 Sep 1995 23:06:58 -0600 Date: Tue, 19 Sep 1995 23:06:58 -0600 From: Charlie Root Message-Id: <199509200506.XAA01966@megasoft.tic.ab.ca> To: questions@freebsd.org Subject: sio0 not responding:( Sender: owner-questions@freebsd.org Precedence: bulk I upgraded to 2.1.0-STABLE recently... For some reason the kernel upon bootup does not see my sio0 but does see sio1. In 2.1-SNAP it did see sio0 but not sio2 or sio3. Also in SNAP I could boot into config and do a probe and attach on sio0 and than quit and the sio0 would than be recognized... I really need com1 to be recognized somehow... It would seem that 2.1.0-STABLE has taken out the probe/attach in the userconfig on bootup? Any suggestions on how to demand that the kernel sees the comport? I have tried the internel 28.8 modem in all the other PC's and it works fine... And as I said, it works fine if I can probe/attach sio0 before booting the kernel... Please help:( Phil... philw@megasoft.tic.ab.ca