Hi Walter, yep not default for every kind of ppc system, only for those specific G4 ibook's with the radeon 9200 variant, tho eMacs with those would also seems like a save bet-!? Sry I haven't yet gotten around to the FAQ/ Known Issues addition but I plan on spending some time on it tomorrow :)
For everyone else reading up on this I figured I should post our conclusion so far here as well: 1. yaboot params don't seem to stick/ carry over from live-boot initiated installations (intentionally?? for many mac users this would probably be unexpected and result in what I'd like to describe as "wtf I already had the correct params set why doesn't it work as expected" and be cause for confusion as the needed workarounds to "make it work" would not be actually used anymore while still assumed to be in use, so likely cause for seemingly "not working out of the box Question: what can be done about that or is pointing to more detailed Information on that and the actual params needed the only available course of action or can those params be set default out of the box on affected system configurations? 2. Radeon 9200/ RV 280 (M9+) chips on the PowerBook6,5 (ibook G4, 12' inch, 1.2 GHz) and also likely similar ibook and eMac Radeon 9000 range of chips for some reason won't work reliable on Radeon-KMS with AGP transfer enabled, so those need "radeon.agpmode=-1" no idea if it's a flaw in the way Apple implemented AGP on these ibooks or in combination with an expectation of the driver on how AGP is supposed to be implemented, or simply some bug, but it won't work at the moment and causes the freeze issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878 3. using the older framebuffer params in any way on top of things causes conflicts with KMS which even with "radeon.agpmode=-1" set would cause UI/ GUI issues like incomplete loading or nonfuctional UI/ GUI, so we additionally would need "video=ofonly" here and should not try to additionally use any combination of eg. "radeonfb" (which quite a few older workaround instructions might confusingly suggest and result in the user having any variation of params but not only the above 2 he or she would need to make it work) 4. with "video=ofonly radeon.agpmode=-1" those ibooks would boot and be useable prefectly fine BUT there will be "sluggish" feeling 2D/ gui/ windows moving and no accel at all which would be the result of not having Xorg properly configured/ detecting the chip and using the appropriate driver out of the box which also would have to be initiated manually at this point: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/1058641 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1366556 to fix from a booted Installation: sudo service lightdm stop sudo Xorg -configure sudo mv xorg.conf.new /etc/X11/xorg.conf sudo nano /etc/X11/xorg.conf [Here some driver options could be set, eg. uncomment pageflip and set it to "True", save any edits and after that reboot] sudo shutdown -r now --------------- Grüße boris -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1377878 Title: PPC - GUI freezes except for mouse pointer Status in “linux” package in Ubuntu: Confirmed Bug description: During the installation the computer freezes completely except for the mouse pointer. And even that is stuck with whatever shape it happened to have at the time it froze. The steps I have to cause the freeze are run Ubiquity to start the installation open a terminal, run Ubuntu-bug and let it launch Firefox. It will freeze every time then. Even the consoles (ctrl-alt-f1 etc) are unavailable. What kind of information can I collect and how? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
