Jump to content

maka

Members
 View Profile  See their activity

  • Posts

    137

  • Joined

  • Last visited

 Content Type 

Everything posted by maka

  1. maka
    For lazy people like me clapper from flathub is a solution.
  2. maka
    I have a T9 2017 rk3328 box running Ubuntu xcfe many hours for downloading. There are not problems but xcfe displays lunchs himself many times and i have to close 20 or more instances of this application when checking the progress. Box is not crashed by this funny clonning. is it possible to avoid this? p.d. la test trunk
  3. maka
    yes. Things that can be tried: - DTS phy-mode = "rgmii-id"; or phy-mode = "rgmii-rxid"; - UBOOT CONFIG_PHY_REALTEK=y CONFIG_DWC_ETH_QOS=y CONFIG_DWC_ETH_QOS_ROCKCHIP=y CONFIG_DM_PMIC=y CONFIG_PMIC_RK8XX=y CONFIG_REGULATOR_RK8XX=y CONFIG_PWM_ROCKCHIP=y
  4. maka
    Can you boot in a working ethernet and then reboot to this trial?
  5. maka
    I know that told you the ID of your chip but also told you to switch to phy1 but you didn't. I think It is possible to use the generic driver but don't know if It will work. Changes in dtb must be accurate.
  6. maka
    I see this on your dts: ethernet-phy@1 { compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22"; But I think should be: ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x01>; And try to use the generic driver for ethernet.
  7. maka
    It is shown on internet how to get maskrom, serIal, and more. Also there is a clue that this box should start with firefly dtb but not stated exactly. Things are different from 1997 now and getting this working without experience is very difficult. With kernel 4.4 you could try with android dtb.
  8. maka
    You can not use android dtb. You must try without It or try the rk3399 files included in the sdcard. i cant see the second rockchip (pmic)
  9. maka
    It seems to me that Gnome is installed by tasksel because you didnt deselect it. I mean that gnome is selected by default.
  10. maka
    Have you connected the HDMI?
  11. maka
    All you need is in this thread CSC Armbian for RK3318/RK3328 TV box boards And the special uboot is there. You have a chance to brick you device so if you don't understand something don't go ahead.
  12. maka
    Armbian CSC rk3318 from @jock says: • OTG USB 2.0 port (also as boot device!)
  13. maka
    I think your driver is already in armbian, but your chip is not identified. To get it working you can identify it in the ethernet node this way: mdio { compatible = "snps,dwmac-mdio"; #address-cells = < 0x01 >; #size-cells = < 0x00 >; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; ====> compatible = "ethernet-phy-id7b74.4411", "ethernet-phy-ieee802.3-c22";
  14. maka
    The driver is well so the problem seems you are in the wrong ethernet phy. Change from phy0 to phy1 in the ethernet node.
  15. maka
    I have a T9 rk3328 tv box with rtl8723bs wifi. This chip got burned out a hot day and the box powers off when is on. There is a way to kill the sdio?
  16. maka
    There is rockchip-vdec2 in edge images that gives you support for h264.
  17. maka
    What do you mean by heavy youtube?
  18. maka
    Another reason to change is that gnome interface does not work anymore on some rockchip cpus like rk3566 and 3576.
  19. maka
    Try with armbian for quartz64 model B. Be lucky!
  20. maka
    Maybe I just deserve one like?
  21. maka
    I have made your work and mend the file that I think you are reporting to work well (I am not sure because your reports are not traceable) I hope you are lucky. rk3566-box-demo_x96x6_24.dtb
  22. maka
    Yes but is ICPLUS chip You can try this, maybe the chip is awaked mdio { compatible = "snps,dwmac-mdio"; #address-cells = < 0x01 >; #size-cells = < 0x00 >; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; ====> compatible = "ethernet-phy-id001c.c916", "ethernet-phy-ieee802.3-c22";
  23. maka
    Maybe the kernel has made the old dtbs broken. Must be that because rockchip get patches every day. You have one USB otg. Its not that enough?
  24. maka
    You almost get the same result with rtl or icplus drivers so It seems that you have another kind of chip for ethernet.
  25. maka
    Tx and Rx delay maybe wrong, compare with the android dtb if It worked or change to the box- demo values. Have you tried the icplus dtb?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept