• Please review our updated Terms and Rules here

Machinist X99 Motherboards?

With all of the CPU vulnerability mitigations, having HT on cripples performance by up to 50% in some workloads. It's why I turn all of that crap off, it cripples performance on older CPUs.
 
From my research:

Benefits of Multithreading
• Improved throughput. ...
• Simultaneous and fully symmetric use of multiple processors for computation and I/O.
• Superior application responsiveness. ...
• Improved server responsiveness. ...
• Minimized system resource usage. ...
• Program structure simplification. ...
• Better communication.

Disadvantages of multi threading
Multithreaded and multicontexted applications present the following disadvantages:
• Difficulty of writing code as multithreaded and multicontexted applications are not easy to write.
• Difficulty of debugging.
• Difficulty of managing concurrency.
• Difficulty of testing. ...
• Difficulty of porting existing code.
 
Last edited:
While the cheap Chinese power supply works, I get a bit uneasy about the gutlessness of it all (weighs barely more than the box used to ship it). I broke down and bought a used (RFE) Corsair RM750i for less than $50 shipped. That thing is a beast of a unit. Nameplate says 62.5A on the +12, which I guess ought to work. The Chinese one didn't even have a PCIe connector, which made me even more leery.
 
A peripheral question. I'm running Linux and the sensors report indicate this for my graphics card:
Code: 
Adapter: PCI adapter
GPU core:    887.00 mV (min =  +0.82 V, max =  +1.21 V)
fan1:        2220 RPM
temp1:        +57.0°C  (high = +95.0°C, hyst =  +3.0°C)
                       (crit = +105.0°C, hyst =  +5.0°C)
                       (emerg = +135.0°C, hyst =  +5.0°C)
The card is " NVIDIA Corporation GF100GL [Quadro 4000] (rev a3)". I know, not state of the art, but okay for my purposes.
My question relates to the sensor temperature; it's always stated as 57.0C, never budging from that. Is this normal?
 
57C sounds about right for a video card of that type, especially if you're not loading it down.

Just take readings for sensors done by Linux with a grain of salt, because they can be wildly inaccurate on some hardware.

The Quadro 4000 I don't think has current Linux driver support, you'd have to be running an older distro with an older kernel to use one of the older Nvidia driver stacks. By default, Linux uses the Nouveau open source driver, and it leaves a lot to be desired.
 
My liquid cooled 4090 lopes at about 53-55 and the hotspot while gaming is about 65 or so. I don't overclock my GPU as the gains in FPS are very slight. You don't have anything to be concerned with.
 
Last edited:
GiGaBiTe said:
The Quadro 4000 I don't think has current Linux driver support, you'd have to be running an older distro with an older kernel to use one of the older Nvidia driver stacks. By default, Linux uses the Nouveau open source driver, and it leaves a lot to be desired.
Click to expand...
Bookworm has no problem with it thus far, but then, I'm not a gamer.
 
Just curious Chuck, do you go through the hassle of installing the proprietary Nvidia drivers on systems like this, or stick with Nouveau?
(I only say hassle because my laptop has a Nvidia chip with the legacy 390.xx driver, or Nouveau. Both are a hassle in my experience.)
 
Left it with Nouveau. I run 2 monitors off the card and haven't run into any issues. I am a little curious, however. Near the top-rear of the card, there's a 4-pin connector with the legend "For Mac". Did I get a special version of the card?

I don't know about Nvidia support for consumer graphics nowadays--they're riding high on the AI thing.
 
Chuck(G) said:
Bookworm has no problem with it thus far, but then, I'm not a gamer.
Click to expand...

The Nouveau OSS driver doesn't have the same performance or features that the proprietary Nvidia driver does. While it will generally work fine for basic desktop use, and some light 3D acceleration, it leaves a lot to be desired with games. The Nouveau driver doesn't have the Nvidia control panel, so many features there don't work at all, or you have to muck around in config files manually to make them work.

Chuck(G) said:
FWIW, the Nvidia-supplied driver appears to be fairly recent, but I haven't tried it: https://www.nvidia.com/download/driverResults.aspx/193764/en-us/
The non-free nvidia-driver package is also available in Bookworm: https://packages.debian.org/bookworm/nvidia-driver
Click to expand...

That driver won't work. The last driver version that supported your Quadro 4000 is the 390 branch.
www.nvidia.com

Linux x64 (AMD64/EM64T) Display Driver | 390.157 | Linux 64-bit | NVIDIA

Download the English (US) Linux x64 (AMD64/EM64T) Display Driver for Linux 64-bit systems. Released 2022.11.22
www.nvidia.com

This driver won't compile against modern kernels, leaving you to have to either use the Nouveau driver, or rely on community driver bundles for your specific distro. Several distros have the 390xx branch available on 3rd party repositories, but YMMV on how it will work since Nvidia no longer supports it. For it to continue working, the community has to keep it maintained. With the rapid development of the Kernel going on these days, it's a bit of a headache.

I have always had a lot more trouble keeping old Nvidia cards working under Linux due to driver issues. AMD on the other hand has contributed quite a bit to the OSS Radeon driver, making it easier to keep older cards working with most of the features working.
 
Chuck(G) said:
Left it with Nouveau. I run 2 monitors off the card and haven't run into any issues. I am a little curious, however. Near the top-rear of the card, there's a 4-pin connector with the legend "For Mac". Did I get a special version of the card?

I don't know about Nvidia support for consumer graphics nowadays--they're riding high on the AI thing.
Click to expand...
Does the 4-pin connector appear to be power? It may be that if using in a Mac not enough power was delivered via the PCIe connector.
 
Could be--the connector is located close to the 6-pin PCIe power connector.

And you're right @GiGaBiTe, I installed the Debian nvidia-driver (what a load of files!) and had to go back and purge it and rebuild the kernel. Oh well--I'll check for a community 390 build for Bookworm, but maybe it's not worth the trouble. :(

Maybe I'll look around for a decent AMD-based card--one of these days...
 
A little tidbit for those who run Debian/Ubuntu on one of these.

I was experiencing periodic network connection drops running Debian 12 Bookworm. This was a little strange because I'd installed Debian 11 Bullseye with no problems earlier. The network chip on this motherboard is the Realtek RTL8111/8168/8411.

Digging a bit, I found that the culprit seemed to be the RTL8169 driver in the kernel. Simply installing the older 8168 module didn't solve the problem. I found that loading the 8168 at boot time and blacklisting the 8169 module was the fix required. It seems that this has not been an uncommon problem with Debian, Mint, Proxmox, Ubuntu...

FWIW, the lspci -k entry now looks like:
Code: 
5:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
        Kernel driver in use: r8168
        Kernel modules: r8168

Hope this is of some use to someone.
 
After a long shakeout period, I think I've got a stable Realtek ethernet connection on Bookworm. After installing the old r8168-dkms module, the /etc/modprobe.d/r8168-dkms.conf file should look like this:
Code: 
# settings for r8168-dkms

# map the specific PCI IDs instead of blacklisting the whole r8169 module
alias   pci:v00001186d00004300sv00001186sd00004B10bc*sc*i*      r8168
alias   pci:v000010ECd00008168sv*sd*bc*sc*i*                    r8168

options r8168 eee_enable=0

# if the aliases above do not work, uncomment the following line
# to blacklist the whole r8169 module
blacklist r8169
It took quite a bit of searching through trouble reports and solutions and trying each one, but this one appears to be a winner. It appears that the "energy efficient ethernet" feature was causing the connection to drop periodically.
 
There are some things that shouldn't be green washed, Ethernet being among them.

Usually, there are a few options in the BIOS that can control whether the Ethernet is shut off or not. Some manufacturers call it "Green Net", others put it in the "ErP Ready" functionality, which does a lot more.

Disabling Green Net and ErP Ready options usually fixes that annoyance.
 
You must log in or register to reply here.
Back
Top