[Gutsy Tribe 3 Kubuntu 7.10 LiveCD 64b] need all_generic_ide kernel option for system to boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
System: Acer Aspire 5920G (Centrino 2 Duo 7300, 2 GB RAM, chipset Intel 965G, GeForce 8600 M GT with 256 MB, 160 GB SATA), system on HDD: Vista Premium 32 bit, trying to install: Kubuntu 7.10 (Gutsy, Tribe 3) LiveCD 64 bit.
Problem: LiveCD couldn't even start desktop system.
Without kernel options
quiet splash --
and in safe graphics mode I could see the messages. First
BusyBox...
/bin/sh: can't access tty; job control turned off
was without any previous warning. I have used code
modprobe ata_piix
exit
It has helped a little. However, there was another error:
cp unable to open '/root/var/log' no such file or directory
Begin: Running /scripts/
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init
And that's all... I have tried
modprobe piix
modprobe ide_generic
but it doesn't help. I'm too green to know what I should do next. But I hope it helps somebody to understand this problem. Thank you in advance for your help. I have the same problem with Kubuntu 7.04 LiveCD, please see:
http://
description: | updated |
description: | updated |
Hi! Thank you for taking time to report this bug and help us make Ubuntu become better.
It took me a while to realize that you were able to type commands after the message "can't access tty, job control turned off".
It is important to understand that this message come for many many different errors.
I have actually open a new bug about this message: bug #129612.
Rather than typing 'modprobe ata_piix; exit' I would suggest you type:
cat /var/log/casper.log and looks for error message.
(Actually, the real error message have probably be shown on screen, just a bit before the "can't access tty, job control turned off")
This is the real problem that need to be fixed and caused busybox (just a shell to type commands) to be called because the
system was not able to continue loading normally.