ASUS Linux Driver Adding Ability To Toggle CPU Cores, APU Memory Settings & dGPU TGP

[phoronix]

Phoronix: ASUS Linux Driver Adding Ability To Toggle CPU Cores, APU Memory Settings & dGPU TGP

The ASUS WMI platform driver for Linux that is predominantly used by ASUS laptops for enabling more functionality under Linux has a new patch series available that is enabling yet more features for the latest ASUS hardware on Linux...

https://www.phoronix.com/news/ASUS-Linux-Cores-APU-Mem-TGP

[M@GOid]

Given the current state of Asus product quality and RMA process, I would advise anyone to stay away of their products.

[Weasel]

Given the current state of Asus product quality and RMA process, I would advise anyone to stay away of their products.

For me, motherboards don't usually fail, but when they do, it's always Asus.

[Kjell]

For me, motherboards don't usually fail, but when they do, it's always Asus.

Are you me?

It's always ASUS and the support is nonexistent.. Not to mention the fact that they're reserving control over fundemental BIOS settings like CPPC for ROG models.

[M@GOid]

For me, motherboards don't usually fail, but when they do, it's always Asus.

I saw a friend lost 2 Asus motherboards back to back. And worst, just a couple months after warranty expires. I personally have 2 Xonar U5 USB soundcards, both with the infamous humidity problem that goes away (temporarily) with a blow dryer.

[pWe00Iri3e7Z9lHOX2Qx]

My only Asus producct is the ROG Strix G15 I'm typing this on, and it's been a good experience overall. Part of that is due to the nice work by Luke. The most annoying thing for me has been that RTC alarms don't work properly, so I can't setup a sleep then hibernate routine (e.g. sleep for 180 minutes, then hibernate).

[pong]

Are you me?

It's always ASUS and the support is nonexistent.. Not to mention the fact that they're reserving control over fundemental BIOS settings like CPPC for ROG models.

And even the basic settings for PCIE-ASPM related enablement.
That is egregiously bad, but that it doesn't default to ENABLED so at least the OS & drivers can easily figure out whether
they want to do it for certain devices or not, ok, fine, but just breaking it "by default" for the whole system by disabling it and not giving the
user control is insane in this day and age since it isn't exactly a new thing.
I've got two different model motherboards suffering from this and nothing has improved in their BIOS for years.

And of course fwupd facilitation etc. is really well overdue for many.

[RushingAlien]

This is why Asus is one of my choices for Linux devices.

[ahrs]

For me, motherboards don't usually fail, but when they do, it's always Asus.

For me it's always Gigabyte. I've had good luck with Asus.

I'm still running some random Asus Prime motherboard in my "home server" (it's nothing fancy, it was my old desktop from 2019 with an i7 6700k in it and is still ticking along since it doesn't do much. I'm amazed the cheap Corsair power supply I used at the time still hasn't given in yet because that's probably what will kill it.)

My desktop has a ROG Crosshair VIII in it and that's doing fine too (I have had to reflash it once or twice though but BIOS flashback makes that easy, all motherboards should have that)

I'm just one person though and this was all a few years ago now. Asus today seems a very different company.

[yump]

How does this benefit from vendor-specific interfaces and drivers beyond what is already provided by /sys/devices/system/CPU*/online, power1_cap in the dGPU's hwmon directory, etc.?

Does panel_fhd use less memory bandwidth than just changing the resolution in the display settings?