Martin Pool wrote:
> sudo hdparm /dev/hda
Well the existing setting were not too bad:
/dev/hda:
multcount = 0 (off)
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 = 117210240, start = 0
> sudo hdparm /dev/hda -u 1 -d 1
I tried that, but it didn't make any noticable difference. I also
tried enabling 32-bit IO_support which seems to work OK, but still
doesn't fix the slow disk speed.
> I'm told dapper tries to auto-set these, but does so conservatively wrt
> firmware bugs. It may be too conservative in your case -- or it may be
> right and your machine actually can't do it. I have caused crashes by
> setting these but never lost data, but be warned.
I'm not going to fiddle with this too much further.
> So you can either just suffer, or set it by hand, or file a bug
> with hardware details to get the autodetection improved.
Since this didn't fix the problem, I don't think the cause is
hdparm related.
I think I'll go back to kernel 2.6.15-23-686 and get some dstat
results and then compare those results with what I'm getting with
2.6.15-25-686.
Cheers,
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"I don't think any MS Exec will ever die of old age. Satan
doesn't need the competition."
-- Digital Wokan on LinuxToday.com
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
