SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i've come across a strange problem just recently. whenever i try to change to another console (e.g. CTRL+ALT+F2) OR i want to close X my pc is dead. like in windooze. well, i didnt have this problem some time ago, so i tried out to disable the experimental r200 (radeon chip) DRI support by putting # before the lines Load "GLcore", Load "glx" and Load "dri" in my XF86Config file. it didnt do nothing. same problem. i wonder if there could exist a linux program that does something like this because of bad memory handling or whatsoever or even my kernel. i get no error messages from any possible file in my /var/log/. any suggestions?
my sys:
athlon tb 1400/256mb infineon ram/80gb 7200rpm ibm hdd/radeon 8500 agp gc
i use window maker as window manager on xfree 4.2.0.
You might want to check the /var/log/XFree86.0.log file at the beginning to verify the exact XF86Config file in use.
If you are running in run level 4 try CTRL-ALT-F6 for the terminal screen. Run level 4 only has one console available on tty6. To deteremine run level try "ps -P 1" at a console prompt. I think the level would be indicated inside the square brackets (3 or 4).
If run level 3 then you should have six tty consoles available. If the console is working and you switch back to X and it is locked up, try CTRL-ALT-BKSP to restart the X server.
In either case, if you can switch back to the console or after you are able to recover, then try "tail ~/.xsession-errors" and see if there are any recent errors that might indicate the problem. If you have a functioning console you could also check the output from "dmesg" while X is locked. Perhaps you might locate something to indicate where to look.
If you are unable to detect any thing else as being related to the problem try a different video adapter if possible. Others here may post more information that might help in regard to the Radeon. I use run level 4 and switch to tty6, and then back to X without any problems. I have the ATI XPert 2000 AGP video.
Distribution: Slackware 10, Fedora Core 3, Mac OS X
Posts: 617
Rep:
from the sounds of it (your keyboard locking) you have a hard lockup. This could be hardware related (something screwed with your card) but is most probably something wrong with the driver that X is using.
Try looking on the Xfree86 website for problems with this card's driver.
If there is a newer version of X then you could try that, see if the problem clears up.
If that doesn't work then you could try, for the time being, using the framebuffer device. This works with most cards (definately yours) and will bypass these driver issues. If it works with this then you will know that it is related to the driver or the card (unlikely) and not another program (the kernel or something).
This might be laborius though to get the framebuffer working.
btw, do you use mozilla at anypoint? What windowmanage/XFree86 version? it is possible that one of these might be locking it up (mozilla always does for me).
thx for the help again. my system specs are listed in my post .
the most probable thing ist the r200 experimental driver. i tried to turn it off, but i think the install substitudes the standard xfree 4.2.0 radeon.o and radeon_drv.o with it's own and that can only be bypassed by uninstalling the driver or reinstalling xfree. i'll let you know
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.