Closed jannis3005 closed 4 years ago
aymanbagabas
commented
5 years ago This might be out of the driver's scope. Could you provide the ACPI dumps using acpidump specifically I need DSDT and SSDT tables.
For more info refer to https://01.org/linux-acpi/utilities
jannis3005
commented
5 years ago i hope everything is in the attached file
aymanbagabas
commented
5 years ago Your Matebook E doesn't use the same mechanism as other models. I'd like to investigate on this more if you're still interested.
[ 3.397014] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
dmesg is interesting because when I was looking at the DSDT table from your dump.txt I couldn't find a device that has the aforementioned GUID. This means that the dump.txt I'm afraid is not sufficient and this may be involved with more firmware data.Could you provide the rest of the firmware data? You could do the following.
cd /tmp
sudo cp -r /sys/firmware/acpi/tables firmware
sudo rm -f firmware/MSDM
sudo chown -R 1000:1000 firmware
zip -r firmware.zip firmwareWe're deleting MSDM because it includes your Windows license key and I don't think you wanna share that :smile: Now, save /tmp/firmware.zip somewhere in your system so then you can upload it here.
I'd need more info from dmesg but with verbose wmi. First, stick options wmi debug_event=1 debug_dump_wdg=1 in /etc/modprobe.d/wmi.conf. You could do
sudoedit /etc/modprobe.d/wmi.confThen copy options wmi debug_event=1 debug_dump_wdg=1 and paste it in /etc/modprobe.d/wmi.conf. Now, do sudo mkinitcpio -p linux and reboot. This would make dmesg dumps WMI data.
Please try out branch matebook-e. I've updated that branch to listen to events coming from your device. You could do the following to branch to matebook-e, compile the code, and then test it.
git clone https://github.com/aymanbagabas/Huawei-WMI.git
cd Huawei-WMI
git checkout matebook-e
make
sudo rmmod huawei_wmi
sudo insmod huawei-wmi.koNow, try out all the special keys from F1 to F10. Nothing would happen but I'm interested in the logs that the driver would record on dmesg. This should also include the wmi data from step 2.
After you do these three steps use dmesg > dmesg.txt and upload dmesg.txt and firmware.zip here.
Please let me know if you have any questions or if you're having any troubles. These data would help debug the issue and hopefully, we can fix it and get it to work.
aymanbagabas
commented
5 years ago Can you also provide lsusb -v and lspci -nnv? Since the keyboard is detachable and there is a keyboard driver firmware on https://consumer.huawei.com/en/support/laptops/matebook-e/ , this might need an extra driver :crossed_fingers: hopefully not.
jannis3005
commented
5 years ago hope I've got everything correct :)
aymanbagabas
commented
5 years ago Hi @jannis3005,
Thank you for taking the time and yes, you got everything correct thank you!
The Matebook E is interesting, looking at the provided firmware files, it appears to follow the same mechanism that the Matebook X has. It uses the same "legacy" interface. Check out #9 for more info. If you'd like to help with that, I'd really appreciate it.
Now, your dmesg log shows Unknown response type 3 at the bottom. I've updated matebook-e branch to print out incoming keycodes. Make sure you have both debug_event=1 and debug_dump_wdg=1 in your /etc/modprobe.d/wmi.conf then do sudo mkinitcpio -p linux. If you have both enabled, you should see a DEBUG message in dmesg everytime you press a special key. Please do the following:
rm -rf Huawei-WMI
git clone https://github.com/aymanbagabas/Huawei-WMI.git
cd Huawei-WMI
git checkout matebook-e
make
sudo rmmod huawei_wmi
sudo insmod huawei-wmi.koNow, try all of the Fn row, special keys, and observe changes in dmesg -w. After pressing all of F1-F12, please provide dmesg > dmesg.txt file.
Here's the decompiled BMOF data section from your DSDT firmware table. mbe-wmi0-bmof.txt
It looks like the one from the Matebook X here. Apparently, the tables from acpidump are different from the ones in firmware.zip which is new to me.
jannis3005
commented
5 years ago When I do dmesg -w and press all the keys from F1 to F12 with the FN key set to media functionality, nothing happens. I've attached dmesg.txt anyways. I think I followed all of your instructions correctly. Shouldn't dmesg -w print out all the pressed keys from the WMI?
cat /etc/modprobe.d/wmi.confoptions wmi debug_event=1 debug_dump_wdg=1
aymanbagabas
commented
5 years ago Could you try adding wmi.debug_event=1 wmi.debug_dump_wdg=1 to your cmdline and then reboot. If you're using GRUB, it would go in /etc/default/grub. You to have update your GRUB menu using sudo grub-mkconfig -o /boot/grub/grub.cfg. Also it looks like the driver didn't get loaded since it's an out of kernel driver, dmesg should give a warning when insmod the driver. When loaded, you should get a message like this
[ 3.319924] huawei_wmi: loading out-of-tree module taints kernel.
[ 3.319967] huawei_wmi: module verification failed: signature and/or required key missing - tainting kernelPlease try the following:
sudo mkdir /lib/modules/$(uname -r)/updates/
rm -rf Huawei-WMI
git clone https://github.com/aymanbagabas/Huawei-WMI.git
cd Huawei-WMI
git checkout matebook-e
make
sudo cp huawei-wmi.ko /lib/modules/$(uname -r)/updates/
sudo depmod
sudo depmod -aMake sure non of the above commands fail or give you an error message.
Now reboot, press all Fn keys while observing dmesg -w and upload dmesg > dmesg.txt.
jannis3005
commented
5 years ago This is weird. I followed all of your instructions, there were no errors. After rebooting, when I run lsmod it shows huawei_wmi as a loaded module. But it still doesn't show anything on dmesg -w. I tried it again with the first method, but with the GRUB cmdline parameters set, and it shows the module with lsmod and it does not give an error on insmod. but still, i do not get any output when pressing the keys.
jannis3005
commented
5 years ago I just tried the following: I removed the kernel module and rebooted. then i run dmesg -w before running insmod huawei_wmi.ko. The moment i run insmod huawei_wmi.ko, 4 lines pop up in dmesg:
[ 237.428891] GUID 59142400-C6A3-40fa-BADB-8A2652834100
[ 237.428933] input: Huawei WMI hotkeys as /devices/platform/huawei-wmi/input/input31
[ 237.429008] GUID ABBC0F5C-8EA1-11D1-A000-C90629100000
[ 237.429041] input: Huawei WMI hotkeys as /devices/platform/huawei-wmi/input/input32so it seems to be loading correctly
aymanbagabas
commented
5 years ago @jannis3005 I sort of see the problem now.
Nothing wrong with the driver, the issue is that the keyboard is connected through USB as you can see in this comment lsusb -v Bus 001 Device 002: ID 12d1:1097 Huawei Technologies Co., Ltd. That's the keyboard USB device.
Now, I want you to try sudo evtest with the device corresponding to this USB device. It might have the name of 12d1:1097 Huawei Technologies Co., Ltd., HOLTEK, or USB-HID KB MS and get the output after pressing the hotkeys. If that didn't work, try to find the device in sudo evtest that detects brightness keys since brightness down works for you. The display key is different, it's actually mapped to Super-p which cycles through display options and works in Windows, GNOME, KDE, etc.
The issue is that we're missing the USB driver that reports events to Huawei-WMI. You're getting nothing because events from this USB device doesn't go anywhere and that's why you're not getting anything in dmesg. Using options wmi debug_event=1 debug_dump_wdg=1, dmesg should report ANY WMI event received, something like this
[10000.569616] wmi: DEBUG Event INTEGER_TYPE - 641
[10000.569625] wmi: DEBUG Event GUID: ABBC0F5C-8EA1-11D1-A000-C90629100000And that's without the driver being loaded notice 641 is 0x281 which is the brightness down key defined here.
Once this "theory" is confirmed, I'll put some code up to fix this. We might not need any extra drivers, it could be as easy as a hwdb table added to systemd-udev.
Also, I'm curious, what do you have under /sys/class/leds/?
Thank you for your support and contribution to this project.
jannis3005
commented
5 years ago Hey,
I found the correct device, take a look
also, here's
/sys/class/leds/aymanbagabas
commented
5 years ago That's great news! Please try the attached file using the method described in the readme. Feel free to adjust it as you like. Refer to /usr/include/linux/input-event-codes.h and for more info here.
Although it should hopefully work, I see from your output that F1-11 keys are being clicked. Are you sure Fn toggle is off? That's why you're getting ^@ and ^[OP etc. Use something like xev to detect that F1-11 keys aren't being triggered and report back.
Also I'd like to see what the other inputs have
/dev/input/event5: HOLTEK USB-HID KB MS Consumer Control
/dev/input/event6: HOLTEK USB-HID KB MS
/dev/input/event7: HOLTEK USB-HID KB MS TouchpadOne of them could lead us to a functional mic mute LED.
jannis3005
commented
5 years ago It seems to be a bit more complicated. The device listet as device 4 seems to be responsible for the monitor key, as well as print and paste. device 6 seems to be responsible for brightness up and down.
Though, Device 6 seems to report brightness down for both brightness down and up and the fn key.
as for device 5, it shows events for key_mute key_volumeup and down and a whole bunch of other stuff, however, when i press the buttons nothing outputs
well, and device 7 does excatly what the name suggests. it fires a whole bunch of events when touching the touchpad
jannis3005
commented
5 years ago jannis3005
commented
5 years ago Maybe some more details that i found out:
event4 seems to receive events for every key on the keyboard, EXCEPT: FN-Key Brightness-Down Brightness-UP Keyboard-Brightness Mute Volume-DOWN Volume-UP Mic-MUTE WIFI SETUP
However, it does receive events when pressing f1-f12, as well as screenmirrormodetoggle or hoewver that is called, and also for print and paste. The screenmirrormodetoggle event is received as LEFT_META.
The Volume-Keys on the side of the detachable tablet, located next to the fingerprint, do work. The events show up in event3, the AT Translated Set 2 Keyboard
I think the events of the media keys not working are supposed to show up in event6, where brightness down also shows up. but as you can see from the output above, the two brightness keys are indistignuishable. I dont know if it helps, but i checked the scancodes using showkey --scancodes. brightness down und brightness up and fn key have the same scancode, all the not working keys also dont have a scancode
aymanbagabas
commented
5 years ago as for device 5, it shows events for key_mute key_volumeup and down and a whole bunch of other stuff, however, when i press the buttons nothing outputs
I'm interested in this. Please upload sudo evtest output after pressing all special keys.
This comment will help you debug the issue even further so take a look. A usbhid-dump output would be really helpful here. https://github.com/DIGImend/usbhid-dump
Seems like there is a driver for hid-holtek same manufacturer as your keyboard in the linux kernel https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/hid/hid-holtek-kbd.c . But it's not the same keyboard 04d9:a055 so I don't know if that would work. Can you provide your lsmod?
jannis3005
commented
5 years ago Sorry for the late response, here are the outputs:
sudo evtestusbhid-dump --entitiy=all model=12d1lsmodjannis3005
commented
5 years ago For usbhid-dump the key order pressed is: fn-key > brighness-down > brightness-up > Keyboard brightness > ... > WIFI > Setup > print > paste
aymanbagabas
commented
5 years ago For usbhid-dump the key order pressed is: fn-key > brighness-down > brightness-up > Keyboard brightness > ... > WIFI > Setup > print > paste
Just to be clear, when you say fn-key, do you mean fn key was toggled on? LED is on? Because that would produce F1-F12 keys to my knowledge.
jannis3005
commented
5 years ago No for sure it wasn't on
jannis3005
commented
4 years ago @aymanbagabas are you still interested in trying to solve this?
aymanbagabas
commented
4 years ago @aymanbagabas are you still interested in trying to solve this?
I don't really have the tools (Matebook E) and knowledge (I know nothing about HID). I'm sure a HID driver for this would have a lot in common with Huawei-WMI driver. Closing for now since it's not related to Huawei-WMI.
aymanbagabas
commented
4 years ago You know what, this seems interesting. Now that I've seen this tool, this should be very trivial (ofc after doing some more reading about USB HID). If you'd be willing to help in building this I'd be happy to work on it.
These were taken from https://github.com/aymanbagabas/Huawei-WMI/issues/19#issuecomment-531661897 USB HID dump. We have 4 descriptors for 4 devices (shown in the evtest). Now we need to know which one is which and which one needs working on.
aymanbagabas
commented
4 years ago Can you run usbhid-dump again, press all special keys, and attach that here? (please indicate which stream corresponds with what key) So basically, a STREAM is the data coming from the usb device. We need to translate them to key presses (though I'm not yet sure how).
jannis3005
commented
4 years ago Here you go :)
usbhid-dumpaymanbagabas
commented
4 years ago Cool, now we gotta figure out how to translate these data to the input sub-system. Needs some research :) I still don't know if this necessarily needs a kernel driver or if it can be done in user-space.
hid-holtek-kbd this, for example, changes the device descriptor because it's faulty and thus needs a kernel driver. In our case, I'm not sure. Needs more investigation. LMK if you find anything (literally anything can be examples forums wikis) and I'll do the same whenever I have time.
jannis3005
commented
4 years ago Sure. Ill search whenever i've got some spare time :)
aymanbagabas
commented
4 years ago Alright, I might've found something. This tutorial explains how these descriptors work. First, we have 4 usbhid devices defined by the usb hub, each has its own descriptor. If you look at your lsusb dump, you can see that it defines 4 interfaces numbered from 0..3. Now looking at the dmesg log you provided, we can see that the system identified all 4 devices and mapped them to input devices which they are. These 4 devices define your touchpad, mouse, touchscreen, and keyboard (as you can see from the descriptors).
Now the one responsible for the special keys is provided by event6 i.e. 001:002:001 Bus001 Device002 Interface001 (you can see this in lsusb).
From that device descriptor, we can see that it has a vendor defined usage // Usage Page (Vendor Defined 0xFF01), which means, it probably needs a driver. You can also see the report ID (6) which corresponds with the stream data we're getting. The descriptor also defines one usage Usage (0x03) which is the same data coming from the streams. Looking at your evtest log for event6, we can see that it only defines the brightness down key with a value of ff010003. I'm very certain that this value corresponds to Usage Page (Vendor Defined 0xFF01) and Usage (0x03) -> ff010003.
TLDR, we might need to write a driver similar to hid-holtek-kbd but with a fixed descriptor that has all missing key usages defined.
jannis3005
commented
4 years ago Okay, that sounds pretty solid and looking at hid-holtek-kbd, also looks doable, even considering that I know almost nothing about kernel drivers
aymanbagabas
commented
4 years ago https://github.com/torvalds/linux/blob/master/drivers/hid/usbhid/hid-core.c#L67
This might be easier :)
On Fri, Jan 24, 2020, 12:19 AM Jannis Göing notifications@github.com wrote:
Okay, that sounds pretty solid and looking at hid-holtek-kbd, also looks doable, even considering that I know almost nothing about kernel drivers
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/aymanbagabas/Huawei-WMI/issues/19?email_source=notifications&email_token=AAYKJ3DDXSJHV7SO66DREYLQ7J26VA5CNFSM4IQGJ2M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJZYDXA#issuecomment-577995228, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYKJ3BMTNURXXVXBABBJ6DQ7J26VANCNFSM4IQGJ2MQ .
jannis3005
commented
4 years ago So this means we just give the USB HID Core Driver some Params?
aymanbagabas
commented
4 years ago Yes, you are right. You'd pass the fixed descriptors as parameters. My concern is how LEDs would work in this case.
On Fri, Jan 24, 2020, 3:51 AM Jannis Göing notifications@github.com wrote:
So this means we just give the USB HID Core Driver some Params?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/aymanbagabas/Huawei-WMI/issues/19?email_source=notifications&email_token=AAYKJ3CM6N2ZFD2WMXRQIA3Q7KTXJA5CNFSM4IQGJ2M2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJ2D6CY#issuecomment-578043659, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYKJ3EFREYPQNMT7DPJJYDQ7KTXJANCNFSM4IQGJ2MQ .
jannis3005
commented
4 years ago I'd suggest we look into getting the Buttons working at all first because that's the most important part and would make the most difference. The FN-LED works already. It Would just be the Microphone-LED we'd have to worry about afterwards. I could try and find out though, just have to find out how to find out first ;) :D
aymanbagabas
commented
4 years ago Try
quirks=0x12d1:0x1097:0x05,0x0C,0x09,0x01,0xA1,0x01,0x85,0x02,0x15,0x00,0x25,0x01,0x95,0x14,0x75,0x01,0x0A,0x83,0x01,0x0A,0x8A,0x01,0x0A,0x92,0x01,0x0A,0x94,0x01,0x09,0xCD,0x09,0xB7,0x09,0xB6,0x09,0xB5,0x09,0xE2,0x09,0xEA,0x09,0xE9,0x0A,0x21,0x02,0x0A,0x23,0x02,0x0A,0x24,0x02,0x0A,0x25,0x02,0x0A,0x26,0x02,0x0A,0x27,0x02,0x0A,0x2A,0x02,0x09,0x70,0x09,0x6F,0x81,0x02,0x95,0x01,0x75,0x0C,0x81,0x01,0xC0,0x06,0x01,0xFF,0x09,0x01,0xA1,0x01,0x85,0x06,0x15,0x00,0x26,0xFF,0x00,0x09,0x01,0x09,0x03,0x09,0x04,0x09,0x09,0x75,0x08,0x95,0x07,0x81,0x00,0xC0or
quirks=0x12d1:0x1097:0x050C0901A101850215002501951475010A83010A8A010A92010A940109CD09B709B609B509E209EA09E90A21020A23020A24020A25020A26020A27020A2A020970096F81029501750C8101C00601FF0901A1018506150026FF000901090309040909750895078100C0not sure how this works.
aymanbagabas
commented
4 years ago Put it in /etc/modprobe.d/usbhid.conf
options usbhid quirks=...Restart and test. Provide a dmesg log and evtest of event6.
jannis3005
commented
4 years ago i tried in cmdline usbhid.quirks=... with the first one, the entire keyboard stopped working, with the second one it was like before
jannis3005
commented
4 years ago For the first one:
jannis3005
commented
4 years ago For the second one:
jannis3005
commented
4 years ago I'll try and add that file to initframs
jannis3005
commented
4 years ago The first one breaks the entire keyboard and touchpad except for the FN-Toggle and Backlight & Backlight Toggle. Ill have to boot from live-usb and remove the quirks to be able to continue.
aymanbagabas
commented
4 years ago The first one breaks the entire keyboard and touchpad except for the FN-Toggle and Backlight & Backlight Toggle. Ill have to boot from live-usb and remove the quirks to be able to continue.
No need just override the modprobe during boot with GRUB https://wiki.archlinux.org/index.php/Kernel_module#Using_kernel_command_line set it back to usbhid.quirks=
aymanbagabas
commented
4 years ago Try this hid-huawei-1.zip
# extract
make
sudo insmod hid-huawei.koAgain please provide dmesg and evtest of event6 logs.
jannis3005
commented
4 years ago I cannot provide evtest of event6, since after insmod it is gone
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: Power Button
/dev/input/event3: AT Translated Set 2 keyboard
/dev/input/event4: HOLTEK USB-HID KB MS
/dev/input/event5: HOLTEK USB-HID KB MS
/dev/input/event7: HOLTEK USB-HID KB MS Mouse
/dev/input/event8: HOLTEK USB-HID KB MS Touchpad
/dev/input/event9: Intel HID events
/dev/input/event10: Intel HID 5 button array
/dev/input/event11: Intel Virtual Button driver
/dev/input/event12: PC Speaker
/dev/input/event13: Wacom HID 485B Pen
/dev/input/event14: Wacom HID 485B Finger
/dev/input/event15: HDA Intel PCH Mic
/dev/input/event16: HDA Intel PCH Front Headphone
/dev/input/event17: HDA Intel PCH HDMI/DP,pcm=3
/dev/input/event18: Huawei WMI hotkeys
/dev/input/event19: Huawei WMI hotkeys
/dev/input/event20: Video Bus
/dev/input/event21: HDA Intel PCH HDMI/DP,pcm=7
/dev/input/event22: HDA Intel PCH HDMI/DP,pcm=8
/dev/input/event23: HDA Intel PCH HDMI/DP,pcm=9
/dev/input/event24: HDA Intel PCH HDMI/DP,pcm=10I just wanna see if it changes anything for event4 and event5 (HOLTEK USB-HID KB MS) as what dmesg states after insmod.
jannis3005
commented
4 years ago Okay, here you go:
sudo evtest event4sudo evtest event5The Brightness-Down Event in Event5 comes from the FN-Key which still acts as Brightness down, however the Brightness-Keys that both workes as Brightness down before now do nothing
So we now know, that we can change something this way, but right now it's not the desired change :)
Hey @aymanbagabas,
I've tried getting it to work on the Matebook E, but I couldn't get it to work. Since I don't have any Experience in developing in C nor in developing device drivers, it would be cool if you could help me out.
Here's the output of the commands from your email.
lsmod
``` huawei_wmi 16384 0 ledtrig_audio 16384 3 snd_hda_codec_generic,huawei_wmi,snd_hda_codec_realtek wmi_bmof 16384 0 intel_wmi_thunderbolt 20480 0 wmi 36864 3 intel_wmi_thunderbolt,huawei_wmi,wmi_bmof sparse_keymap 16384 3 intel_hid,huawei_wmi,intel_vbtn ```dmesg
``` [ 0.000000] microcode: microcode updated early to revision 0xb4, date = 2019-04-01 [ 0.000000] Linux version 5.2.9-arch1-1-ARCH (builduser@heftig-119803) (gcc version 9.1.0 (GCC)) #1 SMP PREEMPT Fri Aug 16 11:29:43 UTC 2019 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ed16dad4-073a-47d3-aa81-d3b6c1441d82 rw audit=0 loglevel=3 quiet [ 0.000000] KERNEL supported cpus: [ 0.000000] Intel GenuineIntel [ 0.000000] AMD AuthenticAMD [ 0.000000] Hygon HygonGenuine [ 0.000000] Centaur CentaurHauls [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers' [ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR' [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64 [ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64 [ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format. [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000066825fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000066826000-0x0000000066826fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000066827000-0x000000006685afff] usable [ 0.000000] BIOS-e820: [mem 0x000000006685b000-0x000000006685bfff] reserved [ 0.000000] BIOS-e820: [mem 0x000000006685c000-0x0000000067b87fff] usable [ 0.000000] BIOS-e820: [mem 0x0000000067b88000-0x0000000068c87fff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x0000000068c88000-0x000000007ee9dfff] usable [ 0.000000] BIOS-e820: [mem 0x000000007ee9e000-0x000000007f09dfff] type 20 [ 0.000000] BIOS-e820: [mem 0x000000007f09e000-0x000000007f88dfff] reserved [ 0.000000] BIOS-e820: [mem 0x000000007f88e000-0x000000007ff7dfff] ACPI NVS [ 0.000000] BIOS-e820: [mem 0x000000007ff7e000-0x000000007fffdfff] ACPI data [ 0.000000] BIOS-e820: [mem 0x000000007fffe000-0x000000007fffefff] usable [ 0.000000] BIOS-e820: [mem 0x000000007ffff000-0x000000008cffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000171ffffff] usable [ 0.000000] NX (Execute Disable) protection: active [ 0.000000] efi: EFI v2.50 by INSYDE Corp. [ 0.000000] efi: ACPI 2.0=0x7fffd014 SMBIOS=0x7f114000 SMBIOS 3.0=0x7f112000 ESRT=0x7f110dd8 PROP=0x66822f98 [ 0.000000] SMBIOS 3.0.0 present. [ 0.000000] DMI: HUAWEI HUAWEI MateBook E/HUAWEI MateBook E, BIOS 2.07 10/31/2018 [ 0.000000] tsc: Detected 1600.000 MHz processor [ 0.001565] tsc: Detected 1608.000 MHz TSC [ 0.001565] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved [ 0.001569] e820: remove [mem 0x000a0000-0x000fffff] usable [ 0.001587] last_pfn = 0x172000 max_arch_pfn = 0x400000000 [ 0.001594] MTRR default type: write-back [ 0.001596] MTRR fixed ranges enabled: [ 0.001598] 00000-9FFFF write-back [ 0.001600] A0000-BFFFF uncachable [ 0.001602] C0000-FFFFF write-protect [ 0.001604] MTRR variable ranges enabled: [ 0.001607] 0 base 00C0000000 mask 7FC0000000 uncachable [ 0.001609] 1 base 00A0000000 mask 7FE0000000 uncachable [ 0.001611] 2 base 0090000000 mask 7FF0000000 uncachable [ 0.001612] 3 base 008C000000 mask 7FFC000000 uncachable [ 0.001614] 4 base 008A000000 mask 7FFE000000 uncachable [ 0.001616] 5 base 0089000000 mask 7FFF000000 uncachable [ 0.001618] 6 base 0088800000 mask 7FFF800000 uncachable [ 0.001619] 7 disabled [ 0.001620] 8 disabled [ 0.001621] 9 disabled [ 0.004254] x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT [ 0.004793] last_pfn = 0x7ffff max_arch_pfn = 0x400000000 [ 0.031391] esrt: Reserving ESRT space from 0x000000007f110dd8 to 0x000000007f110e38. [ 0.031408] check: Scanning 1 areas for low memory corruption [ 0.031417] Using GB pages for direct mapping [ 0.031421] BRK [0x12e601000, 0x12e601fff] PGTABLE [ 0.031425] BRK [0x12e602000, 0x12e602fff] PGTABLE [ 0.031427] BRK [0x12e603000, 0x12e603fff] PGTABLE [ 0.031486] BRK [0x12e604000, 0x12e604fff] PGTABLE [ 0.031490] BRK [0x12e605000, 0x12e605fff] PGTABLE [ 0.031745] BRK [0x12e606000, 0x12e606fff] PGTABLE [ 0.031806] BRK [0x12e607000, 0x12e607fff] PGTABLE [ 0.032009] BRK [0x12e608000, 0x12e608fff] PGTABLE [ 0.032074] BRK [0x12e609000, 0x12e609fff] PGTABLE [ 0.032157] BRK [0x12e60a000, 0x12e60afff] PGTABLE [ 0.032242] BRK [0x12e60b000, 0x12e60bfff] PGTABLE [ 0.032303] Secure boot could not be determined [ 0.032305] RAMDISK: [mem 0x36967000-0x374aafff] [ 0.032323] ACPI: Early table checksum verification disabled [ 0.032329] ACPI: RSDP 0x000000007FFFD014 000024 (v02 HUAWEI) [ 0.032336] ACPI: XSDT 0x000000007FFB0188 000104 (v01 HUAWEI KBL-ULT 00000000 01000013) [ 0.032347] ACPI: FACP 0x000000007FFDF000 00010C (v05 HUAWEI KBL-ULT 00000000 ACPI 00040000) [ 0.032357] ACPI: DSDT 0x000000007FFB4000 027824 (v02 HUAWEI KBL-ULT 00000000 ACPI 00040000) [ 0.032364] ACPI: FACS 0x000000007FF50000 000040 [ 0.032369] ACPI: UEFI 0x000000007FFFC000 000236 (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032374] ACPI: UEFI 0x000000007FFFB000 000042 (v01 HUAWEI KBL-ULT 00000002 ACPI 00040000) [ 0.032380] ACPI: ECDT 0x000000007FFFA000 0000C1 (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032386] ACPI: SSDT 0x000000007FFF8000 0010B6 (v01 HUAWEI KBL-ULT 00001000 ACPI 00040000) [ 0.032393] ACPI: MSDM 0x000000007FFF7000 000055 (v03 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032402] ACPI: SSDT 0x000000007FFF6000 000505 (v02 HUAWEI KBL-ULT 00001000 ACPI 00040000) [ 0.032407] ACPI: SSDT 0x000000007FFF5000 000046 (v02 HUAWEI KBL-ULT 00003000 ACPI 00040000) [ 0.032413] ACPI: TPM2 0x000000007FFF4000 000034 (v03 HUAWEI KBL-ULT 00000000 ACPI 00040000) [ 0.032418] ACPI: SSDT 0x000000007FFF0000 003120 (v02 HUAWEI KBL-ULT 00003000 ACPI 00040000) [ 0.032424] ACPI: SSDT 0x000000007FFE3000 00C7AF (v02 HUAWEI KBL-ULT 00001000 ACPI 00040000) [ 0.032429] ACPI: SSDT 0x000000007FFE2000 00077D (v02 HUAWEI KBL-ULT 00000000 ACPI 00040000) [ 0.032435] ACPI: ASPT 0x000000007FFE1000 000034 (v07 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032440] ACPI: BOOT 0x000000007FFE0000 000028 (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032445] ACPI: HPET 0x000000007FFDE000 000038 (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032451] ACPI: APIC 0x000000007FFDD000 0000BC (v03 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032456] ACPI: MCFG 0x000000007FFDC000 00003C (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032462] ACPI: SSDT 0x000000007FFB3000 0001BC (v02 HUAWEI KBL-ULT 00001000 ACPI 00040000) [ 0.032467] ACPI: WSMT 0x000000007FFB2000 000028 (v01 HUAWEI KBL-ULT 00000000 ACPI 00040000) [ 0.032473] ACPI: SSDT 0x000000007FFB1000 000BC9 (v02 HUAWEI KBL-ULT 00001000 ACPI 00040000) [ 0.032478] ACPI: DBGP 0x000000007FFAF000 000034 (v01 HUAWEI KBL-ULT 00000002 ACPI 00040000) [ 0.032484] ACPI: DBG2 0x000000007FFAE000 000054 (v00 HUAWEI KBL-ULT 00000002 ACPI 00040000) [ 0.032489] ACPI: SSDT 0x000000007FFAC000 001086 (v02 HUAWEI KBL-ULT 00001000 ACPI 00040000) [ 0.032495] ACPI: SSDT 0x000000007FFAB000 000EDE (v02 HUAWEI KBL-ULT 00003000 ACPI 00040000) [ 0.032500] ACPI: DMAR 0x000000007FFAA000 000180 (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032506] ACPI: NHLT 0x000000007FFA9000 00002D (v00 HUAWEI KBL-ULT 00000002 ACPI 00040000) [ 0.032511] ACPI: FPDT 0x000000007FFA8000 000044 (v01 HUAWEI KBL-ULT 00000002 ACPI 00040000) [ 0.032516] ACPI: BGRT 0x000000007FFA7000 000038 (v01 HUAWEI KBL-ULT 00000001 ACPI 00040000) [ 0.032531] ACPI: Local APIC address 0xfee00000 [ 0.032853] No NUMA configuration found [ 0.032855] Faking a node at [mem 0x0000000000000000-0x0000000171ffffff] [ 0.032861] NODE_DATA(0) allocated [mem 0x171ffc000-0x171ffffff] [ 0.032898] Zone ranges: [ 0.032900] DMA [mem 0x0000000000001000-0x0000000000ffffff] [ 0.032902] DMA32 [mem 0x0000000001000000-0x00000000ffffffff] [ 0.032905] Normal [mem 0x0000000100000000-0x0000000171ffffff] [ 0.032907] Device empty [ 0.032908] Movable zone start for each node [ 0.032910] Early memory node ranges [ 0.032912] node 0: [mem 0x0000000000001000-0x0000000000057fff] [ 0.032913] node 0: [mem 0x0000000000059000-0x000000000009dfff] [ 0.032915] node 0: [mem 0x0000000000100000-0x0000000066825fff] [ 0.032916] node 0: [mem 0x0000000066827000-0x000000006685afff] [ 0.032917] node 0: [mem 0x000000006685c000-0x0000000067b87fff] [ 0.032919] node 0: [mem 0x0000000068c88000-0x000000007ee9dfff] [ 0.032920] node 0: [mem 0x000000007fffe000-0x000000007fffefff] [ 0.032921] node 0: [mem 0x0000000100000000-0x0000000171ffffff] [ 0.033035] Zeroed struct page in unavailable ranges: 8903 pages [ 0.033037] Initmem setup node 0 [mem 0x0000000000001000-0x0000000171ffffff] [ 0.033041] On node 0 totalpages: 982329 [ 0.033043] DMA zone: 64 pages used for memmap [ 0.033044] DMA zone: 22 pages reserved [ 0.033046] DMA zone: 3996 pages, LIFO batch:0 [ 0.033125] DMA32 zone: 7991 pages used for memmap [ 0.033127] DMA32 zone: 511389 pages, LIFO batch:63 [ 0.045866] Normal zone: 7296 pages used for memmap [ 0.045867] Normal zone: 466944 pages, LIFO batch:63 [ 0.054845] Reserving Intel graphics memory at [mem 0x89000000-0x8cffffff] [ 0.055537] ACPI: PM-Timer IO Port: 0x1808 [ 0.055540] ACPI: Local APIC address 0xfee00000 [ 0.055553] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [ 0.055555] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) [ 0.055556] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) [ 0.055557] ACPI: LAPIC_NMI (acpi_id[0x04] high edge lint[0x1]) [ 0.055558] ACPI: LAPIC_NMI (acpi_id[0x05] high edge lint[0x1]) [ 0.055560] ACPI: LAPIC_NMI (acpi_id[0x06] high edge lint[0x1]) [ 0.055561] ACPI: LAPIC_NMI (acpi_id[0x07] high edge lint[0x1]) [ 0.055562] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1]) [ 0.055599] IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-119 [ 0.055603] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [ 0.055606] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [ 0.055609] ACPI: IRQ0 used by override. [ 0.055611] ACPI: IRQ9 used by override. [ 0.055615] Using ACPI (MADT) for SMP configuration information [ 0.055618] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.055647] smpboot: Allowing 4 CPUs, 0 hotplug CPUs [ 0.055707] PM: Registered nosave memory: [mem 0x00000000-0x00000fff] [ 0.055711] PM: Registered nosave memory: [mem 0x00058000-0x00058fff] [ 0.055714] PM: Registered nosave memory: [mem 0x0009e000-0x000fffff] [ 0.055717] PM: Registered nosave memory: [mem 0x66826000-0x66826fff] [ 0.055721] PM: Registered nosave memory: [mem 0x6685b000-0x6685bfff] [ 0.055724] PM: Registered nosave memory: [mem 0x67b88000-0x68c87fff] [ 0.055727] PM: Registered nosave memory: [mem 0x7ee9e000-0x7f09dfff] [ 0.055729] PM: Registered nosave memory: [mem 0x7f09e000-0x7f88dfff] [ 0.055730] PM: Registered nosave memory: [mem 0x7f88e000-0x7ff7dfff] [ 0.055731] PM: Registered nosave memory: [mem 0x7ff7e000-0x7fffdfff] [ 0.055735] PM: Registered nosave memory: [mem 0x7ffff000-0x8cffffff] [ 0.055736] PM: Registered nosave memory: [mem 0x8d000000-0xdfffffff] [ 0.055737] PM: Registered nosave memory: [mem 0xe0000000-0xefffffff] [ 0.055738] PM: Registered nosave memory: [mem 0xf0000000-0xfcffffff] [ 0.055739] PM: Registered nosave memory: [mem 0xfd000000-0xfe7fffff] [ 0.055741] PM: Registered nosave memory: [mem 0xfe800000-0xfebfffff] [ 0.055742] PM: Registered nosave memory: [mem 0xfec00000-0xfec00fff] [ 0.055743] PM: Registered nosave memory: [mem 0xfec01000-0xfecfffff] [ 0.055744] PM: Registered nosave memory: [mem 0xfed00000-0xfed00fff] [ 0.055745] PM: Registered nosave memory: [mem 0xfed01000-0xfed0ffff] [ 0.055747] PM: Registered nosave memory: [mem 0xfed10000-0xfed19fff] [ 0.055748] PM: Registered nosave memory: [mem 0xfed1a000-0xfed83fff] [ 0.055749] PM: Registered nosave memory: [mem 0xfed84000-0xfed84fff] [ 0.055750] PM: Registered nosave memory: [mem 0xfed85000-0xfedfffff] [ 0.055752] PM: Registered nosave memory: [mem 0xfee00000-0xfee00fff] [ 0.055753] PM: Registered nosave memory: [mem 0xfee01000-0xff9fffff] [ 0.055754] PM: Registered nosave memory: [mem 0xffa00000-0xffffffff] [ 0.055758] [mem 0x8d000000-0xdfffffff] available for PCI devices [ 0.055760] Booting paravirtualized kernel on bare hardware [ 0.055765] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370452778343963 ns [ 0.267610] setup_percpu: NR_CPUS:320 nr_cpumask_bits:320 nr_cpu_ids:4 nr_node_ids:1 [ 0.268002] percpu: Embedded 54 pages/cpu s184320 r8192 d28672 u524288 [ 0.268019] pcpu-alloc: s184320 r8192 d28672 u524288 alloc=1*2097152 [ 0.268021] pcpu-alloc: [0] 0 1 2 3 [ 0.268061] Built 1 zonelists, mobility grouping on. Total pages: 966956 [ 0.268063] Policy zone: Normal [ 0.268066] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ed16dad4-073a-47d3-aa81-d3b6c1441d82 rw audit=0 loglevel=3 quiet [ 0.268152] audit: disabled (until reboot) [ 0.275921] Calgary: detecting Calgary via BIOS EBDA area [ 0.275924] Calgary: Unable to locate Rio Grande table in EBDA - bailing! [ 0.291598] Memory: 3707924K/3929316K available (12291K kernel code, 1319K rwdata, 3900K rodata, 1612K init, 3616K bss, 221392K reserved, 0K cma-reserved) [ 0.291830] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.291850] Kernel/User page tables isolation: enabled [ 0.291876] ftrace: allocating 37366 entries in 146 pages [ 0.324336] rcu: Preemptible hierarchical RCU implementation. [ 0.324338] rcu: CONFIG_RCU_FANOUT set to non-default value of 32. [ 0.324342] rcu: RCU dyntick-idle grace-period acceleration is enabled. [ 0.324345] rcu: RCU restricting CPUs from NR_CPUS=320 to nr_cpu_ids=4. [ 0.324346] rcu: RCU priority boosting: priority 1 delay 500 ms. [ 0.324353] Tasks RCU enabled. [ 0.324357] rcu: RCU calculated value of scheduler-enlistment delay is 30 jiffies. [ 0.324358] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.327784] NR_IRQS: 20736, nr_irqs: 1024, preallocated irqs: 16 [ 0.328073] rcu: Offload RCU callbacks from CPUs: (none). [ 0.328279] random: get_random_bytes called from start_kernel+0x37e/0x559 with crng_init=0 [ 0.328323] Console: colour dummy device 80x25 [ 0.328330] printk: console [tty0] enabled [ 0.328364] ACPI: Core revision 20190509 [ 0.329170] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635855245 ns [ 0.329207] hpet clockevent registered [ 0.329269] APIC: Switch to symmetric I/O mode setup [ 0.329274] DMAR: Host address width 39 [ 0.329276] DMAR: DRHD base: 0x000000fed90000 flags: 0x0 [ 0.329288] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap 1c0000c40660462 ecap 19e2ff0505e [ 0.329290] DMAR: DRHD base: 0x000000fed91000 flags: 0x1 [ 0.329299] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap d2008c40660462 ecap f050da [ 0.329301] DMAR: RMRR base: 0x0000007f78a000 end: 0x0000007f7a9fff [ 0.329305] DMAR: RMRR base: 0x00000088800000 end: 0x0000008cffffff [ 0.329307] DMAR: ANDD device: 1 name: \_SB.PCI0.I2C0 [ 0.329309] DMAR: ANDD device: 2 name: \_SB.PCI0.I2C1 [ 0.329310] DMAR: ANDD device: 3 name: \_SB.PCI0.I2C2 [ 0.329311] DMAR: ANDD device: 7 name: \_SB.PCI0.SPI0 [ 0.329312] DMAR: ANDD device: 8 name: \_SB.PCI0.SPI1 [ 0.329313] DMAR: ANDD device: 9 name: \_SB.PCI0.UA00 [ 0.329316] DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 [ 0.329317] DMAR-IR: HPET id 0 under DRHD base 0xfed91000 [ 0.329319] DMAR-IR: Queued invalidation will be enabled to support x2apic and Intr-remapping. [ 0.331181] DMAR-IR: Enabled IRQ remapping in x2apic mode [ 0.331183] x2apic enabled [ 0.331203] Switched APIC routing to cluster x2apic. [ 0.335380] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 [ 0.349227] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x172daa3a18b, max_idle_ns: 440795212390 ns [ 0.349236] Calibrating delay loop (skipped), value calculated using timer frequency.. 3217.00 BogoMIPS (lpj=5360000) [ 0.349240] pid_max: default: 32768 minimum: 301 [ 0.355700] LSM: Security Framework initializing [ 0.355709] Yama: becoming mindful. [ 0.356721] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.357235] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.357268] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) [ 0.357285] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes) [ 0.357566] *** VALIDATE proc *** [ 0.357654] *** VALIDATE cgroup1 *** [ 0.357656] *** VALIDATE cgroup2 *** [ 0.357755] mce: CPU0: Thermal monitoring enabled (TM1) [ 0.357793] process: using mwait in idle threads [ 0.357798] Last level iTLB entries: 4KB 64, 2MB 8, 4MB 8 [ 0.357800] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0, 1GB 4 [ 0.357802] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization [ 0.357804] Spectre V2 : Mitigation: Full generic retpoline [ 0.357806] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch [ 0.357807] Spectre V2 : Enabling Restricted Speculation for firmware calls [ 0.357811] Spectre V2 : mitigation: Enabling conditional Indirect Branch Prediction Barrier [ 0.357812] Spectre V2 : User space: Mitigation: STIBP via seccomp and prctl [ 0.357815] Speculative Store Bypass: Mitigation: Speculative Store Bypass disabled via prctl and seccomp [ 0.357821] MDS: Mitigation: Clear CPU buffers [ 0.358340] Freeing SMP alternatives memory: 32K [ 0.362744] TSC deadline timer enabled [ 0.362757] smpboot: CPU0: Intel(R) Core(TM) i5-7Y54 CPU @ 1.20GHz (family: 0x6, model: 0x8e, stepping: 0x9) [ 0.382629] Performance Events: PEBS fmt3+, Skylake events, 32-deep LBR, full-width counters, Intel PMU driver. [ 0.382645] ... version: 4 [ 0.382646] ... bit width: 48 [ 0.382647] ... generic registers: 4 [ 0.382649] ... value mask: 0000ffffffffffff [ 0.382650] ... max period: 00007fffffffffff [ 0.382651] ... fixed-purpose events: 3 [ 0.382653] ... event mask: 000000070000000f [ 0.389248] rcu: Hierarchical SRCU implementation. [ 0.412802] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter. [ 0.419276] smp: Bringing up secondary CPUs ... [ 0.459303] x86: Booting SMP configuration: [ 0.459305] .... node #0, CPUs: #1 #2 [ 0.501751] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [ 0.539309] #3 [ 0.541207] smp: Brought up 1 node, 4 CPUs [ 0.541207] smpboot: Max logical packages: 1 [ 0.541207] smpboot: Total of 4 processors activated (12869.00 BogoMIPS) [ 0.542890] devtmpfs: initialized [ 0.542890] x86/mm: Memory block size: 128MB [ 0.543391] PM: Registering ACPI NVS region [mem 0x66826000-0x66826fff] (4096 bytes) [ 0.543391] PM: Registering ACPI NVS region [mem 0x67b88000-0x68c87fff] (17825792 bytes) [ 0.543391] PM: Registering ACPI NVS region [mem 0x7f88e000-0x7ff7dfff] (7274496 bytes) [ 0.543391] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 6370867519511994 ns [ 0.543391] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.543391] pinctrl core: initialized pinctrl subsystem [ 0.543391] PM: RTC time: 15:54:01, date: 2019-08-27 [ 0.543391] NET: Registered protocol family 16 [ 0.543520] cpuidle: using governor ladder [ 0.543520] cpuidle: using governor menu [ 0.545945] Simple Boot Flag at 0x44 set to 0x1 [ 0.546001] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [ 0.546003] ACPI: bus type PCI registered [ 0.546006] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5 [ 0.546161] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000) [ 0.546181] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in E820 [ 0.546181] PCI: Using configuration type 1 for base access [ 0.546288] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [ 0.547567] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages [ 0.547567] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages [ 0.552739] ACPI: Added _OSI(Module Device) [ 0.552741] ACPI: Added _OSI(Processor Device) [ 0.552743] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.552745] ACPI: Added _OSI(Processor Aggregator Device) [ 0.552750] ACPI: Added _OSI(Linux-Dell-Video) [ 0.552752] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [ 0.552756] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [ 0.634475] ACPI: 11 ACPI AML tables successfully acquired and loaded [ 0.638261] ACPI: EC: EC started [ 0.638262] ACPI: EC: interrupt blocked [ 0.642932] ACPI: \: Used as first EC [ 0.642935] ACPI: \: GPE=0x50, EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.642936] ACPI: EC: Boot ECDT EC used to handle transactions [ 0.648608] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [ 0.709586] ACPI: Dynamic OEM Table Load: [ 0.709615] ACPI: SSDT 0xFFFF8D52EC817800 000507 (v02 PmRef Cpu0Ist 00003000 INTL 20160527) [ 0.710800] ACPI: \_PR_.CPU0: _OSC native thermal LVT Acked [ 0.713212] ACPI: Dynamic OEM Table Load: [ 0.713227] ACPI: SSDT 0xFFFF8D52ECBD0C00 0003FF (v02 PmRef Cpu0Cst 00003001 INTL 20160527) [ 0.714340] ACPI: Dynamic OEM Table Load: [ 0.714352] ACPI: SSDT 0xFFFF8D52ECB04600 000115 (v02 PmRef Cpu0Hwp 00003000 INTL 20160527) [ 0.715130] ACPI: Dynamic OEM Table Load: [ 0.715141] ACPI: SSDT 0xFFFF8D52ECB05400 0001A4 (v02 PmRef HwpLvt 00003000 INTL 20160527) [ 0.716783] ACPI: Dynamic OEM Table Load: [ 0.716799] ACPI: SSDT 0xFFFF8D52EC815000 00065C (v02 PmRef ApIst 00003000 INTL 20160527) [ 0.718555] ACPI: Dynamic OEM Table Load: [ 0.718567] ACPI: SSDT 0xFFFF8D52ECB05600 000197 (v02 PmRef ApHwp 00003000 INTL 20160527) [ 0.719603] ACPI: Dynamic OEM Table Load: [ 0.719614] ACPI: SSDT 0xFFFF8D52ECB04400 00018A (v02 PmRef ApCst 00003000 INTL 20160527) [ 0.723391] ACPI: Interpreter enabled [ 0.723494] ACPI: (supports S0 S3 S4 S5) [ 0.723496] ACPI: Using IOAPIC for interrupt routing [ 0.723582] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.725054] ACPI: Enabled 6 GPEs in block 00 to 7F [ 0.752080] ACPI: Power Resource [WRST] (on) [ 0.752906] ACPI: Power Resource [WRST] (on) [ 0.753721] ACPI: Power Resource [WRST] (on) [ 0.754537] ACPI: Power Resource [WRST] (on) [ 0.755343] ACPI: Power Resource [WRST] (on) [ 0.756155] ACPI: Power Resource [WRST] (on) [ 0.756959] ACPI: Power Resource [WRST] (on) [ 0.757759] ACPI: Power Resource [WRST] (on) [ 0.758880] ACPI: Power Resource [WRST] (on) [ 0.759688] ACPI: Power Resource [WRST] (on) [ 0.760491] ACPI: Power Resource [WRST] (on) [ 0.761291] ACPI: Power Resource [WRST] (on) [ 0.762021] ACPI: Power Resource [WRST] (on) [ 0.762779] ACPI: Power Resource [WRST] (on) [ 0.763526] ACPI: Power Resource [WRST] (on) [ 0.764258] ACPI: Power Resource [WRST] (on) [ 0.764997] ACPI: Power Resource [WRST] (on) [ 0.765734] ACPI: Power Resource [WRST] (on) [ 0.766471] ACPI: Power Resource [WRST] (on) [ 0.767207] ACPI: Power Resource [WRST] (on) [ 0.789276] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-fe]) [ 0.789288] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3] [ 0.796047] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug SHPCHotplug PME AER PCIeCapability LTR] [ 0.796049] acpi PNP0A08:00: FADT indicates ASPM is unsupported, using BIOS configuration [ 0.801147] PCI host bridge to bus 0000:00 [ 0.801151] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.801154] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.801156] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.801158] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000c3fff window] [ 0.801160] pci_bus 0000:00: root bus resource [mem 0x000c4000-0x000c7fff window] [ 0.801162] pci_bus 0000:00: root bus resource [mem 0x000c8000-0x000cbfff window] [ 0.801164] pci_bus 0000:00: root bus resource [mem 0x000cc000-0x000cffff window] [ 0.801166] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff window] [ 0.801167] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff window] [ 0.801169] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff window] [ 0.801171] pci_bus 0000:00: root bus resource [mem 0x000dc000-0x000dffff window] [ 0.801173] pci_bus 0000:00: root bus resource [mem 0x000e0000-0x000e3fff window] [ 0.801175] pci_bus 0000:00: root bus resource [mem 0x000e4000-0x000e7fff window] [ 0.801177] pci_bus 0000:00: root bus resource [mem 0x000e8000-0x000ebfff window] [ 0.801179] pci_bus 0000:00: root bus resource [mem 0x000ec000-0x000effff window] [ 0.801180] pci_bus 0000:00: root bus resource [mem 0x000f0000-0x000fffff window] [ 0.801182] pci_bus 0000:00: root bus resource [mem 0x8d000000-0xdfffffff window] [ 0.801184] pci_bus 0000:00: root bus resource [mem 0xfd000000-0xfe7fffff window] [ 0.801187] pci_bus 0000:00: root bus resource [bus 00-fe] [ 0.801203] pci 0000:00:00.0: [8086:590c] type 00 class 0x060000 [ 0.803155] pci 0000:00:02.0: [8086:591e] type 00 class 0x030000 [ 0.803178] pci 0000:00:02.0: reg 0x10: [mem 0xa0000000-0xa0ffffff 64bit] [ 0.803190] pci 0000:00:02.0: reg 0x18: [mem 0x90000000-0x9fffffff 64bit pref] [ 0.803198] pci 0000:00:02.0: reg 0x20: [io 0x3000-0x303f] [ 0.803229] pci 0000:00:02.0: BAR 2: assigned to efifb [ 0.805185] pci 0000:00:04.0: [8086:1903] type 00 class 0x118000 [ 0.805210] pci 0000:00:04.0: reg 0x10: [mem 0xa1530000-0xa1537fff 64bit] [ 0.807248] pci 0000:00:05.0: [8086:1919] type 00 class 0x048000 [ 0.807271] pci 0000:00:05.0: reg 0x10: [mem 0xa1000000-0xa13fffff 64bit] [ 0.809263] pci 0000:00:13.0: [8086:9d35] type 00 class 0x000000 [ 0.809299] pci 0000:00:13.0: reg 0x10: [mem 0xa1542000-0xa1542fff 64bit] [ 0.811357] pci 0000:00:14.0: [8086:9d2f] type 00 class 0x0c0330 [ 0.811391] pci 0000:00:14.0: reg 0x10: [mem 0xa1500000-0xa150ffff 64bit] [ 0.811501] pci 0000:00:14.0: PME# supported from D3hot D3cold [ 0.813639] pci 0000:00:14.2: [8086:9d31] type 00 class 0x118000 [ 0.813673] pci 0000:00:14.2: reg 0x10: [mem 0xa1543000-0xa1543fff 64bit] [ 0.815794] pci 0000:00:14.3: [8086:9d32] type 00 class 0x048000 [ 0.815926] pci 0000:00:14.3: reg 0x10: [mem 0xa1510000-0xa151ffff 64bit] [ 0.818494] pci 0000:00:15.0: [8086:9d60] type 00 class 0x118000 [ 0.818759] pci 0000:00:15.0: reg 0x10: [mem 0xa1544000-0xa1544fff 64bit] [ 0.821805] pci 0000:00:15.1: [8086:9d61] type 00 class 0x118000 [ 0.822069] pci 0000:00:15.1: reg 0x10: [mem 0xa1545000-0xa1545fff 64bit] [ 0.825121] pci 0000:00:15.2: [8086:9d62] type 00 class 0x118000 [ 0.825385] pci 0000:00:15.2: reg 0x10: [mem 0xa1546000-0xa1546fff 64bit] [ 0.828363] pci 0000:00:16.0: [8086:9d3a] type 00 class 0x078000 [ 0.828402] pci 0000:00:16.0: reg 0x10: [mem 0xa1547000-0xa1547fff 64bit] [ 0.828518] pci 0000:00:16.0: PME# supported from D3hot [ 0.830688] pci 0000:00:17.0: [8086:9d03] type 00 class 0x010601 [ 0.830718] pci 0000:00:17.0: reg 0x10: [mem 0xa1540000-0xa1541fff] [ 0.830730] pci 0000:00:17.0: reg 0x14: [mem 0xa154d000-0xa154d0ff] [ 0.830743] pci 0000:00:17.0: reg 0x18: [io 0x3080-0x3087] [ 0.830755] pci 0000:00:17.0: reg 0x1c: [io 0x3088-0x308b] [ 0.830767] pci 0000:00:17.0: reg 0x20: [io 0x3060-0x307f] [ 0.830779] pci 0000:00:17.0: reg 0x24: [mem 0xa154b000-0xa154b7ff] [ 0.830856] pci 0000:00:17.0: PME# supported from D3hot [ 0.833031] pci 0000:00:1d.0: [8086:9d18] type 01 class 0x060400 [ 0.833189] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold [ 0.835548] pci 0000:00:1e.0: [8086:9d27] type 00 class 0x118000 [ 0.835819] pci 0000:00:1e.0: reg 0x10: [mem 0xa1548000-0xa1548fff 64bit] [ 0.838887] pci 0000:00:1e.2: [8086:9d29] type 00 class 0x118000 [ 0.839158] pci 0000:00:1e.2: reg 0x10: [mem 0xa1549000-0xa1549fff 64bit] [ 0.842212] pci 0000:00:1e.3: [8086:9d2a] type 00 class 0x118000 [ 0.842482] pci 0000:00:1e.3: reg 0x10: [mem 0xa154a000-0xa154afff 64bit] [ 0.845465] pci 0000:00:1f.0: [8086:9d4b] type 00 class 0x060100 [ 0.847759] pci 0000:00:1f.2: [8086:9d21] type 00 class 0x058000 [ 0.847790] pci 0000:00:1f.2: reg 0x10: [mem 0xa153c000-0xa153ffff] [ 0.850014] pci 0000:00:1f.3: [8086:9d71] type 00 class 0x040380 [ 0.850061] pci 0000:00:1f.3: reg 0x10: [mem 0xa1538000-0xa153bfff 64bit] [ 0.850109] pci 0000:00:1f.3: reg 0x20: [mem 0xa1520000-0xa152ffff 64bit] [ 0.850192] pci 0000:00:1f.3: PME# supported from D3hot D3cold [ 0.852426] pci 0000:00:1f.4: [8086:9d23] type 00 class 0x0c0500 [ 0.852490] pci 0000:00:1f.4: reg 0x10: [mem 0xa154c000-0xa154c0ff 64bit] [ 0.852563] pci 0000:00:1f.4: reg 0x20: [io 0x3040-0x305f] [ 0.855295] pci 0000:01:00.0: [8086:24fd] type 00 class 0x028000 [ 0.855456] pci 0000:01:00.0: reg 0x10: [mem 0xa1400000-0xa1401fff 64bit] [ 0.856363] pci 0000:01:00.0: PME# supported from D0 D3hot D3cold [ 0.857342] pci 0000:00:1d.0: PCI bridge to [bus 01] [ 0.857351] pci 0000:00:1d.0: bridge window [mem 0xa1400000-0xa14fffff] [ 0.889655] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.889811] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *10 11 12 14 15) [ 0.889961] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.890110] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.890260] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.890414] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.890562] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.890711] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 *11 12 14 15) [ 0.893042] platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff] [ 0.893047] acpi MSFT0101:00: platform device creation failed: -16 [ 0.893717] ACPI: EC: interrupt unblocked [ 0.893749] ACPI: EC: event unblocked [ 0.893806] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x50, EC_CMD/EC_SC=0x66, EC_DATA=0x62 [ 0.893809] ACPI: \_SB_.PCI0.LPCB.EC0_: Boot DSDT EC used to handle transactions and events [ 0.893992] pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.893992] pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.893992] pci 0000:00:02.0: vgaarb: bridge control possible [ 0.893992] vgaarb: loaded [ 0.893992] ACPI: bus type USB registered [ 0.893992] usbcore: registered new interface driver usbfs [ 0.893992] usbcore: registered new interface driver hub [ 0.893992] usbcore: registered new device driver usb [ 0.893992] pps_core: LinuxPPS API ver. 1 registered [ 0.893992] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giomettievtest
``` Select the device event number [0-23]: 18 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "Huawei WMI hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 171 (KEY_CONFIG) Event code 190 (KEY_F20) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 238 (KEY_WLAN) Event code 240 (KEY_UNKNOWN) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Testing ... (interrupt to exit) ``` ```Select the device event number [0-23]: 17 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: "Huawei WMI hotkeys" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 171 (KEY_CONFIG) Event code 190 (KEY_F20) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 238 (KEY_WLAN) Event code 240 (KEY_UNKNOWN) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) Properties: Testing ... (interrupt to exit) ```When using in Terminal Emulator, Brightness Keys both just lower the brightness and the Monitor Config Key (F8) works, but testing stays empty. When runnig from TTY, the brighness keys result in
^@and the monitor config key inp, no result for the other keys, both with device 17 and 18.