Hi all,
After a clean re-install of Kubuntu, I still have the same problem I had - see my previous thread:
http://kubuntuforums.net/forums/inde...opic=3085004.0
In the fresh installation, I tried adding "noapic" or "notsc" or "acpi=noirq" to the kernel boot line; with "acpi=noirq" I frequently get a good session, but not always; with "notsc" the system hangs at boot; with "noapic" I get no change.
Basically these are the symptoms of a "bad boot":
- Slow icon animations, which slow all the operations - when I open a folder on the desktop, or an application, I have to wait for about a second for the animation to complete before anything else happens.
- Accelerated 3D programs are terribly slow (I use the game Chromium for a quick check).
- There's a general "sluggish-ness" in the system. It doesn't seem very responsive.
- Movies in Kaffeine are "jerky", as if it skips a frame every two.
- The "nVidia" logo when X starts stays on-screen for a second instead of just for an instant.
The system is not really usable this way, it's really annoying.
With a "good boot" instead everything is quick and responsive.
With the "acpi=noirq" I usually get a good session, unless I leave my joystick plugged in during boot - that way I get a 90% chance of a bad boot.
So basically: the joystick can't be the culprit, because sometimes I get a good session with it being plugged during boot; and if I plug in after boot when I have a good session, the session stays good.
The "acpi=noirq" helps raising the chances of getting a good session, but not to 100% - I still get bad sessions, even with the joystick unplugged.
It doesn't look like it's a video driver problem, because when I have a good session, everything stays good until next reboot, and everything's very stable.
All my hardware is good - I repeatedly tested the hard disks and memory. And of course everything works fine with Windows XP (or at least, as fine as it can work with Windows ).
So what do you think... Is it a kernel problem? Or KDE? Or what else? What could I do to get rid of this annoying problem, which forces me to several reboots to get a good session to work with?
Thanks,
Cristian
After a clean re-install of Kubuntu, I still have the same problem I had - see my previous thread:
http://kubuntuforums.net/forums/inde...opic=3085004.0
In the fresh installation, I tried adding "noapic" or "notsc" or "acpi=noirq" to the kernel boot line; with "acpi=noirq" I frequently get a good session, but not always; with "notsc" the system hangs at boot; with "noapic" I get no change.
Basically these are the symptoms of a "bad boot":
- Slow icon animations, which slow all the operations - when I open a folder on the desktop, or an application, I have to wait for about a second for the animation to complete before anything else happens.
- Accelerated 3D programs are terribly slow (I use the game Chromium for a quick check).
- There's a general "sluggish-ness" in the system. It doesn't seem very responsive.
- Movies in Kaffeine are "jerky", as if it skips a frame every two.
- The "nVidia" logo when X starts stays on-screen for a second instead of just for an instant.
The system is not really usable this way, it's really annoying.
With a "good boot" instead everything is quick and responsive.
With the "acpi=noirq" I usually get a good session, unless I leave my joystick plugged in during boot - that way I get a 90% chance of a bad boot.
So basically: the joystick can't be the culprit, because sometimes I get a good session with it being plugged during boot; and if I plug in after boot when I have a good session, the session stays good.
The "acpi=noirq" helps raising the chances of getting a good session, but not to 100% - I still get bad sessions, even with the joystick unplugged.
It doesn't look like it's a video driver problem, because when I have a good session, everything stays good until next reboot, and everything's very stable.
All my hardware is good - I repeatedly tested the hard disks and memory. And of course everything works fine with Windows XP (or at least, as fine as it can work with Windows ).
So what do you think... Is it a kernel problem? Or KDE? Or what else? What could I do to get rid of this annoying problem, which forces me to several reboots to get a good session to work with?
Thanks,
Cristian
Comment