Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
[Hardware] The enemy you know: nvidia vs AMD
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
[Hardware] The enemy you know: nvidia vs AMD
I've been an nvidia guy forever. Have learned to tolerate their proprietary drivers and truth be told, for a long timer prefered to manually install the nvidia sourced drivers instead of using the versioned drivers provided with the distributions...this since I often end up genning my own highly customized kernel that looks nothing like what was in the distro. I do a bit of number crunching so using the GPU as a general purpose processor is important to me as well. Lately though I've been noticing the "planned obsolescence" path of nvidia hardware and came to the realization that I've got older 16X cards that are useless to me based on the way nvidia develops and releases their drivers.
I'm ready to investigate the Radeon side of things but am very concerned that the "we are open source friendly" face is pure marketing hype designed to confuse folks who dont really understand what it means to be open source. A LOT of tech these days pretends/lies, and you don't find out that they lock down key components without investing significant effort to understand their software chain. The example is: AMD "says" their drivers are in the mainline linux kernel, yet they still have and amdgpu-pro package on their website. The drivers are either open source or they are not...Then, the packages on their website are NOT actual code. They are to open up your package trust path to their servers to download additional unspecified BLOBS. To their credit, at least nvidia gives you a complete BLOB archive when you download their drivers.
For me to invest ANY additional effort into testing/comparing the AMD/Radeon cards I need to know that the required drivers and tools are 100% open source and that their source is available, and not hidden or obscured, or reliant upon something that is not open source, exempting a HAL firmware BLOB that I would expect be specific for each model card that AMD sell, but that BLOB should be freely distributable and its API must be documented to the OS community. If I can buy an RX580 card, download the Debian distro X11 drivers/firmware, mesa, and openCL and use the card for accelerated openGL, as well as parallel GPU programming then it's all good. If I find that feature components are missing and that I must download unspecified BLOB components from AMD then I'm not interested in going any further.
Anyone have a handle on this who wants to chime in?
I'm ready to investigate the Radeon side of things but am very concerned that the "we are open source friendly" face is pure marketing hype designed to confuse folks who dont really understand what it means to be open source. A LOT of tech these days pretends/lies, and you don't find out that they lock down key components without investing significant effort to understand their software chain. The example is: AMD "says" their drivers are in the mainline linux kernel, yet they still have and amdgpu-pro package on their website. The drivers are either open source or they are not...Then, the packages on their website are NOT actual code. They are to open up your package trust path to their servers to download additional unspecified BLOBS. To their credit, at least nvidia gives you a complete BLOB archive when you download their drivers.
For me to invest ANY additional effort into testing/comparing the AMD/Radeon cards I need to know that the required drivers and tools are 100% open source and that their source is available, and not hidden or obscured, or reliant upon something that is not open source, exempting a HAL firmware BLOB that I would expect be specific for each model card that AMD sell, but that BLOB should be freely distributable and its API must be documented to the OS community. If I can buy an RX580 card, download the Debian distro X11 drivers/firmware, mesa, and openCL and use the card for accelerated openGL, as well as parallel GPU programming then it's all good. If I find that feature components are missing and that I must download unspecified BLOB components from AMD then I'm not interested in going any further.
Anyone have a handle on this who wants to chime in?
-
- Posts: 300
- Joined: 2015-06-07 14:38
- Has thanked: 11 times
- Been thanked: 32 times
Re: [Hardware] The enemy you know: nvidia vs AMD
I can't speak to their actual open stance. However I know with my RX570 I need the firmware-linux-nonfree package. I don't know how you feel about that.
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: [Hardware] The enemy you know: nvidia vs AMD
The AMDGPU-PRO drivers are completely separate from the open source amdgpu kernel driver. AMD themselves only recommend the PRO drivers for their PRO cards and recommend that everybody else use the open source version. The amdgpu kernel driver is completely open.kent_dorfman766 wrote: ↑2023-05-19 04:02The example is: AMD "says" their drivers are in the mainline linux kernel, yet they still have and amdgpu-pro package on their website. The drivers are either open source or they are not...
However, the situation with all three major graphics chip suppliers is now the same: the core driver is open source (even for NVIDIA) but the proprietary code needed to make the hardware function correctly is supplied in the firmware. This is a general problem for people who prefer "open" hardware — almost every component on the motherboard needs firmware and it is almost always proprietary. Debian users only notice the hardware that requires the non-free firmware to be loaded by the operating system but the rest of the hardware had blobs implanted at the factory.
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
I tried to explain that I expect a HAL firmware BLOB, but it needs to be available and distributable thru the debian distro channels, not something that you have to retrieve from AMD.I need the firmware-linux-nonfree package. I don't know how you feel about that.
No one makes hardware anymore that doesn't have am FPGA/PL firmware image associated with it. It allows the vendor to make changes and fixes without spinning new hardware boards.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
Totally get that, and as mentioned previously, I expect there to be a firmware blob because I myself do FPGA/PL programming and understand how/why of it, but do we know for certain that there are not hidden gotchas in AMD support of open source. Have they fully opened the X11 and GPU processing APIs for the cards they currently sell? If I attempt to do GPU generic programming for RX580 using openCL, am I going to find that there is a proprietary component that could dissappear and render my hardware useless if I revive it ten years from now to run a legacy simulation? Which is what I'm running into with nvidia legacy GPUs and CUDA programming currently.This is a general problem for people who prefer "open" hardware — almost every component on the motherboard needs firmware and it is almost always proprietary. Debian users only notice the hardware that requires the non-free firmware to be loaded by the operating system but the rest of the hardware had blobs implanted at the factory.
-
- Posts: 300
- Joined: 2015-06-07 14:38
- Has thanked: 11 times
- Been thanked: 32 times
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: [Hardware] The enemy you know: nvidia vs AMD
"X11" (by which I presume you mean the DRM stack) is fully open for AMD hardware and for GPGPU AMD have moved to ROCm:kent_dorfman766 wrote: ↑2023-05-19 21:43Have they fully opened the X11 and GPU processing APIs for the cards they currently sell?
https://gpuopen.com/learn/amd-lab-notes ... on-readme/
Which is also open source
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
If it is open then where is the source? All I see on their website it marketing hype and executable archives. that's my point. It aint open if they are not providing, or are obscuring, access to the sourcecode for the SDKs.and for GPGPU AMD have moved to ROCm:
https://gpuopen.com/learn/amd-lab-notes ... on-readme/
Which is also open source
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: [Hardware] The enemy you know: nvidia vs AMD
https://github.com/ROCmSoftwarePlatform?
But I don't actually use GPGPU so apologies if I'm wrong about this.
But I don't actually use GPGPU so apologies if I'm wrong about this.
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: [Hardware] The enemy you know: nvidia vs AMD
That's the DRM stack, as used by Mesa.
Speaking of which, Mesa under AMD does have shortfalls in respect of the more advanced Vulkan shaders because most development has been driven by Valve (Steam) and so favours WINE (Proton) applications. Vulkan should degrade gracefully though.
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
ok, so with comment from @Random_Troll I located a public git repo for ROCm, but time will tell if it contains all the necessary components to build the GPU programming SDKs and tools from scratch. Doesn't appear to be any top-level README that explains the build process, but it's not to AMDs advantage to provide such if they want you to use their pre-built components.
The test is "can I purchase an RX580 and under linux write/execute a heavy math program that takes advantage of the stream processing cores, and do so without relying upon ANY closed or obfuscated software components." Will try to do something that is as portable as possible between CUDA and ROCm to compare timing results, if I can get it to work at all.
Will see. On my way to WorstBuy now to get a GPU since I can't find one locally on craigslist.
The test is "can I purchase an RX580 and under linux write/execute a heavy math program that takes advantage of the stream processing cores, and do so without relying upon ANY closed or obfuscated software components." Will try to do something that is as portable as possible between CUDA and ROCm to compare timing results, if I can get it to work at all.
Will see. On my way to WorstBuy now to get a GPU since I can't find one locally on craigslist.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
Am not particularly interested in vulkan at the moment, and prefer to do any graphics coding in openGL, but am hoping that mesa/DRM doesn't prove to be a bottleneck. My only current frame of reference is nvidia closed-source openGL, which is good high performance in my apps.Speaking of which, Mesa under AMD does have shortfalls in respect of the more advanced Vulkan shaders because most development has been driven by Valve (Steam) and so favours WINE (Proton) applications. Vulkan should degrade gracefully though.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
update--
based on information in this thread and gathering bits and pieces off the net, I attempted to install and benchmark/compare a Radeon RX580 against my existing nvidia GTX1060 with pretty dismal results.
The marketing hype says the two GPUs are on an even par with each others capabilities so I was expecting similar numbers. I ran the glxgears program where I disabled (unthrottled) the vblank sync, first under the nvidia closed source drivers and got around 15000fps. I then did the same test on the Radeon and only got 5000fps. Thats 1/3 of the throughput!
Both glxinfo outputs show that acceleration is enabled, but nvidia replaces a lot of the mesa libraries with their own special sauce. The radeon test seems to attempt to make use of mesa more heavily, but in my experience mesa has always had pretty poor performance for openGL.
So, barring anyone being able to offer advice on what I'm overlooking, I have to form the opinion that a 2/3 performance hit is a very steep penalty to accept as a consequency of happily drinking the open-source coolaid.
Can anyone offer any mitigating thoughts or direction as to what I may be doing wrong in my benchmarking? and yes, I know glxgears is NOT a true comprehensive benchmark, but that big a difference in frame rates screams loudly.
Oh, a parting thought that may be an indicator...the glxifo visual output indicates "slow" for many of the radeon driven visuals. Not sunch caveats for the nvidia. Is this an indicator that the drivers and not truly being accelerated by using the GPU under amdgpu?
based on information in this thread and gathering bits and pieces off the net, I attempted to install and benchmark/compare a Radeon RX580 against my existing nvidia GTX1060 with pretty dismal results.
The marketing hype says the two GPUs are on an even par with each others capabilities so I was expecting similar numbers. I ran the glxgears program where I disabled (unthrottled) the vblank sync, first under the nvidia closed source drivers and got around 15000fps. I then did the same test on the Radeon and only got 5000fps. Thats 1/3 of the throughput!
Both glxinfo outputs show that acceleration is enabled, but nvidia replaces a lot of the mesa libraries with their own special sauce. The radeon test seems to attempt to make use of mesa more heavily, but in my experience mesa has always had pretty poor performance for openGL.
So, barring anyone being able to offer advice on what I'm overlooking, I have to form the opinion that a 2/3 performance hit is a very steep penalty to accept as a consequency of happily drinking the open-source coolaid.
Can anyone offer any mitigating thoughts or direction as to what I may be doing wrong in my benchmarking? and yes, I know glxgears is NOT a true comprehensive benchmark, but that big a difference in frame rates screams loudly.
Oh, a parting thought that may be an indicator...the glxifo visual output indicates "slow" for many of the radeon driven visuals. Not sunch caveats for the nvidia. Is this an indicator that the drivers and not truly being accelerated by using the GPU under amdgpu?
-
- Posts: 444
- Joined: 2023-02-07 13:35
- Been thanked: 105 times
Re: [Hardware] The enemy you know: nvidia vs AMD
See https://wiki.cchtml.com/index.php/Glxge ... _Benchmarkkent_dorfman766 wrote: ↑2023-05-20 22:21Can anyone offer any mitigating thoughts or direction as to what I may be doing wrong in my benchmarking?
For more reasonable benchmarks check https://wiki.archlinux.org/title/Benchmarking#Graphics.
Use radeontop to confirm full hardware utilisation.
Jeder nach seinen Fähigkeiten, jedem nach seinen Bedürfnissen.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
@Random_Troll
The feedback is appreciated. I downloaded and built glmark2 and executed on both machines. Performance score closely reflects what I was getting with glxgears: nvideo=14700 and radeon=5000
Most test catagories consistently rated nearly three times the throughput on nvidia over radeon. Not sure that radeontop is that useful, but I did an iteration and noticed that the utilization of most categories topped out at 35ish percent, with an oocasional 50% spike. The clocks maxed out early and stayed near 100%.
radeon xorg log file
The feedback is appreciated. I downloaded and built glmark2 and executed on both machines. Performance score closely reflects what I was getting with glxgears: nvideo=14700 and radeon=5000
Most test catagories consistently rated nearly three times the throughput on nvidia over radeon. Not sure that radeontop is that useful, but I did an iteration and noticed that the utilization of most categories topped out at 35ish percent, with an oocasional 50% spike. The clocks maxed out early and stayed near 100%.
Code: Select all
=======================================================
glmark2 2023.01
=======================================================
OpenGL Information
GL_VENDOR: AMD
GL_RENDERER: Radeon RX 580 Series (POLARIS10, DRM 3.40.0, 5.10.0-17-amd64, LLVM 11.0.1)
GL_VERSION: 4.6 (Compatibility Profile) Mesa 20.3.5
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 2887 FrameTime: 0.346 ms
[build] use-vbo=true: FPS: 5832 FrameTime: 0.171 ms
[texture] texture-filter=nearest: FPS: 5791 FrameTime: 0.173 ms
[texture] texture-filter=linear: FPS: 5738 FrameTime: 0.174 ms
[texture] texture-filter=mipmap: FPS: 5689 FrameTime: 0.176 ms
[shading] shading=gouraud: FPS: 5670 FrameTime: 0.176 ms
[shading] shading=blinn-phong-inf: FPS: 6766 FrameTime: 0.148 ms
[shading] shading=phong: FPS: 7095 FrameTime: 0.141 ms
[shading] shading=cel: FPS: 7045 FrameTime: 0.142 ms
[bump] bump-render=high-poly: FPS: 7049 FrameTime: 0.142 ms
[bump] bump-render=normals: FPS: 5650 FrameTime: 0.177 ms
[bump] bump-render=height: FPS: 5792 FrameTime: 0.173 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 7083 FrameTime: 0.141 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 7001 FrameTime: 0.143 ms
[pulsar] light=false:quads=5:texture=false: FPS: 5624 FrameTime: 0.178 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 3546 FrameTime: 0.282 ms
[desktop] effect=shadow:windows=4: FPS: 2628 FrameTime: 0.381 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 200 FrameTime: 5.003 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 210 FrameTime: 4.776 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 390 FrameTime: 2.567 ms
[ideas] speed=duration: FPS: 1715 FrameTime: 0.583 ms
[jellyfish] <default>: FPS: 4919 FrameTime: 0.203 ms
[terrain] <default>: FPS: 1834 FrameTime: 0.545 ms
[shadow] <default>: FPS: 3889 FrameTime: 0.257 ms
[refract] <default>: FPS: 3304 FrameTime: 0.303 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 6694 FrameTime: 0.149 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 6305 FrameTime: 0.159 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 6491 FrameTime: 0.154 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 6101 FrameTime: 0.164 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 6237 FrameTime: 0.160 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 5838 FrameTime: 0.171 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 6215 FrameTime: 0.161 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 6444 FrameTime: 0.155 ms
=======================================================
glmark2 Score: 4958
=======================================================
Code: Select all
=======================================================
glmark2 2023.01
=======================================================
OpenGL Information
GL_VENDOR: NVIDIA Corporation
GL_RENDERER: NVIDIA GeForce GTX 1060 3GB/PCIe/SSE2
GL_VERSION: 4.6.0 NVIDIA 470.182.03
Surface Config: buf=32 r=8 g=8 b=8 a=8 depth=24 stencil=0 samples=0
Surface Size: 800x600 windowed
=======================================================
[build] use-vbo=false: FPS: 6523 FrameTime: 0.153 ms
[build] use-vbo=true: FPS: 23637 FrameTime: 0.042 ms
[texture] texture-filter=nearest: FPS: 21412 FrameTime: 0.047 ms
[texture] texture-filter=linear: FPS: 21375 FrameTime: 0.047 ms
[texture] texture-filter=mipmap: FPS: 21733 FrameTime: 0.046 ms
[shading] shading=gouraud: FPS: 20101 FrameTime: 0.050 ms
[shading] shading=blinn-phong-inf: FPS: 19872 FrameTime: 0.050 ms
[shading] shading=phong: FPS: 19424 FrameTime: 0.051 ms
[shading] shading=cel: FPS: 19563 FrameTime: 0.051 ms
[bump] bump-render=high-poly: FPS: 14476 FrameTime: 0.069 ms
[bump] bump-render=normals: FPS: 24106 FrameTime: 0.041 ms
[bump] bump-render=height: FPS: 23478 FrameTime: 0.043 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 17750 FrameTime: 0.056 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 11026 FrameTime: 0.091 ms
[pulsar] light=false:quads=5:texture=false: FPS: 15071 FrameTime: 0.066 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 2266 FrameTime: 0.441 ms
[desktop] effect=shadow:windows=4: FPS: 3115 FrameTime: 0.321 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 208 FrameTime: 4.827 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 214 FrameTime: 4.692 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 361 FrameTime: 2.774 ms
[ideas] speed=duration: FPS: 3356 FrameTime: 0.298 ms
[jellyfish] <default>: FPS: 12059 FrameTime: 0.083 ms
[terrain] <default>: FPS: 1214 FrameTime: 0.824 ms
[shadow] <default>: FPS: 6920 FrameTime: 0.145 ms
[refract] <default>: FPS: 2918 FrameTime: 0.343 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 22445 FrameTime: 0.045 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 21638 FrameTime: 0.046 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 22247 FrameTime: 0.045 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 21762 FrameTime: 0.046 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 21289 FrameTime: 0.047 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 21458 FrameTime: 0.047 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 21317 FrameTime: 0.047 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 20695 FrameTime: 0.048 ms
=======================================================
glmark2 Score: 14696
=======================================================
Code: Select all
[ 148.097]
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[ 148.106] Build Operating System: linux Debian
[ 148.109] Current Operating System: Linux greybox 5.10.0-17-amd64 #1 SMP Debian 5.10.136-1 (2022-08-13) x86_64
[ 148.109] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-17-amd64 root=UUID=16dc07f0-7a25-4f93-a7f5-2ae79e6a1c06 ro 1
[ 148.115] Build Date: 23 March 2023 10:25:56AM
[ 148.118] xorg-server 2:1.20.11-1+deb11u6 (https://www.debian.org/support)
[ 148.121] Current version of pixman: 0.40.0
[ 148.127] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 148.127] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 148.139] (==) Log file: "/home/rprowel/.local/share/xorg/Xorg.0.log", Time: Sat May 20 17:28:52 2023
[ 148.143] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 148.143] (==) No Layout section. Using the first Screen section.
[ 148.143] (==) No screen section available. Using defaults.
[ 148.143] (**) |-->Screen "Default Screen Section" (0)
[ 148.143] (**) | |-->Monitor "<default monitor>"
[ 148.144] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 148.144] (==) Automatically adding devices
[ 148.144] (==) Automatically enabling devices
[ 148.145] (==) Automatically adding GPU devices
[ 148.145] (==) Max clients allowed: 256, resource mask: 0x1fffff
[ 148.147] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[ 148.147] Entry deleted from font path.
[ 148.151] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 148.151] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 148.151] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 148.151] (II) Loader magic: 0x55e367bf0e40
[ 148.151] (II) Module ABI versions:
[ 148.151] X.Org ANSI C Emulation: 0.4
[ 148.151] X.Org Video Driver: 24.1
[ 148.151] X.Org XInput driver : 24.1
[ 148.151] X.Org Server Extension : 10.0
[ 148.152] (++) using VT number 1
[ 148.154] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[ 148.155] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 148.156] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0
[ 148.163] (--) PCI:*(8@0:0:0) 1002:67df:1682:c580 rev 231, Mem @ 0xc0000000/268435456, 0xd0000000/2097152, 0xd0200000/262144, I/O @ 0x00004000/256,
BIOS @ 0x????????/131072
[ 148.164] (II) LoadModule: "glx"
[ 148.164] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 148.176] (II) Module glx: vendor="X.Org Foundation"
[ 148.176] compiled for 1.20.11, module version = 1.0.0
[ 148.176] ABI class: X.Org Server Extension, version 10.0
[ 148.176] (II) Applying OutputClass "AMDgpu" to /dev/dri/card0
[ 148.176] loading driver: amdgpu
[ 148.176] (==) Matched amdgpu as autoconfigured driver 0
[ 148.176] (==) Matched ati as autoconfigured driver 1
[ 148.176] (==) Matched modesetting as autoconfigured driver 2
[ 148.176] (==) Matched fbdev as autoconfigured driver 3
[ 148.176] (==) Matched vesa as autoconfigured driver 4
[ 148.176] (==) Assigned the driver to the xf86ConfigLayout
[ 148.176] (II) LoadModule: "amdgpu"
[ 148.177] (II) Loading /usr/lib/xorg/modules/drivers/amdgpu_drv.so
[ 148.183] (II) Module amdgpu: vendor="X.Org Foundation"
[ 148.183] compiled for 1.20.9, module version = 19.1.0
[ 148.183] Module class: X.Org Video Driver
[ 148.183] ABI class: X.Org Video Driver, version 24.1
[ 148.183] (II) LoadModule: "ati"
[ 148.183] (WW) Warning, couldn't open module ati
[ 148.183] (EE) Failed to load module "ati" (module does not exist, 0)
[ 148.183] (II) LoadModule: "modesetting"
[ 148.183] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 148.185] (II) Module modesetting: vendor="X.Org Foundation"
[ 148.185] compiled for 1.20.11, module version = 1.20.11
[ 148.185] Module class: X.Org Video Driver
[ 148.185] ABI class: X.Org Video Driver, version 24.1
[ 148.185] (II) LoadModule: "fbdev"
[ 148.185] (WW) Warning, couldn't open module fbdev
[ 148.185] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 148.185] (II) LoadModule: "vesa"
[ 148.185] (WW) Warning, couldn't open module vesa
[ 148.185] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 148.185] (II) AMDGPU: Driver for AMD Radeon:
All GPUs supported by the amdgpu kernel driver
[ 148.185] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 148.186] (WW) Falling back to old probe method for modesetting
[ 148.187] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 148.187] (II) AMDGPU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 148.187] (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32
[ 148.187] (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps)
[ 148.187] (==) AMDGPU(0): Default visual is TrueColor
[ 148.187] (==) AMDGPU(0): RGB weight 888
[ 148.187] (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC)
[ 148.187] (--) AMDGPU(0): Chipset: "Radeon RX 580 Series" (ChipID = 0x67df)
[ 148.187] (II) Loading sub module "fb"
[ 148.187] (II) LoadModule: "fb"
[ 148.187] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 148.188] (II) Module fb: vendor="X.Org Foundation"
[ 148.188] compiled for 1.20.11, module version = 1.0.0
[ 148.188] ABI class: X.Org ANSI C Emulation, version 0.4
[ 148.188] (II) Loading sub module "dri2"
[ 148.188] (II) LoadModule: "dri2"
[ 148.188] (II) Module "dri2" already built-in
[ 148.523] (II) Loading sub module "glamoregl"
[ 148.523] (II) LoadModule: "glamoregl"
[ 148.523] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 148.535] (II) Module glamoregl: vendor="X.Org Foundation"
[ 148.535] compiled for 1.20.11, module version = 1.0.1
[ 148.535] ABI class: X.Org ANSI C Emulation, version 0.4
[ 148.577] (II) AMDGPU(0): glamor X acceleration enabled on Radeon RX 580 Series (POLARIS10, DRM 3.40.0, 5.10.0-17-amd64, LLVM 11.0.1)
[ 148.577] (II) AMDGPU(0): glamor detected, initialising EGL layer.
[ 148.577] (==) AMDGPU(0): TearFree property default: auto
[ 148.577] (==) AMDGPU(0): VariableRefresh: disabled
[ 148.577] (II) AMDGPU(0): KMS Pageflipping: enabled
[ 148.577] (II) AMDGPU(0): Output DisplayPort-0 has no monitor section
[ 148.577] (II) AMDGPU(0): Output DisplayPort-1 has no monitor section
[ 148.577] (II) AMDGPU(0): Output DisplayPort-2 has no monitor section
[ 148.578] (II) AMDGPU(0): Output HDMI-A-0 has no monitor section
[ 148.578] (II) AMDGPU(0): Output DVI-D-0 has no monitor section
[ 148.590] (II) AMDGPU(0): EDID for output DisplayPort-0
[ 148.590] (II) AMDGPU(0): EDID for output DisplayPort-1
[ 148.590] (II) AMDGPU(0): EDID for output DisplayPort-2
[ 148.590] (II) AMDGPU(0): EDID for output HDMI-A-0
[ 148.591] (II) AMDGPU(0): Manufacturer: HWP Model: 288f Serial#: 16843009
[ 148.591] (II) AMDGPU(0): Year: 2010 Week: 30
[ 148.591] (II) AMDGPU(0): EDID Version: 1.3
[ 148.591] (II) AMDGPU(0): Digital Display Input
[ 148.591] (II) AMDGPU(0): Max Image Size [cm]: horiz.: 51 vert.: 29
[ 148.591] (II) AMDGPU(0): Gamma: 2.20
[ 148.591] (II) AMDGPU(0): DPMS capabilities: Off
[ 148.591] (II) AMDGPU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 148.591] (II) AMDGPU(0): Default color space is primary color space
[ 148.591] (II) AMDGPU(0): First detailed timing is preferred mode
[ 148.591] (II) AMDGPU(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
[ 148.591] (II) AMDGPU(0): blueX: 0.150 blueY: 0.060 whiteX: 0.313 whiteY: 0.329
[ 148.591] (II) AMDGPU(0): Supported established timings:
[ 148.591] (II) AMDGPU(0): 720x400@70Hz
[ 148.591] (II) AMDGPU(0): 640x480@60Hz
[ 148.591] (II) AMDGPU(0): 800x600@60Hz
[ 148.591] (II) AMDGPU(0): 1024x768@60Hz
[ 148.591] (II) AMDGPU(0): Manufacturer's mask: 0
[ 148.591] (II) AMDGPU(0): Supported standard timings:
[ 148.591] (II) AMDGPU(0): #0: hsize: 1280 vsize 720 refresh: 60 vid: 49281
[ 148.591] (II) AMDGPU(0): #1: hsize: 1280 vsize 960 refresh: 60 vid: 16513
[ 148.591] (II) AMDGPU(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
[ 148.591] (II) AMDGPU(0): #3: hsize: 1440 vsize 900 refresh: 60 vid: 149
[ 148.591] (II) AMDGPU(0): #4: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
[ 148.591] (II) AMDGPU(0): #5: hsize: 1680 vsize 1050 refresh: 60 vid: 179
[ 148.591] (II) AMDGPU(0): #6: hsize: 1920 vsize 1080 refresh: 60 vid: 49361
[ 148.591] (II) AMDGPU(0): Supported detailed timing:
[ 148.591] (II) AMDGPU(0): clock: 148.5 MHz Image Size: 510 x 287 mm
[ 148.591] (II) AMDGPU(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
[ 148.591] (II) AMDGPU(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
[ 148.591] (II) AMDGPU(0): Ranges: V min: 50 V max: 76 Hz, H min: 24 H max: 94 kHz, PixClock max 175 MHz
[ 148.591] (II) AMDGPU(0): Monitor name: HP 2310
[ 148.591] (II) AMDGPU(0): Serial No: 3CQ030NGW8
[ 148.591] (II) AMDGPU(0): Supported detailed timing:
[ 148.591] (II) AMDGPU(0): clock: 27.0 MHz Image Size: 510 x 287 mm
[ 148.591] (II) AMDGPU(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
[ 148.591] (II) AMDGPU(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
[ 148.591] (II) AMDGPU(0): Supported detailed timing:
[ 148.591] (II) AMDGPU(0): clock: 27.0 MHz Image Size: 510 x 287 mm
[ 148.591] (II) AMDGPU(0): h_active: 720 h_sync: 732 h_sync_end 796 h_blank_end 864 h_border: 0
[ 148.591] (II) AMDGPU(0): v_active: 576 v_sync: 581 v_sync_end 586 v_blanking: 625 v_border: 0
[ 148.591] (II) AMDGPU(0): Supported detailed timing:
[ 148.591] (II) AMDGPU(0): clock: 74.2 MHz Image Size: 510 x 287 mm
[ 148.591] (II) AMDGPU(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
[ 148.591] (II) AMDGPU(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 148.591] (II) AMDGPU(0): Supported detailed timing:
[ 148.591] (II) AMDGPU(0): clock: 74.2 MHz Image Size: 510 x 287 mm
[ 148.591] (II) AMDGPU(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
[ 148.591] (II) AMDGPU(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
[ 148.591] (II) AMDGPU(0): Number of EDID sections to follow: 1
[ 148.591] (II) AMDGPU(0): EDID (in hex):
[ 148.591] (II) AMDGPU(0): 00ffffffffffff0022f08f2801010101
[ 148.591] (II) AMDGPU(0): 1e14010380331d782eee95a3544c9926
[ 148.591] (II) AMDGPU(0): 0f5054a1080081c0814081809500a940
[ 148.591] (II) AMDGPU(0): b300d1c00101023a801871382d40582c
[ 148.591] (II) AMDGPU(0): 4500fe1f1100001e000000fd00324c18
[ 148.592] (II) AMDGPU(0): 5e11000a202020202020000000fc0048
[ 148.592] (II) AMDGPU(0): 5020323331300a2020202020000000ff
[ 148.592] (II) AMDGPU(0): 003343513033304e4757380a2020012e
[ 148.592] (II) AMDGPU(0): 020323f1230907074984020301111210
[ 148.592] (II) AMDGPU(0): 1f13830100006c030c001000b82dc001
[ 148.592] (II) AMDGPU(0): 0101018c0ad08a20e02d10103e9600fe
[ 148.592] (II) AMDGPU(0): 1f110000188c0ad090204031200c4055
[ 148.592] (II) AMDGPU(0): 00fe1f11000018011d007251d01e206e
[ 148.592] (II) AMDGPU(0): 285500fe1f1100001e011d00bc52d01e
[ 148.592] (II) AMDGPU(0): 20b8285540fe1f1100001e0000000000
[ 148.592] (II) AMDGPU(0): 000000000000000000000000000000b7
[ 148.592] (--) AMDGPU(0): HDMI max TMDS frequency 225000KHz
[ 148.592] (II) AMDGPU(0): Printing probed modes for output HDMI-A-0
[ 148.592] (II) AMDGPU(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[ 148.592] (II) AMDGPU(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1920x1080"x59.9 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.4 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1280x800"x60.0 148.50 1280 2008 2052 2200 800 1084 1089 1125 +hsync +vsync (67.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1280x720"x59.9 74.18 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "720x480"x60.0 27.03 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
[ 148.592] (II) AMDGPU(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
[ 148.592] (II) AMDGPU(0): EDID for output DVI-D-0
[ 148.592] (II) AMDGPU(0): Output DisplayPort-0 disconnected
[ 148.592] (II) AMDGPU(0): Output DisplayPort-1 disconnected
[ 148.592] (II) AMDGPU(0): Output DisplayPort-2 disconnected
[ 148.592] (II) AMDGPU(0): Output HDMI-A-0 connected
[ 148.592] (II) AMDGPU(0): Output DVI-D-0 disconnected
[ 148.592] (II) AMDGPU(0): Using exact sizes for initial modes
[ 148.592] (II) AMDGPU(0): Output HDMI-A-0 using initial mode 1920x1080 +0+0
[ 148.592] (II) AMDGPU(0): mem size init: gart size :1ffc3a000 vram size: s:1feee6000 visible:fbe7000
[ 148.592] (==) AMDGPU(0): DPI set to (96, 96)
[ 148.592] (==) AMDGPU(0): Using gamma correction (1.0, 1.0, 1.0)
[ 148.592] (II) Loading sub module "ramdac"
[ 148.592] (II) LoadModule: "ramdac"
[ 148.593] (II) Module "ramdac" already built-in
[ 148.593] (II) UnloadModule: "modesetting"
[ 148.593] (II) Unloading modesetting
[ 148.594] (II) AMDGPU(0): [DRI2] Setup complete
[ 148.594] (II) AMDGPU(0): [DRI2] DRI driver: radeonsi
[ 148.594] (II) AMDGPU(0): [DRI2] VDPAU driver: radeonsi
[ 148.595] (II) AMDGPU(0): Front buffer pitch: 8192 bytes
[ 148.595] (II) AMDGPU(0): SYNC extension fences enabled
[ 148.596] (II) AMDGPU(0): Present extension enabled
[ 148.596] (==) AMDGPU(0): DRI3 enabled
[ 148.596] (==) AMDGPU(0): Backing store enabled
[ 148.596] (II) AMDGPU(0): Direct rendering enabled
[ 148.670] (II) AMDGPU(0): Use GLAMOR acceleration.
[ 148.670] (II) AMDGPU(0): Acceleration enabled
[ 148.670] (==) AMDGPU(0): DPMS enabled
[ 148.670] (==) AMDGPU(0): Silken mouse enabled
[ 148.671] (II) AMDGPU(0): Set up textured video (glamor)
[ 148.691] (II) Initializing extension Generic Event Extension
[ 148.691] (II) Initializing extension SHAPE
[ 148.691] (II) Initializing extension MIT-SHM
[ 148.691] (II) Initializing extension XInputExtension
[ 148.693] (II) Initializing extension XTEST
[ 148.693] (II) Initializing extension BIG-REQUESTS
[ 148.694] (II) Initializing extension SYNC
[ 148.694] (II) Initializing extension XKEYBOARD
[ 148.694] (II) Initializing extension XC-MISC
[ 148.694] (II) Initializing extension SECURITY
[ 148.695] (II) Initializing extension XFIXES
[ 148.695] (II) Initializing extension RENDER
[ 148.695] (II) Initializing extension RANDR
[ 148.696] (II) Initializing extension COMPOSITE
[ 148.696] (II) Initializing extension DAMAGE
[ 148.696] (II) Initializing extension MIT-SCREEN-SAVER
[ 148.696] (II) Initializing extension DOUBLE-BUFFER
[ 148.696] (II) Initializing extension RECORD
[ 148.697] (II) Initializing extension DPMS
[ 148.697] (II) Initializing extension Present
[ 148.697] (II) Initializing extension DRI3
[ 148.697] (II) Initializing extension X-Resource
[ 148.698] (II) Initializing extension XVideo
[ 148.698] (II) Initializing extension XVideo-MotionCompensation
[ 148.698] (II) Initializing extension SELinux
[ 148.698] (II) SELinux: Disabled on system
[ 148.698] (II) Initializing extension GLX
[ 148.707] (II) AIGLX: Loaded and initialized radeonsi
[ 148.707] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 148.707] (II) Initializing extension XFree86-VidModeExtension
[ 148.707] (II) Initializing extension XFree86-DGA
[ 148.708] (II) Initializing extension XFree86-DRI
[ 148.708] (II) Initializing extension DRI2
[ 148.713] (II) AMDGPU(0): Setting screen physical size to 508 x 285
[ 148.915] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[ 148.915] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 148.915] (II) LoadModule: "libinput"
[ 148.915] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
[ 148.922] (II) Module libinput: vendor="X.Org Foundation"
[ 148.922] compiled for 1.20.8, module version = 0.30.0
[ 148.922] Module class: X.Org XInput Driver
[ 148.922] ABI class: X.Org XInput driver, version 24.1
[ 148.922] (II) Using input driver 'libinput' for 'Power Button'
[ 148.924] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 27 paused 0
[ 148.924] (**) Power Button: always reports core events
[ 148.924] (**) Option "Device" "/dev/input/event2"
[ 148.924] (**) Option "_source" "server/udev"
[ 148.931] (II) event2 - Power Button: is tagged by udev as: Keyboard
[ 148.932] (II) event2 - Power Button: device is a keyboard
[ 148.932] (II) event2 - Power Button: device removed
[ 148.932] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[ 148.932] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 148.932] (**) Option "xkb_model" "pc105"
[ 148.932] (**) Option "xkb_layout" "us"
[ 148.934] (II) event2 - Power Button: is tagged by udev as: Keyboard
[ 148.934] (II) event2 - Power Button: device is a keyboard
[ 148.935] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 148.935] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 148.935] (II) Using input driver 'libinput' for 'Power Button'
[ 148.936] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 30 paused 0
[ 148.936] (**) Power Button: always reports core events
[ 148.936] (**) Option "Device" "/dev/input/event1"
[ 148.936] (**) Option "_source" "server/udev"
[ 148.938] (II) event1 - Power Button: is tagged by udev as: Keyboard
[ 148.938] (II) event1 - Power Button: device is a keyboard
[ 148.938] (II) event1 - Power Button: device removed
[ 148.938] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/PNP0C0C:00/input/input1/event1"
[ 148.938] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 148.938] (**) Option "xkb_model" "pc105"
[ 148.938] (**) Option "xkb_layout" "us"
[ 148.940] (II) event1 - Power Button: is tagged by udev as: Keyboard
[ 148.941] (II) event1 - Power Button: device is a keyboard
[ 148.943] (II) config/udev: Adding input device PS/2+USB Mouse (/dev/input/event17)
[ 148.943] (**) PS/2+USB Mouse: Applying InputClass "libinput pointer catchall"
[ 148.943] (II) Using input driver 'libinput' for 'PS/2+USB Mouse'
[ 149.004] (II) systemd-logind: got fd for /dev/input/event17 13:81 fd 31 paused 0
[ 149.004] (**) PS/2+USB Mouse: always reports core events
[ 149.004] (**) Option "Device" "/dev/input/event17"
[ 149.004] (**) Option "_source" "server/udev"
[ 149.008] (II) event17 - PS/2+USB Mouse: is tagged by udev as: Mouse
[ 149.008] (II) event17 - PS/2+USB Mouse: device is a pointer
[ 149.008] (II) event17 - PS/2+USB Mouse: device removed
[ 149.008] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:03.0/0000:02:00.0/0000:03:00.0/0000:04:00.0/0000:05:02.0/usb7/7-3/7-3:1.0
/0003:1267:0210.0001/input/input17/event17"
[ 149.008] (II) XINPUT: Adding extended input device "PS/2+USB Mouse" (type: MOUSE, id 8)
[ 149.009] (**) Option "AccelerationScheme" "none"
[ 149.009] (**) PS/2+USB Mouse: (accel) selected scheme none/0
[ 149.009] (**) PS/2+USB Mouse: (accel) acceleration factor: 2.000
[ 149.009] (**) PS/2+USB Mouse: (accel) acceleration threshold: 4
[ 149.012] (II) event17 - PS/2+USB Mouse: is tagged by udev as: Mouse
[ 149.013] (II) event17 - PS/2+USB Mouse: device is a pointer
[ 149.015] (II) config/udev: Adding input device PS/2+USB Mouse (/dev/input/mouse0)
[ 149.015] (II) No input driver specified, ignoring this device.
[ 149.015] (II) This device may have been added with another device file.
[ 149.016] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event4)
[ 149.016] (II) No input driver specified, ignoring this device.
[ 149.016] (II) This device may have been added with another device file.
[ 149.017] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event5)
[ 149.017] (II) No input driver specified, ignoring this device.
[ 149.017] (II) This device may have been added with another device file.
[ 149.018] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event6)
[ 149.018] (II) No input driver specified, ignoring this device.
[ 149.018] (II) This device may have been added with another device file.
[ 149.019] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event7)
[ 149.019] (II) No input driver specified, ignoring this device.
[ 149.019] (II) This device may have been added with another device file.
[ 149.019] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event8)
[ 149.019] (II) No input driver specified, ignoring this device.
[ 149.019] (II) This device may have been added with another device file.
[ 149.020] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=11 (/dev/input/event9)
[ 149.020] (II) No input driver specified, ignoring this device.
[ 149.020] (II) This device may have been added with another device file.
[ 149.021] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event10)
[ 149.021] (II) No input driver specified, ignoring this device.
[ 149.021] (II) This device may have been added with another device file.
[ 149.022] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event11)
[ 149.022] (II) No input driver specified, ignoring this device.
[ 149.022] (II) This device may have been added with another device file.
[ 149.022] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event12)
[ 149.022] (II) No input driver specified, ignoring this device.
[ 149.022] (II) This device may have been added with another device file.
[ 149.023] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event13)
[ 149.023] (II) No input driver specified, ignoring this device.
[ 149.023] (II) This device may have been added with another device file.
[ 149.024] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event14)
[ 149.024] (II) No input driver specified, ignoring this device.
[ 149.024] (II) This device may have been added with another device file.
[ 149.025] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event15)
[ 149.025] (II) No input driver specified, ignoring this device.
[ 149.025] (II) This device may have been added with another device file.
[ 149.025] (II) config/udev: Adding input device HDA Intel Line Out Side (/dev/input/event16)
[ 149.025] (II) No input driver specified, ignoring this device.
[ 149.025] (II) This device may have been added with another device file.
[ 149.026] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 149.026] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[ 149.026] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[ 149.027] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 32 paused 0
[ 149.027] (**) AT Translated Set 2 keyboard: always reports core events
[ 149.027] (**) Option "Device" "/dev/input/event0"
[ 149.027] (**) Option "_source" "server/udev"
[ 149.029] (II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 149.030] (II) event0 - AT Translated Set 2 keyboard: device is a keyboard
[ 149.030] (II) event0 - AT Translated Set 2 keyboard: device removed
[ 149.030] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 149.030] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 149.030] (**) Option "xkb_model" "pc105"
[ 149.030] (**) Option "xkb_layout" "us"
[ 149.033] (II) event0 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[ 149.033] (II) event0 - AT Translated Set 2 keyboard: device is a keyboard
[ 149.034] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[ 149.034] (II) No input driver specified, ignoring this device.
[ 149.034] (II) This device may have been added with another device file.
[ 325.639] (**) Option "fd" "27"
[ 325.639] (II) event2 - Power Button: device removed
[ 325.639] (**) Option "fd" "30"
[ 325.639] (II) event1 - Power Button: device removed
[ 325.639] (**) Option "fd" "31"
[ 325.640] (II) event17 - PS/2+USB Mouse: device removed
[ 325.640] (**) Option "fd" "32"
[ 325.640] (II) event0 - AT Translated Set 2 keyboard: device removed
[ 325.641] (II) UnloadModule: "libinput"
[ 325.641] (II) systemd-logind: releasing fd for 13:64
[ 325.752] (II) UnloadModule: "libinput"
[ 325.752] (II) systemd-logind: releasing fd for 13:81
[ 325.820] (II) UnloadModule: "libinput"
[ 325.820] (II) systemd-logind: releasing fd for 13:65
[ 325.856] (II) UnloadModule: "libinput"
[ 325.856] (II) systemd-logind: releasing fd for 13:66
[ 325.897] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 325.897] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 325.897] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 325.898] (II) Server terminated successfully (0). Closing log file.
Re: [Hardware] The enemy you know: nvidia vs AMD
Your kernel (and thus the version of amdgpu) is perhaps a bit not-up-to-date? Try sid/bkworm.5.10.0-17-amd64
One of our pro bono undertakings is to help retired executives try Linux desktops. As a result of past unhappy experiences, we always reject computers that have Nvidia video chips. For business desktops AMD gpu also has a unique advantage in that the amdgpu driver is embedded in the Linux kernel.
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
No thanks. I don't do "unstable", and really intend to run 11 until 2026 if I can.Your kernel (and thus the version of amdgpu) is perhaps a bit not-up-to-date? Try sid/bkworm.
Maybe I'll build the module from source and test it, but if you are stating that the amdgpu is not "stable" then it should be documented as such in big bold glaring letters. LOL
But truth be told, I am very sceptical that a kernel module update is gonna account for the massive performance difference between nvidia proprietary and amdgpu.
Re: [Hardware] The enemy you know: nvidia vs AMD
Linux 5.10 is a "stable" (LTS) kernel. I'm sure you know what that means. The next LTS Linux kernel release was 6.1, one of the major highlights of of the 6.1 kernel is the optimizations for AMD PCs, especially the amdgpu driver.
Because our company has made a concerted effort to switch all our desktop computers to AMD Ryzens and Radeons, I have documented, from a user/supervisor's perspective, the more than one-and-half year of bkworm development history in a separate thread:
viewtopic.php?t=149947
During the bkworm development, it was officially labeled as "unstable", but, as I mentioned in the aforementioned thread, bkworm in the form of sid was actually more stable than the "stable" version (Bullseye), at least as far as desktops go. In Debian, unlike the Linux kernels, "stable" doesn't mean "stable stable", but simply means it is "version stable".
Because our company has made a concerted effort to switch all our desktop computers to AMD Ryzens and Radeons, I have documented, from a user/supervisor's perspective, the more than one-and-half year of bkworm development history in a separate thread:
viewtopic.php?t=149947
During the bkworm development, it was officially labeled as "unstable", but, as I mentioned in the aforementioned thread, bkworm in the form of sid was actually more stable than the "stable" version (Bullseye), at least as far as desktops go. In Debian, unlike the Linux kernels, "stable" doesn't mean "stable stable", but simply means it is "version stable".
- kent_dorfman766
- Posts: 540
- Joined: 2022-12-16 06:34
- Location: socialist states of america
- Has thanked: 59 times
- Been thanked: 70 times
Re: [Hardware] The enemy you know: nvidia vs AMD
@pwzhangzz
I will take a look at the 6.1 kernel and modules, and maybe update that component, but I got away from bleeding edge when I dumped Fedora several years ago in favor of longer release cycles. Thanks!
Am also concerned that updates/stability might favor wayland, which I have no interest in at all.
I will take a look at the 6.1 kernel and modules, and maybe update that component, but I got away from bleeding edge when I dumped Fedora several years ago in favor of longer release cycles. Thanks!
Am also concerned that updates/stability might favor wayland, which I have no interest in at all.