I get the first prompt because of "break=top", do a "modprobe piix" which causes a short barrage of IDE-related messages that look correct to me, then an "exit". At that point there are several more pages of messages, and then a new prompt. (Actually some messages appear after the prompt--I'm assuming that those were cached by syslog/whatever.)
The last non-log message is something like "Begin mount root file system". The log messages seem consistent with modprobe'ing to make a root device available. In this case, though, I don't see why it'd be doing that, since the root filesystem is on the cdrom and obviously already available. The final messages are from the IDE code, and a USB message about my mouse. None of this looks even remotely like an error message to me. The only thing that sticks out in my mind is that this system already has Linux on it, and has two disks with RAID partitions on them. I suppose maybe the boot code could be tripping over that, though I don't see why it'd care what was on the disks at all at boot time. Since there is no error message at all, this leaves me feeling that maybe there is a logic error in the Ubuntu boot scripts (triggered by something about my system that is a little unusual). -- Feisty boot fail "can't access tty" IDE SATA problem https://bugs.launchpad.net/bugs/106864 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
