Suse 9.1 - Very..very slow

[linuxmad]

I've tried Suse 9.1 Pro on 3 machines.
The number 1) is a PIV 3 GHz with hiperthreading and 512 MB Ram, the number 2) a PIV 2.8 Ghz with 512 MB Ram and the number 3) is a PIII at 700 MHZ with 256 MB Ram.
Suse did well on number 1 machine, everything worked as it should and it booted with an SMP kernel. The speed was adequate. Everything poped up almost instantaneously apart from YAST that is a bit slow, still not noticeable enough.
The number 2) and 3) machines were so slow that it took ages to log in. They booted fast but It took me almost 2 to 3 or even more minutes to see the complete desktop running, and after that every application took ages to open, even a simple xterm.
Now, i've googled a bit and found out that in version 9.0 there were some people complaining about the same, and aparently some solve the problem by deleting the entry "desktop" in /boot/grub/menu.lst file or by disabling ACPI (acpi=off) at boot.
I have tried that and almost everything i could find to discover what was happening, even looking at "top" trying to find some lags but... nothing.
I know that number 3) is old and only has 256 mb Ram, still Fedora Core 1 runs on it at lightnig speeds not to mention Slackware.Number 2) is a new machine so... i can't really understand why.
Any ideas ???
Thank you!!!

[psi42]

Please post the last 50 lines or so of the following files:

/var/log/messages
/var/log/syslog
/var/log/XFree86.0.log
/var/log/debug

(Please attach as a separate file)

~psi42

[linuxmad]

Psi42, i tried to get the files you asked, however two of them where not there.
/var/log/syslog .... does not exist
/var/log/debug ..... does not exist

I managed to get the other two and they are attached,
Thanks.

[GaryJones32]

lots of things kind of misconfigured there
i'm not really familiar with -- perhaps others can comment


kernel: mtrr: 0xd6000000,0x2000000 overlaps existing 0xd6000000,0x400000

this is missconfigured processor type range registers
this controls i/o accross pci/agp yes ????
this may not be a problem cause i see later the video driver is dealing with this issue i just don't know -- never seen that before

May 14 10:34:18 dhcppc14 rcpowersaved: CPU frequency scaling is not supported by your processor.
May 14 10:34:18 dhcppc14 rcpowersaved: enter 'POWERSAVE_CPUFREQD_MODULE=off' in /etc/sysconfig/powersave/common to avoid this warning.

i guess turn that off like it says

May 13 13:52:43 dhcppc14 nscd: 2939: while accepting connection: Bad file descriptor
May 13 13:52:43 dhcppc14 nscd: 2939: while accepting connection: Operation not supported
May 13 13:52:43 dhcppc14 last message repeated 889 times

get that ! it says that message was generated 889 times in a row !!!!!!!
while you set there and wonder why your machine doesn't work
ncsd =(name service cache daemon)
if you are not running NIS aka(Sun Yellow Pages)
that is - one server with all the network config files
you don't need nscd so turn it off

that's all i see of hand
everything else looks ok
see if that nscd thing is the problem

[psi42]

and also theres...

May 13 12:55:16 dhcppc14 kernel: powernow:
This module only works with AMD K7 CPUs


Odd...?
Are you sure you aren't using a processor-specific kernel?



Oh, and it looks like you are using the "nv" driver for your nvidia card. Grab the nvidia proprietary drivers, that _will_ help.

~psi42

[linuxmad]

I will try all that next week, as the machine is at work.
Thnaks you guys;)

[mdwatts]

A misconfigured network (localhost etc.) can be the cause of very slow systems. Did you configure networking correctly during installation?

Check to see what services are running and disable/stop any you do not require.

[linuxmad]

I tried the pointed solutions and none of them worked so,... i decided to install again in the number 3 machine, but this time with ACPI off from the beguining and i decided to put the machine as a standalone machine with no NIS.
Guess what.... it worked. KDE now runs fast, still not as fast as in other Distros, and YAST appears to be a little slow also in particular in this machine, however i think that the initial problem was solved and at least i have a full desktop completely usable.
Thank you all for the tips.

;)