Jump to content

jpegqs

Members
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please give at least compiled dtb's for your TV-boxes. I tried to rebuild the image for legacy kernel with the latest Armbian-build, and now HDMI doesn't work at all. Update: The problem seems to be that the TV boxes use gmac0, the driver of which is RK630_PHY, and this driver is not enabled in linux-rk35xx-vendor.config. compatible = "ethernet-phy-id0044.1400", "ethernet-phy-ieee802.3-c22"; #define RK630_PHY_ID 0x00441400 Update2: Still doesn't work, even with this driver (preinstalled Android uses this driver).
  2. Is it like this in the dts file or did you do it another way? - ethernet0 = &gmac1; + ethernet0 = &gmac0; &gmac0 { - status = "disabled"; + status = "okay"; }; I tried this in rk3528-mangopi-m28k.dts but no luck.
  3. Armbian now supports MangoPI M28K (BOARD=mangopi-m28k BRANCH=vendor), which uses kernel 6.1. HDMI-audio works with dtb from MangoPI. But now Ethernet port doesn't work, neither with this dtb, nor with what I did for the old kernel.
  4. Most likely this: But did you notice that this is a "minimal" build? You need to install desktop packages if you need a desktop.
  5. No. I don't know what you're talking about. I didn't make any changes to armbi_root, whatever this is. Sounds like a fake flash media that reports more capacity than it actually has.
  6. There's an unsolved problem with the RK3528 video driver, it is necessary to connect an HDMI cable or turn on the monitor a few seconds after turning on the TV-box. Also, at the first boot there is nothing on screen, because first you need to enter the Armbian configuration script using ssh (over a LAN connection).
  7. With BRCMFMAC driver or BCMDHD driver? Or did it work with both drivers?
  8. The preinstalled Android on the RK3528 uses the BCMDHD driver, which is located in the "drivers/net/wireless/rockchip_wlan/rkwifi/bcmdhd" directory. As you can see, Rockchip has its own driver for Broadcom. Which is missing some patches. I'm pretty sure that these patches must include this line: {BCM4335_CHIP_ID, 1, DONT_CARE, "bcm4335b0_ag", "bcm4335"}, There's number of repositories on Github that have this line (link). But they have no history of driver updates.
  9. I tried to use the firmware from Android, it ends with this: [dhd] ======== PULL WL_REG_ON(-1) LOW! ======== [WLAN_RFKILL]: rockchip_wifi_power: 0 [WLAN_RFKILL]: rockchip_wifi_power: toggle = false wifi power off [WLAN_RFKILL]: rockchip_wifi_power: toggle = false [WLAN_RFKILL]: wifi shut off power [GPIO106-0] [dhd] ANDROID-ERROR) failed to power up wifi chip, max retry reached ** But I don't care about WiFi because: 1) I don't like anything wireless, 2) WiFi in cheap TV boxes is of crap quality. How to try the same:
  10. I have patches here, but read this thread first. Do not install it to EMMC.
  11. Are there legal reasons to request TV box manufacturers to publish the patches they used for Android? Although Chinese companies will likely ignore this, there is no real leverage over them.
  12. But the GPU (Mali-450) is 10-years old. It's not only slow, but doesn't support many OpenGL extensions, so Doom 3 refuse to run, and Quake 3 has glitches (these games are older than the GPU).
  13. The heatsink is held on by glue, you need to carefully insert a thin knife into the gap until the knife passes through the glue. I removed the heatsink today and replaced the glue with a thermal pad. Because at the factory the heatsink was poorly glued to the edge of the chip, so the chip overheats under heavy load. It's too late, but maybe it will be useful to someone.
  14. Attention: do not try to install Armbian on EMMC, you may brick the TV-box: At least until it's known why this happens and how to avoid it.
  15. That's a build with my patches and hacks. There are some problems. I haven't tried installing it because it's enough for me that it works from the SD card. I rewrote the original U-Boot and nothing broke. This means U-Boot is not signed. Maybe it's SPL. What if you write a copy of the bootloaders from Android onto an SD card, will the bootloader use them? Or does it only check EMMC. There is also this report:
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines