Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 25025 - Vesa framebuffer (fb0) is distorted when tdfxfb (fb1) is initialized
Summary: Vesa framebuffer (fb0) is distorted when tdfxfb (fb1) is initialized
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Michal Januszewski (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-21 20:53 UTC by Timm Wimmers
Modified: 2004-10-23 06:18 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Timm Wimmers 2003-07-21 20:53:37 UTC
First I tried to use 'framebuffer' and 'bootsplash' with the tdfxfb driver.
Framebuffer works fine, but didn't get a /proc/splash so 'bootsplash' fails.
Kernelparameter was: video=tdfxfb:1280x768@76 (this make tdfxfb to be fb0). All
VT's are in expected video modes.

If I switch to vesa with kernelparameter: video=vesa:ywrap,mtrr vga=0x31a (this
makes vesa to be /dev/fb0 and tdfx to be /dev/fb1), the framebuffer _works_
until fb1 is initialized for just a second and ends up in a mangled and
distorted console (all VT's), but boot normaly into X11 and /proc/splash is present.

I think, this can be solved by disabling the tdfx-driver (not tried yet, because
running a really slow machine) in the kernel and use only  vesa, but vesa didn't
support refreshrates greater than 60HZ, so I recommend to fix tdfxfb.

Thank you.
Comment 1 Timm Wimmers 2003-07-21 20:56:24 UTC
Forgotten the used kernelsources: gentoo-sources 2.4.20-rc5
Comment 2 SpanKY gentoo-dev 2003-09-11 19:17:16 UTC
this still a problem with latest gentoo sources ?
Comment 3 Troy Dack 2003-09-12 06:37:27 UTC
Instructions on www.bootsplash.org (the origin of the bootsplash patches) look like 
most testing was only conducted with the VESA fb driver. 
 
As you have found, having 2 different fb drivers trying to access the hardware (in 
your case tdfx-fb and vesafb) is likely to cause problems. 
 
Please test this with only the VESA fb driver (ie: don't build the tdfxfb driver either 
as a module or in the kernel). 
 
If it works with just VESA then I suggest that you contact the author of the tdfxfb 
driver. 
 
Also have a search on forums.gentoo.org, there are reports there from people who 
have successfully achieved better refresh rates from the vesafb. 
Comment 4 Daniel Black (RETIRED) gentoo-dev 2004-10-02 07:08:22 UTC
tad is not an active developer. 
Comment 5 Michal Januszewski (RETIRED) gentoo-dev 2004-10-02 10:29:47 UTC
Any updates on the problem? Is this still an issue with the latest 2.6 kernels?
Comment 6 Michal Januszewski (RETIRED) gentoo-dev 2004-10-23 06:18:02 UTC
Closing, since the has been no comment from the bug reporter for almost a year..