frustration! modules!

nixel · 05-07-2004, 10:33 PM

when i thought i would have nothing wrong with anything else...after ssh...after mouse tweeking...NOW...the damn sound module wont load...snd-via82xx..modprobe cant find this module..

Code:

$ locate via82xx
/lib/modules/2.4.22/kernel/sound/pci/snd-via82xx.o.gz
/lib/modules/2.6.5/kernel/sound/pci/snd-via82xx.ko
/usr/src/linux-2.6.5/sound/pci/via82xx.c
# modprobe snd-via82xx
FATAL: Module snd_via82xx not found.
# depmod
# modprobe snd-via82xx
WARNING: Error inserting snd (/lib/modules/2.6.5/kernel/sound/core/snd.ko): Invalid module format
WARNING: Error inserting snd_seq_device (/lib/modules/2.6.5/kernel/sound/core/seq/snd-seq-device.ko): Invalid module format
WARNING: Error inserting snd_rawmidi (/lib/modules/2.6.5/kernel/sound/core/snd-rawmidi.ko): Invalid module format
WARNING: Error inserting snd_mpu401_uart (/lib/modules/2.6.5/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko): Invalid module format
WARNING: Error inserting snd_page_alloc (/lib/modules/2.6.5/kernel/sound/core/snd-page-alloc.ko): Invalid module format
WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.5/kernel/sound/pci/ac97/snd-ac97-codec.ko): Invalid module format
WARNING: Error inserting snd_timer (/lib/modules/2.6.5/kernel/sound/core/snd-timer.ko): Invalid module format
WARNING: Error inserting snd_pcm (/lib/modules/2.6.5/kernel/sound/core/snd-pcm.ko): Invalid module format
FATAL: Error inserting snd_via82xx (/lib/modules/2.6.5/kernel/sound/pci/snd-via82xx.ko): Invalid module format

help..im getting tired of these errors...it seems like i can even USE linux but just spend most of my time fixing it.

edit: before anyone even asks this question ill go ahead and answer it. YES i did compile alsa as modules and i did compile "sound support" into the kernel.

edit again: i checked the 'dmesg' output and it gave me this:

Code:

atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
serio: kseriod exiting
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
snd: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 preempt K7 gc
c-3.2'
snd_seq_device: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 pr
eempt K7 gcc-3.2'
snd_rawmidi: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 preem
pt K7 gcc-3.2'
snd_mpu401_uart: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 p
reempt K7 gcc-3.2'
snd_page_alloc: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 pr
eempt K7 gcc-3.2'
snd_ac97_codec: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 pr
eempt K7 gcc-3.2'
snd_timer: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 preempt
 K7 gcc-3.2'
snd_pcm: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 preempt K
7 gcc-3.2'
snd_via82xx: version magic '2.6.5 SMP preempt K7 gcc-3.2' should be '2.6.5 preem
pt K7 gcc-3.2'

any suggestions?

ilikejam · 05-08-2004, 01:42 AM

Did you do make modules_install during the kernel compile? Looks like you've got modules from an SMP enabled kernel installed with a non-SMP kernel.

Dave

motub · 05-08-2004, 02:59 AM

So, this is happening when you try to boot the 2.6.5 kernel? I see that there are also modules for 2.4.22-- can you still boot that kernel? Do those modules load?

ilikejam is probably right, though-- I've had to do make modules and make modules_install a couple of times after installing a new 2.6 series kernel, even though "make" appears to build and install them. Doing so has always fixed a similar problem for me (just different modules

).

nixel · 05-08-2004, 09:17 AM

in windows right i cant boot any of the kernels, re-installing AGAIN.

ilikejam: after make menuconfig i did a 'make', 'make modules_install', and 'make install'

its weird though, with the help of this forum, i got ssh working, then my mouse started to mess up, i fixed the mouse, now the sound drivers arent loading. how are they related? i have no idea.

before i even go on with ANOTHER linux install, what is SMP?

Y@bon · 05-08-2004, 10:15 AM

The sequence of compilation is :
make mrproper ; make [x]config ; make clean ; make bzImage; make modules ; make modules_install [; make install]
Final make install depend on your configuration...
Prefer to manually copy kernel and System.map image...
And finally lilo

motub · 05-08-2004, 10:26 AM

SMP= Symmetric Multi Proccessing, meaning that you have multiple CPUs.

Shade · 05-08-2004, 10:56 AM

Yeah, it definitely looks like you've somehow got some precompiled kernel modules in your /lib/modules/2.6.5/ space.

Did you use the slackware package for alsa, or compile it yourself?

And now it won't boot?

--Shade

PS- to explain the many problems you're having, I'd say you've got monkeys in your computer.

nixel · 05-09-2004, 07:16 AM

heres an update. i re-installed everything again..and i was going through the kernel looking for anything pertaining to SMP and found the multi-processing thing. for some reason it was checked to compile it in by default. took it out and compiled 2.6.5 and everything is working. its the little things in linux that piss me off =)

motub · 05-09-2004, 07:25 AM

Congratulations!

But what you say is very funny (and is the reason I love Slack so much)-- the kernel is, of course, not "a little thing".

But what's cool about Slack is that once you fixed the one setting that was wrong (one setting! in the entire kernel!!!)--everything then worked perfectly.

Under the majority of other distros, you'd probably still be chasing errors, 'cause they're like onions. Slack is simple. You may have to spend a couple of days chasing down the "one little typo", but once you've found it, you're done.

nixel · 05-09-2004, 08:16 AM

true, motub..i started with redhat and used it for 3 months before switching to slackware. i learned more about linux in 2 days using slackware than with 3 months working in redhat. since im still a newbie. its hard for me to comprehend error messages in linux. but once everything is fixed (with the help of this forum) i feel accomplished and i wonder what to do next.

Linux.tar.gz · 05-11-2004, 07:24 PM

Quote:

Originally posted by nixel
true, motub..i started with redhat and used it for 3 months before switching to slackware. i learned more about linux in 2 days using slackware than with 3 months working in redhat. since im still a newbie. its hard for me to comprehend error messages in linux. but once everything is fixed (with the help of this forum) i feel accomplished and i wonder what to do next.

For my part, i learned more about computers in 6 monthes using slackware than with 10 years working in windowXX.