Phiebie, alioop,

I don't want to hijack this thread, but I'd like to point that I *did not* suggest that the OP switch to testing or unstable: in fact I explicitly said to said in post #6, to stay with stable and explained how to install a backported kernel. Then when the OP stated they wanted a newer kernel than what was in backports, I went to some effort in post #10 explaining how to build a newer kernel from source.

As far as I can see these are the only posts that actually provided anything constructive.

I don't know where you got the idea that I ever encouraged the OP upgrade: in fact that suggestion came from alioop.

Evo2.

True. I did suggest using Debian Testing. Which I do not believe would be any more difficult to master than Stable. AND the apps would be up to date. No need to over whelm a newbies with 'back ports' or 'pinning' or other kinds of exotic Debian options to get up to date apps. Especially when one has Testing/Squeeze to use. Which is, in my opinion, pretty stable.

Lets get this man's operating system up and running with the latest apps. That will keep him with Linux and hopefully in the Debian camp with the lease problems.

Back ports? Us old hands can relate. The young buck will be left in a fog. Lets wait until he's better versed in Debian for that.

sorry to be late in replying,actually i,m still sticky with Lenny stable after a lot of researches on the internet,any way i have installed the kernel version 2.6.30 as evo2 have explained just as a start and latter may be i,ll try to compile new kernel,so after booting via new kernel there was a lot of issues such as many modules failed to load and failed to start or to connect to X server and hence doesn't start KDE or Gnome desktops ,then i,ll provide you with the things i made.
the kernel that i installed via my apt-cach is :
linux-image-2.6.30-bpo.2-686-bigmem - Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
then the other images was:
linux-image-2.6.29-bpo.2-486 - Linux 2.6.29 image on x86
linux-image-2.6.29-bpo.2-686 - Linux 2.6.29 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.29-bpo.2-686-bigmem - Linux 2.6.29 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.29-bpo.2-amd64 - Linux 2.6.29 image on AMD64
linux-image-2.6.30-bpo.1-486 - Linux 2.6.30 image on x86
linux-image-2.6.30-bpo.1-686 - Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.30-bpo.1-686-bigmem - Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.30-bpo.1-amd64 - Linux 2.6.30 image on AMD64
linux-image-2.6.30-bpo.2-486 - Linux 2.6.30 image on x86
linux-image-2.6.30-bpo.2-686 - Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.30-bpo.2-686-bigmem - Linux 2.6.30 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6.30-bpo.2-amd64 - Linux 2.6.30 image on AMD64
so,as i mentioned i have installed the one that i saied about.

then,are there any suggestions?! and is there a possibility that if i compile a newer version of the kernel then the issues will be erased or no matter what is the version?
thx in advance.

Hi,

welcome back!


Hmm, these issues seem a bit strange to me.

Since, you say you don't have X (Gnome or KDE), you may find it a little difficult to perform all the diagnostics that I'd like to see the output from. So I'll just start by asking:

If you boot into the old kernel (you can select it just from the grub menu at boot time) do you still have these problems?

Sure there is a possibility, but I think the way forward is to try to workout what the current problem is.

Cheers,

Evo2.

Hello there!,
sure i can boot the system via the old kernel and get the old stuff.
i guess the next question will be about the dmesg output right?,then i can boot the new kernel and pipe the result of dmesg to a file and post it here if u request it.
GreetZ

I have no problems running Squeeze on my box
I made SqueezeBox from this very install I am writing from on e17!
http://linux.softpedia.com/get/Syste...86-53583.shtml


the rest are Lenny upgraded to lenny proposed updates/lenny & 1/2/debian backports
so they got Flash,etc
http://linux.softpedia.com/progMoreB...isX-31789.html

heres the debian sources.list generator
http://debgen.simplylinux.ch/

Sorry, can I laugh?

Testing is so unstable at the moment it could not even qualify for Experimental.

Tonight: suddenly my shift key didn't work anymore. Neither did SHFT-ALT-F1, etc. I had to reboot. GLX wouldn't work anymore. No KDE effects. Then again the SHIFT key not working in KDE, but SHFT-ALT-F1 did. In the console the SHIFT key worked which precludes a hardware error. I switched back and forth between console and X several times to confirm the behaviour. Suddenly X restarted. Then the SHIFT key was working again even in X.

This is just one example, I think I encounter something strange every day. Like no file extension attachment in OOWriter 'save as', no column resize in Krusader, no drag-n-drop of attachments in KMail, graphic effects random come-and-go in KDE to mention just a few.

jlinkels

From lurking in the #debian irc channels the past few years, I have noticed that testing is usually more "unstable" than unstable. Especially now with all of the kde4 issues.

That being said, backports.org usually has a newer kernel than testing.

If you do not want to mess with things not working then you run stable and use as few packages from backports.org as you absolutely need.

I run sid and I haven't been able to get an official Debian kernel to boot since 2.6.26, so instead I use a liquorix kernel and keep a sidux kernel installed in case something goes wrong.

That is weird, and contrary to the intentions of the Unstable -> Testing -> Stable chain. But you are not the only one or first one stating this.

I am running Testing on various machines since Sarge was testing and apart from some minor issues I never had any serious problems. The machine I am running Testing on now is at the edge of unusable, and I keep machine next to it on my desk running Stable. I would say most if not all issues are related with KDE4 and KDE applications.

I have to be honest and tell that despite of all these problems I do like the visual eye candy and effects on KDE4. No it doesn't become boring if you choose carefully some effects. Therefor I don switch back to Stable and KDE 3.5 on that machine.

Your recommendation would be to switch to Unstable? It can't get much worse, can it?

jlinkels

Yep, or just the contents on /var/log/dmesg.

Can you also please post the output of the following command with both the old and new kernels:
Cheers,

Evo2.

i,ve tried to boot the system again on 2.6.30 and i got the dmesg output that u can see via the attached files.
and i executed that command and got the following:
i hope that will help u figuring out the issue .
thx in advanced.

Attached Files

	dmesg-2.6.30.txt (52.5 KB, 15 views)
	var-log-dmesge.txt (38.8 KB, 10 views)

It seems that this is actually after booting to the 2.6.26 kernel. Do you have the output for the 2.6.30 kernel?

The var-log-dmesge.txt seems to be for the 2.6.26 and looks ok. dmesg-2.6.30.txt seems to be from the 2.6.30 and again everything looks ok.
From these files I can't even see a problem.

I guess I need you to find the log file that contains the errors that you see when booting the 2.6.30 kernel. Please have a look at the other log files to in /var/log/ to find one that contains the errors. Candidate files could be: messages, syslog and kern.log.

Cheers,

Evo2.

I realize that I'm digressing from the original post but...

I also find the opinion that 'Testing' is more unstable than 'Unstable' contrary. At lease contrary to my years of experience with 'Testing'. And I've never read that anywhere else.

I've been using 'Testing' since Etch. And if one waits just a few months after an Official Stable Release is posted before dist-upgrading, (like right now) 'Testing' is very stable. It certainly beats Sid/Unstable hands down. Which is always in turmoil.

I've played around with Sid/Unstable before - several times - and it's a real chore to maintain. Not so with 'Testing'. True, I would not suggest it to someone who really depends on their OS for work/business. What's the term? Mission Critical? For that Lenny/Stable is the proper OS to use. But as an everyday desktop, 'Testing is great.

I've never had any problems with any Testing version of Debian since it was Etch. As far as Squeeze, I had problems with the Grub2 version. I tried to manually bring it on line. If I had waited, as I did on my second install, it would have been easily done. As it is with all of Debian's normal app/program upgrades.

I see the original poster is now asking what to do next after installing a new kernel and how to address his NEW problems. So this is becoming an example of one problem piled on top of another. I don't know if this is the proper way to assist.

I would guess if one likes to shoot trouble all the time this is a perfect exercise. On the other hand, if one wants an OS with up to date apps/programs, it might not have been the way to go. Installing Testing/Squeeze would have been easier and more economical by far.

0 members found this post helpful.

So you are able to draw a conclusion based on the experiences of the OP in the is thread that it is better to upgrade from stable to testing instead of installing a backported package. WTF are you smoking?

Evo2.

Me too... apologies to the OP!

It has been stated more than once. Far more often.

I have been running Testing since Sarge was testing, which is comparable to you. But I have never seen a mess like this.

I repeated that statement (Sid is more stable than Testing) with a question mark, not as a statement. I appreciate other points of view.

Don't worry, my servers run Stable. Even my machines I have to work on run stable. I am running testing on my home machine on which I can afford to play around because I have more systems. I need to. I am not sure I mentioned in this thread, but last time I tried the .doc export filter was broken in OOwriter, the extension was not added to the file name, couldn't resize columns in Krusader, can't drag 'n drop attachments in KMail without typing out the complete path/filename, my quoted original message in KMail disappeared when I try to reply, one day my desktop effects work, the next day they don't, Quanta is not there (and who knows if it ever will) and some more I can't remember now.

The installer gives you decent choice which Grub to use so that is no problem. Also sometimes the kernel get upgraded during a dist-upgrade, breaking my video driver. But that is normal, if you track testing it is to be expected.

BTW, I realize many problems are induced by KDE4/QT4. Maybe you don't have that many problems when running Gnome or XFCE.

jlinkels