Jump to content

Heisath

Members
  • Posts

    308
  • Joined

  • Last visited

Other groups

Contributor/Maintainer

1 Follower

Profile Information

  • Gender
    Male
  • Location
    Germany

Recent Profile Visitors

4397 profile views
  1. You can try to add new thermal paste or a new thermal pad between the heat spreader and the chip. This helped for some of my boards in the past.
  2. Are you using dvfs on the board? IIRC changing the CPU core speed did lead to some problems with timekeeping. I think we had a patch for that years ago. Maybe try a newer kernel?
  3. This is fixed with PR https://github.com/armbian/build/pull/5392
  4. I will investigate this - probably once again either broken fan patch or mismatched device tree / kernel information.
  5. @Mangix because u-boot was maintained by the kobol team, which have given up supporting both their boards. I do not currently have the time to switch to another u-boot and test / fix upgrade and new image scenarios. But there are only a few patches https://github.com/armbian/build/tree/master/patch/u-boot/legacy/u-boot-helios4 and so it might be possible to go upstream. You are welcome to try and send a patch. I might also try, once I find time + motivation for it.
  6. Hi, I just tested this on my helios4 with linux kernel 5.15.80 uname -a: Linux helios4 5.15.80-mvebu #22.11.1 and both pwm controllers work just fine. Have you tried going back to make sure it is not a HW problem? Or tried swapping fans around? Also make sure your /dev devices symlink to the correct path: /dev/fan-j10 -> /sys/devices/platform/j10-pwm/hwmon/hwmon3 /dev/fan-j17 -> /sys/devices/platform/j17-pwm/hwmon/hwmon4 EDIT: I just did a fresh build from armbian master, 23.02.0-trunk. PWM on both channels working fine. uname -a Linux helios4 5.15.88-mvebu #trunk SMP Sat Jan 14 13:47:38 CET 2023 armv7l GNU/Linux So you'd need to provide more info on how you built your kernel version to get to this problem.
  7. From the error messages I would expect it to be the card. I have a similar problem but mine is a worn out sd card slot, so I just boot from a different medium now.
  8. Ok I will try to reproduce and look at the patch. Does anyone else experience the same? 5.15 has been out for a while.
  9. Ok I checked this and there is no uboot config for 2019 uboot helios4 which has SATA support enabled. Not sure how to best go forth here.
  10. Ok I'll look into it this afternoon.
  11. ClearfogPro and Helios4 images are working ok. ClearfogBase I expect to do the same (not explicitly tested). @TheLinuxBug one improvement for the testing form would be a checkbox for "does not apply" on the feature section. My boards don't have wireless but no options really matches
  12. Yeah that should be no problem. Just compare these two files: (Clearfog configuration) https://github.com/armbian/build/blob/master/config/sources/families/include/mvebu-clearfog.inc (Helios4 configuration) https://github.com/armbian/build/blob/master/config/sources/families/include/mvebu-helios4.inc Just provide a PR with added targets here https://github.com/armbian/build/blob/master/config/sources/families/include/mvebu-helios4.inc#L11 Test it by building locally and we'll have sata uboot on the next release.
  13. Good to know. I am currently bringing mvebu-edge to 6.0.y, but that will take a bit more time.
  14. PR is fine. Just adjust the config, test it and make PR. Even these small things help. As for why it is not in the kernel atm probably nobody added it
  15. @Dee2022 yeah and a fix is already on the way - read the posts above yours
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines