US Robotics modem doesn't work after hardware upgrade
Posted on 2001-07-31
I have recently upgraded my system from P2-300 to an AMD Athlon system.
After the upgrade, my US Robotics 56K Voice/Faxmodem doesn't work in Linux
any more (but works in Win 98). I have tried vgetty and minicom and they
both failed to get any response from the modem. I am running Red Hat 7.1.
A few bits of info. The modem is an ISA PnP board, and /proc/isapnp
Card 1 'USR3070:U.S. Robotics 56K Voice INT' PnP version 1.0
Logical device 0 'USR3070:Unknown'
Device is active
Active port 0x3e8
Active IRQ 7 [0x3]
Port 0x2f8-0x2f8, align 0x0, size 0x8, 10-bit address decoding
IRQ 3 High-Edge
Alternate resources 0:1
Port 0x3f8-0x3f8, align 0x0, size 0x8, 10-bit address decoding
IRQ 4 High-Edge
Alternate resources 0:2
Port 0x3e8-0x3e8, align 0x0, size 0x8, 10-bit address decoding
IRQ 3,4,5,7 High-Edge
Alternate resources 0:3
Port 0x2e8-0x2e8, align 0x0, size 0x8, 10-bit address decoding
IRQ 3,4,5,7 High-Edge
The result of setserial during bootup is:
Serial driver version 5.05a (2001-03-20) with MANY_PORTS MULTIPORT SHARE_IRQ SER
IAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
ttyS02 at port 0x03e8 (irq = 7) is a 16550A
The output in the vgetty log says:
07/30 22:57:28 yS0 vgetty: experimental test release 0.9.27 / 11Mar01
07/30 22:57:28 yS0 mgetty: experimental test release 1.1.25-Feb01
07/30 22:57:28 yS0 reading generic configuration from config file /etc/mgetty+s
07/30 22:57:29 yS0 reading program vgetty configuration from config file /etc/m
07/30 22:57:29 yS0 reading port ttyS0 configuration from config file /etc/mgett
07/30 22:57:29 yS0 check for lockfiles
07/30 22:57:29 yS0 locking the line
07/30 22:57:29 yS0 lowering DTR to reset Modem
07/30 22:57:30 yS0 send: \dATQ0V1H0[0d]
07/30 22:57:30 yS0 waiting for ``OK''
07/30 22:57:50 yS0 timeout in chat script, waiting for `OK'
07/30 22:57:50 yS0 init chat timed out, trying force-init-chat
07/30 22:57:50 yS0 send: \d\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
07/30 22:57:54 yS0 waiting for ``OK''
07/30 22:58:14 yS0 timeout in chat script, waiting for `OK'
07/30 22:58:14 yS0 init chat failed, exiting...: Interrupted system call
07/30 22:58:14 ##### failed in mg_init_data, dev=ttyS0, pid=681
Any help would be greatly appreciated.