3 Com/US Robotics 3CP5610A Controller-Based Modem ??? Help Request - Research To Date
Posts: 1
On 11/29/04 I paid for the SimplyMEPIS CD from Mepis.org. I also bought the SimplyMEPIS book by Roblimo and got another CD that way. SimplyMEPIS 2004.04 installed beautifully on dedicated hdb1 (even recognized and configured my HP LaserJet 5L printer), but after over two months of trying, looking at forums both on both Mepis.org, MepisLovers, and Google, I cannot get my US Robotics/3 Com modem (3CP5610A) to work, so I can't register my SimplyMEPIS or do apt-gets in Mepis (I'm sending this from Win98SE). I also have sound issues, but may be able to correct those with updates if I can get my modem working.
On the spectrum of expertise, I'm not the technical expert like many in the forums, but I really like MEPIS as distribution. I am excited that it will allow me to keep Windows XP from ever entering my home. I did build my computer about three years ago, but Linux represents my first experience doing meaningful work in a command line mode. I've learned a lot, but don't have the knowledge to solve this problem.
I am attaching -
A) items I think are facts about my situation
B) output of various SimplyMEPIS list commands
C) a Win98SE hardware and IRQ profile of my machine
D) the workarounds I've tried thus far, and results
I've tried to be self-sufficient regarding this issue, but at this point, any help would be greatly appreciated.
A) RESEARCH -
Verified that the 3 Com/US Robotics 3CP5610A is controller-based, PCI 56K FaxModem via Andrew Comech Linux modem page. The modem is in fact recommended by users of other Linux distributions.
Verified in modem manual documentation - ???modem is designed to be compatible with Linux versions 1.2 and higher, and drivers are included in kernel???. (Do they mean ???Red Hat??? when they indicate ???Linux 1.2??? and higher?)
Verified modem is using COM 5 in Windows 98SE. IRQ assignment appears to be IRQ 5.
B) VARIOUS SimplyMEPIS KONSOLE LISTS -
$ kudzu -p
class: MODEM
bus: PCI
detached: 0
driver: unknown
desc: "5610 56K FaxModem|56K FaxModem Model 5610"
vendorId: 12b9
deviceId: 1008
subVendorId: 12b9
subDeviceId: 00d7
pciType: 1
pcidom: 0
pcibus: 0
pcidev: a
pcifn: 0
# cat /proc/pci
Bus 0, device 10, function 0:
Class 0700: PCI device 12b9:1008 (rev 1).
IRQ 11.
I/O at 0x9000 [0x9007].
# setserial -g /dev/ttyS*
/dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: 16550A, Port: 0x02f8, IRQ: 3
/dev/ttyS15: No such device or address
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
/dev/ttyS4, UART: unknown, Port: 0x0000, IRQ: 0
/dev/ttyS5: Permission denied
/dev/ttyS6: Permission denied
/dev/ttyS7: Permission denied
/dev/ttySL0: No such device or address
# lspci -vv
0000:00:0a.0 Serial controller: 5610 56K FaxModem 56K FaxModem Model 5610 (rev 0
1) (prog-if 02 [16550])
Subsystem: 5610 56K FaxModem: Unknown device 00d7
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort - <MAbort- >SERR- <PERR-
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 9000 [disabled] [size=8]
Capabilities: <available only to root>
# dmesg
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
ls -l /dev/ttySx
jwwjr@1[~]$ ls -l /dev/ttyS4
crw-rw-rw- 1 root root 4, 68 2003-12-05 17:02 /dev/ttyS4
jwwjr@1[~]$ ls -l /dev/ttyS3
crw-rw-rw- 1 root dialout 4, 67 2001-04-14 20:44 /dev/ttyS3
jwwjr@1[~]$ ls -l /dev/ttyS2
crw-rw-rw- 1 root dialout 4, 66 2001-04-14 20:44 /dev/ttyS2
jwwjr@1[~]$ ls -l /dev/ttyS1
crw-rw-rw- 1 root dialout 4, 65 2003-01-02 00:10 /dev/ttyS1
jwwjr@1[~]$ ls -l /dev/ttyS0
crw-rw-rw- 1 root dialout 4, 64 2003-01-02 00:10 /dev/ttyS0
jwwjr@1[~]$ ls -l /dev/modem
ls: /dev/modem: No such file or directory
jwwjr@2[~]$ ls -l /usr/sbin/pppd
-rwsr-xr-- 1 root dip 232536 2004-07-16 13:30 /usr/sbin/pppd
jwwjr@2[~]$ ls -l /usr/bin/kppp
-rwxr-sr-- 1 root dip 546424 2004-08-03 22:58 /usr/bin/kppp
When running KPPP (as user) /Configure/Device, get the following -
/dev/modem + ???Connect??? = ???kppp cannot find /dev/modem???
/dev/ttyS0 + ???Connect??? = ???Expecting OK??? ???Initializing Modem???(modem hangs)
/dev/ttyS1 + ???Connect??? = ???Expecting OK??? ???The modem does not respond???
/dev/ttyS2 + ???Connect??? = ???Expecting OK??? ???The modem is busy???
/dev/ttyS3 + ???Connect??? = ???Expecting OK??? ???The modem is busy???
/dev/ttyS4 + ???Connect??? = ???Expecting OK??? ???Unable to open modem???
(Note: Can ???Query??? modem in /dev/ttyS0, but all ATI fields are blank.)
C) Win98SE HARDWARE AND IRQ PROFILE OF jwwjr MACHINE
Resource Summary Report
Modem
Port = COM 5
IRQ = 5
I/O Range = 1000 ??? 1007
LinModem list modem utility in Win98SE and returned the following -
PCI Config Info:
Vendor ID: 12b9
Device ID: 1008
SubVendor ID: 12b9
SubDevice ID: 00d7
Revision ID: 201
jwwjr PC
Processor AMD Athlon 1.0 ghz, 266 mhz Front Side Bus
Motherboard ASUS A7M - 266mhz, Rev. 1003, DDR RAM Support - PCI 2.1 spec
Bios Award Medallion BIOS v6.0 (02/13/01)
RAM 512 meg PC-2100 DDR RAM (2 X 256 meg DIMMS, 266 mhz)
Case CoolerMaster ATC-101 - Brushed Aluminum Mid-Tower
Power Supply Sparkle Power - 400 watt ATX PS, v. 2.01
Hard Drive(a) IBM Deskstar, 40 gig, 7,200 rpm, 8.5 ms seek
Hard Drive(b) Seagate Barracuda 80 gig
Floppy Drive Sony 1.44
CD-RW TDK VeloCD - 16/10/40x
DVD Pioneer Slot Loading - 40x DVD ROM DVD-106
Monitor Hitachi CM771 19 in, .22 dot pitch
Graphics Card ATI Radeon 7200 R100QD with 32 meg DDR VRAM
Sound Card C-Media Digital CMI8738/C3DX PCI Audio
Speakers Labtec Pulse 424 with 8" wood subwoofer
Modem US Robotics 3CP5610A 56k Performance Pro Controller-Based PCI
Network Interface CardNot Installed
Keyboard IBM Active Response Keyboard
Mouse Logitec Wheel Mouse
Printer HP LaserJet 5L
Operating System Windows 98 Second Edition
jwwjr Windows 98SE
IRQ Device
0 System timer
1 Standard 101/102-Key or Microsoft Natural Keyboard
2 Programmable interrupt controller
3 Communications Port (COM2)
4 Communications Port (COM1)
5 U.S. Robotics 56K Fax PCI (COM 5)
5 ACPI IRQ Holder for PCI IRQ Steering
6 Standard Floppy Disk Controller
7 ECP Printer Port (LPT1)
8 System CMOS/real time clock
9 VIA Tech 3038 PCI to USB Universal Host Controller
9 VIA Tech 3038 PCI to USB Universal Host Controller
9 ACPI IRQ Holder for PCI IRQ Steering
9 SCI IRQ used by ACPI bus
10 CMI8738/C3DX PCI Audio Device
10 ACPI IRQ Holder for PCI IRQ Steering
11 Radeon DDR
11 ACPI IRQ Holder for PCI IRQ Steering
12 PS/2 Compatible Mouse Port
13 Numeric data processor
14 Primary IDE controller (dual fifo)
14 VIA Bus Master PCI IDE Controller
15 Secondary IDE controller (dual fifo)
15 VIA Bus Master PCI IDE Controller
D) VARIOUS FORUM RECOMMENDATIONS TRIED THUS FAR/RESULTS
Tried modem in SimplyMEPIS versions 2004.04 and 2004.06
Result: Negative
____________________________________________________
Tried running legacy 2.4 kernels in both versions
Result: Negative
____________________________________________________
# setserial /dev/ttyS4 irq 5
Result: Negative
____________________________________________________
???run the following in konsole???
ls -l /usr/sbin/pppd
ls -l /usr/bin/kppp
???then???
Open kuser
Click on ???Groups??? tab
Find ???dip???
Check for username in ???User In Group??? Category
If not, add it
???If that's not the problem, run-???
ls -l /dev/ttyS4
(???if modem is recognized as a ttyS4 device???)
(???results may be: crw-r--r-- 1 root root 4, 68 2004-12-16 18:23 /dev/ttySx???)
???Then, as root, try:???
# chmod a+w /dev/ttyS4
???If that doesn't work, revert it by:???
# chmod o-w /dev/ttyS4
Result: Negative - was able to get it to change permissions to rw- rw- rw-, when tried to ???Connect??? in KPPP ttyS4 message ???The modem is busy???.
_________________________________________________________
???Check jumpers and make sure set correctly??? ???Since Linux (not necessarily Mepis) like modems that are on ttys1(com2), set your modem for com2, irq3. It will no longer be pnp.???
Result: Negative. Tried to change from COM 5 to COM 2 in Win98SE software, will not allow to remove and point away from COM 5, it resets to COM 5. Per research at US Robtics site, the modem is jumperless, and cannot be configured away from COM 5 in Win98SE. Interestingly, they also indicated for AOL users (which I am not), be aware of underlying ???DOS Box software??? that points modem to COM 4 in DOS for AOL users.
_________________________________________________________
???I have a US Robotics 5610 pci modem, PnP set it up as ttyS4, to get in working, ran this in root:???
rm /dev/modem
ln -s /dev/ttyS4 /dev/modem
As user set kppp to use /dev/modem
Result: ??? Negative. Also noticed that there appears to be no /dev/modem in my SimplyMEPIS file system.
__________________________________________________________
???Using FCC ID, got www.driverguide.com and search for driver.???
Result: Negative. Did this and all that was listed for this modem was an RPM beta that US Robotics indicates they don't officially support.
__________________________________________________________
???Disable AC97 on-board modem controller in BIOS
Result: Negative. Modem still works in Win98SE, still doesn't work in Linux.
__________________________________________________________
???Try ???acpi=off??? on GRUB command line.
???Try adding ???pnpbios=off??? as well.
Result: Negative.
___________________________________________________________
???Open a terminal and su to root.???
???Open text editor and open the following file???-
/etc/modutils/modem
???Next, add the following lines to the file???-
pre-install serial rm /dev/modem
post-install serial ln -s /dev/ttySx /dev/modem
???Where x is the comm port that your modem uses, ie ttyS0 is comm 1, ttyS1 is comm 2, and so on. Save the file and exit your editor.???
???Next, as root, run the following???:
# update-modules
???Exit terminal and reboot.???
Result: ??? Negative. Struggled to undo this after trying it.
# setserial /dev/ttyS4 uart 16550A port 0x9000 irq 11 baud_base 115200 spd_vhi skip_test
# ln -sf /dev/ttyS4 /dev/modem
Result: ??? Negative.?? Is it because /dev/modem does not exist in my file structure? (see top, initial post with discovery)
____________________________________________________________
???Buy an external serial modem???:
www.pricewatch.com ??? CenDyne
www.adamantcomputers.com ??? Zoom 1125
Result: I could try this, as well as move to broadband now, but it seems like my current modem should be able to be made to work here. It has been extremely reliable in Win98SE, will run for hours without dropping connection. Also, I'd like to have the modem as a working backup when I do move to broadband.
____________________________________________________________
As stated, I've tried most everything I've been able to find, but after over 2 months, can't solve this. My layperson theory is something related to the COM5 (or the strange note from US Robotics regarding the "DOS box, COM4" for AOL on Windows users (I'm not using AOL)) location in Win98SE is not detected properly by MEPIS, and may contribute to the fact that there is no /dev/modem in the file structure of my installation, but I don't know how to fix it if that is the issue.
Again, any help would be appreciated, if you want to use my hardware info in a support database, please feel free to do so.
Thanks
Jack
USB 5610B Modem Problems
Posts: 93
I'm confused! I've had a 5610B working in Mepis 2004.06 and SM3.3 with no problems for over a year. Haven't needed any drivers either.
Only thought I have is have you tried as su:
mknod /devttyS2 c 4 68 Sets Com 3
ln -s /dev/ttyS2 /dev/modem Sets link to /dev/modem
I have had to do this sometimes with a new install. I believe you said your modem is on COM 3, which I used in the above code. Sometimes you have to start over from the ground up by deleting /dev/modem.
U.S. Robotics - 5610B-???
Posts: 13
I can't believe mepis was the only distro that will recognize my old winmodem out of the box but not this U.S. Robotics - 5610B in the new computer I built for my grandma. When i query modem, it finds the
modem, i think, but then the modem query results come up empty. when i try to dial out, i don't get past initializing modem/ expecting OK. It just sits there forever. I would seriously appreciate it if anyone had any ideas.
I don't think its a problem with the bios or anything, because this is a dual boot machine and the modem works fine with xp.
PLEASE HELP!!
I'm not that familiar with
Posts: 16
I'm not that familiar with Mepis but I was having similar problems with my external robotics modem.I entered bios setup and set modem=com3 then I started mepis,entered modem setup,unchecked lock,set speed to 115200,set modem to cr/lf(i think thats right),leave name set to "my modem",set ttys2(you may have to try each one),press ok and then re-enter then querry modem.Windows loves to use com5 for modems,even over-riding the bios setting but if you force it to com3 in bios,it should work with mepis,at least it worked for me.I hope this helps you as I know the frustration of setting up a modem in ANY operating system.
5610B
Posts: 93
I forgot to mention that for my latest install, where I switched modems from my exp comp to my main system, I set in KPPP modem setup ttyS2 [mine is on COM3]and all was go from there. I did not use /dev/modem.
HTH.
modem
Posts: 49
I din't read through this long thread, but did you try:
# setserial /dev/ttys4 irq 11 port 0x900 autoconfig
then do:
# chown root:dialout /dev/ttys4
and add yourself to the dialout group?
Bob
Modem problems
Posts: 93
Pls try the code I gave in my recent reply but use ttyS4 in both places. Then go into KPPP and set /dev/modem. This should work. Like the guy says....works for me!
Modem Works in 2.4 Kernel / Setserial Needs Baud_Base
Posts: 10
This modem works if you boot with the 2.4 kernel and follow the usual set up instructions (setserial, /dev/modem, KPPP). See the other thread on this:
(or search for "internal hardware modem").
Regards,
dr9873
2.6 kernel
Posts: 49
You might need to load a module depending on how your 2.6 kernel was configured.
Try:
# modprobe ppp_generic
If this works, you can add the line: ppp_generic to the /etc/modules file.
Bob
USR 5610 Still Only in 2.4 Kernel
Posts: 10
After some months interruption, I tried this ppp_generic both with modprobe on the command line (as root) and in the /etc/modules file, but neither solved the problem. If there are any other suggestions of how to get this modem, which works in the 2.4 kernel, to work in 2.6, please post them.
Here is what I do to get the USR 5610 PCI modem to work in 2.4:
1. Put the following in /etc/serial.conf:
/dev/ttyS4 uart 16550A port 0xd800 irq 9 ^fourport ^auto_irq skip_test baud_base 115200 spd_vhi autoconfig
(these become arguments for the setserial command during startup)
2. Configure KPPP to use ttyS4. Alternatively, /dev/modem could be set up as a link to ttyS4, but I don't do this.
3. I also turn off the "lock file" check in the KPPP modem setup.
All of this apparently works, but only with the 2.4 kernel, not with 2.6. I am using the latest SimplyMEPIS 3.1.1-1 installed on my hard drive.
Regards,
dr9873
I have run into this problem
Posts: 1
I have run into this problem with my 3CP5610B USR controller based modem. The problem is that your modem is not being detected because it is on COM5! Can you run ppp manually? You may be able to manually enter ttyS4 as your com port.
I never could get Debian to detect the modem. However, runing ppp and manually entering ttyS4 worked for me with Dam Small Linux (DSL).
http://www.damnsmalllinux.org/
SuSe 9.1 detects everything automaticlly.
Since we have a common problem please feel free to contact me at
COM1 = ttyS0
COM2 = ttyS1
COM1 = ttyS2
COM4 = ttyS3
COM5 = ttyS4
Jack