If beta freeze is not a joke - what about this problem (several bug
reports from several people?) Hardrake claims my modem is Winmodem
3COM 5610. I have no idea if 5610 is winmodem or not - but mine is
3CP2977, PCI hardware modem that has been on duty for several months.
lspci -n:
02:0d.0 Class 0700: 12b9:1008 (rev 01)
lspci -vv:
02:0d.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
2977)
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 d000 [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-
lspcidrake:
unknown : US Robotics/3Com|56K FaxModem Model 5610
[COMMUNICATION_SERIAL]
dmesg:
Serial driver version 5.02 (2000-08-09) with HUB-6 MANY_PORTS MULTIPORT
SHARE_IRQ SERIAL_PCI ISAPNP enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
PCI: Found IRQ 9 for device 02:0d.0
ttyS02 at port 0xd000 (irq = 9) is a 16550A
Note, that it is kernel 2.4.2-3mdk; stock 7.2 came with old serial module
that did not support PCI modems and when I compiled serial-5.05 it
assigned ttyS4 and not ttyS2 (as was in readme, first 4 ports are reserved
for legacy devices).
-andrej
