*** This bug is a duplicate of bug 154199 ***
https://bugs.launchpad.net/bugs/154199
** This bug has been marked a duplicate of bug 154199
gforge install/remove failure loop w/ broken dpkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Actually, it's resolved for users who have already switched to 8.10.
Anyone running a previous version may still be affected.
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
thanks for the follow-up, Michael. Since this does appear to be a
problem with interaction between memtest86+ and a non-default kernel-
img.conf, I'm reassigning to memtest86+ and marking as resolved.
I'm rather concerned by the reason that it's resolved, though, since
memtest86+ still provides i
After further investigation in the memtest86+ package, I discovered the
bug affecting me has already been fixed.
The update-grub command run during my upgrade process was done by the
old package after it was removed (by the postrm file). The new
memtest86+ package doesn't run update-grub any more.
Also, bug #222421 looks similar to this one.
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
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.ubuntu.com
https://lis
I've upgraded to 8.10 today and it's asking me to reboot the system.
Again, there's no initrd line for the new kernels in /boot/grub/menu.lst
Here's the first auto generated kernel entry:
title Ubuntu 8.10, kernel 2.6.27-7-generic
root(hd0,2)
kernel /boot/vmlinuz-2.6
How can I find this information now ?
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
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.ubuntu.com
https://lists.ubun
update-grub handles the case where an initrd doesn't exist by providing
a kernel boot stanza without an initrd line. There are users who have
kernels that don't use initrds, and update-grub doesn't have enough
information to distinguish this use case from the case where a kernel
package has failed
Thanks, I reassign to grub if that has failed to write a correct
menu.lst
** Changed in: grub (Ubuntu)
Sourcepackagename: update-manager => grub
Status: Incomplete => New
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because
The upgrade *did* work. I remember having troubles with gforge, but I
fixed them (I've probably removed the package). I don't think it's
related to the current issue.
The upgrade process worked, but the upgraded system didn't boot because
of the missing Initrd line.
--
Hardy kernel panic after u
Here is what is causing the dpkg error during the upgrade:
Paramétrage de gforge-common (4.6.99+svn6347-1) ...^M
Calculating defaults^M
Reading defaults from /etc/gforge/gforge.conf^M
[: 104: ==: unexpected operator^M
Creating /etc/gforge/gforge.conf^M
[: 107: ==: unexpected operator^M
[: 107: ==
The kernel upgrade seems to have worked, so if the system does not boot
anymore, then this is clearly a kernel bug too.
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Attachment added: "term.log"
http://launchpadlibrarian.net/16364548/term.log
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Attachment added: "main_pre_req.log"
http://launchpadlibrarian.net/16364541/main_pre_req.log
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
** Attachment added: "main.log"
http://launchpadlibrarian.net/16364533/main.log
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
** Attachment added: "apt-term.log"
http://launchpadlibrarian.net/16364517/apt-term.log
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Attachment added: "apt-autoinst-fixup.log"
http://launchpadlibrarian.net/16364507/apt-autoinst-fixup.log
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "apt.log"
http://launchpadlibrarian.net/16364503/apt.log
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
Please attach the files in /var/log/dist-upgrade to this bugreport.
Thanks Michael
** Changed in: update-manager (Ubuntu)
Status: New => Incomplete
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ub
My bad. The 2.6.24.3 kernel in my case was apparently not a stock
Ubuntu kernel, but one I probably compiled myself. During a recent
upgrade, some process or other probably ran update-grub and several
unwanted stanzas got inserted into menu.lst.
--
Hardy kernel panic after upgrade
https://bugs.
I should also note here that I'm tracking the "universe / multiverse"
packages in my sources.list. Perhaps this apparently incomplete kernel
install comes from that repository, in which case it may be beyond the
scope of the Ubuntu bug trackers.
--
Hardy kernel panic after upgrade
https://bugs.l
This bug is still outstanding as of July 22, and has hit me as well.
Please see my report at
http://ubuntuforums.org/showthread.php?p=5440237#post5440237
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubunt
Reopening the bug
** Changed in: update-manager (Ubuntu)
Sourcepackagename: linux => update-manager
Status: Fix Released => New
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
It would be nice to let it get fixed. The user should not be required to
know about "update-grub" at all. Usability is an area where MacOS and
Windows still are superior, and according to bug #1 about Windows market
share we should do everything to make using Ubuntu a no-brainer. The
user should be
Yes. There's an easy fix, but the bug is still there.
And it is not the first time I've to run update-grub to boot my upgraded
ubuntu.
Should we reopen the bug and its package to "upgrade system" or something ?
We can't reproduce it...
--
Hardy kernel panic after upgrade
https://bugs.launchpad.
I agree that this is silly, but I feel like dist-upgrade doing the wrong
thing here is still not okay.
(I had this problem too. SiS chipset, PATA disk.)
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubunt
** Changed in: linux
Status: Confirmed => Invalid
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
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.ubuntu.com
How could I be so blind and/or stupid? I owe you beer or two, Michael
:-). Thank you.
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
You received this bug notification because you are a member of Ubuntu
I had the same problem : sata disk on nforce2, gutsy->hardy then unable
to mount root at boot.
The problem was in menu.lst: the initrd line was missing for the new kernel.
Previous kernel (from gutsy) had a valid initrd line and was working fine, but
hardy kernel didn't have any initrd line.
I s
** Changed in: linux
Status: Unknown => Confirmed
--
Hardy kernel panic after upgrade
https://bugs.launchpad.net/bugs/222799
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.ubuntu.com
** Description changed:
I've got a problem with the new kernel. After upgrade Gutsy->Hardy which
went fine reboot welcomes me with Kernel panic - not syncing: VFS:
unable to mount root on unknown-block(0,0). Trying to boot Gutsy kernel
ends in BusyBox. Quick look around in it showed no har
** Description changed:
I've got a problem with the new kernel. After upgrade Gutsy->Hardy which
went fine reboot welcomes me with Kernel panic - not syncing: VFS:
unable to mount root on unknown-block(0,0). Trying to boot Gutsy kernel
ends in BusyBox. Quick look around in it showed no har
32 matches
Mail list logo
