Mircea Ciocan <[EMAIL PROTECTED]> writes: > Cooker gurus, please help, > > For a while I was strugling with a friends Sony Vaio > laptop with Transmeta processor and some kind of crapified ALI > chipset that was dying at boot on Mkd 9.0 and cooker, now I was > able to recompile a 2.4.20 kernel de-ALIfied, mount the > network.img disk, replace the existing vmlinuz and generate a > small bootable CD from it ( to make thing crappyer this laptop > don't have a floppy, also and the CD-ROM is some kind of FireWire > that only leaves the network install path open), to our nice > surprise the thing booted OK and then failed to load the network > module ( 8139too) due the expected unresolved symbols.
The easiest way to solve those problems is to use "blank.img". http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/gi/docs/README blank.img is a blank boot image without a kernel nor initrd. this image can be used to generate custom boot disk (to use it: compile your custom kernel with everything needed compiled in the kernel, not as a module (loop.o, ext3.o if needed, usb stuff, etc) and put the "vmlinuz" on the blank.img, then boot on it) http://www.linux-mandrake.com/en/90errata.php3#blankimg > OK then I've mounted the network.rdz system image and > then abruptly stopped, the modules are compressed with some kind > of an archiver that I don't know and the archive extension is > .mar !!!, I've never heard of it, can a guru of you help me with > a indication or pointer to overcome that, we are anxious to see > that little noty with Cooker on it and #mdk-cooker is dead :( See my other mail :). -- Guillaume Cottenceau - http://people.mandrakesoft.com/~gc/
