How do you add Stabilized --hash to the initrd
Longtime reader, first time poster. I've recently installed RHEL 5.3, and found that it does not support Firewire with any of their "supported" kernels. I've built kernel 184.108.40.206, and am getting a kernel panic on boot. Comparing my working version of a kernel I built with the one that isn't working, I find the initrd of the working version has
stabilized --hash --interval 1000 /proc/scsi/scsi
while the non-working one does not. I have not been able to find anything that lets me know how to insert that line into the initrd file. Has anyone else run into this?
Get machine to boot from SW RAID
OK, figured out how to get the stabilized line in. I'm trying to boot from a SW RAID, and keep getting a kernel panic, with my kernel 220.127.116.11 build (selected this kernel since we are using it on another machine here). My kernel 2.6.18 build will boot with the RAID and works fine. I've compared the initrd*.img files, and the only differences now between the working and non-working version is the following lines are included in the working version:
echo "Loading dm-mem-cache.ko module"
echo "Loading dm-region_hash.ko module"
echo "Loading dm-message.ko module"
echo "Loading dm-raid45.ko module"
In the menuconfig, the "RAID 4/5 target (EXPERIMENTAL)" option is not available in the later kernel version. Otherwise, all my "multi-device support" options are set the same (although there is an option in the newer kernel for "Device mapper debugging support").
I'm running RAID 1, so it doesn't seem like the raid45 module is important, but it seems like the others must be the cause of this issue.
Anyone have an idea of how I can get this puppy running? Do I need a newer (or older) version of the kernel? Ultimately, we're trying to collect data with a firewire camera, and this has driven the change to the newer (unsupported by Red Hat) kernel.
|All times are GMT -5. The time now is 05:53 PM.|