No desktop with Radeon video chips on LiveCD

Bug #1040544 reported by Lars Noodén
52
This bug affects 8 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The graphical installer fails to bring up a usable box for installation. See the attached screenshot. This is from the PPC Desktop image from 20120821

http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/21606/downloads

Revision history for this message
Lars Noodén (larsnooden) wrote :
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1040544

tags: added: iso-testing
Revision history for this message
Colin Watson (cjwatson) wrote :

I tried to reproduce this in qemu, but I couldn't. The installer is very slow (due in part to a regression caused by the Python 3 port, which I've fixed for our next upload), but it does start.

Can you reproduce this behaviour reliably? Can you provide any installer log files?

Changed in ubiquity (Ubuntu):
status: New → Incomplete
Revision history for this message
Lars Noodén (larsnooden) wrote :

Yes, it happens every time, even with the 2012-09-05.1 Desktop image. The frame of the dialog box comes up but there is no content, just messed up graphics.

tags: added: quantal
ojordan (ojordan12345)
Changed in ubiquity (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
ojordan (ojordan12345) wrote :

I suspect this is only a radeon PowerPC problem. Userspace Mode Setting has been removed and the current kernel config doesn't allow KMS to function (the radeonfb module is built-in). What is happening is that the fbdev driver is used instead in 8 bit pseudo colour. Why that causes ubiquity to not display anythng I don't know. The window sort of grabs the image of background or other windows/menus that are placed over it, but doesn't display images of its own.

Using the yaboot parameters "video=ofonly radeon.agpmode=-1" (which enables KMS and a functioning radeon driver) ubiquity works fine.

Revision history for this message
ojordan (ojordan12345) wrote :

Trying to organise things a bit, this is the general bug of gripes caused by UMS being dropped https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1046951 . It should end up being assigned to the kernel, but it will also need the boot message on the PowerPC CDs changed. Should the latter be raised against "ubuntu-cdimage" project?

Revision history for this message
ojordan (ojordan12345) wrote :

Network applet windows have the same proplem.

Revision history for this message
ojordan (ojordan12345) wrote :

If I remember rightly (which I probably don't), qemu emulates a G4 imac. They use a nouveau card. Using the 'nomodeset' yaboot parameter should drop you into the same 8-bit depth fbdev/offb combination.

Revision history for this message
ojordan (ojordan12345) wrote :

It would be interesting to know if other 'regular' architectures could replicate this bug if they use fbdev in 8 bit mode? Does 'nomodeset' cause 8 bit depth for them?

Revision history for this message
ojordan (ojordan12345) wrote :

We can add the disk utility to the applications that don't work in lubuntu in 8 bit pseudo colour.

summary: - Installer dialog does not come up
+ Installer dialog does not come up on PPC
Revision history for this message
Lars Noodén (larsnooden) wrote : Re: Installer dialog does not come up on PPC

Booting with the parameters 'live video=ofonly' makes the installer dialog readable. This is only a work-around.

Revision history for this message
2blue (arild-lindseth) wrote :

Neither if the work-arounds I have been suggested make intsaller work, "video=ofonly radeon.agpmode=-1" gives an error message; "video=ofonly:2,/vmlinux: Unable to open file, Invalid device"

Revision history for this message
ojordan (ojordan12345) wrote :

Just correcting my post #8. Of course the radeon card is using a fbdev/radeonfb combination and the nvidia cards (using 'nomodeset') will use a fbdev/offb combination. The openfirmware framebuffer (offb) is seemingly limited to 16 colours so the graphics are even worse. Ubiquity doesn't show anything using fbdev/offb either.

@2blue https://wiki.ubuntu.com/PowerPCFAQ#What_yaboot_parameters_should_I_use_for_graphics_problems.3F

Revision history for this message
Greg Faith (gregfaith) wrote :

Okay I have the ATI Radeon RV250 on this PowerBook G4.

I can get to a clean live session with the following kernel command line

live video=radeonfb:1024x768-32@60

I can then make a clean install. but have no obvious graphics module in lsmod.

sudo modprobe radeon does get the module running and the helpers modules.

On reboot ( as expected it is gone)

sudo su
echo radeon >> /etc/modules
exit

and i have bootable install with the radeon module and helpers in lsmod.
Hope this might help.

Revision history for this message
Ron Mitchell (rm2892) wrote : Re: [Bug 1040544] Re: Installer dialog does not come up on PPC

Did not work here Greg. Had to go back to my <radeonfb:yada yada>

Wierd or what?

Ron M.

On Wed, 03 Oct 2012 04:19:19 -0000
Greg Faith <email address hidden> wrote:

> Okay I have the ATI Radeon RV250 on this PowerBook G4.
>
> I can get to a clean live session with the following kernel command line
>
> live video=radeonfb:1024x768-32@60
>
> I can then make a clean install. but have no obvious graphics module in
> lsmod.
>
> sudo modprobe radeon does get the module running and the helpers
> modules.
>
> On reboot ( as expected it is gone)
>
> sudo su
> echo radeon >> /etc/modules
> exit
>
> and i have bootable install with the radeon module and helpers in lsmod.
> Hope this might help.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1047636).
> https://bugs.launchpad.net/bugs/1040544
>
> Title:
> Installer dialog does not come up on PPC
>
> Status in “ubiquity” package in Ubuntu:
> Confirmed
>
> Bug description:
> The graphical installer fails to bring up a usable box for
> installation. See the attached screenshot. This is from the PPC
> Desktop image from 20120821
>
> http://iso.qa.ubuntu.com/qatracker/milestones/219/builds/21606/downloads
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1040544/+subscriptions

--
Ron Mitchell <email address hidden>

Revision history for this message
ojordan (ojordan12345) wrote : Re: Installer dialog does not come up on PPC

@gregfaith if you want to use the radeon modules then you need to disable the radeonfb framebuffer. If you don't do this then the radeon modules don't do anything.

Revision history for this message
Ron Mitchell (rm2892) wrote :

video=ofonly

kills my machine. Can't even get a command line interface up after that.

(Radeon 9200)

Ron Mitchell

Revision history for this message
Andrea Gottardo (gozzi) wrote :

I can confirm the bug is still present in Lubuntu 13.04 on my iMac G5 (RevC) with an ATI X600. I still have to check if the proposed kernel options will fix the problem, I will keep you updated.

Revision history for this message
Lars Noodén (larsnooden) wrote :

Here is the description in the documentation:

https://help.ubuntu.com/community/Lubuntu/Documentation/FAQ/PPC

summary: - Installer dialog does not come up on PPC
+ No desktop with Radeon video chips on LiveCD
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in ubiquity (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.]

Changed in ubiquity (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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