Date: Mon, 9 Sep 1996 08:24:01 -0400 From: "Steve Sims" <SimsS@Infi.Net> To: "Bruce Evans" <bde@zeta.org.au>, <freebsd-hackers@FreeBSD.org>, <housley@pr-comm.com> Subject: Re: Problem with sio0 Message-ID: <199609091224.IAA00602@mh004.infi.net>
index | next in thread | raw e-mail
Bruce - is this a coincidence, or WHAT? I have been suffering for a couple of months with this exact same problem on a Compuke LTE/Elite. I chatted with Nate a little bit on this, and he recommended that I hit you with this. Having just loaded the 8/1 2.2 SNAP, I'll try the patches enclosed and let you know what I find. This has been MOST irritating, but a profound lack of time has prevented me from upgrading my source / poking around. FWIW, the boot probe doesn't find the Megahertz X-Jack at sio1 either.... ...sjs... ---------- > From: Bruce Evans <bde@zeta.org.au> > To: freebsd-hackers@FreeBSD.org; housley@pr-comm.com > Subject: Re: Problem with sio0 > Date: Friday, September 06, 1996 1:45 PM > > >I have a Compaq Contura 430C laptop. On boot I get a message: > > > >sio0 not found at 0x3f8 > > > >The computers BIOS, DOS/Windoze and OS/2 all are able to find it at 0x3f8 > >with IRQ 4 and think it is a NS16550AF. I modified > >/usr/src/sys/i386/isa/sio.c to print the contents of the array "failures". > >On boot all locations contained 0 except #5 and #8. > > > >I would like to fix this problem. I is there more testing I can do to help? > >I tried ignoring, commented out, the lines that set #5 & 8. That caused > >"65 events on a device without a tp" (basically). > > In, -current, try increasing the delays. I guess this would work because > the failure messages show that the expected interrupt arrived a little > late. Also try the CFCR change in the enclosed diffs. > > The delays somehow didn't make it into 2.1.5. Try the enclosed patch > for 2.1.5. It might work for earlier versions too. > > Bruce [SNIP] ...sjs...help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609091224.IAA00602>