Add "ssh" to kernel boot params in http://syslinux.conf/extlinux.conf. This forces the SSH daemon to run at startup so you can SSH into the device from an Ethernet connection to run "dmesg | paste" .. then share the URL so we can see startup/boot and what the reason for failure is.
Posts by chewitt
-
-
The GXL Nexbox A95X device-tree: https://github.com/chewitt/linux/…nexbox-a95x.dts doesn't show any audio support at all so no surprise that HDMI and 3.5mm Jack outputs aren't working. Pick another GXL box device dtb, they are all very similar.
-
1. No. S905X is quite well supported. The issue with most W/Y boxes is they are super low-spec with 1GB RAM which means forget 4K.
2. Yes, because the blobs are firmware and old vendor kernels and moder kernels use the same firmwares. Drivers are something different.
3. The current upstream drivers were written for GXL/GXM; they don't work as well on newer G12/SM1 hardware as this neeeds updates to some of the codec drivers (which nobody made) and older S905 devices don't support HDR and VP9. Newer boxes have more CPU grunt so most of the time you can disable hardware decoding and software decode (1080p is great, forget 4K).
4. Allwinner and Rockchip are both well quite supported with older chipsets and there is considerable active development on support for newer chips. LE contributors are heavily involved in the kernel V4L2 stateless decoding efforts.
-
The approach I use in Hotels is to enable WiFi tethering which shares the WiFi connection over Ethernet and then I can use a normal browser on a laptop to deal with initial login. It's easier in LE to do Ethernet tethering (WiFi hotspot) but there's not always an Ethernet socket in the room (although the Hotel IPTV system probably has a usable connection).
-
The S905 chip requires magic boot code in the first sector of emmc which is the same location for partition records, so in theory you can't have modern u-boot on emmc and then boot an OS that needs to read partition data from the same location; they are mutually exclusive. SD cards boot from a different offset which isn't an issue. So the box must boot from SD card and the only way to force that is to erase vendor u-boot from eMMC (else it's detected and used). NB: The Odroid C2 has some special boot firmware that solves this, but the firmware is packaged to hide how it's done and nobody ever figured it out.
As the WP2 is going to boot LE11 from SD card in all scenarios there's not much difference between using the "box" image via vendor u-boot and the upstream u-boot image. See if the "box" image fits your needs first before doing anything more.
-
Sorry, I didn't understand. do you have LE not working on Station P2 and M1 ?
balbes150 он проверит
-
-
I already installed OpenVFD from CoreELEC repo, and put the correct vfd.conf on ./config folder. No change on the clock...
What am I doing wrong?
If you want to run CE code from CE repos, run CE, and then you post "it doesn't work" messages in the CE forum where someone that cares about CE code issues might reply to your message.
-
can i install LE in USB and boot from Amlogic? if can, please give a tip? thank!
If the (unknown) device has a working device-tree in the upstream kernel, it should be able to boot the AMLGX "box" image from USB.
-
Stuff is a bit broken right now due to not caring too much about old infra that broke itself (again) and people being super-busy with day jobs which is limiting time spent on the new infra which still needs some experimenting. Remember we're all just a bunch of volunteers doing this in our spare time for fun (allegedly)
-
It hasn’t progressed since the last snapshot above (20220504), but since you are the third to find me with WP2, now I’m really trying to get one from somewhere (at a reasonable price).
dtech I have another WP2 box lying unused at my parents in the UK, so if you don't find one via eBay I can always post that one to you when I visit them in mid-July.
-
WP2 is usable with the LE11 codebase based on upstream Linux (currently 5.18.0); albeit with no support for the DVB tuners inside (as there is no support for them upstream) and HEVC decoding being a little unpolished. H264 is good, other codecs are mostly software decoded but that isn't a big deal. NB: That specific image contains upstream u-boot and to use it you must completely erase Android from the internal emmc storage while the "box" image can boot using the vendor u-boot that comes with Android on the emmc storage. Neither WP2 or box image can update an existing image/SD card, a new/clean one is required.
It's not clear/decided whether Amlogic support is formally resurrected for LE11 as newer hardware has some major issues to solve, but there are no plans to stop nightlies.
-
Once the changes go through there will be no hotdog folder and no need for lots of per-folder releases.json files (only one).
-
I didn't submit these changes. Do you want to use for your device?
I'm interested to see what's required for RK3568. Target device would be Odroid-M1.
-
balbes150 do you have RK356x change in a GitHub repo/branch? - I looked but didn't see them in your account.
-
I worked in IT for 25+ years. I would make zero assumptions that any developer expected their code to run in a container on a cheap ARM board device and considered how that might affect transactional integrity in backups. That said, the rate of change in MariaDB from Kodi use is probably low enough that you will get away with our backup process. The best thing to do with backups is a) take them regularly, b) store them off the device that can go wrong, c) prove you can restore them too (not all the time, but occasionally).
-
So does LIbreElec work now with the zero 2 w?
LE11 nightly images will boot/run on the board, but will probably deliver a weak Kodi experience for two reasons. First, 512MB RAM just isn't really enough for Kodi 20 and a good overall experience and we see the same on other 512MB systems which is why the project has chosen to drop official support for all hardware with under 1GB RAM. Second, the newer RPi codebase no longer supports all the "clever but hacky" optimising done to OMX/MMAL in the past (these no longer exist in Kodi) so HEVC will be a problem. The simple reason there are deliberately no official LE 9.2.x images for the Zero2 is: we didin't want to add support for something in LE9.2 that we already dropped support for in the next release (LE10). TL/DR: You can boot LE11 but don't expect it to be great and when it isn't, don't expect support.
-
Zero2W is an awkward one for people. As it's 512MB it really needs the older LE codebase which is lighter on lower spec hardware, but at the same time it launched after we've stopped all work/effort on that codebase. It's not particularly hard to add support for it (although users in that forum thread seem to have done things the hard way) but we deliberately chose not to spin an official image with support; because we already decided to drop support for <1GB devices in LE10+ .. so we don't want add support and encourage people to purchase Zero2W boards when we effectively already discontinued support for them. It's not a bad board, but people have high expectations and it's still low-spec so we have to be sensible about the amount of work we create for ourselves.
