I did my first Debian installation yesterday and
met the same problem when I did a reboot. So I
did some searches in
<http://www.linuxquestions.org>www.linuxquestions.org
and saw one post suggesting that it might be the
initrd line in grub.conf. then I changed "initrd
(hd0,8)/boot/initrd.img-2.6.8" to "initrd
(hd0,8)/boot/initrd.img-2.6.8 root=/dev/hda9"
and everything worked ever since. I thought it
was root=/dev/hda9 which tells initrd where to
look for some of the files so that if you missed
it, it would never know where to locate /dev/console.
On 7/31/05, Björn Johansson
<<mailto:bjorn.johansson@4a-consulting.com>bjorn.johansson@4a-consulting.com
> wrote:
At 18:37 2005-07-31, you wrote:
>Hi,
>
>On dim, 2005-07-31 at 15:14 +0200, Björn Johansson wrote:
> > Hello!
> >
> > I have installed a Debian 2.6.8 standard
kernel from the Debian ftp server
> > using Dselect. But it won't boot up my system! :-( HELP! :-)
> >
> > This is the output:
> >
> > /sbin/init: 432: cannot open dev/console: No such file
> > Kernel panic: Attempted to kill init!
> >
> > The kernel is precompiled btw.
> > My theory is that I need to install the
console device package, but I can't
> > find this anywhere. :-( Do I need to create
> the console device, maybe? Hmm...
> >
> > I'm not a member of the list, so please use the cc.
>
>Did you specify the right initrd.img to use to your bootloader (lilo or
>grub)?
>
>--
>strawks <<mailto:strawks@yahoo.fr>strawks@yahoo.fr>
>
Well.. I haven't specified anything. Like I said
before, I installed a precompiled
package from my Debian system using Dselect. I have several kernels to boot
from and I really would like to get a 2.6 working, because the graphics don't
work 8-(, and the kernel can't find my MX 1000 laser mouse + the standard
2.4 kernel can't even find my ATi Radeon(9800XT) card. I'm thinking right now
that before I should switch to Suse instead! But
I have been using Debian since
1999, so I don't really want to change to
another distribution unless I really
haveto. This Debian Sarge distribution just
didn't like my hardware and the cause
of that was because the netinstall used a 2.4
kernel instead of 2.6. Not cool! Before,
when I ran Woody I had a working system together with a 2.6 kernel which I had
compiled for myself. It was working nice, but then I decided to reformat the
system with Sarge instead. The old system was in a mess, and I didn't want
to mix the old with the new.
I read something about that there could be missing files in /dev.
I will check this out later. Right now I'm sitting with WindowsXP, again..
I need to switch off the computer and change harddrive since a dualboot
solution makes it too hot inside the case. :-( Oh
well, that's another story. :-)
Interesting to see how many tips I can get in this thread, I'll wait a bit..
Björn
--
Dell Inspiron 600m
Pentium-M 1.6G
512MB, 60G
ATI 9000 Mobility