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