On Sat, Mar 11, 2000 at 06:44:32PM -0500, Eric D. Futch wrote:
> Ugh... nevermind. Getting rid of the PNPBIOS option from the kernel
> config got rid of all the unknown strangeness,
Argh!, yes , that was it, PNPBIOS not ``device pnp0''. Close though,
only 3 letters out :)
--
Microsoft
On Sat, Mar 11, 2000 at 05:27:33PM -0500, Eric D. Futch wrote:
> # cat QUAKE | grep ^device | grep pnp
> #
>
> Attached is my kernel config.
>
Hmm, I saw exactly the same thing when I moved to -current and I was
certain that it was pnp0 that caused it, obviously not. Sorry for
wasting your time
Ugh... nevermind. Getting rid of the PNPBIOS option from the kernel
config got rid of all the unknown strangeness, although I still can't
explain it. The signal 11's only hit kdm, so I'm assuming that's a
different problem. Can someone commit the PnP magic for this modem or
should I just send-pr?
# cat QUAKE | grep ^device | grep pnp
#
Attached is my kernel config.
--
Eric Futch New York Connect.Net, Ltd.
[EMAIL PROTECTED] Technical Support Staff
http://www.nyct.net (212) 293-2620
"Bringing New York The Internet Access It Deserves"
On Sat, 11 Mar 2000, Mark Ove
On Sat, Mar 11, 2000 at 03:30:33PM -0500, Eric D. Futch wrote:
> I'm having some weird problems with PnP, I guess. I have a "SmartLink 56K
> Voice Fax Modem" that I just stuck into the computer. Before I added the
> PnP magic to src/sys/isa/sio.c, in the kernel messages just said unknown
> for i
I'm having some weird problems with PnP, I guess. I have a "SmartLink 56K
Voice Fax Modem" that I just stuck into the computer. Before I added the
PnP magic to src/sys/isa/sio.c, in the kernel messages just said unknown
for it, which is what I expected. So at that point I had three unkowns,
one
