Giter Club home page Giter Club logo

Comments (5)

cromerc avatar cromerc commented on September 25, 2024 1

If the rublag fork works for you, you can use tuf-manager: https://git.cromer.cl/cromer/tuf-manager

Tuf-manager has a tray icon that notifies you when the fan mode changes. But currently only works with the rublag fork: https://github.com/rublag/faustus unless the kernel polling gets ported here from that fork in the future.

from faustus.

hackbnw avatar hackbnw commented on September 25, 2024

Hi @ShrirajHegde,

thanks for asking. If you do not have RGB, than you do not need the driver, because this is nearly the only commonly useful feature that a) different from the mainline, b) is not in the mainline kernel. The kernel on your screenshot from other issue (5.8) should likely work fine out of the box. Other feature being reporting fan mode change using the keyboard to the UI with additional flag.

from faustus.

ShrirajHegde avatar ShrirajHegde commented on September 25, 2024

Hi @ShrirajHegde,

thanks for asking. If you do not have RGB, than you do not need the driver, because this is nearly the only commonly useful feature that a) different from the mainline, b) is not in the mainline kernel. The kernel on your screenshot from other issue (5.8) should likely work fine out of the box. Other feature being reporting fan mode change using the keyboard to the UI with additional flag.

ok Today I learned, the fan mode works even though there's no visual feedback, any way to check what fan mode is on?? because this is blind toggling

What about the present button? Anyway to utilize that button? That doesn't do anything

EDIT: MUTE button doesn't work anyway to fix that??

I get this for toggling disable the touchpad.. Is there any way to get this for fan modes? Also, the mute button is really important,anyway to get it?

somehow just two buttons are left out
image

from faustus.

hackbnw avatar hackbnw commented on September 25, 2024

Regarding the mute button it should have been forwarded as can be easily verified by evtest program. Whether or not it is functional is the question of support in the desktop manager and other software:

$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
...
/dev/input/event23:	Asus WMI hotkeys
Select the device event number [0-23]: 23
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
Input device name: "Asus WMI hotkeys"
...
Testing ... (interrupt to exit)
Event: time 1614525523.151239, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7c
Event: time 1614525523.151239, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 1
Event: time 1614525523.151239, -------------- SYN_REPORT ------------
Event: time 1614525523.151286, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 0
Event: time 1614525523.151286, -------------- SYN_REPORT ------------

@cromerc he did submit the sysfs notifications to the mainline torvalds/linux@72ceec5

from faustus.

ShrirajHegde avatar ShrirajHegde commented on September 25, 2024

Regarding the mute button it should have been forwarded as can be easily verified by evtest program. Whether or not it is functional is the question of support in the desktop manager and other software:

$ sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
...
/dev/input/event23:	Asus WMI hotkeys
Select the device event number [0-23]: 23
Input driver version is 1.0.1
Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0
Input device name: "Asus WMI hotkeys"
...
Testing ... (interrupt to exit)
Event: time 1614525523.151239, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7c
Event: time 1614525523.151239, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 1
Event: time 1614525523.151239, -------------- SYN_REPORT ------------
Event: time 1614525523.151286, type 1 (EV_KEY), code 248 (KEY_MICMUTE), value 0
Event: time 1614525523.151286, -------------- SYN_REPORT ------------

@cromerc he did submit the sysfs notifications to the mainline torvalds/linux@72ceec5

This ACPI event fixes it in a "hacky" way(only in Ubuntu, SELinux creates some problems in fedora), this mutes the mic but doesn't work in VMs, it would be great if it worked natively. I am a fedora user so let me check 5.11 and see what happens.

event=button/micmute MICMUTE 00000080 00000000 K
action=/usr/bin/amixer sset 'Capture',0 toggle

from faustus.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.