[Ubuntu-x-swat] [Bug 1870726] Re: [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver
** Changed in: xorg-server (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870726 Title: [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870726/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1870726] Re: [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver
Can anyone experiencing this bug please reproduce it and then collect a system log: journalctl -b0 > journal.txt I am thinking this might be a duplicate of some other bug, depending on whether the system log shows an assertion failure. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870726 Title: [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870726/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871754] [NEW] FFE: update vulkan to 1.2.135
Public bug reported: WIP ** Affects: vulkan-loader (Ubuntu) Importance: Undecided Status: New ** Affects: vulkan-tools (Ubuntu) Importance: Undecided Status: New ** Affects: vulkan-validationlayers (Ubuntu) Importance: Undecided Status: New ** Also affects: vulkan-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: vulkan-validationlayers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to vulkan-loader in Ubuntu. https://bugs.launchpad.net/bugs/1871754 Title: FFE: update vulkan to 1.2.135 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan-loader/+bug/1871754/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1870726] Re: [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver
** Description changed: + WORKAROUND: + + Select "Ubuntu on Wayland" from the login screen before logging in. + + --- + * Ubuntu Focal Fossa 20.04 (dev) * xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu1 * VirtualBox version : 5.2.34_Ubuntu r133883 (installed via apt) Expected : Show desktop after login Happened : On login screen, when password is entered correctly, it gets into a loop and shows the login screen again. But, it takes me to desktop properly if Ubuntu on Wayland is selected. Steps to reproduce : 1) Install Ubuntu 20 on an Oracle VirtualBox 2) Start a live session 3) Click the install button (Entire disk, Apply updates automatic) 4) After reboot, try to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 10:28:22 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=d609fc71-9cba-4875-8bc1-795cb584a629 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870726 Title: [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1870726/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871752] Re: Xorg fails to start at login
*** This bug is a duplicate of bug 1870726 *** https://bugs.launchpad.net/bugs/1870726 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1870726, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1870726 [vboxvideo] Xorg crashes on startup using modeset with vboxvideo kernel driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871752 Title: Xorg fails to start at login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871752/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871752] [NEW] Xorg fails to start at login
Public bug reported: Installed on VirtualBox using qCOW. Installation worked flawlessly. Rebooted and attempted to login. Input password and clicked the button, but was returned to the login screen. Changed to Ubuntu on Wayland and was able to login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 21:03:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=79fa19d3-5e39-401b-854c-2e7e7f26fc41 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871752 Title: Xorg fails to start at login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871752/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1859782] Re: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display
yes, it's been on the queue since Sunday -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1859782 Title: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1859782/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871573] Re: HDMI port does not work on Ubuntu 20.04
Thanks for the bug report. It appears the whole HDMI port is missing, and we're not just failing to detect a monitor. So that would be a kernel bug I think. ** Summary changed: - HDMI port does not work on Ubuntu 20.04 + [Lenovo ThinkPad P1 Gen 2] HDMI port does not work on Ubuntu 20.04 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [Lenovo ThinkPad P1 Gen 2] HDMI port does not work on Ubuntu 20.04 + [Lenovo ThinkPad P1 Gen 2][i915] HDMI port does not work on Ubuntu 20.04 ** Summary changed: - [Lenovo ThinkPad P1 Gen 2][i915] HDMI port does not work on Ubuntu 20.04 + [Lenovo ThinkPad P1 Gen 2][i915 Coffee Lake] HDMI port can't be found -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871573 Title: [Lenovo ThinkPad P1 Gen 2][i915 Coffee Lake] HDMI port can't be found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871573/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871394] Re: modeset: Loss of VGA signal (ast2500) on login
Oh, actually this might be a mutter bug or even a kernel bug related to this: https://gitlab.gnome.org/GNOME/mutter/-/issues/182 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #182 https://gitlab.gnome.org/GNOME/mutter/-/issues/182 ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871394 Title: modeset: Loss of VGA signal (ast2500) on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871394/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462)
Great! ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462)
Yes, Daniel. The picture is normal at all available rates above 60Hz. 120Hz and 144Hz. Awesome. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871662] Re: FFE: new upstream bugfix release 1.20.8
Oh nice. Looks like bug 1859782 will get fixed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871662 Title: FFE: new upstream bugfix release 1.20.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871662/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1859782] Re: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display
Sounds like the fix for this is coming in Xorg 1.20.8?... ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1859782 Title: Xwayland apps like glxgears or Chromium report 58 FPS on a 60Hz display To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1859782/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462)
Is the "pixel pattern error" gone? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Kai-Heng-Feng, Thank you very much for your reply. Previous kernel was removed. I tried to install your new kernel and got same issue. While install new kernel, I found a small error, not sure it would be effected. Below are the details: sudo dpkg -i *.deb [sudo] password for srlungaci: Selecting previously unselected package linux-5.6-headers-5.6.0-8. (Reading database ... 179408 files and directories currently installed.) Preparing to unpack linux-5.6-headers-5.6.0-8_5.6.0-8.8_all.deb ... Unpacking linux-5.6-headers-5.6.0-8 (5.6.0-8.8) ... Selecting previously unselected package linux-buildinfo-5.6.0-8-generic. Preparing to unpack linux-buildinfo-5.6.0-8-generic_5.6.0-8.8_amd64.deb ... Unpacking linux-buildinfo-5.6.0-8-generic (5.6.0-8.8) ... Selecting previously unselected package linux-headers-5.6.0-8-generic. Preparing to unpack linux-headers-5.6.0-8-generic_5.6.0-8.8_amd64.deb ... Unpacking linux-headers-5.6.0-8-generic (5.6.0-8.8) ... Selecting previously unselected package linux-image-unsigned-5.6.0-8-generic. Preparing to unpack linux-image-unsigned-5.6.0-8-generic_5.6.0-8.8_amd64.deb ... Unpacking linux-image-unsigned-5.6.0-8-generic (5.6.0-8.8) ... Selecting previously unselected package linux-modules-5.6.0-8-generic. Preparing to unpack linux-modules-5.6.0-8-generic_5.6.0-8.8_amd64.deb ... Unpacking linux-modules-5.6.0-8-generic (5.6.0-8.8) ... Selecting previously unselected package linux-modules-extra-5.6.0-8-generic. Preparing to unpack linux-modules-extra-5.6.0-8-generic_5.6.0-8.8_amd64.deb ... Unpacking linux-modules-extra-5.6.0-8-generic (5.6.0-8.8) ... Setting up linux-5.6-headers-5.6.0-8 (5.6.0-8.8) ... Setting up linux-buildinfo-5.6.0-8-generic (5.6.0-8.8) ... Setting up linux-headers-5.6.0-8-generic (5.6.0-8.8) ... Setting up linux-modules-5.6.0-8-generic (5.6.0-8.8) ... Setting up linux-image-unsigned-5.6.0-8-generic (5.6.0-8.8) ... I: /boot/vmlinuz.old is now a symlink to vmlinuz-5.4.0-23-generic I: /boot/initrd.img.old is now a symlink to initrd.img-5.4.0-23-generic I: /boot/vmlinuz is now a symlink to vmlinuz-5.6.0-8-generic I: /boot/initrd.img is now a symlink to initrd.img-5.6.0-8-generic Setting up linux-modules-extra-5.6.0-8-generic (5.6.0-8.8) ... Processing triggers for linux-image-unsigned-5.6.0-8-generic (5.6.0-8.8) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.6.0-8-generic modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.6.0-8-generic Found initrd image: /boot/initrd.img-5.6.0-8-generic Found linux image: /boot/vmlinuz-5.4.0-23-generic Found initrd image: /boot/initrd.img-5.4.0-23-generic Found linux image: /boot/vmlinuz-5.4.0-21-generic Found initrd image: /boot/initrd.img-5.4.0-21-generic Adding boot menu entry for UEFI Firmware Settings done Please see the log file. Thank you and have a great day. ** Attachment added: "prevboot2.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5350032/+files/prevboot2.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871394] Re: modeset: Loss of VGA signal (ast2500) on login
Ubuntu 18.04 using Wayland: The monitor connected to the AST2500 VGA has no signal during and after login. "xrandr -q" shows both devices are active. They are listed as XWAYLAND0 and XWAYLAND1. Ubuntu desktop's "Display configuration" window shows both monitors are active. I can move the monitors relative to each other and change the monitor assigned as "primary". When I change these configurations the only thing that appears to be amiss is the missing AST2500 VGA video signal. Ubuntu 20.04 using xorg: The monitor connected to the AST2500 VGA has no signal during or after login. "xrandr -q" shows the DisplayPort and HDMI that are part of the i915 (this machine does not provide the HDMI part of the i915); it does not show the AST2500 device. lspci and lshw show the AST2500 is present. Ubuntu desktop's "Display configuration" window only has options for one monitor. Ubuntu 20.04 using Wayland: I seem to recall switching Ubuntu 20.04 from xorg to wayland using a button in the lower right corner of the login menu to present a menu that permitted me to toggle between xorg and wayland. The button only appears while I am entering the password at the login screen. Today that same button presents a different menu. The options are "Remmina kiosk" and "Ubuntu". I do not know how to toggle to Wayland without the button and I don't recall well enough to recount what I saw in Wayland earlier this week. I will look into Ubuntu 19 tomorrow. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871394 Title: modeset: Loss of VGA signal (ast2500) on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1871394/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871698] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1745799 *** https://bugs.launchpad.net/bugs/1745799 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1745799, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1871698/+attachment/5349867/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1871698/+attachment/5349870/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1871698/+attachment/5349883/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1871698/+attachment/5349885/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1871698/+attachment/5349886/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1871698/+attachment/5349887/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1871698/+attachment/5349888/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1745799 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871698 Title: Xwayland crashed with SIGABRT in OsAbort() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871698/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871345] Re: FFE: Update Intel OpenCL stack for Tiger Lake, build with llvm-10
** Also affects: intel-gmmlib (Ubuntu) Importance: Undecided Status: New ** Description changed: This is a request for a pre-ack to allow updating the Intel OpenCL stack to versions that work with the default llvm release in focal, which is 10. Updated components: + intel-gmmlib19.4.1 -> 20.1.1 spirv-llvm-translator 9.0.0 -> 10.0.0 intel-opencl-clang 9.0.0 -> 10.0.0 intel-graphics-compiler 1.0.3151 -> 1.0.3627 intel-compute-runtime 20.02.15268 -> 20.13.16352 (~weekly releases) - the first three are now in Debian. + the first four are now in Debian. The updated stack is required for Tiger Lake support. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-graphics-compiler in Ubuntu. https://bugs.launchpad.net/bugs/1871345 Title: FFE: Update Intel OpenCL stack for Tiger Lake, build with llvm-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/1871345/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871662] Re: FFE: new upstream bugfix release 1.20.8
ok, I thought this was missing since it's been on the queue for a couple of days now, but probably just unreviewed then -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871662 Title: FFE: new upstream bugfix release 1.20.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871662/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871345] Re: FFE: Update Intel OpenCL stack, build with llvm-10
The previous comment was about a build-issue with llvm-10, which got resolved. So that's not a blocker anymore. ** Description changed: This is a request for a pre-ack to allow updating the Intel OpenCL stack to versions that work with the default llvm release in focal, which is 10. - - The problem right now is that a bug in llvm-10 prevents builds against - it in some packages like intel-opencl-clang, which in turn is a prereq - for the rest. Updated components: spirv-llvm-translator 9.0.0 -> 10.0.0 intel-opencl-clang 9.0.0 -> 10.0.0 intel-graphics-compiler 1.0.3151 -> 1.0.3627 intel-compute-runtime 20.02.15268 -> 20.13.16352 (~weekly releases) - We could update i-g-c and i-c-r that build with llvm-9 now, and rebuild - them later once i-o-c is updated. s-l-t update is already available on - Debian. + the first three are now in Debian. + + The updated stack is required for Tiger Lake support. ** Summary changed: - FFE: Update Intel OpenCL stack, build with llvm-10 + FFE: Update Intel OpenCL stack for Tiger Lake, build with llvm-10 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-graphics-compiler in Ubuntu. https://bugs.launchpad.net/bugs/1871345 Title: FFE: Update Intel OpenCL stack for Tiger Lake, build with llvm-10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/1871345/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871662] Re: FFE: new upstream bugfix release 1.20.8
Thanks for being diligent, but *feature* freeze exceptions are not needed for bugfix releases. ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871662 Title: FFE: new upstream bugfix release 1.20.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871662/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871662] [NEW] FFE: new upstream bugfix release 1.20.8
Public bug reported: The queue has a new bugfix release. The git changelog has these: f84ad082557f9cd xserver 1.20.8 883727986930931 Fix old-style definition warning for xf86OSInputThreadInit() 0c012f968b4e02a Add xf86OSInputThreadInit to stub os-support as well b25948597507808 xwayland: Delete all frame_callback_list nodes in xwl_unrealize_window a033571644d277d xwayland/glamor-gbm: Handle DRM_FORMAT_MOD_INVALID gracefully 3c48bd50ad33f2a dix: Check for NULL spriteInfo in GetPairedDevice 1610ef1d6b5ba99 Fix building with `-fno-common` 2a185dd22ddb5b0 xwayland: Use frame callbacks for Present vblank events 99a6d6b15e0757a xwayland: Use single frame callback for Present flips and normal updates 915cc107767624b xwayland: Add xwl_window_create_frame_callback helper 94dad4f05133171 xwayland: clear pixmaps after creation in rootless mode 0238359bced17f9 xwayland: Call glamor_block_handler from xwl_screen_post_damage a93bce6bfc6c610 xwayland: Split up xwl_screen_post_damage into two phases p 1ba5e528d52ed9d modesetting: Disable atomic support by default d44bbb471096165 glamor: Fix a compiler warning since the recent OOM fixes. d2a6c8708ca4f27 glamor: Fallback to system memory for RW PBO buffer allocation ca034c2f2cfff8e glamor: Propagate glamor_prepare_access failures in copy helpers a7b165d994d7413 glamor: Error out on out-of-memory when allocating PBO for FBO access 428b5ce4da99a43 glamor: Propagate FBO allocation failure for picture to texture upload 948afd768398955 modesetting: remove unnecessary error message, fix zaphod leases p 1c3e51dabadbf65 xfree86/modes: Bail from xf86RotateRedisplay if pScreen->root is NULL af2fd88b1019f63 os: Ignore dying client in ResetCurrentRequest e5293f1c5d7b20d Revert "dri2: Don't make reference to noClientException" d845ceae53bb425 Restrict 1x1 pixmap filling optimization to GXcopy p c2ef88c4d3a551f modesetting: Explicitly #include "mi.h" p ad7364d8d7f936b configure: Define GLAMOR_HAS_EGL_QUERY_DRIVER when available of which we already had the four commits marked with a 'p'. ** Affects: xorg-server (Ubuntu) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: Invalid ** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1871662 Title: FFE: new upstream bugfix release 1.20.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1871662/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1852166] Re: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462)
It seems that I am able to set the refresh rate to 120Hz and 144Hz. Feel free to close this. xserver-xorg-video-nouveau 1:1.0.16-1 Linux shahar-desktop 5.3.0-46-generic #38-Ubuntu SMP Fri Mar 27 17:37:05 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1852166 Title: [nouveau] Pixel pattern error at 120Hz or 144Hz, but 60Hz works (monitor MSI Optix G24C / model 1462) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852166/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
P.B. I tried to verify your observation. Without luck. First I generated a Windows-10 bootable USB drive and managed to install and run the "AMD Driver Auto-detect tool". On Windows it was successful to set the computer into standby and resume. Then I've done a warm-start of the computer an booted into Linux. Now I was able to set the machine into standby and back to resume successfully. The next experiment was to do a power down reset and try the standby/resume with Linux again. It stopped with a blank black screen with backlight switched on. After a warm start (Alt-SysReq-B) all subsequent standby/resume cycles worked perfectly. My guess is that after a warm start some GPU register settings remain untouched causing success of the resume. Or in other words, the initial setup of the GPU is missing something which is done with the first (unsuccessful) standby/resume after power up. My ubuntu kernel version is meanwhile 5.3.0-46-generic. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871573] Re: HDMI port does not work on Ubuntu 20.04
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871573 Title: HDMI port does not work on Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871573/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871573] [NEW] HDMI port does not work on Ubuntu 20.04
You have been subscribed to a public bug: Hi, I know that you have certified version 18.04 and that 20.04 is not out yet. So this is more heads up. I am testing Ubuntu 20.04 on new Lenovo P1 2nd gen. Currently HDMI does not work. How do I know that problem is not in cable or monitor ? If I boot to windows, HDMI port works as expected. Thank you, Igor RACIC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 10:00:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed nvidia, 440.64, 5.4.0-21-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f] InstallationDate: Installed on 2020-04-01 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: LENOVO 20QTCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 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.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- HDMI port does not work on Ubuntu 20.04 https://bugs.launchpad.net/bugs/1871573 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
it'll be fixed in 20.0.5 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1855402] Re: [TGL] mesa support
20.0.4 is in focal ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1855402 Title: [TGL] mesa support To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855402/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871303] Re: [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software rendering cache surface: out of memory
Being stuck in low resolution would be a different problem. But if I was to guess I would say that is due to the kernel options you have: recovery nomodeset Those both need to be removed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1871303 Title: [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software rendering cache surface: out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1871303/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
Re: [Ubuntu-x-swat] [Bug 1871303] Re: [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software rendering cache surface: out of memory
Thanks, I tried the nvidia driver 435. seems that Umbuntu rejects and and reverted to the nouveau driver. But the resolution is very low and the rendering quality is bad. In the ubuntu settings/displays/resolution it does not give me a high resolution option. My eyes are just about burned out getting this far, the rendering is bad, like a really bad focus, blurry. Ken On Wed, Apr 8, 2020 at 9:06 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > It looks like a bug in an old driver, possibly relating only to old > video cards. So a fix is unlikely to arrive in that particular driver > version. > > You might want to try uninstalling the Nvidia driver version 390 and > then either: > > * Do nothing -- the built-in open source driver should work; or > > * sudo apt install nvidia-driver-435 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871303 > > Title: > [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software > rendering cache surface: out of memory > > Status in nvidia-graphics-drivers-390 package in Ubuntu: > New > > Bug description: > Boot hangs up on initiating graphics. I can only finish the boot if I > use the recovery mode. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 > Uname: Linux 4.15.0-91-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .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.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 > 07:21:36 PST 2019 >GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > Date: Tue Apr 7 09:02:40 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > DkmsStatus: >nvidia, 390.116, 4.15.0-88-generic, x86_64: installed >nvidia, 390.116, 4.15.0-91-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 710] [1043:8572] > InstallationDate: Installed on 2017-07-14 (997 days ago) > InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215.2) > MachineType: ASUS All Series > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic > root=UUID=671dec46-62d2-4163-a941-c528578feb4d ro recovery nomodeset > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/14/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1103 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: H81M-K > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev X.0x > dmi.chassis.asset.tag: Asset-1234567890 > dmi.chassis.type: 3 > dmi.chassis.vendor: Chassis Manufacture > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr1103:bd05/14/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: > dmi.product.family: ASUS MB > dmi.product.name: All Series > dmi.product.version: System Version > dmi.sys.vendor: ASUS > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Tue Apr 7 07:18:59 2020 > xserver.configfile: default > xserver.devices: >inputPower Button KEYBOARD, id 6 >inputPower Button KEYBOARD, id 7 >inputSIGMACHIP Usb Mouse MOUSE, id 8 >inputEee PC WMI hotkeys KEYBOARD, id 9 >inputAT Translated Set 2 keyboard KEYBOARD, id 10 > xserver.errors: open /dev/fb0: No such file or directory > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > > xserver.version: 2:1.19.6-1ubuntu4.3 > > To manage notifications about
[Ubuntu-x-swat] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
This is a very interesting observation! In one of my previous posts I described the fact that after the first unsuccessful resume and a following soft-reset with Alt+SysReq+B all subsequent resumes will succeed. My guess was that there was something changed in the GPU's hardware registers before or after the first resume. It cannot be any software influence since the software started again. After a cold reset the game starts again. My assumption was that the GPU's hardware register change was volatile. Maybe the "AMD Driver Auto-detect tool" stores this one time change non- volatile in any kind of configuration storage element within the GPU. Then it behaves the same like you described. Currently I do not know of any dual use of drivers between Linux and Windows, but to have a built- in non-volatile configuration storage supporting the GPU is very likely. Unfortunately I do not have a dual boot machine. I'm running only Linux. So I'll try to create a USB-stick based Windows 10 to verify your experience. It will take some time. Again, very interesting ... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
I've just tested latest mesa 20.0.4-1ubuntu1 for focal fossa Bug is STILL present -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 ** This bug is no longer a duplicate of bug 1870758 [nvidia] Display scaling results in a blank screen (power save state) ** This bug has been marked a duplicate of bug 1869750 [nvidia] Screens turn off when setting display scaling to 200% -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1870779 Title: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871458] Re: No display signal if NVIDIA driver and display scaling is active
*** This bug is a duplicate of bug 1869750 *** https://bugs.launchpad.net/bugs/1869750 ** This bug is no longer a duplicate of bug 1870758 [nvidia] Display scaling results in a blank screen (power save state) ** This bug has been marked a duplicate of bug 1869750 [nvidia] Screens turn off when setting display scaling to 200% -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1871458 Title: No display signal if NVIDIA driver and display scaling is active To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871458/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1871303] Re: [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software rendering cache surface: out of memory
It looks like a bug in an old driver, possibly relating only to old video cards. So a fix is unlikely to arrive in that particular driver version. You might want to try uninstalling the Nvidia driver version 390 and then either: * Do nothing -- the built-in open source driver should work; or * sudo apt install nvidia-driver-435 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1871303 Title: [nvidia] Xorg crashes in (EE) NVIDIA(0): Failed to allocate software rendering cache surface: out of memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1871303/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
