Greetings I have a LG smartlink modem running an AMD 64, Does anyone know why it won't work? I get " slamr taints kernel" error messages, even if I compile the driver manually, I have tried with the suse default packages on disk five with no joy, I have also downloaded older and newer drivers from linmodem.technion.org and all return the same results. Could some-one please help me here? Preferably some who has it working :) Thanks Chad
On Saturday 05 March 2005 21:43, Chadley Wilson wrote:
Greetings
I have a LG smartlink modem running an AMD 64, Does anyone know why it won't work? I get " slamr taints kernel" error messages,
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.
even if I compile the driver manually, I have tried with the suse default packages on disk five with no joy, I have also downloaded older and newer drivers from linmodem.technion.org and all return the same results.
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.
Could some-one please help me here?
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.
Preferably some who has it working :)
Thanks
Chad
HTH, Matt
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
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
This appears to be the same as the experience I had (also on a Sempron): modules load, but the driver doesn't actually work - see your evidence of the "modem" not responding. Try booting with pci=noacpi, and try a few different options with slmodemd (didn't know there were any...) The test with minicom is sufficient, if it fails trying kppp and kinternet is a waste of time. HTH, Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
Chadley Wilson wrote:
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
Just an explanation of the "taint" message. It means it's not a kernel maintained module, i.e don't report any kernel problem for a kernel that's tainted to the kernel developers, none of them will look at it as they can't troubleshoot something they know nothing about. Regards Sid. -- Sid Boyce .... Large Computer Systems Specialist - Retired Hamradio Callsign G3VBV and Keen Private Pilot Aeroplanes, Linux, Computers and Cricket my major passions ===== LINUX USED HERE, A Microsoft-free Computing Environment ====
I have a LG smartlink modem running an AMD 64, Does anyone know why it won't work?
Make up your mind - you have it running, or it doesn't work?
I get " slamr taints kernel" error messages, even if I compile the driver manually,
This is the kernel developers telling you that they don't want to be bothered with bug reports from binary-only device drivers. Note that the slamr is in the losemodem category, binary-only driver guts with some GPL glue to fit it into Linux. I found that the slamr driver does indeed load on some hardware, but in fact doesn't run properly as it's not supposed to run on that particular hardware. I was able to make it work reliably by inserting some seconds delay between the loading fo the first and second part of the driver, and fiddling acpi. Guess I was lucky, YMMV. Find out first whether the driver is supposed to work with your hardware. If yes, file a bug report ;) Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
On Saturday 05 March 2005 22:17, Volker Kuhlmann wrote:
I have a LG smartlink modem running an AMD 64, Does anyone know why it won't work?
Make up your mind - you have it running, or it doesn't work?
I get " slamr taints kernel" error messages, even if I compile the driver manually,
This is the kernel developers telling you that they don't want to be bothered with bug reports from binary-only device drivers. Note that the slamr is in the losemodem category, binary-only driver guts with some GPL glue to fit it into Linux.
I found that the slamr driver does indeed load on some hardware, but in fact doesn't run properly as it's not supposed to run on that particular hardware. I was able to make it work reliably by inserting some seconds delay between the loading fo the first and second part of the driver, and fiddling acpi. Guess I was lucky, YMMV.
Find out first whether the driver is supposed to work with your hardware. If yes, file a bug report ;)
Agreed, and I understand their point of view, the real question here, is why running the exact same kernel as I do on the intel system, do I not get this error, in this case I physically used the same modem, it works on the intel P4 HT system? I only get the " slamr taints kernel" error messages when I put the modem into an AMD system. I have three amd systems running with different boards and chipsets, ie, ATI, SIS and VIA, The intel systems on test are running INTEL, VIA and SIS chipsets, (chipsets refers to North and South bridge controllers) I am using the suse default kernel on both systems, check79:~ # uname -r 2.6.4-52-default This is why I have poked the question of it being an AMD CPU related issue. (Of course mainboards could also be the issue as boards for AMD are different to those use for intel) Chad
On Monday 07 March 2005 15:28, Chadley Wilson wrote:
On Saturday 05 March 2005 22:17, Volker Kuhlmann wrote:
I have a LG smartlink modem running an AMD 64, Does anyone know why it won't work?
Make up your mind - you have it running, or it doesn't work?
I get " slamr taints kernel" error messages, even if I compile the driver manually,
This is the kernel developers telling you that they don't want to be bothered with bug reports from binary-only device drivers. Note that the slamr is in the losemodem category, binary-only driver guts with some GPL glue to fit it into Linux.
I found that the slamr driver does indeed load on some hardware, but in fact doesn't run properly as it's not supposed to run on that particular hardware. I was able to make it work reliably by inserting some seconds delay between the loading fo the first and second part of the driver, and fiddling acpi. Guess I was lucky, YMMV.
Find out first whether the driver is supposed to work with your hardware. If yes, file a bug report ;)
Agreed, and I understand their point of view, the real question here, is why running the exact same kernel as I do on the intel system, do I not get this error, in this case I physically used the same modem, it works on the intel P4 HT system?
I only get the " slamr taints kernel" error messages when I put the modem into an AMD system. I have three amd systems running with different boards and chipsets, ie, ATI, SIS and VIA, The intel systems on test are running INTEL, VIA and SIS chipsets, (chipsets refers to North and South bridge controllers)
I am using the suse default kernel on both systems, check79:~ # uname -r 2.6.4-52-default
How about upgrading your kernel? You can install a new kernel while keeping this one. A lot happened in the kernels, I recommend to test with a new one, and base further debugging on it.
This is why I have poked the question of it being an AMD CPU related issue.
And just to make sure I got it: You are *not* using a 64 bit AMD, and *not* installing SuSE for amd64, but you are using 32 bit SuSE, and a 32 bit AMD Sempron? And you are compiling a 32 bit version of the smartlink driver, on a 32 bit SuSE installation?
(Of course mainboards could also be the issue as boards for AMD are different to those use for intel)
yes, it is not just the CPU. A lot is different.
Chad
regards, Matt
Hi, Chadley Wilson wrote:
On Saturday 05 March 2005 22:17, Volker Kuhlmann wrote:
I have a LG smartlink modem running an AMD 64, Does anyone know why it won't work?
Make up your mind - you have it running, or it doesn't work?
I get " slamr taints kernel" error messages, even if I compile the driver manually,
This is the kernel developers telling you that they don't want to be bothered with bug reports from binary-only device drivers. Note that the slamr is in the losemodem category, binary-only driver guts with some GPL glue to fit it into Linux.
I found that the slamr driver does indeed load on some hardware, but in fact doesn't run properly as it's not supposed to run on that particular hardware. I was able to make it work reliably by inserting some seconds delay between the loading fo the first and second part of the driver, and fiddling acpi. Guess I was lucky, YMMV.
Find out first whether the driver is supposed to work with your hardware. If yes, file a bug report ;)
Agreed, and I understand their point of view, the real question here, is why running the exact same kernel as I do on the intel system, do I not get this error, in this case I physically used the same modem, it works on the intel P4 HT system?
I only get the " slamr taints kernel" error messages when I put the modem into an AMD system. I have three amd systems running with different boards and chipsets, ie, ATI, SIS and VIA, The intel systems on test are running INTEL, VIA and SIS chipsets, (chipsets refers to North and South bridge controllers)
I am using the suse default kernel on both systems, check79:~ # uname -r 2.6.4-52-default
This is why I have poked the question of it being an AMD CPU related issue. (Of course mainboards could also be the issue as boards for AMD are different to those use for intel)
Chad
You don't need slamr kernel module if running in alsa mode, AFAIK. I am running an ATIIXP modem on a x86 system and just need to load atiixp-sound-modem, start slmodemd -a and wvdial ... Same for some VIA modems, all documented in the README. I heard a 64bit solution is near, but AFAIK dsp.o is needed and smart-link only provides a 32bit version until now, but I could be wrong. Thomas
On Tuesday 08 March 2005 16:14, Thomas Renninger wrote:
You don't need slamr kernel module if running in alsa mode, AFAIK. I am running an ATIIXP modem on a x86 system and just need to load atiixp-sound-modem, start slmodemd -a and wvdial ... Same for some VIA modems, all documented in the README.
I heard a 64bit solution is near, but AFAIK dsp.o is needed and smart-link only provides a 32bit version until now, but I could be wrong.
Thomas
Thanks Thomas and all those who replied; I finally figured it out, and am just returning the support that this list offered me, hope some-one finds it usefull. To get the smartlink modem working. You have to make sure that the following is also installed before trying to compile an alsa module from the slmodem-2.9.x.tar.gz which is available from www.smlink.com or linmodems.technion.ac.il/packages/smartlink I used the slmodem-2.9.9a.tar.gz install these rpms as well alsa-lib-1.0.6-3.i386.rpm (should already be there) alsa-lib-devel-1.0.6-3.i386.rpm (critical) from your cds or installation source. download your kernel source rpm and build the sources. I used apt-get and the freshrpm repos. (If you want a simple script for that I have made one!) my apt sources.list rpm http://ayo.freshrpms.net fedora/linux/3/i386 core updates freshrpms rpm http://rpm.livna.org/ fedora/3/i386 stable unstable testing rpm-src http://rpm.livna.org/ fedora/3/i386 stable unstable testing The modem installation. Copy this script (below) into the folder where you save the slmodem-2*.tar.gz file, just make sure you don't have multiple versions in the same folder otherwise it will try install all of them. I found that by using the 2.9.9a I don't get the taint kernel error You will see in my rc.modules (not for alsa supported modems), that after the modprobe slamr I repeat the loading of slmodemd init script, I found that if I don't then the slmodemd script runs before the slamr module is loaded and the modem will fail. Now Thomas I know you said you don't need the slamr module for alsa mode this is perfectly true. So I have tried to accommodate this. :) I know there are other modules for alsa support, I don't know what they are. I could extend the script to test for them. Would appreciate a bit of community help, contribution or advise with this:) #cat modem_install #!/bin/bash updatedir=$(pwd) tar xzvf slmodem-2*.tar.gz cd slmodem-2* make make install lsmod |grep snd[_-]intel8x0m if [ $? -eq 0 ]; then cd $updatedir/slmodem-2*/modem make SUPPORT_ALSA=1 cd $updatedir make install SUPPORT_ALSA=1 cp $updatedir/slmodemd-alsa /etc/init.d/slmodemd chkconfig --add slmodemd chkconfig slmodemd on else cp scripts/slmodemd /etc/init.d/ chkconfig --add slmodemd chkconfig slmodemd on cd ../ cp rc.modules /etc/rc.modules chmod +x /etc/rc.modules fi #Done The rc.modules file must also be in the same folder as the script above with the slmodem*.tar.gz file also I have made a modified version of the init script slmodemd for alsa called slmodemd-alsa (attached, I hope you get it otherwise on request I can send it to you directly). make sure this file is also in the same folder. Also make sure all the scripts are set executable: #chmod +x scriptname #cat /etc/rc.modules #!/bin/bash modprobe slamr /etc/init.d/slmodem restart /etc/init.d/slmodem restart I have tested this script on intel, amd, and via CPUs using three different modems, two were different laptops ZW9 and the Clevo 8089 and the other is a genuine smartlink chip on a modem card made by LG Electronics. Just moved from one system to the other. I have three PCs (laptops excluded) running sis and via chipsets. If anyone would like to contribute we could possibly have this made into an rpm and put up for download somewhere to simplify things for others. Cheers OH and thanks again guys Chad
participants (5)
-
Chadley Wilson -
Matt T. -
Sid Boyce -
Thomas Renninger -
Volker Kuhlmann