Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I m trying to boot the 2.6 kernel on the DB1500 board that has the AU1500 MIPS processor.
When I built the kernel, a separate folder called usr was created that has the initramfs_data.cpio.gz, initramfs_data.o, gen_init_cpio (elf) and other files...
Now at the YAMON prompt, I dont know what bootargs to give for this compressed initramfs, for the root= arg.
Edit: sorry bout this but i guess i can be wrong about initramfs_data.cpio.gz. i'm not really sure but initramfs_data.cpio.gz can only a part of initrd. it's not really the initrd. to make the initrd, run
Code:
mkinitrd -o initrd-`uname -r` `uname -r`
Edit2: don't use 'uname -r' btw if you're installing a new kernel version.
Last edited by konsolebox; 07-27-2006 at 05:54 PM.
Now at the YAMON prompt, I dont know what bootargs to give for this compressed initramfs, for the root= arg.
you'll only need to specify here the real fs besides initrd that you're trying to boot. example 'root=/dev/hda1'. you can also add 'ro' to make /dev/hda1 mount read only. this is required when booting.
Thanks for your reply..
the thing is i m not using either grub or lilo..this is an embedded system..so my .config file doesnt have a root= entry..
so here is what i have: a boot loader called YAMON that can dnload the kernel image and take boot arguments and start the kernel accordingly..now upto kernel version 2.4, i could supply root=/dev/nfs and then give the location of the file system in nfsaddr=<server ip>:<path of fs> ..
but, i dont know how to do this with the new initramfs..
so far i ve tried the following boot args:
bootargs0 (USER) noinitrd
bootargs1 (USER) ip=xxx.xxx.1.xxx:xxx.xxx.x.xxx root=/dev/nfs
bootargs2 (USER) nfsroot=xxx.xxx.x.xxx:/tftpboot/usr_as/initramfs_list
Thanks for your reply..
the thing is i m not using either grub or lilo..this is an embedded system..so my .config file doesnt have a root= entry..
so here is what i have: a boot loader called YAMON that can dnload the kernel image and take boot arguments and start the kernel accordingly..now upto kernel version 2.4, i could supply root=/dev/nfs and then give the location of the file system in nfsaddr=<server ip>:<path of fs> ..
but, i dont know how to do this with the new initramfs..
so far i ve tried the following boot args:
bootargs0 (USER) noinitrd
bootargs1 (USER) ip=xxx.xxx.1.xxx:xxx.xxx.x.xxx root=/dev/nfs
bootargs2 (USER) nfsroot=xxx.xxx.x.xxx:/tftpboot/usr_as/initramfs_list
doesnt work!
ashlesha.
Evenin! I'm not all that familiar with embedded systems, but I have used NFS mounts and network booting and such. It may just be a problem with your kernel. There is an option in the 2.6 kernels to allow NFS as the root filesystem (I believe it lives in the filesystem section of the kernel config). From the sounds of your issue, this may not be enabled on your kernel. Other than that, your command line args seem correct assuming you aren't giving any typos when you type them on your actual system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.