Jump to content

Dee2022

Members
  • Posts

    4
  • Joined

  • Last visited

  1. @Mangix Thank you @FredK same to you. I'm now running Armbian 24.2.1 Bookworm with Linux 6.6.16-current-mvebu. And really am in a doubt to perform: sudo apt upgrade....
  2. @FredK Same here. I didn't know what to do with the .kwb images.
  3. Hi all, Today I upgraded armbian on my Helios 4. I wish I hadn't. The system won't boot anymore. Received the "Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid" message. Any hints on trying to recover from this? To be honest, I'm stuck at the moment. I recovered from this through the following steps: Get the 'original' image (although dated) from the Helios site (https://wiki.kobol.io/helios4/) Created another sd card Booted And had access again. The hardest part was recoving the old lukskey for opening the encrypted partitions from the raid array.
  4. Hi everybody, This is my first post over here, so apologies if this is not in the right format. I discovered the following issue with the fans of my Helios4 Armada388 system yesterday, after upgrading to the latest version of OMV based on Armbian 22.08.4 Bullseye with Linux 5.15.72-mvebu: The fans were spinning very fast and thus making a lot of noise. This was a new issue. I looked at the fancontrol utility and noticed that the config was broken on Armbian 22.08.4 Bullseye with Linux 5.15.72-mvebu From the logfiles: Oct 12 07:23:36 helios4 kernel: [ 14.629414] hwmon hwmon2: temp1_input not attached to any thermal zone Oct 12 07:23:36 helios4 kernel: [ 14.629422] lm75 0-004c: hwmon2: sensor 'lm75' Oct 12 07:23:36 helios4 kernel: [ 15.520811] pwm-fan j17-pwm: error -EBUSY: Could not get PWM Oct 12 07:23:36 helios4 kernel: [ 15.520824] pwm-fan: probe of j17-pwm failed with error -16 Oct 12 07:23:37 helios4 fancontrol[1313]: Settings for /dev/fan-j10/pwm1: Oct 12 07:23:37 helios4 fancontrol[1313]: Depends on /dev/thermal-cpu/temp1_input Oct 12 07:23:37 helios4 fancontrol[1313]: Controls Oct 12 07:23:37 helios4 fancontrol[1313]: MINTEMP=40 Oct 12 07:23:37 helios4 fancontrol[1313]: MAXTEMP=80 Oct 12 07:23:37 helios4 fancontrol[1313]: MINSTART=20 Oct 12 07:23:37 helios4 fancontrol[1313]: MINSTOP=29 Oct 12 07:23:37 helios4 fancontrol[1313]: MINPWM=0 Oct 12 07:23:37 helios4 fancontrol[1313]: MAXPWM=255 Oct 12 07:23:37 helios4 fancontrol[1313]: AVERAGE=1 Oct 12 07:23:37 helios4 kernel: [ 27.722907] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: user_xattr,usrjquota=aquota.user,grpjquota=aquota.group, jqfmt=vfsv0,acl. Quota mode: journalled. Oct 12 07:23:37 helios4 fancontrol[1313]: Settings for /dev/fan-j17/pwm1: Oct 12 07:23:37 helios4 fancontrol[1313]: Depends on /dev/thermal-cpu/temp1_input Oct 12 07:23:37 helios4 fancontrol[1313]: Controls Oct 12 07:23:37 helios4 fancontrol[1313]: MINTEMP=40 Oct 12 07:23:37 helios4 fancontrol[1313]: MAXTEMP=80 Oct 12 07:23:37 helios4 fancontrol[1313]: MINSTART=20 Oct 12 07:23:37 helios4 systemd[1]: Mounted /srv/dev-disk-by-uuid-0fc50881-8a99-4064-a279-301a326ff75b. Oct 12 07:23:37 helios4 fancontrol[1313]: MINSTOP=29 Oct 12 07:23:37 helios4 fancontrol[1313]: MINPWM=0 Oct 12 07:23:37 helios4 fancontrol[1313]: MAXPWM=255 Oct 12 07:23:37 helios4 fancontrol[1313]: AVERAGE=1 Oct 12 07:23:37 helios4 systemd[1]: Started fan speed regulator. Oct 12 07:23:37 helios4 fancontrol[1720]: Loading configuration from /etc/fancontrol ... Oct 12 07:23:37 helios4 systemd[1]: Starting File System Quota Check... Oct 12 07:23:37 helios4 fancontrol[1720]: Common settings: Oct 12 07:23:37 helios4 fancontrol[1720]: INTERVAL=10 Oct 12 07:23:38 helios4 fancontrol[1720]: Settings for /dev/fan-j10/pwm1: Oct 12 07:23:38 helios4 fancontrol[1720]: Depends on /dev/thermal-cpu/temp1_input Oct 12 07:23:38 helios4 fancontrol[1720]: Controls Oct 12 07:23:38 helios4 fancontrol[1720]: MINTEMP=40 Oct 12 07:23:38 helios4 fancontrol[1720]: MAXTEMP=80 Oct 12 07:23:38 helios4 fancontrol[1720]: MINSTART=20 Oct 12 07:23:38 helios4 fancontrol[1720]: MINSTOP=29 Oct 12 07:23:38 helios4 fancontrol[1720]: MINPWM=0 Oct 12 07:23:38 helios4 fancontrol[1720]: MAXPWM=255 Oct 12 07:23:38 helios4 fancontrol[1720]: AVERAGE=1 Oct 12 07:23:38 helios4 fancontrol[1720]: Settings for /dev/fan-j17/pwm1: Oct 12 07:23:38 helios4 fancontrol[1720]: Depends on /dev/thermal-cpu/temp1_input Oct 12 07:23:38 helios4 fancontrol[1720]: Controls Oct 12 07:23:38 helios4 fancontrol[1720]: MINTEMP=40 Oct 12 07:23:38 helios4 fancontrol[1720]: MAXTEMP=80 Oct 12 07:23:38 helios4 fancontrol[1720]: MINSTART=20 Oct 12 07:23:38 helios4 fancontrol[1720]: MINSTOP=29 Oct 12 07:23:38 helios4 fancontrol[1720]: MINPWM=0 Oct 12 07:23:38 helios4 fancontrol[1720]: MAXPWM=255 Oct 12 07:23:38 helios4 fancontrol[1720]: AVERAGE=1 Oct 12 07:23:38 helios4 fancontrol[1720]: Error: file /dev/fan-j17/pwm1 doesn't exist Oct 12 07:23:38 helios4 fancontrol[1720]: At least one referenced file is missing. Either some required kernel Oct 12 07:23:38 helios4 fancontrol[1720]: modules haven't been loaded, or your configuration file is outdated. Oct 12 07:23:38 helios4 fancontrol[1720]: In the latter case, you should run pwmconfig again. Oct 12 07:23:38 helios4 systemd[1]: fancontrol.service: Main process exited, code=exited, status=1/FAILURE Oct 12 07:23:38 helios4 systemd[1]: fancontrol.service: Failed with result 'exit-code'. Oct 12 07:23:38 helios4 systemd[1]: fancontrol.service: Consumed 1.012s CPU time. On the website https://wiki.kobol.io/helios4/pwm/ I read the following: "Patch requirement Currently Linux gpio-mvebu driver does not allow more than 1 PWM under the same gpio bank. Helios4 uses 2 PWM under same bank therefore this patch needs to be applied to kernel source to remove the restriction." I assumed there was something wrong with the kernel. Downgrading to kernel helios4 5.15.69-mvebu #22.08.2 solved the issue of fancontrol not working. So I assume the required patch, that was always there IMO, has been removed from the latest kernel. Any thoughts on this issue?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines