[NTLUG:Discuss] No kernel, no Cisco, no webcam

[Jack Snodgrass]

don't know all of the answers. ;)

as far as
kernel-module version  mismatch
you can sometimes get by with
insmod -f modulename
to '-f' force the modules to load ( and ignore the
kernel version ) It depends on how different the
2.4.19-4GB is to the 2.4.19 one.


if it was me... I'd try this

get an unmodified copy of the 2.4.19 kernel source

unpack that and try and compile that. I'd just
use the 2.4.19 name and let the modules install in
the /lib/modules/2.4.19 directory ( assuming that
susie uses the -4GB extension )

keep your susie kernel stuff and copy your new
bzImage kernel to the /boot partition. update
your lilo or grub or whatever so that you can
boot from either your new kernel  or your susie
kernel.

Once that is done, then try and get either your
web cam or vpn thing working with the generic 2.4.19
kernel.

Once you get that one working, move onto the next
one.

Everything starts with your 2.4.19 generic kernel.

Susie and RedHat put in their 'fixes' but I really
don't think that you need to go with those. The
generic/stock kernels usually work just fine.

jack



>
> If three is charmed, then everything should be fine from
> now on.
>
> My webcam driver says he needs 2.4.19, and the vpn installation
> messages complained, said he needs the same thing. When my
> 2.4.19 kernel compile didn't go, I tried installing vpn against
> SuSE's stock 8.1 kernel (linux-2.4.19.SuSE):
>
> <vpn startup attempt>
> Everything seemed to go well with the installation, but when I ran
> /etc/init.d/vpnclient_init start
> I got this error dump:
>
> Starting /usr/local/bin/vpnclient:
> /lib/modules/2.4.19-4GB/CiscoVPN/cisco_ipsec: kernel-module version
> mismatch
>         /lib/modules/2.4.19-4GB/CiscoVPN/cisco_ipsec was compiled for
> kernel version 2.4.19
>         while this kernel is version 2.4.19-4GB.
> Failed (insmod)
> </vpn startup attempt>
>
> When I tried to compile the 2.4.19 kernel, on the 'make dep' step
> (I learned how to spell it this time :) I got tons of "undefined
> reference to `rwsem_wake'" messages; following is the end of the run:
>
> ipc/ipc.o(.text+0x444e): undefined reference to
> `rwsem_down_write_failed'
> ipc/ipc.o(.text+0x4462): undefined reference to `rwsem_wake'
> ipc/ipc.o(.text+0x4482): undefined reference to
> `rwsem_down_write_failed'
> ipc/ipc.o(.text+0x4496): undefined reference to `rwsem_wake'
> drivers/char/char.o: In function `.text.lock.mem':
> drivers/char/char.o(.text+0x892): undefined reference to
> `rwsem_down_read_failed'
> drivers/char/char.o(.text+0x8a3): undefined reference to `rwsem_wake'
> drivers/char/char.o(.text+0x8b3): undefined reference to `rwsem_wake'
> make: *** [vmlinux] Error 1
>
> I tried to just forge ahead and make the modules, etc, but he didn't
> create a bzImage.
>
> Should I quit my day job?
>
> /dennis
>
> ---------------------------------------------------------------------------
> Office phone: 817-762-8304
>
> ---------------------------------------------------------------------------
> Everything should be made as simple as possible,
> but not simpler.
>
>
>
>
>
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
>
>