On Saturday 05 March 2005 16:05, Matt T. wrote:
I think this is *not* an error message. Just some kernel developers complaining that the slamr module is not GPL, or something similar.
Despite this message it should work.
Again, if you *think* it does not work because of the "tainiting" messages, then try again. Just ignore the message, and see if it works.
You need to give more details. What modem - internal, PCMCIA, USB?
And do you run SuSE in 64 bit or in 32 bit. if 64 bit, are you sure the code is for 64 bit, and does not contain binary 32 bit parts?
Did you check /var/log/messages for any hints (despite the tainting nonsense)?
Check /var/log/messages if it gives you a device somewhere, such as /dev/modem, or /dev/ttySL0, or similar. And then see if that works, use it in kppp or kinternet, or minicom.
HTH, Matt
It is an internal pci modem, there are no other messages in the logs the modem simply fails when running a query from Kppp and fails to initialise in minicom. I have also tried it with kinternet. The modules load and device nodes are created. The rpm creates a link ttySL0 to modem. If I run slmodemd --alsa I get slamr0 does not exist errors, while ls -la /dev |grep slamr returns slamr0 to 4 I have tried recompiling the modules in the /lib/modules directory and manually inserting those too. The reason I posted was simply to establish if anyone else had a smartlink running on an AMD Sempron. check79:~ # lspci |grep Smart 0000:00:05.0 Modem: Smart Link Ltd.: Unknown device 8800 (rev 02) check79:~ # rmmod slamr check79:~ # modprobe slamr check79:~ #dmesg slamr: module license 'Smart Link Ltd.' taints kernel. slamr: SmartLink AMRMO modem. check79:~ # lsmod |grep slamr slamr 315908 0 check79:~ # ls -la /dev/ |grep ttySL lrwxrwxrwx 1 root root 11 Mar 6 23:31 modem -> /dev/ttySL0 crw-rw---- 1 root uucp 212, 0 Apr 6 2004 ttySL0 Thanks for the reply Chad