You are not logged in.

Pages: 1

#1 2017-03-07 15:16:42

xinyifly
Member
Registered: 2017-03-07
Posts: 4

Macbook April 2016 intel-lpss error

[root@tux dsdt]# dmesg | grep -i lpss
[    4.345719] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[    4.345844] intel-lpss 0000:00:15.0: can't derive routing for PCI INT A
[    4.345845] intel-lpss 0000:00:15.0: PCI INT A: not connected
[    4.345867] intel-lpss: probe of 0000:00:15.0 failed with error -22
[    4.362421] intel-lpss 0000:00:15.2: enabling device (0000 -> 0002)
[    4.362520] intel-lpss 0000:00:15.2: can't derive routing for PCI INT C
[    4.362521] intel-lpss 0000:00:15.2: PCI INT C: not connected
[    4.362551] intel-lpss: probe of 0000:00:15.2 failed with error -22
[    4.379061] intel-lpss 0000:00:19.0: enabling device (0000 -> 0002)
[    4.379189] intel-lpss 0000:00:19.0: can't derive routing for PCI INT A
[    4.379190] intel-lpss 0000:00:19.0: PCI INT A: not connected
[    4.379219] intel-lpss: probe of 0000:00:19.0 failed with error -22
[    4.399061] intel-lpss 0000:00:1e.0: enabling device (0000 -> 0002)
[    4.399158] intel-lpss 0000:00:1e.0: can't derive routing for PCI INT A
[    4.399159] intel-lpss 0000:00:1e.0: PCI INT A: not connected
[    4.399185] intel-lpss: probe of 0000:00:1e.0 failed with error -22
[    4.415726] intel-lpss 0000:00:1e.3: enabling device (0000 -> 0002)
[    4.415855] intel-lpss 0000:00:1e.3: can't derive routing for PCI INT D
[    4.415857] intel-lpss 0000:00:1e.3: PCI INT D: not connected
[    4.415884] intel-lpss: probe of 0000:00:1e.3 failed with error -22

Thus I can't get this keyboard driver to work.
https://github.com/cb22/macbook12-spi-driver/issues/11

Last edited by xinyifly (2017-03-08 06:42:29)

Offline

#2 2017-03-07 15:19:02

xinyifly
Member
Registered: 2017-03-07
Posts: 4

Re: Macbook April 2016 intel-lpss error

[root@tux dsdt]# dmesg | grep -i error
[    0.523229] ACPI Error: Method parse/execution failed [\_PR.CPU0.GCAP] (Node ffff8802660c97d0), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.523259] ACPI Error: Method parse/execution failed [\_PR.CPU0._OSC] (Node ffff8802660c9280), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.523273] ACPI: Marking method _OSC as Serialized because of AE_ALREADY_EXISTS error
[    0.523638] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.523651] ACPI Error: Method parse/execution failed [\_PR.CPU1.GCAP] (Node ffff8802660c9488), AE_NOT_FOUND (20160831/psparse-543)
[    0.523664] ACPI Error: Method parse/execution failed [\_PR.CPU1._OSC] (Node ffff8802660c9ca8), AE_NOT_FOUND (20160831/psparse-543)
[    0.524007] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.524017] ACPI Error: Method parse/execution failed [\_PR.CPU2.GCAP] (Node ffff8802660c9870), AE_NOT_FOUND (20160831/psparse-543)
[    0.524031] ACPI Error: Method parse/execution failed [\_PR.CPU2._OSC] (Node ffff8802660c9690), AE_NOT_FOUND (20160831/psparse-543)
[    0.524377] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.524387] ACPI Error: Method parse/execution failed [\_PR.CPU3.GCAP] (Node ffff8802660c9c08), AE_NOT_FOUND (20160831/psparse-543)
[    0.524399] ACPI Error: Method parse/execution failed [\_PR.CPU3._OSC] (Node ffff8802660c9730), AE_NOT_FOUND (20160831/psparse-543)
[    0.524735] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.524744] ACPI Error: Method parse/execution failed [\_PR.CPU4.GCAP] (Node ffff8802660c92d0), AE_NOT_FOUND (20160831/psparse-543)
[    0.524765] ACPI Error: Method parse/execution failed [\_PR.CPU4._OSC] (Node ffff8802660c9de8), AE_NOT_FOUND (20160831/psparse-543)
[    0.525103] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.525117] ACPI Error: Method parse/execution failed [\_PR.CPU5.GCAP] (Node ffff8802660c9be0), AE_NOT_FOUND (20160831/psparse-543)
[    0.525135] ACPI Error: Method parse/execution failed [\_PR.CPU5._OSC] (Node ffff8802660c9230), AE_NOT_FOUND (20160831/psparse-543)
[    0.525473] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.525487] ACPI Error: Method parse/execution failed [\_PR.CPU6.GCAP] (Node ffff8802660c9758), AE_NOT_FOUND (20160831/psparse-543)
[    0.525505] ACPI Error: Method parse/execution failed [\_PR.CPU6._OSC] (Node ffff8802660c9d48), AE_NOT_FOUND (20160831/psparse-543)
[    0.525841] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.525855] ACPI Error: Method parse/execution failed [\_PR.CPU7.GCAP] (Node ffff8802660c9c80), AE_NOT_FOUND (20160831/psparse-543)
[    0.525873] ACPI Error: Method parse/execution failed [\_PR.CPU7._OSC] (Node ffff8802660c96e0), AE_NOT_FOUND (20160831/psparse-543)
[    0.526783] ACPI Error: Method parse/execution failed [\_PR.CPU0.GCAP] (Node ffff8802660c97d0), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.526816] ACPI Error: Method parse/execution failed [\_PR.CPU0._PDC] (Node ffff8802660c93c0), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.526833] ACPI: Marking method _PDC as Serialized because of AE_ALREADY_EXISTS error
[    0.527415] ACPI Error: Method parse/execution failed [\_PR.CPU1.APPT] (Node ffff8802660c9140), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.527443] ACPI Error: Method parse/execution failed [\_PR.CPU1.GCAP] (Node ffff8802660c9488), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.527462] ACPI Error: Method parse/execution failed [\_PR.CPU1._PDC] (Node ffff8802660c9af0), AE_ALREADY_EXISTS (20160831/psparse-543)
[    0.527478] ACPI: Marking method _PDC as Serialized because of AE_ALREADY_EXISTS error
[    0.527904] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.527919] ACPI Error: Method parse/execution failed [\_PR.CPU2.GCAP] (Node ffff8802660c9870), AE_NOT_FOUND (20160831/psparse-543)
[    0.527937] ACPI Error: Method parse/execution failed [\_PR.CPU2._PDC] (Node ffff8802660c93e8), AE_NOT_FOUND (20160831/psparse-543)
[    0.528357] ACPI Error: [\_SB_.OSCP] Namespace lookup failure, AE_NOT_FOUND (20160831/psargs-359)
[    0.528372] ACPI Error: Method parse/execution failed [\_PR.CPU3.GCAP] (Node ffff8802660c9c08), AE_NOT_FOUND (20160831/psparse-543)
[    0.528390] ACPI Error: Method parse/execution failed [\_PR.CPU3._PDC] (Node ffff8802660c9500), AE_NOT_FOUND (20160831/psparse-543)
[    4.345867] intel-lpss: probe of 0000:00:15.0 failed with error -22
[    4.362551] intel-lpss: probe of 0000:00:15.2 failed with error -22
[    4.379219] intel-lpss: probe of 0000:00:19.0 failed with error -22
[    4.399185] intel-lpss: probe of 0000:00:1e.0 failed with error -22
[    4.415884] intel-lpss: probe of 0000:00:1e.3 failed with error -22
[    4.419079] hci_bcm: probe of BCM2E7C:00 failed with error -22
[    4.567949] brcmfmac 0000:02:00.0: Direct firmware load for brcm/brcmfmac4350c2-pcie.txt failed with error -2
[root@tux dsdt]# uname -a
Linux tux 4.9.11-1-ARCH #1 SMP PREEMPT Sun Feb 19 13:45:52 UTC 2017 x86_64 GNU/Linux

Offline

#3 2017-03-07 21:12:48

mrunion
Member
From: Jonesborough, TN
Registered: 2007-01-26
Posts: 1,938
Website

Re: Macbook April 2016 intel-lpss error

Is there a question?

Matt

"It is very difficult to educate the educated."

Offline

#4 2017-03-08 06:40:39

xinyifly
Member
Registered: 2017-03-07
Posts: 4

Re: Macbook April 2016 intel-lpss error

mrunion wrote:

Is there a question?

Yes, it might be the root cause that I can't let intel-lpss enumerate the APP000D slave device even with a DSDT hack.
You can follow the github issue and repo for more information about this keyboard driver for new macbook.

Offline

#5 2017-03-08 06:46:02

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Macbook April 2016 intel-lpss error

Again, what exactly do you want? Do you want to others to confirm if this is the root cause for your problem? In any case, please go through: http://www.catb.org/~esr/faqs/smart-questions.html

Offline

#6 2017-03-08 06:58:48

xinyifly
Member
Registered: 2017-03-07
Posts: 4

Re: Macbook April 2016 intel-lpss error

x33a wrote:

Again, what exactly do you want? Do you want to others to confirm if this is the root cause for your problem? In any case, please go through: http://www.catb.org/~esr/faqs/smart-questions.html

Sorry for that. But I thought it's some information for Arch Linux developers. I just reported the errors in dmesg when I fresh installed an Arch Linux in macbook9, 1 April 2016. These errors exist even with an liveCD image. Also, I want to confirm if these errors matter or do they influence the spi device which enumerated by intel-lpss.
I think it's related to https://wiki.archlinux.org/index.php/Ma … sion_9.2C1 the keyboard part

Last edited by xinyifly (2017-03-08 07:01:58)

Offline

Pages: 1

Board footer

Powered by FluxBB