Remember this i7 8600K stay at 4.8ghz if you have delid can pass easily 5.0ghz
^_^

What's delid? :)

Delidding is the process of removing the metal heat spreader in a desktop CPU. By removing the lid you can place the cooler directly on the chip. Haven't tested myself but according to many websites it allows for better cooling. There are also tools to do it safely.


Remember this i7 8600K stay at 4.8ghz if you have delid can pass easily 5.0ghz
^_^

What's delid? :)

Delidding is the process of removing the metal heat spreader in a desktop CPU.

By removing the lid you can place the cooler directly on the chip.

Haven't tested myself but according to many websites it allows for better cooling.

There are also tools to do it safely.


Exactly and is highly recommended if want oc intel 8xxx beyond 4.7ghz

Easily can reduce temps around 20 degrees with good thermal paste

However delid remove intel cpu warranty

This tools is recommended

Delid Die Mate 2





Thermal Grizzly Conductonaut


This is official page of Delid Die Mate 2 and guide

http://der8auer.com/delid-die-mate/

^_^

Thanks, you learn something new every day :D

With AMD though, the heatpipe connector goes directly on the chip anyway, right? At least that's what I did when attaching my Noctua cooler.

With AMD though, the heatpipe connector goes directly on the chip anyway, right? At least that's what I did when attaching my Noctua cooler.

The integrated heat spreaders are the metal casing over the CPU die & they're not supposed to be removed... it's just that after Sandy Bridge Intel stopped soldering them, instead using much cheaper (and much less effective) thermal paste. So now it's a thing to de-lid them and replace the stock paste with something better to greatly reduce temperatures & allow for much better overclocks.

The IHS on AMD CPUs are still soldered; de-lidding them would offer no benefit.

Latest updates to Wine brought Mesa freeze back even with workaround patch.

Reverting commit 0832b5cded389096dcf74ac93367ae4ee4b8d35b and applying the workaround patch, prevents the freeze.

See https://source.winehq.org/git/wine.git/commitdiff/0832b5cded389096dcf74ac93367ae4ee4b8d35b

Józef Kucia add sample_c_lz
https://github.com/wine-mirror/wine/commit/ce8610cea58ed1ba9d8f17857e507d9d6c30132d
https://github.com/wine-mirror/wine/commit/e23ffa5548ae6806fa21fe93fb3f7684ec971b70

Yeah, I updated the howto.

New patches maybe in next hours can be approved (jozef kucia stay very active*)

[PATCH 1/4] wined3d: Disable pixel shader when rasterization is disabled.

[PATCH 2/4] wined3d: Handle stream output components when rasterization is disabled.

[PATCH 3/4] d3d11/tests: Add test for stream output components.

[PATCH 4/4] wined3d: Invalidate pixel shader only when rasterization is toggled.

https://source.winehq.org/patches/data/138358

Should fix GPU hangs in The Witcher 3 and Unigine: Superposition.

*Maybe because wine 3.0rc stay for begin later in this month, maybe next wine will be last of wine 2.x series (possible 2.21) after this in teory wine 3.0rc phase begins aka frozen code

Staging 2.21 will be very interesting

^_^

Should fix GPU hangs in The Witcher 3 and Unigine: Superposition.

Great! Right now you need to revert one commit to work around it.

Unfortunately some major bugs still remain:

https://bugs.winehq.org/show_bug.cgi?id=42820
https://bugs.winehq.org/show_bug.cgi?id=43131
https://bugs.winehq.org/show_bug.cgi?id=43828

It's merged to master now.

Should I call this a small improvement with Wine Staging 2.20? The "black veil" in the starting room of Kaer Morhen now has a texture. FPS is still a bit wonky but stutters more compared to 2.19.


Should I call this a small improvement with Wine Staging 2.20? The "black veil" in the starting room of Kaer Morhen now has a texture.

It has been a texture for a while for me. The root cause of this bug is still present.

FPS is still a bit wonky but stutters more compared to 2.19.

I have a feeling that unless Nvidia will fix their kernel module, this will remain an issue. May be Wine developers will find some workaround, but they are more focused on features than on optimizing for Nvidia blob now.

From Henri Verbeet, one of the Wine developers:

As a rough estimate I'd say about 40-50% of our users are using NVIDIA GPUs, of which about 80-90% are using the proprietary drivers. That's certainly a significant number of people, which of course we'll try to help where reasonably possible. But it's not just about numbers; Wine is in the first place a Free Software project, and quite frankly plenty of us would be happier if more of our users used Free Software drivers.

Interestingly, it means that number of Mesa users is higher for Wine, than percentage in POL stats (27% open / 73% blob).

Interestingly, it means that number of Mesa users is higher for Wine, than percentage in POL stats (27% open / 73% blob).

Maybe it's because of how TW3 works with Mesa drivers? And also I think there's no script for TW3 in PoL to install it easily and make it work properly, so Wine is better choice.

Interestingly, it means that number of Mesa users is higher for Wine, than percentage in POL stats (27% open / 73% blob).

Maybe it's because of how TW3 works with Mesa drivers?

In part, but Wine in general tends to work better with Mesa.

And also I think there's no script for TW3 in PoL to install it easily and make it work properly, so Wine is better choice.

POL is using Wine, but until recently, stock and staging Wine weren't ready enough and manual tweaks were needed to make a working combination. Now staging will probably get in good shape.

I think in part, the best thing about Mesa and Wine is the Gallium-Nine feature. In many gameplay benchmarks I've seen it's almost or on par with Windows. Meanwhile Witcher 3 is a perfect example that even without Nine, Mesa still beats Nvidia.

Today I've finished dusting off (literally in that sense) my old i5 system, highly thinking about putting an average AMD gpu dedicated just for Wine gaming and a few benchmarks. Will wait to see what else AMD has for show before diving in though.

I've never had an AMD card until now so I'm considering what it'd be like to use it with MESA.

I've never had an AMD card until now so I'm considering what it'd be like to use it with MESA.

These days it's a good time to get AMD already.

This is not good example, Nvidia drivers or Wine have some major problems with performance,
GPU utilisation don't go more then like ~60%. Going for uber to low on Nvidia give max + 20 fps (1440p uber -> 720p low) bug #42592. But anyway AMD is still better choice for Linux.

Looks like your CPU is pretty much fully loaded (always hard to judge with hyperthreading). Apparently, this doesn't happen with Mesa. Which means that the Nvidia blob is apparently wasting a lot of CPU when processing the Wine rendering. This probably means that Wine is doing some pretty uncommon things that the Nvidia blob was not optimised for (or worse even sacrificed in favour of other optimisations).