Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Apr 2000 14:53:21 -0400
From:      "Chris BeHanna" <behanna@fast.net>
To:        Freebsd-questions@freebsd.org
Subject:   ISA Modem on 4.0-RELEASE
Message-ID:  <200004131853.OAA08427@post3.fast.net>

next in thread | raw e-mail | index | archive | help
	Before anyone groans "another one?", I searched the archives
for getting a PnP ISA modem working on 4.0, tried everything I found, 
and it still doesn't work.

	I have the pnpinfo output on a floppy with me, but the PC here at
work won't read the floppy (damnable Compaq!).  I have tried putting 
the card's ID into the modem id array in sio.c (and yes, I did take 
care to use the logical ID rather than the serial number), but that 
didn't work. I also tried enabling all four sio devices in my 
configuration file and rebuilding the kernel, but that didn't work, 
either.

	Finally, I did a boot -v to see what was going on during the ISA
probe.  My sound card was detected and reported its resource data 
(it's CSN 1), and then I got the message "PnP device failed to report 
resource data", which I presume to be a failure when my modem was 
probed.

	FYI, the modem is a Zoom Telephonics V.90 ISA Faxmodem, and
it reports the symbolic name ZTIa001.  If I could have loaded the 
pnpinfo, dmesg, and kernel config from the floppy that I brought to 
work with me, I'd've done so, but Compaq floppy drives are too damned 
snooty to read floppies written on another vendor's drive.

	So it looks like I'll have to go through the painful experience
of rebuilding my Win2K partition after all, so that I can connect to 
the internet and give more detailed information.  (I was hoping, 
instead, to d/l the vmware package and load Win2K under *that*, so 
that my wife can use her preferred email package and I can stop 
booting back and forth between Windows and FreeBSD.)

	What I'm hoping for by sending this message is for someone
to tell me how to do the 4.0 equivalent of
"pnp 2 0 enable os irq0 7 port0 0x3e8", even if it means hardcoding 
the information somewhere and rebuilding the kernel, just as a 
workaround for now.  That command string allowed my modem to work 
under 3.4 as recently as last week.

	Weird question:  if pnpinfo can successfully extract information
from the card, why does the boot-time probe fail to do so?

Thanks,
Chris BeHanna
behanna@fast.net


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004131853.OAA08427>