1) Sure, you can use whatever USB wifi is otherwise supported on Linux. Note that it's good to do a little research before you buy wifi dongle. Dongles, which have no mainline driver, are not supported in LE. If in doubt, tell here which chip is used and I can check.
Posts by jernej
-
-
I have LTS version. I'll try to fix ethernet before LE11 stable is released, but no promises.
-
tested latest LibreELEC-H6.arm-11.0-nightly-20221203-164bd92-beelink-gs1.img.gz, still unable to boot, same error.
Sorry for late response, but obviously I took some time off LE. I'll surely work on this issue before stable is released.
Is openvfd module included in kernel for Tanix TX6 in development release?
No, but I2C bus is exposed and you can write script to drive display. I have some python script example, but it wasn't tested on LE. I can provide it to you as example, if you want.
Do the nightly images for the H6 include phy ethernet driver support for the Orange Pi 3 LTS?
No.
How it can be possible? What mechanism or tricks do you use?
Simple. While kernel is really 64-bit, userspace in 32-bit. In fact, widevine is the only reason why we release all ARM images with 32-bit userspace.
-
I'm not expert in passthrough at all and I only test it with video playback. I suggest you ask this in more general subforum.
-
Orange Pi 3 LTS
While I have it on my desk, I didn't add support for it just yet in LE. It needs Ethernet PHY driver and wifi is totally unsupported by mainline Linux. I plan to add PHY driver, but no for wifi.
H6 (SoC on OPi 3 LTS) has solid support in LE. Missing features are analog audio output (I have wip driver for that, but no time to fix minor issues) and 10-bit display pipeline. This means that 10-bit HEVC videos are correctly decoded but they are displayed as 8-bit, so some banding can be visible in HDR output.
-
offbeat next nightly image will have latest kernel which includes SD card voltage adjustment fix. Can you please test? If it still doesn't work, I guess I'll have to dig into ATF issue.
-
offbeat can you check board version? Test on 1.0 didn't show any issues. From what I've been told, there is also 2.0.
Regarding network issue - It seems that other dwmac based drivers also experience it based on quick google search, but that doesn't necessarily mean that the issue is in common code.
While there is kernel bugzilla, I'm not sure how much is used by netdev people. ML is still best way to go.
-
If board is powered on, it should bring up power menu, where you can select power down. If board is powered down, it will power it up. But note that it also depends on U-Boot and Crust firmware. If you have problems, test it first on freshly written image to SD card.
-
Use something that is already supported by Linux kernel, e.g. without out-of-tree drivers. Integrated wifi and both of your USB devices are Realtek based. Sad thing is that only a handful of Realtek wifi adapters are supported by upstream Linux kernel and yours are not among them. Before you ask, we don't accept out of tree wifi drivers anymore and we are reducing number of existing ones. It's not worth the hassle.
There are many wifi related topics on this forum, use search.
-
Sorry to say, but I went over H6 DDR3 driver so many times that I don't think I can find any important difference between mainline and vendor driver anymore. Actually, there is one pretty big difference in code for checking bus width and rank, but code based on vendor driver was unreliable. Once that was fixed, most H6 DRAM issues have gone away. You can try getting additional output with adding #define DEBUG 1 at the very top (before includes) of H6 DRAM driver in U-Boot and look for additional info. You can also test older versions of U-Boot, but that's most I can help you with.
-
And Kodi upscaling seems to take literally no effort on the CPU/GPU.i
That's true when using DRMPRIME rendering, which is default for all boards except Generic (I think). DRMPRIME renderer uses DRM planes for video rendering, which are implemented via dedicated HW blocks inside display pipeline. So this is basically the third option, which is actually more common than GPU scaling on ARM boards and most efficient too. Usually there is little to no scaling options in HW, so quality is what it is.
-
U-Boot is overwritten by install2emmc. Anyway, using different U-Boot is not recommended. AFAIK U-Boot from Armbian doesn't support any suspend/resume features.
-
Does anybody know if h616 boxes are supported now ?
If you can't find it among nightly images, then no. While H616 seems nice on paper to many users, developers are not that interested in it, so there is basically no progress, at least in areas important for LE (video/audio).
-
Why would you need to go through Armbian? Mentioned install script will completely reformat eMMC, no matter what is on it.
-
Not directly and there is not enough information for each detail, so some guess work is needed.
-
Certainly problem with usb controller
No, problem is wrong DT file (board description). Each board is wired differently, like USB ports and their power supplies. But modifying or writing DT file for board without schematic is very hard. Certainly out of scope of this forum.
-
You can try with Beelink GS1 image if it is better fit. If not, you'll have to provide proper dtb file or modify existing one on the fly with dt overlays. However, it's not easy to figure out what to enable and how things are linked together, especially if you've never done that.
-
what I want to tell you is to install the version that brings the patch so that ethernet works in the 3 LTS and the ethernet works
OPi 3 LTS is on my TODO list. I obtained it recently, so testing is not a problem anymore. But I have to deal with some other things before. Linux 5.10 (used in LE10) doesn't have appropriate Ethernet PHY driver for LTS and it possibly has other issues with ethernet reset line and PMIC, so LE10 OPi3 image doesn't work on LTS, at least not well, as you already found out. Even if I fix it, I'm not sure how many LE10 point releases will be there.
