Xorg problem with Slack 13
Mike Jones
AMD Athlon 800 (An old Time box)
NVidia GeForce MX440 graphics card
Install goes ok.
Add user, log in as user, startx, get Xfce "Tips" with keyboard and mouse
locked out.
Hard reboot (pwr off+on at mains) (plus inevitable fsck)
This time, run Xorg -configure, run X -config /root/xorg.conf.new
Get black screen and locked up mouse and keyboard again.
Hard reboot etc.
This time run xorgsetup, and still get black screen plus lock up.
Hard reboot again, try xorgconfig, get "Command not found".
Last option = use xorg.conf from existing Slack 12.2 install on other
partition (using "nv" driver). Get black screen plus lock up again.
Hmmm. Something isn't quite right here.
Slack 12.2 installs and runs fine, and I've never had any problems with
this "old faithful" machine.
I did get Slack 13 to work with a different dual-core machine, but no
luck with the Athlon 800.
Any ideas folks?
--
*===( http://www.400monkeys.com/God/
*===( http://principiadiscordia.com/
*===( http://www.slackware.com/
Grant
>
>
>AMD Athlon 800 (An old Time box)
>
>NVidia GeForce MX440 graphics card
>
>Install goes ok.
>
[doesn't work]
>Any ideas folks?
Custom kernel, always works for me -- first thing I do after
new install is put in the latest -stable kernel, fine tuned to
the particular hardware.
With older hardware there's a swag of new kernel stuff can be
turned off.
Grant.
--
http://bugsplatter.id.au
Manuel Reimer
> Get black screen and locked up mouse and keyboard again.
Do you have hald running? The Xorg server in Slackware 13.0 has a silly
bug, which forces hald to be running, even if autodetect of devices is
disabled in xorg.conf...
I reported this and another bug (small patch for Qt, which makes KDE4
more stable) to Patrick, but no answer so far... :-(
CU
Manuel
Mike Jones
Hal is running, as per default install.
No KDE\QT stuff installed. All Xfce\GTK based, as usual for me.
The news there is a bug with such an annoyance adds to my suspicion I'll
be waiting until 13.2 to switch my systems from 12.2. Too many buggy
prototype things going on for my liking here, and I've wasted enough time
in the past chasing Xorg "developmental features".
Unless I'm missing something?
Leon Whyte
>
> AMD Athlon 800 (An old Time box)
>
> NVidia GeForce MX440 graphics card
>
> Install goes ok.
>
> Add user, log in as user, startx, get Xfce "Tips" with keyboard and mouse
> locked out.
>
> Hard reboot (pwr off+on at mains) (plus inevitable fsck)
>
> This time, run Xorg -configure, run X -config /root/xorg.conf.new
>
> Get black screen and locked up mouse and keyboard again.
>
> Hard reboot etc.
>
> This time run xorgsetup, and still get black screen plus lock up.
>
> Hard reboot again, try xorgconfig, get "Command not found".
>
> Last option = use xorg.conf from existing Slack 12.2 install on other
> partition (using "nv" driver). Get black screen plus lock up again.
>
>
>
> Hmmm. Something isn't quite right here.
>
> Slack 12.2 installs and runs fine, and I've never had any problems with
> this "old faithful" machine.
>
> I did get Slack 13 to work with a different dual-core machine, but no
> luck with the Athlon 800.
>
> Any ideas folks?
>
I have the nVidia video on my computer and had similar problems.
I went to the nvidia site and downloaded these:
NVIDIA-Linux-x86_64-185.18.36-pkg2.run
NVIDIA-Linux-x86-185.18.36-pkg1.run
I then logged in as root and ran:
sh NVIDIA-Linux-x86_64-185.18.36-pkg2.run
Using the appropriate file to fit whether I was running 32 or 64.
This fixed Slackware 13 for me.
--
A computer without Microsoft is like a chocolate cake without mustard.
< running Linux >
Mike Jones
I have the NVidia drivers already, but this should surely work with the
vanilla NV driver? Everything works fine on Slack 12.2, so there is
something about the Xorg in Slack 13 that has changed, and not for the
better by the look of it, as I recall similar glitches with Slack 11 on
one of my pooters (can't recall which one though).
Worth a go though, before I stick 12.2 back on that partition.
Mikhail Zotov
> NVidia GeForce MX440 graphics card
> Add user, log in as user, startx, get Xfce "Tips" with keyboard and mouse
> locked out.
>
> Hard reboot (pwr off+on at mains) (plus inevitable fsck)
> Any ideas folks?
Yep. Just add
Option "AllowEmptyInput" "False"
to the "ServerLayout" section of /etc/X11/xorg.conf
As far as I can tell, this is not Slack's fault but a change
in X.org
And there's no need for hard reboot if anything similar happens
next time. Hold Alt+SysRq and slowly press R S E I U B (without
blanks). Chances are you will see the prompt after "E".
--
Mikhail
Martin
> Add user, log in as user, startx, get Xfce "Tips" with keyboard and mouse
> locked out.
I had a problem with keyboard and mouse as well. It appears HAL or the
combination of HAL and xorg didn't like them. Since I have better things to
do than debugging cruft I simply disabled HAL in xorg.conf (following the
instructions in CHANGES_AND_HINTS.TXT).
Cannot help with the black screen, though.
Martin
Mike Jones
If losing HAL is what it takes, no problem. Its a pest application to me
anyhow. I'll give that a try tommorrow. Cheers!
Mike Jones
> On Tue, 20 Oct 2009 10:17:52 GMT
> Mike Jones <N...@Arizona.Bay> wrote:
>> NVidia GeForce MX440 graphics card
> ...
>> Add user, log in as user, startx, get Xfce "Tips" with keyboard and
>> mouse locked out.
>>
>> Hard reboot (pwr off+on at mains) (plus inevitable fsck)
> ...
>> Any ideas folks?
>
> Yep. Just add
>
> Option "AllowEmptyInput" "False"
>
> to the "ServerLayout" section of /etc/X11/xorg.conf As far as I can
> tell, this is not Slack's fault but a change in X.org
I fully expected it to be an Xorg glitch. Every time they do something
clever, things get snarled up until somebody prods them with a stick.
I mean, blame Slackware? C'maaaahn! ;)
> And there's no need for hard reboot if anything similar happens next
> time. Hold Alt+SysRq and slowly press R S E I U B (without blanks).
> Chances are you will see the prompt after "E".
Ah. Useful. Cheers!
Mike Jones
> Responding to Mikhail Zotov:
>
>> On Tue, 20 Oct 2009 10:17:52 GMT
>> Mike Jones <N...@Arizona.Bay> wrote:
>>> NVidia GeForce MX440 graphics card
>> ...
>>> Add user, log in as user, startx, get Xfce "Tips" with keyboard and
>>> mouse locked out.
>>>
>>> Hard reboot (pwr off+on at mains) (plus inevitable fsck)
>> ...
>>> Any ideas folks?
>>
>> Yep. Just add
>>
>> Option "AllowEmptyInput" "False"
>>
>> to the "ServerLayout" section of /etc/X11/xorg.conf As far as I can
>> tell, this is not Slack's fault but a change in X.org
>
>
> I fully expected it to be an Xorg glitch. Every time they do something
> clever, things get snarled up until somebody prods them with a stick.
>
> I mean, blame Slackware? C'maaaahn! ;)
>
>> And there's no need for hard reboot if anything similar happens next
>> time. Hold Alt+SysRq and slowly press R S E I U B (without blanks).
>> Chances are you will see the prompt after "E".
>
>
> Ah. Useful. Cheers!
Hmmm. Just tried the kill-HAL thing, no change.
Added Option "AllowEmptyInput" "False" as suggested, and now getting a
black screen and requiring a full RSEIUB reboot to get out of the lockup.
Bah!
Peter Chant
>
> If losing HAL is what it takes, no problem. Its a pest application to me
> anyhow. I'll give that a try tommorrow. Cheers!
>
But how will you open the pod bay doors...?
Daisy, daisy givveee mmmmmeeee yyyyyyyooooouuuurrrrr aaaaannssss....
Mikhail Zotov
Mike Jones <N...@Arizona.Bay> wrote:
...
> Hmmm. Just tried the kill-HAL thing, no change.
I have hald running (though I don't understand exactly why :-)
> Added Option "AllowEmptyInput" "False" as suggested, and now getting a
> black screen and requiring a full RSEIUB reboot to get out of the lockup.
Bad. On the machine I am posting from at the moment, I have an nvidia
MX400. xorg.conf reads as this (with just a few irrelevant parts
snipped):
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "AllowEmptyInput" "False"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
FontPath "/usr/X11R6/lib/X11/fonts/local/"
...
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection
Section "Module"
Load "glx"
Load "dbe"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc104"
Option "XkbLayout" "us,ru"
Option "XkbOptions" "grp:rwin_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
...
EndSection
Section "Device"
Identifier "Card0"
Driver "nv"
VendorName "nVidia Corporation"
BoardName "NV11 [GeForce2 MX/MX 400]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
...
EndSection
# EOF
Notice old-fashioned drivers for the mouse and kbd are used.
I recall I had problems when evdev was installed. Actually,
it is sometimes possible to have a good result _without_ any
xorg.conf file.
HTH,
Mikhail
Mike Jones
[...]
> Notice old-fashioned drivers for the mouse and kbd are used. I recall I
> had problems when evdev was installed. Actually, it is sometimes
> possible to have a good result _without_ any xorg.conf file.
I just tried a FULL install, jut in case I'd introduced any "bits
missing" glitches. I also tried each and every step mentioned already,
plus installing the NVidia driver. This barfed on GCC_4.2 built kernel
and GCC_4.3 actually installed. I ignored that warning, and got a barfed
up NVidia driver with warnings.
I'm getting a very strong sense of Slack_12.0 deja-vu here. (Had this
kind of fun with that too.)
Maybe I'll just stick with 12.2 until 13.2 is out, as there does seem to
be a bit of "rushed-out" buggy stuff in 13.0.
Thanks for the help guys. Its always appreciated.
Mike Jones
> Mike Jones wrote:
>
>
>
>> If losing HAL is what it takes, no problem. Its a pest application to
>> me anyhow. I'll give that a try tommorrow. Cheers!
>>
>>
> But how will you open the pod bay doors...?
>
I have access to power tools. >:)
Paul
Thank you, that option did the trick for me.