RPi4 is no longer unobtanium so pricing is returning to normal. The 2GB board it's not the $20-30 device you're looking for, but if you want something super reliable and no issues or guesswork on software support.. that's the device.
Posts by chewitt
-
-
This is the current also conf we embed: https://github.com/chewitt/alsa-l…sound-card.conf
This is an older version: https://github.com/chewitt/alsa-l…sound-card.conf
The older conf has all the analogue device pcm extras needed for speaker-test to work with multiple channels. In the absence of all of them (as per the current conf) speaker-test will only output stereo since this is all the default pcm device supports/exposes. This is 100% same on my system; which happily outputs multi-channel PCM and PT on the HDMI connection (which is not the analogue pcm device). So kudos for playing "spot the difference" .. but this difference is not the thing you are looking for.
NB: The only reason the older conf exists was an earlier attempt to work around a driver not-technically-a-bug where alsa does not pass mixer controls correctly. This patch hacks a fix: https://github.com/chewitt/linux/…702a070dc71c133
I'd ask that you play with cables and AVR/TV ports. Multi-channel output depends on the ELD data read from EDID/HDMI and the usual "but it works in the legacy image!" claim means little due to a) the upstream codebase being 100% different, and b) the amount of hideous stuff the legacy kernel ignores/overrides/fakes to work around TVs and monitors that provide bad/broken EDID data.
And yes the greatest percentage of AMLGX users are probably using default 2-channel output. However, enough folks have complained about the earlier multi-channel state (that the kernel patch resolved) that I know people are using multi-channel output.

-
-
Can you retest with a current nightly image .. I believe the kernel should be newer than 6.1 by now. Let's see if that changes anything..?
-
It makes no difference. VNC relies on copy/cloning the windowing system output. LE does not use a windowing system. So VNC would need an interface that taps directly into the zero-copy (designed not to copy/clone content) display pipeline.
-
You cannot select between the AVR or the de-embedder in Kodi, it will only offer "the" device it sees on the HDMI connection. If the splitter claims to be passing-through the properties of the upstream device or it's injecting properties .. no idea. If the splitter device is giving you problems perhaps remove it and attach the HTPC direct to the AVR, then run "getedid" to capture the EDID from the AVR and set things up so the HTPC/Kodi always sees the AVR as direct-connected. Then place the de-embedder back in the chain and hope it all still works.
-
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?
-
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.
-
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?
-
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
-
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.