Modem doesn't work after updating the kernel

Hungry ghost · 04-25-2005, 12:35 PM

Hi all. I'm using FC3 and a Neto Dragon modem driver. I used yum to update the kernel to the latest version available for FC3, which is 2.6.10-1.760_FC3. After updating the kernel I rebooted uninstalled the previous modem driver and reinstall the driver in the new kernel. The problem is, when I execute

Code:

/sbin/modprobe slamr

to load the modem modules I get this error:

[root@localhost slmodem-2.9.10]# /sbin/modprobe slamr
FATAL: Error inserting slamr (/lib/modules/2.6.10-1.760_FC3/extra/slamr.ko): Unknown symbol in module, or unknown parameter (see dmesg)

So I tried dmesg. The output was very long; here's the slamr prt of it:

slamr: module license 'Smart Link Ltd.' taints kernel.
slamr: Unknown symbol get_device
slamr: Unknown symbol put_device
slamr: Unknown symbol device_release_driver
[root@localhost slmodem-2.9.10]#

Then I tried with depmod and the modprobe command again, but I get the same results. By the way, this is the output of lsmod:

[root@localhost user]# /sbin/lsmod
Module Size Used by
parport_pc 26629 1
lp 12077 0
parport 37001 2 parport_pc,lp
autofs4 23493 0
sunrpc 156325 1
nls_iso8859_1 4161 1
vfat 12609 1
fat 39905 1 vfat
dm_mod 55637 0
video 15813 0
button 6609 0
battery 9285 0
ac 4805 0
md5 4033 1
ipv6 231681 8
stv680 24781 0
videodev 9537 1 stv680
uhci_hcd 31449 0
ehci_hcd 35273 0
hw_random 5845 0
i2c_i801 8141 0
i2c_core 20801 1 i2c_i801
snd_intel8x0 33249 0
snd_ac97_codec 67489 1 snd_intel8x0
snd_pcm_oss 47989 0
snd_mixer_oss 17089 1 snd_pcm_oss
snd_pcm 93001 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss
snd_timer 29125 1 snd_pcm
snd 52645 6 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 10017 1 snd
snd_page_alloc 9541 2 snd_intel8x0,snd_pcm
8139too 26433 0
mii 4673 1 8139too
floppy 57841 0
ext3 116297 2
jbd 69977 1 ext3
ata_piix 8517 0
libata 41285 1 ata_piix
sd_mod 17217 0
scsi_mod 122177 2 libata,sd_mod
[root@localhost user]#

There's no slamr module there. Does anyone know what might be wrong here??
Second question: The driver's readme says the kernel sources must be installed and configured. Shall I reconfigure the kernel after upgrading it with yum?? If so, how to do it the easy way??
Thanks in advance.

fancypiper · 04-25-2005, 12:53 PM

As the error message states, I would check dmesg.

Do you have a symbolic link /usr/src/linux that points to the new kernel source? Red Hat/Fedora use /usr/src/linux-<number here> instead and you may need to create /usr/src/linux

I have a win<something> or some other kernel module driver I have to install.
# Compiling/installing kernel modules
You will need to have installed:
1. The developmental packages (compiler)
2. The kernel-source code that matches your running kernel
3. The module source or install code

Check out your system and look under the hood and see if you installed the stuff you need to do the job. Open an x terminal and type in this sequence of commands to see what kernel we are running and see if you have the kernel source installed:

Code:

[fancy@tinwhistle fancy]$ su -
Password:
[root@tinwhistle root]# uname -r
2.4.20-28.7

I am running kernel version 2.4.20-28.7. Do I have the proper source code?

Code:

[root@tinwhistle root]# cd /usr/src
[root@tinwhistle src]# ls -alc
total 3
drwxr-xr-x    4 root     root          136 Jun 12 14:53 .
drwxr-xr-x   16 root     root          424 Jun  4 12:04 ..
lrwxrwxrwx    1 root     root           14 Jun  4 12:11 linux-2.4 -> linux-2.4.20-28.7
drwxr-xr-x   16 root     root          584 Jun  4 12:11 linux-2.4.20-28.7
drwxr-xr-x    7 root     root          168 Jun  4 12:08 redhat
[root@tinwhistle src]#

I do have the same kernel version source code installed in the directory /usr/src/linux-2.4.20-28.7 and there is a symbolic link named linux-2.4 pointing to it.

If you don't see something similiar to this (but in color), you will need to install the kernel source.

NOTE: I noticed that Red Hat didn't make the symbolic link /usr/src/linux that all of the INSTALL files that I have read mentioned that I need. I may as well make one now to save editing the files in the source code every time I need to compile anything concerning the kernel. So, I'll make that link just now:

Code:

[root@tinwhistle src]# ln -s linux-2.4.20-28.7 linux         
[root@tinwhistle src]# ls -alc
total 3
drwxr-xr-x    4 root     root          160 Jun 12 15:46 .
drwxr-xr-x   16 root     root          424 Jun  4 12:04 ..
lrwxrwxrwx    1 root     root           14 Jun 12 15:46 linux -> linux-2.4.20-28.7
lrwxrwxrwx    1 root     root           14 Jun  4 12:11 linux-2.4 -> linux-2.4.20-28.7
drwxr-xr-x   16 root     root          584 Jun  4 12:11 linux-2.4.20-28.7
drwxr-xr-x    7 root     root          168 Jun  4 12:08 redhat
[root@tinwhistle src]#

Ah, there it is, so that's done.

Next, did I install the compiler?

Code:

[root@tinwhistle src]# gcc -v          
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113)
[root@tinwhistle src]#

Yes, I have a compiler installed.

If you don't have those two things installed, you have to install them first off your install CD.

If they are installed, download the source and happy compiling.

Make sure you carefully read the README and INSTALL files after extracting and before compiling/installing.

Hungry ghost · 04-25-2005, 01:03 PM

The slamr part of dmesg output was:

slamr: module license 'Smart Link Ltd.' taints kernel.
slamr: Unknown symbol get_device
slamr: Unknown symbol put_device
slamr: Unknown symbol device_release_driver
[root@localhost slmodem-2.9.10]#

I think 2.6 kernels install on /usr/lib/modules/<kernel_version/build, and as for the driver's readme and makefile, I think it's this build directory what Makefile is looking for, so I think it's ok there. The problem is that modprobe can't load the module. Maybe I must reconfigure the kernel??

fancypiper · 04-25-2005, 01:26 PM

BTW, the kernel is installed in /boot, the kernel-source code is located at /usr/src/linux-<version number here>

Once again, try and answer these questions. I think you have a kernel that doesn't match the kernel-source code.

What kernel are you running?

uname -r

Have you got the same kernel-source in the directory /usr/src/linux-<version number reported by uname -r here>?

Do you have a symbolic link /usr/src/linux that points there?

Were all instructions read and followed in the INSTALL and README files in the extracted zipped tarball?

Hungry ghost · 04-25-2005, 02:14 PM

hmm, there is no linux or linux-<kernel_version> in /usr/src but this is what I have in /lib/modules: 2.6.10-1.760_FC3 2.6.9-1.6.9-1.667 which are the previous kernel and the latest, installed this morning. Inside /lib/modules/2.6.10-1.760_FC3/build I found this:

arch fs ipc Makefile net sound
crypto include kernel mm scripts usr
drivers init lib Module.symvers security

I'm not sure, but this seems to be the kernel itself. For some reason it seems to be in /lib/modules/2.6.10-1.760_FC3. Maybe FC3 put it there?? or maybe 2.6 kernels it go there?? I don't know, but the driver's Makefile has this line:

Code:

KERNEL_DIR:=/lib/modules/$(shell uname -r)/build

so it seems to be looking in the right location. The driver's Readme says "Default KERNEL_DIR is '/lib/modules/<kernel-version>/build'. Many Linux Distributions use directory '/usr/src/linux-<version>' also", so I guess it's ok there. Maybe I must reconfigure the kernel. Shall I just run make xconfig, and that's it??

P.S.: I had installed this driver with the previous kernel and worked fine, being that the kernel's source code was not in /usr/src/linux, so I guess it's about something else.

fancypiper · 04-25-2005, 02:29 PM

Try:

yum install kernel-source
up2date kernel-source
apt-get install kernel-source

Use whatever you have installed and configured.

Create the link /usr/src/linux, extract and install the driver.

I bet that will fix it.

Fedora Core 3 Tips and Tricks