Unsolved
14 Posts
1
2528
Fn and brightness key causing a lot of errors in kernel logs
Dell Precision 7540
I have been trying to track a lot errors down at least where they are coming from and when I press Fn and the brightness key these errors comes up in my dmesg logs every time.
[21616.163915] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190703/psargs-330)
[21616.163946] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[21616.164396] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[21616.164839] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[21616.165322] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[21616.165554] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[21616.165802] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
These errors are known to the kernel developers and they say it is in the machine firmware and from what I can read it is a lot of machines including the 5530,7530 and mostly all the developers Precision's. The Dell XPS has the same thing going also.
user_76ace8
1 Message
0
November 6th, 2019 18:00
I have exactly the same problem on XPS 15 7590, sometimes after Fn+brightness button, my screen will go dark and these kernel errors appear.
freefreeno
14 Posts
0
November 28th, 2019 01:00
Well it seems to be a bios related issue so I don't think kernel developers are gonna fix it. Dell doesnt seem to be fixing it either. So we have error after error without any solution. Sad thing is my PC came with Linux. never make the mistake of thinking a PC bought with Linux is any better or more compatible because you will be disappointed.
mtsn
10 Posts
0
December 19th, 2019 21:00
same with me. 7530 with ubuntu 19.10 and bios 1.12.1, allows for brightness to be turned up/down with third party app, but not through the [fn]+[up|down] keys. I'm monitoring several posts about this. One person has stated that a fix is coming out at the end of December.
freefreeno
14 Posts
0
February 5th, 2020 13:00
Oh I can turn brightness up and down all day but it fill logs with errors.
MathiasB
5 Posts
1
March 4th, 2020 12:00
Same issue with my XPS15 7590 (with latest bios v1.5.0):
[ 166.559647] ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PEG0.PEGP.BRT6.LCD], AE_NOT_FOUND (20190703/psargs-330)
[ 166.559673] No Local Variables are initialized for Method [BRT6]
[ 166.559676] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation)
[ 166.559678] Arg0: 000000003826563d Integer 0000000000000002
[ 166.559687] Arg1: 00000000fe03c42b Integer 0000000000000000
[ 166.559698] ACPI Error: Aborting method \_SB.PCI0.PEG0.PEGP.BRT6 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[ 166.560138] ACPI Error: Aborting method \EV5 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[ 166.560481] ACPI Error: Aborting method \SMEE due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[ 166.560742] ACPI Error: Aborting method \SMIE due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[ 166.560903] ACPI Error: Aborting method \NEVT due to previous error (AE_NOT_FOUND) (20190703/psparse-529)
[ 166.561065] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_NOT_FOUND) (20190703/psparse-529)