Prev: state of the video driver nation (was: KDE Desktop Effects + Fglrx)
Next: nfs on new 13.1 inistall won't connect
From: Joseph H. Rosevear on 20 Jun 2010 03:42
Recently got Slackware 13.0. Was using 12.0. Found that the graphics
in 13.0 are flaky. intel driver gives graphics artifacts, especially
in Kde. vesa driver avoids this problem, but the supplied
xorg.conf-vesa needed files and modules sections tweaked. Don't know
if I did that right. Works OK now except that console switching causes
the screen to blank. Often necessitates a reboot. And the screen
resolution that I want isn't available it seems. Modes line:

Modes "1024x768" "800x600" "640x480"

Yet what I get looks like 640x480.

Screen also blanks sometimes after periods of non-use. Especially
annoying, because the blanking sometimes necessitates a reboot. Trying

noapic acpi=off

on the boot line and

xset s off
xset -dpms

from xterm. Don't know yet if that helps.

Wondered if 13.1 will help with the above? Would really like to use
the intel driver, but no graphics artifacts please. Or vesa driver,
but no crippling screen blanking please. Perhaps 640x480 resolution is
sufferable.
From: Henrik Carlqvist on 20 Jun 2010 06:06
"Joseph H. Rosevear" <joe(a)prune.hopto.org> wrote:

> Recently got Slackware 13.0. Was using 12.0. Found that the graphics
> in 13.0 are flaky. intel driver gives graphics artifacts, especially
> in Kde.

There were known problems in the intel driver at the time of the release
of 13.0. In an attempt to work around those problems there are a number of
alternate intel drivers included in extra/xf86-video-intel-alternate. If
you are lucky it might help to use one of those drivers.

12.x did not have these problems and it seems as if the problem now are
fixed as 13.1 no longer includes alternate intel drivers in extra.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root(a)localhost postmaster(a)localhost

From: Mike Jones on 20 Jun 2010 08:17
Responding to Joseph H. Rosevear:

[...]
>
> Screen also blanks sometimes after periods of non-use. Especially
> annoying, because the blanking sometimes necessitates a reboot.


TIP: Hold down Alt+PrintScreen and slowly type R S E C B S U B

If you're lucky, you'll end up at a command promt /before/ you complete
the sequence, removing the need to reboot to escape an xorg lockup.

If not, you end up with a reboot and nothing lost, right? ;)

??? Does anybody know the xorg.conf entry that avoids these lockouts?

Something about "null input", or similar? I forgot it!


Also...

# In /etc/rd.c/rc.M

/bin/setterm -blank 0

# In /etc/X11/xorg.conf

Section "ServerFlags"
Option "DPMS"
Option "BlankTime" "0"
Option "StandbyTime" "0"
Option "SuspendTime" "0"
Option "OffTime" "0"
EndSection


....does it for me on 12.2

This way leaves it clear for other things to use DPMS for manual screen
locking etc.

TIP(FWIW): If you "chmod nobody:users /usr/bin/xlock" each user that runs
xlock will get a prompt asking for a new user\xlock-specific password for
that user account (saved to $HOME/.xlockrc). A neat way to avoid using
the user's full password (and PAM!) to unlock, and allows a simpler
password just for this function, is so desired.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Joseph H. Rosevear on 20 Jun 2010 14:17
Henrik Carlqvist <Henrik.Carlqvist(a)deadspam.com> wrote:
> There were known problems in the intel driver at the time of the release
> of 13.0. In an attempt to work around those problems there are a number of
> alternate intel drivers included in extra/xf86-video-intel-alternate. If
> you are lucky it might help to use one of those drivers.

Where are they? I couldn't find extra/xf86-video-intel-alternate on
the first three 13.0 install disks or in my installed 13.0.

I did find them on the Internet, and I tried them. No joy.

> 12.x did not have these problems and it seems as if the problem now are
> fixed as 13.1 no longer includes alternate intel drivers in extra.

Thanks. I'll get 13.1.

-Joe
From: Joseph H. Rosevear on 20 Jun 2010 14:30
Mike Jones <luck(a)dasteem.invalid> wrote:
> TIP: Hold down Alt+PrintScreen and slowly type R S E C B S U B
>
> If you're lucky, you'll end up at a command promt /before/ you complete
> the sequence, removing the need to reboot to escape an xorg lockup.

Thanks. This might be useful.

> # In /etc/rd.c/rc.M
>
> /bin/setterm -blank 0

I haven't seen this one. I've been fiddling with xset. Looks like I
need to fiddle with setterm *and* xset.
>
> # In /etc/X11/xorg.conf
>
> Section "ServerFlags"
> Option "DPMS"
> Option "BlankTime" "0"
> Option "StandbyTime" "0"
> Option "SuspendTime" "0"
> Option "OffTime" "0"
> EndSection

I think I can do this with xset, but perhaps I'll do it your way. Does
setting the times to 0 turn off the option?

> This way leaves it clear for other things to use DPMS for manual screen
> locking etc.

Good idea.

-Joe
 |  Next  |  Last
Pages: 1 2 3
Prev: state of the video driver nation (was: KDE Desktop Effects + Fglrx)
Next: nfs on new 13.1 inistall won't connect