I think this should be marked as won't fix, but since I can't I'll mark
it as invalid for now.
** Changed in: lilo (Ubuntu)
Status: Incomplete => Invalid
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because you are a memb
I am on Ubuntu 10.04 and everything is fine. I am using grub2 now.
Thanks
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Please could you see if this is still a problem in a newer version of
Ubuntu?
** Changed in: lilo (Ubuntu)
Status: Confirmed => Incomplete
** Tags added: patch
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because you are
The user Juan Sebastian Cobaleda Cano is a troll, or something. We, in
the Ubuntu-Co Team are checking all his changes in Launchpad. Sorry for
the problems.
** Changed in: lilo (Ubuntu)
Assignee: Juan Sebastian Cobaleda Cano (sebastiancobaleda) => (unassigned)
Status: Fix Released => C
you have to download the kernel of www.kernel.org
and you have to get the new stable version
** Changed in: lilo (Ubuntu)
Assignee: Kyle McMartin (kyle) => cobaleda (sebastiancobaleda)
Status: Confirmed => Fix Released
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.
Please test with the following patch applied.
** Attachment added: "lilo debdiff to fix 0-sized initrds"
http://librarian.launchpad.net/7243175/lilo_22.6.1-9ubuntu3.debdiff
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because
** Changed in: lilo (Ubuntu)
Status: Fix Committed => Confirmed
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubunt
I am able to boot only with instruction to lilo on boot screen:
root=/dev/hda1
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing li
Not OK.
After reboot, my system doesn't work.
If I boot my new kernel (2.6.20) I end in busybox (initramfs) prompt.
I see this messages:
mount: Mounting /root/dev on /dev/.static/dev failed:No such file or directory
usb 1-1: configuration #1 chosen from 1 choice
Done.
mount: Mounting /sys on /root
OK. I commented initrd with zero size initrd.img
# initrd=/initrd.img.old
in lilo.conf and everything upgraded. I will have to check if I can boot now.
--
lilo won't add the new kernel 2.6.20
https://bugs.launchpad.net/bugs/88219
You received this bug notification because you are a member o
I just upgraded from 6.10 to 7.04 beta through internet. I had some error's
with this packages: initramfs-tools, console-setup, ubuntu-minimal, usplash,
kubuntu-artwork-usplash, kubuntu-desktop, linux-image-2.6.20-14-generic,
linux-image-generic, linux-restricted-modules-2.6.20-14-generic,
li
Bringing milestone forward.
** Changed in: lilo (Ubuntu)
Target: 7.04-beta => ubuntu-7.04
--
lilo won't add the new kernel 2.6.20
https://launchpad.net/bugs/88219
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sorry, patch doesn't work, warning doesn't trigger, same error. The
initramfs's which are zero size are for 2.6.17 - I assume they're like
that because of the udev compatability madness
--
lilo won't add the new kernel 2.6.20
https://launchpad.net/bugs/88219
--
ubuntu-bugs mailing list
ubuntu-
The real question here is why are these initramfs not being properly
generated in the first place...
** Changed in: lilo (Ubuntu)
Importance: Undecided => High
Assignee: (unassigned) => Kyle McMartin
Status: Confirmed => Fix Committed
--
lilo won't add the new kernel 2.6.20
https:
Someone want to give this a test? I don't feel like blowing away my
bootsector...
** Attachment added: "debdiff for lilo to fix 0-byte initrds."
http://librarian.launchpad.net/6775728/lilo.debdiff
--
lilo won't add the new kernel 2.6.20
https://launchpad.net/bugs/88219
--
ubuntu-bugs mailin
Milestoning for beta.
** Changed in: lilo (Ubuntu)
Target: None => 7.04-beta
--
lilo won't add the new kernel 2.6.20
https://launchpad.net/bugs/88219
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I ran into the same problem on a (Intel) Macbook Pro. The problem is
because something is leaving 0 byte initrd.img files around in /boot. A
trivial work around is to rm or move them out of the way. However this
effectively breaks upgrades from Edgy to Feisty on machines that use
lilo. Either u
** Changed in: Ubuntu
Sourcepackagename: None => lilo
--
lilo won't add the new kernel 2.6.20
https://launchpad.net/bugs/88219
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
18 matches
Mail list logo