Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No display after upgrade to Kernel 5.19 #174

Closed
Taulim opened this issue Aug 24, 2022 · 5 comments
Closed

No display after upgrade to Kernel 5.19 #174

Taulim opened this issue Aug 24, 2022 · 5 comments

Comments

@Taulim
Copy link

Taulim commented Aug 24, 2022

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="22.04 LTS"
ID=pop
ID_LIKE="ubuntu debian"
PRETTY_NAME="Pop!_OS 22.04 LTS"
VERSION_ID="22.04"
HOME_URL="https://pop.system76.com"
SUPPORT_URL="https://support.system76.com"
BUG_REPORT_URL="https:/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=jammy
UBUNTU_CODENAME=jammy
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

nvidia-driver-515:
  Installed: 515.48.07-1pop0~1657640780~22.04~e863eed
  Candidate: 515.48.07-1pop0~1657640780~22.04~e863eed
  Version table:
     515.65.01-0ubuntu0.22.04.1 500
        500 http://apt.pop-os.org/ubuntu jammy-security/restricted amd64 Packages
        500 http://apt.pop-os.org/ubuntu jammy-updates/restricted amd64 Packages
 *** 515.48.07-1pop0~1657640780~22.04~e863eed 1001
       1001 http://apt.pop-os.org/release jammy/main amd64 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

After upgrading to Kernel 5.19 (from 5.18) the display goes black after Bios / Bootloader.

Old Kernel: 5.18.10-76051810.202207071639~1659403207~22.04~cb5f582
New Kernel: 5.19.0.76051900.202207312230~1660780566~22.04~9d60db1

If I select Pop_OS-oldkern.conf at boot time it works as expected.

When I try to run the new Kernel (default option) the following error is logged to /var/log/syslog:

Aug 24 11:31:20 pop-os systemd[1]: systemd-backlight@backlight:nvidia_0.service: start operation timed out. Terminating.
Aug 24 11:31:20 pop-os systemd[1]: systemd-backlight@backlight:nvidia_0.service: Main process exited, code=killed, status=15/TERM
Aug 24 11:31:20 pop-os systemd[1]: systemd-backlight@backlight:nvidia_0.service: Failed with result 'timeout'.
Aug 24 11:31:20 pop-os systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:nvidia_0.
Aug 24 11:31:32 pop-os kernel: [  111.354845] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Aug 24 11:31:32 pop-os kernel: [  111.356630] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Aug 24 11:31:44 pop-os kernel: [  123.578765] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Aug 24 11:31:44 pop-os kernel: [  123.579249] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer
Aug 24 11:31:56 pop-os kernel: [  135.802751] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT])
Aug 24 11:31:56 pop-os kernel: [  135.804390] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer

Steps to reproduce (if you know):

Expected behavior:

Other Notes:

My system is mostly 'clean' (with no crazy changes).

@leviport
Copy link
Member

Can you describe what hardware this is on? Also, does your install have full disk encryption?

@leviport leviport transferred this issue from pop-os/pop Aug 24, 2022
@Taulim
Copy link
Author

Taulim commented Aug 24, 2022

Also, does your install have full disk encryption? No

Can you describe what hardware this is on? Sure :)

image

@BramVerb
Copy link

BramVerb commented Sep 2, 2022

I have the same issue, also on NVIDIA graphics. I have been using the F12 + old kernel trick to be able to use my computer. I do however use disk encryption
image

Is there any updates on this issue?

@leviport
Copy link
Member

leviport commented Sep 2, 2022

If your install is encrypted, then you're probably experiencing pop-os/plymouth-theme#31 instead. I feel like this one is different since it does not involve encryption.

@Taulim
Copy link
Author

Taulim commented Nov 8, 2022

This issue seem to have been fixed with a new Kernel update.

@Taulim Taulim closed this as completed Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants