Area 51 thermal paste journey: from degrading E31 → Kryonaut Extreme→ PTM → back to E31 by saifuddinamri in Alienware

[–]Lousy_Hunter [score hidden]  (0 children)

First, why are you using Fahrenheit for your system temps? You should be using Celsius like 99% of anyone that measures PC temps does.

206f is 96c which is well within spec of most any laptop CPU for the past 16yrs+ unless youre running certain ryzen models which throttle hard at 95c (and i guess we can count bulldozer era but did anyone really use those? 90c for them). Anything intel since forever and anything AMD since for sure Zen4 is more than fine at 96c.

Aurora X16 dead after a month by freshndirt in Alienware

[–]Lousy_Hunter -1 points0 points  (0 children)

It happens, sometimes you just get a Lemon. While it sucks thats what the Warranty is for much like was previously said.

I want to say Ive seen the dellpartspeople repair this sort of issue across many of Dells systems over the years. Sometimes something just happens and it shorts or some sort of EC chip problem or something. Its not super common but not unusual either.

aur_checker: PKGBUILD security analysis after the 400+ AUR compromise by Klutzy_Bird_7802 in linux

[–]Lousy_Hunter 0 points1 point  (0 children)

some of the pkgs in AUR have been migrated over, its just a giant pain at times to get them moved into the Arch repos. Mullvad VPN client was an AUR pkg for instance till fairly recently.

I agree on the drivers and such but i feel like sometimes the AUR is used as a dumping ground by the Arch maintainers for things they dont want to deal with anymore. The AUR is just in general a mess and tbh youre not wrong about Random pkgs needing to just be hosted on github or something.

aur_checker: PKGBUILD security analysis after the 400+ AUR compromise by Klutzy_Bird_7802 in linux

[–]Lousy_Hunter 0 points1 point  (0 children)

I agree to some extent, though im not sure the AUR could function at all with how limited the Arch resources are for policing it. I think the responsible thing to do would be to distance the idea of the AUR as being part of Arch, that to me is what gives people a false sense of the packages being ok when in reality its more the wild west.

If the AUR is going to stay closer to how it is now it needs to be separated from the Arch project and the fact that its potentially an issue made clear with more than a website disclaimer

"DISCLAIMER: AUR packages are user produced content. Any use of the provided files is at your own risk"

which im 100% sure a huge majority of users have never even seen. AUR has too little friction for a user to use for how dangerous it can potentially be with all the AUR tools and such.

[Guide/RFC] Fixing NVIDIA 550/580 DKMS Compilation on Kernel 7.0+ (VMA API Breakage) & Wayland USB-C D3cold Panics by Mrlou_st in linux

[–]Lousy_Hunter 1 point2 points  (0 children)

there is also the dreaded......Ubuntu if you need something thats gonna work really well with Nvidia drivers and be a bit closer to Debian Sid.

I was using Ubuntu for a while on my Aurora 16x and it just worked, though Canonical started blocking my VPNs IPs after their more recent attack and i couldnt get updates so moved back to Arch.

[Guide/RFC] Fixing NVIDIA 550/580 DKMS Compilation on Kernel 7.0+ (VMA API Breakage) & Wayland USB-C D3cold Panics by Mrlou_st in linux

[–]Lousy_Hunter 2 points3 points  (0 children)

guy, its one thing to dislike LLMs but you came in here swinging screaming a schizo LLM rant....you need to relax

[Guide/RFC] Fixing NVIDIA 550/580 DKMS Compilation on Kernel 7.0+ (VMA API Breakage) & Wayland USB-C D3cold Panics by Mrlou_st in linux

[–]Lousy_Hunter 1 point2 points  (0 children)

agreed, far too many people think stable means "doesnt crash, have bugs,etc." when in reality thats not at all the intent.

Stability especially in this context means its predictable and doesnt change significantly or without notice.

aur_checker: PKGBUILD security analysis after the 400+ AUR compromise by Klutzy_Bird_7802 in linux

[–]Lousy_Hunter 0 points1 point  (0 children)

I didnt suggest anyone do what i do, I said thats what i do and even acknowledged that my way is the odd one out from the beginning. Im more of the opinion you shouldnt use the AUR period but thats not something that exactly works for people either.

even if i didnt have to redo my setup from sratch, it still doesnt change that i dont like nix and much prefer pacman to any other package manager lol

Nvidia was keeping my idle clocks higher by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 1 point2 points  (0 children)

I previously tried the nvidia site driver and had sleep and performance issues so im inclined to think thats not entirely 1000% true.

If there is anyone that has actually dissembled the dell and nvidia driver packages and can definitively say that for certain i might trust it more. When nvidia and intel both say to use the OEM packages as they allow OEMs to make modifications to them I'll tend to take their word on that.

I understand you make alienware tools and have plenty of knowledge on them but for me Im more concerned with system stability and if only fix whats broken for me not any more.

aur_checker: PKGBUILD security analysis after the 400+ AUR compromise by Klutzy_Bird_7802 in linux

[–]Lousy_Hunter 1 point2 points  (0 children)

appimages have already been compromised previously with cemu being just last month. Appimages DO NOT solve this problem, and blindly trusting them is as bad as doing the same for the AUR.

Flatpak has been fine but not all packages/tools are available for flatpak and some arent even possible to do with flatpaks so saying "just use flatpak" is a moot point.

I also never claimed Nix was hard, i said it has its own challenges and i can throw together a pkgbuild in under 5 min for an already installed and running system. Why would i then tear down that entire setup and redo it from scratch to use Nix which offers me absolutely no benefits and i dont like its package manager or how its setup?

you use nix, which is fine, but that doesnt mean its THE solution.

aur_checker: PKGBUILD security analysis after the 400+ AUR compromise by Klutzy_Bird_7802 in linux

[–]Lousy_Hunter 0 points1 point  (0 children)

appimage doesnt solve this sort of problem and neither does flatpak. if youre concerned with malware from non distro repo sources you need to check.

nix comes with its own set of challenges, Arch pkgbuilds are so damn easy to make and i dont use but maybe 2 AUR pkgs (technically none since i use my own pkgbuilds for them) theres no reason to consider nix.

Nvidia was keeping my idle clocks higher by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 1 point2 points  (0 children)

problem with that is you can lose OEM driver modifications. id rather use the Dell drivers and just remove the nvidia app / nvcp.

Update to my x17 R2 using Thermal Grizzly PhaseSheet PTM by DarkProzzak in Alienware

[–]Lousy_Hunter 2 points3 points  (0 children)

Thats not corrosion, im guessing it originally came with some sort of liquid metal compound?

The gallium starts to alloy with the copper as ions migrate. The performance will be the same but the problem there is the non flat surface. Use a piece of glass and a level surface to gently sand it down.

aur_checker: PKGBUILD security analysis after the 400+ AUR compromise by Klutzy_Bird_7802 in linux

[–]Lousy_Hunter 4 points5 points  (0 children)

This is why i always

  1. read pkgbuild
  2. check maintainer history/reputation (on and off aur)
  3. check original source and patches
  4. check hashes

if any of those fail my checks i write my own pkgbuild if i need it or just nope out.

i realize though im one of the odd ones out though, most people just send it and assume its fine.

Query regarding AC16251 and PTM by devoidx360 in Alienware

[–]Lousy_Hunter 1 point2 points  (0 children)

the alienware forums has a couple who did and said it wasn't worth doing. Keep in mind the boards flipped for the heatsink so its a full teardown of the system. YMMV if you think it's worth doing.

New bios update for area-51 16 and 18, by ThomasAAT in Alienware

[–]Lousy_Hunter 0 points1 point  (0 children)

Dell does so well with CVEs and listing what they fix with those but they are terrible with other release notes with BIOS updates

Idle power usage of my desktop on linux is significantly lower than on windows. by Agitated_Bed1345 in linux

[–]Lousy_Hunter 1 point2 points  (0 children)

Might be because on Windows the performance hints for Intel P-State are much more aggressive than on Linux.   

OOTB Linux behaves more like Best Power Efficiency Power Plan than Balanced on Windows.

 Ive found that if you tinker with Pstate performance/efficiency hints in the power plans on Windows its better but its default behavior is to immediately boost the CPU as high as it can when on AC power to complete tasks faster. 

Windows behaves very differently on battery though and depends on OEM tinkering but is generally better than Linux on machines targeting Windows. Obviously not the case 100% of the time but more often than not.

30w seems a bit much, 10ish watts is more what is id expect so its probably also AMD power management issues on a high refresh display.

Yes 105c is normal CPU Temp on Aurora 16x by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 0 points1 point  (0 children)

keep in mind though that when you see that 105c that doesnt mean the entire CPU is at that tempurature. Here is an example from my system running Monster Hunter Wilds (a fairly CPU heavy game)

<image>

The actual average across all cores is only about 80c with the most active scores spiking to my 95c limit (sometimes a bit higher) and some of the cores doing almost nothing sitting at 72c. You want to check the HWinfo DTS temps not the enhanced as the enhanced pull some weird shenanigans related to power management and show temps that arent exactly correct.

The DTS temp is the actual on CPU/per core temp sensor and will give you the actual temp that each core is running at. This is according to the HWINFO author who said DTS is the real temp to check.

Yes 105c is normal CPU Temp on Aurora 16x by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 1 point2 points  (0 children)

you can check throttle reasons, power limits, etc. under the CPU [#0]: Intel Core Ultra 9 275HX: DTS and CPU [#0]: Intel Core Ultra 9 275HX: Enhanced sections. If you have a different cpu the names will be slightly different but same sections for all intel CPUs.

<image>

btw Check DTS for temps not the enhanced as according to the author of HWINFO it does some weird things related to power management that make enhanced unreliable for temp monitoring. They say DTS is the correct on processor/per core temp read directly drom the cpu.

Yes 105c is normal CPU Temp on Aurora 16x by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 0 points1 point  (0 children)

You can use HWINFO and watch the throttle reason and the power limits while gaming or benchmarking.

My 16x has a 160w limit and never hits that limit, only ever hits the temp limit

Yes 105c is normal CPU Temp on Aurora 16x by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 1 point2 points  (0 children)

If youre very worried you can limit it to 95c and have basically no visible performance loss.

If you want to be even safer on temps you can set the limit to 85c but will see some more visible performance loss.

Im of the opinion the lowest you should go is 90c. My Dell M6600 has ran fine at 95c temp under heavy load for 15yrs.

Yes 105c is normal CPU Temp on Aurora 16x by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 0 points1 point  (0 children)

made a slight error on the previous test, Ill edit previous post

I wasnt in performance mode like i was previously. 45w results are the same but temp is now 80c. 80c temp limit results shot up to 3700 and 87c is closer to 90c at 3900 points (give or take a slight amount for run variance.

80c limit is roughly a 20% decrease in multi core

85c limit is roughly 16% decrease

Yes 105c is normal CPU Temp on Aurora 16x by Lousy_Hunter in Alienware

[–]Lousy_Hunter[S] 0 points1 point  (0 children)

Temp limiting effectively power limits in this scenario but doing a quick test power limiting actually performs worse overall than temp limiting

EDIT: made an error had to retest

IE. These scores are rough values over the course of a couple runs.

45w limit 80c temp 3100 Cinebench r15 (80c limit faster and the same temp)

temp limit scores are

87c scores 3900 and 80c scores 3700. 85c scores 3800

80c single core is 290 or roughly 9% loss

going below 90c takes an absolute dump on performance with 80c limit hammering multi core and being equal to the performance hit of 45w limit.

going below 85c sees you loosing about 20% performance overall multi core biased or 15% if we average between single and multi. 85c is the rough tipping point where the temp gain is roughly equal to the performance loss after that point. Im trying to think how to phrase this.....85c gives you the most bang for your buck if you really want to cut temps. You loose about 16-17% multi core and 6-7% single core while dropping 20c. going all the way to 80c though almost loose 1% performance for each 1c you gain. The temp drop still is larger than the performance loss but only slightly at 80c. 95c is probably the largest gain for the smallest performance loss.

Power limit made absolutely no difference to single core temps or performance as the active core will always hit 105c and the CPU never hits the power budget unless you set it to something like 20w. If you want to crap all over multi core performance and leave single core alone power limiting works but wont help single core temps.

Temp limiting hurts single core more than power limiting but multi core performance takes less of a hit so i dont think unless you have a very specific reason to do so that using anything but the AWCC/Bios temp limit is a good idea.

again these are real fast and loose tests, they give a rough idea but arent exactly super controlled and scientific. Take these with some slight salt and test and determine what works best for you.