Good Work Man, keep up the fight. I am currently still in the planning stages of doing my own strip down and kernel recompile of Bering. I have been watching your mail exchanges and your success has been an inspiration. Thanks for the follow up post.
Eric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Adrian Stovall Sent: Wednesday, February 27, 2002 5:56 PM To: 'Brad Fritz'; Adrian Stovall Cc: LEAF (E-mail) Subject: SUMMARY?: [Leaf-user] newbie question (Bering/2.4/IDE) Whew! today was an adventure...I decided that I wanted to try to compile all the modules that I need/use into my own 2.4 kernel (ide, eepro, pci, etc). I grabbed the latest kernel source, put it on my old, rusty Pentium Pro 200/redhat 6.2 box, and followed the instructions in the readme (spent a while updating gcc and other packages that were a bit out-of-date in my distro). I used the bering.config as my starting point, and started changing m's, y's, and n's as appropriate and copied it as .config in the dir I untarred the kernel stuff in. I ran make oldconfig and make dep, made a bzImage, copied it to the HD of my router as "linux", etc...several hours and a few passes of syslinux later, I managed to get 2.4 to boot from the HD without having to include modules.lrp. Next up is some more slimming... I am a very happy man. If I can get the perl package to load successfully, I'll be a very happy man (and I'll work on getting a configuration utility I've been writing in perl to go). I want to thank everyone who responded...I may not follow everyones advice, but seeing the suggestions that people had made it easier for me to decide what road to travel. If I come up with any useful utilities, I'll be sure to let everybody in on it. -----Original Message----- From: Brad Fritz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 27, 2002 6:41 AM To: Adrian Stovall Cc: LEAF (E-mail) Subject: Re: [Leaf-user] newbie question (Bering/2.4/IDE) On Tue, 26 Feb 2002 14:48:09 CST Adrian wrote: > Hi all...I had successfully finished a previous install with a 2.2.19-IDE > kernel and run from a small IDE HD. Cool. > What I would like to do is repeat this with a 2.4 kernel (currently messing > around with Bering Beta4...no probs running from floppy). What do I need to > do to make this run from a hard drive? > > I'm hoping for something other than "compile a 2.4 kernel with IDE support > enabled", but I'll try to if I have no choice (severe lack of experience > with compiling a kernel on my own). Compiling a 2.4 kernel with IDE support using Jacques' kernel config [1] as a starting point shouldn't be too bad. For an alternative solution, read on... > Is there a 2.4-IDE kernel out there? Am I stupid, and there's some simple > config option to make the Bering 2.4 kernel boot from my HD? I recently setup Bering (beta 3) on a compact flash card plugged into an CF-to-IDE adaptor. I use the stock kernel with with the IDE modules loaded via the initrd image. This isn't necessarily easier than recompiling the kernel, but if you *really* want to avoid re-compiling the kernel, the procedure below should work. Disclaimer: This is mostly from memory, so there may be a few mistakes. I am also assuming the hard disk is /dev/hdc and is temporarily installed in a full-blown Linux system for installation of Bering. 1. Format a partition of your HDD with an MS-DOS filesystem as described in Charles' LRP Hard Disk HOTWO [2] or with the Linux fdisk and mkfs.msdos commands [3]. 2. Mount a copy of the Bering image somewhere convenient: mount -o loop /tmp/bering-1680-b4.bin /mnt/disk/ 3. Uncompress a copy of the Bering initrd.lrp: gunzip -c < /mnt/disk/initrd.lrp > /tmp/initrd 4. Mount the uncompressed ramdisk image: mount -o loop /tmp/initrd /mnt/initrd 5. Copy the ide-disk.o, ide-mod.o, and ide-probe-mod.o modules from the ide directory of Jacques' modules directory [4] to the mounted initrd image: cp /tmp/ide-disk.o /tmp/ide-mod.o /tmp/ide-probe-mod.o \ /mnt/initrd/boot/lib/modules/ 6. Add lines to boot/etc/modules of the initrd image to load the ide modules: echo ide-mod >> /mnt/initrd/boot/etc/modules echo ide-disk >> /mnt/initrd/boot/etc/modules echo ide-probe-mod >> /mnt/initrd/boot/etc/modules 7. Unmount the initrd image: umount /mnt/initrd 8. Mount the MS-DOS partition you created on the hard drive: mount /dev/hdc1 /mnt/newdisk 9. Copy all files from the Bering image to the new disk: cp /mnt/disk/* /mnt/newdisk 10. Replace the old initrd.lrp with the new one: gzip -9 < /tmp/initrd > /mnt/newdisk/initrd.lrp 11. Edit syslinux.cfg on the new disk and change the fd0u1680 references to hdc1. 12. Unmount the hard drive: umount /mnt/newdisk 13. Run syslinux on the hard drive partition: syslinux /dev/hdc1 14. Cross your fingers and try to boot from the new image. :) If you run into problems, setting the VERBOSE and DEBUG flags in /linuxrc (in the initrd file system) may help debugging them. > I'm running this on a Dell PowerApp Web 100 (single PIII-73/256MB/dual > EEPro100) and using Bering Beta4/Syslinux 1.66 on my HD. > > Any info is *greatly* appreciated. I've probably missed a few details here or there, but it should give you an idea for an approach that doesn't require a kernel recompile....although recompiling the kernel with IDE support is probably less work. ;) --Brad [1] http://leaf.sourceforge.net/devel/jnilo/bering/beta4/bering-b4.config [2] http://lrp.steinkuehler.net/Documentation/LRPHardDiskHOWTO.txt [3] I had trouble getting the mkfs.msdos created filesystem to boot correctly using syslinux, but it was probably due to an error on my part. [4] http://leaf.sourceforge.net/devel/jnilo/bering/beta4/modules/drivers/ide/ > TIA > > Adrian _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
