This is a report on experience in getting my 3com 5610 modem working... includes details of *relevant* output from all the configuration utilities I could find, and a *working* solution. (there seem to be a significant number of people in an identical situation) -------------------- Hi all, After reading all about how the 3com 5610 (or USR 5610, as 3com seems to refer to it) modem worked well in linux, I went off and bought one via paypal. Woohoo! .... or so I thought. Turns out it was a little more trouble to configure than expected. I'm running debian 3.0r2 on the i386 platform. I tried everything in the modem and serial howto's, to no avail. Having read through some nifty posts online, I found the suggestion to MAKEDEV -v ttyS4. That solved my problem. It seems I'm not the only person to have been stumped by this, so here is how I got mine working (and how I found the information about the modem. Just a note: before I managed to get mine working, setserial would always respond with strange messages like: # setserial /dev/ttys4 port 0xe400 irq 9 uart 16550A > /dev/ttys4: Input/output error (note: I had used small s in ttys4, because the 'ls ttys*' returned what looked like a valid ttys4 port) # setserial /dev/ttyS4 port 0xe400 irq 9 uart 16550A > /dev/ttyS4: No such file or directory (note: because I hadn't MAKEDEV'd the device yet) # setserial /dev/ttyS04 port 0xe400 irq 9 uart 16550A > /dev/ttyS04: No such file or directory (even though dmesg made me think that it was set up as ttyS04, which made no sense) Here are the important portions of various ways of finding out about the device itself: # cat /proc/pci > Bus 0, device 10, function 0: > Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 1). > IRQ 9. > I/O at 0xe400 [0xe407]. > # setserial -g /dev/ttyS* > /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 <-- serial port 1 > /dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3 <-- serial port 2 > /dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4 > /dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3 > # lspci -vv > 00:0a.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550]) > Subsystem: US Robotics/3Com USR 56k Internal FAX Modem (Model 5610) > Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- > Interrupt: pin A routed to IRQ 9 > Region 0: I/O ports at e400 [size=8] > Capabilities: [dc] Power Management version 2 > Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0+,D1-,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=2 PME- > # dmesg > Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled > ttyS00 at 0x03f8 (irq = 4) is a 16550A > ttyS01 at 0x02f8 (irq = 3) is a 16550A > PCI: Found IRQ 9 for device 00:0a.0 > Redundant entry in serial pci_table. Please send the output of > lspci -vv, this message (12b9,1008,12b9,00ad) > and the manufacturer and name of serial board or modem board > to serial-pci-info@lists.sourceforge.net. > ttyS04 at port 0xe400 (irq = 9) is a 16550A > Finally, to get the modem to work I used the following 4 commands: # MAKEDEV -v /dev/ttyS4 # setserial /dev/ttyS4 port 0xe400 irq 9 uart 16550A # setserial -g ttyS4 > ttyS4, UART: 16550A, Port: 0xe400, IRQ: 2 (I also added a line to /etc/wvdial.conf, after [Dialer Defaults] I inserted the line 'Modem = /dev/ttyS4') To get wvdial working, I then used: ----------- # wvdialconf wvdial.conf Scanning your serial ports for a modem. ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud ttyS0<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 4800 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 4800 baud, next try: 9600 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 19200 baud ttyS1<*1>: ATQ0 V1 E1 -- failed with 19200 baud, next try: 115200 baud ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. Port Scan<*1>: S2 S3 ttyS4<*1>: ATQ0 V1 E1 -- OK ttyS4<*1>: ATQ0 V1 E1 Z -- OK ttyS4<*1>: ATQ0 V1 E1 S0=0 -- OK ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK ttyS4<*1>: Modem Identifier: ATI -- 5601 ttyS4<*1>: Speed 4800: AT -- OK ttyS4<*1>: Speed 9600: AT -- OK ttyS4<*1>: Speed 19200: AT -- OK ttyS4<*1>: Speed 38400: AT -- OK ttyS4<*1>: Speed 57600: AT -- OK ttyS4<*1>: Speed 115200: AT -- OK ttyS4<*1>: Max speed is 115200; that should be safe. ttyS4<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK Found a modem on /dev/ttyS4. Modem configuration written to wvdial.conf. ttyS4<Info>: Speed 115200; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" -------------- Now my modem appears to be quite happy, although I have yet to bring it online (I'm writing this from a second dial-up system), when I run wvdial, I at least hear a clicking sound... Good luck to everyone else with their 3com modems... too bad the USR site includes *NO* useful information about how to get a modem set up in linux. Francis Esmonde-White francis@esmonde-white.com
Attachment:
3com_5610_modem_config.README
Description: Binary data