PDA

View Full Version : Knoppix and US Robotics 56k Internal Modem



tb75252
05-19-2003, 04:25 AM
I just purchased Knoppix v. 3.2 and must admit that I am completely new to Linux. (I am also not a great expert with Windows...)

Anyhow, it appears that Knoppix does not detect my internal model (US Robotics 56k - not a Winmodem AFAIK). Could someone please tell me if Knoppix works with this modem? If so, would you mind giving me DETAILED instructions on how to make it work or point me to a source of help? (Keep in mind I am a newbie - please do not overdo it with tech jargon.)

I tried finding an answer in the help files that come on the CD-ROM but there is nothing under keywords such as "modem" or "detection".

A big Thank You to anybody who will give me a hand.

Tiziano

EdlinUser
05-19-2003, 04:24 PM
PCI modems use nonstandard COM ports (COM 5 in this case, called ttyS4).
MattT helped me with a little script.
http://www.knoppix.net/forum/viewtopic.php?t=2322
Here is his script:

Type this into a root shell:

cd /dev
./MAKEDEV ttyS4
ln -s ttyS4 modem
chmod 777 modem
chmod 777 ttyS4

To get a root shell. KStart==>KNOPPIX==>root shell.
You'll have to type this each time you start your computer. I'm trying to write a BASH script to do this but so far no luck.

Welcome to Knoppix, suddenly computers are fun again!

tb75252
05-20-2003, 04:41 AM
I followed EdlinUser suggestion but KPPP indicates that "the modem is busy". (This is an improvement because before KPPP indicated that "the modem was not found".) Of course, it is not true that the modem is busy because I am not connected to the Internet when I type in the script.
Any other suggestions?
Thanks in advance.

Tiziano

garyng
05-20-2003, 07:15 AM
Have you tried Modem->Query Modem in the Setup option ?

tb75252
05-21-2003, 01:43 AM
In reply to garyng's message: Yes, I have queried the modem in the Setup section of KPPP and it tells me that the modem is busy. This is not true because I am not connected to the Internet when I query the modem...

Tiziano

garyng
05-21-2003, 03:40 AM
that would usually means the programs sent some AT command from there and got no response.

I am also puzzled some what about linux serial port handling myself. I have a good old Hayes PCMCIA which kppp have no problem accessing but if I try minicom, I just cannot connect to it, again, nothing shown in the terminal and all AT commands goes to a black hole.

andrewdodd13
07-26-2003, 12:28 PM
Are there any drivers out there which I could use to make my US Robotics 56k winmodem work?
I didn't actually know it was a winmodem until i booted windows selectivly and it asked to load a program called winmodem.
Please help!

transistordude
08-09-2004, 12:16 AM
Hello,
I am also looking for Knoppix use with an internal USR modem. In Windows, I get these infos:
Control Panel-> Phone and Modem Options->modems tab-> Properties button:
U.S. Robotics 56K
IO Range A400-A407, IRQ 22

In Knoppix, I get that COM3 is busy.
It is not supposed to be a winmodem.

transistordude
08-09-2004, 12:37 AM
On the modem card, it is written model 0778. Doing a google search, I found a person who claimed it was the same as 5610A. Any help please?
Frank

transistordude
08-09-2004, 01:20 AM
I just got my modem to work. :D It was on Com3 in Windows XP and got assigned to COM5 on Linux.
Here are some commands and responses that I got:

>>>>>>>>>lspci -v

02:02.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550])
Subsystem: US Robotics/3Com: Unknown device 00d7
Flags: medium devsel, IRQ 22
I/O ports at a400 [size=8]
Capabilities: [dc] Power Management version 2


>>>>>>>>>lspci -vv

02:02.0 Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 01) (prog-if 02 [16550])
Subsystem: US Robotics/3Com: Unknown device 00d7
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 22
Region 0: I/O ports at a400 [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-

>>>>>>>>> cat /proc/pci
Bus 2, device 2, function 0:
Serial controller: US Robotics/3Com 56K FaxModem Model 5610 (rev 1).
IRQ 22.
I/O at 0xa400 [0xa407].

cat /var/log/messages |grep ttyS
Aug 8 18:23:13 lightning kernel: ttyS04 at port 0xa400 (irq = 22) is a 16550A
Aug 8 19:49:53 lightning kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Aug 8 19:49:53 lightning kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
Aug 8 19:49:53 lightning kernel: ttyS04 at port 0xa400 (irq = 22) is a 16550A

cat /var/log/messages
Aug 8 18:23:13 lightning kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled
Aug 8 18:23:13 lightning kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Aug 8 18:23:13 lightning kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A
Aug 8 18:23:13 lightning kernel: Redundant entry in serial pci_table. Please send the output of
Aug 8 18:23:13 lightning kernel: lspci -vv, this message (12b9,1008,12b9,00d7)
Aug 8 18:23:13 lightning kernel: and the manufacturer and name of serial board or modem board
Aug 8 18:23:13 lightning kernel: to serial-pci-info@lists.sourceforge.net.
Aug 8 18:23:13 lightning kernel: ttyS04 at port 0xa400 (irq = 22) is a 16550A



after all that, I just did:
setserial /dev/ttyS4 irq 22 ( you will need to check your IRQ)
ln /dev/ttyS4 /dev/modem

Hope this helps.
Frank