Results 1 to 6 of 6
after (trying) to compile a 2.6.6 kernel on a Debian 2.4 machine i get the following errors..
Code:
modprobe: Can't open dependencies file /lib/modules/2.6.6-04aug2004/modules.dep
(No such file or directory)
modprobe: ...
- 08-06-2004 #1Just Joined!
- Join Date
- Aug 2004
- Posts
- 4
cant open modules.dep
after (trying) to compile a 2.6.6 kernel on a Debian 2.4 machine i get the following errors..
I tried finding some artikels about it on google but sadly i got nothing usefull.Code:modprobe: Can't open dependencies file /lib/modules/2.6.6-04aug2004/modules.dep (No such file or directory) modprobe: Can't open dependencies file /lib/modules/2.6.6-04aug2004/modules.dep (No such file or directory) pivot_root: No such file or directory /sbin/init: 424: cannot open dev/console: No such file Kernel panic: Attempted to kill init!
I havent got a clue what went wrong or where so if any of you guys know anything that could help me get it running again pls let me know...
- 08-06-2004 #2Just Joined!
- Join Date
- Jul 2004
- Location
- UK
- Posts
- 77
Are you compiling as a regular user or root?
Armage
- 08-06-2004 #3Just Joined!
- Join Date
- Aug 2004
- Posts
- 4
all compiling was done as root
- 08-06-2004 #4Just Joined!
- Join Date
- Jul 2004
- Location
- UK
- Posts
- 77
When compiling the kernel did you set ACPI=y?
If you did try taking this out.
Armage
- 08-09-2004 #5Just Joined!
- Join Date
- Aug 2004
- Posts
- 4
i tried taking it out, but it still cant find modules.dep
however it now starts stating it at an earlier point than before
- 07-15-2006 #6Just Joined!
- Join Date
- Jul 2006
- Posts
- 1
(replying on this 2 y/o discussion, just as I found it among the first results in google (while searching for : "kinit: opening console: No such file or directory"). now it could be used as a reference for anyone with a similiar issue)
this situation could be the result of a missing or wrong /dev/console device-file, which is needed for booting. (maybe unless using an initrd - which holds this device-file)
to recover from this situation, one may boot such a system using a LiveCD, mount the regarded Linux OS filesystem, remove the erratic /dev/console from the mounted FS (if exists), and recreate it - using : mknod -m 600 /dev/console c 5 1 (or copy it (using : cp -a ) from the LiveCD)
That's it.


Reply With Quote
