Very early boot failure on iMac G5 ("rev 2")

Please test with a USB keyboard and mouse in order to test your hypothesis about
the issue being related to bluetooth

I can't, the unit has no USB input devices. All-bluetooth is one of Apple's
stock configurations, not mine. Do not ask testers to execute multiple
configurations, they are responsible for bug reports on their own hardware
alone. The "hypothesis" was just gravy, I should not even have to produce one,
just the bug report itself.

(In reply to comment #1)
> Please test with a USB keyboard and mouse in order to test your hypothesis about
> the issue being related to bluetooth

I have an iMac G5 2.1GHz, connected to its keyboard and mouse via USB. I think I can confirm this behavior (see below).
In fact, the computer exhibits different behavior depending on what boot option is selected ("live" or "live-powerpc64")

If booted under the "live" option, the behavior described above is what happens.

If booted under the "live-powerpc64" option, the above OpenFirmware screen comes up, but is overlaid (not refreshed, just
printed directly over in a different but still fixed-width font) with the following:

MM Init

cf000100

MM Init Done

cf000012

Setup Arch

And does not continue to boot. A hard power-down (several seconds holding down the power key) is necessary to restart.

I confirme this bug.

I posted another bug ( bug #26113 ) exactly about this problem on iMac G5 rev 3 (the iSight line). I was able to boot a kernel compiled by benh with it latest patches ( available at http://gate.crashing.org/~benh/vmlinux.bz2 ). I have installed an ubuntu with this kernel. But the radeon is not recognize by radeonfb ( product id = 0x3e50 ) and Xorg does not start correctly. Currently i have colored verticals lines.

So benh is doing a great job to support this and as ben.collins said, those patches may be included in 2.6.16. Will they be backported to 2.6.15 -powerpc64 ?

Verso l'Alto !

I'm doubting this will get in dapper. I'll do my best though.

Hello,

I'm runing a 2.6.16-rc5 kernel compiled with make-kpkg, but it still do not support neither the fan nor the radeon X600.

Keep waiting ...

I reach to run Xorg. I explain the process at http://ozlabs.org/pipermail/linuxppc-dev/2006-March/021514.html I'm writin an Howto in the wiki.

Hello,

The howto is available at https://wiki.ubuntu.com/iMacG5revC

Étienne.

Used text installer for Dapper 6.0.6 final.

The boot prompt accepts bluetooth keyboard input (l for Linux, x for Mac OS X, and all that). Bootup sequence is normal. At login screen, Dapper fails to detect keyboard/mouse input.

Note the silliness here, as the little bootloader manages to handle bluetooth keyboard inputs, and fully booted Dapper does not.

Result is that user cannot log in.

Looks like it is related to bug #32415.

That's not due to xorg, but radeonfb.

Can anyone test this out with a Feisty nightly and/or a currently updated Edgy so we can see if this bug still exists?

Hi,

Tested on iMac G5 rev C on feisty. It fail to mount root FS.

Étienne.
--
Verso l'Alto !

Can someone test this under a newer Feisty build so we can see if this bug still exists with the newest 2.6.20 kernel?

http://cdimage.ubuntu.com/ports/releases/feisty/herd-5/

Timothy Smith said

> Can someone test this under a newer Feisty build
> so we can see if this bug still exists with the newest
> 2.6.20 kernel?

Tested under Feisty final - bug is still there - see my report
https://launchpad.net/ubuntu/+source/bluez-utils/+bug/32415/comments/113

Strongly suspect pure bluetooth problem as guesstimated in original bug report here.

Amazing how long this bluetooth bug has sat around and was supposedly "fixed" with the updated bluez package. Not!

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]