** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Trusty)
Status: Incomplete => Invalid
** Changed in: udev (Ubuntu)
Status: Confirmed => Invalid
** Changed in: udev (Ubuntu Trusty)
Status: Confirmed => Invalid
--
You received
** Changed in: udev (Ubuntu Trusty)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
saucy/trusty CD images are unbootable, stuck in
** Changed in: udev (Ubuntu Trusty)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
saucy/trusty CD images are unbootable, stuck in
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as Won't Fix.
** Changed in: udev (Ubuntu Saucy)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu Saucy)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Last I checked the bug still occurred with all drives and cards
unplugged. But I will retest when I can...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
saucy/trusty CD
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
saucy/trusty CD images are unbootable, stuck in BusyBox shell
Status in “linux” package in
So it looks like we have a difference in hard drivers. You have an SSD drive:
INTEL SSDSC2CW12 400i PQ: 0 ANSI: 5
I have a mechanical drive:
SAMSUNG HM251HI, 2AJ10001, max UDMA/133
Do you happen to have a mechanical drive to see if you can reproduce the
issue with it?
Also, can other folks
All the prior releases are available from:
http://releases.ubuntu.com/
However, I don't think the early daily releases are still available.
It's strange that we have the same machine, but I'm unable to reproduce
the bug. I'm going to compare your dmesg/lspci output to mine to see
what hw diffs
It might be handy to compare details with the 5 other people who claim
to be experiencing this bug too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
saucy/trusty CD
rootdelay=90 makes no difference to me.
Image attached
** Attachment added: IMG_0069.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+attachment/3916545/+files/IMG_0069.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is
Does anyone know where to find the old saucy daily images? If I had
access to them, I could (slowly) bisect the problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
** Attachment added: 20131115_130257.jpg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1212977/+attachment/3909619/+files/20131115_130257.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I think I may have been able to reproduce this today with Trusty. The
system dropped to the busybox shell. It looked like there was a timeout
waiting to find the root filesystem by uuid. I took a digital picture
and will attach to the bug.
Daniel, can you also take a digital picture of your
If you are seeing the same message as me, can you try using the
rootdelay boot option?
From the GRUB prompt select e. Once there you can add the line
rootdelay=90 to the end of the line.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Sorry, I can't reboot my server to test things very often. Here are some
results from today:
raring LiveCD legacy: OK
raring LiveCD EFI: SOMETIMES boots, sometimes reboots post-plymouth.
raring installed legacy: OK
saucy LiveCD legacy: FAIL - stuck in BusyBox shell
saucy LiveCD EFI: FAIL - stuck
** Changed in: linux (Ubuntu Saucy)
Status: Confirmed = Incomplete
** Changed in: udev (Ubuntu Saucy)
Status: Confirmed = Incomplete
** Changed in: udev (Ubuntu Trusty)
Status: Confirmed = Incomplete
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Incomplete
For some reason, I cannot install or LiveCD boot Raring in Legacy
mode. I can only get to the GRUB menu by setting the BIOS to use EFI.
Daniel, can you see if you can boot the latest Raring image with the
BIOS set to Legacy mode and selecting the legacy USB option from the F12
boot menu?
** Also
I've got a workaround now at lease (other than upgrading). I installed
saucy on a new disk in a separate machine and then transplanted the disk
into the OptiPlex 990. It runs well. So whatever the problem is, it is
isolated to the installation media. The problem doesn't exist after
installation.
at least :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1212977
Title:
saucy/trusty CD images are unbootable, stuck in BusyBox shell
Status in “linux” package in Ubuntu:
Confirmed
Thanks for the update, Daniel. I'm going to bring my system BIOS back
to A07 and install Raring, to get as close to your original config as
possible. Maybe that will allow me to reproduce the issue.
It still would be a good test to try the latest Trusty image.
--
You received this bug
21 matches
Mail list logo
