To avoid these accidental kernel upgrades make sure to you don't install the linux-image meta pacakges (eg linux-image-2.6-686), since these will depend on the latest kernel.

Evo2.

I'm running Testing with the occasional package from Unstable on both my machines at home.
My main machine runs Fluxbox,and the spare runs Lxde.Both without problems.
So i'd say your assumtion regarding Kde4 is probably right.

My goodness, I didn't mean to start a firestorm. My apologizes to one and all if I stepped on anyone's toes. But I'm sticking to my guns: Squeeze/Testing is pretty damn stable. I'll even go so far as to say it's rock solid. I know, I know, that's a term reserved for Debian Stable. And rightly so. Still, Squeeze had not failed me since I've been using it. And neither did Etch/Testing nor Lenny/Testing. And I would guess, with the next Testing version, what ever that might be call - if I wait a few months before dist-upgrading - neither will it.

You know what makes Debian so stable? It's sticking to the appropriate sources. Once you start with the 'Backports', and 'Experimental ports' and the 'pinning' from Unstable and installing Sources packages, then it's not Debian Stable anymore. It ends up being a bastardized distro. And no, it's not that easy to keep up with.

And running Sid/Unstable is better? Get real. Now let me ask you: What have you been smoking? Even sudix is problematic. Sid/Unstable requires as much of an upkeep as sudix. And certainly more than Squeeze/Testing.

To get back to the original reason for this post, if this individual want's to use more up to date apps, programs and kernels with the least amount of problems, use Squeeze/Testing. If you want to go off the deep end, try Sid or backporting or pinning or whatever. But if you do, grit your teeth, girth your loins and be prepared to do a lot of work. 'Oh, all you have to do is open this config file and...'. 'Now do this and check that and delete this line'. Now cross your fingers and pray. Yeah, sure. Easy. No sweat. Don't give me that!

You know why I'm such a Debian advocate? It's because all it take is 'apt-get install xyz' or 'apt-get remove xyz'. And also because I'm lazy as hell. Why make it more complicated than that? Backports, pinning, Unstable, phfft! Don't need it. Don't want it. Not necessary. Never had to do this.

And in reply to evo2, I've stopped smoking that happy weed many years ago. When I had long hair. Hell, that was when I had HAIR! I probably wouldn't have stopped if it didn't get so expensive and I didn't have to take a drug test for my job. Now that I'm 62 and retired, I just might light up again. What the hell. Why not? I enjoyed it. Beats the hell out of the cheap beers I'm drinking.

Sorry, was Monday morning when I wrote that post... always in a foul mood on Monday mornings :-(

62 and retired. Sounds like a little farming - perhaps a herb garden would help keep you occupied ;-)

Cheers,

Evo2.

Start my own herb garden? I don't know if that's a good idea.

I can't be sure, but I think I've got a cop as a neighbor. So, I'll stay away from 'growing my own'. (Damn cops can't mind their own business!)

Even though I haven't had any weed for years, I do have fond memories. Damn it was nice getting high. Of course, it was just as nice running my fingers through my hair. And now I have neither!!! What the hell happened? Oh, I know. I got older.

the following files have been taken from var/log,check them out.

dmesg.0

faillog

kdm.log.1

lastlog

syslog.1

syslog.2.gz

syslog.3.gz

Xorg.0.log


the problem with the new kernel is that can,t connect to the X server,but the KDM exists in the systems processes.
by the way the last time i,ve tried the newer kernel i boot it in single user mode and i got the kernel panic message ,then the system stopped working..
thx for ur continuous efforts bro.
i forgot to say that no matter if any one talk abt smthn related to this sub.

I have problems with where the files are hosted. Can you please either upload them here or provide direct links to them?

Thanks,

Evo2.

Nice one. It may take me a little time to digest all though!

Cheers,

Evo2.

K take ur time thx anyway

I had a look at all your log files and there don't appear to be any references to the 2.6.30 kernel. Unless I missed something either you posted the wrong files or nothing is logged when you boot to the 2.6.30 kernel.

Evo2.