Comment # 13 on bug 104064 from
(In reply to Alex Deucher from comment #12)
> (In reply to taijian from comment #11)
> > Addendum: What DOES work now without crashing the system is dynamically en-
> > and disabling the dGPU via
> > 
> > # echo "\\_SB.PCI0.PEG0.PEGP._{OFF|ON}" > /proc/acpi/call
> > 
> > So that is definitely progress!
> 
> Are you messing with that while the driver is loaded?  Doing so will cause
> problems because you're changing the hw state behind the driver's back.

Yeah, I know. The problem is that I cannot unload the driver, because modprobe
always complains about it being in use. However, I found that with 4.17-wip the
system actually remains stable after disabling the hardware, as long as I don't
try to use it - which was not the case before, where it would crash much
faster.

But seriously, what I'm doing is that I have two boot entries, one that
blacklists amdgpu and does the acpi_call thingy and one that doesn't. So one
for mobile usage, one for gaming. Would be nice, though, if I did not need to
reboot to switch between the two use cases...


You are receiving this mail because: