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.
Distribution: Usually Linux Mint, Debian, Ubuntu or CentOS
Posts: 234
Rep:
hiya
the log is in /var/log (boot.log and boot.msg amongst others)
the hanging problem is very very common, and altho i dont know the exact solution i fixed mine by erasing the .kde directory in my personal home directory. this will probably work if it is only ur user which is crashing, but u will lose a lot of ur desktop settings, so i wud recommend backing up any stuff in the .kde directory that is clearly ok and has an obvious purpose. obviously all ur shortcuts and files in ur home directory will remain untouched by doing this.
maybe u cud giv me a hand installing new kernels tho coz i tried once n screwed my whole pc up!! lol
Is there any better solution toward the KDE hang thingy.......
and btw, I have a problem with the lilo boot up after the kernel build........ is that lilo ignore the "vga" command, which set the screen ration.............
Distribution: Usually Linux Mint, Debian, Ubuntu or CentOS
Posts: 234
Rep:
not that i know of, its certainly the way i fix that problem whenever it crops up from time to time. why dont u just save rename the .kde file as .kde.old or whateva, then u can just copy whatever u want to the new .kde directory when kde automatically recreates it for ur user. that way ur settings wont actually hav been lost.
as far as lilo goes i dont really know as i use GRUB. whenever ive tried lilo its always screwed up.
I had a very similar problem. On log out I would get a blank screen but I noticed that the mouse cursor for "gpm" was still working when I moved the mouse. Apparently the display was showing a text screen.
The solution (link below) was to add "TerminateServer=true" to the "kdmrc file.
I had a very similar problem. On log out I would get a blank screen but I noticed that the mouse cursor for "gpm" was still working when I moved the mouse. Apparently the display was showing a text screen.
The solution (link below) was to add "TerminateServer=true" to the "kdmrc file.
It didn't work for me since I don't use kdm.. I start in runlevel 3.
Has anyone found a solution?
Skuzye
Does Ctrl Alt F1 or Alt F1 get you back to a shell console? I've had problems with some graphics drivers not properly switching back to a text display after shutting down X.
In some cases I've had to disable the frame buffer console and boot logo and in other cases I've had to use a different graphics driver in X or specify a different card/chip model to the driver.
Since you can type in "startx" and get back to a GUI it really isn't a hang. It's a problem with the displaying of the text for the console.
Does Ctrl Alt F1 or Alt F1 get you back to a shell console? I've had problems with some graphics drivers not properly switching back to a text display after shutting down X.
In some cases I've had to disable the frame buffer console and boot logo and in other cases I've had to use a different graphics driver in X or specify a different card/chip model to the driver.
Since you can type in "startx" and get back to a GUI it really isn't a hang. It's a problem with the displaying of the text for the console.
No, using Ctrl Alf F1 or whatever doesn't work. Well, my monitor stays like there's no signal at all, although I know the system is working because I can type "startx" and it comes to life.
I don't understand how boot logo or frame buffer console is related to the subject since this is gone after the system start up.
I can't use other graphics because I really need the 3D acceleration from fglrx.
No, using Ctrl Alf F1 or whatever doesn't work. Well, my monitor stays like there's no signal at all, although I know the system is working because I can type "startx" and it comes to life.
I don't understand how boot logo or frame buffer console is related to the subject since this is gone after the system start up.
I can't use other graphics because I really need the 3D acceleration from fglrx.
Skuzye
The frame buffer console sets a text mode for the graphics display and the frame buffer driver remains loaded. In some cases I've found that disabling frame buffer support avoids problems like this. That isn't necessarily a good solution for you but it might help determine if the frame buffer driver is a problem. You can install different frame buffer drivers for the console. I think the default one is VESA.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.