View previous topic :: View next topic |
Author |
Message |
spitzwegerich l33t
Joined: 04 Mar 2003 Posts: 697 Location: Lower Bavaria, Central Europe
|
Posted: Mon Mar 24, 2003 7:08 pm Post subject: insmod net-pf-1 failed |
|
|
hello!
I followed the installation instructions and wanted to reboot into my new system. But after each boot-message of the form
************************* [ok]
i got lots of these messages:
Code: |
insmod: /lib/modules/2.4.20-gentoo-r1/kernel/net/unix/unix.o: insmod net-pf-1 failed
|
Finally i got to the login-prompt, and after entering the username "root" as well after entering the password i again got lots of these messages.
I decided to do a depmod and it told me that there are unresolved symbols in unix.o
After that i wanted to log in in a second console (alt+f2), and after entering the username i again got this message. but this time it never stopped. there was also a new kind of message. i got:
4 times
Code: |
insmod: /lib/modules/2.4.20-gentoo-r1/kernel/net/unix/unix.o: insmod net-pf-1 failed
|
followed by 2 times
Code: |
Note: /etc/modules.conf is more recent than /lib/modules/2.4.20-gentoo-r1/modules.dep
|
and this pattern came again and again and it never stopped. i succeded in safely rebooting the system by ctrl+alt+del, and now already the boot process hangs with this 4+2 error messages pattern.
When i compiled the kernel, I tried to set as many kernel options as possible to modules. Maybe i did that to some option which should have been set to "enabled". I can post my .config file if you think that would be interesting.
I don't have an idea how to fix this. Please help me.
Thanks,
~michael |
|
Back to top |
|
|
gamera2_00 n00b
Joined: 05 Mar 2003 Posts: 47
|
Posted: Mon Mar 24, 2003 10:02 pm Post subject: |
|
|
Some things MUST be inside of the kernel for it to boot properly. Read the help part in menuconfig for each component if you're not ABSOLUTELY SURE if it should or should not be inside of the kernel.
Also, building modlues for EVERYTHING isn't always good, sometimes there's alternate versions of drivers that make conflicts. You shouldn't need to change too many of the default general settings. Also, avoid making modules for things you know you don't (and will never) have or need. (it wastes alot of time).
Try backing up your kernel config and make distclean if you've upgraded binutils or gcc since the last time you've compiled your kernel. (sometimes this helps too, but it wipes your kernel config settings, so be careful) _________________ "Please be aware, that while this message is being broadcast today, you may recive it tommorow, possibly yesterday." |
|
Back to top |
|
|
spitzwegerich l33t
Joined: 04 Mar 2003 Posts: 697 Location: Lower Bavaria, Central Europe
|
Posted: Tue Mar 25, 2003 7:21 pm Post subject: |
|
|
many thanks for your reply!
after make distclean and playing around with the kernel options, i found out that CONFIG_UNIX must be set to "enabled" instead of "module". |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|