Problems geting PCI US Robotics 5610 hardware modem to work

[rpeck]

I understand that a number of folks have gotten the US Robotics 5610 PCI hardware modem to work.

XP on the same box detects the device fine, and says it uses irq 23 and is at 0xc800. It configures
com3 to be the modem.

lspci on Knoppix shows irq 5 and the same address.

I've tried using setserial to configure the serial port, and kppp (Query modem...), pppconfig and
minicom to try to connect to the modem, with no luck. My setserial command looks something like:

setserial /dev/ttyS4 port 0xc800 irq 5 uart 16550A

I've tried irq 5 and 23, and ttyS4 and S7, all with no results. setserial -g shows the change, but
kppp and minicom fail to connect to the device. pppconfig hangs while probing the device.


Any clues?

Thanks!

[rpeck]

Various combinations of setserial and wvdialconf also fail. . . Rats. . .

[tdjokic]

I hope you will find something usefful here http://www.math.sunysb.edu/~comech/tools/PCImodems.html

This is good too:

"The 5610B works with Mepis 2004.06 and SM 3.3. I did nothing special. But you have to make sure you have it on the correct COM Port for your machine. Sometimes u have to confirm the com port via windoz - I hate to say that. You may have to link the port to /dev/modem.

Alternatively, try ls -l /dev/modem to find out the com port. You can also do things like ls -l /dev/ttyS2, etc. All from Command line. The latter gives the c 4 68 part of it. Also see man pages on ls. Watch the spaces in the code.

Two other handy pieces of code, from cmnd line as su:

mknod /devttyS2 c 4 68 Here S2 is COM3, etc.
(this sets S2)

ln -s /dev/ttyS2 /dev/modem Links e.g. S2 to /dev/modem"

[rpeck]

Yeah, I've alrady tried all of that. kppp says "modem not responding", and wvdialconf fails it its scan.

[tdjokic]

Out of ideas. Did you try any other Linux with this modem? Mepis, Kanotix, ...

[rpeck]

I'm installing RedHat right now, but the install is taking a looooong time for some reason. . .

XP detected the modem just fine, but I didn't have a chance to try it before I needed
to activate. . . and we happen to be out of activation codes at the moment. I might
end up trying that, if RedHat also fails.

[rpeck]

Another data point: I put another, identical modem (famous last words. . .) into a RedHat box that we had, and RH detected it at boot time.
I am going to try RedHat on the same box that I've been configuring Knoppix on, to see if RH also detects the modem on that box (the two boxes have different motherboards, so you never know. . .).

[wh7qq]

I understand that a number of folks have gotten the US Robotics 5610 PCI hardware modem to work.

XP on the same box detects the device fine, and says it uses irq 23 and is at 0xc800. It configures
com3 to be the modem.

lspci on Knoppix shows irq 5 and the same address.

I've tried using setserial to configure the serial port, and kppp (Query modem...), pppconfig and
minicom to try to connect to the modem, with no luck. My setserial command looks something like:

setserial /dev/ttyS4 port 0xc800 irq 5 uart 16550A

I've tried irq 5 and 23, and ttyS4 and S7, all with no results. setserial -g shows the change, but
kppp and minicom fail to connect to the device. pppconfig hangs while probing the device.


Any clues?

Thanks!

The following output in dmesg seems to be a clue (this message showed up with the 2.6.x kernels):

PCI: Using ACPI for IRQ routing
** PCI interrupts are no longer routed automatically. If this
** causes a device to stop working, it is probably because the
** driver failed to call pci_enable_device(). As a temporary
** workaround, the "pci=routeirq" argument restores the old
** behavior. If this argument makes the device work again,
** please email the output of "lspci" to bjorn.helgaas@hp.com
** so I can fix the driver.



If you boot:knoppix pci=routeirq and then sudo setserial /dev/ttyS4 port 0xXXXX irq XX uart 16550 (X's from sudo lspci -vv output for 5610), kppp will recognize the modem, dial and function normally online. The lspci output is hardware specific and varies with things like which pci slot your 5610 is in.

I am not sure if this trick works on the hd installed version...it does not work on kanotix 2005-02 live or hd installed.

wh7qq

[rpeck]

I tried this and several variations of it weeks ago, and the modem still was not detected by kppp (this is a hard-drive install). This is something of an oddball system (an Advantech shoebox-sized embedded PC), but RedHat Enterprise 3 and 4 are able to detect and use the modem just fine. Personally, I've given up on Knoppix/Debian for now, although we may want to get back to it some time.

If someone on the Knoppix team would like to try to get to the bottom of this we may be able to make a machine available on the network.