Screen Blank While restarting/shutdown

konsolebox · 07-26-2006, 09:18 PM

on my opinion that should appear.

here's an update btw. instead of doing a blind typing, you can do this in the run command box:

Code:

chvt 1; fbset -v "value"

raskin · 07-27-2006, 04:29 AM

Hello, konsolebox.. <I must go read what LQ friend list is>. I can suppose situation where chvt + fbset will give other results, but I'm not sure. It can get tty it is run from - or not.. About console switching - read middle of the thread, any deinitialization of video mode set by that fine driver (TFD) fails, more or less.
About run level: go to /etc/init.d . Create two scripts: doing chvt 1 and doing fbset (or running sample svgalib go-to-textmode program). Then create two links in /etc/rc6.d (and same in rc0.d): S00_30_chvt and S00_60_fbset .
In svgalib.conf try killing mouse.. If you try to initialize mouse while X is alive, you'll have to fight for control, and X is bigger and already there, you know...
About step-by step: I am just throwing ideas. I've encountered similar problems, but ignored them (and later found DRI driver). I'm not sure if something will help. I'm sure it mustn't (but there are possibly deadly bugs - though unlikely) ruin your disk contents, and you understand well it can ruin your session when run. So I propose experiments which are most close to what should work. I can give ideas and advice on rough edges, but not complete guide..

kushalkoolwal · 07-28-2006, 02:22 PM

Quote:

Originally Posted by konsolebox

on my opinion that should appear.

here's an update btw. instead of doing a blind typing, you can do this in the run command box:

Code:

chvt 1; fbset -v "value"

ok I tried the fbset method but it did not work.

my fbset returned the following information:

Code:

mode "1024x768-76"
    # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
    geometry 1024 768 1024 768 16
    timings 12714 128 32 16 4 128 4
    rgba 5/11,6/5,5/0,0/0
endmode

So as Konsolebox suggested, I gave the following command:

Code:

chvt 1; fbset -v "1024x768-76"

Again the monitor went out of range i.e. the blank screen. Now on hitting ctrl-alt-f7(blindly) I was again taken to my fluxbox windows manager and I got the following message on my xterm screen:

Code:

chvt 1; fbset -v "1024x768-76"
Opening framebuffer device '/dev/fb0'
Reading mode database from file '/etc/fb.modes'
Unknown video mode '1024x768-76'
root@debian:~#

Am I missing something?

Any other settings which you think might work?

If this does not work then I think I will try the svgalib path as suggested by raskin

Thank you.

raskin · 07-28-2006, 03:04 PM

read man fbset and post /etc/fb.modes here.

kushalkoolwal · 07-28-2006, 03:23 PM

Quote:

Originally Posted by raskin

read man fbset and post /etc/fb.modes here.

Here is my fb.modes:
http://www.cs.uoregon.edu/~kushal/fb.modes

I also tried giving the command:

chvt 1; fbset -v "1024x768-75"

since the "1024-768-75" was there in the fb.modes file but I got the same out of range message from monitor. As mentioned before I can type blindly everything.

I am using "ViewSonic VG510b" monitor. I have tried changing monitors also but the same old result.

If we can find a way to reset the framebuffer text console to it's default setting by fbset then I think it may do the trick.

Thank you once again for the help.

raskin · 07-28-2006, 04:31 PM

Well, did you try to type it in real console blindly? Might work differently..

kushalkoolwal · 07-28-2006, 04:33 PM

Quote:

Originally Posted by raskin

Well, did you try to type it in real console blindly? Might work differently..

What do you mean by real console? You mean first I type chvt 1 and then when the screen goes to blank then I type fbset "<mode>"

As far as I understand chvt 1 means it will change to virtual console 1, right? How do I get access to real console?

konsolebox · 07-28-2006, 06:08 PM

it seems that the values in fb.modes are not compatible with your monitor. ok you can do my trick.

restart system to console. then run fbset. take note of the mode and enter the values to /etc/fb.modes. if the mode already exist, just comment it with '# ' then enter the new values below it.

now restart the system again so that fb.modes is surely loaded.
try 'fbset <mode>' in console. nothing should change to your monitor.

then run x and try the old procedure with the mode.

konsolebox · 07-28-2006, 06:11 PM

btw don't run 'chvt 1; fbset -v "1024x768-##"' in xterm or konsole. run it in the run command box.

kushalkoolwal · 07-28-2006, 06:54 PM

Quote:

Originally Posted by konsolebox

btw don't run 'chvt 1; fbset -v "1024x768-##"' in xterm or konsole. run it in the run command box.

Right now I am using fluxbox manager. The system with GNOME installation is on a another hard drive. I can try the Run command box method on GNOME but what should I do for the fluxbox??

konsolebox · 07-28-2006, 07:37 PM

add this text to your ~/.fluxbox/keys

Code:

Control F10 :ExecCommand "fbrun"

restart fluxbox (windows key + r)
then press ctrl-f10 to show the run dialog box

reference: http://forums.debian.net/viewtopic.php?t=5382&

kushalkoolwal · 07-28-2006, 08:31 PM

Quote:

restart system to console. then run fbset. take note of the mode and enter the values to /etc/fb.modes. if the mode already exist, just comment it with '# ' then enter the new values below it.

Yes I entered the new values which I got from fbset

Quote:

now restart the system again so that fb.modes is surely loaded.
try 'fbset <mode>' in console. nothing should change to your monitor.

Yes the screen did not change. May be I am getting on to somethig....(atleast I think so)

Quote:

then run x and try the old procedure with the mode.

grrrrr....There goes my screen OUT OF RANGE again. Exact same behaviour. When I switch back to Fluxbox by Ctrl-Alt-F7, I get this at the terminal:

Code:

Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven

Opening frame buffer device `/dev/fb0'
Reading mode database from file `/etc/fb.modes'
Using video mode `1024x768-76'
Setting video mode to `/dev/fb0'

Yes I did run the command "chvt 1; fbset...." from the Run Dialog box as you had suggested.

Well, is there anything I can do to solve this. We all have come this far and I really don't want to give up at this stage....

Again thank you very very much. Appreciate your efforts. Long Live Linux and people like you.

konsolebox · 07-28-2006, 08:42 PM

oh well i failed.

. i'll try think of another solution. meanwhile.. have you tried raskin's idea?

raskin · 07-29-2006, 01:46 AM

Did you try my modification - blind run for fbset?
Of my ideas - I said plenty... SVGAtextmode, svgalib app, another X with vesa driver.

kushalkoolwal · 07-29-2006, 03:42 AM

Quote:

Originally Posted by raskin

Did you try my modification - blind run for fbset?
Of my ideas - I said plenty... SVGAtextmode, svgalib app, another X with vesa driver.

Yes I tried the blind run but did not work.

Now I think I will try the svgalib first and then SVGAtextmode. Even if they don't work then I think I will use the vesa driver...