iB::Topic::refresh rate different in X vs. cmd line

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » X and Fluxbox » refresh rate different in X vs. cmd line

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

[ Track this topic :: Email this topic :: Print this topic ]

Topic: refresh rate different in X vs. cmd line, interesting problem

< Next Oldest | Next Newest >

irun5k

Group: Members
Posts: 24
Joined: July 2004

Posted: Oct. 12 2004,20:48

Using DSL in a digital picture frame project, all working well with one minor exception.

When shutting down the box, X shuts down first and you revert back to a command line and normally see the remaining shutdown commands happen. Not in my case. The refresh rate for some reason changes when going back to command line, and as a result it messes up the display on the LCD (standard, rolling horizontal lines you get when the refresh rate is wrong.) When you boot back up all is fine again, but the dirty shutdown still bothers me because it (1) isn't clean & shouldn't happen this way, and (2) seems like it could cause monitor damage.

The LCD is a 15" samsung tft. So, can anybody explain why the refresh rate shifts when stopping X and going to a command line, and how most systems handle this gracefully (where as mine does not?)

Thanks!

ke4nt1

Group: Members
Posts: 2329
Joined: Oct. 2003

Posted: Oct. 12 2004,23:31

I'm guessing your running XVesa..
Have you tried booting up with a proper framebuffer ?

Sometimes I see a similar problem, where the text is writing
with larger than the standard 40/80 lines of text, which makes
everything appear diagonal.
This ONLY occurs AFTER exiting X, and back to cli prompt ..

Other times I truly see two images , in each half of the screen..
In both instances, setting up the framebuffer solved this issue..
Same thing, this ONLY happens after I exit X , and back to the prompt.

What resolution are you running now for your frame?
try that resolution at startup by typing fb1024x768 , for ex.
Then select the xfbdev xserver at the xsetup screens,
and see if it is better behaved..

73
ke4nt

irun5k

Group: Members
Posts: 24
Joined: July 2004

Posted: Oct. 13 2004,01:50

Quote

I'm guessing your running XVesa..
Have you tried booting up with a proper framebuffer ?

Yes, you guessed right. I'm running in 1024x768, 24 bit depth (thats the max mode listed.) Hardware is an EPIA 5000. Interesting suggestion about booting with a framebuffer. I will have to give this a try. I'm running a standard DSL hd install... I'm sure I can find something in the forums here to tell me how to "automagically" pass in a fb1024x768 directive.

Thanks for the tip!
Brian

irun5k

Group: Members
Posts: 24
Joined: July 2004

Posted: Oct. 18 2004,14:00

Hmm. Any advice on where in lilo.conf to stick "fb1024x768"? Haven't had much luck finding out. Since I'm in hdinstall mode, I think I have to pass fb1024x768 in lilo.conf, right?

ke4nt1

Group: Members
Posts: 2329
Joined: Oct. 2003

Posted: Oct. 18 2004,14:56

Yes, you will need to edit lilo.conf, and rerun lilo to make that work.

I suggest you first try this with a liveCD , to test and get the parameters right,
THEN apply your successful setup parameters to the lilo.conf..

There are several posts in the forums detailing editing your
lilo.conf file..

73
ke4nt

4 replies since Oct. 12 2004,20:48

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Damn Small Linux Board » Damn Small Linux » X and Fluxbox » refresh rate different in X vs. cmd line