Hi I have created a mandrake custom install disk using blank.img, and a kernel I have built with patches to support my SCSI hardware. Does anyone know what features I should have in this ?? The problem that I was having the other day (Kernel Panic after boot disk found scsi controllers) was due to my not having included initd or ramdisk support in the kernel. I have rectified this, and can now install mandrake but.... I never put the module support in there so every time it tries to add a module it complains. I shall rebuild with the module support, but am I missing anything else. Also, my custom kernel is 2.2.16, 7.1 shipped with 2.2.15 and I assume the default mandrake boot kernel is also 2.2.15 - will by 2.2.16 boot kernel play ball with the modules from 2.2.15 ?? Also, once I have installed, I need to get a full version of my new kernel onto the box, as the MD default kernel has no scsi support (and certainly not the SCSI support for my 2.2.18 supported SCSI controller). What should I do?? can I build the new kernel, switch to another console (right after install) and copy it over the stock mandrake kernel, then hopefully reboot with the system picking up my new kernel?? And... 1 last question. I am building these kernels on my laptop, the boot drive for which is partition 9 (on an IDE drive) Hence before it links bzImage 3,9 gets shoved in the code as being the boot drive (which of course it wont be when it gets onto my new machine) I thought lilo was what identified the /boot drive, not having 3,9 hard-coded into the kernel? Regards Nigel
