NOTICE: rog-core is now obsoleted and you will get a better experience using the dkms module or patch, and asus-nb-ctrl.
The last version of rog-core will work with any kernel with or without this patch and provide full functions.
rog-core is a utility for Linux to control many aspects (eventually) of the ASUS ROG laptops like the Zephyrus GX502GW.
One of the benefits of this app (for me at least) is that you don't require a kernel with correct support for the laptop keyboard EC. The app reads and writes direct to the device interrupts, and can be customised (in source) quite extensively to do what you want such as directly controlling your laptop backlight rather than emitting a key-press for the DE to handle.
Other laptop functions such as fan modes or battery charge limiting will need kernel level support which exists in most newer kernels (higher than 5.6.10).
Please help test or provide info for:
- GL703(0x1869)
- GL553/GL753 (device = 0x1854) (attempted support from researching 2nd-hand info, multizone may work)
Laptop support is modified on a per-case basis as the EC for the keyboard varies a little between models, e.g, some RGB modes are missing, or it's a single colour. As far as I can see, the EC does not give us a way to find what modes are supported.
Media keys are Volume -/+, Mute output, previous, next, play/pause. These keys are grouped together on one interface block on the keyboard EC as a "Consumer Device" HID, all other fn+ combo are on another interface which is "Vendor Custom", this includes things like keyboard LED brightness and mode change keys, Calc, fan-mode toggles etc.
| MODEL | Media keys | Additional FN+ | AniMe | Touchpad-Numpad | Fan Modes | Charge Limit |
|---|---|---|---|---|---|---|
| GM501 | X | X | X | X | ||
| GX502 | X | X | X | X | ||
| GX531 | X | X | X | X | ||
| GX701 | X | X | X | X | ||
| G512 | X | X | X | X | ||
| G712 | X | X | X | X | ||
| G531 | X | X | X | X | ||
| G731 | X | X | X | X | ||
| G532 | X | X | X | X | ||
| GA401 | X | X | X | X | X | |
| GA502 | X | X | X | X | X | |
| GU502 | X | X | X | X | X |
NOTE: GA14/GA401 and GA15/GA502/GU502, You will need kernel patches.
Models GA401, GA502, GU502 support LED brightness change only (no RGB).
| MODEL | SINGLE | BREATHING | STROBE | RAINBOW | STAR | RAIN | HIGHLIGHT | LASER | RIPPLE | PULSE | COMET | FLASH | ZONES | PER-KEY RGB |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| G512LI | X | X | X | X | ||||||||||
| G712LI | X | X | X | X | ||||||||||
| GM501 | X | X | X | X | X | |||||||||
| GX531 | X | X | X | X | X | |||||||||
| G512 | X | X | X | X | X | |||||||||
| G712 | X | X | X | X | X | |||||||||
| GX502 | X | X | X | X | X | X | X | X | X | X | X | X | X | |
| GX701 | X | X | X | X | X | X | X | X | X | X | X | X | X | |
| G531 | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
| G731 | X | X | X | X | X | X | X | X | X | X | X | X | X | X |
| G532 | X | X | X | X | X | X | X | X | X | X | X | X | X |
- Setting/modifying built-in LED modes
- Per-key LED setting
- Fancy LED modes (See examples)
- Daemon mode
- Saving settings for reload
- System control
- ROG key custom mapping (Can be done in source)
- Fan/Performance mode
- Screen off? Now mapped to a keycode but has no effect
- Screen brightness up/down
- Touchpad toggle
- Sleep
- Airplane mode
- Capture and use hotkeys
- Aura control by Aura keys
- Volume + media controls work
- Mic mute
- Logging - required for journalctl
- AniMatrix display on G14 models that include it
- Set battery charge limit (with kernel supporting this)
rustc+cargo+makelibusb-1.0-0-devlibdbus-1-devllvmlibclang-dev
Run make then sudo make install then reboot.
The default init method is to use the udev rule, this ensures that the service is started when the device is initialised and ready.
If you are upgrading from a previous installed version, you will need to restart the service or reboot.
$ systemctl daemon-reload && systemctl restart rog-core
You may also need to activate the service for debian install. If running Pop!_OS, I suggest disabling system76-power
gnome-shell extension, or at least limiting use of the power-management parts as rog-core lets you set the same things
(one or the other will overwrite pstates). I will create a shell extension at some point similar to system76, but using
the rog-core parts. It is safe to leave system76-power.service enabled and use for switching between graphics modes.
Alternatively, instead of building manually you can use the PPA.
sudo add-apt-repository ppa:lukedjones/rog-core
sudo apt-get update
sudo apt-get install rog-core
the rog-core service will run when the device is initialised.
Thanks to @aspann you can grab it here sys-power/rog-core
You can find the thingimajig here. If you are using a GA14 or GA15 series, you may need kernel patches.
Occasionally I might break things for you by tweaking or changing the config file layout. Usually this will mean you
need to remove /etc/rog-core.conf and restart the daemon to create a new one. You can back up the old one and copy
settings back over (then restart daemon again).
NOTE! Fan mode toggling requires a newer kernel. I'm unsure when the patches required for it got merged - I've tested with the 5.6.6 kernel and above only. To see if the fan-mode changed cat either:
cat /sys/devices/platform/asus-nb-wmi/throttle_thermal_policyorcat /sys/devices/platform/asus-nb-wmi/fan_boost_mode
The numbers are 0 = Normal/Balanced, 1 = Boost, 2 = Silent.
Running the program as a daemon manually will require root. Standard (non-daemon) mode expects to be communicating with the daemon mode over dbus.
Commands are given by:
rog-core <option> <command> <command-options>
Help is available through:
rog-core --help
rog-core <command> --help
Some commands may have subcommands:
rog-core <command> <subcommand> --help
$ rog-core --help
Usage: rog-core [OPTIONS]
Optional arguments:
-h, --help print help message
-v, --version show program version number
-d, --daemon start daemon
-b, --bright VAL <off, low, med, high>
-f, --fan-mode FAN <silent, normal, boost>
Available commands:
led-mode Set the keyboard lighting from built-in modes
$ rog-core led-mode --help
Usage: rog-core led-mode [OPTIONS]
Optional arguments:
-h, --help print help message
Available commands:
stable set a single static colour
breathe pulse between one or two colours
strobe strobe through all colours
rainbow rainbow cycling in one of four directions
star rain pattern mimicking raindrops
rain rain pattern of three preset colours
highlight pressed keys are highlighted to fade
laser pressed keys generate horizontal laser
ripple pressed keys ripple outwards like a splash
pulse set a rapid pulse
comet set a vertical line zooming from left
flash set a wide vertical line zooming from left
multi-static 4-zone multi-colour
$ rog-core led-mode stable --help
Usage: rog-core led-mode stable [OPTIONS]
Optional arguments:
-h, --help print help message
-c HEX set the RGB value e.g, ff00ff
$ rog-core led-mode star --help
Usage: rog-core led-mode star [OPTIONS]
Optional arguments:
-h, --help print help message
-c HEX set the first RGB value e.g, ff00ff
-C HEX set the second RGB value e.g, ff00ff
-s SPEED set the speed: low, med, high
The ROG key can be customized in a limited way by use of presets:
- Power
- Sleep
- MediaRecord
- MediaFastFwd
- MediaRewind
- MediaNext
- MediaPrev
- MediaStop
- MediaPlayPause
- MediaVolMute
- MediaVolUp
- MediaVolDown
- BacklightInc
- BacklightDec
- ControlConfig
- LaunchTextEditor
- LaunchEmailApp
- LaunchNewsReader
- LaunchCalendar
- LaunchCalculator
- LaunchWebBrowser
- FileBrowser
This key can be changed in /etc/rogcore.conf, for example:
{
"rog_key": "FileBrowser",
If the daemon service is enabled then on boot the following will be reloaded from save:
- LED brightness
- Last used built-in mode
- fan-boost/thermal mode
- battery charging limit
The daemon also saves the settings per mode as the keyboard does not do this itself - this means cycling through modes with the Aura keys will use the settings that were used via CLI.
Daemon mode creates a config file at /etc/rogcore.conf which you can edit a
little of. Most parts will be byte arrays, but you can adjust things like
mode_performance.
See README_DBUS.md.
You will want to look at what MeuMeu has done with https://github.com/Meumeu/ZephyrusBling/
TODO: see ./wireshark_data/ for some captures.
At a minimum it probably needs to be a Zephyrus laptop. If there is enough interest I will remove the restriction on board names so that anyone can try the app.
From there I'll need wireshark captures from Windows using Armoury Crate if possible:
- No USB devices plugged in
- One action per capture, 2 or 3 times
- An action may be switching a mode or pressing a button
The real ticket items are:
- Captures from installing Armoury Crate. To do this you need to uninstall almost all ASUS junkware and such
- Byte sequence captures from hotkeys pressed in linux (which I need to make a tool for)
- lsusb output
lsusb:
First do lsusb |grep 0b05 and check the part after 0b05:, output looks like:
Bus 001 Device 005: ID 0b05:1866 ASUSTek Computer, Inc. N-KEY Device
Then do sudo lsusb -vd 0b05:1866 > ~/laptop_info and give that to me.
Other helpful info can be gained from sudo usbhid-dump, for which you may need to unload kernel drivers. Please google
this.
Also required (for my book-keeping of data):
cat /sys/class/dmi/id/product_namecat /sys/class/dmi/id/product_familycat /sys/class/dmi/id/board_name
Mozilla Public License 2 (MPL-2.0)
- flukejones, project maintainer.
- tuxuser
- aspann
- meumeu
- Anyone missed? Please contact me
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent