DELETE

[leukimi]

DELETE

[dominiksalvet]

Hello @leukimi and welcome to the asus-fan-control community! :wave: :rabbit:

• /usr/local/bin/asus-fan-control: 411: Illegal number: Erro

This is suspiciously similar to #34. Please run the following script with root permissions:

{ echo '\_SB.PCI0.LPCB.EC0.RRAM 1335' > /proc/acpi/call &&
  cat /proc/acpi/call # usually there is no newline in the output
  printf '\n%s\n' "$?"; } # hence we are using printf to make output clean

What is the output?

afc-gui not working.

Afc-gui is asus-fan-control's extension, so until asus-fan-control is working, we cannot say really much about wheter afc-gui works or not. The error output hints the same - the same error report as mentioned above.

First, the file afc-gui is not found directly. Path does not contain $HOME/.local/share/bin/

Assuming you are rather talking about $HOME/.local/bin/, this is a notorious issue with Ubuntu as far as I can tell. After adding the first executable file here, you must relog/reboot. Then it works as expected.

[leukimi]

DELETE

[dominiksalvet]

bash: /proc/acpi/call: No such file or directory

I suspect that you do not have acpi_call installed - GitPack installs it automatically in normal circumstances. Try sudo apt update && sudo apt install acpi-call-dkms. That should fix it.

I noticed you manage to use colors in your post, and I wonder how you manage to do that. It increases readability. I don't see any buttons in the header that would allow me to add color information to text.

Take a look at your post - I have modified it so that it has colors as well. See its history and changes.

[dominiksalvet]

Take a look at your post - I have modified it so that it has colors as well. See its history and changes.

Oh, there is no raw view... instead of ``` at the beginning of the code block, I used ```sh. You can use different languages as well, e,g,. ```java.

[leukimi]

DELETE

[dominiksalvet]

Someone posted in another forum that you have to load the acpi_call first before using it.

Definitely the right step - I have forgotten about it. :+1:

Exit code 0 tells me this went "well" but Error: AE_NOT_FOUND seems it didn't go well.

It means that the ACPI call has been performed correctly but it ended up with an ACPI error. Unfortunately, AE_NOT_FOUND is a notorious issue that some laptop models suffer from. I interpret it as Access Entry NOT FOUND, so your laptop probably does not have the EC0 interface/entry.

So far there is no solution to that. Even then, asus-fan-control would need to be modified accordingly as it currently uses the ACPI path as a constant, not per-device. It wouldn't be hard to implement it, though.

See #34 and this afc-scout issue for more information. Unfortunately, I am not able to help you as per the current state. :disappointed:

[leukimi]

DELETE

[dominiksalvet]

Well, that's very good news! 👏 Thank you for the information. ❤️ The ASUS community will appreciate it.

I expect that asus-fan-control still does not work on your device, does it? 🤔 If not, feel free to close the issue as it is effectively solved. Otherwise, maybe asus-fan-control started to work due ACPI/kernel update... who knows...

[leukimi]

DELETE

[leukimi]

DELETE

[dominiksalvet]

@leukimi Once any AFC issue is closed, it is considered solved. So no need to add any "solved" indicator. It is rather confusing in this particular case as it does not really solve the issue described in the title "Add support for ASUS X70ID-TY004V motherboard K70ID"... Furthermore, this issue is labeled with AE_NOT_FOUND and it may indicate that it solves the infamous AE_NOT_FOUND problem that AFC suffers from.

Due to the reasons stated above, I am removing the "solved" indicator.

[dominiksalvet]

But anyway, thank you for your contribution! :heart: