__/ [ nikoli ] on Monday 21 August 2006 06:45 \__
> Roy Schestowitz wrote:
>> __/ [ nikoli ] on Saturday 19 August 2006 19:45 \__
>>
>> > I have Suse 10.1 running KDE
>> > AMD x64 2500+ (2.2 GHz) w/ 512 RAM
>> >
>> > I also have about 40 gigs of mp3s on an NTFS partition... seperate hard
>> > drive actually.
>> >
>> > The issue I'm having is that amarok "skips" all the time. It seems like
>> > everytime I call up another process, the music skips. Starting Firefox
>> > can cause it to skip. Mostly it's larger tasks that cause the problem
>> > though... like installing software starting an online update. Not only
>> > is it a problem for amarok, but it seems like my entire system is over
>> > tasked during larger tasks.
>> >
>> > For instance, if I start "software management" in YaST, my entire
>> > system will become basically useless until it's done reading the
>> > package informantion... about 2 or 3 minutes! My mouse skips all over.
>> > I can't switch between windows, no music plays, etc. CPU usage is at
>> > 100% the entire time.
>> >
>> > So two questions:
>> > 1. Does playing music from an NTFS partition cause CPU overhead?
>>
>>
>> It should not. AmaroK (used to be) is buggy. I use version 1.2.x (old) and
>> it causes system-wide problems on occasions.
>>
>>
>> > 2. Is this just a limitof my hardware?
>>
>>
>> It sounds like there is something terribly wrong with the software, unless
>> there is some issue reading from disk (physical). It's very unlikely
>> though as it would not have affected the system in such a way. It would
>> have just spewed out an error and stop the reading operations. It's
>> probable to assume that some rotten process is running and causing the
>> issues. Try doing some profiling. System monitors, KSysGaurd,
>> gnome-monitor etc. (CTRL+ESC if you are using KDE... AmaroK seems to
>> sugget so).
>
> Well I don't know what it was but I just did an oline update and
> rebooted. Now everything is working VERY well. I would love to see what
> this thing can do with a gig or two of RAM!
Interesting coincidence: This morning I had some problem with AmaroK, again.
I woke up and AmaroK was 'fried'. Restart AmaroK and it hogs resources.
Restarting KDE did not help. Start YaST and it will take ages to get going.
Rebooting the box and everything was resolved. This afternoon, to make
matters worse, AmaroK's volume control was b0rked (not having an effect,
i.e. on/mute). I didn't try restarting arts, but I did try the aNode engine
to no avail. Then, restarted KDE, but also no good. I needed to reboot to
resolve this. It's very strange that AmaroK misbehaves more than it used to
(initially, this box had a fine uptime of 150 days and needed to be reboot
to revive the pilot daemon after that long period of time). That version 1.2
of AmaroK should still be considered a beta and not be included with SUSE.
XMMS is rock solid. Not enough function though...
|
|