Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
09-29-2005, 03:25 AM
|
#1
|
LQ Newbie
Registered: Apr 2005
Location: Geraldton, Western Australia
Distribution: Ubuntu 6.06 Dapper Drake/Sabayon 3.2 Mini
Posts: 9
Rep:
|
Dynalink (Agere/Lucent chipset) Modem not working!
I just bought a Dynalink 1456VQH-T4 with Agere/Lucent chipset so I can use the Net on my SUSE 9.2 Pro box and now it wont connect as it cant find the device (on connection). Drivers installed fine but as soon as it trys to connect it cant find it. Is this SUSE having problems setting it to a /dev/ ?
Is there a way to fix this?
(If it helps I have a ASUS A7N8X-X mobo, with Athlon 2500+ and 512MB ram and the modem is located in (PCI Slot 7 (PCI bus 1, device 9, function 0)) as stated by Windows which it works fine in.)
Last edited by mercuryone; 09-29-2005 at 07:23 AM.
|
|
|
10-02-2005, 10:16 AM
|
#2
|
Member
Registered: Jul 2003
Location: San Francisco, CA, USA
Distribution: Kubuntu Hardy
Posts: 103
Rep:
|
Hi Mercuryone,
Which drivers did you install, and from where?
Hopefully you have the "ltmodem" driver package. If so, it should have created special device files under /dev/ttyLT0 or /dev/ttyLTM0. Depending on your distro, you may need to explicitly create a link to /dev/modem.
Another possibility is that you are using an unsupported Lucent modem (not all are supported). Have you tried running "scanmodem"?
Lots more information may be found here:
http://linmodems.technion.ac.il/
Regards,
Jeff Trull
|
|
|
10-06-2005, 05:35 AM
|
#3
|
LQ Newbie
Registered: Apr 2005
Location: Geraldton, Western Australia
Distribution: Ubuntu 6.06 Dapper Drake/Sabayon 3.2 Mini
Posts: 9
Original Poster
Rep:
|
I'm using the drivers that came with SUSE 9.2 Pro.
And it did create the special device files at /dev/ttyLT0 but said it was unable to find the device on trying to dial up.
Got any suggestions?
Last edited by mercuryone; 06-11-2011 at 04:39 AM.
|
|
|
10-06-2005, 10:43 AM
|
#4
|
Member
Registered: Jul 2003
Location: San Francisco, CA, USA
Distribution: Kubuntu Hardy
Posts: 103
Rep:
|
Hi Jason,
Here are a few things to check:
1) you should have a /dev/modem link to /dev/ttyLT0. Execute this command:
ls -l /dev/modem
You should get something like this back:
lrwxrwxrwx 1 root root 16 2005-09-28 15:35 /dev/modem -> /dev/ttyLT0
If you don't, this is probably your problem. An easy way to fix is to use YaST to configure /dev/ttyLT0 instead of /dev/modem. Look for "modem" under the Hardware section. Pick your modem, then select "edit", then change "Modem Device" from /dev/modem to /dev/ttyLT0.
2) the special kernel modules for the modem should be loaded. Execute this command:
/sbin/lsmod | grep lt
You should lines for lt_modem and lt_serial. If not, the driver has not been successfully installed.
3) you should have a supported Lucent/Agere modem. Not all of them are supported - that's where "scanmodem" would be helpful from the link I posted earlier. Another way to find out is to do this:
/sbin/lspci -n -d 11c1:
You should see something like this:
0000:00:06.0 Class 0780: 11c1:044e (rev 01)
Take note of the "device" number, which is 044e in my example. If this command gives no output, or the device number is not in the ranges 0440-044f or 0450-045c, you do not have a supported Lucent/Agere modem.
Good luck,
Jeff Trull
|
|
|
All times are GMT -5. The time now is 04:06 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|