Oryx Pro 4B No display output on kernel 6.4.x about linux HOT 21 OPEN

This issue is about the Oryx Pro 4B, which does not have a 7900XTX. Please keep discussion about that hardware in pop-os/pop#3099

from linux.

A dmesg log when booting with nomodeset can be found here:
https://termbin.com/zer6

Although I'm not quite sure whether it helps in any way...

from linux.

Our oryp4 lab unit seems ok with the current kernel and NVIDIA driver. Which version of the NVIDIA driver is your machine running? You can check with nvidia-smi

from linux.

I'm currently on fedora and it seems the nvidia drivers aren't installed by default, I'm using nouveau, so I can not check nvidia-smi right now...

I had the same issue on pop os and other distro's, but I did not proceed to install anything. I used the nvidia pop os live usb without manually installing any drivers, simply doing a system upgrade makes it fail...

Does pop os come by default with nouveau drivers if you select the nvidia live distro?

I'll try with the nvidia drivers instead of nouveau...

from linux.

The NVIDIA version comes with NVIDIA drivers. The Intel/AMD version doesn't have NVIDIA, so it will default to Nouveau.

from linux.

But I installed the NVIDIA version :/ I'm so confused....

Also, I can not seem to install the nvidia drivers on fedora, in the system76 power management status it says that the graphics are enabled but I can not find it in lsmod or have nvidia-smi as a command

EDIT: Time to re-install pop os I guess....

from linux.

I just re-installed Pop OS with the NVIDIA drivers, I switched my graphics mode to Hybrid, and ran nvidia-smi. Which now returns the following:

NVIDIA-SMI 535.86.05 Driver Version: 535.86.05 CUDA Version: 12.2

However, after doing a system update, it installed the newest kernel and in the newest kernel, even when hybrid graphics is enabled, I get a black screen during boot.

This is a default newly installed pop os system

from linux.

Encountering the same issue with my desktop, but on an AMD GPU (7900 XTX). While the monitor is connected using DP, there's no output on the new kernel. Switching back to kernel 6.2.6 fixes the problem.

I tried moving config files and booting into the new kernel again, but it hasn't helped.

from linux.

exact same issue as previous commenter, 7900 xtx doesn't have any video output on 6.4.6, boots just fine on 6.2.6

from linux.

could these issues perhaps be related to one another?

in any case I think I'll try reinstalling the old kernel and deleting the new one. Is there a command I can use to not install a specific kernel version with updates?

from linux.

It's possible that they are related, but I'd like to keep them separate until we have more info supporting that possibility. It's easier to combine issues than to suss out several different bugs in one issue thread.

Can you try the steps I mentioned in pop-os/pop#3099 (comment) to see if your machine gives us any different clues?

I've noticed that the Oryx I have in the lab is just an oryp4, not an oryp4-b, so I'll have to dig through my library to see if I have a -b anywhere.

from linux.

I made a discovery on the 7900XT front: pop-os/pop#3099 (comment)

If that linux-firmware fixes everything for the oryp4-b as well, then this should be a very fast fix.

from linux.

That linux-firmware update was released, so I'd recommend removing that staging branch and just installing normal updates. I'm not sure if it fixes the oryp4-b since I haven't seen the same behavior on our oryp4, but hopefully it improves the situation.

from linux.

I just updated my system and rebooted, but the newest kernel is still having issues...

from linux.

It's possible that they are related, but I'd like to keep them separate until we have more info supporting that possibility. It's easier to combine issues than to suss out several different bugs in one issue thread.

Can you try the steps I mentioned in pop-os/pop#3099 (comment) to see if your machine gives us any different clues?

I've noticed that the Oryx I have in the lab is just an oryp4, not an oryp4-b, so I'll have to dig through my library to see if I have a -b anywhere.

This doesn't do anything because the screen instantly jumps to a no output display, I can not see the boot messages appear.

from linux.

Safe to assume the two issues aren't related then. I'll keep working on this. I'll need to find a way to recreate the problem in my lab.

from linux.

I also noticed that when I force shut off the computer after I booted the newer kernel (since I can't see anything), it starts up again with a message about the NVRAM and the CMOS battery. It's giving error messages about them, I ignore them and then it reboots several times, afterwards I'm able to select the older kernel again in order to boot.

Is there a way I can temporarely solve this isssue? I need this laptop this friday to work, whether it be the latest kernel or the older one doesn't matter for me, I just need a working system that boots normally without me having to manually select the kernel each time. I have to give a presentation, and I don't want this to fail.

from linux.

As I mentioned in pop-os/pop#3099 (comment), you can set the oldkern as the default in the systemd-boot menu.

from linux.

My apologies, I must've misread that part.

from linux.

I'm having the same issue with my laptop. At boot the internal Monitor stays blank. There is an output on the external monitor, but only when I get to the lightdm log-in screen, cryptsetup stays blank. The output is in a very strange resolution ,only half of the screen is displayed. The internal screen is set to a very strange resolution of: 15360 x 8640 with a refresh rate of 28.65 hz.
There seems to be an issue with the kernel 6.4.6 and the intel i915 driver, the EDID Data cannot be retrieved correctly and the screen output is not right. There has already been made a fix in Kernel 6.4.12. See: https://gitlab.freedesktop.org/drm/intel/-/issues/8789

from linux.

sorry for the late reply @clodsman ,

when I'm back from vacation hopefully the kernel will be available so I can do a check to see wether that fixes the issue. Otherwise, I'll wait patiently. Thank you for this report.

from linux.