Posts by Lochnair

Quote from ilmich

Lochnair my apologies, the repository was not updated. try again now.

Thank you

Thanks!

Some fiddling later and I've got the builds going. I think the only problem was that the RTL8189ES package wasn't actually added to the ADDITIONAL_PACKAGES for the device, so the modules didn't get included in the build.

After adding that it seems to work well, connected to the wifi without any difficulty
The only thing I'm not sure about if it's using the correct MAC addresses or not, the label on the box doesn't say, so I'm not sure what they're supposed to be.

dmesg_wifi.log

Quote from ilmich

Hi Lochnair , try this test build where I compiled the driver you suggested (and added firmware for usb ethernet)

https://ilmich.libreelec.tv/libreelec-12/test/

Unfortunately we have to go by trial and error because I don't have your device.

Thanks ilmich, the firmware you added looks like it made error go away.

As for Wi-Fi, no such luck yet. I think the module didn't get included in the build somehow?

Btw is the repository up-to-date? I wanted to poke around a bit myself, so I wouldn't have to take up more of your time than I have to, but ran into issues getting it to build:

Exception: Invalid package reference: dependency optee-os in package u-boot::PKG_DEPENDS_TARGET is not valid
Parallel build failure - see log for details. Time of failure: Sun Oct 27 16:20:43 UTC 2024
make: *** [Makefile:10: image] Error 1

If I remove the optee-os from the device options file, then it gets further, but fails with a patch seemingly being already applied:

patching file arch/arm64/boot/dts/rockchip/rk3328.dtsi

Reversed (or previously applied) patch detected!  Assume -R? [n] 

Apply anyway? [n] 

Skipping patch.

1 out of 1 hunk ignored -- saving rejects to file arch/arm64/boot/dts/rockchip/rk3328.dtsi.rej

Quote from ilmich

I'm happy, the work behind it was long and sometimes complicated.

I looked at the device trees in the code to see if it was something simple like the wrong GPIO pin to enable the wifi chip,
and yeah saw there was a bunch of patches to get varies things to work, so yeah I can believe it took a lot of effort

Quote from ilmich

I saw some errors related to missing firmware. Let's see what I can do.

This?

[   16.194157] r8152-cfgselector 1-1: reset high-speed USB device number 2 using dwc2
[   16.759131] r8152 1-1:1.0: Direct firmware load for rtl_nic/rtl8153b-2.fw failed with error -2
[   16.759213] r8152 1-1:1.0: unable to load firmware patch rtl_nic/rtl8153b-2.fw (-2)

That should be my USB ethernet adapter, which does work fine despite that message.
Looking through the logs I can't find anything wifi related at all. From what I found here, this driver might be needed for this chip. Not familiar with how the libreelec builds work, but since it's out-of-tree should probably be added like this package for rtl8192fu?

I'll give it a try tomorrow if I get the chance.

Just got one of these cheapo boards (branded as x96mini), and you may have saved it from going straight to landfill.
The stock Android is terrible, but LibreELEC seems to run pretty well on it, so thanks a lot!

Ethernet and Wi-Fi doesn't work, although ethernet doesn't work on stock too (ip link reports no-carrier), so might be a hardware issue on mine.
I've gotten around it with a USB ethernet adapter I had laying around.

Some notes from my messing around:

Sadly adb doesn't seem to work with either USB A-to-A (could be the cable idk) or over network, so to be able to poke around I installed TermOne Plus and used a reverse shell so I could test things from my laptop:

On laptop:

nc -l -p 2222 | tee -a shell.log

On box:

rm -f f;mknod f p; cat f | sh -i 2>&1 | busybox nc 192.168.1.8 2222 > f

I also used nc to copy files of it, as TermOne didn't seem to be able to write do internal storage or the USB stick I had in it, even when it had the storage permission enabled. Nor was ftp/ssh etc available by default.

Some files:
dmesg_libreelec.log
dmesg_stock.log
dtb_from_image.txt
dtb_from_proc.txt

Ended up dumping DTB from both image and /proc as I wasn't sure if I did it correctly from the image, both attached should they be useful somehow.

Plus a couple of pics of the board: