Probably. It was on by default. There’s an advanced menu. I don’t think any of these things should be affecting this. It will take more troubleshooting time than I have right now. I will use Qubes on this thing, but not now, unfortunately.
How do I check if it is actually the 2024 or the 2023? The specifications of both of them seem the same. Is it possible to put here also the Sabrina Fox’s guide as I don’t know where to find it?
(I did use two different usbs still same issue)
the answer to this, like the answer to most questions, is github
@thimbles_taxidermist GitHub - Sabrina-Fox/WM2-Help: GPD Win Max 2 Wiki/Guide
also listed earlier by @alzer89
check bios settings for hardware confirmation or use live linux version and go to about to confirm you received what you think
also dom0 does pick up on the joystick immediately once I press enter to accept
1 Like
Is it possible this is just a linux kernel issue with supporting newer devices and once I wait a certain period of time the touch screen will work?
Does Qubes often need more drivers to support touch screens? Should I be installing something using sudo dnf install in dom0 to get a better chance of proper support?
I would like to demo test Qubes to see if updates to Qubes make the system more usable. Can I install Qubes to a USB drive and boot from that to test the system or will this be too slow to test such a thing?
Touchscreen should work based on this:
- The fix also allows the touch screen and FN buttons to work.
No USB with 4.2.0-rc5 on Framework Laptop 13 AMD · Issue #8734 · QubesOS/qubes-issues · GitHub
If it’s not working for your then you can try asking the @Kungers in that github issue to confirm whether it works or not.
You can install it on a USB drive but it may be slow depending on drive type. There are fast USB SSD disks available.
1 Like
@wmrom, would it be possible for you to post the output of xinput in dom0?
This will list the devices that X11 has access to, namely, the model of touch screen.
It is likely that the touch screen will show itself as more than one device (usually one for finger input, and one for stylus input).
Once we have that, we should be able to help you get it working 
1 Like
this worked and i don’t know why i didn’t implement this sooner
i forgot my password, but solution!
Also @apparatus or @alzer89, I got everything sort of working…
but my vm-pool and varlibpool or something is reversed and I don’t know why.
If I do a reinstall, can I keep a fourth partition I use data on? Is there any way to switch these tow things? The reinstall could mess up the 4th partition which is not a qubes partition and has other data. (I know it’s bad practice do have Qubes only take up part of the drive.)
i posted this elsewhere but no one is answering. there’s already a thread that’s similar and the conventional wisdom is reinstall. how can vm-pool even get switched with the other pool?
1 Like
Can you explain in more detail what you mean by this?
Or even better, with outputs of what your vm-pool actually looks like?
Of course you can. There’s an option in the installer.
What does this mean? Switch what two things?
You’re more likely to get the answers you seek if you explain in more accurate detail. Don’t assume that everyone knows what you’re talking about.
Context is key
vm-pool is way too small. varlibpool is way too large. i wish i could switch the sizes.
these aren’t typical partitions (they won’t show up in gparted if I use a live OS or they do, but in a strange way)
i don’t understand what they are or how to change their sizes using commands. if i can just use a command to resize them that would be better than an entire reinstall.
Then check some of these out: