Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
Greetings everyone. I have the two modems listed above, on my desktop PC, both PCI modems. In SuSE the Lucent is detected as "Risq Modular LT Winmodem" or something like that, and installs with yast as "Modem0" This is just hunky-dory except that I cant get any dialer <Gnome-ppp, Gnome-dial, KInternet, KPPP> To work with it! Gnome-PPP doesnt Detect it, and KInternet just gives me "Exit Code 3". It doesnt even attempt to dial.
All my Windoze control panel says is "Lucent Winmodem" but it IS the PCI modem, So Im not 100% sure what it is. The conexant Im not really worried about, but if you can get it to work as well/or It would be great. I use linux 100% for everything else but I still have to go to windoze for internet so please dont make me have to do this!!
Guys be patient with me, Im new to linux and Im sure I didnt give you enough information, so If you need more I would be glad to give you more, Just please be patient and dont give up hope on me!
did you try a symlink from /dev/modem0 --> /dev/modem ?
I know with my Zoom (lucent based) the driver needed to be linked as modem and not modem0
Sorry about the misunderstanding about the drivers, My past experience on dialup modems was with 2.4
I would imaging that if the link is not the problem maybe the config script for pppd? I have never attempted a dual modem config, I assume that is what your doing?
Annother Idea: what about a live CD such as Mandriva Live with a similar kernal that will run pppd? That way you could view it's settings and adapt for you distro?
I am only trying to set up one modem. Forget about the conexant. I will try those things, but since I am on dial up <hint hint> Its a bit hard to get a Live CD distro, plus it wont really help me much. I will try those config files, and post a screenshot when I get home for some more specific details.
so for linking your /dev/modem0 to /dev/modem, you would open a terminal and type this:
text after > symbol is a comment, don't include it in your comands
Code:
$ su >change to super user (root)
<root password> >enter your root password
# cd /dev >change to the device directory
# ls -l m* >this is not needed but helpful the ls command used
>together with the -l option will display more detailed
>information about the directory such as
>file/dir permissions, the owner and most
>importantlu for us, existing links and whatthey
>point to.The m* simply tells ls to list all files
>beginning with m. You could changer this to
>modem* to get less results if you need to.
Here's an example of what it should look like:
Code:
brw-r----- 1 root disk 9, 0 Nov 2 17:27 md0
crw-r----- 1 root kmem 1, 1 Nov 2 12:26 mem
crw-rw---- 1 root root 13, 63 Nov 2 12:26 mice
lrwxrwxrwx 1 root root 12 Nov 2 12:26 midi -> snd/midiC0D0
lrwxrwxrwx 1 root root 12 Nov 2 12:27 midi1 -> snd/midiC0D1
crw------- 1 pyrael root 14, 0 Nov 2 12:26 mixer
crw-rw---- 1 root root 13, 32 Nov 2 12:26 mouse0
crw-rw---- 1 root root 13, 32 Nov 2 12:26 modem -> modem0
crw-rw---- 1 root root 13, 32 Nov 2 12:26 modem0
If you notice, the links are listed with the link name then -> and then the file it points to
since in the example we find the link is already created, we don't need to go any further.
However, we are giong to pretend that the link is wrong.
to remove the link :
Code:
#rm modem
This will remove the symbolic link from the directory
To create a new symbolic link, you use the command ln -s <source> <link name> :
if you type ls modem* you will list the entries for modem* in the usual view. If you use xtrem (etc..)
you will notice the link flashing red if it is a "broken link" this can be helpful when trying to pinpiont
the problem
I did all you said here, but I have a problem. First of all, when during installation SUSE recognize the modem, I get info that the modem is set as /dev/ttsLT0. When I configure it after, modem is then /dev/modem0. I tried to link to /dev/modem, but the problem is that neither LT0 or modem0 doesn't exists in /dev/. Can I make them manually or something?
I did some searching in google, and came across This Site .
Try thier drivers, They say that they have drivers (in rpm and source format) for the 2.6 kernel. You'll probably want to read ALL the documentation before using them. but (if Suse uses rpm) you should be able to install/configure you modem easilly.
Good luck and hope this helps.
By the way, if you don't already know, you can download the driver under windows and the switch to linux and mount windows to get the driver (since obviously you can't download with linux at the moment). ---just a tip
Well this site is for Conexant modems, and I have Lucent. Problem is that Suse recognizes the modem and reports that drivers are installed and that the modem is /dev/ttyLT0 or dev/modem0 but neither of this two files exists. Does anyone knows why? I use Suse 10.
This is the best advice I can give you, Try re-installing the driver. Here's the Source Tarball for Lucent Winmodems: ltmodem-2.6-alk-7.tar.bz2
Maybe, by re-installing the Driver for the modem, you can fix it. From what I read about winmodems and 2.6 is that many distros were released before there was full support for the modem. So, it is possible that the drivers your distro has supplied are a "generic" or "fit-all" driver. In order for the Lucent Winmodem to work under 2.4 (as I recall) you needed a program called lt_serial This program acted aas a kind of interpreter between the modem and OS. Winmodems are completely software based so, the best suggestion I can make is to try the above driver.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.