Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am trying to boot a ramdisk and am getting the following error:
16384 ram0 (driver?)
16384 ram181 (driver?)
No filesystem could mount root, tried:ext2 iso9660.
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (1,0)
This is RHEL5 so input the ramdisk_blocksize into isolinux.cfg:
APPEND initrd=initrd.img root=/dev/ram0 ramdisk_blocksize=1024 ramdisk=2969600 rw init=/etc/rc.d/rc.sysinit
normal ramdisk that erases all data on reboot. This system does not have a hard drive. The messages scroll by so fast that I can not tell if there are any errors before the 182 16384 ram0-182 (driver?) scroll by and it ends in Panic.
I am not sure I have ever heard of someone trying to boot to a ram disk like that.
You'd have to create it, format it and load the data to it before almost anything was loaded or configured. To even run a script you'd have to be up in linux. I guess you could then use loadlin or such to change command control to the ram disk.
You might be able to create it with memdisk and pxe or gpxe boot.
Since isolinux is very similar to pxe, both syslinux products, I believe it should work. I am trying to replicate what slackware does with their busybox ramdisk.
Slackware isolinux.cfg file:
append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw SLACK_KERNEL=huge.s
append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw SLACK_KERNEL=hugesmp.s
append initrd=initrd.img load_ramdisk=1 prompt_ramdisk=0 rw SLACK_KERNEL=speakup.s
I think I have found the problem. but will not able to test until tomorrow. I thought the kernel would create the ram0... devices dynamically. I am going to try and add the devices to ramdisk to see if that helps.
The system is booting from the DVD now. I change to a 64 bit version of the 220.127.116.11 kernel based on the Redhat 2.6.18 X64 config. The 32 bit version of the 18.104.22.168 was based on the RedHat 2.6.18 32bit config, so I am not sure what is different about the two kernels. I did a diff on the config files, but the amount of differences was huge.
Last edited by clcbluemont; 06-30-2010 at 12:31 PM.
All is working now under the 64 bit version of the 22.214.171.124 kernel. Using extlinux 4.0 for the flash drive version and isolinux for the DVD version. Still not sure what option was kernel option in the 32 bit version was missing to cause it to fail like that.