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.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Therein lies part of the problem/solution: HAL. Not your keyboard or anything like that.

I inquired about the very same issue a while back, and was told that one needed to configure the zapper in one of the enigmatic HAL configuration files (filename something like ridiculous.freedesktop.default.10.org.fdi.hal.fdi.10 :/) if it had already not been in there by default.

In my case, I have in my xorg.conf the three magic lines required to keep HAL the heck away from my input devices, so as far as that goes, CTRL-ALT-BACKSPACE doesn't work for me either, to my chagrin, and probably won't ever work again unless I bow down to HAL.

If folkenfanel's using HAL, make sure you've got everything up to date, and with HAL running and given full reign, as sakho says, the patch should make it work.

Do let us know if you get it working, and if anything weird was involved.

most everything works fine stock kernel with SIS760, except during a switch between users or end session, system hangs at a flashing cursor. no problem with a reboot or shutdown, just hangs up with a end session or switch user. running GXINE for playing a DVD has a bit of a glitch where i get herringbone distortion of the picture except when i use a small view window. if i upsize the window or go fullscreen, i get herringbone distortion of the picture, with the number of segments related to how much bigger the view is to the small stable window. in full screen it looks like a double image..... don't know if this has anything to do with xorg or the codec, haven't really investigated it much yet.

Intel 82865G and none of the drivers provided in slack-current worked for me.
I can't start x, it gets to the kde bootsplash and freezes there. i have to make a hard reboot.
This is with and without a xorg.conf
if i try to do telinit 4 it fires up kdm but then it accepts no input.
Hope somebody can help.

I hate to say this, but it appears as if the 82865 chipsets are simply not going to work with 13.0 :/ There's nothing we can do about it either, it seems -- there have been numerous reports of it not working, and I can't find any indication of anything we're doing wrong. If someone has the inclination the bring it up on the xorg mailing list, feel free - I'm subscribed there, so I'll participate as needed.

I hate to say this, but it appears as if the 82865 chipsets are simply not going to work with 13.0 :/ There's nothing we can do about it either, it seems -- there have been numerous reports of it not working, and I can't find any indication of anything we're doing wrong. If someone has the inclination the bring it up on the xorg mailing list, feel free - I'm subscribed there, so I'll participate as needed.

I re-installed Slack 12.2 and played around a bit to be sure the Intel driver in 12.2, and the machine, worked OK for me before I used Slackpkg to upgrade to 13. It certainly shows no sign of working beyond freezing after loading the KDE initialization screen, with either 2.8.0 or 2.7.1 (the earlier revs don't even get that far and 2.7.1 showed video glitches). My attempt to use a later kernel got me a bit further on (see previous) but it still froze up after being in the desktop for a bit. I didn't manage to recompile the drivers and the X server etc against the new kernel. Maybe it would help to use a later kernel with everything rebuilt against it - but that's not guaranteed and it would delay 13 quite a bit longer I expect. Have Fedora and/or SUSE - or any distro - got the 2.8.0 to work?

I Folkenfanel:
Do you mean that you have an intel 865 box and you can startx????
If so can you post your xorg.conf to compare????
I have that option in my xorg.conf and with the 2.7.99.901 driver at least kde starts but after loading the desktop it freezes..
Can you post your xorg.conf of that machine????
Thanks ind advance.

Hmm... I used slackpkg to upgrade to the latest -current packages today, and logging out of X seemed to stop working. When I log out of Xfce and TWM, I don't get KDM back. Instead I get a black screen with a blinking ASCII dash at the top left corner, which stays there forever. The HD light does not blink. At that stage, I can still switch to other virtual consoles. Pressing the power button initiates the shutdown sequence. However, CTRL-ALT-BACKSPACE does nothing when I'm at that point.

For the record, Xorg -current is working fine for me here. Just checked my update status via rsync and it's up to date (though I think it's relevant to mention I'm not running the stock 64-current kernel, but my 2.6.30.5 version). Also, I'm using the nVidia binary driver.

When I log out of Xfce and TWM, I don't get KDM back. Instead I get a black screen with a blinking ASCII dash at the top left corner, which stays there forever.

Did a few more tests. It happened every time I used kdm. It didn't make a different whether the wm was kde, xfce or twm. I also created a new user account just for testing this, but it didn't make a difference.

Logging out continued to work if I started X from the command line, though, and it worked if I used xdm instead of kdm. So I switched to xdm.

When I log out of Xfce and TWM, I don't get KDM back. Instead I get a black screen with a blinking ASCII dash at the top left corner, which stays there forever.

Hi, this might not be the same but I had a similar problem with Intel driver 2.8.0 and kernel 2.6.30 (without KMS). I "fixed" it by uncommenting line "TerminateServer=true" in /etc/kde/kdm/kdmrc (so kdm terminates the server process in the end of the session and starts another one for the next session). But then, every now and then, I had another problem that when I tried to log in (in kdm), the keyboard produced capitals when caps lock was off, and small letters when caps lock was on, and I could not type Enter at all. So I changed back to Intel driver 2.7.1 which has not shown this problem nor the session termination problem. Google found another report of the termination problem of Intel driver 2.8.0, which should only show on kernel 2.6.30 both with and without KMS and on kernel 2.6.29 with KMS but NOT on kernel 2.6.29 without KMS (like in Slackware current).