GPD WIN Mini 2024 display rotated in game mode
Been trying to get the latest Bazzite stable to run in game mode, but the screen is rotated. In desktop mode there are no issues. The 2024 Win mini has the same display as the Ally, but the fix for the Ally doesn’t work for me.
109 Replies
GitHub
Don't rotate GPU Win Mini 2024 7640U display (#1351) · ublue-os/baz...
The GPD Win Mini 2024 edition has a native landscape display. This means it doesn't need to be rotated like the 2023 edition.
They recently released a 7640U version, which is not being d...
update to latest, and enter:
rpm-ostree kargs --delete==eDP-1:panel_orientation=right_side_up
should be good after thatI’ll try that right now. I rebased it earlier this morning with no changes, so I hope this will work.
for f in /sys/class/dmi/id/*; do echo "$f:"; sudo cat $f; donealready patched by another user
thankfully
seems not
oh he has t odelete the quirk
it only doesn't add the karg
if it was alreadfy added it's gotta be deleted
well, have it remove the karg too
hes on stable
yea it hit stable last night
No key found
get the codes
rpm-ostree status
an then run what antheas saidNothing is happening. It just creates a line I can type in.
I’m in the 07/12 build
rpm-ostree status | fpaste
rpm-ostree kargs | fpastecopy it again
it should print a bunch of stuff
It did print a bunch of stuff now. I made a typo.
add an fpaste at the end if you cant copy it
ok now the other 2 while i look into it
what cpu does your unit have?
fatphobic?
probably fingered
fat
Discord pls…..
ok so kargs did not update
for some reason
otherwise it would have stripped the previous build
hey you typed it
admin priviledges smh
Is there any way to write over the kargs on the user side?
yeah this but written properly
lol.
@Kyle Gospo you dont remove the existing quirk
should be an elif ":G1617-01:" =~ ":$SYS_ID:" remove if exists
whats the CPU of your unit
8840u
|7640U isnt there a CPU unit with this that needs the quirk?
why did you add it into the selector
or the last years model only had a 7840u
Only 7840u available for the 2023 model.
in any case, does it work now?
Not sure what command I need to do to fix the quirk.
rpm-ostree kargs --delete=video=eDP-1:panel_orientation=right_side_upStill No key found
video=eDP-1:panel_orientation=right_side_up
it's right there in your kargs
if it's not found you are typoing itload the discord in your handheld and copy the commands
i had 2 =
hehe
I was just about to say that. My phone is in portrait so I can’t tell where the spaces are sometimes. lol
That’s what did it. It’s updating now.
The orientation has been corrected now! I’ll check the unified refresh rate real quick too.
if anything is wrong with refresh rate, send what you expected to happen
Will do thank you both for your help.
Basically vrr did not work correctly for me. The frame rate was inconsistent and it would always run at 120hz. I was told to disable unified refresh rate for it to work, but there was no option for that since it got removed.
how about now
Still doesn’t work on my end sadly.
force compositing vrr quirk
where is that applied
Developer options
I have it on in the dev options
why does vrr need user intervention?
Never understood that myself. My guess is that it’s only applying to the steam deck edid.
It shouldn't in the latest versions
That was a temporary workaround for a bug that we patched already
But it's still worth testing
I’m gonna restart again to check
Is there a way to reapply the fix?
You haven't ported a lot of quirks to ally x
The only thing that you can do is toggle the force composition on, if that didn't fix anything for you turn it off
Which ones are you talking about?
Gnome icon
Actually that's it
Cool, I'll fix it
I can shed a little more info on the issue. When in QAM adjusting the frame limiter with vrr on will always show 120hz in the parentheses. In game play, if I set it to something like 40fps with vrr on. It keeps floating a little above 40fps and can look choppy.
Did it work with the previous gamescope?
Didn’t really test that due to the rotation issue on slim
I can definitely rebase and apply the fix on it if you want me to test it.
VRR will not work below 47hz most likely
It's not designed to go that low
60 would do something similar.
It would float around at 70fps and be choppy with vrr on.
I’m gonna try slim again to see if it works. I’ll post my results in a bit.
done
So it initially works on bazzite Slim, but it keeps updating the kargs and reverting it back.
Bazzite-dc has the fix
Is it in your container?
GitHub
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
That with the rotation fix worked. It’s 99% perfect. The one thing I need to do is change the range of the vrr. It’s between 60 and 120 and I want to lower 60hz to something else.
But normal bazzite 60hz works too right?
None of the GPD devices have VRR enabled
one of them has a 40,60 range
I think the problem here is we don't have gamescope configured for this specific display
He could do a vrr range before
He's using the other build that's older
regardless, if it's not defined here then who knows what values gamescope is using
It does. No issues so far.
no
ADAPTIVE_SYNC=1
no or potentially wrong range
not marked as an external display (needed for VRR)So you don't know if it's better
I have the vrr option available for some reason, but enabling it causes the same issues.
There you go
Let's fix the touch gestures and drop the older builds finally
Oh this is on slim btw. I can revert back if needed.
probably because it's not marked external
like I said, this display isn't defined in gamescope-session
so who knows what gamescope is doing here
obviously the wrong thing
Yea that’s probably the issue
I need a good way to detect your specific hardware
did we get a full dump of all DMI info?
60hz is the minimum
for your hardware
I can dump it if needed. Do you need me to go back to stable for it?
you can fps limit lower, but refresh rate is 60 at a minimum
nope
I see. I thought the ROG can go lower, and since they use the same display…..
ROG is 40-120
GPD Win MIni 2024's site says 60-120
It’s most likely inaccurate.
I can test with lower refresh rates. Worst case scenario I use my monitor to revert.
Hmmm. Didn’t think that was true.
for f in /sys/class/dmi/id/*; do echo "$f:"; sudo cat $f; done
need the output of thisGo find the dmesg
Remember he's on the April build now
ok that sucks
once again it looks like nothing unique about the DMI info?
@Smash and Crash run this:
if ( xrandr --prop 2>$1 | grep -e "1920x1080 " > /dev/null ) ; then echo "it worked"; fiambiguous redirect
I might rebase back. I kept thinking this is just like the ROG display with lower refresh rates available. Now knowing that 60 is the lowest, I think it should be fine.
It's not if it's vrr
If it's vrr it's around 47
Less with framerate compensation I know nothing about
I see. I'll stay on slim for now then. Just let me know if anything needs to be pulled or tested.
You didn't explain what's the difference between latest and that
Both work at 60hz
oh my bad. It still shows 120hz on latest, but the frame limiter does work if VRR is off.
Does?
If vrr is off the only framerates are 60 and 120
With frame rate, turning the vrr off will run properly at 30, 60, 120, or any one of them on the slider. The refresh rate will always stay at 120hz though.
Lastest?
Latest?
Yep
latest stable
latest stable does not have your display marked as external, so VRR behavior is unknown/undefined
let's try again when I have this handheld defined in gamescope-session
sure thing. Just ping me whenever it's ready.
you didnt transfer all the quirks?
hm?
how come the build from 2 months ago works
idk lol
Fix is to detect the landscape display and do the same thing we do for the ally
potentially
you already have a quirk for it with the cpu
why didnt you centralize the quirks
that's a rotation thing in bazzite's kargs, totally divorced from how chimeraos gamescope session works
there's no quirk for this handheld in there
and no rotation value needed
i know
why does this matter?
fork
so the CPU works for karns and not for the session?
*kargs
I'm going to rebase to stable. I'm going to run more tests to get more accurate results.