Date: Sat, 18 Mar 2000 16:35:14 -0500 From: "Jim Freeze" <jim@freeze.org> To: "Jim Freeze" <jim@freeze.org>, "Andrew" <acs@fl.net.au> Cc: "FreeBSD Questions" <freebsd-questions@FreeBSD.ORG> Subject: Re: User PPP and Internal PCI Modem Message-ID: <005601bf9121$d9c3cf60$f36ec8d0@lexmark.com> References: <Pine.BSF.4.05.10003181826100.21677-100000@jander.fl.net.au> <003201bf9103$757207c0$846ec8d0@lexmark.com>
next in thread | previous in thread | raw e-mail | index | archive | help
...the saga continues... Figuring that maybe the kernel does not support com3 and com4, I rebuilt the kernel with sio2 and sio3 support. sio2 - irq5 sio3 - irq9 I also noticed that the modem is showing up at irq11. Here is the report from my bios: Bus No. 0 Device No. 9 Func No. 0 Vendor ID 12B9 Device ID 1008 Device Class Simple COMM. Controller IRQ 11 The irq 11 is troubling. Not knowing what to do, I tried to experiment, I built the kernel with com3 at irq 11 and then with com4 at irq 11. ...still no change in the dmesg output, other than the irq number. The Linux modem page talks about setting skip_test in a startup script. I'm not sure this applies to FBSD. I suppose that I could force the irqs on the pci slot through the bios, but why would I get a different result than just setting the irq in the kernel to what the devices currently reads. Why, when I match irqs, does this device not get detected by fbsd? I would be very interested in any advice or similar experiences that others have worked through. Thanks Jim 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?005601bf9121$d9c3cf60$f36ec8d0>