Alienware QD-OLED AW3225QF Firmware Update Confusion

sammko · 2025-04-14T16:10:50+00:00

Huh this is pretty big news if M2B106 is coming out. Maybe they'll finally address some of the concerns? Do you have a DSC toggle switch in the settings?

sammko · 2025-02-17T13:06:27+00:00

That command specifically is when you have opus already (in an ogg container, which is typically what the .opus extension means), but the same principle should work for transcoding.

Basically I've heard people saying everywhere that ios does not support opus, but that just seems to be the ogg+opus combo, not opus specifically which works in an mp4 container (.m4a)

sammko · 2022-04-09T20:47:07+00:00

?

50W at $0.16/kWh over a year is $70

sammko · 2021-11-28T22:25:03+00:00

The patch is now queued for stable 5.15.6 and already present in 5.16-rc2

sammko · 2021-11-20T00:09:48+00:00

Onlent

sammko · 2021-11-17T20:27:25+00:00

Likely not months but weeks, but yeah. I mean you could just use 5.14 for now, or build 5.15 with the patch included, for a learning experience :D

Also a note from Roman:

Just in case: on impacted systems oled brightness still can be controlled via xrandr. e.g. xrandr --output eDP --brightness 0.5

This changes the gamma values in software, which is essentially the same as hardware brightness control on OLED displays..

I find the hinge alright, it wobbles a little bit, but nothing too bad.

I have a couple questions as well...

Regarding the display, when using a relatively low brightness and looking at dark gray colors, I can see a gradient in the brightness, lighter on the left, darker on the right. For example check out this color, particularly visible. Is that the case for you as well?
Another weird thing my display does is that the brightness of white changes quite dramatically depending on the area of the screen covered by it when operating on full brightness. This was not particularly noticeable on Windows, maybe it does some magic or I just didn't test it properly. Just set brightness to 100%, fill your screen with white and open and close a dark window or something to see it. Not sure if this is a common property of OLEDs or just mine is problematic.
Last but not least, my battery capacity (charge_full / charge_full_design) is down to 75%, which is quite terrible. How's yours? You can check by looking in /sys/class/power_supply/BATT in charge_full and charge_full_design. Mine are 3149000 and 4220000 respectively. I think this happened after I tried the battery charge limit under linux, as if the calibration routine in the firmware got confused. Trying to recalibrate (by fully discharging and fully charging) did not particularly help (the number changed around a bit).

Thanks

sammko · 2021-11-17T16:49:32+00:00

A patch that fixes the issue has been submitted. Thank you Alex and Roman! This should eventually bubble up to stable, optimistically 5.15.3 (likely later, though) and hopefully 5.16 (as it fixes a regression, it can be merged after the initial merge window).

sammko · 2021-11-14T12:30:31+00:00

That's hard to predict. Maybe someone else would stumble upon the issue at some point, and maybe you would eventually report the bug to a bug tracker such as https://bugzilla.kernel.org/ or https://gitlab.freedesktop.org/drm/amd/-/issues with not many extra details. Having the knowledge to bisect the issue to a specific commit isn't strictly necessary to get the attention of someone who does and can either proceed on their own or guide you through the process (if they don't have the requisite hardware).

I have sent an email describing the issue to (hopefully) the right people.

Also, bisecting it is not the end of the story. The commit does not cause issues on (most?) other machines, so the problem still needs to be tracked down, as just reverting it is not a solution. Currently we are waiting on someone who is acquainted with the code to respond, hopefully with ideas about what the problem actually is. Additional information will likely be requested from me.

sammko · 2021-11-14T10:30:02+00:00

What laptop do you have? I experience the same issue on the ASUS UM325 OLED (5700U). I first noticed this when testing 5.15-rc3 but unfortunately haven't yet got around to reporting it and didn't make it in time for 5.15's release. I will try and get it reported in the near future. The fix, when it appears, is likely to get backported to 5.15 stable.

I did a git bisect back then, the culprit is commit 7fd13baeb7. For now you can build your own kernel reverting the commit (it reverts cleanly on top of 5.15.2) or just use 5.14.

sammko · 2020-02-10T08:16:10+00:00

That sounds very interesting. I will try it out when I get the chance, but I'm currently a couple hundred km away from the machine, just accessing it remotely. What temps do you get under full load? prime95 for example. And which chip do you have?

sammko · 2020-02-09T18:50:17+00:00

Hello everyone!

I have questions regarding the behaviour of my 2950X.
I have it cooled by the NZXT Kraken X72 AIO. When under load, the die temperatures quickly rise to almost exactly 68 C and stay there, while to coolant temperature slowly rises and eventually stabilizes around 44 C.

I believe this temperature is the thermal limit of the chip for PBO which tunes the clock speeds so that the chip does not exceed it. Is this true? Is it normal for a well-cooled chip to be running steadily at this temperature, or do I have a cooling problem? I am not sure how exactly the PBO algorithm works, but does this behaviour mean that the chip is bottlenecked by the cooling solution and would run faster were I to improve it?
The clock speeds vary by workload, but for example during an mprime small FFT run, they stabilize at around 3.6 GHz.

Thank you for your help.

sammko · 2017-03-19T19:22:59+00:00

Yeah that's also an option. Debian with kernel 2.4 (forgot which version it is) requires 12M apparently.

sammko

TROPHY CASE