Gyro Not Working on ROG Ally
Hey all.
I grabbed a ROG Ally Z1. Works great except for the fact that the system’s built in gyro doesn’t work at all. I have Bazzite installed on my Ayn Loki and it works there. Tried a reinstall and gyro still isn’t working.
When I go into advanced controller settings, the gyro shows all 0. If I hit the “steam” or “…” button equivalents on the Ally, it shows random weird numbers. The internet says that gyro works. Not sure if this is my unit or something that can be fixed on the software end. Any help would be greatly appreciated.
84 Replies
Z1 ally ey?
You might be the first one
Can you go into the handheld daemon settings by double tapping the crate button and check it out?
Probably grabbing some logs would be great too
Wow. Yeah it was cheap couldn’t pass it up. Yeah sure what logs do you need me to grab?
Yes those price cuts are insane
sudo dmesg | fpaste
cat ~/.config/hhd/logs/hhd.log | fpaste
Maybe the path on the second one needs tweakingOk. Give me a few and I’ll run those? Just have to let the doggo out.
Sure
https://paste.centos.org/view/16ee0e61
The second script doesn't work
That's ok 🙂
There's also this concerning message but following the instructions doesn't do anything.
Requires drivers could not be loaded:
- If you are using secure boot, run "ujust enroll-secure-boot-key", then reboot and enter the password "ublue-os" when prompted.
- This message will not appear if the issue is resolved.
@Jan the bmi patch I told you about loaded by mistake, nix and rebuild kernel please? @Kyle Gospo
That's the issue probably
Ah gotcha.
The gyro driver didn't load
And the older one mistakenly did
If you know Linux, blacklist the modules for bmc150 and load the ones for bmi323
But probably the secure boot keys will fix it
I'll push a new 6.7 build with ProjectC and the BMI patch removed by the end of the day
currently trial running BORE under load
Sure thing
Is 323 an akmod or part of the kernel?
I thought it was part of the kernel now
BMI323?
Yep
I believe its part of 6.8
But the current 6.7
Do you patch it in or is it a akmod
Ok. I don't know Linux enough to know what that means, but if I can get back to the secure boot menu on boot I can probable get rid of that message.
You can turn off secure boot for now too
Unless you need it for anticheat in win
Or you can mess with it up to you
patch it in via the
rog-ally-gyro-fix.patch patchNah I dont think I need it. I'll turn it off for now. Thanks. 🙂 Glad I helped you find something.
Then it's the gyro patch
And the drivers load in random order
I'm on my phone can't explain how to blacklist kernel modules
But you make a file in /etc/modprobe.d starting with blacklist <module> and lsmod | grep bmc will give you the module names
If I remember right
Or you can wait 1-2 days
Ok no worries. I'll make my way through it. 🙂 Thank you.
Ok think I did the blacklist. I now have a conf file with this in it:
blacklist bmc150_accel_i2c
blacklist bmc150_accel_core
Now to learn how to enable bmi323
Akmod
If I need to change those lemme know, I ship a few
If it wasn't due to secure boot it will autoenable
After reboot
Gotcha. I'm still getting that secure boot "required drivers" error so I'll have to jump back into the bios to make sure I disabled secure boot correctly.
Oh YAY! Fixed!
Gyro is gyroing. 🙂
greetings
I installed bazzite on my Z1E Ally and almost everything works great/as expected.
Gyro however sometimes work and fails most of the time. I did try updating, restarts and complete shutdowns.
I can‘t replicate when gyro starts to work and when it fails. Most of the time, it will fail after suspend but restart etc. won‘t necessarily work to reactivate gyro all the time. If it‘s working, it will keep it like that until suspending/shutting down etc.
when it happens
journalctl -b 0 | fpastehttps://paste.centos.org/view/7fca7d32
sorry for the delay, kids and stuff
Use the uninstall script on the hhd github
So I need to reinstall hhd then?
It's built in
Oh I hadn’t to install it in the first place…thanks, will try
I don't see any errors about the gyro
@Kyle Gospo any ideas?
New kernel?
After updating it worked again for a few minutes of testing (like sometimes before). Same problem again, not recognising the gyro at all. And while it worked, it had a really stuttery behaviour, so it wasn’t really usable. Mouse (via gyro) kept moving to the upper left corner.
What game
What gyro settings, steam or
Steam input, so I’d say on every game. Behaviour shows in control haptics, too. Tested in FO NV and ME Andromeda. Mostly as mouse output, joystick with same problems.
We haven't had an issue like that before
The ally has been very well behaved when it comes to gyro
Gyro Sync is on?
What’s that?
If it’s a totally random problem, I might just reinstall the OS then.
What settings are you using for hhd? Are you using a dualsense controller with the gyro sync option?
What 3d mapping are you using for gyro?
In steam
DS Edge with and without output sync (tried that before, forgot to mention). Also tried switching between controllers.
Using yaw and roll mostly - if this was your question.
Player space usually has issues
Because of the roll inversion
You need the sync otherwise you get jitters
So after suspend the steam calibration is stuck at 0?
It’s on sync again, weird long numbers for the 1st and 2nd bar. 0.0 for the 3rd. Can observe switching numbers if pressing the quick setting button of the Ally (left one). It even shows something with E+25 then.
Strange numbers became permanent after restart.
so that means the gyro broke
send another log now that you removed the local version
that filled the log with selinux errors
@Kyle Gospo whats up with this
why did the driver fail
@Jan whats the status of the ally gyro patches
That driver is provided by a kmod, it has not changed
why
didnt jan pull in the patches for it
We aren't using the one in Jan's Kernel
Never have
I will remove it from the F40 builds, that is just how it's been for all of F39
how did this happen then
No idea
does the ally have another hardware fault
Would be helpful if a single other person had this problem
I don't want to make assumptions
@Smabe gyro works?
I could switch the SSD to my windows one and try there again, if that would be helpful. I didn’t play alot with the gyro on Windows but when I did, I never noticed any problems.
latest ver?
Yup
that would be great
i cant find error 22 in the source code
i found it
uh dont have the source for the kmod
GitHub
GitHub - KyleGospo/bmi323: BMI323 IMU Linux driver kmod
BMI323 IMU Linux driver kmod. Contribute to KyleGospo/bmi323 development by creating an account on GitHub.
ok so 0 clue
try rolling back to 2 weeks ago or using windows
youre the first to have this
could be the kernel, could be your device
but the gyro is busted
It worked on Windows
Obv I’m not that familiar with Linux that much. How do I roll back? I might also just reinstall then I guess?
no theres a command
and a guide for it
you can choose from all images the last 90 days
Found it, will try - thanks a lot for your help and effort!
@Kyle Gospo theoretically how do we disable the kmod and/or the kernel module
jan has included the proper patches for the kernel
remove the line installing it
but I'm not doing that in F39
it's gone from F40
without that
you can't
cant you force unload it temporarely
you cannot, it's part of the image
you'd be unloading the whole module and not just the kmod
yeah
what does whole module mean
bmi323
yea
all of it needs to be yeeted
I'm saying if you unload that, it's not gonna load bmi323 from the kernel
it's gonna unload bmi323
no gyro
if you uninstall it will it load the one from the kernel
yes, but the end user cannot
I'd have to build a whole new image of F39
cant you layer it
you cannot remove something included in the OCI layer
ostree limitation
i thought you could
Rollback didn’t help, so I went with a fresh install which works flawlessly now.
Good to hear. Hopefully this bug will be fixed with the new kernel next week
I rebuilt the ISO with the last image build
if he reinstalled, he's on the current stable kernel
I think this bug is randim
But removing the kmod will hopefully fix it
I used my already prepared drive from 1-2 weeks ago