You are not logged in.

#21 2016-01-11 18:13:41

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,063
Website

Re: vesa and x-server issues

nitrofurano wrote:

sysrq+alt+b also doesn’t work

Edit the file at /etc/sysctl.conf and add this line:

kernel.sysreq = 1

You can also set this as a kernel parameter via GRUB to prevent you having to power cycle after changing the file.

Offline

#22 2016-01-13 07:44:15

ohnonot
...again
Registered: 2015-09-29
Posts: 5,592

Re: vesa and x-server issues

nitrofurano, please keep in mind that the problem you experience is a debian problem, not a bunsenlabs problem, since bunsenlabs' basis is debian stable.
so you might want to consider searching on debian forums, too.

there's also a remote possibility that your gpu cannot support your monitor, or has difficulties with it.

Offline

#23 2016-01-20 18:08:01

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

thanks, Head_on_a_Stick! (i guess that didn’t work, i’ll try later)
btw, ohnonot, which debian forums do you recommend?

anyway, that savage gpu was onboard, and due on these issues, i tried to connect a “NVIDIA Corporation NV36 [GeForge FX 5700] (rev a1)” (i found it around from an older desktop computer), and most of these problems (including reboot and shutdown, i wonder why) disappeared

the problem is that, as it is connected to a cinescope display (that Nokia 447zi 17inch), it is still not displaying 1400x1050 as used to do on Crunchbang, whatever without xorg.conf, or with the xorg.conf below (i tried that above as well, and nothing)

Section "Device"
  Identifier "Configured Video Device"
  #Driver "vesa"
  Driver "nvidia"
EndSection

Section "Monitor"
  Identifier    "Configured Monitor"
  Horizsync    30.0-72.0
  Vertrefresh  50.0-120.0
  modeline  "1400x1050@60" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
  modeline  "1280x960@60" 102.1 1280 1360 1496 1712 960 961 964 994 -hsync +vsync
  modeline  "1024x768@60" 65.0 1024 1048 1184 1344 768 771 777 806 -vsync -hsync
  modeline  "800x600@60" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
  modeline  "640x480@60" 25.2 640 656 752 800 480 490 492 525 -vsync -hsync
EndSection

Section "Screen"
  Identifier "Default Screen"
  Monitor "Configured Monitor"
  Device "Configured Video Device"
  DefaultDepth 24
  Subsection "Display"
    Depth 24
    #Modes "1400x1050" "1280x960" "1024x768" "800x600" "640x480"
    Modes "1400x1050@60" "1280x960@60" "1024x768@60" "800x600@60" "640x480@60"
  EndSubsection
EndSection

(this nvidia gpu has a svga (where is it connected), dvi and s-video connectors, but i guess this shouldn’t be the issue causing that)

any idea if there is something wrong in this xorg.conf? (or should we mention that famous Torvald’s quote “nvidia fxxx you”? big_smile )

(thanks a lot in advance!)

Offline

#24 2016-01-20 20:19:46

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

i tried now to follow this information - http://www.arunviswanathan.com/node/53 - and i can get 1400x1050 60hz working fine - weird is that i used to be able to do that by editing xorg.conf only - and using xrandr seems far more toilsome

Offline

#25 2016-01-20 20:50:42

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

having this at /etc/profile.d/xrandr.sh seems to work:

#xrandr | grep maximum
#gtf 1400 1050 60

xrandr --newmode "1400x1050_60.00"  122.61  1400 1488 1640 1880  1050 1051 1054 1087  -HSync +Vsync
xrandr --addmode VGA-1 1400x1050_60.00

xrandr --newmode "1280x960_60.00"  102.10  1280 1360 1496 1712  960 961 964 994  -HSync +Vsync
xrandr --addmode VGA-1 1280x960_60.00

xrandr --newmode "1152x864_60.00"  81.62  1152 1216 1336 1520  864 865 868 895  -HSync +Vsync
xrandr --addmode VGA-1 1152x864_60.00

xrandr --output VGA-1 --mode 1400x1050_60.00

Last edited by nitrofurano (2016-01-20 20:55:48)

Offline

#26 2016-01-20 21:43:02

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

(oops, /etc/profile.d/xrandr.sh only works on Lubuntu (i thought i was testing it on BunsenLabs, not Lubuntu! big_smile ), i wonder why isn’t that working on BunsenLabs... :S )

Offline

#27 2016-01-20 21:46:04

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,063
Website

Re: vesa and x-server issues

Call the script from ~/.config/openbox/autostart instead.

Offline

#28 2016-01-21 05:51:34

ohnonot
...again
Registered: 2015-09-29
Posts: 5,592

Re: vesa and x-server issues

Offline

#29 2016-01-21 14:16:08

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

Head_on_a_Stick wrote:

Call the script from ~/.config/openbox/autostart instead.

doing only this is very counterproductive because it will only affect openbox, and only on the current user (i wanted to do it for all users and all window managers) - the fact is that i use a lot of different window managers (depending on my mood! big_smile ), and have to add it on all window manager config files for all users is quite toilsome

and btw, i found a bug on BunsenLabs: nothing inside /etc/profile.d is automatically executed - i had to run "bash /etc/profile.d/xrandr.sh" from a terminal

is there somewhere we should edit for allowing all scripts from /etc/profile.d/ ? and will be this bug fixed in the next BunsenLab installers and netinstall-scripts? this would be really great! smile


yes, i still use such old hardware! big_smile (planned obsolescence isn’t for me, at all! big_smile)

Last edited by nitrofurano (2016-01-21 14:17:24)

Offline

#30 2016-01-21 14:41:29

damo
....moderator....
Registered: 2015-08-20
Posts: 6,734

Re: vesa and x-server issues

^ If you think you have found a bug, coud you start another thread for it, with an appropriate title? Otherwise it may not be noticed wink


Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt  «» BunsenLabs on DeviantArt

Offline

#31 2016-01-21 18:06:25

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,063
Website

Re: vesa and x-server issues

nitrofurano wrote:
Head_on_a_Stick wrote:

Call the script from ~/.config/openbox/autostart instead.

doing only this is very counterproductive because it will only affect openbox, and only on the current user (i wanted to do it for all users and all window managers) - the fact is that i use a lot of different window managers (depending on my mood! big_smile ), and have to add it on all window manager config files for all users is quite toilsome

Well use /etc/X11/xorg.conf.d then.

I have already linked you to a guide earlier in the thread.

Offline

#32 2016-01-22 14:01:06

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

Head_on_a_Stick wrote:
nitrofurano wrote:
Head_on_a_Stick wrote:

Call the script from ~/.config/openbox/autostart instead.

doing only this is very counterproductive because it will only affect openbox, and only on the current user (i wanted to do it for all users and all window managers) - the fact is that i use a lot of different window managers (depending on my mood! big_smile ), and have to add it on all window manager config files for all users is quite toilsome

Well use /etc/X11/xorg.conf.d then.

doesn’t work... :S

I have already linked you to a guide earlier in the thread.

where?

Offline

#33 2016-01-22 18:09:28

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,063
Website

Offline

#34 2016-01-23 12:32:38

nitrofurano
Member
Registered: 2016-01-09
Posts: 43
Website

Re: vesa and x-server issues

Offline

#35 2016-01-23 12:40:26

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,063
Website

Re: vesa and x-server issues

Does it work now?

If so, please add [SOLVED] to the thread title to help others who have this problem wink

I'm going to move this to GUI & Applications as it is an EDID issue rather than a bug with Debian/BL

Offline

Board footer

Powered by FluxBB