SlackwareThis Forum is for the discussion of Slackware 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.
That may be part of your problem. The ltmodem-8.29a will work with gcc 3.2 but not with gcc 3.3 (I ran into this problem with Feodra Core) Slackware 9.1 base install uses gcc 3.2 and I installed the ltmodem-8.29a.tar.gz package without any problems. I think the ltmodem-6.00 package was for kernel 2.2.x.
I suspect the ltmodem developers are working on this. (As I understand it they usually need to cajole Agere systems to compile the propriatary part of the driver in gcc 3.3.) Unless you have strong reasons to use gcc 3.3 I would try to get back to gcc 3.2.
I saw the same problem with a pctel driver in which the work around was to force the loading of the modules.
I did that and got /usr/bin/gcc -> gcc 3.2.3, so I'm guessing I didn't install correctly (no other version was listed). I guess I screwed up, I'm good at that. I'd like to think I'm getting DSL, but I'm not exactly sure when that will be, so for now I have to deal with this PCI modem.
How would I go about installing the 2.4.22 kernel drivers. From adz's last post I gather I'm using gcc 3.2.3 (still a 3.2 version, no? Or does it have to be just 3.2?) I copied the lt_modem.o and lt_serial.o into the ltmodem-8.26a9 directory and then tried to ./build_module, but it spit the same gcc=2 kernel version=3 error at me.
Opps, didn't see the previous three posts, before the following.
Don't understand, worked fine for me (running Slack 9.1 with default GGC 3.2.3) using ltmodem-8.26a9.tar.gz .
Had to run ./autoload twice, then after completed, had to edit /etc/moules.conf and add the three lines (in my Tecra 8100 post).
Prior to adding the lines, kppp query modem produced either modem busy or modem not responding (forget which), anyway, after editing and running depmod -a the little devil (lt modem) came to life.
The Mandrake rpm version of ltmodem went right on without having to change or edit /etcmodules.conf.
However MD isn't my cup of tea, and tried it just to see if it worked before attempting Slack 9.1. Actually I tried to shoe horn in the MD rpm version (both 2.4.22 kernels) but it wouldn't work, so bit the bullet and did ltmodem-8.26a9.tar.gz.
ADZ: A lot easier to deal with just one modem, especially with a laptop and when dual booting. Besides, the LT modem was conflicting with my USR external modem, it would query fine, but when kppp attempted to dial it would hang-up on ATZ.
Well, the lines wrote to my /etc/modules.conf before I even had to edit them. I'm going to try this again. Should I just copy the drivers from the /drivers-2.4.22 folder onto the original ones in /ltmodem-8.26a9? I checked out your Tecra post, DonLuis, but everything you said to do is written to my file.
I'm really confused, all of this should be working. You guys have been great in support, and I thank you, but maybe I just suck at this lol. Oh well, I don't like to quit, so I'll keep you guys up to date.
Correct me if I'm wrong, you have 2.4.22 kernel and ggc 3.2.3 right.
Confusing to me too. Did you or did you not make it completely through the install process ? And if so what happened (besides it writing the correct data to /etc/modules.conf)?
Have you done < modprobe -a > and checked for unresolved symbols ?
You could try copying the drivers (not sure), myself I'd remove it all and start fresh, if moving the drivers doesn't work.
I've found it can take hours going through the debugging drill, especially when you've made a lot of changes, whereas a fresh install cleans the platter in a few minutes (depending on processor speed and provided you have the Slack 9.1 CD's available).
I've got it. I think it might be that me trying the 6.0 package before, and then trying to do the 8.26a9 package over it caused the two .o files to feel they were they same and not overwrite. I completely reformatted, unzipped 8.26a9, ./build_module, ./ltinst2, ./autoload, ./checkout and got the same error as before.
The difference this time is that I ignored it, ./autoload twice more, minicom -s ->/dev/ttyLT0, and then I opened up KPPP despite errors and it worked. So I guess just ignore the errors and we should all be fine.
Thanks for the help guys; it is appreciated very much.