This bug was rediscovered recently as bug #959700 and should now be
fixed in 12.04.
** Changed in: grub (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Sorry, I mean bug #957262, not 959700.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/222421
Title:
initrd not configured in menu
I created new bug #322949. I think it is related to this one from some
point of view. initrd.img is build during kernel removal.
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/222421
You received this bug notification because you are a
Ubuntu is a Good Thing, and I would like to recommend it to my friends,
giving them CDs. However, I cannot do this when I know that the
installation CD or a routine kernel upgrade could leave their computer
in an unbootable state. Especially when it is now clear where the error
lies. Please can
With all due respect, Steve, I fear that you are never going to solve
this/these bug(s) unless you are more critical of your own reasoning.
Whilst I now use computers primarily for email and word processing,
you can see from my web page that I was a computer science lecturer and
have taught reasone
Since this problem
* is known to happen sometimes (whether the circumstances are clear or not),
* happens on valid systems (for example using do_bootloader=no is not an error),
* may reappear in the future (any package can call update-grub after kernel
unpacking and the kernel package may not call
On Fri, Jan 09, 2009 at 08:04:57PM -, Paul Taylor wrote:
> First, is this a legitimate possibility?
Yes, it is.
> Even if it is, could it be eliminated by generating a dummy initramfs, even
> where it is not needed
No, because the entire problem is that update-grub is being called (for a
rea
Sorry, "thinking aloud".
And I do hate text boxes on web forms, and their assumption that
"carriage return" means "new paragraph". A "preview" button would
help, to give one the opportunity to correct the line breaking.
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.0
Thanks to Steve Langasek for his thinking allowed about this important
bug.
In his faulty sequence, and on the occasion that the bug hit me, the crucial
failure is that
** there is kernel entry in menu.lst with no accompanying initrd **
(in particular, the default entry had this).
Looking at th
Yes, the sequence here that results in this kind of breakage must be:
- kernel is unpacked
- update-grub is called
- initramfs is generated (in kernel package postinst)
- update-grub is *not* called
- kernel package postinst ends successfully, leaving the kernel configured
but menu.lst broken
T
On Wed, 07 Jan 2009 18:56:34 -
Michael wrote:
> Did you set "do_bootloader = no" in /etc/kernel-img.conf ?
I didn't change anything in that file.
> That was the reason my initrd.img was not generated after upgrade (see
> bug #222799).
initrd was generated. It just wasn't in grub's menu.lst
Did you set "do_bootloader = no" in /etc/kernel-img.conf ?
That was the reason my initrd.img was not generated after upgrade (see
bug #222799).
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/222421
You received this bug notification be
I don't have that system anymore :(
Maybe the problem is that initramfs-tools are installed after the
kernel. Maybe intrepid's kernel won't work with hardy's initramfs-tools.
In that situation, installation of new kernel wouldn't generate initrd,
but it would update grub menu.lst. And then, after
Ante, do you have the full dpkg log from this upgrade? From what I see
in /usr/sbin/update-initramfs, only initramfs updates (-u) are deferred
as a trigger; initramfs creation (-c) is still processed immediately.
So the initramfs should still have been created at the right point in
time, but perha
Duplicate of bug #222799 ?
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/222421
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.
I can confirm this happend on 8.04->8.10Beta. I did upgrade with update-
manager. Initrd was generated, but grub didn't pick it up. It looks like
grub is configured before initrd was created:
2008-10-03 02:04:09 configure grub 0.97-29ubuntu36 0.97-29ubuntu36
...
2008-10-03 02:11:07 status triggers
I can confirm this bug.. in fact, I'm two-for-two on the Ubuntu systems
I have. Maybe relevant: I use software RAID-1 for the root filesystems
of both systems. The initrd.img was properly created; the menu.lst was
just missing the "initrd" line. BUT: the menu.lst entries for the old
2.6.22 kerne
I've got same problem
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/222421
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.ubunt
>As you're the only user who has reported this error...
I think Paul is not the only one. It should be thousends. But probably
most of the is a newbie like me. What should they do? I needed hours
to find this page. And still I don't know what to do. I wanted simply
to try the new 8.04 - define
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => Medium
Status: New => Confirmed
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/222421
You received this bug notification because you are a member of Ubuntu
Bugs, which
On Thu, Jun 26, 2008 at 09:44:07PM -, Paul Taylor wrote:
> This dialogue seems to be split between two pages - it is not possible
> to merge them?
Not without explicitly copying from one to the other. Sorry, there's no
perfect way to merge bug reports. (The 'perfect' way is to make sure
dupl
This dialogue seems to be split between two pages - it is not possible
to merge them?
> if the initrd.img has not been created, then that's certainly a bug in its
> own right,
> though not a bug in grub, and we should still try to get that fixed.
I would point out that in my case the initrd.img
to Steve Langasek:
How do you know that (occurrence of) this bug is "rare"? It renders
the computer unusable, especially if it occurs during use of the
installation CD. If this happens to someone who is "just trying out"
Linux for the first time, they'll (re)install Windows Vista and never
co
I find it shocking that nothing has been done about the fact that the
installation CD can leave someone's computer in an unusable state, from
which it is only possible to recover using other tools and considerable
Linux experience.
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.
Xubuntu 8.04 (24 April 2008) CD image downloaded
My only differences from "standard" set-up:
(1) Old hardware
(2) DIY disk partitioning.
On completion of the intallation, it failed to boot, with messages like this:
VFS: cannot open root deveice "UUID=" or unknown block (0,0)
Please append a corre
Description of my hardware:
Mainboard Gigabyte GA-7IX ATX SOYO 5EMA+ 100Mz (Skt7)
ProcessorAMD K6-2-550
Memory 128Mb DIMM PC100
NB this is less RAM than the Xubuntu 8.04 documentation says that I
need.
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/1
Hi Steve,
you are right, initrd-2.6.24-16-generic was ready in the system, ONLY
record for initrd in menu.lst was missing. I added initrd line to
menu.lst and system started as expected.
--
initrd not configured in menu.lst after upgrade from Ubuntu 7.10 to 8.04
https://bugs.launchpad.net/bugs/2
Hi psl,
Thank you for taking the time to report this bug and help to improve
Ubuntu.
Can you tell me whether /boot/initrd-2.6.24-16-generic exists on your
system? The only case I see where update-grub would fail to add the
initrd line to menu.lst is if the initrd itself doesn't exist for some
re
28 matches
Mail list logo
