According to Alfred: While burning my CPU.
>
> Hy to everyone!
>
> Booting SuSE 2.2.9 shows:
> modprobe: Can�t locate module char-major-4
> modprobe: Can�t locate module eth1
>
> /etc/conf.modules shows:
> alias char-major-4 serial
> alias eth1 eepro100
>
> The files serial.o and eepro100 i�ve found in
> /usr/src/linux-2.2.9/drivers/char/serial.o and
> /usr/scr/linux-2.2.9/drivers/net/eepro100.0
>
> This files i did not found in /lib/modules/2.2.9/driver/...
>
> Starting:
> # insmod -f /usr/scr/linux-2.2.9/drivers/char/serial.o
> shows the error:
> serial.o Couldn�t find the kernel version the modul was compiled for.
>
> Any suggestions for me?
Read the Modules-HOWTO located in your /usr/doc/* dir, somewhere, you seem
to have a misconception about how modules work.
'Normaly speaking'
1) modprobe looks for modules in /lib/modules/2.2.9/
2) There is NO driver directory in /lib/modules/2.x.x
3) The error message "Couldn't find the kernel version the modul was
compiled for" is correct, that will always happen when you tell insmod or
modprobe to load a module which is NOT in /lib/modules/2.x.x beacuse
"depmod" does not make dependancies from the "kernel source tree" but from
"/lib/modules".
Unless a module has been compiled as a "standalone module" things will go
wrong, seriel.o is not a standalone module, in fact there arn't many of them
anyway.
man modprobe
insmod
depmod
less /usr/src/linux/README
Will all help you as well.
>
>
>
> - - - - - - - - - - - - - - - - - - -
> Mit freundlichen Gr��en, Alfred Frank
> - - - - - - - - - - - - - - - - - - -
>
--
Regards Richard.
[EMAIL PROTECTED]
