from Ben Collins in IRC: "the fix was reverting back to amd74xx IDE
driver instead of pata_amd." Got me back up and running; should have a
kernel update by tomorrow...
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Fix Committed
--
2.6.20-15 still won't boot
https://b
And one from fixed (regressed) kernel.
** Attachment added: "dmesg3.txt"
http://librarian.launchpad.net/7331974/dmesg3.txt
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Yet another dmesg from 2.6.20 that won't boot
** Attachment added: "dmesg2.txt"
http://librarian.launchpad.net/7331329/dmesg2.txt
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
Problem persists with new install. I downloaded the daily build for
today, and got it installed, albeit a little strangely. When the live
cd booted, just like the 2.6.20-14 version I tried, couldn't do anything
with any of my partitions, and the installer failed to reformat them
from the wizard.
Also, I should add that I had to edit the boot command line to read
(hd0,2) from (hd1,2) to get it to do anything at all.
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
dmesg attached from failed 2.6.20-15 boot. Accomplished by mounting USB
stick.
** Attachment added: "dmesg.txt"
http://librarian.launchpad.net/7331014/dmesg.txt
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of
Progress? Different error messages now.
** Attachment added: "IMG_2979.JPG"
http://librarian.launchpad.net/7330784/IMG_2979.JPG
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
Same here, that's what I meant when I said "directory does not exist"
earlier.
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
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
My errors are slightly different, but result is same. I was never able
to boot into -14 or -15; -13 works fine. Filed a new bug report
#106418.
--
MASTER: Computer will not boot after 2.6.20-14.23 kernel upgrade
https://bugs.launchpad.net/bugs/106063
You received this bug notification because y
** Description changed:
Binary package hint: linux-source-2.6.20
From my forum post; 2.6.20-15.25 still does not fix:
I've had problems for about a week, and I'm unsure of how to proceed.
Installed Feisty beta, and had a rockin' system until upgrade from
kernel 2.6.20-13 to 2.6.20-
Don't need a pic. It says "directory does not exist." Tried it double
checking all the UUID's in grub and fstab.
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Here they are from the -13 booted system:
[EMAIL PROTECTED]:~$ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 2007-04-14 09:40 1d18a66c-ae41-4c7f-84a2-e3481708cffe
-> ../../hda3
lrwxrwxrwx 1 root root 10 2007-04-14 09:40 73c931e8-fecc-4cc7-81af-54dcb8c4dec6
-> ../../hda5
lrwxrwxrwx 1
And where it ends up. By the way that "Check root=bootarg cat
/proc/cmdline" error at the end is new with these -15 kernels, did not
appear with the -14 ones.
My mobo is an ASUS P5NSLI, with an Nvidia GeForce 7600 GS graphics card
and two IDE drives. Feisty is on a separate partition - I don't m
2nd one, as it finally continues to go...
** Attachment added: "IMG_2977.JPG"
http://librarian.launchpad.net/7330367/IMG_2977.JPG
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug c
3 pics coming at you. This first one is where my system first hangs for
quite a long time...
** Attachment added: "IMG_2975.JPG"
http://librarian.launchpad.net/7330363/IMG_2975.JPG
--
2.6.20-15 still won't boot
https://bugs.launchpad.net/bugs/106418
You received this bug notification because
libata.ignore_hpa=0, entered into grub, gives me an uknown boot option
message. Is that where it should be added? My system pauses at
ata2.00: qc timeout (cmd oxfer)" then gives me "ata2.00:failed to set
xfermode (err_mask=0x4)," then continues to try to boot, eventually
ending up in busybox. I
Public bug reported:
Binary package hint: linux-source-2.6.20
>From my forum post; 2.6.20-15.25 still does not fix:
I've had problems for about a week, and I'm unsure of how to proceed.
Installed Feisty beta, and had a rockin' system until upgrade from
kernel 2.6.20-13 to 2.6.20-14. Starting wit
I've had a similar problem - boot hangs and I get "ata2.00: failed to
set xfermode (err_mask=0x4)." since upgrading to 2.6.20-14; 2.6.20-13
still boots fine. I was hoping this patch would fix me up, but it does
not...
--
pata driver in libata not mounting /home
https://bugs.launchpad.net/bugs/
same here with ASUS P5NSLI motherboard. Searched all over for a
solution; this is the first bug report I've found with exact same
symptoms as me (able to boot 2.6.20-13, but not 2.6.20-14).
--
Ubuntu feisty: Failed to set xfermode with 2.6.20-14
https://bugs.launchpad.net/bugs/103677
You receive
19 matches
Mail list logo
