Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 43203 - "Powered by Gentoo" frambuffer logo glitch
Summary: "Powered by Gentoo" frambuffer logo glitch
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: PPC All
: High minor (vote)
Assignee: (DEPRECATED)
Depends on:
Reported: 2004-02-28 06:54 UTC by Maciej J. Woloszyk
Modified: 2004-04-11 15:03 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Maciej J. Woloszyk 2004-02-28 06:54:13 UTC
Some time ago I've found that my favourite framebuffer logo (black background
"Powered by Gentoo") doesn't look well on my new machine (Pegasos II PPC with
Radeon 9200 and Radeon frambuffer driver). The problem is that there are some
strange bright dots on the logo - as I can't really take snapshot of the boot
screen I used a digital camera, and placed the picture (~75kB) here:
I use the newest ppc-sources-dev and all other logos looks fine only this one
is distorted. I checked the includes in kernel sources and there is notning
wrong with them - they are exactly the same as on my other x86 machine where
the logo looks right. I think the problem is somewhere in radeon framebuffer
because on x86 where it looks good I used vesa framebuffer (with exactly the
same Radeon I use now in PPC machine).

Comment 1 Jason Cox (RETIRED) gentoo-dev 2004-04-11 13:35:43 UTC
Could you try using the vesa framebuffer and see if the problem still exists? Also, which exact kernel is this on?
Comment 2 Maciej J. Woloszyk 2004-04-11 14:15:05 UTC
Well, I'd be more than happy to try the VESA if only you tell me how to do that on PPC ;) Or maybe there is something I don't know? And yes - the same (exactly) card put in x86 PC using VESA framebuffer works just fine - logo looks exactly as it's supposed to.
And to the version of the kernel version it's 2.4.24-ppc-dev-r2, but I had this effect from the first time I've run Gentoo on this machine and then it was 2.4.22-ppc-dev. It is possible of course that it's something wrong with my hardware, but then I would like to see something that would make a proof especially that almost everything else works fine (to the extents of the hardware and firmware support).
Comment 3 Jason Cox (RETIRED) gentoo-dev 2004-04-11 14:28:00 UTC
You need to build vesafb into the kernel, instead of radeonfb. Then pass video=vesa,XXXXXX on your kernel line in lilo/grub.conf.
Comment 4 Maciej J. Woloszyk 2004-04-11 14:37:49 UTC
Haven't you seen the irony? ;) How am I supposed to compile in VESA
framebuffer (which is x86 PC feature and uses VESA bios) into PPC kernel?
VESA is strictly x86 and (I did checked the kernel configuration) it even
doesn't appear on PPC.
Comment 5 Jason Cox (RETIRED) gentoo-dev 2004-04-11 14:41:00 UTC
Heh. Wow, I didn't know that. Perhaps this is better left to the ppc-kernel team. I'm an x86 kernel guy, and haven't really played with the PPCs. Sorry about that. The only thing I can think of is possibly filing a bug at, or joining #gentoo-ppc on and asking there. Maybe an upgrade to a 2.6 kernel would help. I think your best bet would be 2.6.5-mm4 which contains the latest fb drivers.
Comment 6 Maciej J. Woloszyk 2004-04-11 14:52:45 UTC
Well - I do consider an upgrade to 2.6, but for a moment I don't have time for
And additionally it's not that easy with Pegasos - as far as I know
there is only one specific working version of 2.6 kernel with full Pegasos
And finally - I've reported this error with the severity "minor" as It's just
a bit annoying and nothing more - everything else seems to work fine. And as
I don't really turn the machine off a lot it's not much of a problem.
Comment 7 Jason Cox (RETIRED) gentoo-dev 2004-04-11 15:03:14 UTC
I'm sorry I couldn't help you more. The only thing I can recommend is heading to and posting there. I'd include a link back to this thread if you decide to start a thread on the kernel bug tracker.