Created attachment 260685 [details] Bios file - V303 - Latest Hi , i'm using this laptop with it's latest bios (V303 - https://www.asus.com/Laptops/ASUS-FX553VD/HelpDesk_BIOS/ ) I can't control keyboard LED backlight level with it's dedicated FN keys or anything else. FN keys are recognized by Linux Mint but pressing them have no effect. Kernels from 4.10 to 4.14 are the same on that regard. And also i have these errors on "inxi -F && dmesg | grep -i error" [ 0.031175] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS (20170728/dswload-378) [ 0.040665] ACPI Error: 1 table load failures, 10 successful (20170728/tbxfload-246) [ 0.506425] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM [ 1.694527] RAS: Correctable Errors collector initialized. [ 9.833145] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro I'm not a developer but only a user. So if i opened that issue to the wrong place can you point me the correct place to open it? Thanks. I'm adding bios to attachment , just in case.
please attach the ACPI dump and the full dmesg for this machine.. From what it looks like, this could be a firmware bug... This error message seems serious: [ 0.040665] ACPI Error: 1 table load failures, 10 successful (20170728/tbxfload-246)
(In reply to Erik Schmauss from comment #1) > please attach the ACPI dump and the full dmesg for this machine.. From what > it looks like, this could be a firmware bug... > This error message seems serious: > [ 0.040665] ACPI Error: 1 table load failures, 10 successful > (20170728/tbxfload-246) When i command acpidump it says this. Could not open table file: /sys/firmware/acpi/tables/SSDT6 Could not get ACPI tables, AE_ACCESS Also here is the dmesg.But since it is hell long , i apologise for that mess already. I will put it in a text format as an attachment otherwise it is not readable when i paste here.
Created attachment 260935 [details] Requested dmesg output dmesg output
try running acpidump with sudo
(In reply to Erik Schmauss from comment #4) > try running acpidump with sudo Wow , sorry. I'm a noob. Here you go. I'm adding this an attachment too because it is also too long.
Created attachment 260937 [details] sudo acpidump > acpi.dat sudo acpidump > acpi.dat
These tables contain a firmware bug. If you want to get rid of the error messages below the firmware must be fixed. [ 0.030685] ACPI Error: [PRT0] Namespace lookup failure, AE_ALREADY_EXISTS (20170728/dswload-378) [ 0.030692] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog (20170728/psobject-252) [ 0.030765] ACPI Exception: AE_ALREADY_EXISTS, (SSDT:SataTabl) while loading table (20170728/tbxfload-228) [ 0.039918] ACPI Error: 1 table load failures, 10 successful (20170728/tbxfload-246) So you might want to contact ASUS about this issue.
(In reply to Erik Schmauss from comment #7) > These tables contain a firmware bug. If you want to get rid of the error > messages below the firmware must be fixed. > > [ 0.030685] ACPI Error: [PRT0] Namespace lookup failure, > AE_ALREADY_EXISTS (20170728/dswload-378) > [ 0.030692] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog > (20170728/psobject-252) > [ 0.030765] ACPI Exception: AE_ALREADY_EXISTS, (SSDT:SataTabl) while > loading table (20170728/tbxfload-228) > [ 0.039918] ACPI Error: 1 table load failures, 10 successful > (20170728/tbxfload-246) > > So you might want to contact ASUS about this issue. I already tried that but they ignored me and they said "we are offering Windows 10". Funny thing is , that laptop comes with Endless OS. They clearly doesn't gave any attention to me. How can i make them fix that? They're ignoring Linux.
The issue we see on linux is that there is one firmware table that is unable to load due to a table (ssdt10) containing a pre-existing object declared in a separate table (dsdt). There are a total of 17 ssdt tables but only 16 ssdt tables can load. If windows 10 shows a similar behavior, you might be able to convince them to fix their firmware. You can check which acpi tables have been loaded on windows on the registry under the hardware tab.
(In reply to Erik Schmauss from comment #9) > The issue we see on linux is that there is one firmware table that is unable > to load due to a table (ssdt10) containing a pre-existing object declared in > a separate table (dsdt). There are a total of 17 ssdt tables but only 16 > ssdt tables can load. If windows 10 shows a similar behavior, you might be > able to convince them to fix their firmware. You can check which acpi tables > have been loaded on windows on the registry under the hardware tab. Got it but i really dislike Windows and i don't want to install it. First of all ; i will link them this thread for explanation. I hope that works. Thanks for everything , btw LED keyboard backlight is not an issue anymore. It was working with one of the daily Ubuntu kernels. I hope it will be on mainline kernel soon. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1732686 So i'm editing the title , ACPI is not related to keyboard.
(In reply to Erik Schmauss from comment #7) > These tables contain a firmware bug. If you want to get rid of the error > messages below the firmware must be fixed. > > [ 0.030685] ACPI Error: [PRT0] Namespace lookup failure, > AE_ALREADY_EXISTS (20170728/dswload-378) > [ 0.030692] ACPI Exception: AE_ALREADY_EXISTS, During name lookup/catalog > (20170728/psobject-252) > [ 0.030765] ACPI Exception: AE_ALREADY_EXISTS, (SSDT:SataTabl) while > loading table (20170728/tbxfload-228) > [ 0.039918] ACPI Error: 1 table load failures, 10 successful > (20170728/tbxfload-246) > > So you might want to contact ASUS about this issue. As many users has acpi errors, simplest solution is that intel developers use dev_info instead of dev_err call for those message. This way you disable all acpi errors: enable ACPI_NO_ERROR_MESSAGES. Exporting ACPI_HELP_APP as terminal environment variable does not work. ./include/acpi/platform/acenv.h /* acpi_help configuration. Error messages disabled. */ #ifdef ACPI_HELP_APP #define ACPI_NO_ERROR_MESSAGES #endif +#define ACPI_NO_ERROR_MESSAGES
as the ACPI errors are about a Firmware Bug, there is nothing we can do from kernel' point of view. As I don't see a real kernel problem on this box, bug closed.