On Sun, Jan 30, 2005 at 06:38:57PM +0200, AKL. Mantas Kriauciunas wrote: > Hi, > > I can't boot 2.6.8 and 2.6.10 kernels on my system while 2.6.7 was > installed on same system and starts without problems few months ago. > > I got the same error like others - cannot open dev/console, preceded > by a message from pivot_root which does not found the root partition. > > I use grub and xfs file system on SATA drive (hde) on system with > Athlon (k7) CPU. > > Tried several initrd versions (0.1.77, 0.1.76, 0.1.73, 0.1.67), but > without success :( AFAIK when I installed 2.6.7 kernel, then > initrd-tools version 0.1.67 were installed on my system and initrd was > generated corectly, this kernel starts without problems. > > It seems bugs 290474 and 271038 are related - in both cases kernel > doesn't start with message "cannot open dev/console: No such file" > > I can send initrd, generated when I install kernel-image 2.6.8 and > 2.6.10, which doesn't start.
If you uncomress the image you should be able to mount it using a loopback device. And then inspect what is inside. Alternatelvely, just regenerate the image using mkinitrd. If you add the -k argument then it will leave what went into the image in a directory in /tmp. In any case, the most likely cause of this is that the drivers required to mount your root partition were not persent. This could be a FS driver, but more likely an IDE or SCSI driver of some sort. Can you give a little more information on what your root partition lives on. Also, what modules are loaded up on the working 2.6.7 system? By comparing this to what ends up on the CD, you can probably shed some light on what has gone astray. -- Horms -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
