Aurelien Jarno <[EMAIL PROTECTED]> writes:

> Could you please remove the module (rmmod rt2500), insert it with insmod
> and a full path to make sure you load the right one (insmod
> /lib/_kernel_version_/kernel/drivers/net/wireless/rt2500.ko) to see if
> you still have a problem.

Before doing this, I updated my kernel & rt2500 source, and recompiled
(using gcc-4.0 this time -- before is was 3.3):

# make-kpkg clean && make-kpkg --append-to-version -10-wasp-2 modules_image 
kernel_image

# ifdown eth1
# rmmod rt2500
# insmod /lib/modules/2.6.12-10-wasp-2/kernel/drivers/net/wireless/rt2500.ko
# dmesg | tail -5
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
spurious 8259A interrupt: IRQ7.
PCI: Found IRQ 10 for device 0000:02:08.0
PCI: Sharing IRQ 10 with 0000:00:1f.3
rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com
# strings
# /lib/modules/2.6.12-10-wasp-2/kernel/drivers/net/wireless/rt2500.ko | grep 
vermagic
vermagic=2.6.12-10-wasp-2 preempt PENTIUM4 gcc-4.0

Of course, the first time it loaded (during boot) it still warned:

rt2500: no version for "struct_module" found: kernel tainted.

Which I found with:

# dmesg | grep rt2500
rt2500: no version for "struct_module" found: kernel tainted.
rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com
rt2500 1.1.0 CVS 2005/07/10 http://rt2x00.serialmonkey.com

In this case, that also shows the success of the second insmod.

Since it didn't give the taint message the second time the module was
loaded, I also tried manually loading the module before the system
loaded it (I had to boot with init=/bin/sh to do so, something in the
boot process (hotplug?) was very insistent about loading the module,
even in single user mode).  When I did so it gave the kernel taint
message, so evidently it only gives the error the first time the module
is loaded.  But this was using the same exact command as is used above
(i.e., insmod /lib/modules, etc.).

So I'm reasonably certain that the problem is not that I'm loading the
wrong module (i.e., a kernel/module version mismatch).  Unfortunately,
it's hard to do a cut & paste from console after init=/bin/sh, or I'd
give you that.  ;) If you have a way to keep the module from being
loaded during boot I can try that, though.  (I've tried 'alias rt2500
off' in /etc/modules.conf, disabling network, and single user mode.)

Anyway, I hope this helps.  Let me know if there's anything else I can
do on this end.

-- 
Jeremy Hankins <[EMAIL PROTECTED]>
PGP fingerprint: 748F 4D16 538E 75D6 8333  9E10 D212 B5ED 37D0 0A03


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to