FC13->FC14 64bit upgrade issue

[ObsoleteAcey]

I just upgraded my FC13 system (previously upgraded from FC12 without a problem) to FC14 using the full DVD upgrade and now have a curious issue: my computer is running in "slow mo".

My mouse and keyboard respond sluggishly, applications load slowly, windows swap slowly, even my screensaver is slow. If I go to another console session, it is also sluggish, even after I kill the X session with an init 3.

I tried video playback and although the video was a bit "stuttery" (it was only barely noticeable is a little more sluggish than normal) the sound was fine and stayed in sync with the video.

I've checked CPU usage and memory usage and it's all fine (in fact it's using less memory than it was under FC13). I'm at a loss... this happened the moment I rebooted my machine after the upgrade. I've done a full yum update and still have this issue.

My machine is a Core2 Quad 2.66gig with 3gigs of RAM, nVidia 9500GS.

Has anyone else had a similar issue or does anyone know what may be wrong?

[erroneus]

I am experiencing a similar issue. My machine ran comfortably on F13 and now that I have finally moved to F14, I am regretting it. The performance of compiz is abysmal. I can't say that keyboard and mouse is any slower, but the graphics are laggy. This is the same nvidia driver that I was using under F13 so I doubt that is the cause.

I am also noticing that the temperature of the nvidia chip is a bit higher than it was before the upgrade.

My machine just isn't that old yet -- It is a completely maxed out Dell Latitude D830 -- maximum options for everything -- RAM, video, HD, everything. And it was slick under F13. What could it be?

[ObsoleteAcey]

I'm unsure myself. Unlikely mine was caused by graphics driver. The first thing i did was rebuild my nVidia driver. This is when i first noticed it as the terminal was very slow responding to my keypresses. I am running KDE on mine.. it's not maxed out and the machine is 2 years old but it's pretty quick even by todays standards.

[erroneus]

Adding to the details, I decided to use the rpmfusion nonfree updates testing to update to a newer version of the driver -- still not optimal but about 25% better when rotating from one face of the cube to the next. The video chip is still running hot as well.

[William Haller]

On one work box I've upgraded to F14, I had to disable desktop effects in KDE to get a usable system after having everything working in F13.

[ObsoleteAcey]

booting back to kernel image 2.6.34.7-61.fc13.x86_64 seems to resolve the issue i am having.

Both 2.6.35.6-45.fc14.x86_64 and 2.6.35.6-48.fc14.x86_64 seem to have this issue

[hephasteus]

It's looking like memory compaction commits went well but all the graphics commits on 35 went pretty horrible. Maybe 14 will be good with .36 kernel.

[leigh123linux]

Originally Posted by erroneus

I am experiencing a similar issue. My machine ran comfortably on F13 and now that I have finally moved to F14, I am regretting it. The performance of compiz is abysmal. I can't say that keyboard and mouse is any slower, but the graphics are laggy. This is the same nvidia driver that I was using under F13 so I doubt that is the cause.

I am also noticing that the temperature of the nvidia chip is a bit higher than it was before the upgrade.

My machine just isn't that old yet -- It is a completely maxed out Dell Latitude D830 -- maximum options for everything -- RAM, video, HD, everything. And it was slick under F13. What could it be?

I pushed a compiz bugfix to updates-testing today, I doubt it will fix the performance issue .

http://koji.fedoraproject.org/koji/b...buildID=207035

Do you notice lag/no menu when right clicking on items in the notification area or window list?

[ObsoleteAcey]

anyone else having this issue? I'm still experiancing the "slow down" even on the latest kernel, so i'm still running my old F13 kernel

[erroneus]

Actually, no. I have been meaning to comment on it. Over the past few updates, the performance has been gradually returning. I wonder if debugging code was left in with previous versions of various libraries or something? Whatever the case, the display speed has returned to what I was comfortable with in F13.

[ObsoleteAcey]

Mine hasn't. The whole computer still feels like it's stuck in a bog. Something about those F14 kernels is no good. Maybe I will have to make my own and see if I can get performance back

[ObsoleteAcey]

Well it's been 4 months and I still have this issue with f14 kernels. It has gotten slightly better but still unusable. Has anyone at all had this issue?

Sent from my HTC Hero using Tapatalk

[erroneus]

My machines all run "normally" now. Whatever tweaks and optimizations that were done along the way have done the trick.

What hardware are you running? I recall long ago I had some issues with my computer where things would run too hot and the computer would just drop power. Turned out I had a hardware problem. Another time after that, I would get performance issues after running a little while... I somehow allowed dust to collect inside the laptop and it was affecting performance. (Eventually the dust/heat killed the GPU and the system board was replaced a second time... Thanks Dell! I'm glad I bought the warranty -- both failures were MY FAULT and they covered it. The first time I spilled apple juice on it, the second time it was excessive dust accumulation.)

In any case, I wonder if your problem isn't related to the hardware itself somehow or if it is just old enough to fall outside of some optimized driver code somewhere.

[ObsoleteAcey]

erroneus, I accidentally (as in it was the default boot option and i was out of the room after a reboot) booted to a FC14 kernel and now everything is... fine? I to must have gotten a fix in some updates in the last week or 2 that have fixed the problem.

Anyways, for the record I am using a Core2 Quad 2.66GHz, gForce 9500GS desktop. Had a recent dust clearout (about 2 months ago) which gave a significant drop in GPU operating temp.

[erroneus]

Nice. I am thinking I am due for another dust-out myself.