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
recompilealthough 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