Posts by chewitt

Read previous posts. Nothing changed.

LE is not a conventional Linux distro, so /var/lib/alsa exists inside the read-only SYSTEM file and there is no asound.state file there because it is not required (sound is configured on each boot). There is also no need to create alsa.conf files since PCM and PT work fine with the default board based conf that we embed in the image (the "error" message that you post shows "Found hardware: gx-sound-card" which proves this is loaded). All GXBB devices have the same alsa.conf and this is proven with a large number of box/board devices, and C2 is the most-used device with the AMLGX image. I have no idea what the issue is, but I'm highly confident it's local to your iLE nstall or more people would be complaining (and it works fine here). Have you gone through the normal routine of checking cables, ports?

Quote from ian_j

should I worry about any settings I need for the SSD, Trim etc?

It's no longer 2008, SSDs are normal, and the kernel understands when trim etc. are needed.

Quote from SpookyHands

Thank you, yeah I should have mentioned I'm currently working with CE

You are definitely in the wrong forum then, and the kernel mailing list won't be interested in the problem either. Neither of us support the vendor codebase these days.

What WiFi chip is in the box?

Quote from Xcalibur.uy

For what I understad, it has to automatically chose the image but it does not. I had to edit the ini file and change the value to the correct one (q200/q201)

Incorrect. You must always configure the device-tree file in uEnv.ini

https://wiki.libreelec.tv/hardware/amlogic

The hardware problem on my board was dry solder joints on the UART pins causing noise. I resoldered the pins and I have no boot issues with upstream u-boot. Someone else forced a UART line to positive or something? (forget what, but it's commented somewhere) and that solved their problem. WeTek did a reasonable job of design and an above average (for 2015/16 standards) job of supporting devices; but ultimately they're just another Amlogic board manufactured by a Chinese ODM manufacturer (Videostrong is on the schematics). We're now 7-8 years on from the manufacturing date and some boards are showing some age related issues, which is also not unusual.

In the absence of a debug log ..

NB: LSPCON is unlikely in an nVidia ION box .. it is not a NUC. It is much older than NUCs and their LSPCON silliness.

There's a warning message about unsupported ABI versions between Xorg and the nVidia driver, and EGL fails to initialise. Those are prob. related. Not sure what to suggest other than downgrading to old releases until you find something that works.

On your end you don't really need the compatibility so use EXT4 on the drive and perhaps Transmit to shift files. SFTP is slower than NFS/SMB but the client will queue files and transfer things reliably. On the parental end .. exFAT is really the only option for plug/play with macOS unless you add third-party drivers to the OS.

The best investment(s) I made for reliable playback were some Synology NAS devices in the network. Simple to copy media to after ripping etc. and the LE device becomes a simple/dumb playback client accessing content from an SMB share and with nothing dangling/attached to the RPi(4). On the parental end I have a similar arrangement where the NAS also acts as the media device, but also a local TimeMachine destination so I don't rely upon elderly minds remembering to make backup copies on a USB device (they are good at hoarding data but backup habits evade them). Once in a while we copy new data from removable drives to the parental NAS where there's disk redundancy and also remote sync of specific dirs back to the NAS at mine to effect some off-site backup of important files.

That's a little beyond my knowledge, but FWIW i've never seen those timeouts on other G12B devices using the kernel (and u-boot) sources that LE has been using for ages. I'd suggest you post the Q to the linux-amlogic kernel mailing list.

video=HDMI-A-1:1920x1080M@60

^ You can append that to boot params in cmdline.txt and it will force initial resolution to 1920x1080 .. or perhaps 1280x720M@60 if it's an older set without FullHD resolutions.

I'd use EXT4 for Linux filesystems and simply use the network to transfer files; thus avoiding the dependency on exFAT or NTFS for Windows compatibility. There's nothing wrong with Samba/SMB for the server. We don't enable/provide NFS. You can always use an SFTP (SCP) client to transfer files over SSH.

LE is not a company. We have no products. There is no Engineering, no Project Management, no Product Management, no Marketing, .. and no Sales. We do have a support forum. You are welcome to use it (as-is) .. or not. Your choice.

It was related to reserved memory regions.

See: https://patchwork.kernel.org/project/linux-…[email protected]/

Interesting. Thanks for the tip..

LE11 uses Python 3.11.12. What are the add-ons?