| View previous topic :: View next topic |
| Author |
Message |
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
 Posted: Sun Jun 26, 2022 7:28 pm Post subject: (fixed?) fresh install - Xorg is extremely slow and laggy |
 |
|
I just performed a fresh gentoo install after having borked my system. On this new install, for some reason, xorg is extremely slow and laggy when I connect my external monitors. I have the latest nvidia-drivers installed and followed the gentoo wiki for all of multi monitor setups, nvidia, bublebee and intel video. I don't know if I've overlooked something but still everything is extremely slow. If someone could point me in the right direction that would help. Here is the relevant information about my setup.
| lspci | grep VGA: |
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation TU104M [GeForce RTX 2070 SUPER Mobile / Max-Q] (rev a1)
|
| eix nvidia-drivers: |
[I] x11-drivers/nvidia-drivers
Available versions: 390.151(0/390) 470.129.06(0/470) 510.73.05-r1(0/510) ~515.48.07(0/515) [M]~515.49.05(0/vulkan) {+X dist-kernel (+)driver kernel-open persistenced +static-libs +tools wayland ABI_X86="32 64"}
Installed versions: 510.73.05-r1(0/510)(10:45:54 AM 06/26/2022)(X driver persistenced static-libs tools wayland -dist-kernel ABI_X86="64 -32")
Homepage: https://developer.nvidia.com/vulkan-driver
Description: NVIDIA Accelerated Graphics Driver
|
| /etc/portage/make.conf: |
VIDEO_CARDS="nvidia intel i915"
USE="xinerama gles gles2 X vulkan opengl vaapi vdpau opencl wayland"
|
| sudo emerge -pv nvidia-drivers: |
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] x11-drivers/nvidia-drivers-510.73.05-r1:0/510::gentoo USE="X driver persistenced static-libs tools wayland -dist-kernel" ABI_X86="(64) -32" 0 KiB
|
| sudo emerge -pv xorg-drivers: |
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] x11-base/xorg-drivers-21.1::gentoo INPUT_DEVICES="libinput synaptics -elographics -evdev -joystick -vmmouse -void -wacom" VIDEO_CARDS="i915 intel nvidia -amdgpu -ast -dummy -fbdev (-freedreno) (-geode) -glint -mga -nouveau -nv (-omap) -qxl -r128 -radeon -radeonsi -siliconmotion (-tegra) (-vc4) -vesa -via -virtualbox -vmware" 0 KiB |
linux-firmware is installed and loading properly
| sys-kernel/linux-firmware: |
[I] sys-kernel/linux-firmware
Available versions: 20210629^bstd 20210716^bstd 20210818^bstd 20210919^bstd 20211027^bstd 20211216^bstd 20220209^bstd 20220310^bstd 20220411^bstd 20220509^bstd 20220610^bstd **99999999*l^bstd {initramfs +redistributable savedconfig unknown-license}
Installed versions: 20220610^bst(01:34:15 PM 06/20/2022)(initramfs redistributable -savedconfig -unknown-license)
|
| dmesg | grep i915: |
[ 1.355177] i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 1.355180] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 1.370350] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
[ 1.370518] Loading firmware: i915/kbl_dmc_ver1_04.bin
[ 1.372198] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4)
[ 3.468501] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[ 3.501249] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops)
[ 4.039257] fbcon: i915drmfb (fb1) is primary device
[ 4.042379] i915 0000:00:02.0: [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS.
[ 6.419001] i915 0000:00:02.0: [drm] fb1: i915drmfb frame buffer device
[ 8.120292] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops) |
| lsmod: |
Module Size Used by
bbswitch 16384 0
nvidia_drm 61440 2
nvidia_modeset 1114112 3 nvidia_drm
intel_tcc_cooling 20480 0
nvidia 38580224 98 nvidia_modeset
i2c_nvidia_gpu 16384 0
intel_pch_thermal 16384 0
|
| cat /proc/mtrr: |
reg00: base=0x080000000 ( 2048MB), size= 2048MB, count=1: uncachable
reg01: base=0x040000000 ( 1024MB), size= 1024MB, count=1: uncachable
reg02: base=0x03e000000 ( 992MB), size= 32MB, count=1: uncachable
reg03: base=0x03d000000 ( 976MB), size= 16MB, count=1: uncachable
reg04: base=0x2000000000 (131072MB), size=131072MB, count=1: uncachable
reg05: base=0x1000000000 (65536MB), size=65536MB, count=1: uncachable
reg06: base=0x800000000 (32768MB), size=32768MB, count=1: uncachable
reg07: base=0x4000000000 (262144MB), size=262144MB, count=1: uncachable
|
glxinfo output
for some reason it says:
server glx vendor string: SGI
server glx version string: 1.4
shouldn't this be set to nvidia or intel?
direct rendering is true
my user belongs to both the video and plugdev groups
For some reason ARandR show that I have a display named "None-2-1" that I have disabled.
If anyone could give me some insights as to what might be wrong or if I forgot to do something please let me know.
Last edited by <3 on Thu Jul 07, 2022 12:31 am; edited 2 times in total |
|
| Back to top |
|
 |
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Mon Jun 27, 2022 10:55 pm Post subject: |
|
|
| I forgot to mention that I am running gentoo-sources-5.15.41 and nvidia-drivers-510.73.05-r1, Currently I have unmasked nvidia-drivers-515.48.07 but I am still having the same issue. I don't see anything in dmesg or /var/log/Xorg.0.log that stands out as a potential culprit. |
|
| Back to top |
|
|
jburns
Veteran
Joined: 18 Jan 2007
Posts: 1214
Location: Massachusetts USA
|
| Posted: Tue Jun 28, 2022 2:46 am Post subject: |
|
|
VIDEO_CARDS="nvidia intel i915" should not have i915. i915 causes an old driver to be built. Note you will still see a i915 driver listed in dmesg, this is the driver generated by the kernel.
In the glxinfo output the server glx vendor string: SGI is OK. It is the vendor of the software. You should see nvidia or intel later in the output.
You could also look at the Xorg log file it might help. |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Tue Jun 28, 2022 5:02 pm Post subject: |
|
|
the choice of video cards for intel are i915, i965, intel, iris. Some of the choices are exclusive, some can be set in parallel.
For most modern hardware you probably what iris, so i965 should ok as well. Which one to use depends on what driver architecture you want to use.
Unforutnately, the flag has in times different meaning for different packages (intel is an example)
Here is what my comments in make.conf say
| Quote: |
# VIDEO_CARDS="intel" - uses chip specific 2D acceleration driver, not installed if i965 is also set.
# VIDEO_CARDS="i965" - uses Glamor 2D acceleration driver in xorg-server, overwrites intel for xorg-drivers.
# However, for 3D 'intel' can be needed, since this is the only flag recognized by libdrm,
# and is required to be set to use, for example, vaapi. Thus we set both !
# VIDEO_CARDS="iris" is purely Mesa flag, new 3D driver for Gen8+ intel GPUs that uses Gallium3D
# VIDEO_CARDS="intel i965" for Mesa use 'classic' 3D driver
VIDEO_CARDS="i965 intel iris"
where at the end of the day iris driver is used, while intel flag is used for libdrm. But I can switch to i965 if I want, this is architecture is also built in and installed. |
|
|
| Back to top |
|
|
grknight
Retired Dev
Joined: 20 Feb 2015
Posts: 1653
|
| Posted: Tue Jun 28, 2022 8:46 pm Post subject: |
|
|
| dmpogo wrote: | the choice of video cards for intel are i915, i965, intel, iris. Some of the choices are exclusive, some can be set in parallel.
For most modern hardware you probably what iris, so i965 should ok as well. Which one to use depends on what driver architecture you want to use.
Unforutnately, the flag has in times different meaning for different packages (intel is an example)
Here is what my comments in make.conf say
| Quote: |
# VIDEO_CARDS="intel" - uses chip specific 2D acceleration driver, not installed if i965 is also set.
# VIDEO_CARDS="i965" - uses Glamor 2D acceleration driver in xorg-server, overwrites intel for xorg-drivers.
# However, for 3D 'intel' can be needed, since this is the only flag recognized by libdrm,
# and is required to be set to use, for example, vaapi. Thus we set both !
# VIDEO_CARDS="iris" is purely Mesa flag, new 3D driver for Gen8+ intel GPUs that uses Gallium3D
# VIDEO_CARDS="intel i965" for Mesa use 'classic' 3D driver
VIDEO_CARDS="i965 intel iris"
where at the end of the day iris driver is used, while intel flag is used for libdrm. But I can switch to i965 if I want, this is architecture is also built in and installed. |
|
As of a few months ago, this is now outdated with the latest mesa and xorg-drivers.
The above example can be simplified to just VIDEO_CARDS="intel" as i965 and iris have been retired (basically) as USE options. |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Tue Jun 28, 2022 10:06 pm Post subject: |
|
|
| I have updated my VIDEO_CARDS to "intel nvidia" then did an emerge -uDvN world and still I have the same issues. |
|
| Back to top |
|
|
dmpogo
Advocate
Joined: 02 Sep 2004
Posts: 3267
Location: Canada
|
| Posted: Tue Jun 28, 2022 10:09 pm Post subject: |
|
|
| grknight wrote: | | dmpogo wrote: | the choice of video cards for intel are i915, i965, intel, iris. Some of the choices are exclusive, some can be set in parallel.
For most modern hardware you probably what iris, so i965 should ok as well. Which one to use depends on what driver architecture you want to use.
Unforutnately, the flag has in times different meaning for different packages (intel is an example)
Here is what my comments in make.conf say
| Quote: |
# VIDEO_CARDS="intel" - uses chip specific 2D acceleration driver, not installed if i965 is also set.
# VIDEO_CARDS="i965" - uses Glamor 2D acceleration driver in xorg-server, overwrites intel for xorg-drivers.
# However, for 3D 'intel' can be needed, since this is the only flag recognized by libdrm,
# and is required to be set to use, for example, vaapi. Thus we set both !
# VIDEO_CARDS="iris" is purely Mesa flag, new 3D driver for Gen8+ intel GPUs that uses Gallium3D
# VIDEO_CARDS="intel i965" for Mesa use 'classic' 3D driver
VIDEO_CARDS="i965 intel iris"
where at the end of the day iris driver is used, while intel flag is used for libdrm. But I can switch to i965 if I want, this is architecture is also built in and installed. |
|
As of a few months ago, this is now outdated with the latest mesa and xorg-drivers.
The above example can be simplified to just VIDEO_CARDS="intel" as i965 and iris have been retired (basically) as USE options. |
I see ! and I see that classic versus gallium choice was retired for mesa as well, am I right ? |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Tue Jun 28, 2022 10:20 pm Post subject: |
|
|
| <3 wrote: | | I have updated my VIDEO_CARDS to "intel nvidia" then did an emerge -uDvN world and still I have the same issues. |
I should also mention that I copied the entire contents on etc/portage* from my previous working install to this new install. I've only made minor changes here or there to those files on this new install. Like changing "i915 and iris" to intel. Although that didn't seem to fix anything.
Last edited by <3 on Thu Jun 30, 2022 8:46 pm; edited 1 time in total |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Tue Jun 28, 2022 10:31 pm Post subject: |
|
|
it looks like the wgetpast posting of glxinfo has expired and the forum is not allowing me to post the output directly here. I just ran glxinfo again and for some reason it says "slow" a lot of times as if I needed a reminder.
Here is another wgetpaste of my glxinfo
https://dpaste.com/FGN5ZRUTN
Is there any significance in that? |
|
| Back to top |
|
|
<3
Veteran
Joined: 21 Oct 2004
Posts: 1081
|
| Posted: Thu Jul 07, 2022 12:30 am Post subject: |
|
|
I really don't know how or what I''ve done but some how 2d rendering seems to be working fine. It could have been me revering back to the 400 series nvidia-drivers then reverting back to 500 series or disabling some framebuffer support in the kernel (I don't remember which one I disabled and what I left enabled). I tried a million other things any it could have been any of those things. All I know is that it seems to work now.
/shrug |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
