buttons not working ally x
Hello, I recently downloaded bazzite onto my ally x
it seems my button mapping is all wrong and i am unable to use any of the 4 settings buttons.
when i go to Test Input in settings
my stand button R1
R1 is Y
etc. any way i can fix the mapping?
thank you
15 Replies
Did you use an old ISO? From before the ally x release date.
The controls are fully supported and tested on the ally x.
Only the deck image has support for handhelds (we have had a few funny people installing the desktop image on handhelds and expected things to work)
@HikariKnight Thanks for the reply. I made sure to select the option with Ally & Ally x + KDE > New User. I've tried it using belana etcher, rufus.
gpart to completely wipe the ssd, select first option for install, im no longer being requested mok (i've entered it several times now).
When i go into settings > test controller inputs, the start and select button registers as r1,l1 and stea,/ qam doesnt register at all.
Hi update here:
I was able to fix it with the following
still odd becuase I must've reinstalled bazzite at dozens of times following the guide.
sudo systemctl enable --now hhd@$(whoami) this fixed it
cat /sys/devices/virtual/dmi/id/product_name
sorry for the inconvenience, bazzite setup script misses some devicesthanks antheas for getting to this while i was asleep.
yeah if you can get us the product name from that command we can add hhd to start up as your ally x might have a different product name than what we have for the ally x
Rog Ally X RC72LA_RC72LA
@Kyle Gospo
im on it
was the
Rog Ally X part of the name returned? or was it exactly like thatsec i will get it again
yes
cat /sys/devices/virtual/dmi/id/product_name returns ROG Ally X RC72LA_RC72LAok thanks, writing a patch now
can you also run
/usr/libexec/hwsupport/sysid and tell me what that returns
it should return ROG Ally X RC72LAyes it is
ROG Ally X RC72LAhuh @antheas no idea why it didnt work on this one as the dmi was already covered
Setup script woes
yeah will check around in it
the dmi is covered though, we truncate the rog ally dmis as asus keep adding more so it cuts off anything after
RC72LA and RC72L, at least for some checks like hhd
and if a specific dmi need special care we just add that to not be truncated
only thing i can think of is that something went wrong with /usr/libexec/bazzite-enable-hhd $USER
everything else looks goodIt's a random bug
It's not fully reliable
Doesn't run every time
F