[Gutsy Tribe 3 Kubuntu 7.10 LiveCD 64b] need all_generic_ide kernel option for system to boot

[errenay]

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/init-boyyom
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://ubuntuforums.org/showthread.php?t=415009&highlight=can%27t+access+tty&page=26

[Paul Dufresne (paulduf)]

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.

[errenay (errenay)]

Thank you for help.
First thing: there was no such file like casper.log in /var/log (there is no even such directory like /var/log). But there was file casper.log in main directory. The output:

Begin: Running /scripts/casper/premount ...
Done.
Done.
mount: Mounting /dev/sda1 on /cdrom failed: No such device
mount: Mounting /dev/sda2 on /cdrom failed: No such device
mount: Mounting /dev/sda3 on /cdrom failed: No such device
stdin: error 0
...
The same stuff a few times
...
Unable to find a medium containing a live system

One more thing: sda is my hard drive (SATA). I have also checked booting but with additional kernel option
all_generic_ide
In such case everything works and system boots to LiveCD desktop. Hope it helps.

[Paul Dufresne (paulduf)]

And if you boot without parameters...
and that at busybox prompt you type:
dmesg

Is there any error messages in there? (use Shift-PageUp if needed to go to previous pages).

[errenay (errenay)]

Sorry,
dmesg: not found.
Strange, because I could see that there are some kernel outputs before busybox.

[Paul Dufresne (paulduf)]

Thanks, for these information.

Do you keep resolution to VGA when booting?

If you are able to boot with need all_generic_ide kernel option, and then access Internet from there
(some like me have to open a console and use 'sudo pppeoconf' before being able to use Internet), then:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[errenay (errenay)]

Yes, VGA is used (no changes there). Resolution (1280x800) is properly recognized.

[Paul Dufresne (paulduf)]

Thanks for all these information.
Moving bug from Casper to linux-source-2.6.22 (kernel).
That is sad that we don't have a clear error message before busybox command prompt show up.
I have personally observed that the system seems FOR ME, to write the 'uncompressing linux kernel' on text mode while graphical mode is set, so that some unreadable lines show up on the top (I recognize the dots and vmlinuz word because I have seen that on other/older distributions even if almost completely unreadable). So I believe first kernel messages are lost while in graphical mode, just before it switch to text mode.

Confirming bug, letting a kernel developer to take a look and decide which move need to be made next.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, this bug is a duplicate of bug 127163 and is being marked as such. Feel free to submit any future bugs you may find.

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!