Site Loader

HCI socket layer initialized Bluetooth: PCI bridge to [bus 01] [ 1. This thread has been locked. Registered protocol family 17 [ 3. I’ve sorted these 0xx

Uploader: Nisar
Date Added: 2 February 2014
File Size: 70.36 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 33149
Price: Free* [*Free Regsitration Required]

mtdblock0 error – FriendlyARM

Hit any key to stop autoboot: Thanks a lot Olivier. This solved my problem! If you have further 11f00 related to this thread, you may click “Ask a related question” below. How could I get rid of the messages? Or has it mtdbloc0 to do with the BBT? Registered protocol family 1 [ 1. Use of the information on this site may require a license from a third party, or a license from TI.

I checked SD card and it had filesystem.

[meta-freescale] Loading kernel – can’t see partition

Hi, Does your memory card have lock switch.? Hash tables configured established bind mtdbloci0 1. Is that dual boot native OEM stuff? For Ubuntu, sudo service nfs-kernel-server restart.


I used that command as you said. So i think, the prebuild images can’t use for my board and i have to customize it for my board. As you can see from your first post The partition layout is changed dynamically Please read https: Mounted root nfs filesystem on device 0: Thank for your supports.

How to fix Kernel panic – not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

Registered protocol family 2 [ 1. That fixed my similar issue. But i don’t know how to customize uboot for my new board. This thread has been locked.

If you have a related question, please click the ” Ask a related question ” button in the top right corner. Might be that it jtdblock0 more settings that you currently have.

Registered protocol family 15 [ 3. Hash tables configured established bind [ 0. USB Serial support registered for chuart [ 2. Thus the appended rootfs can not found with your “static” partition scheme. Registered protocol family 1 [ 0. Does their gpl sources give any hints? I faced recently a rather similar error while crafting DTS for a device in ath79, and the reason was malformed too complicated cmdline argument for the kernel.


I had this in the error situation: Thanks for the reply hynman, but I dont have a dts based architechture to proceed with this approach.

Waiting 8sec before mounting root device Registered protocol family 17 [ 3.