Bugzilla

Warning for the overly adventurous: I just tried adding the `-amd_no_dgpu_accel` boot-arg, and it made my system temporarily unbootable. I got out of it by forcing a reset, then doing Cmd-R to boot into the Recovery partition, then using nvram in the Terminal app to get rid of this boot-arg.

I noticed that this boot-arg is recognized by the AMDRadeonX4000 kernel extension. Apparently it [disables the AMD GPU framebuffer](https://gist.github.com/mayankk2308/ba3aa2b529ea38a6c37e7a83e431cbe7). I hoped that this meant it wouldn't use "vidmem" at all, but only "system". Perhaps it did, but you can't test on a system you can't boot :-)

Warning for the overly adventurous: I just tried adding the `-amd_no_dgpu_accel` boot-arg, and it made my system temporarily unbootable. I got out of it by forcing a reset, then doing Cmd-R to boot into the Recovery partition, then using nvram in the Terminal app to get rid of this boot-arg.

I noticed that this boot-arg is recognized by the AMDRadeonX4000 kernel extension. Apparently it [disables the AMD GPU framebuffer](https://gist.github.com/mayankk2308/ba3aa2b529ea38a6c37e7a83e431cbe7). I hoped that this meant it wouldn't use "vidmem" at all, but only "sysmem". Perhaps it did, but you can't test on a system you can't boot :-)

Warning for the overly adventurous: I just tried adding the `-amd_no_dgpu_accel` kernel boot-arg, and it made my system temporarily unbootable. I got out of it by forcing a reset, then doing Cmd-R to boot into the Recovery partition, then using nvram in the Terminal app to get rid of this boot-arg.

I noticed that this boot-arg is recognized by the AMDRadeonX4000 kernel extension. Apparently it [disables the AMD GPU framebuffer](https://gist.github.com/mayankk2308/ba3aa2b529ea38a6c37e7a83e431cbe7). I hoped that this meant it wouldn't use "vidmem" at all, but only "sysmem". Perhaps it did, but you can't test on a system you can't boot :-)