On Wed, 16 Feb 2000, Michael Symalla wrote:
> Hi Martin,
>
> I did it that way and now he not longer complains about missing
> modules, great! But now my 3com network adapter (which is included in
> the kernel) is not longer initialized, so no eth0 ;-) with 2.0.36
> this was a module and everythi
On Wed, 16 Feb 2000, Ron Rademaker wrote:
> Check your /etc/init.d/modutils, during installation you selected some
> modules to be loaded into your kernel at boot time, when upgrading to a
> new kernel, such a file isn't changed, so it's looking in
> /lib/modules/2.2.14 for modules that are now in
Hi Martin,
I did it that way and now he not longer complains about missing
modules, great! But now my 3com network adapter (which is included in
the kernel) is not longer initialized, so no eth0 ;-) with 2.0.36
this was a module and everything worked fine, but how do start the
network adapter now?
Check your /etc/init.d/modutils, during installation you selected some
modules to be loaded into your kernel at boot time, when upgrading to a
new kernel, such a file isn't changed, so it's looking in
/lib/modules/2.2.14 for modules that are now in your not a module but
right in the kernel.
Easy wa
Re:Hi!
Check the file /etc/modules and remove the entries the bootprocess
complains about...
Martin
On Wed, 16 Feb 2000, Michael Symalla wrote:
> Hi!
>
> I just tried to update my kernel from 2.0.36 to 2.2.14. Compiling,
> mpkg and dpkg worked fine, but when I try to boot the new kernel it
> a
Hi!
I just tried to update my kernel from 2.0.36 to 2.2.14. Compiling,
mpkg and dpkg worked fine, but when I try to boot the new kernel it
always claims that it can't locate some modules. The funny thing is,
that he misses modules (like 3c59x for my network adapter) which I
have definitly NOT comp
6 matches
Mail list logo
