Bazzite 3.0 New install - GPD Win 4 6800U - Gyro not working
Hi! New user here. Just installed bazzite, almost everything working perfectly apart from external screen not working in desktop mode (not so important) and gyro not working. I have been trying to investigate this last one. Tried removing conf for HHD, rebooting, played with several options of HD to no avail. On a fresh boot, calibration values in Steam show either 0 all of them or some weird numbers, no reaction to movement. Doing a lsmod I found the bmi160 module, shouldn't I have the bmi260 instead? any idea how to troubleshoot this further?
EDIT: this is the dmesg output for the bmi modules
[ 6.300967] bmi160_i2c i2c-BMI0160:00: supply vdd not found, using dummy regulator
[ 6.313653] bmi160_i2c i2c-BMI0160:00: supply vddio not found, using dummy regulator
[ 6.315550] bmi160_i2c i2c-BMI0160:00: mounting matrix not found: using identity...
[ 6.317966] bmi160_i2c i2c-BMI0160:00: Error reading chip id
[ 6.319329] bmi160_i2c: probe of i2c-BMI0160:00 failed with error -121
44 Replies
GitHub
GitHub - aarron-lee/gpd-win-tricks: Info on running linux on GPD Wi...
Info on running linux on GPD Win devices. Contribute to aarron-lee/gpd-win-tricks development by creating an account on GitHub.
Try the gyro fix
yeah, I followed your guide, thanks a lot by the way. Giro fix installs succesfully but has no effect. The issue is present imediately after a fresh boot in any case. Based on the dmesg output above I think I might have the wrong module installed? Wouldn't I need a module for the bmi260?
Let me double check on my win 4 too
Looks like I might need to update the gyro fix for Bazzite 3.0
sorry, I'm maybe getting something wrong but I just checked the code of your fix and I see it's modprob'ing the bm260 modules ... I think the problem is that I don't have these modules ... 🤔
Yep, looking more closely, looks like it's definitely something else
So for more context, the win4 actually has a bmi160. My understanding is that due to some id mislabeling on gpd's part, it was misidentifying as a bmi260
I'm assuming maybe there's now an upstream kernel fix for this somewhere
But I'd have to investigate more later, currently traveling
no worries, I will do some more googling in the meantime, thanks!
Worst case scenario, temporarily rollback to pre-3.0 Bazzite and pin
can I rollback to a previous version even if 3.0 is the first version I installed?
Yep, definitely possible
Check the rollback documentation
Universal Blue
Updates, Rollback, and Rebasing on Bazzite
Yes it is true for all of them, however I mostly focus on documentation on the Bazzite image which is why it’s here. Desktop images of Bazzite follow the same automatic update style that the main images follow. However, there’s also the -deck images that do not follow this which is why I wanted to differentiate between them. As for pinning, w...
It's bmi260 when you get the chip id error
@Kyle Gospo 260 kmod is missing
Make sure if secure boot is on you enrolled the mok key
Or that
could have sworn we agreed all the gyro kmods were no longer needed
and they should be removed
I'm not using secureboot
160, 323 yes
150 yes
I will restore 260 later today
260 no
thanks guys, so I won't rollback and just wait for an update, right?
yup
should just start working later on
Sorry, just double checking, I got an update this morning. Dmesg still showing the wrong id error for the BMI160 and gyro not working. Updates come via topgrade, right? Anything else I need to do?
@antheas I restored 260 like you asked
Do you want me to restore all three?
No just 260 is out of tree right now
Well it's in and seemingly still broken
So it should work
It should load
I will try again later this evening, I updated and tried again this morning but it didn't work. Dmesg gave the same message like in the first message of the thread
It should
But below it there should be an extra 260 message
the module is not there I'm afraid, checked again dsmeg output and a 'lsmod | grep bmi' only returns entries related to the 160...
Something went wrong then @Kyle Gospo
Like I said, we probably need those modules
Bmi160 conflicts and loads incorrectly without the patch
It doesn't conflict
That's how it is supposed to work
It returns enodev after the chip id check fail
And lets the 260 load
And lets the 260 load
Do we know for certain that patch is in fsync 160?
To exit I mean
160 does not need a patch
150 never needed a patch
I did before, that's why I was building a kmod
It was misinformation
Interesting
We found that out when the patch was going to go upstream
And I forced them to check it again
@kikeminchas Can you
modinfo bmi260
And see if we get a return?'modinfo: ERROR: Module 260 not found.'
Huh? That should say module bmi260 not found
modinfo: ERROR: Module bmi260 not found.
All right, that's helpful
Give me a bit I'll figure it out
my fault, typed it wrong
All good, just needed to know
I just got an update this morning, got the bmi260 module and the gyro is working 🔥 thanks a lot!