I think my i915-unleashed.service is unnecessarily dirty, any competent sysadmin will be probably triggered by it: https://codeberg.org/Breadly/.dotfiles/commit/a3b0807f2ec78415c39c78b7d47274385d630bd8
But it is working as intended 
(If you do have any tip to do it more properly it would be welcome tho)
@chesheer Yep! I'm using #X11 since the same time and saw:
- Kernel panic because of #Nvidia drivers
- Strange glitches and system freeze because of #intel #i915 drivers (in combination with #Libreboot and probably dying #GPU )
– Lagging interface in ~2006, because I've just installed #Radeon drivers and didn't configure 3D accel in #xorgconf
- #XServer ? Lol, it just works all the time 
Even when manual xorg.conf configuration were replaced by HAL, then by evdev...
Finally got my hardware brightness buttons to work in #BunsenLabs.
1. With root permission, append this string:
acpi_backlight=native
Between the quotes in the line:
GRUB_CMDLINE_DEFAULT=" "
Which is found in the file:
/etc/default/grub
2. Run in terminal:
sudo update grub
3. Reboot
4. Use hardware backlight keys as normal.
This took me over a week of scorched retinae to unearth. Now i post it here.
#Linux #Debian #Debian12 #CrunchBang #CrunchBangPlusPlus #oldlaptop #i915 #acpi #grub
Further testing @elementary I am very happy I eventually could fix the annoying "hanging screen" bug, which was due to a bug of the #i915 graphics driver. Now the whole experience is a lot better thanks to the great hint of @mikael I only read by chance.
https://github.com/elementary/gala/issues/2023
Now I hope the remaining glitches of the very important #AppCenter and #SoftwareUpdates parts are fixed before release of #OS8, because they don't seem stable enough to me right now.
What Happened? Using the current OS 8 preview/daily, Wayland session, ThinkPad X280, Intel graphics, I observe a complete freeze of the whole screen (including the mouse pointer) for seconds. Durin...
This is the source for #intel #i915 #sriov support using #dkms . Just wish support was in the OOTB kernels - not yet.
Even though the host is seemingly working, it's a bit fragile as will need rebuilding for each kernel update (pinned for now)
Anyone gone through this with the #n100 ? Surely there must be others?
Prior to this I tried full GPU passthrough (ie full device passthrough, not virtual gpu) , but couldn't get it to work reliably.
I don’t really understand the cause and effect here but I finally got rid of “GPU HANG” issue with #i915, i.e.
Breadly 
Eugene account has moved
Alex
OtterCynical
Johannes Brakensiek
Mikael Hansson
planetf1
Jarkko SakkinenJul 02 21:20:50 suppilovahvero kernel: i915 0000:03:00.0: [drm] GPU HANG: ecode 12:1:84dfd7f7, in ChaosGate.exe >
Jul 02 21:20:50 suppilovahvero kernel: i915 0000:03:00.0: [drm] ChaosGate.exe[40919] context reset due to GPU ha>
I did the following:
/etc/modprobe.d/i915.conf and run sudo dracut --force (in Fedora).The contents of /etc/modprobe.d/i915.conf are the following:
options i915 enable_guc=3
options i915 enable_fbc=1
I put these there because I found multiple forum posts etc. where this was the suggested solution but obviously I have zero idea what they’re doing 🤷 I’ve played Chaos Gate as a test without hangs, and it used to hang within just few minutes.
It is still a bit weird that #Fedora 40 with its default settings gives such crap results on Intel Arc A770.
Can someone tell me, why #i915 fails with #DRM issues, and starts with a black screen after #Grub - sometimes? Sending the system to sleep (standby) and waking resolves the black-screen.
Full dmesg: https://gist.github.com/AliveDevil/742f355ba24b80e7a19a3503c7e04b69
Ruling out hardware failure, because:
- Leap 15.5 didn't have this issue (5.14 kernel).
- Leap 15.6 started having this issue (6.4 kernel).
- Fedora 40 didn't have this issue (6.8, I guess?)
AliveDevil
Thomas Cherryhomes