Feedback: installation-guides/ubuntu/ubuntu-focal.html

[theno2soco]

I have been having issues trying to get No Man's Sky running using Vulkan on xubuntu 20.04 with an Intel® UHD Graphics 750 integrated GPU until I can afford a dedicated GPU.

I used this page:

https://dgpu-docs.intel.com/installation-guides/ubuntu/ubuntu-focal.html

After completing the installation I ran the configuring permissions:

makem@makem-pc:~$ stat -c "%G" /dev/dri/render stat: cannot stat '/dev/dri/render': No such file or directory makem@makem-pc:~$ groups ${USER} makem : makem adm cdrom sudo dip plugdev lpadmin lxd sambashare makem@makem-pc:~$

stat: cannot stat '/dev/dri/render*': No such file or directory - error

[ketrintel]

When /dev/dri/render* doesn't exist, it usually means the kernel driver hasn't loaded / initialized correctly. Can you look in your kernel log (dmesg) and look for any lines relating to i915?

You can also try running lsmod and see if i915 is loaded correctly.

What kernel are you using?

The Intel UHD graphics 750 might be new enough that you will need to install the kernel for 20.04.3, which from https://ubuntu.com/about/release-cycle looks like it will be the same kernel which is shipping with Ubuntu 21.04 (which is a 5.11 kernel)

[pepla]

Hi @theno2soco - have you resolve your installation issue? Can you please let us know if topic can be considered as closed or do you need any additional assistance from our side?

[theno2soco]

The game which is played via Steam opens without errors now but is unplayable because the mouse movement is very very slow.

I have not upgraded as suggested because I need expert advice upgrading in case I mess up a stable install because I don't wait until a 'proper' gfx card is reasonably available.

I have asked for advice in ubuntu forums.

[theno2soco]

I upgraded from 20.04 to 21.04 Whereas before the upgrade NMS failed due to vulcan errors, then after some weeks loaded correctly, it now hangs with a black screen and the only way out is a hard boot. So, it was capable of playing slowly but since the update fails again

[theno2soco]

I am now using the kernel 5.13.4-051304-generic in Ubuntu 21.04 but still get the black screen.

[theno2soco]

Today, reinstalled 20.04

[pepla]

Is it working slowly again with 20.04 but no black screen?

[theno2soco]

Today, reinstalled 20.04 and I am back to square one. Vulkan errors now which is where I was just before it suddenly started to work. Which I assume was due to some Linux regular update. Maybe it will some time in the future start working again but too slow to use. I need Intel iGPU drivers!

[theno2soco]

Today I got it working but it was using software rendering! Where are the Intel IGPU drivers?

[ketrintel]

You previously mentioned that there are no files matching /dev/dri/render*, which indicates the kernel driver (i915.ko) isn't loading, which would prevent the GPU from being usable.

Can you provide the output of:

cat << EOF | sh
cat /etc/os-release
uname -a
lspci -kk | grep VGA -A 3
lsmod | grep 915
EOF

Also check your kernel log and look for any errors relating to i915.

If we can determine the i915.ko is loading and initializing the card, then next we would look to investigate if the X server is initializing correctly.

[theno2soco]

I can confirm /dev/dri/render* does not exist. Someone said I could enable DRI3 in xorg.conf but that's beyond me :(

Maybe add below into: /usr/share/doc/xserver-xorg-video-intel/xorg.conf?

Section "Device" Identifier "Intel Graphics" Driver "intel" Option "DRI" "3" EndSection

There are errors in the kernel.log:

Your graphics device 4c8a is not properly supported by the driver in this Jul 25 18:32:20 makems-TUF kernel: [ 1.576192] kernel version. To force driver probe anyway, use i915.force_probe=4c8a

i915.force_probe=4c8a is already in grub

NMS plays now, the only fault being that it is very very slow, so much so that it would take over 30 minutes to get to game selection.

#14.txt i915.txt steam latest.txt

[ketrintel]

From your kernel log, we see that the 5.8 kernel may have partial support for 4c8a, but it is still wrapped behind an "early access" flag, which can be turned off with the force_probe module parameter:

Jul 26 10:35:36 makems-TUF kernel: [    1.561088] i915 0000:00:02.0: Your graphics device 4c8a is not properly supported by the driver in this
Jul 26 10:35:36 makems-TUF kernel: [    1.561088] kernel version. To force driver probe anyway, use i915.force_probe=4c8a

A few options:

1. See if there is a linux-oem kernel provided by Ubuntu that supports the GPU. I think you can use 'ubuntu-drivers list-oem' to search for that. If there isn't a kernel provided directly by Ubuntu, then...
2. You can try to add the "i915.force_probe=4c8a" parameter to your system's kernel command line (see below), or...
3. Use one of the "tip of tree" Linux kernels from Ubuntu's various kernel PPA channels (sounds like you tried this) and the latest Mesa packages.

To try option #1, you can edit your /etc/default/grub to add "i915.force_probe=4c8a" to the GRUB_CMDLINE_LINUX_DEFAULT entry, for example:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.force_probe=4c8a"

Then regenerate your grub boot loader:

sudo update-grub

and reboot and check the kernel log again.

If that doesn't work, you would need a newer hardware enabled stack. From your other comments, it sounds like you've tried both the default 21.04 kernel as well as the latest 5.13 kernel available from the Ubuntu PPAs. It might be a combination of needing both a newer kernel -and- a newer version of Mesa and/or Wayland. We don't currently provide those packages in our repositories, but there are PPAs that provide recent builds of Mesa.

In parallel to you trying that, we can reach out to folks on the Mesa and i915 teams to see if they have any information on the status of 4c8a support.

[theno2soco]

Thank you ketrintel,

I have edited my post prior to yours before seeing yours and it covers the grub addition. Yes, I tried 5.13 and it gave a black screen meaning a hard boot followed. Thanks for the options.

[ketrintel]

Can you provide the output from:

find /sys/module/i915/parameters/ -type f -print -exec sudo cat {} \;

The above will find all the files in /sys/module/i915/parameters, print the file name, then the contents of the file (which requires sudo access read the file, hence the sudo)

[theno2soco]

i915 params.txt

Disable display!

http://ppa.launchpad.net/oibaf/graphics-drivers/ubuntu is installed

[theno2soco]

Today I was presented with a software update which included mesa and dri drivers. I installed them and started NMS from steam. The game loaded without errors but slowly. It first presented the 'leaving page' as if I wanted to end the game. This was quickly overwritten by the choices page, single or multiplayer. The cursor appeared after a second or so but was almost unmovable. Eventually I was able to choose to return to desktop.

I have attached steam system output and a new i915 params output.

steam system 3.txt

i915 params 2.txt

[theno2soco]

I received an update of a further 16 packages today, installed them and the result was the same as previously. It took some 15 to 20 seconds for the cursor to actually move and complete the request to return to desktop.

steam system 4.txt

i915 params 3.txt

Edit: I see that 3 weeks ago it was reported that NMS performed better than in windows - no errors reported: Steam PlayProton 6.3-5 Distro:Manjaro Linux Kernel:5.10.49-1-MANJARO RAM:12 GB GPU Driver:4.6 Mesa 21.1.4 GPU:Intel Mesa Intel HD 630 (KBL GT2) CPU:Intel Core i7-7700HQ @ 2.80GHz

https://www.protondb.com/app/275850

[theno2soco]

Further updates for mesa and vulcan today. But game is still un-playable.

steam system 5.txt

[theno2soco]

Further updates for mesa and vulcan today. But game is still un-playable. It takes a number of seconds to move the mouse step by step to the place where you can choose to exit to the desktop and even then when you hold down the mouse button to exit you can watch the circle fill step by step until it executes.

steam system 6.txt

[theno2soco]

Further updates for mesa and vulcan today. However, no change, game is still un-playable.

steam system 7.txt

[theno2soco]

Further updates for mesa and vulcan today. However, no change, game is still un-playable. I notice there is always a lot of fan noise and this time I waited to see if it would die down before moving the mouse but it did not. Once I had the mouse in the right place it took 7 seconds for the 'ring' to fill up and I left to the desktop.

steam system 8.txt

[theno2soco]

Further updates for mesa and vulcan today. However, no change, game is still un-playable.

steam system 9.txt

[theno2soco]

Further updates for mesa and vulcan today. However, no apparent change.

steam system 10.txt

[theno2soco]

Further 17 (Usually 16?), updates for mesa and vulcan today. However, no change, game is still un-playable.

steam system 11.txt

[theno2soco]

Further updates for mesa and vulcan today. Following reboot, steam NMS hung saying "running". Exited Steam, rebooted and this time "running" stayed on for a shorter time and the game began. Still very very slow to fully load and not playable. I never actually play the game because if it takes a long time to close, as I found once when I did try to play, it effectively locks up the machine loading just the journey through the stars because it is so slow. I just move the mouse in short steps guiding it to the the Desktop option and quit.

I have a video showing an attempt to return to Desktop (Quit). For the whole time of the video I was holding the left mouse button down. The video is 50mb so too large to send, however it is 24.72 seconds long.

If it is possible I would appreciate some feedback informing me if I am being helpful or wasting my time for over 12 days.

steam system 12.txt

[pepla]

@theno2soco sorry to hear that you are still experiencing the problem. Can you please clarify for us if this is issue witch you are experiencing only with this one game (No Man's Sky), or other games are also affected?

Can you please confirm also if you are compiling mesa in debug or release mode?

The reason for those questions is one of the know issues within this particular game: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3135

[theno2soco]

@theno2soco sorry to hear that you are still experiencing the problem. Can you please clarify for us if this is issue witch you are experiencing only with this one game (No Man's Sky), or other games are also affected?

Can you please confirm also if you are compiling mesa in debug or release mode?

The reason for those questions is one of the know issues within this particular game: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3135

I don't play any other game.

I am not compiling anything.

The outcome stated in the url you point to does not relate to my problem.

I use Intel® UHD Graphics 750 in my Desktop PC

If you read the post from @ketrintel, 13 days ago and those preceding that post you will see the issue is different.

My issue is that the Intel GPU is not being used at all.

Every day for the past 12 days there have been updates to vulcan and msa so I assumed, wrongly it seems, that somebody was attempting to get this GPU to be used.

This assumption was backed up by this statement below posted by @ketrintel 14 days ago:

"In parallel to you trying that, we can reach out to folks on the Mesa and i915 teams to see if they have any information on the status of 4c8a support."

May I suggest you contact him rather than starting a new trail?

I would appreciate knowing who is providing the updated software and whether I should continue as I have been doing.

[theno2soco]

Further 21 updates for mesa and vulcan today. No change to my previous post.

steam system 13.txt

[theno2soco]

I have just noticed this in lspci -v: 00:02.0 VGA compatible controller: Intel Corporation Device 4c8a (rev 04) (prog-if 00 [VGA controller]) DeviceName: Onboard - Video Subsystem: ASUSTeK Computer Inc. Device 8694 Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at 6000000000 (64-bit, non-prefetchable) [size=16M] Memory at 4000000000 (64-bit, prefetchable) [size=256M] I/O ports at 4000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: <access denied>

[pepla]

Hi @theno2soco We get to know internally that your configuration is expected to be working. That being said, expectation for upcoming changes to make it working unfortunately is incorrect and you can stop verify daily updates for now.

The very item to determine next steps in debug will be for you to run those to commands and copy the output for our review: 'glxinfo ' and 'vulkaninfo '.

[theno2soco]

Thank you for keeping me in the loop.

Output requested:

glxinfo 1.txt

vulcaninfo 1.txt

[theno2soco]

The game Satisfactory does not run on this machine for same reasons.

[pepla]

Hi @theno2soco, First of all - totally apologies for big delays with our responses and inconvenience that those games are still not working for you. I would assume then you are sill seeing the same issue.

Unfortunately Im hearing from our driver team that glxinfo log which you provided is incomplete. From vulkanfio we can see that indeed you are not getting acceleration on vulkan. If you have this system still up and running can you please provide:

1. Full dmesg output
2. Full glxinfo and vulkaninfo outputs again.

[theno2soco]

As requested:

1. https://paste.ubuntu.com/p/N2nWSRkwy6/
2. glxinfo2.txt
3. vulkaninfo.txt22 I notice glxinfo size has changed today (24/9/21) so I post another file:
4. glxinfo3.txt .

[pepla]

Thanks, provided logs were helpful. We can confirm that kernel driver hasn't loaded correctly on you system. In order to speed up debug and resolution we are going to reporduce this problem and debug further.

[theno2soco]

I have changed my MSI monitor connection to the computer to DisplayPort to DisplayPort Cable and added a second ASUS monitor with HDMI to HDMI connection. The display settings only show one monitor and both monitors show my desktop in the default resolution 1024 x 768. None of the display settings can be changed as normal.

I am wondering if this is related to the ongoing problem?

[theno2soco]

I have changed my MSI monitor connection to the computer to Display Port to Display Port and added a second ASUS monitor with HDMI to HDMI connection. The display settings only show one monitor and both monitors show my desktop in the default resolution 1024 x 768. None of the display settings can be changed as normal. Remove the HDMI connection and resolution is back to normal with the Display Port connection only.

I am wondering if this is related to the ongoing problem?

This combination has since been checked and works fine in Windows - the problem is probably the kernel driver.

[FrancoMaxime]

From your kernel log, we see that the 5.8 kernel may have partial support for 4c8a, but it is still wrapped behind an "early access" flag, which can be turned off with the force_probe module parameter:

Jul 26 10:35:36 makems-TUF kernel: [    1.561088] i915 0000:00:02.0: Your graphics device 4c8a is not properly supported by the driver in this
Jul 26 10:35:36 makems-TUF kernel: [    1.561088] kernel version. To force driver probe anyway, use i915.force_probe=4c8a

A few options:

1. See if there is a linux-oem kernel provided by Ubuntu that supports the GPU. I think you can use 'ubuntu-drivers list-oem' to search for that. If there isn't a kernel provided directly by Ubuntu, then...

2. You can try to add the "i915.force_probe=4c8a" parameter to your system's kernel command line (see below), or...

3. Use one of the "tip of tree" Linux kernels from Ubuntu's various kernel PPA channels (sounds like you tried this) **and** the latest Mesa packages.

To try option #1, you can edit your /etc/default/grub to add "i915.force_probe=4c8a" to the GRUB_CMDLINE_LINUX_DEFAULT entry, for example:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.force_probe=4c8a"

Then regenerate your grub boot loader:

sudo update-grub

and reboot and check the kernel log again.

If that doesn't work, you would need a newer hardware enabled stack. From your other comments, it sounds like you've tried both the default 21.04 kernel as well as the latest 5.13 kernel available from the Ubuntu PPAs. It might be a combination of needing both a newer kernel -and- a newer version of Mesa and/or Wayland. We don't currently provide those packages in our repositories, but there are PPAs that provide recent builds of Mesa.

In parallel to you trying that, we can reach out to folks on the Mesa and i915 teams to see if they have any information on the status of 4c8a support.

That works for me, thanks! (with the good i915.force_probe address)