Hi all...
Just performed a new install from the DVD onto a spare machine.
However, after the install finishes, i get the KUBUNTU splash screen for about 3 minutes ( does nothing and progress bar does not move ).
After this, i get a black screen with this message :
/bin/sh: can't access tty; job control turned off
(initramfs)
I have now tried this on 2 different machines with same results.
Any ideas ?
thank you
Quote from: vvulture on September 30, 2007, 07:28:06 AM
Hi all...
Just performed a new install from the DVD onto a spare machine.
However, after the install finishes, i get the KUBUNTU splash screen for about 3 minutes ( does nothing and progress bar does not move ).
After this, i get a black screen with this message :
/bin/sh: can't access tty; job control turned off
(initramfs)
I have now tried this on 2 different machines with same results.
Any ideas ?
thank you
Take a look at this thread on http://ubuntuforums.org/showthread.php?t=292533
On some hardware the Grub menu does not get created correctly and the boot partition cannot be found.
My problem was with the Intel dg965wh motherboard. It (and I assume some other motherboards) insists that the boot partition be flagged as "bootable."
I have 1 IDE and 4 SATA drives. It (and/or grub) "sees" the IDE drive as sde and the boot partition as /dev/sde1.
I started in recovery mode, ran "fdisk /dev/sde," entered "a" (toggle a bootable flag), "1" (partition number), and "w" (write table to disk).
Quote from: linuxmce.org@sedwards.com on September 30, 2007, 04:54:19 PM
My problem was with the Intel dg965wh motherboard. It (and I assume some other motherboards) insists that the boot partition be flagged as "bootable."
I have 1 IDE and 4 SATA drives. It (and/or grub) "sees" the IDE drive as sde and the boot partition as /dev/sde1.
I started in recovery mode, ran "fdisk /dev/sde," entered "a" (toggle a bootable flag), "1" (partition number), and "w" (write table to disk).
ok... I did not realise you were using a i965 board. We've had exactly the same situation here :-)
thanks for the replies guys...
i got it working by using a different HDD. The HDD was the only common piece of hardware i had used on the 2 systems so it made sense see if it caused the problem... as it turned out, i was right.
cheers