Gah! Winmodems and compilers as always

slakmagik · 07-08-2003, 11:42 PM

Here we go again.

I tried to compile drivers for a Lucent modem before and went through hell and back with it and never did get the whole thing to work. So I bought a hardware modem and got it working with my P100 and Vector (I think it was Vector) but it died. So now I've got a PCTel modem in my Athlon box running Slack9 and I tried to compile those drivers. I installed from a screwy magazine disk so I'm missing silly little things like BSD games from the Y diskset and the kernel source.

But I do seem to have stuff in /usr/include, so I used the --with-includes=/usr/include flag. Maybe I screwed that up. And this is with the 2.4.20 kernel and gcc 3.2.2. Yet here's my error messages:

Code:

root@slackath:/home/digiot# insmod pctel
Using /lib/modules/2.4.20/misc/pctel.o
/lib/modules/2.4.20/misc/pctel.o: The module you are trying to load 
(/lib/modules/2.4.20/misc/pctel.o) is compiled with a gcc
version 2 compiler, while the kernel you are running is compiled with
a gcc version 3 compiler. This is known to not work.
root@slackath:/home/digiot#

Then insmod ptserial gives a string of stuff like the first line in the following and ends with this:

Code:

/lib/modules/2.4.20/misc/ptserial.o: unresolved symbol put_uart_mcr
/lib/modules/2.4.20/misc/ptserial.o:
Hint: You are trying to load a module without a GPL compatible license
      and it has unresolved symbols.  Contact the module supplier for
      assistance, only they can help you.

Last time something like this happened, I ripped Vector out and installed CORE to give myself room to try to recompile the kernel and it got the modules to load but still didn't work after that. And I am not never no way ripping out my Slack 9.

I've ordered DSL (finally) and I really really hope I can get that working but, until then, does anybody have suggestions? I've done the whole search and read thing from last time but I obviously still don't get it.

This is so frustrating. I'm sick of having to deal with XP on this Celeron box just so I can surf. Thanks.

slakmagik · 07-09-2003, 11:42 PM

footfrisbee · 07-10-2003, 04:00 AM

Check out this site for the latest on pctel drivers.

Cerbere · 07-10-2003, 05:11 AM

I think you need to brush up on your searching skills. I had the same problem last night and I just entered 'pctel slack 9' in the little box at the top of this forum, which led me to this thread: http://www.linuxquestions.org/questi...=pctel+slack+9
The gist of it is that you use:
insmod -f pctel
insmod -f ptserial
to force the loading of the modules. It's ugly but it works.

Enjoy!
--- Cerbere

slakmagik · 07-10-2003, 06:50 PM

That isn't what I wanted to do. I did that before with the Lucent drivers. I did it again anyway. This failure's different. pctel loaded with complaints. ptserial did this:

|--root@slackath Thu Jul 10 19:37:11
|--bash 2.05b /home/digiot/misctext $ insmod -f ptserial
Using /lib/modules/2.4.20/misc/ptserial.o
Warning: loading /lib/modules/2.4.20/misc/ptserial.o will taint the kernel: non-GPL license - GPL linked with proprietary libraries
See http://www.tux.org/lkml/#export-tainted for information about tainted modules
Warning: loading /lib/modules/2.4.20/misc/ptserial.o will taint the kernel: forced load
/lib/modules/2.4.20/misc/ptserial.o: init_module: Input/output error
/lib/modules/2.4.20/misc/ptserial.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg

dmesg
PCTel: No device detected. Abort module loading.

less /var/log/syslog
Jul 10 16:48:22 slackath modprobe: modprobe: Can't locate module char-major-10-1
34
Jul 10 16:49:32 slackath last message repeated 2 times
Jul 10 16:54:16 slackath modprobe: modprobe: Can't locate module char-major-10-1
34

Thanks for the responses and any further help. 'lspci' gives me '00:0b.0 Modem: PCTel Inc HSP MicroModem 56 (rev 02)' but, to be honest, I don't even know what that means. But I'm guessing I've got the wrong device file pointing at the modem, somehow?

slakmagik · 07-10-2003, 09:04 PM

This is driving me daft. I figured out I'd had the wrong chipset so uninstalled the checkinstall package and recompiled - had a nifty time with that because of various stupid typos trying to pass the '--with-kernel-includes=' option because of my goofy setup, but it compiled and this time I was able to force them. But now 'ppp-on' gives me 'connect script failed' whereas 'kppp' gives me 'modem busy'. I can't find the ppp logs that should either be in /var or in /etc/ppp and 'locate' didn't turn up any likely suspects so I can't tell *why* it failed or why kppp thinks my modem should be busy.

I did notice this in /var/log/messages:

PCI: Found IRQ 11 for device 00:13.1
PCI: Sharing IRQ 11 with 00:0b.0

Later, there is stuff about finding a PC Tel modem and root starting pppd - then "exit" and that's it.

*sigh*

slakmagik · 07-10-2003, 09:21 PM

Argh. Helpful error messages. It was supposed to create a 'modem' link to /dev/ttyS15 but didn't - so I edited the modem link to reflect that. Might have got it backwards, but I think that was it. I cranked up minicom and ATZ got 'OK' and ATI 3 got a report of the driver and version. And now ppp-go takes longer to crap out before it reports the script failed.

This is progress, right?

I don't know. When I had the hardware modem I input the same stuff to pppsetup. I have no idea why it won't work now when it did then. I *think* that may be all that's left that's wrong but I definitely don't know how to handscript a connection.

Cerbere · 07-11-2003, 05:09 AM

I still think you're not being tenacious enough with your searches. While searching the other night I found some accounts of similar issues (but luckily, I didn't run up against them). I'm guessing that device 00:13.1 is your sound card (or more likely onboard sound) since some of the posts mention that IRQ conflict.

Try these links (and follow the links that they mention as well).

Thread dealing with scagman's troubles and eventual success with a PCTel (makes fascinating reading, really)
http://www.linuxquestions.org/questi...ighlight=pctel

Thread with a quick review of what bongski55 had to do to get his PCTel working
http://www.linuxquestions.org/questi...&highlight=hsp

a How-To that deals with several of the PCTel issues (including the IRQ conflicts)
http://www.peacefulaction.org/sayamindu/pctel.html

and finally, the thread I gave you yesterday, which links to both of the threads above
http://www.linuxquestions.org/questi...=pctel+slack+9

Enjoy!
--- Cerbere

slakmagik · 07-11-2003, 10:22 PM

Windows is toast.

I got it working. Like I say, I was actually beyond the modem driver issues - couldn't get the connection to work. But I did follow out all those links. One of them was new to me. What actually worked, maybe, was the third. It's actually a Windows solution. They mention a bug in the drivers that can only be solved by rmmod and reinserting them or even rebooting altogether. So I rebooted and did *nothing* but insmod and startx so I could run kppp via fluxbox. Whether that did it or redoing the process just fixed something I'd screwed up before, I got everything to work up to NO CARRIER in the connect script which is better than ppp-go's simple "script failed". So then I poked around in kppp and realized it was set by default to a hardware flow control and I flipped that to software. Whether that was it or not, I tried to connect again and my jaw dropped when it actually did it.

Rock and roll! Thanks folks.