Hey!
Hopefully I’m posting this in the right place. My 2020 Razer Blade Stealth (4K model) has issues that I believe are related to the graphics drivers.
Firstly, right after install (with nonfree) in order to actually boot acpi_osci="Windows 2019"
is required. I’m unsure if other values will work - they might - but that one gets us into the UI. Note that this only works on the i3 version. I’m pretty sure GDM isn’t happy about… something, with the GNOME distribution, but it won’t boot for me in any case, no matter what settings I try
Note that booting takes a long time (a few minutes), as does shutting down. Throughout this process these errors can be seen:
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:91:pipe A] flip_done timed out
[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:91:pipe A] flip_done timed out
Which I believe are the cause of the slowness, and related to the i915
driver. I’m going to try disabling the intel driver and just using nvidia later!
@durzo mentions this in this thread: https://forum.manjaro.org/t/drm-atomic-helper-flip-done-timed-out/17858
@tau is having a similar issue in this thread: https://forum.manjaro.org/t/laptop-is-not-waking-from-suspend/14571
Issue here: https://gitlab.freedesktop.org/drm/intel/-/issues/2414
Anyway, otherwise my clean install seems pretty functional! It’s using video-linux
and is pretty outdated though.
After an upgrade and reboot, the display is 800x600
. It can be changed with xrandr
so not a huge issue.
I upgraded to kernel 5.8 and installed the nvidia prime drivers (version 450), and this didn’t solve any issues.
Otherwise, there’s a thread on the Razer Insider forum here: https://insider.razer.com/index.php?threads/new-2020-stealth-linux-support.57151/
. Note that most people there are trying Ubuntu, which when I tried didn’t have properly functional graphics drivers + couldn’t control display brightness.
I’m not yet able to include links until discourse trusts me more, hence… the code block links.
From what I’ve gathered we’re just going to have to wait until i915 upstream has resolved the issues, but there’s an alternative configuration that might work