Philipp, Saturday, February 05, 2000, 5:57:38 PM, you wrote: PT> The cleanest way for 6.3 is: PT> - don't compile scsi support into kernel, i.e. use a standard SuSE kernel. PT> - add 'initrd=/boot/initrd' to the global section of /etc/lilo.conf PT> - add "aic7xxx" to the INITRD_MODULES = entry in /etc/rc.config PT> - call 'mkinitrd' PT> - call 'lilo' PT> next time you boot, all should be well. PT> Ahhh, I just had an insight. If you're using 6.3 and after install compiled PT> your own kernel, make sure that aic7xxx is *not* in INITRD_MODULES. If it PT> is, remove it and then run mkinitrd afterwards. It will detect that no PT> modules need to be loaded from the initial ramdisk and will delete the PT> initrd. Finish this off with calling lilo and your kernel with builtin SCSI PT> support should boot without problems. Is this why I have not been able to boot to a recompiled kernel in 6.3? I've tried compiling both sources from suse cd's as well as 2.2.14 tar ball. Boot stops, after going through most of the process including detecting the partitions, with: /sbin/init.d/kbd: /usr/bin/find does not exist. Exit. Then tells me to either bail with ^d or login and mount rw and fix it. Fix what? I have confirmed that 'find' is definitely there. Besides, I can boot to the standard suse kernel just fine. Suse is entirely on my sda disk and win98 is on hda. However, suse is booted from Boot Magic --> lilo. I have scsi support (ncr53c8xx) compiled into the kernel. I'm under the belief that since I'm booting to scsi I need to have support compiled in, not as module. Right? That's the way I've always done it. (IDE as modules though). CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_INITRD=y CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y CONFIG_BLK_DEV_SR=m CONFIG_CHR_DEV_SG=m CONFIG_SCSI_NCR53c8xx=y CONFIG_SCSI_NCR53c8xx_DEFAULT_TAGS=8 CONFIG_SCSI_NCR53c8xx_MAX_TAGS=32 CONFIG_SCSI_NCR53c8xx_SYNC=40 I'll try your suggestion above asap. Should I recompile without RAM and INITRD support? Never had such problems prior to 6.3. I seem to be having many other new problems but will start new threads for each. PT> Please give me feedback as it seems that maybe an SDB article is needed for PT> such problems. I have printed out the SDB article on the new boot process but either it wasn't very clear or I just misunderstood it. Is the purpose of this new process so that I can boot without scsi support compiled in and therefore save resources while not actually reading/writing from/to disk? Lastly, is there a way to redirect the failed boot mesg to a file? Seems that when I reboot the mesg file is over written. I haven't found the failed mesg anywhere in /var/log. Thanks, Tim, NJ mailto:tajcs@mindspring.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/