@lex

Members
  • Content Count

    447
  • Joined

  • Last visited

2 Followers

About @lex

  • Rank
    Embedded member

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

1762 profile views
  1. @lex

    Updated htop

    According to this: https://github.com/armbian/build/blob/master/packages/bsp/helios4/90-helios4-hwmon.rules , it is not related to CPU temp. My guess is just a missing kernel config.
  2. @lex

    Updated htop

    Please check if you have: cat /sys/class/hwmon/hwmon0/name
  3. @lex

    Updated htop

    The path is hard coded in the HTOP for the cpu temp. I think the problem is that some boards (kernel) use the hwmon driver and sometimes different kernel config. I think the best approach would be to traverse /sys and try to find the label for the cputemp / gputemp / regulators, etc.. But what exactly look for to be Universal? In my x64 for example, same Intel, different kernel configs (server vs desktop) points to different locations: cat /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp2_label Core 0 cat /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp3_label Core 1 cat /sys/devices/platform/coretemp.0/hwmon/hwmon2/temp2_label Core 0
  4. I had the impression it was the other way around. Have you had success with lima? or anyone? Anyway, Looking forward to seeing the @NicoD's video about tee panfrost experience.
  5. i have had success with OV5640 on FE HW (H3,H5,A64, possibly H2+) You should check camera schematic of your board if it matches the same way FE handle the camera. I think I2C must be tied to CSI or you cannot communicate with the sensor. vfe_v4l2 driver seems to be from Android and has additional Image Processing in it. (ISP) (Kernel 3.x and 4.4.y, perhaps 4.9.y). I think there is still no support for OPIs, BPIs and some others for the mainline OV5640 / OV5647 and you have to use the Android kernel way or until someone writes the code.
  6. I have some experiments with legacy kernel 4.4 before the BPI updated the kernel source (changes on eMMC and possibly Wifi, my board is too old to check the new features), I don't know if it has been improved or not. Recently, the mainline stable kernel 4.20 has reached a very stable condition and you can even run KODI on A64, thanks to jernejsk's work. I think the problem is on the new eMMC version. I can't help on this since i don't have this hw revision. Tip: try to build Armbian without enabling eMMC and/or Wifi and see what happens. Grab the complete boot log, i think there are others here with the new hw revision that can help.
  7. This weekend I was revising and testing the OV5640 for some A64 boards. To enable the Camera (OV5640) on NanoPi A64 for the mainline kernel you have to update the following: * DT * GPIO-I2C Here is the excerpt : Kernel config: CONFIG_I2C_GPIO=m CONFIG_VIDEO_OV5640=m CONFIG_VIDEO_SUN6I_CSI=m
  8. Hmm. maybe you mean CPU version. A64 is the old one and R18 is the new one, they are essentially the same. Maybe you mean eMMC version , the new one has a newer eMMC version and you should run with a newer Kernel version that handles this new eMMC.
  9. Maybe when you install the games it updates the libGl or libEGL. I think this would happen to all distro but you could try to freeze (somehow) the libs on Armbian which has symlink to libmali. As a suggestion, you could install symlinks and find the libs and its symlink. Try on the first install: symlinks /lib/aarch64-linux-gnu Take notes and then do it again after reboot.
  10. That's the reason. It updates to new libEGL and breaks the symlink to libmali. If for some reason the new lib is installed you have to manually re-create the symlinks, or just don't update.
  11. Another interesting thing, i have been running my kernel without any patch related to the issue and have not seen any problem on my NanoPi A64. Although i don't usually run for a long time so the issue could manifest in time. I had a comment about this on linux-sunxi list a long time ago, maybe i was just lucky. I will have a look at your PR.
  12. Do you have an RTC backup battery attached to your Pine64?
  13. I see now. Then "reset" is not working properly, i suppose. stmac did not reset. If someone can check, do a cold boot, do a reboot and do a reboot again and check eth0.
  14. @froezus I don't see your u-boot patched , it is the only ATF that should be patched?
  15. I changed the timeout value from 100 ms (stmac had 10 ms and now has 100 ms) to 200 ms to see if could help,i get stmac crashes with this value. If i issue a sudo reboot from this session (100 ms default) again the OPI One Plus reboot normally. Changing u-boot version ethernet works on reboot but not hdmi. I also patched only ATF and not u-boot and i get random results, sometimes it works some times not. I am not sure u-boot must be patched.