Ubuntu 9.04 rc does not boot on k8

Bug #362629 reported by Michael Lazarev
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Jaunty by Michael Lazarev

Bug Description

I made a live USB from freshly downloaded ubuntu-9.04-rc-desktop-i386.iso

On the second boot, I choose "Run Ubuntu without installing it"
Three seconds later, I got the following screen:

-----------------------------------------------------------------------

[ 2.969192] powernow-k8: BIOS error - no PSBor ACPI _PSS objects
Loading, please wait...

BusyBox v1.10.2 (Ubuntu 1:1.10.2-2ubuntu7) built -in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _

-----------------------------------------------------------------------

Before this at the first boot from USB, I started integrity check.
It booted, showed a progress bar and reported that no errors were found.

I tried Ubuntu 9.04 Beta earlier, and there was no such error.
I believe, it was introduced later.

lshw attached.

Please, contact me, I am willing to help.

Revision history for this message
Michael Lazarev (milaz) wrote :
tags: added: 9.04 bios powernow rc
Michael Lazarev (milaz)
description: updated
Revision history for this message
zosX (zosxavius) wrote :

I have the same problem here. SiS Chipset, Athlon 64 3000. The ACPI option at boot only gets so far as well before it dumps into busybox (usually around the USB detection). Not fun. I was greatly looking foward to this release as it seems driver situation for ATI has improved. I'll be watching this bug report. Oh, and ACPI is definitely enabled in my bios, sleep state is set to S3. I don't think it would be possible to disable it and still boot into XP without a reinstall. :/

Revision history for this message
zosX (zosxavius) wrote :

I should add that trying both 32 and 64-bit flavors yield identical results. Somethings fishy with the new kernel....

Revision history for this message
Tokenekie (tokenekie) wrote :

See progress on bug https://bugs.launchpad.net/ubuntu/+source/casper/+bug/363038

Comment by user David Mandala shows a recent build of Jaunty seems to have solved the problem.

Currently trying to confirm the fix on my x86 PC.

Revision history for this message
Michael Lazarev (milaz) wrote :

@Tokenekie: thanks!

I've just downloaded the jaunty-desktop-i386.iso dated 18-Apr-2009 08:07 at http://cdimage.ubuntu.com/daily-live/current/, exactly like David Mandala.

I report that I can boot again.

Revision history for this message
Michael Lazarev (milaz) wrote :

Having switched to tty1, I see now that error message is still there:

-----------------------------------------------------------------------

[ 2.965188] powernow-k8: BIOS error - no PSBor ACPI _PSS objects
Loading, please wait...

-----------------------------------------------------------------------

but booting process successfully continues instead of throwing me into BusyBox.

Revision history for this message
Tokenekie (tokenekie) wrote :

Hm, there might still be an issue regarding persistence. I used 4/19/2009's "Jaunty-desktop-i386" build but even though I asked the usb-creator to make a persistent usb, the resulting live usb was NOT persistent.

So the new x86 build is now confirmed to create a working live usb, but it might not make a persistent one. I'm going to try to verify this issue right now.

Changed in ubuntu:
status: New → Confirmed
Revision history for this message
zosX (zosxavius) wrote : Re: [Bug 362629] Re: Ubuntu 9.04 rc does not boot on k8

I would like to add that I used the daily and got the same result.
Waiting for a while and exiting busybox allowed it to continue to
boot. I should also add that this was installed via wubi on an XP
partition. I know its not related to this bug, but upon installation
it asks to install to a partition and fails to see the virtual
partition that wubi created as it appears to be running off of the
livecd image. It will try to install to any real partition you have.
Not really what you want when you already created a virtual partition.
I remember from before that it would just install by default to the
virtual drive, so I'm thinking that this bug is also affecting the
detection of the fs.......

You might want to fix this one before relase.....

Revision history for this message
zosX (zosxavius) wrote :

First of all I apologize if this is posted twice. I responded via e-mail first and didn't see the response listed on the bug report page so if it does appear spontaneously from the ethereal void, you'll know why.

I would like to add that I used the daily and got the same result.
Waiting for a while and exiting busybox allowed it to continue to
boot. I should also add that this was installed via wubi on an XP
partition. I know its not related to this bug, but upon installation
it asks to install to a partition and fails to see the virtual
partition that wubi created as it appears to be running off of the
livecd image. It will try to install to any real partition you have.
Not really what you want when you already created a virtual partition.
I remember from before that it would just install by default to the
virtual drive, so I'm thinking that this bug is also affecting the
detection of the fs.......

You might want to fix this one before relase.....

Revision history for this message
Rave[N]Black (blackravener) wrote :

try removing usb stick right after linux fully shuts down and reinsert it just after bios screen shows up.
I don't know why (I'm nowhere near linux guru), but it seemed to work on my ubuntu 8.10 live usb.

Revision history for this message
zosX (zosxavius) wrote :

Well, I'm booting off a virtual partition and getting the same
problem. Clearly its something wrong with the USB detection and power
management. It may be be that my bios has an error, that someone just
uncovered. The latest build is still exhibiting the same problem.

-z-

Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage , so I have classified this bug as a bug in linux kernel package.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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