kvvvp Posted December 17, 2025 Posted December 17, 2025 10/31/2025 в 10:28 AM, MeJune сказал: I have installed additional IR remote and OpenVFD. What kernel version are you using? 0 Quote
MeJune Posted December 20, 2025 Posted December 20, 2025 @kvvvp Build from branch v20251014 (kernel 6.17.2) 1 Quote
emor acid Posted January 8 Posted January 8 On 10/20/2025 at 5:10 PM, emor acid said: hi, Compilation error, I also decompiled the dts available for Android for reference update armbian dts ，Give to those in need use sudo armbian-add-overlay ***.dts this dts can avaible rtl8211f on h618 /dts-v1/; /plugin/; / { compatible = "allwinner,sun50i-h618"; fragment@0 { target = <&mmc1>; __overlay__ { status = "disabled"; }; }; fragment@1 { target = <&emac1>; __overlay__ { status = "disabled"; }; }; fragment@2 { target = <&pio>; __overlay__ { x98h_rgmii_pins: x98h-rgmii-pins { pins = "PI0", "PI1", "PI2", "PI3", "PI4", "PI5", "PI6", "PI7", "PI8", "PI9", "PI10", "PI11", "PI12", "PI13", "PI14", "PI15"; function = "emac0"; drive-strength = <40>; }; }; }; /* 3. 配置千兆网卡 */ fragment@3 { target = <&emac0>; __overlay__ { pinctrl-names = "default"; pinctrl-0 = <&x98h_rgmii_pins>; phy-mode = "rgmii"; phy-handle = <&rgmii_phy>; phy-io-supply = <®_aldo1>; allwinner,tx-delay-ps = <700>; allwinner,rx-delay-ps = <3100>; status = "okay"; mdio { rgmii_phy: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <1>; reset-gpios = <&pio 8 16 1>; reset-assert-us = <30000>; reset-deassert-us = <150000>; }; }; }; }; }; 0 Quote
xdatravelbug Posted January 20 Posted January 20 @kil I also own a T95H and playing around with that now. Would it be possible getting your final dts, dtb and .config for u-boot? Thanks in advance & best regards 0 Quote
kvvvp Posted January 23 Posted January 23 Build from branch v20250306. error! [ Failed to fetch SHA1 of 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git' 'tag' 'v6.12.11' - make sure it's correct ] How to remove the error? 0 Quote
Nguyễn Lân Posted January 28 Posted January 28 Dear @Nick A I used your rom "Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img.xz" date April.2025 to flash my box Vontar H618 which i checked inside the box that the chip marked "HK6334Q" So far so good the Armbian running, however the wifi still doesnt work I read all around and aware that the HK6334Q chip will need the builded rom "Support AIC8800" to get wifi working Appreciate if you or someone else helping me to find way out for this wifi? And any recently builded rom support for both Alwinner H618 and HK6334Q (or AIC8800) drivers Many thank in advance 0 Quote
Nick A Posted Thursday at 02:12 PM Posted Thursday at 02:12 PM @Nguyễn Lân The HK6334Q Wi-Fi/BT chip uses the brcmfmac4334 firmware. If your Wi-Fi chip is detected by the kernel, the dmesg log will show the names of the .bin and .txt files it is looking for. 0 Quote
Nick A Posted Thursday at 02:53 PM Posted Thursday at 02:53 PM (edited) @kvvvp I don't have any issues building from branch v20250306. Do you have docker installed? Edited Thursday at 02:59 PM by Nick A 0 Quote
Nguyễn Lân Posted Friday at 02:18 AM Posted Friday at 02:18 AM @Nick A I flashed your latest build in Dec.2025 which is named to use for Transpeed, and in addition, manually added brcmfmac4334 firmware. Wifi is working now but bluetooth. Other malfunction in previous rom version April.2025 also disappear. Thank for your time to advise me 0 Quote
BoringName Posted Saturday at 06:13 AM Posted Saturday at 06:13 AM This is a great thread. I've had a magcubic android 12 box I've been using for a while just to watch things off a USB when we stay at hotels. It looks like the one in this video but the chip ID's are different. Mine seems to be running with Samsung memory, the clock chip? is FD650 instead of FD6551 and the wifi chip is labelled as HK5236F. Most hotel TV's don't support modern video codecs so this has worked ok. But I want to look at accessing my NAS remotely and this box is a bit of a dud if you want to install your own apps. Play store doesn't work, aurora store doesn't work. Tried sideloading Tailscale and it just crashes. While doing some research I noticed it also seems to be sold under the Vontar brand so I flashed @Nick A "Armbian-unofficial_25.05.0-trunk_Vontar-h618_bookworm_edge_6.12.11_xfce_desktop.img" to an SD card and it booted up. Happy days. It appears to have ethernet but I have not plugged it in yet. No wifi though. I just have 2 questions. 1. Is there any way this can be made to boot from internal storage or do I need to keep the SD card in if I want to run Armbian on it? 2. Is there a driver available for this wifi chip and do I need to mess around updating the boot image or can I just run a command for it? I'm not a regular linux user but I've got a bit of experience messing around. I don't currently have an environment setup to build my own image but I've played around with WSL before so I could probably set something up. Thanks for everyone that has contributed to this. It's good to make use of these boxes considering how cheap they are. 0 Quote
Nick A Posted Saturday at 09:13 AM Posted Saturday at 09:13 AM @BoringName I wonder if this wifi chip is a aic8800. Try booting the x98h image. 0 Quote
John Taylor Posted Saturday at 09:32 AM Posted Saturday at 09:32 AM (edited) 25 minutes ago, Nick A said: I wonder if this wifi chip is a aic8800. Try booting the x98h image. If you can get termux app to run in android, you may be able to dump the dtb, which may give you clues as to the compatability of the chip. I have issues with some tv boxes with termux versions, but there are older versions available if the current one in playstore won't load or just doesn't work. su -c 'dd if=/sys/firmware/fdt of=<USB_PATH>/device.dtb' or simply su -c 'cp /sys/firmware/fdt <USB_PATH>/device.dtb' [Change USB_PATH as required, of course] The path /sys/firmware/fdt is correct for accessing the in-memory DTB on most running Linux/Android systems. The link http://nskhuman.ru/allwinner/krugh618.php?np=3 refers to what looks like your box or similar: "The board contains a microcircuit with the designation HK5236F - this is a hybrid microcircuit, its possible analogue is AW869A manufactured by Allwinner. AW869A is a dual-band WiFi6, BT5.2 highly integrated module, supporting WLAN 1*1 IEEE 802.11a/b/g/n/ac/ax and BT 5.2 standard, can realize WLAN/BT, has low power consumption" The links after that text give more info.... Edited Saturday at 09:42 AM by John Taylor 0 Quote
BoringName Posted Saturday at 10:08 AM Posted Saturday at 10:08 AM 45 minutes ago, Nick A said: I wonder if this wifi chip is a aic8800. Try booting the x98h image. I tried apt-get update and apt-get upgrade thinking it might grab what it needs but that was a bad idea as it will not boot at all now. So I may as well start from scratch and try the x98h image. 28 minutes ago, John Taylor said: The link http://nskhuman.ru/allwinner/krugh618.php?np=3 refers to what looks like your box or similar: The wifi chip is the same but item 3 on mine is samsung and item 7 is an FD650 which is referenced on that page as a possible alternative. It might be worth noting the units digital clock display was blank using the vontar image, I expect that was due to the chip mismatch. I'll see how the x98h image goes, if that fails I'll look into termux. No wifi isn't the end of the world as I can find a use for it just using ethernet but wifi (and bluetooth) would be nice. Thanks. 0 Quote
BoringName Posted Saturday at 11:00 AM Posted Saturday at 11:00 AM I didn't mention earlier but after I ran the update/upgrade commands I also manually updated the locale file. During the original setup I accidentally selected the wrong locale, I went into armbian config, deselected the wrong one and selected the correct one but the incorrect locale was still being referenced constantly. So I manually removed it from etc/default/locale. I thought this may have been a reason for it no longer booting and not the update/upgrade commands. I'm just explaining that so you understand why I also tried update/upgrade with the x98h image. Turns out it wasn't me messing with the locale that stopped it booting as this image also will not boot now after apt-get update, apt-get upgrade. This image originally booted ok and it seems the ethernet works better. Downloading from the commands listed above took about 20 seconds vs 30 minutes on the vontar image. But wifi/bluetooth still will not work. One other difference is when I select the bluetooth manager app it actually loaded whereas the vontar image would state something about a service not running. The app loaded but had no devices listed. I'll see how I go with termux. The play store doesn't work on it but I was able to sideload a couple of apps. 0 Quote
BoringName Posted Saturday at 11:57 AM Posted Saturday at 11:57 AM (edited) Well that was fun. Termux wouldn't load so I found an older version from 2022 thinking that version is older than the box so has a higher chance of working. That also wouldn't open until I went a bit silly and attempted to open it multiple times. Just like Mustafa in Austin Powers, once I attempted to load it 3 times in a row it would show up. Bizarre but I now have a dump of Device.DTB How do I view it properly? I opened it in notepad++ and most of it is gibberish but I can make out a few details that are a bit surprising. Namely - allwinner,h616 arm,sun50iw9p1 The label on this thing says H618 but it appears to be a H616. Where do I go to from here? Edit: I have attached the dtb file and two dumps of the file. One using fdtdump and the other using dtc. It seems the btlpm section has the same values of a device Nick referenced on page 4 of this thread. I don't know if that means anything.... Edit2: I tried "Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_xfce_desktop.img" this boots ok, ethernet works but again, no wifi/bluetooth. I'm a little surprised every image I've tried so far has mostly worked. I guess these vendors just throw together whatever parts they can get cheap but the core of the units is the same. Thanks. dtsdump.txt fdtdump.txt device.dtb Edited Saturday at 01:04 PM by BoringName 0 Quote
Nick A Posted Saturday at 03:24 PM Posted Saturday at 03:24 PM (edited) If this is AW869A chip then it uses the AIC 8800 Linux Driver. My X98H TV box has a AIC8800 chip in it. https://linux-sunxi.org/Wifi#AW869A AW869A The AW869A is a highly integrated module with Dual band WiFi6 combination solution to support 1 × 1 IEEE 802.11b/g/n/ac/ax WLAN standards It uses the aic8800 firmware. A driver can be found at AIC 8800 Linux Driver. You'll need to compare the GPIO settings. Your Android dts uses HEX the mainline kernel is using DEC. https://www.rapidtables.com/convert/number/hex-to-decimal.html?x=12 rfkill { compatible = "allwinner,sunxi-rfkill"; status = "okay"; chip_en; power_en; pinctrl-0 = <0x63>; pinctrl-names = "default"; phandle = <0xcc>; wlan { compatible = "allwinner,sunxi-wlan"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; wlan_busnum = <0x01>; wlan_power; wlan_regon = <0x23 0x06 0x12 0x00>; wlan_hostwake = <0x23 0x06 0x0f 0x00>; wakeup-source; phandle = <0xcd>; }; bt { compatible = "allwinner,sunxi-bt"; clocks = <0x0e 0x04>; clock-names = "osc32k-out"; bt_power; bt_rst_n = <0x23 0x06 0x13 0x01>; phandle = <0xce>; }; }; btlpm { compatible = "allwinner,sunxi-btlpm"; status = "okay"; uart_index = <0x01>; bt_wake = <0x23 0x06 0x11 0x00>; bt_hostwake = <0x23 0x06 0x10 0x01>; wakeup-source; phandle = <0xd0>; }; Mainline dts: https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L87-L95 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L182-L200 https://github.com/NickAlilovic/build/blob/666dc0fabd8a284ccf50d784f6bd0bf948dd073d/patch/kernel/archive/warpme-6.12/2001-arm64-dts-allwinner-h618-add-x98h.patch#L278-L297 The specific values <0x23 0x06 0x12 0x00> generally map to: 0x23: The controller or bank ID: pinctrl@300b000 { phandle = <0x23>; 0x06: The specific GPIO pin number: In Allwinner's pinctrl driver, banks are 32 pins wide. The formula is: (Bank_Letter_Index * 32) + Pin_Number 1. The Bank Index Map Bank Index PA 0 PB 1 PC 2 PD 3 PE 4 PF 5 PG 6 PH 7 PI 8 0x12: The active-high/low flags or drive strength. In the 3-cell GPIO format used by Allwinner (sunxi), the third cell (e.g., 0x12) is a bitmask that defines the electrical properties of the pin. To decode 0x12 (which is binary 0001 0010), you break it down into bits: 1. Bitmask Breakdown for 0x12 Bit 0 (0x01): Active Polarity. 0 = Active High. 1 = Active Low (Our bit 0 is 0, so this is Active High). Bit 1 (0x02): Open Drain / Open Source. 0 = Push-Pull. 1 = Single-ended/Open-Drain (Our bit 1 is 1, so this is Open-Drain). Bit 4 (0x10): Internal Pull-up. 0 = No pull-up. 1 = Pull-up Enabled (Our bit 4 is 1, so this is Pull-up Enabled). Summary of 0x12: This pin is configured as Active High, with an Open-Drain output and an internal Pull-up resistor enabled. 0x00: Reserved or additional configuration. In Allwinner-based systems (like the H6 or H616), this value is defined in the GPIO controller's device tree binding documentation within the Linux kernel source code. The structure is documented in the kernel under Documentation/devicetree/bindings/pinctrl/allwinner,sun4i-a10-pinctrl.yaml Edited Saturday at 05:36 PM by Nick A 0 Quote
BoringName Posted Saturday at 11:40 PM Posted Saturday at 11:40 PM (edited) 8 hours ago, Nick A said: You'll need to compare the GPIO settings. Your Android dts uses HEX the mainline kernel is using DEC. Ok, just so I'm following you correctly. This line in my DTS dump bt_rst_n = <0x23 0x06 0x13 0x01>; In decimal is <35 6 19 1> In the patch you linked the line above should be matched to these values at line 293? reset-gpios = <&pio 6 13 GPIO_ACTIVE_LOW>; /* PH13 bt_rst_n */ So I should change this to reset-gpios = <&pio 6 19 GPIO_ACTIVE_HIGH>; /* PH13 bt_rst_n */ Repeat for all the other values to match the DTS dump then build the image? Is there a way to set these values at the command line without having to build an image? edit: Actually my high low flag is 0x13 which is 0001 0011. This is read from right to left isn't it? So Bit 0 is actually a 1 which means in the example above I should set it to the following? reset-gpios = <&pio 6 19 GPIO_ACTIVE_LOW>; /* PH13 bt_rst_n */ Sorry I'm probably getting in a little over my head.... Edited Sunday at 12:01 AM by BoringName 0 Quote
Nick A Posted Sunday at 12:25 AM Posted Sunday at 12:25 AM (edited) @BoringName Looks right. You can decompile the dtb into a dts.. edit the dts and compile it again. You will find it in the /boot directory. dtc -I dtb -O dts -o mainline_edit.dts your_mainline_file.dtb dtc -I dts -O dtb -o modified_mainline.dtb mainline_edit.dts Edited Sunday at 12:26 AM by Nick A 0 Quote
BoringName Posted Sunday at 12:34 AM Posted Sunday at 12:34 AM (edited) 14 minutes ago, Nick A said: You can decompile the dtb into a dts.. edit the dts and compile it again. You will find it in the /boot directory. Excellent, thanks. One more thing. I just reloaded the x98h image. When I previously loaded this image, I didn't check dmesg like I did with the other images. They had no mention of Wifi at all but this one does. It seems to start enabling wifi but then fails here rwnx_load_firmware :firmware path = /lib/firmware/aic8800_sdio/fw_patch_table_u03.bin rwnx_load_firmware: fw_patch_table_u03.bin file failed to open wrong size of firmware file aicbt_patch_table_alloc fail edit: So lib/firmware/aic8800_sdio/fw_patch_table_u03.bin does not exist which probably explains that error. I'll see if I can get my hands on that file and see if that fixes things before I worry about compiling/decompiling stuff. Edited Sunday at 12:41 AM by BoringName 0 Quote
BoringName Posted Sunday at 04:16 AM Posted Sunday at 04:16 AM (edited) We have progress, sorry I feel like I'm spamming this thread a bit but at least I have a result. Wifi is now working. Still no bluetooth. For anyone playing at home with this box, to get to this point I installed x98h image from Nick's github. I then downloaded the following files from walnutpi's github fw_patch_table_u03.bin fw_adid_u03.bin fw_patch_u03.bin fmacfw.bin aic_userconfig.txt I copied these files to the device and placed them in /lib/firmware/aic8800_sdio/ Then shutdown the unit and powered it back up. Doing a restart isn't enough, you need to shut it down. So just bluetooth to go. The only related message seems to be sdio_err: <aicwf_sdio_bus_pwrctl,1380>: bus down Which I expect will probably require me to update the dtb settings as previously discussed. Happy to settle with just the wifi working but I'll take a shot at getting bluetooth going because I may as well finish what I started. Thanks for the help thus far. edit: I've tried decompiling the /boot/dtb/allwinner/sun50i-h618-x98h.dtb file but I can't find any of the relevant info to change in the dts file. It's like the sections listed in the patch file linked earlier are not there at all. I understand it's in a different format but as an example. The following section line 278 to 297 +&uart1 { + pinctrl-names = "default"; + pinctrl-0 = <&uart1_pins>, <&uart1_rts_cts_pins>; + uart-has-rtscts; + status = "okay"; + + bluetooth { + compatible = "allwinner,sunxi-btlpm"; + // max-speed = <1500000>; + + clocks = <&rtc 1>; + clock-names = "lpo"; + vbat-supply = <®_dldo1>; + vddio-supply = <®_dldo1>; + enable-gpios = <&pio 6 19 GPIO_ACTIVE_HIGH>; /* PH19 bt_power */ + reset-gpios = <&pio 6 13 GPIO_ACTIVE_LOW>; /* PH13 bt_rst_n */ + device-wakeup-gpios = <&pio 6 17 GPIO_ACTIVE_HIGH>; /* PH17 bt_wake */ + host-wakeup-gpios = <&pio 6 16 GPIO_ACTIVE_HIGH>; /* PH16 bt_hostwake */ + }; +}; I've tried searching the dts file for "uart1", "bluetooth", "bt", "btlpm", "lpo", the hex equivalent of the values above, all the different value names etc... of the small amount of results that do show up, most of them are not even remotely close to matching anything above. "usart1" does have a section detailing the pins and rtscts but it seems that bluetooth section just isn't there. This is just one example, lines 87 to 102 don't appear to be there either. There is some values for vcc-3v3 but that's it. I'll probably have to look at updating the values in the patch file and building an image. Edited Sunday at 06:17 AM by BoringName 0 Quote
BoringName Posted Sunday at 10:24 AM Posted Sunday at 10:24 AM (edited) Bluetooth now working, no compiling required via hciattach. I don't know how much of this is necessary because I generally don't know what I'm doing. But here goes. Apparently hciattach is a legacy app that requires the firmware to be in /etc/firmware so I made a folder and setup a symlink before running the hciattach. <NOT REQUIRED> sudo mkdir -p /etc/firmware <NOT REQUIRED> sudo ln -sf /lib/firmware/aic8800_sdio/*.* /etc/firmware sudo hciattach -s 1500000 /dev/ttyS1 any 1500000 flow nosleep <NOT REQUIRED> sudo hciconfig hci0 up Bluetooth should be available now. You can test it with sudo hcitool -i hci0 scan This will display any devices in the area the bluetooth adapter has detected. I had installed armbian-firmware package so that might also be required but I doubt it. I will flash a new image and start from scratch just to make sure everything I've stated works on a fresh install and then update the thread. Edit: I tested it on a fresh image and the only command required for bluetooth to activate was the hciattach line. I couldn't figure out how to do strikethrough in the code block so I just listed added the "NOT REQUIRED" info. I didn't want to remove them in case it helps someone else. The firmware files I mentioned in a previous post need to copied over and the device powered down before running the hciattach command. The hciattach commands do not persist through a reboot so I need to figure out how to get this to run on startup, hopefully the easy part. Thanks for all the help. Hard to beat that feeling when you spend hours troubleshooting something and it fires up for the first time! Edited Sunday at 01:33 PM by BoringName 0 Quote
BoringName Posted yesterday at 01:04 AM Posted yesterday at 01:04 AM (edited) Installed to the EMMC with armbian-install and no issues it all. Took about 10 minutes and now boots from the EMMC with no SD card inserted. I think I paid $35AU for this thing and it came with the remote, a bluetooth keyboard, HDMI cable and power supply. Absolute bargain when you compare it to the current price of Rasperry PI's especially when it comes with it's own case and internal storage. Thanks to everyone who contributed to getting these images out there, it's fantastic. I've also got the IR remote working. I followed rafman's post but this didn't fully work for me. It allowed the remote to work and I could see it was working with ir-keytable -t but the desktop and any open apps wouldn't respond to it. The solution was to copy the toml file to /etc/rc_keymaps/magcubic.toml then edit /etc/rc_maps.cfg and add the following to the bottom of the file * rc-empty <whatever_name>.toml * rc-empty magcubic.toml Adding the line to the rc.local file was not required. I've attached a picture of the remote and the toml file I created. I didn't map the buttons in the top right section as this remote has a learning function and you're supposed to learn the codes from your TV remote. But here are the codes my remote was using for these buttons by default. Power 0x1f1 Set 0x1f2 TVIN 0x1f3 VOL- 0x1f4 VOL+ 0x1f5 Edit: If you are going to use on media player apps you will probably want to edit the toml file and change "KEY_OK" to "KEY_SPACE". OK doesn't let you select things with the OK button but SPACE does. magcubic.toml Edited yesterday at 02:01 AM by BoringName 0 Quote
BoringName Posted yesterday at 08:59 AM Posted yesterday at 08:59 AM (edited) And now I've hit a road block. I can't get video acceleration to work. VLC just displays a blank screen no matter what output I select and MPV playback is very stuttered. I wanted this box to act as an Emby client, got it all configured to load emby via the ir remote and got all the functionality working but when I play a video it's so choppy it's basically unwatchable. 576p is almost bearable, 1080p is not. I've spent all day on it and got nowhere. I've followed the instruction in this post but it made no difference - Repository for v4l2request hardware video decoding (rockchip, allwinner) edit: Ok the instructions in that post did actually work, I just didn't notice one of the commands had not run properly when I first tried it. Video playback in mpv is buttery smooth, now I just need to figure out how to get emby to do the same. Edited yesterday at 10:33 AM by BoringName 0 Quote
robertoj Posted 17 hours ago Posted 17 hours ago 16 hours ago, BoringName said: edit: Ok the instructions in that post did actually work, I just didn't notice one of the commands had not run properly when I first tried it. Video playback in mpv is buttery smooth, now I just need to figure out how to get emby to do the same. You can't use emby and the h618 acceleration with ffmpeg-v4l2request... you need to make emby work under Debian, and tell emby to use mpv. 0 Quote
BoringName Posted 16 hours ago Posted 16 hours ago (edited) 5 hours ago, robertoj said: You can't use emby and the h618 acceleration with ffmpeg-v4l2request... you need to make emby work under Debian, and tell emby to use mpv. I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video I've set it to use mpv but it seems the emby package has it's own version of mpv and ffmpeg baked in as the versions reported in the mpv.log are different and it fails to use drm, it seems the following errors are the problem. [ 0.028][v][libmpv_render/drmprime] drmprime hwdec requires at least one dmabuf interop backend. [ 0.028][v][libmpv_render] Loading failed. [ 1.422][v][ffmpeg] Unable to open any dma_heap device [ 1.422][e][ffmpeg/video] hevc: Failed to set destination format: S265 1920x1080 [ 1.422][e][ffmpeg/video] hevc: Failed setup for format drm_prime: hwaccel initialisation returned error. When I launch the same file directly in mpv, it plays fine and doesn't have the errors above. The system has mpv version 0.35.1 but emby reports using 0.38.0-dirty. Same with ffmpeg and all the associated lib files, they are all higher versions and I can't find duplicates in the system so I believe they are packaged as part of the emby app so I really doubt it's something I will be able to fix unfortunately. Tried Kodi and that's missing all the acceleration settings. Jellyfin client doesn't work with an emby server anymore. Just to attempt to keep this on topic, I don't suppose there is anything I can config with the image that might resolve the dma_heap errors? edit: I figured out a solution, emby lets you configure an external player. I just set that to /usr/bin/mpv and it works. Edited 11 hours ago by BoringName 0 Quote
Brow Mosh Posted 3 hours ago Posted 3 hours ago Hi guys. Just sharing my experience. After reading @Johan S success story, I bought a Transpeed 8K 4GB 64GB. (https://www.aliexpress.com/item/1005005534455685.html) Apparently, mine is different, and nothing, I've tried, worked. But sharing is caring, so here we go. 🧩 DEVICE SPECIFICATION & FULL FINDINGS SUMMARY 📦 Device Identity Model: Transpeed 8K618‑T (or clone variant) SoC: Allwinner H618 (sun50i‑h618 family) CPU: Quad‑core ARM Cortex‑A53 DRAM: 4 GB DDR3 PMIC: AXP1530 (BOOT0), AXP313 (BL31) Boot Chain: BOOT0 → BL31 → Vendor U‑Boot 2025 → Kernel 🧠 DRAM & Bootloader Behavior DRAM training succeeds at 648 MHz DRAM type: DDR3 DRAM size: 4096 MB Bootloader reports chip ID 0x2100 BL31 applies CPU errata 855873 & 1530924 Vendor U‑Boot loads: Kernel DTB Initrd (always) → cannot be disabled Vendor U‑Boot ignores Armbian boot scripts and forces initramfs boot 💾 STORAGE 1. SD Card Slot — NON‑STANDARD HARDWARE This is the root cause of all Linux failures. BOOT0 reports: card no is 2 → SD wired to MMC2, not MMC0 sdcard 2 line count 8 → 8‑bit bus width (SD normally max 4‑bit) MMC 5.1 → SD treated as eMMC, not SD Speed: 50 MHz (HSSDR52/SDR25) Vendor U‑Boot handles it Mainline Linux cannot Linux symptoms: sunxi-mmc ... data error send stop command failed lsblk hangs ls /dev/mmcblk* hangs Kernel freezes on MMC access Armbian drops to initramfs MiniArch boots but freezes shortly after Conclusion: The SD interface is electrically non‑standard and incompatible with mainline Linux. 2. eMMC Detected as /dev/mmcblk2 Stable under vendor bootloader Linux could use it — but SD instability prevents reaching userspace 🖥️ DISPLAY HDMI DDC errors: pinctrl_get for HDMI2.0 DDC fail tv_power failed Likely missing regulators in DTB HDMI output unreliable 🌐 NETWORKING Ethernet PHY: AC300 Should work under Linux if system boots Wi‑Fi: AIC8800 (doable. Android is rooted, so just copy '/aicsdio', 'aic8800_fdrv.ko' and 'aic8800_bsp.ko') 🧪 IMAGES TESTED Armbian Armbian-unofficial_25.05.0-trunk_Transpeed-8k618-t_bookworm_edge_6.12.11_server Armbian-20240726-unofficial_24.8.0-trunk_Transpeed-8k618-t_bookworm_edge_6.7.12_server Results: Always dropped to initramfs Could not mount /dev/mmcblk0p2 init=/bin/sh ignored (because vendor U‑Boot forces initrd) SD access hangs kernel No path to userspace MiniArch MiniArch-20240715-6.18.3-board-h618.transpeed-8k618-t-SD-Image MiniArch-20240715-6.18.3-board-h618.vontar_h618-SD-Image Results: Kernel boots Reaches userspace Shows login banner Then freezes due to SD/MMC errors lsblk and ls /dev/mmcblk* hang MiniArch boots further than Armbian, but still fails due to the same SD hardware issue. 🖧 UART TESTING Tried multiple UART speeds: 115200 (default) 921600 (Android kernel switches to this mid‑boot) Other speeds (varied) Findings: Vendor U‑Boot uses 115200 Android kernel switches to 921600, causing “garbage” output MiniArch & Armbian stay at 115200 UART is stable — not the issue 🧪 BOOT PARAMETER TESTING Tried: init=/bin/sh root=/dev/ram Removing root= Editing armbianEnv.txt Editing extlinux.conf Disabling overlays Changing DTBs Adding earlycon Adding rootwait Adding rootdelay=10 Findings: Vendor U‑Boot ignores Armbian boot parameters Always loads initrd → always enters initramfs init=/bin/sh never executed under Armbian MiniArch does honor init=/bin/sh, but MMC hangs prevent installation 🧨 ROOT CAUSE SUMMARY The device has non‑standard SD/MMC wiring: SD slot wired to MMC2 (normally eMMC controller) SD slot uses 8‑bit MMC mode SD slot uses MMC 5.1 protocol SD slot uses 50 MHz high‑speed timing Vendor kernel supports this Mainline Linux does not This causes: Armbian initramfs failures MiniArch kernel freezes MMC access hangs eMMC inaccessible No way to install Linux No way to reach userspace reliably This is a hardware design incompatibility, not a software bug. 🟩 FINAL ASSESSMENT The device is not compatible with mainline Linux, because: SD interface is wired incorrectly Vendor U‑Boot forces initramfs MMC controller hangs under mainline drivers eMMC cannot be accessed due to SD instability DTB regulators missing HDMI DDC errors (Wi‑Fi requires proprietary driver Android works because it uses the proprietary Allwinner MMC driver. Mainline Linux does not.) 🟦 Images 0 Quote
robertoj Posted 1 hour ago Posted 1 hour ago 14 hours ago, BoringName said: I got emby installed and working. Made it launch with the ir remote, it was all perfect until I tried to play a video Oh so I stand corrected... I was going from information on the website: I don't see a Linux client, and in other sites: emby was open source but now it's not 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.