From owner-freebsd-hackers Thu Jul 11 14:25:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA06300 for hackers-outgoing; Thu, 11 Jul 1996 14:25:11 -0700 (PDT) Received: from shogun.tdktca.com ([206.26.1.21]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA06126 for ; Thu, 11 Jul 1996 14:23:44 -0700 (PDT) Received: from shogun.tdktca.com (daemon@localhost) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id QAA13462 for ; Thu, 11 Jul 1996 16:24:32 -0500 (CDT) Received: from fa.tdktca.com (bsd.fa.tdktca.com [163.49.131.129]) by shogun.tdktca.com (8.7.2/8.7.2) with ESMTP id QAA13456 for ; Thu, 11 Jul 1996 16:24:31 -0500 (CDT) Received: (from alex@localhost) by fa.tdktca.com (8.7.5/8.6.12) id QAA03058; Thu, 11 Jul 1996 16:27:44 -0500 (CDT) Date: Thu, 11 Jul 1996 16:27:44 -0500 (CDT) From: Alex Nash To: Thomas Graichen cc: hackers@freebsd.org Subject: Re: sio / modem problems In-Reply-To: <199607112048.WAA03185@titania.physik.fu-berlin.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 11 Jul 1996, Thomas Graichen wrote: > i have an internal creatix phone-master modem - which will be detected in > FreeBSD 2.0.5 but not in the 2.1.0 RELEASE or the march 2.2 snap - it's > configured for irq 2 and comport 4 (2e8) - i tried to hack the sioprobe > from 2.0.5 quickly into a 2.1.0 kernel - but it didn't help - any ideas ? > > what has changed since then - bruce or someone else do you have any idea what > may be the reason for this behavior - another modem works fine and the 2.0.5 > kernel as said before detects it fine (as linux does) ? I recently fixed a modem detection problem from someone by inserting "DELAY(1000);"'s in sioprobe() everywhere the /* EXTRA DELAY? */ comment appeared. It's a hack, but clearly some portion of that code is running too close to the edge for some (read: cheap?) serial ports (in this case it was an internal Zoom modem in a Packard Bell computer). Unfortunately I was never able to track down exactly where the problem was since each changed required recompiling the kernel on my end and then FTPing it over a 14.4 modem to the end user. As soon as this guy gets sources on his system, I'll resume tracking this down. Alex