I haven't had any luck yet doing this with a grub based machine. One machine I converted over to lilo -- and no problem, but then the suse default kernels wouldn't work right. Am I stuck with a choice between the two -- using the suse boot-loader grub and not being able to use standard kernels with no ram-disks, vs. booting from disk and but not being able to get suse to boot in a sane manner? I've gotten suse to come up under lilo (after some work) buit nothing was right -- disks were not mounted (but they were) no devices were mounted (though all disks were) root was initially read only... I just rebooted into a standard kernel and shelve it for the time. But I've another system that I'd really like to boot my own gen'ed kernel -- It's not that I can't have a ram disk for (whatever, but my builds usually don't need them -- I put the files I need to boot in my kernel.. Is there some 'gotcha'? Every time my kernel comes up it complains about not being able to find the console device -- had the same problem on the other system I converted to lilo -- and the problem went away -- so it's obviously something that grub needs to be told to pass to my kernel, I just am not sure what it is wanting... Thanks... _inda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org