On 12/24/19 9:06 PM, You-Sheng Yang wrote: > What's inside other wmi_bus-PNP0C14* folders? /sys/class/wmi_bus/wmi_bus-PNP0C14\:01 7430019A-DCE9-4548-BAB0-9FDE0935CAFF device FCB424F1-075A-4E0E-BFC4-62F3E71771FA subsystem 7FF47003-3B6C-4E5E-A227-E979824A85D1 E2BE5EE3-42DA-49DB-8378-1F5247388202 power uevent
/sys/class/wmi_bus/wmi_bus-PNP0C14\:02 85D2E869-365A-4ACE-A4D3-CD692B1698A0 8F4D3679-749E-4479-9B16-C62601FD25F0 device power subsystem uevent /sys/class/wmi_bus/wmi_bus-PNP0C14\:03 40D1BF71-A82D-4E59-A168-3985E03B2E87 D9F41781-F633-4400-9355-601770BEC510 power uevent 431F16ED-0C2B-444C-B267-27DEB140CF9C device > By previous experience, BIOS vendor may implement some WMI interface > that can be used to control anything they want. Somehow such interfaces > could be misused on Linux as they're mostly designed for Windows. For > example, 86CCFD48-205E-4A77-9C48-2021CBEDE341 is for controlling Intel > thunderbolt power, and it should not appear on a platform without > thunderbolt ports. When it goes wrong, the most appropriate solution > should be in the BIOS side, so looking for new BIOS updates should be > the first thing you wanna try, but sometimes you can only try work > arounds like removing fwupd/boltd or so. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857307 Title: Wireless wouldn't turn on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1857307/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
