From owner-freebsd-questions Fri Sep 13 14:12:23 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA17692 for questions-outgoing; Fri, 13 Sep 1996 14:12:23 -0700 (PDT) Received: from alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id OAA17679 for ; Fri, 13 Sep 1996 14:12:17 -0700 (PDT) Received: from hmmm.alaska.net by alaska.net (5.x/SMI-SVR4) id AA02877; Fri, 13 Sep 1996 13:10:40 -0800 Message-Id: <323A15D0.6C2C@alaska.net> Date: Fri, 13 Sep 1996 19:17:52 -0700 From: hmmm X-Mailer: Mozilla 2.02 (Win16; I) Mime-Version: 1.0 To: freebsd-questions Subject: modems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk i'm just going to put this in the drop box ... no replies necessary. something is really screwy here. i can't wait for a new slick sio driver! i had a 14.4 ISA Hayes modem. after coming to the conclusion that you cannot configure an internal modem & com port on the same port & irq, i still had problems. i moved the modem to sio3/irq5 (disabled ed0 temporarily) and enabled sio2, even though it is completely unused. the kernel reported sio 2&3 not found. after thorough testing, i found that whenever the kernel reported this, all i had to do was boot DOS, run COMITs modem diagnostics, then reboot to BSD. the kernel would then find sio3 without fail. but if a crashed iijppp, and had to reboot, sio3 would be lost again, and i'd have to do the COMIT thing again. with a working stable setup - as above - i then disable sio2. sio3 (modem) is now permenantly lost. no tricks find it this time. so i re-enable sio2. sio3 found immediately. i'm an embedded hacker scaling the walls of unix, and ain't too smart, but this definitly seems like buggy behavior.