We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

Bug 384 - fbcon doesn't reset vidmode on SDL_Quit()
Summary: fbcon doesn't reset vidmode on SDL_Quit()
Status: RESOLVED WORKSFORME
Alias: None
Product: SDL
Classification: Unclassified
Component: video (show other bugs)
Version: HG 1.2
Hardware: x86 Linux
: P2 normal
Assignee: Ryan C. Gordon
QA Contact: Sam Lantinga
URL: http://lists.libsdl.org/pipermail/sdl...
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-25 19:48 UTC by Ryan C. Gordon
Modified: 2007-05-28 22:40 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan C. Gordon 2007-01-25 19:48:58 UTC
Apparently the fbcon target doesn't always reset the video mode on exit:

   http://lists.libsdl.org/pipermail/sdl-libsdl.org/2007-January/059751.html


Most relevant info follows.

"Here's the exact code that will duplicate the problem:

int main(int argc, char**argv)
{
    SDL_Init(SDL_INIT_VIDEO);
    SDL_SetVideoMode(1024, 768, 32, SDL_FULLSCREEN | SDL_ANYFORMAT | SDL_HWSURFACE | SDL_DOUBLEBUF);
    SDL_Quit();
    return 0;
}

Here's output of "dmesg | grep radeon":

radeonfb: Found Intel x86 BIOS ROM Image
radeonfb: Retrieved PLL infos from BIOS
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=378.00 Mhz, System=338.00 MHz
radeonfb: PLL min 20000 max 40000
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type no found
radeonfb (0000:01:00.0): ATI Radeon NH

I'm using linux kernel 2.6.16.27 (built using LFS 6.2 and jhalfs).  I've added a few items from blfs like nfs + dependencies, along with inetd servers.

Like always, any help is appreciated... now onto my V4L Hauppauge ImpactVCB issue :-)."


--ryan.
Comment 1 Ryan C. Gordon 2007-05-28 22:40:18 UTC
(This worked for me when I tested it...I think it might be a flakey kernel driver.)

--ryan.