Home > Cannot Open > Initramfs Cannot Open Root Device Null

Initramfs Cannot Open Root Device Null


There you can reconfigure and recompile the kernel (again described very well in the Gentoo handbook). Tools Insider University Program Groups Corporate Citizenship TI University Program Russian E2E (сообщество E2E) Japanese E2E (日本語コミュニティ) Learn E2E Launch Your Design Motor Drive & Control Videos More Cancel Linux Linux make oldconfig Set EXT4=y and any other filesystem modules (for some reason Slackware doesn't always enable it). I build kernel on Linux platform . his comment is here

Quote: create a new config file as /tftpboot/pxelinux.cfg/default NOTE: There are more options available such as MAC or IP identification for multiple config files see syslinux/pxelinux documentation for help. During boot, the kernel loads just fine but there is an error when the kernel tries to load the filesystem, shown below. It maybe romfs install problem. Reply With Quote 04-20-2011 #2 Lakshmipathi View Profile View Forum Posts Private Message View Articles Linux Guru Join Date Sep 2006 Location 3rd rock from sun - Often seen near moon

Vfs Cannot Open Root Device Or Unknown-block(0 0)

populate_rootfs... Please visit this page to clear all LQ-related cookies. chort View Public Profile View LQ Blog View Review Entries View HCL Entries Visit chort's homepage!

And then when I go to run my application, I get the following error: "insmod: error inserting 'cmem.ko': -1 Invalid module format". To me that screams of Gentoo not being able to communicate with the physical disk at all. And run "make" and "make linux image" again.

<{POST_SNAPBACK}> Hi Hippo thanks for reply ! Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Reply With Quote November 19th, 2006,08:35 PM #10 hippo View Profile View Forum Posts Altera Guru Join Date Oct 2005 Location Taipei, Taiwan Posts 1,667 Rep Power 1 Originally posted by

But I get this error message when it tries to boot: VFS: Cannot open root device "" or unknown-block(8,3) Please append a correct "root=" boot option Kernelpanic - not syncing: VFS: Vfs Cannot Open Root Device Redhat then I load zImage to board and this is message I got : uClinux/Nios II Altera Nios II support 2004 Microtronix Datacom Ltd. Trying to unpack rootfs image as initramfs... https://e2e.ti.com/support/embedded/linux/f/354/t/101591 RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.

I tried editing Gentoo's fstab to use UUIDs like Debian, to no avail. Vfs Cannot Open Root Device Centos more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed The uncompressed initramfs image appears to be around 21.5 MB, which should leave about 10 MB of space to load kernel modules. fuse init (API version 7.23) io scheduler noop registered io scheduler deadline registered io scheduler cfq registered (default) imx-weim 21b8000.weim: Driver registered.

Vfs Cannot Open Root Device Redhat

Register Help Remember Me? thanks .

<{POST_SNAPBACK}> [/quote] Please restore to default setting, and try again, make clean make menuconfig Kernel/Library/Defaults Selection ---> (linux-2.6.x) Kernel Version (None) Libc Version[*] Default all settings (lose changes) Vfs Cannot Open Root Device Or Unknown-block(0 0) I did : + make clean + rm -rf romfs + make vendor_hwselect SYSPTF=~/...../standard_1c12.ptf + make romfs + make menuconfig [*] Default all settings (lose changes) [ ] Customize Kernel Settings Please Append A Correct Root= Boot Option share|improve this answer answered Jan 5 at 13:12 Thawn 71317 add a comment| up vote 1 down vote USB device discovery has been an asynchronous process for a few years now.

Make sure your kernel is compiled with the following options (NOT MODULES!!) -->NFS client CONFIG_NETWORK_FILESYSTEMS=y CONFIG_NFS_FS=y CONFIG_NFS_V3=y -->NFS root CONFIG_ROOT_NFS=y -->Kernel level network autoconfiguration CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y and of course, your network http://bestimageweb.com/cannot-open/linux-cannot-open-root-device.php RPC: Registered tcp NFSv4.1 backchannel transport module. I did but I got the same message error . "..... Trademarks | Privacy Policy | Terms of Use Visit Jeremy's Blog. Please Append A Correct "root=" Boot Option; Here Are The Available Partitions:

The line that concerns me is about half way down the screen shot you attached where it reads: Please append a correct "root=" option; here are the available partitions: but lists but I got error when I load kernel to board . .... Reply Cancel Cancel Reply Suggest as Answer Use rich formatting Mastermind 41690 points Bernie Thompson TI Mar 30, 2011 7:45 PM In reply to Bryan Evenson: Bryan EvensonWhen a kernel module http://bestimageweb.com/cannot-open/lilo-cannot-open-root-device.php Register. 04-15-2011 #1 Persson121 View Profile View Forum Posts Private Message View Articles Just Joined!

This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. Vfs: Cannot Open Root Device "nfs" Or Unknown-block(2,0) I only get the insmod error if I'm running an initramfs; if I use an NFS insmod works just fine. did you follow the uclinux-dist wiki page?

However, when booting to it I get a kernel panic and a message about it not being able to open root device: fstab for Debian and fstab for Gentoo.

Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. My initramfs was probably too big. See kernel.org/doc/Documentation/kernel-parameters.txt for more detail. –vik Jan 8 at 18:42 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up Vfs Error Join Date Apr 2011 Posts 2 I have the same problem then I'm add root=/dev/ram0 option to my kernel and add /dev/ram0 to my initrd.

I also tried editing boot options for Gentoo in grub. The problem maybe you miss the rootfs. If anyone has any ideas, I'll post whatever output is needed. check over here However, I believe I'm rebuilding both the kernel and the modules whenever I have changed my kernel configuration.

The time now is 07:56 PM. Home Forum Today's Posts | FAQ | Calendar | Community Groups | Forum Actions Mark Forums Read | Quick Links View Site Leaders | Unanswered Posts | Forum Rules Articles Marketplace Boot from USB for mfgtools Use default environment for mfgtools Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr}; Hit any key to stop autoboot: 0 Kernel image @ 0x80800000 [ 0x000000 - The initramfs source is busybox, python and gcc from ubuntu.

The easiest way to fix this is use UUID= in /etc/fstab and PARTUUID= in the bootloader args you're passing to the kernel. Follow Us TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | m.ti.com (Mobile Version) TI is a global semiconductor design and manufacturing company. Reply With Quote November 17th, 2006,11:50 PM #2 hippo View Profile View Forum Posts Altera Guru Join Date Oct 2005 Location Taipei, Taiwan Posts 1,667 Rep Power 1 No, you should devtmpfs: initialized VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5 clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns pinctrl core: initialized pinctrl subsystem NET: Registered

The problem maybe you miss the rootfs. So what's going on here and how should I proceed? What do you think ?Like • Show 0 Likes0 Actions matt67 May 31, 2016 2:01 AMMark CorrectCorrect AnswerI found what was the problem ! Please turn JavaScript back on and reload this page.More questions in i.MX Community Where is this place located?NXP CommunityAll Placesi.MX CommunityLog in to create and rate content, and to follow, bookmark,

Using 'conf at 1' configuration Trying 'fdt at 1' fdt subimage Description: gpl327xx.dtb Type: Flat Device Tree Compression: uncompressed Data Start: 0x00661ae8 Data Size: 2174 Bytes = 2.1 KiB Architecture: ARM yes .