SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Click Here to receive this Complete Guide absolutely free.
I just read about xorgsetup, and when I ran it had completely forgot about kdm running in f7 (I was in console in f6 I believe). It worked fine, and I hit "yes" to "Rename old xorg.conf file to xorg.conf.backup". The next step told me it was running, and created an error-file it told me to remove when I next started it up.
Now when I attempt to log into kde (The graphical login works) it tells me it doesn't have write access to $home/flux and xserver won't start.
When I decided to run "startx" it came up with a huge list of errors. I'm not entirely sure what to do now, short of just reinstalling X and KDE from the installation cd's.
I just went in with a MEPIS livecd and there's no xorg.conf.backup like it said there would be, and the xorg.conf seems fine regardless. Now I have no clue why I can't get any kind of windows manager running, and just when I was close to actually getting my wireless working.
I can't really get logs of what happens (Not any way that I know of, if nothing else) so I can't exactly say what happens.
When I boot up - It goes into KDE's graphical login. I use Ctrl+Alt+f6 and go into the console.
When I run "xorgsetup" I end up with:
"Fatal Server Error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock and try again.
Which was my initial error. I'm assuming that's because Kde's login is still open on f7. I'm not sure how to close that, and run xorgsetup properly.
Also - I'm not really sure what it means by no write access to $home/flux
Su to root after Ctrl-Alt-F6 and enter use the init command to enter the mode for multiuser w/o X. I don't know what Slackware uses for that Run Level, but the comments in /etc/inittab will tell you. It's the equivalent of init level 3 on other distros.
I went in, changed the inittab to runlevel 3 and ran xorgsetup. It only gave me one option - That of color depth and then said it was finished. I'm not sure why it didn't do anything else, but whatever.
When I rebooted and tried to login via kde's login, I get the same error. The little window that shows login process will show up, but stop at interprocess communication (the first graphic) and a message about no write access to $home/flux.
I'm not entirely sure what this actually means, and I don't recall ever changing any kind of permissions. I really wish I hadn't have run xorgsetup. Ahh well, live and learn. If I could fix it, it would probably be much better than a reinstall, though if necessary I would (I have doubts it would be necessary regardless).
I'm wondering if there is a problem with your home partition. When linux boots up originaly the partitions are mounted read-only and are checked for errors. If there is a problem at that stage, perhaps they are still mounted read-only. Other than that, you will need to look in the Xorg.0.log and find out if there are any problems indicated there.
Also, if you log in as root, can you run startx successfully? If you changed to a non-graphical init level, you shouldn't have seen a graphical log-in screen. Please check the comments on the /etc/telinit file, because Slackware's init levels may be different. On my system, 3 would be correct for this mode. 5 is for the graphical login.
You can use the init or telinit program to change to the runlevel you want instead of editing the telinit file.
I went in, changed the inittab to runlevel 3 and ran xorgsetup.
tht wil work only when u reboot after changing inittab
if u r runnning x or any x application tht means u r in run level 4, for going to run levl 3 without rebooting try "telint 3" as root
When I rebooted and tried to login via kde's login,
how came u end up with kde login if the sytem run level is 3 ??
u wil be in a text mode only at tty1(if ur default runlevel is 3), u have to manually start the x server by giving the "startx" command, and u wont see any kde login window(kdm) or gnome (gdm)or xdm
i asked u to try "telinit 3"--> while u r in ur X
if u r getting graphical login that means u r in runlevl 4, so for best fixxing the x configuration, change the runlevel to 3 in /etc/inittab(if u r rebooting)
# Default runlevel. (Do not set to 0 or 6)
id:3:initdefault: ---->change to this if it is 4
I really wish I hadn't have run xorgsetup
dont b like this everything wil b right
what graphix card u r having (can u post the result of lspci)
I went in and reformatted Slackware (I entirely forgot to check this thread beforehand) but alas, the problem rose again. This time through I did a full install, formatted -every- Linux partition with a slow format and haven't run Xorgsetup/Xorgconfig. Yesterday I rebooted-shutdown (When I run "shutdown now" it will display the message but do nothing...), and when I attempted to boot it up today, I'm getting the same error.
It's a fresh install, too.
Edit: I forgot to note that my default Runlevel is 3, and KDE is my preferred Window Manager (until I get everything running stable, then I'll probably switch to Fluxbox).
It tells me it can't create an Xauthority file (it time-outs 3 or so times) and then attempts to run KDE regardless. KDE stops at the first login step and the error message is actually behind the KDE login. I'm assuming it's the same "No write access to $Home$flux, though.
I'm running a PIII coppermine, 256 mb of ram and Nvidia TNT Riva/Pro graphics card.
I'm actually fairly close to getting my wireless to working I believe, but given that I can't even log in or anything, it's a bit of a hinderence.
Any help appreciated,
Last edited by BloodiedMind; 03-08-2006 at 03:36 PM.
I don't think it's the graphics card, as I have run KDE on both installations fine for the first bit. When I reboot it seems to mess up with the
No write access to $home/flux.
I'm not sure why this is even happening, it might have been different if I had never been able to properly run KDE in the first place, but it randomly doing that is just irritating.
/$home/flux is on another partition, could that be a potential issue?
It also times out creation of a Xauthority file, which I assume is just because it has no write access.
Edit: Missed the part about using fluxbox or Xfce, I'll go try that in a minute and report back with what happens.
Last edited by BloodiedMind; 03-09-2006 at 04:30 PM.
xwmconfig won't even work, as X cannot create a directory on /home/flux, and so it will not run.
So I can't even attempt to use Fluxbox (which more than likely would not work, I would assume).
I am using Reiserfs on both my main partition and /home partition, if that would make any difference.