[Desktop-packages] [Bug 2046224] Re: [amdgpu] Resolutions lower than max results in corrupted screen
This issue should be fixed by commit [1],
it had been merged by mantic 6.5 kernel, and will be released in next update.
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2de19022c5d7ff519dd5b9690f7713267bd1abfe
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
Status in linux package in Ubuntu:
New
Status in xorg-server package in Ubuntu:
New
Bug description:
Upgrading from 23.04 to 23.10 resulted in corrupt screen when
switching to lower resolutions. Only maximum resolution works.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: MATE
Date: Tue Dec 12 01:21:01 2023
DistUpgraded: 2023-12-10 13:34:46,170 DEBUG icon theme changed, re-reading
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev c2)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Phoenix [17aa:3c92]
InstallationDate: Installed on 2023-11-04 (38 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64
(20230807.2)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=2a5d61f3-134e-404f-bc44-06c827cf55f6 ro quiet splash
amd_pstate=guided vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-12-10 (1 days ago)
dmi.bios.date: 06/16/2023
dmi.bios.release: 1.34
dmi.bios.vendor: LENOVO
dmi.bios.version: M3CN34WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76463 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion Slim 5 16APH8
dmi.ec.firmware.release: 1.34
dmi.modalias:
dmi:bvnLENOVO:bvrM3CN34WW:bd06/16/2023:br1.34:efr1.34:svnLENOVO:pn82Y9:pvrLegionSlim516APH8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrLegionSlim516APH8:skuLENOVO_MT_82Y9_BU_idea_FM_LegionSlim516APH8:
dmi.product.family: Legion Slim 5 16APH8
dmi.product.name: 82Y9
dmi.product.sku: LENOVO_MT_82Y9_BU_idea_FM_Legion Slim 5 16APH8
dmi.product.version: Legion Slim 5 16APH8
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2046224/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Description changed:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the laptop's
internal one) and each attempt shows something different (at first it
tries to recover the contents of all 3 screens, then it shows only one
of them, and then it shows the same content on all 3, but it never gets
responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-generic 6.5.0.10.12
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Thu Nov 16 02:27:45 2023
InstallationDate: Installed on 2023-07-02 (137 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-10-generic N/A
linux-backports-modules-6.5.0-10-generic N/A
linux-firmware20230919.git3672ccab-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
dmi.bios.date: 06/13/2023
dmi.bios.release: 1.44
dmi.bios.vendor: LENOVO
dmi.bios.version: R1BET75W(1.44 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UD000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.44
dmi.modalias:
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
dmi.product.family: ThinkPad T14 Gen 1
dmi.product.name: 20UD000GUS
dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
dmi.product.version: ThinkPad T14 Gen 1
dmi.sys.vendor: LENOVO
+
+ X-HWE-Bug: Bug #2047389
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2043640
Title:
amdgpu: GPU Recovery fails, frequent hangs
Status in Mesa:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in mesa package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Confirmed
Status in mesa source package in Jammy:
New
Status in linux source package in Lunar:
Confirmed
Status in mesa source package in Lunar:
New
Bug description:
I've been using 23.04 for a few months, and experienced a total system
hang occasionally when sharing my screen over Zoom or Google Meet
(running on Google Chrome).
At first it hangs and then it periodically flashes like it's trying
(unsuccessfully) to recover; I've got 3 screens (including the
laptop's internal one) and each attempt shows something different (at
first it tries to recover the contents of all 3 screens, then it shows
only one of them, and then it shows the same content on all 3, but it
never gets responsive).
I've recently upgraded to 23.10, hoping a new kernel would help the
situation. It's only gotten considerably worse now; it hangs sometimes
just when opening Zoom; it's somehow easier to reproduce with Google
Chrome. Interestingly, it fails quickly and reliably now when enabling
my webcam (with special effects). It started hanging badly when using
Google Maps as well.
For all these behaviors, I suspect amdgpu is to blame (I'm running on
Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
anything interesting.
Any tips about debugging this further?
ProblemType: Bug
[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
Hi, The bug status of focal is in progress, will these patched be backported to focal? It blocks many OEM projects. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
Thanks BinLi, Also confirmed cdc_mbim with Quectel modem OK. ** Also affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in usb-modeswitch package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925779] Re: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port.
Tested on Sideswipe2-AMD, it used a new version of BIOS R1CET56W. HDMI audio works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925779 Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port. Status in alsa-driver package in Ubuntu: New Bug description: No sound at all when the audio output from HDMI port. [Steps to reproduce] 1. Install the daily build image on Lenovo T14s-AMD 2. Login the system 3. Connect the HDMI port with a Monitor 4. Select the 'Output Device' is HDMI 5. Try to play sound from the monitor [Actual result] No sound at all when the audio output from HDMI port. The internal speaker works normally. [Test image] http://cdimage.ubuntu.com/ubuntu/daily-live/current/hirsute-desktop-amd64.iso [Test Device] https://certification.canonical.com/hardware/202006-27964 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 06:18:01 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: u 1424 F pulseaudio /dev/snd/controlC1: u 1424 F pulseaudio /dev/snd/controlC0: u 1424 F pulseaudio /dev/snd/pcmC0D0c: u 1424 F...m pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET55T(1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UHZ5DXUS dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR1CET55T(1.24):bd09/15/2020:br1.24:efr1.24:svnLENOVO:pn20UHZ5DXUS:pvrThinkPadT14sGen1:rvnLENOVO:rn20UHZ5DXUS:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UHZ5DXUS dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920749] Re: [Lenovo ThinkPad X1 Yoga 4th] Computer stuck when screen touched with touchpen
Probably duplicated to 1920785. ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1920749 Title: [Lenovo ThinkPad X1 Yoga 4th] Computer stuck when screen touched with touchpen Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in xf86-input-wacom package in Ubuntu: Invalid Bug description: I have a Lenovo Thinkpad X1 Yoga 4th Gen. My OS version is 20.04. My touchscreen works fine, but when I use my pen the entire OS freezes and even any sound that plays repeats in a loop that is maybe half a second long. The only way I found to get out of this is to force shutdown. I can reproduce this on my laptop without fail. And it is independent of any program I have open. This problem started around 17th March (I don't remember exactly) and update almost every day. Description: Ubuntu 20.04.2 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2292] InstallationDate: Installed on 2020-05-09 (317 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QFS10B00 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18 Tags: focal ubuntu Uname: Linux 5.8.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET60W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN2HET60W(1.43):bd01/14/2021:br1.43:efr1.22:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFS10B00 dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1920749/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
Updated to xserver-xorg-core:amd64 (2:1.19.6-1ubuntu4.6, 2:1.19.6-1ubuntu4.7) Stock Bionic got multiple resolutions to set. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Released Status in xorg-server source package in Focal: Fix Released Status in xorg-server-hwe-18.04 source package in Focal: Invalid Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e this is required to support new laptop models which use such panels [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
Verified on stock Ubuntu 18.04.4 apt install xserver-xorg-core-hwe-18.04 (2:1.20.8-2ubuntu2.2~18.04.1) Multiple resolutions can be set then. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Confirmed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e this is required to support new laptop models which use such panels [Test case] Test that a proper list of modes is shown with a panel that uses the new EDID. [Regression potential] The patch retains the previous code path for setting modes on GTF-able monitors, and only adds support for non-GTF monitors. So in that sense there shouldn't be any regression potential, this has been reviewed by an upstream expert. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Tags added: oem-priority originate-from-1883198 sutton ** Tags added: originate-from-1882188 ** Tags added: originate-from-1881988 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg package in Ubuntu: New Bug description: Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Description changed: Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 + + https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e ** Changed in: xorg (Ubuntu) Importance: Undecided => Critical ** Changed in: xorg (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in HWE Next: New Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg package in Ubuntu: New Bug description: Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883497] Re: Only timing mode list in EDID supported on continuous freq monitors
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1883497 Title: Only timing mode list in EDID supported on continuous freq monitors Status in X.Org X server: New Status in xf86-video-intel: Unknown Status in xorg package in Ubuntu: New Bug description: Some new laptop display set EDID continuous freq bit 1. Then Xorg only uses the timing modes defined in EDID, no other modes are shown on Xorg. Upstream Bug: https://gitlab.freedesktop.org/drm/intel/-/issues/313 Fix of Xorg in merge request: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421 https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1883497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Re: Lenovo ThinkPad P73 touchpad does not work *after* installation
Please use hybrid GPU mode in BIOS. Or use psmouse.elantech_smbus=0 as workaround for now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1868474 Title: Lenovo ThinkPad P73 touchpad does not work *after* installation Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853440] Re: Volume either 0 or 100% on Lenovo X1 Carbon G7
Could you try linux-oem-osp1 kernel? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: pop:GNOME DisplayManager: gdm3 DistroRelease: Pop!_OS 19.10 Package: linux PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022-generic 5.3.7 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1pop0~1573683812~19.10~50e928a Tags: third-party-packages eoan Uname: Linux 5.3.0-22-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837962] Re: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while
** Also affects: libinput (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1837962 Title: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while Status in libinput: Unknown Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Bionic: New Status in libinput source package in Disco: Fix Released Status in libinput source package in Eoan: Fix Released Bug description: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1837962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1837962] [NEW] Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while
Public bug reported: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Tap-to-Click of SYNA8005 touchpad () failed to work after a while + Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1837962 Title: Tap-to-Click of SYNA8005 touchpad (06CB:CD8C) failed to work after a while Status in libinput package in Ubuntu: New Bug description: [Impact] 4.18+ kernel with Ubuntu 18.04. libinput 1.10.4-1 xserver-xorg-input-libinput 0.27.1-1 tap-to-click is on by default. After tapping on SYNA8005 (06CB:CD8C) for 50+ times, touchpad will be no response when tapping. [Fix] libinput detect these taps as palm, so permanently disable tap-to-click. upstream patch of libinput already fixed this issue: commit 237ebb7cc4e9bf035891176acb08b1bf558ee989 Author: Peter Hutterer Date: Mon Jun 25 14:50:22 2018 +1000 touchpad: don't disable tapping on MT_TOOL_PALM The tapping code can handle palm states now, so there is no need to disable tapping altogether when a tool-based palm is detected. Fixes https://gitlab.freedesktop.org/libinput/libinput/issues/65 Signed-off-by: Peter Hutterer [Test] Cherry-picked this commit to 1.10.4 and rebuild libinput, tested for thousands of times. touchpad taping OK. [Regression Potential] Low, upstream fix, tested OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1837962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power
after updated all the 5 packages below to new version, this issue seems fixed in my quick testing. nvidia-driver-390 (390.77-0ubuntu0.18.04.1) gdm3 (3.28.3-0ubuntu18.04.1) ubuntu-drivers-common (1:0.5.2.1) nvidia-prime (0.8.8.1) nvidia-settings (390.77-0ubuntu0.18.04.1) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Committed Status in nvidia-prime source package in Bionic: Fix Committed Status in nvidia-settings source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Bionic: Fix Committed Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic- proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390 /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia- ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1778011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
This issue should be fixed by the bug: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011 Please test the proposed packages or wait for the release channel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765363 Title: prime-select intel is not powering off the nvidia card Status in nvidia-prime package in Ubuntu: Confirmed Bug description: Right now, it seems that prime-select intel makes sure the nvidia driver is not loaded, as nvidia-settings reports. But my power consumption is > 20W. cat /proc/acpi/bbswitch reports the card is still on. If bbswitch and powertop are reliable, then the nvidia card is still powered. This is a thinkpad w520 in Optimus mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 19 19:56:21 2018 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2017-12-14 (125 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
