Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to get my regular dial-up modem to connect on Suse 8.2 but I can't seem to get it...
Normally I connect via an ethernet so it's all working already, but I also have a dial-up connection that I have to use sometimes and I can't get Suse to find my modem.
i found setting up my dial up modem quite easy with suse. my 56k modem (which i don't use because i have a DSL connection...but they're nice to have) is an external Zoom v.92/v.90. what worked for me was (and this is where SuSE has that habit of making it way too easy for you) head into the YaST2 Controll Center. -click on network devices, then click on modem on the right part of the screen. if YaST detects your modem right away, it'll show you what it is, but if not, click on "Configure"....then go through the process of settign up your modem.
There might also be a chance that your 56k isn't suported ty linux (hence by being a winmodem).....for some reading about that head over to http://www.linmodems.org
From what I've read ~ Redhat has zero support for Winmodems (correct?) and when I built this computer I originally installed Redhat 9 which had no difficulty detecting, and utilizing this modem. Sooooooo ~ I'm taking the benefit of the doubt that it's not a winmodem. It's a US Robotics 56 faxmodem, which ScanModem (which I got off the website you gave me) said was a serial connection. Soooo ~ I configured Yast to read through all the serial ports and one of them says that the modem is not responding, every other one says that the modem is busy (which I assume means that there's something else connected to those ports). I'm using KPPP to try and connect.
Not sure why, but I had similar issues in Suse 8.2 with a USR 56.6k internal (hardware controller) modem. I had to link it to dev/modem (ln -sf /dev/ttyS4 /dev/modem) and then configure via Yast before I could get it to dial out. WHen trying to configure to the COM port itself, it wouldn't dial out...hope this helps.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.