X96 Max+ and ceemmc -x failure

roisiano · 5 June 2020 17:53

Please, confirm me if I understand it or correct me if I’m wrong (probably).
I want to use this TV-Box as a TVHeadend server (I configured this in CE 9.2.2 in SD), so I want to use a stable CE version in “internal” eMMC.

Now it’s supposed that the TV-Box has a CE on eMMC, but it does not starts.
So that… with these “start conditions”, if I want stable 9.2.2 CE version, shold I…?

Install a nightly in a new internal SD card
Trying to install CE nightly “above” the CE installation (that does not start) that I have in eMMC at this moment
If the process is OK and nighly now starts from eMMC, then can I update to stable version putting “CoreELEC-Amlogic-ng.arm-9.2.2.tar” in Update folder?
Supposing that previous steps are right… if I use the backup that I have in my SD for CE 9.2.2 stable version… would it work in eMMC or not (because paths are different)?

Kind regards

TheCoolest · 5 June 2020 21:25

No:
Step 3 will not work.
Step 4 is unnecessary, because the installation transfers all your data to the eMMC.

roisiano · 6 June 2020 15:04

Well… finally I dit this:

Flash an Android image from SD card.
Install the last nightly in an SD and restore a backup of the previous 9.2.2.
Install this to internal (ceemmc -x ; option 3)
OK; it is into eMMC.
“Update” to 9.2.2 stable on eMMC.
But… it seems that I have some problems of performance (comparing to nightly), some problems using “entware”… so…
Back to “nigthly”

Really it was not my intention at all to put a nightly in eMMC, but I’m not satisfied with performance and some problems when I changed to 9.2.2, so I’m using nightly at the moment.

I hope the next stable will be ready soon and shows more performance in eMMC (in SD works really fine). At this moment, for my X96 Max+, if I want it in eMMC (and I want), is the nightly.

Kind regards

Compent · 6 June 2020 23:20

I run every single nightly that comes along and although there are the occasional bugs and glitches, I tend to find them as rock solid as the stable releases, with the added benefits of being closer to the bleeding edge of development, so I would not treat nightly as being potentially automatically likely to be unstable as for the vast majority of the time they will work extremely well and if you do come across a nightly with a bug that adversely affects your box performance or stability, you can simply go back to a previous working one and await appropriate modifications and fixes.

relkai · 7 June 2020 00:51

I have to add: If you are really experiencing a bug in the nightlies, it’s very important to report it, so we are able to locate and fix it as soon as possible.

roisiano · 7 June 2020 14:44

Well… I don’t really “have” noghing against the nihtlies.
I have been using them for a X96 Max+ (S905X3) some months until the 9.2.2 stable was realeased with no significative problems at all.
But, in this case, I want to use this TV-Box as a TVHeadend server, in a place that is quite far from my home, and I’ll go to his place once a month, more or less… so, if, for example, I had some problem after an update, I could not solve it in several days or weeks.
For this reason I prefer clearly the stable version for this particular case.
If I used this TV-Box at home, it would not be a problem for me.

Anyway, I will use nightly in eMMC for this TV-Box, and probably I will not have problems until a new stable version will be released.

Thanks for your fantastic job and kind regards!

relkai · 7 June 2020 19:06

We absolutely agree, that a stable release should be preferred over a nightly one, especially in such use cases.
But for the moment you have no other choice, because the last stable isn’t prepared for your hardware yet.

Please be patient for a little more time.
As soon as the next stable is released, you can switch to it, of course.

roisiano · 12 June 2020 19:48

By the way… using now stable 9.2.3 in this Tv-Box.
Excellent.
Fantastic job.

PatrickJB · 25 June 2020 10:37

Just wondering which version of CE you’re running on the X96 MAX+? Is a firmware upgrade needed for CE to work from internal or is it safe to move to internal with the standard firmware? Also does dual boot work OK?

Seems that installing CE on this box is complicated which is a shame as it seems quite a good box for the price.

Portisch · 25 June 2020 11:36

I really can not recommend this box as it get sometimes sold with different SoC and also with lowest quality of internal eMMC.

PatrickJB · 25 June 2020 11:55

Thanks for the warning.

ak4490 · 5 July 2020 06:58

I use the dtb file “sm1_s905x3_4g_1gbit”, and burn the img to my usb flash disk with etcher successful. login into shell and ceemmc -x successful. My coreelec version is 9.2.3. Maybe you can have a try.

bubblegum57 · 5 July 2020 08:23

Just wanted to say, install to emmc worked on my X96 Max+

dual boot CE or Android

bestbudget · 11 December 2020 13:53

That’s exactly why I’m here - to get this information. Thank’s!

nmocruz · 19 April 2021 10:28

Do you have a new link for this firmware?

kris007 · 7 September 2021 15:19

Today I successfully installed CoreElec version 19.2-Matrix_rc3 (Stable) on my X96max + … in SINGLE BOOT mode
Thanks to everyone for working on CoreElec !!!

Krotosz6 · 22 September 2022 09:12

Hi. I have X96 max with s905x2 4g_1gbit. http://ix.io/4b6D
I have successfully installed CE on SD. When I tried to use the ceemmc tool I got this issue:


Install CoreELEC on eMMC.
Continue? [y]: y

Moved 'env' from offset 0x00004d400000, size 0x000000800000 to offset 0x000000400000
Moved 'misc' from offset 0x000051400000, size 0x000000800000 to offset 0x000000c00000
Moved 'logo' from offset 0x00004e400000, size 0x000000800000 to offset 0x000001400000
Moved 'dtbo' from offset 0x000052400000, size 0x000000800000 to offset 0x000001c00000

Starting to format the new 'CE_STORAGE' partition...
mke2fs 1.45.7 (28-Jan-2021)
Discarding device blocks: done
Creating filesystem with 15111168 4k blocks and 3784704 inodes
Filesystem UUID: 04334eb3-3b24-4e33-8680-b234f0034336
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424

Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done

Error opening file for writing '/dev/reserved'!
Failed to write the new partition table to eMMC!

ls -l

total 40
drwxr-xr-x    2 root     root          4096 Sep 21 21:48 backup
drwx------    2 root     root         16384 Aug  6  2021 lost+found
drwxrwxrwx    2 root     root          4096 Aug  6  2021 music
drwxrwxrwx    2 root     root          4096 Aug  6  2021 pictures
drwxrwxrwx    2 root     root          4096 Sep 21 20:11 screenshots
drwxrwxrwx    2 root     root          4096 Aug  6  2021 tvshows
drwxrwxrwx    2 root     root          4096 Aug  6  2021 videos
NowePudlo:~ # ls -l /sys.block
ls: /sys.block: No such file or directory
NowePudlo:~ # ls -l /sys/block
total 0
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop0 -> ../devices/virtual/block/loop0
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop1 -> ../devices/virtual/block/loop1
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop2 -> ../devices/virtual/block/loop2
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop3 -> ../devices/virtual/block/loop3
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop4 -> ../devices/virtual/block/loop4
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop5 -> ../devices/virtual/block/loop5
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop6 -> ../devices/virtual/block/loop6
lrwxrwxrwx    1 root     root             0 Jan  1  2015 loop7 -> ../devices/virtual/block/loop7
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk0 -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk0boot0 -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0/mmcblk0boot0
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk0boot1 -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0/mmcblk0boot1
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk0rpmb -> ../devices/platform/ffe07000.emmc/mmc_host/emmc/emmc:0001/block/mmcblk0/mmcblk0rpmb
lrwxrwxrwx    1 root     root             0 Jan  1  2015 mmcblk1 -> ../devices/platform/ffe05000.sd2/mmc_host/sd/sd:59b4/block/mmcblk1

mount

devtmpfs on /dev type devtmpfs (rw,relatime,size=1901604k,nr_inodes=475401,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=763092k,nr_inodes=819200,mode=755)
/dev/mmcblk1p1 on /flash type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
/dev/loop0 on / type squashfs (ro,relatime)
/dev/mmcblk1p2 on /storage type ext4 (rw,noatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /var type tmpfs (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=1907724k,nr_inodes=409600)
sunrpc on /run/nfs/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)

When I try this:

 mount -o remount,rw /flash
wget -O /flash.dtb.img "https://discourse.coreelec.org/uploads/short-url/j83hKWRQD6Og4LszyJoZ8uLVubu.dt
b"
Connecting to discourse.coreelec.org (116.203.16.118:443)
wget: can't open '/flash.dtb.img': Read-only file system

What should he do now? I don’t know if my device will start CE from SD?

vpeter · 22 September 2022 09:27

Use the nightly where this issue is fixed.

https://relkai.coreelec.org/

Krotosz6 · 22 September 2022 10:21

It works. Thank You man. You guys are doing a great job with CE. Should I now go back to the stable version on MMC?

Rexter · 23 October 2022 20:21

No, I just tried the stable version and it’s not fixed yet. I will be staying on the alpha for a while