For me, this was the problem I had. Just installed Ubuntu 8.10 - the Intrepid
Ibex on a AMD64.
There was a big delay on booting from bios to os as well. Turned out I had a
jumper on the extra data drives I had in the system, (Western Digital), on the
master w/slave jumpers. Diagram showed f
Per the last comment, I'm marking this Fix Released for Hardy. However
the 2.6.20 task will be closed since Feisty has reached it's End of Life
- http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . Thanks.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in
...and it works again, with the final Hardy kernel.
Gerv
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notification because you are a member of Ubuntu
Bugs, w
Reopening. The beta kernels seem to alternate between working and not
working. At the moment (2.6.24-16 and 2.6.24-15) they are not working,
so I'm reopening this bug. 2.6.24-14 does work.
Gerv
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Fix Committed => New
--
Boot failure: hard
"'linux-source-2.6.24' is a binary package. This bug has been assigned
to its source package 'linux' instead."
Huh? How can linux-source be a binary package? :-| Oh well, hope it's in
the right place now.
Gerv
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bug
Ah, maybe that's why no-one was looking at my bug. Switching package to
linux-source-2.6.24.
Gerv
** Changed in: linux (Ubuntu)
Sourcepackagename: linux-source-2.6.20 => linux
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug not
There doesn't seem to be a "works for me" status, so I'll go with "fix
committed".
Gerv
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: New => Fix Committed
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notificatio
Not really, I just read your blog.
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I've just updated to the latest packages, and 2.6.24-14 boots fine for
me.
Are you still interested in the dmesg output from the boot of 2.6.24-12?
Gerv
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notification because you a
> or grep it for particular strings
anything to do with "sd", "ata" or "scsi" might help.
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Let me know if there's anything else you need. I could probably manually
copy out the last few lines of dmesg output from the bad boot, or grep
it for particular strings, if that would help.
Gerv
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You re
** Attachment added: "lspci -vvv from booting last good kernel"
http://launchpadlibrarian.net/13110400/lspci-vvv.txt
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notification because you are a member of Ubuntu
Bugs, which
You didn't say whether from the broken boot or the good boot. lspci
isn't available on the broken boot, and I have no way of getting the
dmesg output out of the computer because I can't access my disks or
mount a USB drive. So here are the files from a good boot.
Gerv
** Attachment added: "dmesg
> Please let me know what additional information I can provide to help
debug this problem.
I think the output from the following commands might help:
dmesg
lspci -vvv
--
Boot failure: hard disk does not exist (Hardy beta)
https://bugs.launchpad.net/bugs/208222
You received this bug notification
I know you guys are busy and it's just been a weekend, but I
would have thought that "your soon-to-be-released operating system makes
my machine unbootable" bugs might attract a certain amount of interest
:-) Or at least being allocated an Importance...
Gerv
--
Boot failure: hard disk does not
15 matches
Mail list logo
