Compiler/AM3352: Ramdisk error

Hello Subramanya,

Please, refer to this post to boot your board from ramfs.

Best regards,
Kemal

Hi Kemal,

Tried with above post with creating ramdisk image with provided step. Still issue is didn't solved.

Please help me to solve this issue.

Regards,

Subramanya

Can you post the log?

Please find below logs.

[ 2.113836] usb usb2: Product: MUSB HDRC host driver
[ 2.119038] usb usb2: Manufacturer: Linux 3.14.26 musb-hcd
[ 2.124783] usb usb2: SerialNumber: musb-hdrc.1.auto
[ 2.131022] hub 2-0:1.0: USB hub found
[ 2.135031] hub 2-0:1.0: 1 port detected
[ 2.141079] pinctrl-single 44e10800.pinmux: pin 44e1092c.0 already requestedt
[ 2.153525] pinctrl-single 44e10800.pinmux: pin-75 (4a100000.ethernet) statu2
[ 2.161369] pinctrl-single 44e10800.pinmux: could not request pin 75 (44e109e
[ 2.173760] cpsw 4a100000.ethernet: Error applying setting, reverse things bk
[ 2.228393] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 2.234795] davinci_mdio 4a101000.mdio: detected phy mask fffffffc
[ 2.242949] libphy: 4a101000.mdio: probed
[ 2.247188] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, drit
[ 2.257207] davinci_mdio 4a101000.mdio: phy[1]: device 4a101000.mdio:01, drit
[ 2.267931] cpsw 4a100000.ethernet: Detected MACID = 50:65:83:5d:f0:4e
[ 2.277597] input: gpio_keys.13 as /devices/gpio_keys.13/input/input1
[ 2.285617] rtc-pcf8563 1-0051: setting system clock to 1970-05-12 23:13:52 )
[ 2.298066] RAMDISK: gzip image found at block 0
[ 2.526230] RAMDISK: incomplete write (12944 != 32768)
[ 2.531666] write error
[ 2.611198] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 2.617503] devtmpfs: error mounting -2
[ 2.622001] Freeing unused kernel memory: 344K (c080d000 - c0863000)
[ 2.628745] Kernel panic - not syncing: No working init found. Try passing .
[ 17.C

Hi Kemal,

I followed above steps even though i am getting same error.

But filesystem is booting properly with NOR flash.

When i boot zImage/uImage, filesystem(initrd) and device tree from DDR2 directly using bootm command at that time i am not able to boot device completely.As i shown in above logs.

I need to boot from DDR for my experiment.

Also i checked hexdump values of initrd both from flash and DDR both looks same.

Please help us to solve this issue.

Regards,

Subramanya 

Can you attach me your ramdisk.gz image?

Hi Kemal,

As per company policy i am not able to share image files.

Please suggests me.

Regards,

Subramanya

I am attaching you mine. Can you try to boot your board with this ramfs image?

1541.ramdisk.gz

Dear Kemal,

i tried with your filesystem still i am facing somple problem while booting from DDR2. Please find below logs

## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.14.26
Created: 2019-07-04 10:30:43 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4460496 Bytes = 4.3 MiB
Load Address: 82000000
Entry Point: 82000000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 84080000 ...
Image Name:
Created: 2019-08-01 7:18:20 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6567298 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 84000000
Booting using the fdt blob at 0x84000000
Loading Kernel Image ... OK
Loading Ramdisk to 879bc000, end 87fff582 ... OK
Loading Device Tree to 879b0000, end 879bb3dd ... OK

[ 2.491739] RAMDISK: incomplete write (12876 != 32768)
[ 2.497168] write error
[ 2.573552] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 2.579857] devtmpfs: mounted
[ 2.583457] Freeing unused kernel memory: 344K (c080d000 - c0863000)
[ 2.590780] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc2
[ 2.600650] Starting init: /sbin/init exists but couldn't execute it (error )
[ 2.608407] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc0
[ 2.618182] Starting init: /etc/init exists but couldn't execute it (error -)
[ 2.625787] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.635543] Starting init: /bin/init exists but couldn't execute it (error -)
[ 2.643123] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.652875] Starting init: /bin/sh exists but couldn't execute it (error -5)
[ 2.660271] Kernel panic - not syncing: No working init found. Try passing .

Regards,

Subramanya

Subramanya Musale said:

## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.14.26

Hi Kemal,

I tried with new kernel also 4.14.79 still i am facing same issue.

Please find below logs

# Loading init Ramdisk from Legacy Image at 84080000 ...
Image Name: 
Created: 2019-08-01 7:18:20 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 6567298 Bytes = 6.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 84000000
Booting using the fdt blob at 0x84000000
Loading Ramdisk to 879bc000, end 87fff582 ... OK
Loading Device Tree to 879af000, end 879bb0ae ... OK

[ 1.650320] RAMDISK: gzip image found at block 0
[ 1.911758] RAMDISK: incomplete write (12876 != 32768)
[ 1.917192] write error
[ 1.996486] EXT4-fs (ram0): bad geometry: block count 16384 exceeds size of )
[ 2.006057] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 2.012355] devtmpfs: mounted
[ 2.017000] Freeing unused kernel memory: 1024K
[ 2.023029] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc2
[ 2.032949] Starting init: /sbin/init exists but couldn't execute it (error )
[ 2.040706] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc0
[ 2.050544] Starting init: /etc/init exists but couldn't execute it (error -)
[ 2.058191] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.068098] Starting init: /bin/init exists but couldn't execute it (error -)
[ 2.075714] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.085487] Starting init: /bin/sh exists but couldn't execute it (error -5)
[ 2.092885] Kernel panic - not syncing: No working init found. Try passing .
[ 2.107733] ---[ end Kernel panic - not syncing: No working init found. Try.
[ 13.719414] random: crng init done

Regards,

Subramanya

Subramanya Musale said:

[ 1.996486] EXT4-fs (ram0): bad geometry: block count 16384 exceeds size of )

Hi Kemal,

My DDR configured properly, i will get above errors only when i boot from DDR instead of NOR flash.

I tried above method still i am facing same issue.

Regards,

Subramanya

Can you post the log?

Please find below logs

[ 2.250978] RAMDISK: gzip image found at block 0
[ 2.490786] RAMDISK: incomplete write (12876 != 32768)
[ 2.496234] write error
[ 2.572428] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 2.578714] devtmpfs: mounted
[ 2.582324] Freeing unused kernel memory: 344K (c080d000 - c0863000)
[ 2.589644] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc2
[ 2.599528] Starting init: /sbin/init exists but couldn't execute it (error )
[ 2.607269] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc0
[ 2.617046] Starting init: /etc/init exists but couldn't execute it (error -)
[ 2.624646] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.634411] Starting init: /bin/init exists but couldn't execute it (error -)
[ 2.641998] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.651760] Starting init: /bin/sh exists but couldn't execute it (error -5)
[ 2.659157] Kernel panic - not syncing: No working init found. Try passing .

When you use the second method you only need to embed an initramfs image to your kernel and pass rdinit=/sbin/init line to the kernel's command line. Doing it in this way you will not get these "RAMDISK: gzip image found at block 0" , "EXT2-fs (ram0)" messages. Please, run env default -a -f; saveenv; reset commands in U-Boot console, embed an initramfs image to your kernel and just add rdinit=/sbin/init line to your bootargs.

Hi Kemal,

I followed below steps and facing similar issue. Please correct me in my steps.

U-Boot# setenv ipaddr 10.0.50.11
U-Boot# setenv serverip 10.0.50.10
U-Boot# tftp 0x82000000 zImage
U-Boot# tftp 0x84080000 1541.ramdisk.gz
U-Boot# tftp 0x84000000  am335x-evm.dtb
U-Boot# rdinit=/sbin/init

U-Boot# env default -a -f

U-Boot# saveenv

U-Boot# bootz 0x82000000 0x84080000 0x84000000

[ 2.251046] RAMDISK: gzip image found at block 0
[ 2.490666] RAMDISK: incomplete write (12876 != 32768)
[ 2.496093] write error
[ 2.572145] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 2.578478] devtmpfs: mounted
[ 2.582082] Freeing unused kernel memory: 344K (c080d000 - c0863000)
[ 2.589433] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc2
[ 2.599304] Starting init: /sbin/init exists but couldn't execute it (error )
[ 2.607048] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc0
[ 2.616814] Starting init: /etc/init exists but couldn't execute it (error -)
[ 2.624415] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.634184] Starting init: /bin/init exists but couldn't execute it (error -)
[ 2.641797] EXT2-fs (ram0): error: ext2_get_inode: unable to read inode bloc4
[ 2.651567] Starting init: /bin/sh exists but couldn't execute it (error -5)
[ 2.658963] Kernel panic - not syncing: No working init found. Try passing .
[ 24.CCCCCCCC

Regards,

Subramanya

Hi Kemal,

I have seen some issue with Kernel 4.14. In this kernel version device is not booting above method is worked only for 3.14 kernel.

Following steps followed with 4.14 kernel

1) Make menuconfig 

Initramfs source file added absolute path of initramfs.cpio

2) make -->zImage generated

3)uboot# tftp zImage

4) uboot# tftp initrd.uboot

5) uboot# tftp am335x.dtb

6) run ramboot

Kernel is not booting. Please find below logs

U-Boot# run ramboot
Booting from ramdisk ...
Kernel image @ 0x82000000 [ 0x000000 - 0x30b28a8 ]
## Loading init Ramdisk from Legacy Image at 84080000 ...
Image Name: RootFS
Created: 2019-08-02 9:52:03 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 15734105 Bytes = 15 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 84000000
Booting using the fdt blob at 0x84000000
Loading Ramdisk to 870fe000, end 87fff559 ... OK
Loading Device Tree to 870f1000, end 870fd07e ... OK

Starting kernel ...

Please help to solve this

Regards,

Subramanya

Sorry kemal  i didn't understand you point. I think you mean.

The absolute path of initramfs should be within the kernel folder? i.e kernel/linux-version/

Please clarify me with some example.

When you run this command this is the first method and you are loading ramdisk image. You do not need to pass absolute path of initramfs to the kernel.

U-Boot# run ramboot
Booting from ramdisk ...

Hi Kemal,

I removed absolute path and started to boot using run ramboot

uboot# run ramboot

we got login prompt with following errors

and i tried with login: root

               pswd:root

login : admin

pswd:default

Not able to login

please find below logs

Starting logging: Initializing random number generator... [ 3.934914] random)
done.
mount: mounting /dev/ on /mnt/jffs2 failed: Block device required
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
Segmentation fault
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
[ 4.311276] 8192eu: disagrees about version of symbol module_layout
insmod: can't insert '/usr/bin/8192eu.ko': invalid module format
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
nameif: /etc/mactab: No such file or directory
Segmentation fault
chown: unknown user/group admin:root
chown: unknown user/group admin:root
sh: 1: unknown operand
New Monit id: 1138c6dc42fe8817dced8b429957860b
Stored in '/jffs2/.monit.id'
Starting Monit 5.18 daemon with http interface at [*]:2812
Monit start delay set -- pause for 10s
sid_str = , sid = 0x0
------------------ 3g -------------------
[oem_customiser]wait ....
Segmentation fault
sh: missing ]
/usr/bin/noderedcfg: symbol lookup error: /usr/bin/noderedcfg: undefined symbole
Starting network...
Starting ntpd: OK
Starting ProFTPD: [ 18.248064] capability: warning: `proftpd' uses 32-bit cap)
Device proftpd[1102]: Fatal: User: missing arguments on line 31 of '/etc/proftp'
FAILED
[ 18.284487] random: ssh-keygen: uninitialized urandom read (32 bytes read)
ssh-keygen: generating new host keys: RSA1 DSA ECDSA ED25519
Starting sshd: [ 25.297305] random: sshd: uninitialized urandom read (32 byte)
OK
Starting stunnel: [.] stunnel 5.09 on arm-buildroot-linux-gnueabihf platform
[.] Compiled/running with OpenSSL 1.0.2 22 Jan 2015
[.] Threading:FORK Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
[ ] errno: (*__errno_location ())
[.] Reading configuration from file /etc/stunnel/stunnel.conf
[.] UTF-8 byte order mark detected
[ ] Enabling support for engine "capi"
[!] error queue: 2606A074: error:2606A074:engine routines:ENGINE_by_id:no such e
[!] ENGINE_by_id: 260B606D: error:260B606D:engine routines:DYNAMIC_LOAD:init fad
[!] Line 18: "engine = capi": Failed to open the engine
FAIL
Starting IPsec...
Segmentation fault
[ 28.670434] random: crng init done
sh: enabled: unknown operand
Starting udhcpd: cat: can't open '/jffs2/system.ini': No such file or directory
OK
Starting PPTP...
Probe RSTP module...
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
Starting RSTP...
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
sh: Enable: unknown operand
Starting iptables: cat: can't open '/jffs2/system.ini': No such file or directoy
OK

Device login:

Please help me to login

Regards,

Subramanya

Check the /etc/securetty whether the root is allowed to login over this tty. If you tell me what are you trying to accomplish with that ramfs, maybe I could help more.

Hi Kemal,

I logged in but network unreachable.

Not able to ping. BUt pingable in 3.14 kernel.

please find below logs

[ 1.731517] RAMDISK: gzip image found at block 0
[ 3.769894] VFS: Mounted root (ext2 filesystem) on device 1:0.
[ 3.776296] devtmpfs: mounted
[ 3.780971] Freeing unused kernel memory: 1024K
Starting logging: Initializing random number generator... [ 3.952819] random)
done.
mount: mounting /dev/ on /mnt/jffs2 failed: Block device required
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
Segmentation fault
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
[ 4.330637] 8192eu: disagrees about version of symbol module_layout
insmod: can't insert '/usr/bin/8192eu.ko': invalid module format
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
nameif: /etc/mactab: No such file or directory
Segmentation fault
chown: unknown user/group admin:root
chown: unknown user/group admin:root
sh: 1: unknown operand
New Monit id: b2af623c7ce3e7a82e897cc37bcbf548
Stored in '/jffs2/.monit.id'
Starting Monit 5.18 daemon with http interface at [*]:2812
Monit start delay set -- pause for 10s
sid_str = , sid = 0x0
------------------ 3g -------------------
[oem_customiser]wait ....
Segmentation fault
sh: missing ]
/usr/bin/noderedcfg: symbol lookup error: /usr/bin/noderedcfg: undefined symbole
Starting network...
Starting ntpd: OK
Starting ProFTPD: [ 18.263631] capability: warning: `proftpd' uses 32-bit cap)
Device proftpd[1102]: Fatal: User: missing arguments on line 31 of '/etc/proftp'
FAILED
[ 18.299816] random: ssh-keygen: uninitialized urandom read (32 bytes read)
ssh-keygen: generating new host keys: RSA1 [ 25.827531] random: crng init done
DSA ECDSA ED25519
Starting sshd: OK
Starting stunnel: [.] stunnel 5.09 on arm-buildroot-linux-gnueabihf platform
[.] Compiled/running with OpenSSL 1.0.2 22 Jan 2015
[.] Threading:FORK Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
[ ] errno: (*__errno_location ())
[.] Reading configuration from file /etc/stunnel/stunnel.conf
[.] UTF-8 byte order mark detected
[ ] Enabling support for engine "capi"
[!] error queue: 2606A074: error:2606A074:engine routines:ENGINE_by_id:no such e
[!] ENGINE_by_id: 260B606D: error:260B606D:engine routines:DYNAMIC_LOAD:init fad
[!] Line 18: "engine = capi": Failed to open the engine
FAIL
Starting IPsec...
Segmentation fault
sh: enabled: unknown operand
Starting udhcpd: cat: can't open '/jffs2/system.ini': No such file or directory
OK
Starting PPTP...
Probe RSTP module...
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy
Starting RSTP...
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
iniparser: cannot open /jffs2/rstp.ini
cannot parse file: /jffs2/station.ini
sh: Enable: unknown operand
Starting iptables: cat: can't open '/jffs2/system.ini': No such file or directoy
OK

# ping 10.0.50.11
PING 10.0.50.11 (10.0.50.11): 56 data bytes
ping: sendto: Network is unreachable

Please help to solve this issue.

But pingable in 3.14 kernel

Regards,

Subramanya

Please, focus on these errors. You need to fix them to make the ping work.

mount: mounting /dev/ on /mnt/jffs2 failed: Block device required
iptables v1.6.1: can't initialize iptables table `nat': Table does not exist (d)
Perhaps iptables or your kernel needs to be upgraded.
modprobe: can't change directory to '4.14.79-ge669d52447': No such file or direy