linux kernel - Rootfs on SD card -
I have a device on which I have a 3.10 Linux kernel that boots from the busybox (initramfs) < / p>
When I removed the Busiebox filesystem image on the SD card and when I modified the root in / dev / mmcblck0p1 from root = / dev / ram, then it still boots up to the shell so busybox works fine But if I try to use any other FS kernel crashes ...
h I try to generate the rootfix using debootstrap () and I have removed the new rootfish on the SD card. I get an error saying that "failed to execute / sbin / init" I have checked that the file exists and has checked permissions and I like it.
What could be the problem?
WRT rootfs I'm particularly new I was thinking that an FS can be mounted on the SD card but it does not seem that this is the case. I guess / sbin / init is doing whatever the device is up to?
What am I trying to do? --- & gt; I need to create roufs with some packages and libraries (GCC Python etc). What will be the general perspective? I have also tried to build, but I could not find GCC on target. Is not possible within / bin / buildroot in GCC?
- UPDATE -
I am formatting the SD card in ext4 format and the following is the output of fdisk disk / dev / sdb1: 7945 MB, 7945588224 bytes 255 heads, 63 Area / track, 965 cylinder, total 15518727 areas unit = 1 * 512 = 512 bytes area sector size (logical / physical): 512 bytes / 512 bytes I / O size (minimum / optimum): 512 bytes / 512 byte disk identifier : 0xc2aa4908 Device boot start and block id system
and below Written kernel log is a file system I have SD card. Memory card driver works fine I have verified this. If I have a bizbox file system on the SD card, then everything works fine when I am using any other file system I get the following ...
6EXT4-fs ( mmcblk0p1): Mounted file system with compliant data mode. Opts: (tap) 6VFS: mount root (ext4 filesystem) 179: 1 on device 179. 6 Ineffective kernel memory: 84K (c0f00000 - c0f15000) 3request_module: Runaway loop Modofob binfmt-464c 4kworker / u2: 4 (145) The largest stack depth used: 6132 bytes 3 executed / sbin / init failed attempts failed. 3.request_module: Runaway loop modprobe binfmt-464c 3request_module: Runaway loop modprobe binfmt-464c 0 kernel panic - not synchronized: no init found init = option to keep the kernel in the kernel, see the linux documentation / init.txt for the guide. When checked, there is / sbin / init with appropriate permissions!
In all probabilities you 64b binary ( / sbin / init and rest) with 32b kernel only. To either support your kernel 64G or to re-compile 32b user space on your SD card To check for other things:
- Confirm that ELF support is actually enabled in your kernel (this is common practice). But it is possible to disable it).
- See what Google is experiencing with the error and the problems with people. < / Html>
Comments
Post a Comment