My problem wasn't fixed in 2.6.20-12. I did note, however, that the
problem fixed itself after adding the "sleep 10" line (mentioned in
http://ubuntuforums.org/showpost.php?p=2236181&postcount=5) fixes the
problem -- my system boots now.
--
Feisty: unbootable after dist-upgrade
https://launchpad
I can confirm that 2.6.20-12 works perfectly. Thanks!
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Fixed in -12 kernel. Also setting to Confirmed without assigning to
kernel team will get the bug overlooked :)
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) => Ben Collins
Status: Confirmed => Fix Released
--
Feisty: unbootable after dist-upgrade
https://launchpa
And here is my Grub menu.lst
** Attachment added: "mene.lst"
http://librarian.launchpad.net/6852104/menu.lst
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu
I have the same problem on a MacBook Core Duo (not 2).
2.6.20-9 works fine, but upon upgrading, neither 2.6.20-10 nor 2.6.20-11
work.
Once I was able to see some debuging information (not even sure how I
got to it) that suggested that the problem is with mapping the drive by
the UUID (-10 and -11
Ok, I installed yaird and made a new initramfs. 2.6.20-8 boots now.
Now my keyboard doesn't work, can't have everything. ;)
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinf
I have the same problem.
My laptop: Macbook Core Duo
The last line I see is also something with usbhid.
Even Feisty Herd 3 doesn't work.
All 2.6.20 kernels don't work.
2.6.20-8 is the newest kernel I tried.
The first boot lines I get tell me that libgcc.so could not be found. Is that
an error
Setting this back to Confirmed so that it doesn't get overlooked.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Fix Released => Confirmed
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
I tried again on Saturday with the latest feisty packages, but with no
luck. Can someone who has things working please post a tarball of their
/usr/share/initramfs-tools directory? I was tinkering with that last
month and might possibly have messed something up (though I rolled back
what changes
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Needs Info => Fix Released
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
after the latest udev/lvm updates the latest kernel boots without
problems here.
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Any updates on this as far as testing with Herd3 or latest feisty
updates?
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I highly doubt that this is the same problem. It might be best to file
a separate bug for the madwifi issue, because I also noticed that a live
CD built on 2006-01-31 kernel panicked when loading the ath_pci module.
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
u
I just recently upgraded to Feisty and found the only problem to be the
madwifi driver in the restricted-modules package. The error message
that appeared on screen didn't really have anything to do with the
ath_pci driver (I had to scroll up to see that). Maybe this is really
the problem you are
Got the same problem here with root on lvm on raid. It's not yet working
with linux-image-2.6.20-5-generic
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
mine is:
/dev/mapper/benni-root
so it can't be the problem
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I had the same issue and the problem was that menu.lst had
root=/dev/hda2 instead of /dev/sda2. I reported this bug but I cannot
find it anymore. I may have not completed the process.
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bu
Same here using latest feisty on amd64 and lvm. The boot process
terminates at the usb scripts.
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have no lvm nor raid (mdadm) packages installed. I attach my fstab and
these are the contents of my lilo.conf (I execute lilo like this: "lilo
-b /dev/sda"):
boot=/dev/sda3
default=Ubuntu
map=/boot/map
delay=10
image=/vmlinuz initrd=/initrd.img
root=/dev/sda3
label=Ubuntu
read-only
app
I'm having similar problems. I don't have a raid setup, though I turned
one of my partitions into an LVM2 group. The root filesystem is on its
own partition, but /usr is on the LVM partition. I guess if the boot
script was trying to access a binary from /usr/bin or /usr/sbin, that
would explain
Is your root filesystem on raid or lvm?
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The latest kernel version 2.6.20-4 doesn't work either...
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
What kind of additional information can I give you?
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have the same problem with the new packages...
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
@ciplogic: I don't know if you really addressed Javier's problem.
Keep in mind that feisty is currently a development version.
Do you have got an Intel or Motorola cpu?
** Changed in: update-manager (Ubuntu)
Sourcepackagename: update-manager => linux-source-2.6.20
--
Feisty: unbootable after d
With the quiet parameter I have been able to read another error:
/init: /init: 1: cannot open /dev/root: No such device or address
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
Please retest with latest kernel (2.6.20-3) and latest initramfs-tools.
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Needs Info
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
** Changed in: Ubuntu
Sourcepackagename: None => update-manager
Importance: Undecided => High
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm sorry but I don't understand you.
--
Feisty: unbootable after dist-upgrade
https://launchpad.net/bugs/77233
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yes, but I solve that in two ways: I boot using the old kernel + I go to
Grub, edit the boot line of the kernel and remove "splash" word.
Secondly it will ask "an administrative password". I choose the root
pasword (which I setup from the live CD with "sudo su -", secondly
"passwd"). Anyway the def
My computer is a Macbook with an Intel Core Duo processor. I have
changed the resolution of the framebuffer and now I can see more
messages. The problem seems caused by the initramfs image:
...
Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-Q] [-b] [-o
] [parameters...]
modprobe -r
31 matches
Mail list logo
