LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-17-2003, 09:40 PM   #16
shepper
Member
 
Registered: Mar 2003
Location: Dry, Dusty and Conservative
Distribution: OpenBSD, Debian Wheezy/Jessie
Posts: 449

Rep: Reputation: 33

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.
 
Old 11-17-2003, 09:49 PM   #17
salted
LQ Newbie
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 20

Original Poster
Rep: Reputation: 0
Adz:
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.

Shepper:
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.
 
Old 11-17-2003, 09:55 PM   #18
adz
Senior Member
 
Registered: Jun 2003
Location: Sydney
Distribution: Debian, FreeBSD
Posts: 1,713

Rep: Reputation: 53
Come tom think of it, if you installed from source then the binaries could be in /usr/local/bin. Check there aswell. Then redo the symlink to whichever you like.
 
Old 11-17-2003, 10:03 PM   #19
DonLuis
Member
 
Registered: Feb 2003
Location: Republic of Texas
Distribution: ZW-WBEL4-Slack-RHat-Puppy-Debian
Posts: 75

Rep: Reputation: 15
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.

Last edited by DonLuis; 11-17-2003 at 10:19 PM.
 
Old 11-17-2003, 10:30 PM   #20
salted
LQ Newbie
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 20

Original Poster
Rep: Reputation: 0
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.

Thanks,
salted
 
Old 11-17-2003, 11:04 PM   #21
DonLuis
Member
 
Registered: Feb 2003
Location: Republic of Texas
Distribution: ZW-WBEL4-Slack-RHat-Puppy-Debian
Posts: 75

Rep: Reputation: 15
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).
 
Old 11-18-2003, 04:31 AM   #22
justwantin
Member
 
Registered: Aug 2003
Location: Melbourne, Australia
Distribution: Slackware, Slackware ARM, Salix and Porteus
Posts: 552

Rep: Reputation: 45
I didn't follow the whole thread but I was able to do up my winmodem driver modules in slack-9.1 without any problems using ltmodem-8.26a.tar.gz. after a full install of slack.

ltmodem-6.0 whatever would not work.

I followed all steps as per ltmodem script "build_module" and followed the post install steps/instructions.
 
Old 11-18-2003, 10:54 PM   #23
salted
LQ Newbie
 
Registered: Sep 2003
Distribution: Slackware 10.0
Posts: 20

Original Poster
Rep: Reputation: 0
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.
salted
 
Old 11-18-2003, 11:47 PM   #24
DonLuis
Member
 
Registered: Feb 2003
Location: Republic of Texas
Distribution: ZW-WBEL4-Slack-RHat-Puppy-Debian
Posts: 75

Rep: Reputation: 15
Congratulations, you'll note I had run mine twice to get rid of the errors, plus editing modules.conf.

Was elated when kppp queried the modem successfully.

Enjoy.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
errors with automount, module loading and several ones worth the reading... ParticleHunter Linux From Scratch 4 07-26-2005 03:58 AM
How do I stop drivers loading? soaked Fedora 3 07-18-2005 06:06 PM
loading G-force drivers havoc Linux - Newbie 1 04-20-2004 04:00 AM
lots of insmod: errors when loading slackware Belize Slackware 2 12-02-2003 03:34 PM
Mozilla not loading up, just gives me errors. Seph64 *BSD 2 06-03-2003 02:45 AM


All times are GMT -5. The time now is 07:02 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration