Rivafb framebuffer needed on powerbook 12

[sbriglie]

Binary package hint: linux-image-2.6.17-10-powerpc

12 inch display powerbooks (at least recent ones) have a nvidia geforce 5200 go graphics card. As you know the ppc platform requires a framebuffer driver. Since rivafb is compiled as a module in edgy default config (linux-image-2.6.17-10-powerpc 2.6.17-10.33) openfirmware (ofonly) framebuffer driver is used instead, even though my yaboot.conf appends video=rivafb to the kernel. The openfirmware driver is just a generic, failsafe driver for the ppc platform and has many shortcomings. In particular, as stated in Bug #35992 and Bug #21478, lcd brightness control doesn't work (very very annoying) and usplash has completely wrong colors (ofonly works in 8 bit mode). I have tried to solve the problem putting rivafb in the initramfs by editing /etc/initramfs-tools/modules, but without success because, according to dmesg, the kernel loads the framebuffer driver before reading the initrd, so the rivafb module gets loaded too late and fails to work. The error is:
PCI: Unable to reserve mem region #2:8000000@a0000000 for device 0000:00:10.0
rivafb: cannot request PCI regions
rivafb: probe of 0000:00:10.0 failed with error -16

I believe the only solution is to compile rivafb statically into the bzImage, I see radeonfb already is. I'd like to avoid having to recompile my kernel just for this, at least not until edgy is released and the kernel is stabilized.

[sbriglie (sbriglie)]

I have recompiled my kernel with CONFIG_FB_RIVA=y and now lcd brightness control works flawlessly and usplash is in full color. Thanks for the attention

[Brian Murray (brian-murray)]

We are sorry that we didn't get to your bug report earlier, but the 18 month support period for Edgy Eft, 6.10, has reached it's end of life and we are marking the linux-source-2.6.17 task as Won't fix. However, please note that I am opening a linux task for the actively developed kernel where CONFIG_RIVA_FB is still a module.

[Leann Ogasawara (leannogasawara)]

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.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[dino99 (9d9)]

no recent acivity; is it still a problem ?

http://www.iloveubuntu.net/may-9th-2013-sees-end-life-ubuntu-804-hardy-heron-server-ubuntu-1004-lucid-lynx-desktop-and-ubuntu

[Launchpad Janitor (janitor)]

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