Announcement
Collapse
No announcement yet.
Linux 5.16 To Support Sensor Readings On More ASUS Motherboards
Collapse
X
-
Originally posted by MadCatX View PostCare to elaborate on how are distros purposely designed to be incompatible with each other?
When a package for distribution X cannot be used on distribution Y without breaking stuff.
Originally posted by MadCatX View PostAll the board vendors need to do is submit a patch to the mainline kernel. No need to deal with distros.
And even if they send something to the mainline kernel in development, practically every distribution use an older patched kernel and will never see that change implemented if that new development kernel happens to break ABI.
Comment
-
Originally posted by birdie View PostAnd what's wrong with an individual willing to improve Linux?? Companies supporting Linux primarily do that to further their bottom line - they couldn't care less about Linux on the desktop which Phoronix is kinda dedicated to.
Also, there are workplaces with thousands of employees which buy a lot of desktops running Linux. Even though it might not be as much money as to e.g. data centers, it's probably not an negligible amount at least.
- Likes 3
Comment
-
Originally posted by birdie View Post
And what's wrong with an individual willing to improve Linux?? Companies supporting Linux primarily do that to further their bottom line - they couldn't care less about Linux on the desktop which Phoronix is kinda dedicated to. If Linux on the desktop improves after their contributions it's mainly a byproduct, not their primary interest. So, far the only company which has really been improving Linux on the desktop was Valve and only Valve. And if you think they do it because they "love" Linux? Nope, they do it to earn more by selling Steam Deck and games for it.
- Likes 5
Comment
-
Originally posted by Sonadow View PostWhen a package for distribution X-1 is not even usable on distribution X without potentially breaking stuff.
When a package for distribution X cannot be used on distribution Y without breaking stuff.
Why should they open up their secrets for an operating system that has < 2% desktop share?
- Likes 5
Comment
-
Originally posted by Sonadow View Post
When a package for distribution X-1 is not even usable on distribution X without potentially breaking stuff.
When a package for distribution X cannot be used on distribution Y without breaking stuff.
Originally posted by Sonadow View PostWhy should they open up their secrets for an operating system that has < 2% desktop share?
Because there are no secrets to be opened up. Reading out temperature and fan speed sensors data is not rocket science.
Originally posted by Sonadow View PostAnd even if they send something to the mainline kernel in development, practically every distribution use an older patched kernel and will never see that change implemented if that new development kernel happens to break ABI.
- Likes 4
Comment
-
Originally posted by MadCatX View PostThis is not what purposely means. This is just an unfortunate side effect of different distros having different development philosophies and technical issues stemming from a highly complex software ecosystem. If there was a good fix for this, we would've adopted it already but there just isn't one. But it doesn't mean that distros aim to be incompatible on purpose. .
The only reason it does not exist for desktop Linux is entirely down to NIH syndrome and egos.Last edited by Sonadow; 19 September 2021, 11:17 AM.
Comment
-
Originally posted by Sonadow View Post
There IS a fix. Declare a universal base distribution with minimum versions for the kernel and various packages that all distributions must adopt as a baseline. Android and ChromeOS were able to pull this off.
Originally posted by Sonadow View PostThe only reason it does not exist for desktop Linux is entirely down to NIH syndrome and egos.
- Likes 2
Comment
-
I have been using this revert for my Asus TUF Z370-Plus gaming board since a regression was introduced quite a while ago. I don't remember what kernel it was, but it initially started as a patch in some subversion (eg. 5.6.10 or something) then when the new kernel (5.7) was introduced, it was back to non-working again.
Chip on the Asus TUF board i have is NCT-6793, but afaik it uses the 6775 kernel module too.
Code:--- drivers/acpi/acpica/dsopcode.c | 4 ---- 1 file changed, 4 deletions(-) diff --git a/drivers/acpi/acpica/dsopcode.c b/drivers/acpi/acpica/dsopcode.c index 639635291..8ebad18d6 100644 --- a/drivers/acpi/acpica/dsopcode.c +++ b/drivers/acpi/acpica/dsopcode.c @@ -431,10 +431,6 @@ acpi_ds_eval_region_operands(struct acpi_walk_state *walk_state, ACPI_FORMAT_UINT64(obj_desc->region.address), obj_desc->region.length)); - status = acpi_ut_add_address_range(obj_desc->region.space_id, - obj_desc->region.address, - obj_desc->region.length, node); - /* Now the address and length are valid for this opregion */ obj_desc->region.flags |= AOPOBJ_DATA_VALID; --
EDIT: It seems to be quite older than that, i just had to search a bit.
Well.. did not take them that long to fix stuff :P
Last edited by Cybmax; 19 September 2021, 12:27 PM.
Comment
Comment