LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   GPU fans not spinning, and how to run GPU stress test (https://www.linuxquestions.org/questions/linux-hardware-18/gpu-fans-not-spinning-and-how-to-run-gpu-stress-test-4175679432/)

Arct1c_f0x 07-26-2020 08:03 PM
GPU fans not spinning, and how to run GPU stress test
 
Nothing is wrong with my AMD Gigabyte GPU but I noticed that it's fans are not spinning (three fan GPU) although they do start spinning when I power on my tower. I pretty certain that this is because the GPU is in a special mode where the fans don't start spinning until the GPU reaches a certain temp.

Is there any way to make the fans run automatically when the desktop is on? Or would I not want to do that?



2nd question.
What's the best way in your opinion to run a diagnostic GPU stress test? I just want to know how for my own personal edification (There's nothing wrong with my brand new GPU)


Thanks in advance!

scasey 07-26-2020 08:26 PM
It sounds like you’re saying the fans don’t spin when the power is off...???

I would expect the fans to only run when they’re needed.
Gotta say: “If it ain’t broke, don’t fix it.”

EdGr 07-26-2020 08:56 PM
Since you have a new GPU, check the kernel messages to make sure that the kernel recognizes it and loads the firmware. Then, check Xorg.0.log to make sure that X recognizes the GPU and enables acceleration.

For a stress test, run multiple glblurs in parallel. Make the windows large.

Code:
for ((n=0; n<8; n++)); do /usr/libexec/xscreensaver/glblur -fps & done
Three glblurs can max out my six-year-old GPU at 4K.
Ed

Arct1c_f0x 07-27-2020 06:32 AM
Quote:
Originally Posted by scasey (Post 6149630)
It sounds like you’re saying the fans don’t spin when the power is off...???

I would expect the fans to only run when they’re needed.
Gotta say: “If it ain’t broke, don’t fix it.”
Sorry for the confusion. At first when I turn my tower on the fans power on, but then immediately after that anything I do and they don't spin.

ondoho 07-27-2020 06:43 AM
Stress test the GPU - play some games?
IF they use the GPU at all. 'glxinfo' can tell you if that's possible.

Possibly also 'sensors'detect' and 'sensors'.
Read all these commands' man pages before asking about their usage.

verndog 07-27-2020 10:32 AM
There's a tool called 'stress'. From debian based, just
Code:
sudo apt install stress
. Then run something like this
Quote:
stress -c 1 -t 10
from command line.

obobskivich 07-27-2020 02:06 PM
Quote:
Originally Posted by Arct1c_f0x (Post 6149753)
Sorry for the confusion. At first when I turn my tower on the fans power on, but then immediately after that anything I do and they don't spin.
This is normal/designed behavior on newer GPUs (going back at least a few years now - for example my GeForce 1080 does this, and is 2-3 years old, but my Radeon 290X does not, and is a year or two older than that) - you are exactly right, the fan is set to be 'off' unless the GPU hits a pre-defined temperature (usually 40-50* C). Nothing is wrong with operating this way, and this behavior is provided by the card's firmware. It is possible to override this either by A) connecting the fans directly to the computer's power supply (and they will just run all the time, at maximum speed) or B) software. On linux I'm not sure exactly what that software package is, but on Windows you would use something like Afterburner (which is based on Rivatuner) to set a manual fan-curve - this would only apply AFTER the system had booted up and the software was running (in other words, the software is over-riding the card's firmware behavior, not changing it). In general, I would just accept the default behavior, because it is set with sane values - the GPU is not in danger at lower temperatures, and the fans should be spinning up at higher temperatures (and with 3 separate fans, the odds that something is just 'blocking' the fan from spinning are low - if this was a single fan card I would tell you to check and make sure something isn't sticking the fan in place (e.g. like it sucked up a ziptie or something)).

A quick web search found this thread on another forum about 'Afterburner alternatives on linux' that you might find interesting/helpful: https://linustechtips.com/main/topic...tive-on-linux/

Finally, if you want to see the GPU's temperature and fan RPM, psensor (which is basically a nice GUI application to get the same info 'sensors' will provide, as ondoho suggests) should be able to do that for you. This way you can confirm the GPU is indeed under some temperature threshold (for example my newer GeForce card does this, and the fan stays off under 50* C, and only comes on to about 900 RPM under 60* C), and not actually overheating (on a modern GPU that would generally be >90* C).

For loading the GPU up, I agree with the other suggestions - run a 3D game or some other 3D application (like the screensaver suggestion from EdGr is a good one). A lot of 'GPU stress test' applications (like Furmark) are strongly counterindicated by nVidia/AMD as they can create a significant amount of heat for the GPU, which can lead to thermal stress on the board, and/or premature failure (not to mention how much power it wastes).

Arct1c_f0x 07-27-2020 03:22 PM
Quote:
Originally Posted by EdGr (Post 6149638)
Since you have a new GPU, check the kernel messages to make sure that the kernel recognizes it and loads the firmware. Then, check Xorg.0.log to make sure that X recognizes the GPU and enables acceleration.

For a stress test, run multiple glblurs in parallel. Make the windows large.

Code:
for ((n=0; n<8; n++)); do /usr/libexec/xscreensaver/glblur -fps & done
Three glblurs can max out my six-year-old GPU at 4K.
Ed
I'm still pretty new to this. Do you mean check the Kernel messages when the system first boots up? And what is the Xorg.0.log and how do I check it?


when I type the sensors command this is what shows up:

asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +28.0°C


On my other system when I type 'sensors' into a terminal is says amdgpu and then describes all this information about the GPU

Thanks Ed

Arct1c_f0x 07-27-2020 03:25 PM
Quote:
Originally Posted by obobskivich (Post 6149906)
This is normal/designed behavior on newer GPUs (going back at least a few years now - for example my GeForce 1080 does this, and is 2-3 years old, but my Radeon 290X does not, and is a year or two older than that) - you are exactly right, the fan is set to be 'off' unless the GPU hits a pre-defined temperature (usually 40-50* C). Nothing is wrong with operating this way, and this behavior is provided by the card's firmware. It is possible to override this either by A) connecting the fans directly to the computer's power supply (and they will just run all the time, at maximum speed) or B) software. On linux I'm not sure exactly what that software package is, but on Windows you would use something like Afterburner (which is based on Rivatuner) to set a manual fan-curve - this would only apply AFTER the system had booted up and the software was running (in other words, the software is over-riding the card's firmware behavior, not changing it). In general, I would just accept the default behavior, because it is set with sane values - the GPU is not in danger at lower temperatures, and the fans should be spinning up at higher temperatures (and with 3 separate fans, the odds that something is just 'blocking' the fan from spinning are low - if this was a single fan card I would tell you to check and make sure something isn't sticking the fan in place (e.g. like it sucked up a ziptie or something)).

A quick web search found this thread on another forum about 'Afterburner alternatives on linux' that you might find interesting/helpful: https://linustechtips.com/main/topic...tive-on-linux/

Finally, if you want to see the GPU's temperature and fan RPM, psensor (which is basically a nice GUI application to get the same info 'sensors' will provide, as ondoho suggests) should be able to do that for you. This way you can confirm the GPU is indeed under some temperature threshold (for example my newer GeForce card does this, and the fan stays off under 50* C, and only comes on to about 900 RPM under 60* C), and not actually overheating (on a modern GPU that would generally be >90* C).

For loading the GPU up, I agree with the other suggestions - run a 3D game or some other 3D application (like the screensaver suggestion from EdGr is a good one). A lot of 'GPU stress test' applications (like Furmark) are strongly counterindicated by nVidia/AMD as they can create a significant amount of heat for the GPU, which can lead to thermal stress on the board, and/or premature failure (not to mention how much power it wastes).
Thanks a lot obobskivich! You made a lot of useful information plain and concise! I appreciate it and I gave you some rep

ondoho 07-27-2020 04:25 PM
Quote:
Originally Posted by verndog (Post 6149835)
There's a tool called 'stress'. From debian based, just
Code:
sudo apt install stress
. Then run something like this from command line.
If OP's concern is really about the GPU and its fan only, then stressing the CPU is pointless.
Although it could indirectly help troubleshoot the issue.

Quote:
Originally Posted by EdGr (Post 6149638)
For a stress test, run multiple glblurs in parallel. Make the windows large.

Code:
for ((n=0; n<8; n++)); do /usr/libexec/xscreensaver/glblur -fps & done
Nice idea, haven't noticed it before!

EdGr 07-27-2020 06:09 PM
Quote:
Originally Posted by Arct1c_f0x (Post 6149927)
I'm still pretty new to this. Do you mean check the Kernel messages when the system first boots up? And what is the Xorg.0.log and how do I check it?
As root, do:

Code:
dmesg | less
You should see lines like:

Code:
[  11.739473] [drm] radeon kernel modesetting enabled.
...
[  11.743892] [drm] radeon: 2048M of VRAM memory ready
[  11.743894] [drm] radeon: 2048M of GTT memory ready.
[  11.743902] [drm] Loading pitcairn Microcode
[  11.921961] [drm] Internal thermal controller with fan control
In /var/log/Xorg.0.log, you should see lines like:

Code:
[    51.092] (--) RADEON(0): Chipset: "PITCAIRN" (ChipID = 0x6819)
...
[    52.547] (II) RADEON(0): glamor X acceleration enabled on AMD PITCAIRN (DRM 2.50.0, 5.4.51, LLVM 10.0.0)
Quote:
Originally Posted by ondoho (Post 6149953)
Nice idea, haven't noticed it before!
Thanks! I find that glblur is good for testing GPUs and inducing vertigo. ;)
Ed

Arct1c_f0x 07-27-2020 06:32 PM
Quote:
Originally Posted by EdGr (Post 6149988)
As root, do:

Code:
dmesg | less
You should see lines like:

Code:
[  11.739473] [drm] radeon kernel modesetting enabled.
...
[  11.743892] [drm] radeon: 2048M of VRAM memory ready
[  11.743894] [drm] radeon: 2048M of GTT memory ready.
[  11.743902] [drm] Loading pitcairn Microcode
[  11.921961] [drm] Internal thermal controller with fan control
In /var/log/Xorg.0.log, you should see lines like:

Code:
[    51.092] (--) RADEON(0): Chipset: "PITCAIRN" (ChipID = 0x6819)
...
[    52.547] (II) RADEON(0): glamor X acceleration enabled on AMD PITCAIRN (DRM 2.50.0, 5.4.51, LLVM 10.0.0)
Thanks! I find that glblur is good for testing GPUs and inducing vertigo. ;)
Ed
Yeah I want to say that it's definitely not recognizing my GPU for what it is

When i do

Quote:
sudo dmesg | grep -i vga or I type dmesg | grep -i GPU or AMDGPU
Nothing shows up and i've gone through almost every line now and nothing seems to ackowledge my graphics card.

I started up a pc game 'Warband mount and Blade' on steam on this desktop and it ran really really poorly (and warband is not a super graphics intensive game.) I mean obviously my graphics card is working because I have my monitor plugged into it (display port at 1080p) but I think it's running at a stunted level of performance.

Further more when I type sensors in the terminal this is what I get
Quote:
asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1: +47.0°C
I'm downloading AOEII now on steam to try and play that so we'll see. Any deal what the problem is?

EdGr 07-27-2020 06:53 PM
Quote:
Originally Posted by Arct1c_f0x (Post 6149996)
Yeah I want to say that it's definitely not recognizing my GPU for what it is

When i do



Nothing shows up and i've gone through almost every line now and nothing seems to ackowledge my graphics card.

I started up a pc game 'Warband mount and Blade' on steam on this desktop and it ran really really poorly (and warband is not a super graphics intensive game.) I mean obviously my graphics card is working because I have my monitor plugged into it (display port at 1080p) but I think it's running at a stunted level of performance.
You are in for an OS upgrade. You want a very recent OS to support your GPU.

Alternatively, you can install AMD's proprietary driver as a stopgap measure until the open-source drivers have caught up.
Ed

Arct1c_f0x 07-27-2020 08:56 PM
Quote:
Originally Posted by EdGr (Post 6150006)
You are in for an OS upgrade. You want a very recent OS to support your GPU.

Alternatively, you can install AMD's proprietary driver as a stopgap measure until the open-source drivers have caught up.
Ed
That's awesome thanks, Ed! I have pretty much the newest Debian buster version - Debian Buster AMD 64 10.4

This is my graphics card:
https://www.newegg.com/gigabyte-rade...82E16814932236


GIGABYTE Radeon RX 5500 XT DirectX 12 GV-R55XTGAMING OC-8GD 8GB 128-Bit GDDR6 PCI Express 4.0 x16 ATX Video Card

I just bought it, think it need proprietary drivers to function at its full potential?

It's this one the RX 5500 series
Quote:
AMD Radeon™ Product Family Compatibility

Radeon™ Software for Linux® is compatible with the following AMD products.
AMD Product Family Compatibility

AMD Radeon™ RX 5700/5600/5500 Series Graphics
Can't seem to find where the download for the proprietary drivers for my card are but I'll continue looking. Is it right in front of my face and I don't see it?

Thanks again, Ed. I think you're right that I need the proprietary drivers for it to function correctly.

EdGr 07-27-2020 09:45 PM
Quote:
Originally Posted by Arct1c_f0x (Post 6150030)
That's awesome thanks, Ed! I have pretty much the newest Debian buster version - Debian Buster AMD 64 10.4

...

Thanks again, Ed. I think you're right that I need the proprietary drivers for it to function correctly.
Yes, use the proprietary driver for now. Debian takes an especially long time to get new software into a release.
Ed

ondoho 07-28-2020 02:41 AM
^ and a backported kernel.

Arct1c_f0x 07-28-2020 08:52 AM
Okay so I've download the non-free AMD drivers and I've upgraded the Kernel from 4.19 to 5.6

The problem is that when I test the same game everything is still really choppy and there's a slight lag still present.
Keep in mind we're talking about a game that is not super graphics intensive and was made probably ten years ago.


Is there something that I'm missing here? Is it because this graphics card has GDDR6 and PCIe 4.0?
Are there other people who have gotten this type of graphics card to perform at its potential on Debian buster?



I might create a new thread because this problem has changed and morphed into what I think was always the real problem; firmware compatability

Any advice would be much appreciated!

EdGr 07-28-2020 09:28 AM
Post the kernel dmesg output and the Xorg.0.log.
Ed

Arct1c_f0x 07-28-2020 11:25 AM
Output from dmesg
 
1 Attachment(s)
Output from 'dmesh' in terminal

I've included the output from dmesg as a .txt file since it was too large to post here. It's attached 'dmesg output.txt'

This is an interesting bit that I noticed in the output of dmesg. Do you think it has something to do with the problem?

Quote:
[drm] add ip block number 5 <dm>
[ 1.027157] [drm] add ip block number 6 <gfx_v10_0>
[ 1.027157] [drm] add ip block number 7 <sdma_v5_0>
[ 1.027157] [drm] add ip block number 8 <vcn_v2_0>
[ 1.027158] [drm] add ip block number 9 <jpeg_v2_0>
[ 1.027167] amdgpu 0000:0b:00.0: firmware: failed to load amdgpu/navi14_gpu_info.bin (-2)
[ 1.027170] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 1.027171] amdgpu 0000:0b:00.0: Direct firmware load for amdgpu/navi14_gpu_info.bin failed with error -2
[ 1.027172] amdgpu 0000:0b:00.0: Failed to load gpu_info firmware "amdgpu/navi14_gpu_info.bin"
[ 1.027174] amdgpu 0000:0b:00.0: Fatal error during GPU init
[ 1.027175] [drm] amdgpu: finishing device.
[ 1.027250] amdgpu: probe of 0000:0b:00.0 failed with error -2
[ 1.101743] nvme nvme0: 8/0/0 default/read/poll queues
[ 1.102317] nvme0n1: p1 p2 < p5 >
[ 1.210140] ata1: SATA link down (SStatus 0 SControl 300)
[ 1.210167] ata8: SATA link down (SStatus 0 SControl 300)
[ 1.218371] ata9: SATA link down (SStatus 0 SControl 300)
[ 1.232024] usb 5-3: new full-speed USB device number 2 using xhci_hcd
[ 1.232029] usb 3-5: new full-speed USB device number 2 using xhci_hcd
[ 1.372461] ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 1.380458] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

EdGr 07-28-2020 12:22 PM
Yes, the firmware failing to load is the problem. On Debian, firmware needs to be installed manually. You also need to find a recent version that has your GPU's firmware (Debian unoffical 2020_06_22 does not have it).

BTW, Slackware64-current has your GPU's firmware included by default. The firmware does exist. :)
Ed

Arct1c_f0x 07-28-2020 01:53 PM
Quote:
Originally Posted by EdGr (Post 6150298)
Yes, the firmware failing to load is the problem. On Debian, firmware needs to be installed manually. You also need to find a recent version that has your GPU's firmware (Debian unoffical 2020_06_22 does not have it).

BTW, Slackware64-current has your GPU's firmware included by default. The firmware does exist. :)
Ed
So if I use the slackware OS (sorry never heard of it before) then I will be able to see optimal performance from my GPU?

If yes, how similar is it to Debian Buster? Can I still use the Gnome desktop environment?

Do you know the exact name of the driver that I need for my specific card? and If I simply install said driver on my Debian system it will fix my problem? or is the problem that the proper drivers for my card aren't available in Debian?

Sorry for all the questions, Ed. And I really appreciate your assistance in this matter.

EdGr 07-28-2020 02:59 PM
Your GPU is a Navi14.

On Slackware64-current, I see:

Code:
% ls -l /lib/firmware/amdgpu/navi14*
-rw-r--r-- 1 root root 160256 Jul  8 13:02 /lib/firmware/amdgpu/navi14_asd.bin
-rw-r--r-- 1 root root 263296 Jul  8 13:02 /lib/firmware/amdgpu/navi14_ce.bin
-rw-r--r-- 1 root root 263296 Jul  8 13:02 /lib/firmware/amdgpu/navi14_ce_wks.bin
-rw-r--r-- 1 root root    772 Jul  8 13:02 /lib/firmware/amdgpu/navi14_gpu_info.bin
-rw-r--r-- 1 root root 263424 Jul  8 13:02 /lib/firmware/amdgpu/navi14_me.bin
-rw-r--r-- 1 root root 263424 Jul  8 13:02 /lib/firmware/amdgpu/navi14_me_wks.bin
-rw-r--r-- 1 root root 268592 Jul  8 13:02 /lib/firmware/amdgpu/navi14_mec.bin
-rw-r--r-- 1 root root 268592 Jul  8 13:02 /lib/firmware/amdgpu/navi14_mec2.bin
-rw-r--r-- 1 root root 268592 Jul  8 13:02 /lib/firmware/amdgpu/navi14_mec2_wks.bin
-rw-r--r-- 1 root root 268592 Jul  8 13:02 /lib/firmware/amdgpu/navi14_mec_wks.bin
-rw-r--r-- 1 root root 263424 Jul  8 13:02 /lib/firmware/amdgpu/navi14_pfp.bin
-rw-r--r-- 1 root root 263424 Jul  8 13:02 /lib/firmware/amdgpu/navi14_pfp_wks.bin
-rw-r--r-- 1 root root  42664 Jul  8 13:02 /lib/firmware/amdgpu/navi14_rlc.bin
-rw-r--r-- 1 root root  33792 Jul  8 13:02 /lib/firmware/amdgpu/navi14_sdma.bin
-rw-r--r-- 1 root root  33792 Jul  8 13:02 /lib/firmware/amdgpu/navi14_sdma1.bin
-rw-r--r-- 1 root root 264586 Jul  8 13:02 /lib/firmware/amdgpu/navi14_smc.bin
-rw-r--r-- 1 root root 184144 Jul  8 13:02 /lib/firmware/amdgpu/navi14_sos.bin
-rw-r--r-- 1 root root  29440 Jul  8 13:02 /lib/firmware/amdgpu/navi14_ta.bin
-rw-r--r-- 1 root root 390144 Jul  8 13:02 /lib/firmware/amdgpu/navi14_vcn.bin
I do not see these files on Debian testing even after installing firmware-amd-graphics-20190717-2_all.deb. The package is already a year old.

I would expect the AMD proprietary driver to install the firmware. Did it install properly?

At this point, these best thing to do depends on how comfortable you are in debugging OSes.

Slackware "current" has faster turnaround than Debian "testing" but does not include Gnome.
Ed

Arct1c_f0x 07-28-2020 04:36 PM
Quote:
Originally Posted by EdGr (Post 6150367)
Your GPU is a Navi14.


I do not see these files on Debian testing even after installing firmware-amd-graphics-20190717-2_all.deb. The package is already a year old.

I would expect the AMD proprietary driver to install the firmware. Did it install properly?

At this point, these best thing to do depends on how comfortable you are in debugging OSes.

Slackware "current" has faster turnaround than Debian "testing" but does not include Gnome.
Ed
Right now I'm considering returning this GPU and getting another AMD gpu from the RX 580 series because the one I have on my other desktop build is killin' it. It's amazing when it comes to games.
That one has the:
ASUS ROG Strix Radeon RX 580 O8G Gaming OC Edition GDDR5 AMD Graphics Card (ROG-STRIX-RX580-O8G-GAMING)


I mean I know it's sounds stupid but I don't want to give up Gnome because I've gotten so used to using it for my work. I don't really even play any games that are too graphics intensive, I guess I just a little carried away with this purchase. I mean I installed the AMD proprietary drivers so I guess it didn't work.


What do you think?

Edit:
I guess what you're saying is that I probably couldn't get this card to work well with Debian?

obobskivich 07-28-2020 05:32 PM
Pre-script: I like Ed's advice here, but have a few questions/thoughts:

Have you tried Ubuntu? It's based on Debian, and is much 'closer' to what you're used to than Slackware-current will be, basically it's probably a decent 'in-between' in getting you a more familiar environment/system that's more up to date. AMD appears to have support from their driver for 20.04 (the current Ubuntu release - I linked it at the end of this post), which I found linked from Ubuntu's community forums discussing 5500s in 20.04. There are also other rolling-release OSes based on Debian, like Sparky, that are probably even more 'bleeding edge' (similar to Slackware-current, but not so different from Debian as Slackware).

If you go slackware:
As far as gaming in Slackware (if that's the way you want to go after all), it's certainly possible, but dependency resolution can be a pain (relative to apt or dnf), and just getting something like Steam to work takes more involvement than downloading and running a .deb or PPA. Checkout Slackbuilds.org for more info, and read through the documentation for slackpkg, sbopkg, and sbodeps (basically, know what you're getting into). I'd also read through the Slackware install guide on the project's main website too. A properly set-up multilib system with sbopkg + sbodeps is fairly comparable to other distros (e.g. Ubuntu, PCLOS, OEL 8, etc) in terms of 'just go get the program you want and work the dependencies out for me' but installs can take longer if the buildscript requires compilation from source (e.g. installing barrier on Ubuntu takes me about 2 minutes; on a similar Slackware box it took me around 5 hours because it had to compile various dependencies - this is probably a 'worst case' comparison but you should know what you're getting into).


https://www.amd.com/en/support/kb/re...ed-linux-20-20

It definitely looks like this can work in Ubuntu, which will run GNOME 3 and be more similar to what you expect with Debian (just, more current).

EdGr 07-28-2020 06:26 PM
Quote:
Originally Posted by Arct1c_f0x (Post 6150391)
What do you think?

Edit:
I guess what you're saying is that I probably couldn't get this card to work well with Debian?
I think that you have a perfectly good GPU and a too-old OS. This is a common problem with new hardware.

Try another distro as obobskivich suggested. That should be faster than waiting for Debian to catch up.
Ed

Arct1c_f0x 08-01-2020 05:15 PM
Well, gentlemen. I think I'm going to do it. I'm going to switch (at least on this desktop) to Ubuntu, which I've never tried but why not? I can have a three monitor display in Ubuntu right? I'm sure the answer is yes but I'm just asking. I'm going to install the version 20.04 and then I'll install the drivers from the AMD website. I'll let you guys know how it goes!

Arct1c_f0x 08-02-2020 10:04 AM
Ubuntu up and running
 
Proud to say that everything is up and working perfectly! Tried out some games on Ubuntu and everything works great! I originally just bought a newer graphics card to support a 3+ monitor display system that I wanted to set up but I wanted to have the option of playing games as well!

The cool things is that not only did Ubuntu come already preinstalled with the drivers for my graphics card but it also came preinstalled with drivers for everything else that I would have had to install post-installation like the wifi drivers for my motherboard! I'm pretty pleased with how things have gone and I'm thankful for ya'lls help!

The reason I didn't initially want to switch to Ubuntu is that I heard that Canonical was involved in some telemetry shannanigans and I value personal privacy (even in trivial things) as a paramount value.

Thanks again you guys! Ed and obobskivich, thanks to you two especially.

I'm going to go ahead and mark this SOLVED.


MOD REQUEST
I would ask that a moderator change the original name of this entire thread to reflect what transpired in this thread and the solution that was reached.

Thanks again guys.

obobskivich 08-03-2020 09:24 AM
Quote:
Originally Posted by Arct1c_f0x (Post 6151985)
Proud to say that everything is up and working perfectly! Tried out some games on Ubuntu and everything works great! I originally just bought a newer graphics card to support a 3+ monitor display system that I wanted to set up but I wanted to have the option of playing games as well!

The cool things is that not only did Ubuntu come already preinstalled with the drivers for my graphics card but it also came preinstalled with drivers for everything else that I would have had to install post-installation like the wifi drivers for my motherboard! I'm pretty pleased with how things have gone and I'm thankful for ya'lls help!

The reason I didn't initially want to switch to Ubuntu is that I heard that Canonical was involved in some telemetry shannanigans and I value personal privacy (even in trivial things) as a paramount value.

Thanks again you guys! Ed and obobskivich, thanks to you two especially.

I'm going to go ahead and mark this SOLVED.


MOD REQUEST
I would ask that a moderator change the original name of this entire thread to reflect what transpired in this thread and the solution that was reached.

Thanks again guys.
Glad to hear you got it working!

Re: Ubuntu and 'telemetry shannanigans' my understanding is they removed all of the most obnoxious aspects (the Amazon snap) a few major releases ago, and even the Amazon bookmarks were expunged with the release of 20.04 in response to people's dissatisfaction. The MOTD 'its not advertising but we've used it for advertising before' feature (technically the script itself did not run ads, but it draws from a Cannonical site that displayed an ad) still exists, but will never fire unless you're SSH'ing in - you can disable this behavior (and see the full source of the script that would otherwise fire). See more here: https://raymii.org/s/tutorials/Disab...ntu_18.04.html
https://news.ycombinator.com/item?id=14662088

Overall, as 'annoying' as the MOTD News feature seems at face value (from the above links), it's basically a non-issue in practice - I've watched the behavior via firewall and never see this script fire (as in, it never makes the connections specified) on machines that aren't running SSH servers, so it behaves exactly as documented, and I don't believe they have repeated the misstep of putting out an 'ad' via MOTD News again (again, due to community feedback).

EdGr 08-03-2020 11:53 AM
That is good to hear. :)

If you are ever unhappy with Ubuntu, eventually Debian will support your GPU (maybe in a year and with manual firmware installation).
Ed


All times are GMT -5. The time now is 04:05 PM.