Modem Problem Was: Dennis Kibbe lspci -vv

[Dennis Kibbe]

Quoting Michael Havens <bmike1@vei.net>:

> I ran home to find out what lspci -vv would say and am now (because I can not
> get online) in the library to relay the message (or at least the relevant
> part otherwise it would be VERY long).
> 
> 00:0b.0 Serial controler: US Robotics/3Com 56K FaxModem
> Model 5610 (rev 01) (prog - if 02 [16550])
>      Subsystem: US Robotics/3Com: Unknown Device 00d3
>      Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- 
>      Status: Cap + 66 Mhz- UDF- FastB2B- ParErr- DEVSEL=medium > TAbort-
> <MAbort ->SERR-<PERR+
>      Interrupt: pin A routed to IRQ 9
>      Region 0: I/O ports at ec00 [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-
> :-)Mike(-: 
> 480-844-1511 
> hope this helps


OK, It's a Model 5610 which seems to be supported under Linux judging by the
guick Google search I did.

At this point I'd go back to kppp and make sure it points to the device. Further
searching Google should give you some insight, too.

I think you'll be able to finish the job on your own now.

Dennis





-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/