Hi, sorry for the cross post, put it is very important!

I've got a serious problem (it seem to be). I wanted to increase the speed of my
sata maxtor 120 hd on my Suse 9.0 system.
I read in this forum that the dma has to be activated, so I did that by typing:

hdparm -X66 -d1 /dev/hdg6 (its multiboot)

Then everything worked fine, my hd worked 10 times faster. But the problems arrose when I wanted to boot my system.

A lot of "lost interrupt" errors occur when my hd is been called. The last "lost intterrupt error" appears after the message of using_dma = 1.

I tried to boot (grub) with the options: nodma noapci and other things but nothing solves my problem.

It seems that the kernel overrides the boot options, because nodma means: using_dma = 0 right???

Is there someone who has experienced the same problems or someone who knows to solve it???

thanks in advance

I'm assuming you put the hdparm commands into a boot script somewhere ???
otherwise the drive should have lost the hdparm setting on reboot
or the lost interupts don't have anything to do with hdparm ??
i have read in forums where the s-ata drives need the hdparm commands
in rc.sysinit
right after
action $"Remounting root filesystem in read-write mode: " mount -n -o remount,rw /

but that's not first hand knowledge -- i believe hdparm was giving trouble on init otherwise
**edit** if it boots ok the safest thing to do is just set hdparm by hand after boot
if you need to turn stuff off you could try just
hdparm -d0 -a0 -u0 /dev/hdg
there during startup
also you might want to unmasqirq -u1 and see if that works better with the commands you are using
you might want to try -c1 as well

as far as the kernel is concerned it is possible for the kernel to be set to use UDMA by default i think -- also
there is a "use multi-mode by default" in "IDE, ATA " section you can say no or yes to (no might help)

also with those command in grub you specified device right like hdg=nodma

Yes, it working again using Suse Cd System Recovery.

The only thing I changed was the /etc/sysconfig/hardware file. This file is being referred to in the /etc/init.d/boot.idedma file.
In that file the parameters "/dev/hdg:udma2" has to be added instead of "", "/dev/hdgn" or "/dev/hdgff".

So my system boots again and my harddrive acts as a real sata drive..........finally:-)