PCI modem troubles

[fbsd_user]

The problem you describe is common in the 4.x versions of FBSD.
I have seen these solutions voiced previously in this list.

1. Check the PC's bios, look for a toggle to disable plug-n-play
function.

2. Check that your PCI card is not in the first or last PCI
expansion
slot on the motherboard.

3. Disable com1 & com2 in PC's bois

4 add   option   PCI_ENABLE_IO_MODES
to your kernel source and recompile. See LINT

5. add   device  puc
         option  PUC_FASTINTR
to your kernel source and recompile. See LINT

6. Follow bug fix using this url
http://www.freebsd.org/cgi/query-pr.cgi?pr=40636


Try one of the above, one at a time until your problem goes away.



-----Original Message-----
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Alex
Sent: Sunday, September 21, 2003 5:58 PM
To: FreeBSD Questions
Subject: PCI modem troubles

I'm having a little trouble getting FreeBSD 4.8 to recognize my PCI
modem. I
have a US Robotics 56k Performance Pro Modem (not a Winmodem) that
FreeBSD
stubbornly refuses to talk to.

At the urging of kind people on this list, I enabled "pccard" in my
rc.conf
file and I set up my kernel config file with the line "device sio"
after
commenting out sio1 and 2, i.e.:

# device                sio2    at isa? port IO_COM3 irq 5
# device                sio3    at isa? disable port IO_COM4 irq 9
device sio

The system is still not recognizing the modem on PC1, as the message
in
"dmesg" reads

pci1: <unknown card> (vendor=0x12b9, dev=0x1008) at 8.0

Things got even more interesting when I looked at the output of
"pciconf -lv", as the follwoign lines came up:

none1 at pci1:8:0: class=0x070002 card=0x00d312b9 chip=0x100812b9
rev=0x01
hdr=0x00
    vendor   = '3COM Corp, Modem Division (Formerly US Robotics)'
    device   = '3cp803598 USR 56k Internal Modem'
    class    = simple comms
    subclass = UART

It looks like the system is actually finding the modem and is
recognizing
it, but for reasons beyond my understanding it stops short of
actually
talking to the thing. Can anyone offer any suggestions?

Thanks a lot,
Alex

_______________________________________________
freebsd-questions at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"