Fix Releasing this as it sounds as if it has been fixed, barring any
update from the original reporter.
Thanks!
~Jfo
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
boots into busybox with 2.6.28-11-generic kernel.
https://bugs.launchpad.net/bugs/364029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Generally, I would think of update-initramfs not touching _all_ kernels rather
a feature than a problem. For kernels that have not been touched (as the
previous kernel demonstrates) this preserves integrity.
I am not sure I completely understand the upgrade progress here. There seems to
be one s
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
boots into busybox with 2.6.28-11-generic kernel.
https://bugs.launchpad.net/bugs/364029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Yes, it is slightly odd that the kernel is being configured while udev
is only unpacked here, but that isn't the real issue. 'update-initramfs
-u' may be called at any time, and it needs to work. (There is no
support in the packaging system for anything like your timestamp idea,
and I don't think i
** Attachment added: "dpkg.log"
http://launchpadlibrarian.net/25781446/dpkg.log
--
boots into busybox with 2.6.28-11-generic kernel.
https://bugs.launchpad.net/bugs/364029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "term.log"
http://launchpadlibrarian.net/25781519/term.log
--
boots into busybox with 2.6.28-11-generic kernel.
https://bugs.launchpad.net/bugs/364029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/25781116/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/25781117/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/25781118/Dependencies.txt
** A
I believe this is the problem:
Setting up linux-image-2.6.28-11-generic (2.6.28-11.42) ...
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.28-11-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.28-11.40 was configured last, according to dpkg
Two problems, here:
- when update-initramfs is triggered, it only updates what it perceives to be
the "current" initramfs, leaving other initramfses demonstrably broken.
- the "current" initramfs is determined as "the version pointed to by
/vmlinuz", and that's going to be the last kernel *insta
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: New => Triaged
--
boots into busybox with 2.6.28-11-generic kernel.
https://bugs.launchpad.net/bugs/364029
You received this bug notification because you are a member of Ubuntu
Bugs, which
this problem is over for me now.
Doesn't exist anymore with karmic beta (31-11-generic) & the latest updates.
--
boots into busybox with 2.6.28-11-generic kernel.
https://bugs.launchpad.net/bugs/364029
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Can confirm the same thing with Karmic 2.6.31-5-generic kernel.
When booting, i have a useless message: can't find system.map which exist in
/boot (googling around, adding rootdelay=40 or + turn that message off), and
then i failed in busybox needing to exit to continue the boot process.
--
boo
13 matches
Mail list logo
