PDA

View Full Version : Why is everything so slow?



jak8charm
16th July 2004, 10:49 AM
I'm curious if others get the same speeds using fc2 that I do with a comparable system. I really wonder if it's the software, or I forgot to configure something, or what. These are the kinda speeds I get when trying to load programs in fedora.
openoffice- 43 seconds from the time I click it
konqueror- 11 seconds
firefox- 12 seconds.
tux racer- too slow to run it
Somebody suggested to me that it's my video card, but is that even used to accelerate all these programs?
Here's the exact specifications of my cpu at this link-
http://www.fryssupport.net/frys/gq6068a.cfm

If you don't want to click the link, here's the specs.
* CPU: Athlon 2400+
* Chipset: SIS 740
* Devices
o 3.5" 40GB HDD 7200rpm
o 5.25 52x24x52 CD-RW
o 5.25 16X DVD
o 6 in 1 card reader
* Memory: 256M DDR
* Case: ATX
* Power: 250W
* Operation System: Windows XP
* Accessories box
o Keyboard
o Mouse
o Speakers
* Features
o K7SOM+ 7.5A
o 10/100 Fast Ethernet and sound onboard.
o Modem
o PS2 mouse and keyboard, four back panel USB 2.0 port, 1 x parallel port, 1 x serial port, 1 x VGA connector.
o Windows XP Operating System.
o Manual.
o Quick set up sheet.


I'm totally at a loss here. Is it supposed to run that slow on these kind of specs? I was told that linux is fast, but 43 seconds to open a simple word processor is NOT fast.

Viro
16th July 2004, 10:56 AM
Something is definitely wrong with your setup. My guess is your RAM since i've got 1GB and konqueror loads in about 1 second, OpenOffice Writer in 20 seconds and Firefox in 3 seconds. All times using a watch.

Open Office loads slow on *all* platforms. Try running it on Windows to see if it loads faster than when you load it in Fedora. RAM plays an important role in performance. 256 MB really isn't enough to run Fedora with GNOME or KDE.

Just a quick note, become root in the console and type /sbin/hdparm -tT /dev/hda to see the speed of your harddisk. It could be that DMA isn't being enabled.

Pulka
16th July 2004, 11:00 AM
Something strange happened to me.

My fedora core 2 was working fine, and so suse 9.1 in another partition. Yesterday i turned on the computer and everything is too slow! It has been like this for two days. What happened?
I have 3 partitions, one with windows witch is working fine, and the others with linux began working like this.
The only thing i did was update amule, but after the update the system was working fine

kosmosik
16th July 2004, 11:27 AM
Something is definitely wrong with your setup.
I also think so... things that you (one who started thread) can do to generaly improve performance:

1] check hd access mode should be DMA and so on (/etc/sysconfig/harddisks).
2] turn off not used services - default instalation has a lot of this (man chkconfig).
3] use faster FS - f.e. reiserfs, probably few partitions (depending on FS character) with different settings for each - you don't really need access time parameter on dekstop's system /usr partition and so on... (/etc/fstab, yours FS manual)
4] change not frequently used (but used) services with lighter ones. f.e. CUPS (which is powerfull but also is a cow) with LPRng.
5] use lighter window manager, f.e. WindowMaker instead of bloated GNOME/KDE.
6] recompile kernel for your hardware (may be tricky, since Fedora's kernel is not vanilla/is heavly patched)
7] learn to use shell - it is much faster (not in system but user sense) than GUI apps usually...


Open Office loads slow on *all* platforms. Try running it on Windows to see if it loads faster than when you load it in Fedora.
well it will load faster on Windows than on Fedora since default Windows OpenOffice.org install turns on preloading of OOo (small icon that sits in tray and eats 22MB RAM) - on Windows OOo (by default) is already loaded when you run it. you can achieve it with Linux version also. but it involves some scripting. try (*FIXME*):

$ ooffice -plugin quickstart


RAM plays an important role in performance. 256 MB really isn't enough to run Fedora with GNOME or KDE.
it depends on setup. in my work I have workstations with 128MB running just fine with FC1...

Viro
16th July 2004, 11:43 AM
3] use faster FS - f.e. reiserfs, probably few partitions (depending on FS character) with different settings for each - you don't really need access time parameter on dekstop's system /usr partition and so on... (/etc/fstab, yours FS manual)

There are no independent, realworld benchmarks that show that reiserfs has a speed advantage over ext3. In fact, reiserfs is known ot have a much higher CPU usage than ext3, so i doubt moving to reiserfs will significantly improve things.



4] change not frequently used (but used) services with lighter ones. f.e. CUPS (which is powerfull but also is a cow) with LPRng.

Cool. I never knew that. I've always used cups. Will look into making LPRng work.



5] use lighter window manager, f.e. WindowMaker instead of bloated GNOME/KDE.


KDE is fine!! Don't diss my favourite DE :D.



well it will load faster on Windows than on Fedora since default Windows OpenOffice.org install turns on preloading of OOo (small icon that sits in tray and eats 22MB RAM) - on Windows OOo (by default) is already loaded when you run it. you can achieve it with Linux version also. but it involves some scripting. try (*FIXME*):

$ ooffice -plugin quickstart


My mistake then. I've not used WIndows in a long while and I've forgotten about this preloading thing. Thanks for the heads up.



it depends on setup. in my work I have workstations with 128MB running just fine with FC1...

Is that with a GUI? And do you run OpenOffice on it? I bet it must crawl when you do a decent desktop environment (no, WindowMaker doesn't count :p).

jak8charm
16th July 2004, 11:54 AM
hmm. Well, I tried seeing the speed of my harddisk..
Timing buffer-cache reads: 228 MB in 2.01 seconds = 113.62 MB/sec
Timing buffered disk reads: 24 MB in 3.14 seconds = 7.63 MB/sec

Could my kernel or the default services that are running really account for such slow speeds?

Varkk
16th July 2004, 12:30 PM
On my laptop, which has a 5400rpm drive from memory I get this. Run "/sbin/hdparm /dev/hda" and check is DMA is enabled,

/dev/hda:
Timing buffer-cache reads: 128 MB in 0.38 seconds =336.84 MB/sec
Timing buffered disk reads: 64 MB in 2.25 seconds = 28.44 MB/sec

Bana
16th July 2004, 12:44 PM
Sometimes it helps to go through dmesg (kernel output) line by line from the start to see if anything looks like a "Failed - Going to Compatibility Mode" or something like that, also make sure your hardware is being detected correctly. For your CPU check the output of
cat /proc/cpuinfo

You also might want to follow the guide for tuning your system here: http://ccrma.stanford.edu/planetccrma/software/tunesystem.html it covers things such as DMA and harddrive options.

jak8charm
16th July 2004, 02:19 PM
Looks like DMA is enabled.

I tried dmesg, and literally every single line said error.
and hardware is being detected too.

I was just comparing the specs to what it detects, in the terminal it says its an amd athlon xp 1800+, and the actual specs for the cpu is athlon 2400+. Is THAT what the prob is?

Bana
16th July 2004, 06:22 PM
Hmm, perhaps you could paste your dmesg for us to look at? Also, if it is seeing your chip as an 1800+ when it is a 2400+ that could be a significant problem, what does your BIOS see it at?

kosmosik
16th July 2004, 09:11 PM
There are no independent, realworld benchmarks that show that reiserfs has a speed advantage over ext3. In fact, reiserfs is known ot have a much higher CPU usage than ext3, so i doubt moving to reiserfs will significantly improve things.
well none of any benchmarks are realworld and trully independent. everything is dependent on measure methds... as for ReiserFS I don't want to rise a holly war. so just go on and check yourself. beside I haven't said "change to ReiserFS and everything will go blazingly fast!" - I've said that tuning FS, dividing it into different partitions for different purposes may speed up the system. f.e. use ReiserFS on /var and /home partitions since it deals very well with large amounts of small (~4KB) files, if you do large files editing (multimedia? DTP file serving?) use XFS since it does well with very large files, use ext2 as FS on /usr since that partiton doe's not change frequently and ext2 is very fast overall and so on... also you can tweak with FS parameters such as block size. it can speed up a system.


Cool. I never knew that. I've always used cups. Will look into making LPRng work.
I use CUPS with cups-lpd on print servers and LPRng on clients since it is much smaller and does the same (as client).


Is that with a GUI? And do you run OpenOffice on it? I bet it must crawl when you do a decent desktop environment (no, WindowMaker doesn't count :p).
well it is not a speed deamon but it works. stripped down system, with stripped down GNOME, OpenOffice.org, FireFox/ThunderBird, OOo not from fedora but from UX Systems (our local polish edition)... also FF and TB are custom compilations in polish...

imdeemvp
16th July 2004, 09:27 PM
1. power supply 250 watts for AMD 2400+ recommended is 300 and up!

2. some applications run slower in linux like open office...here 18 secs.

3. sis are not that fastest chipsets there is....i will suggest buying a used video card if possible from ebay.com will be good jump in video performance and i recommend something like ati rage xl 16mb or a voodo3 16mb they ran about $10 + $5 shipping.....

4. add more ram :D another stick of 256mb ddr (in your case it is probably a pc2100) you will see a big difference in some applications like open office....

5. open your terminal and type: free -m this command will tell you how much memory is being used by fedora and how much is free and then post it here

good luck :D

Viro
17th July 2004, 02:11 AM
5. open your terminal and type: free -m this command will tell you how much memory is being used by fedora and how much is free and then post it here


Free doesn't really report that you think it does. You'll always get a low amount of free RAM when using the free command, since it takes into accound all the files that are held in RAM as a cache. Free unused memory is such a waste anyway...

imdeemvp
17th July 2004, 06:23 AM
Viro, free -m does not really give the 100% info but it is close and can give him an idea the he needs more ram....and that was the point :D

jak8charm
17th July 2004, 03:44 PM
Here's the output from dmesg. well, most of it anyway. The forum won't let me exceed 10000 characters in the post. ?

[greenstar@localhost greenstar]$ dmesg
status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00

jak8charm
17th July 2004, 03:48 PM
the rest of dmesg.

hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x20
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete


Here's my output for free -m..

[greenstar@localhost greenstar]$ free -m
total used free shared buffers cached
Mem: 219 216 2 0 10 34
-/+ buffers/cache: 171 47
Swap: 996 242 753

cpuinfo

[greenstar@localhost greenstar]$ cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 1800+
stepping : 0
cpu MHz : 1500.662
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 2973.69

[greenstar@localhost greenstar]$

and /sbin/hdparm /dev/hda.

[root@localhost greenstar]# /sbin/hdparm /dev/hda

/dev/hda:
multcount = 16 (on)
IO_support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 16383/255/63, sectors = 80418240, start = 0

friez
17th July 2004, 04:57 PM
my suggest would be check for bad sectors. i got similar error on my hd before it crashed :eek:

hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0xd8 { Busy }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: ATAPI reset complete
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
to check for bad sectors due
e2fsck -cv as root and the drive has to be unmount for this to work

Bana
17th July 2004, 07:48 PM
You also might want to try running some smartd diagnostics on it
man smartd

jak8charm
17th July 2004, 09:21 PM
If the drive is mounted, will it not work at all? Because I'm getting this message:
[root@localhost greenstar]# /sbin/e2fsck -cv /dev/hda
e2fsck 1.35 (28-Feb-2004)
Couldn't find ext2 superblock, trying backup blocks...
/sbin/e2fsck: Bad magic number in super-block while trying to open /dev/hda


I'm going to take a look at that smartd manual in the morning, perhaps there's a set of options for the command that somebody here could recommend?
Sorry for all the questions, guys, once I get this fixed I'll be set. I'm really actually quite happy that the problem is abnormal, and it's not fedora that's slow, that makes me totally stoked to get it all worked out.

Viro
17th July 2004, 10:50 PM
What is hdd? Could you do a /sbin/fdisk -l and report the output of that? Something seems to be up with that drive if it keeps on reporting that error.

friez
18th July 2004, 02:32 AM
yes you have to do it in rescue mode

friez
18th July 2004, 02:33 AM
yes you have to do it in rescue mode :( is hdd a cdrom or dvd drive ? :eek:

pipecrawler
18th July 2004, 02:59 AM
Greetings

/dev/hda:
Timing buffer-cache reads: 2212 MB in 2.00 seconds = 1105.62 MB/sec
Timing buffered disk reads: 174 MB in 3.03 seconds = 57.40 MB/sec

This is fedora core 2 out of the box with 1 Gig Ram
Openoffice opens in 15 sec

Try more Ram

//P

jak8charm
18th July 2004, 12:13 PM
okay.
Disk /dev/hda: 41.1 GB, 41174138880 bytes
255 heads, 63 sectors/track, 5005 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 4877 39070080 83 Linux
/dev/hda3 4878 5004 1020127+ 82 Linux swap


Is there a set list of things that could have gone wrong with the drive that would cause it to act this way?

jak8charm
18th July 2004, 04:15 PM
I'm not really sure what hdd is, but I did start it up in rescue mode, and ran e2fsck -cv on /dev/hda1 and /dev/hda2, and neither said that there were any bad blocks.

I also got a look at what BIOS says when I rebooted as far as what it's detecting my system as, it also said 1800+, interestingly.

Varkk
18th July 2004, 05:14 PM
hmmmm....try checking if the correct FSB and multiplier for your CPU is set in the BIOS, I know of some people who had problems with their motherboard not automatically setting the correct parameters for their chips. Also the harddisk errors could be caused by the PCI bus running at the wrong frequency(caused by FSB running at wrong frequency) causing the IDE controller to run into problems.

imdeemvp
18th July 2004, 05:35 PM
the bios will tell you what brand of hard drive you are using.....enter the bios and check it out!

now if you have windoz installed use this link to test your pc online...it only works for windoz but it will tell you if you have any virus, malware, spyware, and hardware issues....

this is the link and you dont have to register do it as annonymous user:

http://www.pcpitstop.com/pcpitstop/default.asp

good luck :D

james_in_denver
12th October 2004, 02:43 AM
512 Meg ram on an AMD 2400, OpenOffice loads in 6 seconds.

How many daemons/background processes are you running?...

Some of those can eat up quite a bit of ram....

What other programs do you have open at the same time?...

imdeemvp
12th October 2004, 10:59 AM
to find out more about your system open terminal and type: top

james_in_denver
12th October 2004, 05:29 PM
Also, if you have an XP2400, and it's being detected as only an 1800, you need to change your FSB (front side bus) settings.

Please review your motherboard documentation, you might have to change a jumper and/or BIOS setting.

smfinley
21st November 2004, 07:49 PM
Also, to speed things up, you might try disabling ipv6. Add these lines:

alias net-pf-10 off
alias ipv6 off

to /etc/modprobe.conf

This will speed up DNS lookup time in some cases.

Also see: http://stanton-finley.net/fedora_core_3_installation_notes.html

smiler125
28th January 2005, 03:10 AM
Hi

I also have a ECS K7SOM+ motherboard and AMD 2400 CPU that showed incorrectly as 1.2 GHZ
I changed the CPU speed from 100MHZ to 133MHZ and this helped, but now shows as 1.8 GHz. I also tried changing other settings and also there doesn't appear to be any jumper settings to change that would help.

I have emailed ECS to ask them if this motherboard is able to run the processor at it's correct speed, or weather it's not fully compabible with the AMD XP2400- however they have not bothered to respond.

Can anyone advise me on this

Thanks

tk
28th January 2005, 03:14 AM
jak8: actually 1-2 lines would have been enough to describe the problem ;) you should look into the smart tools / smartd as it looks that your HD has some serious problems or will have soon. smartd might tell you what exactly is wrong with it.

mrtaber
28th January 2005, 03:59 AM
Well, all this talk of 'hdparm' got me curious. My otherwise fine SATA hard drives, however, cause hdparm to complain: HDIO_GET_MULTCOUNT failed: Inappropriate ioctl for device. No way for me to tell if DMA is being used or not...it does seem as though the kernel treats them as SCSI drives...

Thanks,
Mark

Galadan
25th February 2005, 07:45 PM
What is hdd? Could you do a /sbin/fdisk -l and report the output of that? Something seems to be up with that drive if it keeps on reporting that error.

heh...I actually know this one! If I'm not mistaken, hdd is the name of the hard disk as a whole, as in the entire physical disk. please correct me if I'm wrong.

Jasper7
20th February 2008, 07:02 AM
To Jack8charm,
just as VIRO said: get 1GB of DDR.
On my Dell 4600C that came with 256MB DDR it took 4.5 minutes from turning it on to get to the internet connection once I installed Fedora 8.
I tried to take out ip6tables, with no avail.
Then I ordered from 1stchoicememory.com 1 GB DDR / 400 MHz for $60, and voila - the whole start-up procedure shrunk to under 2 minutes.

marko
25th February 2008, 12:32 AM
Jasper:
You probably won't get much response from Jack8charm, he hasn't been on fedoraforums
since 2004 (that's the last activity stamp in his profile). This is a very old thread.

Mark