Hi,

I'm in trouble with some things on my MSI GS40 running Tumbleweed:
- Bluetooth doesn't work at all
- if I have external monitor connected via HDMI, powersaving doesn't work (it
looks like that: first laptop monitor switching off, then, after some time,
external monitor switching off. But after some time it switching on again)
- if I plug my Headphones into the "Headphone" socket, there is no automatic
change from Speakers to Headphones
- if there was a powersaving attempt, I see that soundcard changed! Sometimes
that's Analogue Audio, sometimes that's Monitor HDMI Audio
- again after powersaving attempt was done or in the case when I finished DE
session and started it again, WiFi isn't working, I have to swtich it off and
on again to make it working.

I'm using KDE and tried many variants of Power Management: no luck
Same problem exists in other DE: GNOME, XFCE, Cinnamon so it doesn't looks like
DE-dependent

I suppose all mentioned problem relates to ACPI, during boot there are some
error messages:

ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND
(20170831/dswload-210)
ACPI Exception: AE_NOT_FOUND, During name lookup/catalog
(20170831/psobject-252)
ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp11) while loading table
(20170831/tbxfload-228)
ACPI Error: 1 table load failures, 8 successful (20170831/tbxfload-246)
ACPI Error: [^^^PEG0.PEGP.EASP] Namespace lookup failure, AE_NOT_FOUND
(20170831/psargs-364)
ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC._REG, AE_NOT_FOUND
(20170831/psparse-550)

Also there are 2 string where Bluetooth mentioned and they are about errors
again, I'm sure they are here but I can't find it in dmesg output.

These problem were here always since I bought GS40 and installed TW on it.

Before GS40 I had GE62 6QC with Tumbleweed running and I'd like to say there
were no such problem at all! Both GS40 and GE62 share the same Intel HM170
platform and very similar from perspective of hardware. So I suppose all
problems seems to be related with ACPI or, probably, the BIOS code problem.

Please help me to fix that, I'll provide any additional info in case if it's
needed.