Using a U.S. Robotics Fax modem with Slackware 10.0 3923
On Sat, 18 Jun 2005 08:36:55 +0000, Alan Connor Not according to my understanding of logic and also my testing of the command. First, according to...
Dances With Crows For me, I get from lspci:
05:03.0 Serial controller: 3Com Corp, Modem Division (formerly US Robotics) 56K FaxModem Model 5610 (rev 01) (prog-if 02 16550) Subsystem: 3Com Corp, Modem Division (formerly US Robotics): Unknown device 00d3 Control: I-O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium Interrupt: pin A routed to IRQ 104 Region 0: I-O ports at 4028 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-
Forproc-pci, I get:
Bus 5, device 3, function 0: Serial controller: US Robotics-3Com 56K FaxModem Model 5610 (rev 1). IRQ 104. I-O at 0x4028 0x402f.
When I boot the system, the following is invar-log-messages...
kernel: ttyS4 at port 0x4028 (irq = 104) is a 16550A
Now the fact that port 0x4028 is the modem, as identified by either lspci, or byproc-pci, and that the kernel, while booting, buttociates this with ttyS4 tells me the modem is ttyS4. The fact that the irq matches is confirmatory evidence.
-- .~. Jean-David Beyer Registered Linux User 85642. V PGP-Key: 9A2FC99A Registered Machine 241939. ^^-^^ 16:40:00 up 2 days, 10:29, 3 users, load average: 4.05, 2.88, 2.94
Linux groups from Newsgroups