Comment # 16
on bug 103678
from mikhail.v.gavrilov@gmail.com
> Interesting, that indeed that should work. Could be a bug in the VESA BIOS or the driver touching the hardware even if it decided not to do so. > Please try booting with modprobe.blacklist=amdgpu on the kernel commandline. Adding to blacklist amdgpu not solve problem, but it pushed me to the idea of doing the same thing with the intel driver. And after adding i915.modeset=0 i915.blacklist=1 graphics subsusystem was launched sucessful even with enabled IGPU in BIOS. It seems that the intel driver is culprit here.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
