Re: pci hardware modem not working
Levi Waldron wrote:
>
> I just went out and bought a brand new, fully hardware PCI modem (for
> $68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
> to get assigned a ttyS* port during the boot process. The Modem HOWTO
> gives some tips for finding out the essential information, then says
> without giving specific directions, to use that info with setserial to
> assign a serial port to the hardware. However I am at a loss as to how to
> actually do that. Here are the relevant results of what I have tried so
> far. Any advice, or pointers to more detailed instructions?
>
> In the BIOS, PnP OS is OFF.
>
> Using pppconfig and setting the device to any of /dev/ttyS*, then pon,
> gives "No dial tone" results in plog. Output of wvdialconf are at the
> bottom of the info below.
>
> # dmesg | grep tty
>
> # dmesg | grep modem
>
> # lspci -vv
>
> 0000:02:0b.0 Serial controller: 5610 56K FaxModem 56K FaxModem Model 5610
> (rev 01) (prog-if 02 [16550]) Subsystem: U.S. Robotics: Unknown device
> 0110 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 23 Region 0: I/O ports at 2400 [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-
>
>
> # scanpci
>
> pci bus 0x0002 cardnum 0x0b function 0x00: vendor 0x12b9 device 0x1008
> 5610 56K FaxModem 56K FaxModem Model 5610
>
Hi, I acquired such a modem recently, similar to yours but with no Voice.
It's a USRobotics "Performance Pro" 56K V.92 model 5610b. After mucking
around, finally got it working on Debian Sarge, 2.6.7 kernel. dmesg gave me
a line like this:
ttyS14 at I/O 0xe800 (irq = 10) is a 16550A
A modem appeared to be at ttyS14.
But no ttyS14 existed in /dev. So one had to be created, like this:
# cd /dev
# ./MAKEDEV ttyS14
Make a symlink to /dev/modem like this:
# ln -s ttyS14 modem
For my dial-up connection, etc/ppp/options had to be modified. Under
"Require the peer to authenticate itself ...", "auth" was changed to
"noauth". Add yourself to the dip (for KPPP) and dialout groups like this:
# adduser steve dip
# adduser steve dialout
You may need to reboot the computer at this point. KPPP should now work, or
if you prefer, run pppconfig and edit Com to /dev/ttyS14 (or ttyS*
wherever). Pon should work.
If you get the modem "handshake" but can't get to google or ping anyone,
try:
# ifconfig eth0 down
Didn't need setserial for my setup. Maybe this'll work for you or someone
else.
Steve
PS The setserial command that might work for you (didn't for me):
# setserial /dev/ttyS4 irq 23 port 0x2400 autoconfig
Reply to: