Ron Stodden wrote: > Thomas Backlund wrote: > >>Could you head over to >> >>http://www.iki.fi/tmb/Cooker/ >> >>and try my boot & fix disks >> > I tried it. > > Good news: > > 1. Replaced the hd.img floppy syslinux.cfg and vmlinuz with those from > your boot.img > You only needed the vmlinuz, but no harm done AFAIK
> 2. 9.1 installer now runs. Installation completed after adding your fix > floppy. > Nice! > Bad news: > > 3. Booting the new 9.2 installation passed the lilo selection screen > then said: > > "Linux too bigADBE" (or similar) > > and had to quit. (vmlinuz is 665,447 bytes). > weird... that's the boot kernel. You didn't modify the fix disk, or did you? the files for 13mdk after the fix is: vmlinuz-2.4.21-0.13mdk: 1,252,867 bytes System.map-2.4.21-0.13mdk: 582,951 bytes config-2.4.21-0.13mdk: 47,284 bytes the files for 13mdkenterprise after the fix is: vmlinuz-2.4.21-0.13mdkenterprise: 1,298,073 bytes System.map-2.4.21-0.13mdkenterprise: 587,748 bytes config-2.4.21-0.13mdkenterprise: 43,891 bytes and the mdsum for the images: e40d06ee7db6b7fceb7962bf611810c0 13mdkboot.img 64b4504bee188fe9acac94febcbc6c64 13mdkentfix.img 3df471f2423c01f4867350f1eb8ab8ff 13mdkfix.img > Any ideas? If you didn't change the fix disk, and you didn't copy the vmlinuz to the /boot partition maybe lilo didn't run... (could you try to rerun lilo) I used "installkernel" command that is supposed to know if you are uning lilo or grub and update accordingly, but I could of couse force the lilo install, but that would be bad if someone out there is using grub... Or should I just make this fix-images for MDK-installers that does not use grub (this is MDK default AFAIK) If I only could find a ftp host to put theese files on, it would be much easier to make all images available.. My own real homepage will be up for another week AFAIK... Thomas
