Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I try to make someone to convert to Linux, and so installed a SuSe 9.0 system on his machine.
The problem is that he has a Lucent winmodem and I cannot make it work:
SuSe 9.0 auto-detected the modem, auto-installed its driver (/dev/ttyLT0), but anytime I try to dial in, the system becomes and stays irresponsive (no more response to keys pressed on the keyboard or mouse moving or clicks), meanwhile I see endless HDD activity.
I saw that the modem uses com3 in windows, so I tried to change it to /dev/ttyLT2 under linux. No panic this time, but I got an immediate error message saying that no response from modem.
Wow, when I use wvdial directly to dial in, dialing starts in not more than 5 minutes.
Besides, only the first dialing takes so long to start, any following dialing is started immediately. It is a good thing.
Now I think this problem may have something to do with the modem init string.
However, I do not know why this modem works only if it is setup as device /dev/ttyLT0, whilst it uses COM3 in windows?
I think it should use ttyLT2, instead, but I do not have such device.
Should I create it? How?