Maybe, and this is a longshot, it isn't grub at fault at all but a file that it points to. Which Suse exactly is it because I read there was a major error that was unoticed in 10.1rc4 I think and 10.1rc5 followed three days latter with the fix. -- Seek That Thy Might Know