Using Nvidia GPU with ubuntu-frame on ubuntu-core don't find any DRM #143
Comments
|
Hi @aurelien-semence, you're likely missing echo 'GRUB_CMDLINE_LINUX_DEFAULT="nvidia-drm.modeset=1"' \
| sudo tee /etc/default/grub.d/99-nvidia.cfg
sudo update-grubYou'll need to reboot after that. Please let us know if this helped! I've added a work item for ourselves to better document this. Thanks for raising it! I'll close this, let us know if that doesn't help and we'll reopen if we find there's more to it. |
Actually no, this would yield this error message:
I also just verified that 22.04 and newer don't need this kernel parameter. graphics-test-tools.drm-info and |
|
For your information, and |
Yeah so this says you don't have the necessary drivers working. (How) did you install the Nvidia drivers? What's your host OS? |
|
Thanks for your answers. I'm on For I will try adding |
|
@aurelien-semence the Ubuntu Core image you are using does not contain the Nvidia components needed. You need the Nvidia kernel modules and userspace drivers installed on the system hosting the snaps. I know this works on classic Ubuntu (Server or Desktop), but I will have to check if there's a suitable Ubuntu Core image. |
|
@AlanGriffiths @aurelien-semence On Ubuntu core, one needs |
|
Thanks a lot @xnox, However, I have only one screen displaying a gradient, the other is black. The HDMI screen displays the gradient but not the DisplayPort (on the LVDS connector). The I didn't really notice any errors in these logs. Do you have any idea? |
Mir does not currently support the Mir is only seeing one output connected to one card. (I'm surprised that there's a second, disconnected, output with the same name ['OUT-0'] on the card. That looks like a bug.) |
|
I don't know anything about mir and multiple displays. Maybe @Saviq can check above. |
|
@AlanGriffiths Could a naming problem cause an issue with the display on the first screen (DisplayPort)? FYI, after disconnecting HDMI, I still get black screen with following logs: |
|
@aurelien-semence the naming issue would affect configuring the outputs, but shouldn't stop something appearing on the displays. You can confirm this by testing with the version built with the naming fixed: I am not sure how/if DisplayPort would work on Ubuntu Core. On desktop it compiles and loads an evdi kernel module, but that would necessarily work differently on Core. If that device is there, then it would be reported by Mir as a separate "card". |
|
I just tested your modification and it didn't alter the display as you expected. Configuration: The DisplayPort works on Ubuntu Core as it displays the console when I disable |
Sorry, I've been reading DisplayPort as "DisplayLink" (I've been working on that elsewhere and failed to switch context). All I've said about it above is nonsense! The names "DisplayPort-1" and "HDMI-A-1" are what my modification provides, so that appears to be working. |
You likely need to reset that to clear the bad configuration: |
That makes sense to me 👍
Yes, this did the trick. Your modification does correct the naming issue, but it draws the DisplayPort's resolution (1024x768) onto the HDMI (1920x1080) surface, and the DisplayPort is still black. |
I don't have a suitable system with which to investigate properly but it may be a problem in Mir's eglstream configuration code. The naming issue suggest that multi-monitor on Nvidia hasn't been explored much. I'll ping @RAOF, who may have a suitable system, but he's in UTC+10 and won't respond immediately. |
|
I've managed to find a DVI cable so I can attach a second monitor to my nvidia card, and miral-shell (at least) is happy to drive both displays at their (different) native resolutions. Let me try ubuntu-frame with custom display configuraniton… |
|
Oh, no. Merging that PR has resulted in the associated ubuntu-frame release channel disappearing 🤦♀️ |
|
Ok, I can't reproduce what you see, but using any manual display layout I find that the Mir drives the DVI monitor at 920x1200(!!!!!) while incorrectly reporting the resolution as 1920x1200‽ |
You should a collaborator and able to download revision 5818 manually |
This is probably because you've got both outputs at the same location - their top-left pixel is at [0, 0] in both cases, so they overlap. You might have better luck with (Note that the HDMI monitor is now at [1024,0], that is: laid out to the right of DisplayPort-1) |
any annonymous user can download and install any revisions of global snaps these days. I.e. anyone can do |
|
Sorry, I don't have access to device as I'm in holiday. |
|
@RAOF, I've obtained revision 5818 as you suggested and used the parameters you provided. The
Do you have any suggestions on how to get this screen to display as well? Could this issue be related to the Thanks |
|
First some clarifications:
That revision is irrelevant now, there was a brief period after the naming fix was proposed and before the update was published on
The DisplayPort connection is being recognised and used:
No, that's a common thing on outputs (e.g. projectors) where physical size is meaningless.
No, I'm not sure what is logging that message, but it looks unrelated. Finally, I would try validating the hardware: Does the screen work with some other piece of kit? Does the wiring? Does a different screen work on the same port? |
|
I experience the same issue on the 22/edge channel. I tried using a different screen on the same port, but the result was the same. If I uninstall ubuntu-frame, the console is displayed on the screen (as is the BIOS before): I'm not sure what the significant difference would be between displaying text and an image on the screen. |
|
I have confirmed that the screen works with the same hardware when using Ubuntu Mate: |
|
Well, the fact that the text is removed from the display when Frame starts tells us it is doing something with it. There's no obvious reason why nothing shows |
|
Is there a way to get more verbose output that might help us understand what's going wrong? Perhaps through a flag or another method? |
There are a number of reporting options, but I doubt any of those will be more informative. (The most relevant sounding would be An option I think might give a clue is More generally, I find observation this somewhat suspicious:
As Frame always uses a "manual[sic] display layout" I think it might be related to the problems you see. I suspect (without convincing evidence - yet) that something is going wrong when applying the display configuration via the eglstream driver. |
|
Sorry if you've already tried it, but have you tried only the DisplayPort screen plugged in That could distinguish between is this an issue with multi-monitor, or an issue with that particular monitor/port. I'll try to carve out some time for chasing down the weird NVIDIA behaviour I saw with my DVI monitor, but I'll be on holiday next week so it might be a while, sorry. |
@RAOF, I performed a test yesterday and was unable to get any display on the DisplayPort screen. I assume the issue is specific to DisplayPort. @AlanGriffiths, could you please instruct me on how to set those flags? The `ubuntu-frame` logs are as follows:I just noticed this: But, I still have: The `graphics-test-tools.drm-info` logs are as follows: |
|
Hi @RAOF, @AlanGriffiths, Have you had a chance to look into the DisplayPort issue with Nvidia? I noticed there's a new version of ubuntu-core available, so I tried it. The `ubuntu-frame` logs are as follows: |
|
@aurelien-semence if you have no mention of What's your It may be easier if you started with Ubuntu Classic and confirmed that e.g. |
|
Sorry, I must have missed something when I reinstalled the system. The logs mention I cannot install a different OS on this system right now, but I'll attempt it on another one with DisplayPort and Nvidia card. The `ubuntu-frame` logs are as follows: |
|
How about For reference, it's about the userspace drivers: https://mir-server.io/docs/the-graphics-core22-snap-interface |
|
Yes, it is.
|
|
I installed ubuntu-frame on a second computer with ubuntu-core in the same way. This time, I disabled I got the following `ubuntu-frame` logs:I guess interesting part is: However, the hardware is a bit different and it uses 2 drivers: `sudo graphics-test-tools.drm-info`: |
|
@aurelien-semence you don't have a display connected here? Mir won't currently work without an active output. We're working on adding virtual outputs, though. EDIT: Sorry, only saw the Nvidia card at first. So this is the first error: But we're not talking Nvidia at all any more, both displays are connected to the Intel GPU here? Could you actually try with this version of Frame: It's built from canonical/mir#2962, which is a huge refactor of the graphics platforms. |
|
So, I tried your branch on my 2 devices and it starts working on one device. Device 1 (DP + HDMI on Nvidia card)On this device, it's not working. I notice few bugs:
with display.yaml:
trace:As you can see, it ignores display configuration to use: Device 2 (DP on Nvidia card + HDMI on Intel chipset)On this one, I made it working but I can't rotate screen. with `sudo ubuntu-frame --window-management-trace` trace: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have a computer with an Nvidia GT 1030 graphics card, and I'm trying to use
ubuntu-frameto display a simple website. Initially, the prompt is displayed without any issues. However, when I attempt to display something more complex usingubuntu-frame, I encounter a blank screen.I installed
nvidia-core22andubuntu-frame(channel=22/stable), connecting them usingsnap connect ubuntu-frame:graphics-core22 nvidia-core22:graphics-core22to utilize Nvidia drivers withubuntu-frame.The
ubuntu-framelogs are as follows:In version 20, EGL is not mentioned at all, but it is detected in version 22. Therefore, should it be working? Is there a plan to enable it?
My screen is connected via an LVDS connector. Could this be causing the issue?
Thanks.
The text was updated successfully, but these errors were encountered: