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.
Hello,
I'm having problems with the ltmodem-8.31a7 autoload script (FC2 2.6.6-1.427) and thought this would be the best place to ask for help. I've worked with these drivers on Mandrake 8.2, never got it to work, and this is what has prevented me from using Linux... that was a few years ago.
When I execute ./autoload this is the output:
Diagnostic information and Guidance is being written to BLDrecord.txt
...and that's all she wrote.
It's supposed to configure automation of drivers, load at startup ( useful ). It utilizes /etc/modules.conf and I've read that in 2.6.n, /etc/modprobe.conf is the equivalent so I copied the everything from modprobe to modules.conf.
Any ideas?
Thanks
*this thread was originally in the General section but I figured Hardware was much more suitable*
I'm wondering if it would work if I just added this to modules.conf.
The modem drivers are NOT loaded on boot up, but are loaded on demand (typically by ppp initiation), thanks to the lines added by ./autoload to /etc/modules.conf:
# lt_drivers: autoloading and insertion parameter usage
alias char-major-62 lt_serial
alias /dev/tts/LT0 lt_serial
alias /dev/modem lt_serial
Unfortunately I can't test it right now.
> Nope, that didn't work, wvdial never detects a modem.
My modem is on COM11 in Windows and since Linux only supports ttyS0-4 do I need to change it to COM2 for checkout to find a modem on S1:
ttyS0<*1>: ATQ0 V1 E1 -- ATQ0 V1 E1 -- ATQ0 V1 E1 -- nothing.
Port Scan<*1>: S1
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 -- OK
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 Z -- OK
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 S0=0 -- OK
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 -- OK
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK
ttyS1_replace_with_ttyLTO<*1>: Modem Identifier: ATI -- LT V.90 Data+Fax Modem Version 6.00
ttyS1_replace_with_ttyLTO<*1>: Speed 2400: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Speed 4800: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Speed 9600: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Speed 19200: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Speed 38400: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Speed 57600: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Speed 115200: AT -- OK
ttyS1_replace_with_ttyLTO<*1>: Max speed is 115200; that should be safe.
ttyS1_replace_with_ttyLTO<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 S11=55 +FCLASS=0 -- OK
This is what it should look like, while mine fails and no modem is found.
Did you run the build module script first?
./build_module
That actually builds the module. Then you run the install script to put the module in the kernel module directory.
./ltinst2
Finally you run the auto load script last. That sets up the modprobe file and also creates the device (/dev/ttsLT0) in the /dev directory.
./autoload
I've upgraded to kernel 2.6.6-1.427 awhile ago and the sources just a few minutes ago. I've used ltmodem-8.31a7 but wvdial never detected the modem so I used ltmodem-2.6-alk-4.tar.bz2 and that's where I am now. I think this just might work.
Well, I'm definitely making progress, however, I am now more confused than I was before. Wvdial found a modem on ttyS12, symlinked to ttyLT0.
When I dialin with kermit it connects...
Trying: #######...
Device: /dev/ttyS12, modem: generic, speed: 115200
Dial timeout: 70 seconds
To cancel: type your interrupt character (normally Ctrl-C).
Call complete: "CONNECT 28800 V42bis".
Connecting to /dev/ttyS12, speed 115200
Escape character: Ctrl-\ (ASCII 28, FS): enabled
Type the escape character followed by C to get back,
or followed by ? to see other options.
----------------------------------------------------
Level 3 Comm nas2.2mi1 UQKT2
Username:/login:/Login:
Password:
Entering PPP Session.
IP address is 4.229.195.116
MTU is 1524.
Communications disconnect (Back at solare.flare)
----------------------------------------------------
I know for sure I'm connected but I can't access google, etc.
I asked my isp for the dns ip numbers at one point but I don't have them anymore, I'll have to ask again. I've tried gnome-ppp also but for some odd reason, afterwards, when I open a new tab it says 'bash: /dev/null: read-only' and when I reboot it does the same. I resolved it thanks to http://www.linuxquestions.org/questions/history/178660 but I have no idea why this is happening. Is gnome-ppp compatible with Fedora 2. It's not on any of the 4 cd's while MDK 10 installs it by default.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.