Ubuntu
linux-source-2.6.17 package

Linux hangs at boot after upgrade from Dapper to Edgy

Bug #85149 reported by Donald Brendel
6
Affects Status Importance Assigned to Milestone
linux-source-2.6.17 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-2.6.17-11-386

After upgrading from Dapper (linux-image 2.6.15) to Edgy (linux 2.6.17) the system wouldn't boot anymore. Even the message 'uncompressing boot kernel' wouldn't appear anymore. The system simply hangs, even after an extended period of time (1/2 hour+) nothing happens. The harddisk is not busy when the boot hangs. Using the older image fixes the problem (fortunately).

I'm using an SATA HDD via a PROMISE TX2 adapter on an AMD system. Nothing beside the Ubuntu has changed, neither hardware nor software.

See original description
Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Hi Donald

Upgrades are only supported from one Ubuntu version to the next: from Breezy to Dapper, from Dapper to Edgy...
But not from Breezy to Edgy. Surely that's the problem.

You can try to repeat it upgrading from Breezy to Dapper, and then from Dapper to Edgy.

Best regards
Emilio

Changed in linux-source-2.6.17:
status: Unconfirmed → Rejected
Revision history for this message
Donald Brendel (d-brendel) wrote :

Hi Emilio,

Sorry, my fault: I upgraded from Dapper (not Breezy) to Edgy. And due to upgrade problems from Breezy to Dapper (propably my mistake) I did a clean install of Dapper.

What's also interesting: even the Edgy install-cd will not proceed beyond the initial screen on any of the install options. Maybe this gives a clue. I still assume that there's something wrong with the linux kernel 2.17 and SATA (via PROMISE TX2) eventually in combination with external USB drives.

I will wait for the next release (soon) and give it a fresh&clean try.

Anyway thanks for your reply,
Donald Brendel

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote :

Then I reopen the report, and edit the description ;)

Changed in linux-source-2.6.17:
status: Rejected → Unconfirmed
description: updated
Revision history for this message
Cristian Aravena Romero (caravena) wrote :

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available here: <http://wiki.ubuntu.com/DebuggingKernelProblems> Thanks!

Changed in linux-source-2.6.17:
status: Unconfirmed → Needs Info
Revision history for this message
hendry (hendry-webc) wrote :

I've seen this problem when I installed dapper on a friend's machine and then upgraded it to edgy. 2.6.15 boots, 2.6.17 doesn't as this bug earlier describes.

Revision history for this message
hendry (hendry-webc) wrote :
Revision history for this message
hendry (hendry-webc) wrote :
Revision history for this message
Donald Brendel (d-brendel) wrote : Found solution: Linux hangs at boot after upgrade from Dapper to Edgy

I recently found a solution for the mentioned problem. It works for me but has the slight disadvantage that it needs to be fixed after each update of the image. For a perfect explanation of the problem and the cure of it please follow the link: http://www.mohawksoft.org/?q=node/26

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux-source-2.6.17 (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.