I've recently installed suse 9.1 personal on a primary slave hard disk, I've got WinXP Pro on the primary master hard disk along with the MBR. Everything appeared okay at first, although loading the OS with GRUB was a bit erratic - sometimes it worked, sometimes it didn't.

I then did the full online upgrade. Everything appears fine, but now I cannot boot without DMA enabled. If I use the IDE=NODMA switch in GRUB, then everything loads fine. I can then re-enable DMA on the primary master (not much use seeing is that only has WinXP on it). If I try to re-enable DMA on primary slave (with suse on) it just locks up, exactly the same problem as when booting with DMA enabled.

I'm not sure what is happening here. As far as I know the primary slave hard disk is fine - before installing suse on it last week, it was a spare hard disk in Windows and DMA was fully enabled on it. In particular since the problem has really arisen since I performed the upgrade I suspect it may have something to do with that.

Any suggestions or ideas would be welcome, I really don't want to have to do a reinstall or try other distros.

Thanks

Flashy