Public bug reported:
[Description]
In [1] two important fixes in BTRFS are listed:
8e928218780e2f1cf2f5891c7575e8f0b284fcce "btrfs: fix corruption reading
shared and compressed extents after hole punching"
4ea748e1d2c9f8a27332b949e8210dbbf392987e "btrfs: fix deadlock between
clone/dedupe and
Is it already fix in proposed?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode draws too much power
Status in gdm3 package in
Sorry, I have read above and understood why it's needed. I think prime-
select can leave a dummy file somewhere and systemd service nvidia-
fallback should be loaded when there is no this file written by prime-
select.
--
You received this bug notification because you are a member of Kernel
Also, something, probably prime-select, adds nouveau.runpm=0 to
GRUB_CMDLINE_LINUX_DEFAULT
$ cat `which prime-select` | grep nouveau.runpm
boot_params['nouveau.runpm'] = '0'
self._grub_path, ['nouveau.runpm',
'video=VGA'])
I don't understand why it does
--- /tmp/nvidia-fallback.service.orig 2018-08-27 23:52:21.739079571 +0300
+++ /tmp/nvidia-fallback.service2018-08-27 23:55:14.674338550 +0300
@@ -1,7 +1,8 @@
[Unit]
-Description=Fall back on nouveau if nvidia is not loaded
+Description=Fall back on nouveau if nvidia is not loaded and
Can you please explain why is nvidia-fallback needed? It worked without
it before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode
My hardware: Probe URL: https://linux-hardware.org/?probe=572f1e3e6a
nvidia-fallback.service loads nouveau when I switched PRIME to Intel. I
also see nouveau in `sensors` output. `systemctl disable nvidia-
fallback` seems to cure the ptoblem, nouveau kernel module is not loaded
any more and power
7 matches
Mail list logo
