Click to See Complete Forum and Search --> : USRobotics 56K External
nowiz@linux
12-15-2002, 10:12 AM
I'm having trouble getting my USRobotics modem to work with Redhat 8. I'm able to dial out with it, but it will not connect...I get a no carrier message. I haven't been able to find much about problems like this on the web, but it seems that a lot of people are able to connect theirs to a linux machine. I have checked the USRobotics website and found one article about actually configuring the modem to work with unix type systems. Has anyone had to actually do such a thing? It has something to do with saving certain settings in the NVRAM...I just don't want to ruin the modem. I know the modem works with windows machines. I would appreciate any help. THANKS!
z0mbix
12-15-2002, 10:37 AM
I used to use this modem when I first started using Linux. I used kppp to configure and dial-up. It was all very easy to use :)
ShieldWolf
12-15-2002, 10:56 AM
The US Robotics 56K External modem is one of the very best choices there is for any operating system.
Do you have it set up so that you can hear it dial and try to negotiate a protocol? If so, are you getting a dialtone?
Perhaps the cable connecting the modem to the wall jack is faulty. Those cables are cheap, and sometimes poorly made. Try a new cable, and make sure it's plugged in all the way.
Are you dialing the right number? It's easy to transpose a couple of numbers, especially if you're working from memory.
nowiz@linux
12-15-2002, 12:10 PM
As I stated before I was able to use the same setup with a windows computer, so I'm sure that my cables are okay. I am able to dial out and I hear the pings and bings but apparently the modems aren't communicating because the Send Data and Receive Data lights only flash for a brief second before I get the no carrier message. I posted to a PPP newsgroup and was told it was a problem with my modem or ISP. This is why I attempted a different ISP, but I received the same message, so I'm assuming it's the way my modem is configured. Maybe it's the way it's not configured. The USR sight mentioned something about changing the dip switches to 'no echo offline commands' (which I haven't tried yet...I thought I'd see what others had to say first). Thanks for your input.
ViMan
12-15-2002, 02:57 PM
I had no problem getting online with my US Robotics External Modem. All I did was run kppp and choose the modem as /dev/ttyS0 (since it was on my first serial port) and add the other necessary information and everything worked fine. Maybe the problem is with the Authentication method.
nowiz@linux
12-15-2002, 03:03 PM
I find this strange...
I reinstalled redhat...which isn't the first time.
This time I did not install gnome...I installed KDE instead and I connected no problem on the first try. I didn't have to change my modem at all....
Why would this be?
Happy to be connecting!!
fancypiper
12-15-2002, 03:05 PM
Check your /etc/wvdial.conf file and make sure your user name is listed second and your password is third (phone number is first in the section I'm referring).
I have had a version of rp3 to mis-configure that.
You can follow your error messages in real time by opening an x terminal and[phil@fancypiper phil]$ su -
Password:
[root@fancypiper root]# tail -50f /var/log/messages
Modem and connection troubleshooting:
Modem NHFs (http://linuxnewbie.org/nhf/Modems)
Modem HOWTO (http://www.tldp.org/HOWTO/Modem-HOWTO.html)
The kppp Handbook (http://docs.kde.org/2.2.2/kdenetwork/kppp/)
Dial-up Networking Configuration Using KDE's Kppp (http://www.linuxheadquarters.com/howto/networking/kppp.shtml)
Troubleshooting ISP Connection Problems (http://www.onlamp.com/pub/a/onlamp/2001/05/10/ppp.html)
Connecting to AOL with Linux (http://www.yolinux.com/TUTORIALS/LinuxTutorialAOL.html)
nowiz@linux
12-15-2002, 09:52 PM
I have no idea why it didn't work before, but I again reinstalled Redhat. I figured I had nothing to lose and it worked with KDE. This time I installed Gnome and it worked perfectly fine.
Thanks for your replies. I have no idea why it wouldn't work on the first two installs but it works now...Hooray!
fancypiper
12-15-2002, 11:21 PM
It's usually the fault of the nut that holds the mouse. :D
(Ducks and runs for cover)
nowiz@linux
12-16-2002, 08:48 AM
I don't know if this could do it... but my first two installs I used ISOs which I downloaded from an FTP site (and did the check media before installing) and the last two times I used the disks that came with my Redhat 8 bible. I think I'll trash the downloaded disks...
Hired Goon
07-18-2003, 08:12 PM
Sorry for bumping this old topic back up but I'm having similar problems with my US Robotics 56K External. I'm running Mandrake 9.1. When I try to connect I with KPPP, I get the "Modem Ready" message, then it just hangs on "Initializing Modem..." . I dont hear any sounds at all.
I think I've configured KPPP correctly, but when I query the ATI text areas are empty. It's like it knows theres a modem there, but doesnt know what kind it is.
I noticed there are dip switches on the back of the modem, I was thinking maybe they are not set up right:
Current Settings
1 UP (Data Terminal Ready normal)
2 UP (Verbal Result Codes)
3 UP (Supress Result Codes)
4 Down (No Echo, Offline Commands)
5 Down (Auto Answer Off)
6 UP (Carrier detect normal)
7 Down (Load Factory Defaults)
8 Down (Smart Mode)
Any help would be greatly appreciated!
Thank you. :)
nowiz@linux
07-18-2003, 09:25 PM
I hope this helps... my dip switches are set to I believe the factory defaults and are as follows
1 up
2 up
3 down
4 up
5 down
6 up
7 up
8 down
Hired Goon
07-18-2003, 11:03 PM
Nope. No dice. :( Thanks anyway.
Hired Goon
07-20-2003, 02:51 AM
Anyone have any other ideas? :(
mdwatts
07-20-2003, 07:27 AM
Originally posted by Hired Goon
Anyone have any other ideas? :(
Have you tried any of the suggestions in the JL Help Files on Modems (http://justlinux.com/nhf/Modems) as they should give you a few commands/apps you can use to test the modem.
Searching the JL forums for i.e. 'pppd' or 'pppd wvdail' or 'pppd modem' should find you previous threads with other ideas you can try.
Do you have a symlink from the actual device to /dev/modem?
ls -al /dev/modem
and see if it is linked from the actual device.