Hi all.
Perhaps not a debian question, but I have a sneaky feeling it's to do with
what's a module, what's not, and where I set up the aliases for the modules -
so I'm not *entirely* OT for the list ... :-)
After rolling my own kernel (vanilla 2.2.20), an "ifup eth0" locks the box
solid - no m
I always set version info on all modules, which allows you to use old or
non-kernel modules with a new kernel. As a bit of housekeeping I also
rename the Debian modules dir before I "make modules modules_install".
Don't forget to clean out /etc/modules to stop the system trying to load
non-existant
"Aeschlimann Marc" <[EMAIL PROTECTED]> writes:
> I compiled my new kernel (2.2.17) with kernel-package. After that I
> tried the command depmod, the result was : Unresolved symbols in
> /lib/modules/2.2.17/xxx/xxx.o What is the problem ?
Did you have modules lying around in /lib/modules/2.2.1
"Aeschlimann Marc" <[EMAIL PROTECTED]> writes:
> I compiled my new kernel (2.2.17) with kernel-package. After that I
> tried the command depmod, the result was : Unresolved symbols in
> /lib/modules/2.2.17/xxx/xxx.o What is the problem ?
Did you have modules lying around in /lib/modules/2.2.17 be
Hello,
I come from Switzerland so my engish isn't fluent.
I compiled my new kernel (2.2.17) with kernel-package. After that I tried the
command depmod, the result was :
Unresolved symbols in /lib/modules/2.2.17/xxx/xxx.o
What is the problem ?
Best regards.
Marc Aeschlimann
Student at EICN
Switzer
5 matches
Mail list logo