I'm experiencing a frustrating problem with Bazzite on my 2-in-1 laptop. Please help!
My laptop is a 2-in-1 convertable where I can switch it between laptop mode and tablet mode and comes with accelerometer and gyro sensors so it can automatically shift orientation.
Whenever I do a fresh install (and reinstall, trying to fix this problem) of Bazzite, Bazzite detects my laptop's sensors. But after I install some system update via Bazzite portal and rpm-ostree update command, Bazzite no longer detects my laptop's accelerometer and gyro sensors. And I'm getting ready to install Bazzite onto ROG Ally gaming handheld and I'm worried that this problem might show up there too and I have some games that need the gyro on my ROG Ally.
Why is this happening? Is this happening to anyone else too? How do I fix this?
113 Replies
why are you updating with rpm-ostree tho?
Because I tried to Google the problem and came to mistakenly think it might help.
there should be an application named system update
system update (aka topgrade) also runs rpm-ostree to update system btw
keyword also
topgrade is a utility that runs these updates. note them rpm_ostree = true line
...riiiiiiiiiiiiiight?
as in does it run anything else that might fix this
im actually not sure if running topgrade will fix sylia's issue, because as far as i can see most packages relating to hardware enablement exists at the system level, hence updated via rpm-ostree
But after I install some system update via Bazzite portal and rpm-ostree update commandso well, topgrade runs also don't help solve her issue
@amel @Mandarinoo After those updates, I reboot my laptop as you do every time you install an update. And once my laptop is rebooted, the accelerometer and gyro is gone and the autorotate option under Display Settings is gone.
can you post
rpm-ostree status -v?Not at the moment, I'm doing some yardwork while my system reinstalls Bazzite again. This time, I'm not going to install anything from Bazzite Portal and rpm-ostree update command and see if accelerometer/gyro support stays intact.
okay, so here's my suggestion of what you can do if you decide to reinstall:
1. install as usual
2. upon booting for the first time, immediately go to desktop mode and pin the newly installed deployment by running
sudo ostree admin pin 0 on the terminal - here's the exact docs header
3A. if you're happy with the state of your fresh system (it will be behind by a few builds - current bazzite:stable is on OS version 42, but isos are still OS version 41), you can keep it that way. if you want to be able to run normal app updates (but NOT OS/rpm-ostree updates), you can temporarily do this:
3A1. run sudo nano /etc/ublue-os/topgrade.toml
3A2. paste the following line in the end of the file:
and save the file + exit. this should not run the rpm-ostree updater whenever you run the system updater/topgrade from the app drawer. remember this change for eventual removal in the future.
3B. this is if you want to try to understand what the issue is. after pinning the deployment, you can run the system updater/topgrade as usual and see what packages are updated. before hitting R/reboot or Q/quit on the topgrade window, you can scroll up until you see a list of updated packages.
when you reboot, your system will be on the newest OS version 42. you verify if the gyro and accelerometer support is working or not.
if they're not working, you can reboot into BIOS/UEFI (such as using ujust bios command) choosing the Bazzite UEFI entry and booting from there. this should allow you to access the grub menu and boot into the pinned 41 deployment.
^ under normal cases, you can rpm-ostree rollback to get back to the previous deployment. but due to fedora/upstream changes in 42, it is not possible to rebase/rollback from a 42 deployment to 41.
you can also set your grub to be set to always show. this eliminates the need to go to UEFI to go to grub menu. upon fresh install, you can run ujust configure-gruband choose Always Show Grub
this is best done right after your fresh install or before upgrading to 42, if you plan to do so
sorry i can't give a direct solution, troubleshooting suggestion is the best i can do atm!Okay, I'll try later in the day.
@amel @Mandarinoo UPDATE: I just reinstalled Bazzite 41 again. The accelerometer and gyro sensors showed up again, which but this time I didn't install anything from Bazzite portal nor did I run rpm-ostree update command. Instead, I only updated Steam packages and did nothing else and immediately after Bazzite reinstalled and rebooted my laptop. Accelerometer and gyro sensors still dissappeared again after reboot. 😥 So it might not have been the rpm-ostree update command or something I installed from Bazzite. I don't think it's Steam updates either, unlikely.
So what could be causing my issue? A bug in Bazzite version 41?
I have no idea :glorp:
I'm relatively new to this too :)
something is probably malfunctioning (like a service or something), but i can't tell - don't have a device to check with unfortunately
but i almost want to think that on the Ally the problem might not exist. at least i don't think i've seen anyone report
@amel I still haven't tried your steps yet, but I'm willing to try if you still think it may help.
+ im inclined to believe there are more handheld users than there are 2in1 users
actually can you clarify what you mean when you said you "updated steam packages"?
Steam, you know, the gaming platform? As soon as I boot from after Bazzite reinstall, it runs on its own.
alright that clarifies it. i think then there could be something that's not correctly starting up with the system then, but i don't think i can help pinpoint further - sorry!
What laptop is it?
If an update makes it so your sensors are no longer recognized, it needs to be fixed
you're sure a rollback fixes it?
we make sure the gyro on the ally works great
if you send a log we can check the gyro on your 2-in-1
yeah okay i missed the bit where you reinstalled and rebooted without updating your bazzite version
@𝓢𝔂𝓵𝓲𝓪 𝓖𝓻𝓪𝔂 can you do
rpm-ostree status | fpaste (or a screenshot)
maybe it auto updatedI don't know how to generate a log.
journalctl -b 0 | fpastedamn you're fast antheas
Send it to where?
that command generates a URL
post it here
Okay.
But I have another idea. My current installation of Bazzite is KDE. Could there be something about KDE that my laptop's sensors don't like? What I download and install the GNOME version or Bazzite?
sensor data is only consumed by DE's, not managed
probably wont make a difference
I just woke my laptop back on but everything is upside now
And it won't correct itself automatically...
that must be the sensors acting up
It never did this when it was still on Windows two days ago.
can you force manual orientation?
otherwise try rebooting
Yeah, it's right side up now but I had to do it manually.
Reboot? Let me try.
no no no
dont have to
i thought maybe reboot to fix screen orientation
but if its fixed now we just need the logs
journalctl -b 0 | fpasteWow! The log is really long!
Do you want me to post a specific segment here or something?
no, just the URL it outputs when you post the command
oh okay
https://paste.centos.org/view/a09b9d88
What specifically am I supposed to look for in this log?
your device has an amd sensor fusion hub
6.14 has some fixes for that
try testing
brh rebase testingOkay
Okay, it's running
6.14 of what has fixes for my AMD sensor fusion hub?
the kernel
Okay, so I'm running the brh rebase testing command. It's looking just like when I ran the rpm-ostree update command.
yes
then reboot
I thought I tried that last night.
yes, but this on a different branch
youre udpating to the testing branch
with the 6.14 kernel
Okay. it's almost halfway there.
What's the current version of my kernel?
6.13
you can find it in the log
Okay.
top line
anyway, when you reboot it should be 6.14
It's almost done.
It's sitting at 68/69
sometimes the output in console is a little delayed and its already deploying 😛
I mean it completed 68/69. I don't see 69/69 starting yet.
Oh, staging deployment now.
That's done.
reboot and hopefully its fixed
now it says to run systemctl reboot. Is that different from normal reboot?
no
systemd owns all of us
okay it's rebooting.
I'm sorry. I'm kind of new to Linux although I had some brief experience with Ubuntu so my Linux knowledge is limited.
thats ok
maybe it works, maybe it doesnt
remember to rerun the command with stable
average kernel developer
Nope the problem still persists.
screen autorotation kind of works at best in my experience
Just rebooted the autorotation option disappeared again.
It reappeared when I woke up the computer from sleep about 30 when everything was upside-down (picture above)
sounds like average amd sensor fusion hub experience
on my lgo even on windows it causes issues 😂
yes
sounds like your device has 2 sensors as well
looks correct?
has accelero and gyro
I'll be right back
the fixes were for 2 in ones
if your 2 in one broke
well
not much of a fix were they
What if I try installing the GNOME version of Bazzite?
just disable autorotation and live with it
it started working a few months ago anyway
maybe gnome is better
GNOME could be better
if sensors are recognized at least
looks like they are
my initial thought was that your sensors weren't recognized at all, then it won't matter much
but if they do, GNOME could be better at using sensor data
You'll have to reinstall to try it
or use live iso maybe?
of fedora?
could save you the trouble of reinstalling again
Worth a try, I think.
I don't think it's hardware that's damaged, but more likely driver issues? I could maybe live with that, assuming there's going to be fix. But really don't want this problem and when I install Bazzite on my Ally. And I don't want to go back to Windows, especially on my Ally.
oh its driver issues
and no its not a problem on the ally
could fix it, but probably no.
That said, a few issues I've been having, like sleep not working properly, were issues I've only had on KDE and not on GNOME. (Or so I thought... Now it doesn't work on either. I'm tired, Boss.)
I'm going to try GNOME. I'll post about the results here when it's done.
its just that the fusion hub driver is not very mature in its current state. It's buggy at best, and broken at worst.
So it will eventually get fixed?
probably
but when? idk
someone has to report the issue, someone has to try and fix it, and someone has to get it merged in kernel
which is not always very easy
Glad to hear that isn't a problem on the Ally at least. Like I said, I don't want Windows on there anymore. So many annoyances from Windows on the Ally.
the ally is a popular device, so issues are more likely to get reported and fixed 😛
and we got mr antheas here doing gods work on all these handhelds
my ally is sitting next to me
I have to disable the fusion hub in task manager to fix virtual keyboard in windows on my LGO 😐
so not even on windows it works well
I never had that issue on Windows on my laptop.
Oh, you're talking about the Legion Go.
Yeah, its also very device dependent
the bugs you get is random
Does AMD officially provide support for Linux?
Yes
@𝓢𝔂𝓵𝓲𝓪 𝓖𝓻𝓪𝔂 Have you maybe checked for any BIOS updates for your device btw?
That could solve some issues too
I see your device is fairly recent
the driver was not official originally
the legion go has controller gyros
the screen one is trash and just for the screen
No, I have not updated my BIOS. How would I do that from Bazzite?
ally has usb flashing
for your laptop its probably just a fat32 formatted drive to update or a windows utility if you still have that installed
I think I do, not sure.
Let me boot into my bios
@𝓢𝔂𝓵𝓲𝓪 𝓖𝓻𝓪𝔂 https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=md3g7&oscode=w2021&productcode=inspiron-14-7435-2-in-1-laptop&lwp=rt
it seems like they're just security updates, but either way never a bad idea
looks like it can only be updated from windows. Rip.
Looks like my BIOS is outdated by 1 version. Let me try updating it though I'm not confident that will help. My BIOS never had options regarding sensors.
Bios updates often include other bits of firmware code that might help fix (or introduce, no software is without bugs) issues.
firmware for that ships with bios
I can't get the bios to read the downloaded new firmware.
The only way to update is downloading that .exe file and running it in real windows environment. if you don't have that, don't worry about it. probably won't change much
well there's also some bios recovery file but i have no idea how to use that. never had a dell
I'll just try the GNOME version.
It's def worth a try. Might handle rotation better
Let me know how it goes.
sure
@CheckYourFax @antheas @Mandarinoo I have not installed GNOME Bazzite yet, but I'm starting to have a feeling that this is a startup issue. When I booted after last install, it detected my sensors correctly and it worked. But then when I rebooted, the sensors are disabled. But then if I boot it again, the sensors come back.
theres also a selinux bug i think with hid sensors
but it wasnt in your log
It being a kde bug is not outside the world of possibilities
According to logs sensors start up fine
So that's not the issue
So its somewhere between that and your desktop environment. Could still be a lot of things but oh well
I was kind of worried that maybe the hardware may have been damaged some how, but I think we can rule that out 😅. I'll try the GNOME version once I make the USB bootable disk for it.
It's an expensive laptop and I did my best to take good care of it. It be disappointed if it was damaged.
its not damaged
i know the bug you have
i dont know how to fix it
but i know of it
Hopefully this conversation will shed some light on this issue so there will be a fix for it. What's the best avenue for reporting this bug?
your bug is that after sleep your screen turns upside down
and that sometimes after boot screen autorotation does not work
perhaps both of them are kde
ima be honest, its a pain to report
Okay.
Well, I'm out of ideas on how to fix this other than trying the GNOME Bazzite so that's what I'm going to do. I'll post about it here once I get a chance to install and try it out.
thats the only way
But what's the GNOME version like vs the KDE version?
gnome is completely different
gnome is like macos and kde is like windows
Okay. Cool.
@antheas @CheckYourFax Not working. Bazzite is not even detecting the sensors in GNOME. Reverting to KDE. At least it works sometimes. Just buggy.
Thanks for trying to help anyway.
I'll just use the KDE version and hope that the bug gets fixed hopefully sooner.