Yes, this command will show it as prescribed for a multi-boot in eMMC. I can add the output of "cat /proc/cmdline".
Posts by ilikenwf
-
-
Will fw_printenv output the correct information even if I'm booting from emmc? I already installed to emmc using install.sh from the init shell.
-
Cross posting. Since my work is forked from 150balbes' work, which includes khazaq's kernel, I can't claim much credit, but check out the thread over at [S812] MIII Plus 2Gb\16Gb eMMC
Ok, so if you don't mind installing LE to your M8S S812 bcm4335's internal memory and wiping out android, here's what you do. This build will probably work with other versions of the M8S but I'm only targeting the bcm4335 variants.
1. Download my build from Yandex.Disk
2. Write to microSD card
3. Rename the appropriate remote.conf - note that the one for our bcm4335 should be solid now but I notice one of the patches I added makes CEC work so you can use your TV remote too
4. Hook up USB keyboard to your device
5. Insert microSD, and do the toothpick method if you haven't yet setup 150balbes dual boot solution
6. Once you see the LE boot screen, wait until you see an error message in the upper left corner
7. Then, do the following:
8. You'll know you are finished when the script stops executing for a while and no more output comes on the screen. Then, type reboot and remove the microSD card. Your device will now boot into Libreelec.
I haven't tried it yet but this should theoretically work with retroarch too, since the S805 does and my builds are just forked from 150balbes, and thus uses khazaq's kernel...
My sources: GitHub - ilikenwf/LibreELEC.tv: 'Just enough OS' for Kodi
With help we can get the SD card booting working. I tried to work around it by remounting /flash to /dev/mmcblk0p1 in the init scripts but did not succeed.
The only known issues to me right now are that suspend/wake are sometimes a bit buggy...otherwise it works well enough. I'd like to find time sometime to explore various kernel patches that are out there, as well as the khazaq and Libreelec repos for the amlogic specific kernel, amongst a few others, to try and get things working better and up to a newer (3.14) kernel.
-
Ok, so if you don't mind installing LE to your M8S S812 bcm4335's internal memory and wiping out android, here's what you do. This build will probably work with other versions of the M8S but I'm only targeting the bcm4335 variants.
1. Download my build from Yandex.Disk
2. Write to microSD card
3. Rename the appropriate remote.conf - note that the one for our bcm4335 should be solid now but I notice one of the patches I added makes CEC work so you can use your TV remote too
4. Hook up USB keyboard to your device
5. Insert microSD, and do the toothpick method if you haven't yet setup 150balbes dual boot solution
6. Once you see the LE boot screen, wait until you see an error message in the upper left corner
7. Then, do the following:
8. You'll know you are finished when the script stops executing for a while and no more output comes on the screen. Then, type reboot and remove the microSD card. Your device will now boot into Libreelec.
I haven't tried it yet but this should theoretically work with retroarch too, since the S805 does and my builds are just forked from 150balbes, and thus uses khazaq's kernel...
My sources: GitHub - ilikenwf/LibreELEC.tv: 'Just enough OS' for Kodi
With help we can get the SD card booting working. I tried to work around it by remounting /flash to /dev/mmcblk0p1 in the init scripts but did not succeed.
The only known issues to me right now are that suspend/wake are sometimes a bit buggy...otherwise it works well enough. I'd like to find time sometime to explore various kernel patches that are out there, as well as the khazaq and Libreelec repos for the amlogic specific kernel, amongst a few others, to try and get things working better and up to a newer (3.14) kernel.
-
Thereabouts is where the issue is, I've yet to find where the actual device is mapped to the virtual dev/boot dev/system etc virtual devices, and as such I boot up to just the bare initrd and stop because the flash/SYSTEM file is missing until I mount /dev/mmcblk0p1 (the sd card fat partition) to /flash, so it can be found and used.
-
I've been busy with work stuff.
-
There's a needed dtb patch to boot on this device, I have it in my fork of balbes150's work, he's also welcome to copy it sometime..that or the 100M lan version may work for you. Seems to be hit and miss.
The only issue I encounter right now is that booting isn't straightforward because you have to manually mount the mmc and SYSTEM image right now.
balbes150 - I can't seem to locate where the /flash mountpoint is even specified, is the aml_autoscript supposed to do this? If so, what parameters? Currently the script is mounting the internal memory's system partition with the build.prop inside for android instead of /dev/mmcblk0p1, where the SYSTEM image is located.
If we can get past this we'll have a fix for the bcm4335 variants.
-
Update on TV Boxing multiboot from your created image. You are old multiboot, it can not run the new images (which you collect).
So copy over the aml scripts from the current git (or one of your builds for m8s) and rerun the toothpick method?
-
You need to activate the new option of multi-boot (using the files that are included in your new way). Now you have enabled the old scheme, which can only run older images.
This line should look like this
run start_autoscript; run storeboot
LibreELEC.tv/aml_autoscript.src at Amlogic-Krypton · 150balbes/LibreELEC.tv · GitHub
I have the current version of your git built, do I actually need to modify some files? The scripts etc are all from the image I built using your master branch.
-
1. The model on the board itself is M8 v8.9 - the firmware it uses, stock, is cyx_m8s_v8.6_bcm4335_8g2g_kodi_addons_160125_USB - there was a newer release but it wouldn't flash for me...odd that the firmware it uses is 8.6, while the board is labeled 8 .9. My dtb file is somewhere earlier in the thread, and as a patch in my fork of your LE repo.
2. idUI
3. I guess it would have to be 4.4, no versions beyond this have been functional.
-
Nope, doesn't work on the bcm4335 model. Multiboot works in that LE tries to start, but mmcblk0p1 isn't being mounted as /flash (something else is) and so the SYSTEM image isn't available automatically.
-
If you used my GIT, you do not need to rename the script s805_autoscript. Leave it as it is. Activate the multi-boot and the system should normally be run by itself. Pay attention, the activation may be performed once and necessary SD card. Ie You need one time to record your image on the SD card. Use the update mode from Andoid or method of a toothpick. Once you upgrade bootloader, you can use to embed LE any USB flash drive or SD card.
I am using your git, and have already activated multi boot previously, using your images, but none get past the filesystem error message without renaming the s805 script for use instead of aml_autoscript. I can try again next time I reboot the thing, but the last time I had it working, USB wouldn't work either.
Using the renamed s805 I'm at least able to boot, though in a roundabout way as I have to manually mount system. As I said I'll try multiboot once more and see how it goes.
-
Once I figure out how to fix a mount at boot issue, the balbes150 version/thread I'll post a working build of 17.3...I have it working on my bcm4335 M8S, albeit the wifi doesn't list networks (interface shows up), and I have to manually mount the system image at boot until I figure out how to automount mmcblk0p1 and then the image.
-
balbes150 so, I've built your latest 17.3 and now have gotten it to partially work with my bcm4335 S812 M8S. I am using a patch that adds the dts file from the stock android.
Steps:
- Rename s805_autoscript to aml_autoscript
- Manually mount /dev/mmcblk0p1 and then mount SYSTEM to sysroot (how do I automate this? I'm not new to Linux but am new to LE), exit, and then boot
Playback and wired networking appear to be working perfectly, wireless networks did not appear in the setup menu but the interface appears to be working, which is strange...
I also need to get the remote.conf from my stock android as the volume buttons don't currently work as well.
Video and audio quality appear to be be better (much better) than they were in Android. The strange thing is that these boxes' dts files say they are 1G devices, but then the android kernel shows 2GB at boot - think it may be some kind of Chinese knockoff thing there? My only other guess is that perhaps half of that is saved for vram?
Help me get the boot mounts setup and I can put in a pull request.
Work in progress: this seems to add proper working support for the bcm4335 m8s, mostly,… · ilikenwf/LibreELEC.tv@c05fc84 · GitHubAlso, hypothetically, if I wanted to get the retroarch stuff working, is it just pulling that stuff into the build, or does it go deeper than that?
Thanks for all your work!
-
So I've successfully built an LE image several times, but it just bootloops with only the S812 logo screen splash, while @balbes150 's builds at least boot the kernel and hang at the filesystem error...
What am I doing wrong? I'm using his repo, and making as so:
-
So I've finally found the factory images for my device, which is a bcm4335 S812. The cyx_m8s_v8.6_bcm4355 (path=) images are the proper ones, it is slow going but I am currently pulling the latest I could find down from baidu pan.
That said, here is the 100% proper dts/dtb for this device (m8m2_bcm4335_n200C_1G) - I bought it and it said it has 2G ram, I think it iusually shows up as 1.6GB ram or so...yay China.
If anything changes with the newer img file I found, I'll put those up once done downloading.
-
bables150 if and when I get a chance I may attempt to build myself with that one working dts/dtb file...is your build process much different than that of the wiki?
-
Just an FYI, I can't get anything except the n200 AP firmware to work...