lol, very true, very true. Thx for all the help.

An update;

Sorry it took me so long to update this thread but I've been busy (I bet you all know what thats like). Anyways, so I got my ethernet card working and everything but on this kernel build I have two primary problems:

1) When X starts, the startup login screen shows up and everything and I can log in but a few seconds into the process (before anything pops up) I get and error box saying:

"Your session lasted less than 10 seconds. If you have not logged out yourself, this could mean that there is some installation problem or that you may be out of diskspace. Try logging in with one of the failsafe sessions to see if you can fix this problem.
View detailes in ~/.xsession-errors"

So like any good linux user I went to xsession-errors in my home dir and got:
"rm: cannot remove '.' or '..'
rm: cannot remove '.' or '..'
Not enough free disk space on /tmp"

I did a du on /tmp and got a size of 564kB.

I did not have this error in the last kernel build, so Im thinking it is a problem with me ommiting something I should have included. Or maybe it is a problem with xf86config (though I doubt it, i havent touched that is a while).

2) My second problem is an extension of the one unresolved problem to my origninal posting in this thread. Upon startup everything starts up the way it should and all is well. But on shutdown the following processes fail to shutdown (eg. I get a process_name....... [failed]"
a. xfs
b. sm-client
c. automount

xfs is on the list so I am thinking this maybe has something to do with my first problem (what is xfs btw???).

Anyways I'll look into these problems and keep this thread updated. I'm almost positivie that all I need to do is enable or diasable a few flags in my kernel config, the only problem is finding out which ones

Thanks alot to all that have helped and will help;
Movitto

Well, I can confirm that the times I was unable to login the way you describe, the issue was in fact lack of disk space; freeing up about 500 MB solved it-- though I must add that my /home is not a separate partition from /, so I can't tell you whether the 500 MB needs to be in /home or in / if /home is a separate partition.

However, given the problems you're having with /tmp, I'd guess / is the issue. So try logging in as root (that may still work under X) and deleting some files, or log in as root on another virtual console and use mc (Midnight Commander, you almost certainly have it) to delete whatever looks deletable, or to move some files to a different partition (meaning a mounted partition maybe on another drive), in order to free up some space in /tmp, or in fact anywhere on the / partiton.

If worst comes to worst, uninstall some stuff; you can always reinstall it later, when you have your space issue solved (this is only a temporary solution, after all; you need to start thinking about getting some more space anyway, as whenever you install new programs you've discovered or want to try, you will recreate this issue unless you change something now).

Not much help, but hope it at least clarifies the issue a bit.

Motub;

Believe any help is alot of help when it comes to me and linux. I will delete some stuff and see what happens (after all im running linux on a test box so essentially everything is deletable).
The funny thing is though that I can log into X using Gnome but not kde. Im not sure why this is, other threads have suggested it is corrupted kde startup files or such.

Anyways, I will keeps on working at it and see what I get thx alot.

motub;

Thanks alot, you were right. What happend was that I kept on backing up my old kernels when I went to build a new one. These kept on taking more and more disk space. So i went back and deleted all but the one that I use.

Thanks very very very very much (i owe you one, BIG time)

Movitto

deleted

Ok, I can't help you much. I am myself facing a couple of problems building the new 2.6.14.2 kernel. Here's what problems I am facing, maybe you can help me.

As far as your P.C. not shutting down properly is concerned :
Open up /etc/rc.d/rc.modules and uncomment the line that says /sbin/modprobe apm. This will enable the apm module to load. Shutdown/restart your computer (The first time you'll have to manually shut down the computer but after that it'll work fine.

Hope this helps!

Abit late now I think

lol yea. I've installed Linux on many machines by now. I absolutely love it! Anyways, thx once again for everyone that helped me in this post a year and a half ago (where does the time go, it just feels like yesterday!)

lol, yea quite late now didn't realize that, my bad. I was having a couple of problems installing the new kernel and when I was posting my thread, I found this thread in the similar threads section. I started reading through it but didn't realize that it was about a year and a half old.

These guys at LQ are great ! The amount of data they maintain is fabulus. Anyways thanks to everyone.