Screenshot.jpg
I just installed MX 17.1 on a brand new 10.1 inch HP X2 210 G2 windows tablet over the weekend. It's commonly called a 2 in 1.
It has an Atom x5-Z8350 with 4 cores at a max speed of 1.92 Ghz. 4GB of ram (see attached screen shot). 120 GB of mmc storage. Detachable keyboard. A multi-touch screen, and a pen. It came with Windows 10, but I bought it with the intention of wiping it and installing MX.
I knew Win 10 would be unusably slow for me, but I booted it up for curiosity. Cortana started yakking at me, telling me she's always listening, and asking for personal information because she wanted to send my details to HP, Microsoft and McAfee to set up accounts for me. Uh... Nope. It was very sluggish, but I think that's because I'm used to I'm used to snappy Linux laptops. Anyway, GParted promptly got rid of Miss Cortana, and all the people she wanted to "share" me with.
Bluetooth (HID and audio), touch screen, pen, keyboard, HDMI monitor, USB audio & network adapters, Wireless 802.11ac, USB network tethering to my cell phone, Thunderbolt 3 dock (USB sticks, audio in/out, and Gig Ethernet - tho HDMI requires displayport which I'm not dinking with)... 90% of everything is working great, but I admit it took some tinkering.
It is much, much more responsive than the Win 10 it came with.
It has a couple of glitches that I'm still working to solve:
1) Audio is an Intel SST Audio / Realtek RT5640 variant, and while MX has the intel firmware already, it didn't have the requisite Alsa UCM files. I found those on the inter-webs and installed them. When I run MX and Antix from a USB stick (with the firmware and UCM files), it correctly recognizes the card as bytcr-rt5640. Audio is mono and comes only from the left speaker. Headphones don't work at all. But the same files installed on the tablet itself -- MX doesn't identify the card as bytcr-rt5640, and built-in audio doesn't work at all. (Tho, of course I still have bluetooth, USB, and Thunderbolt audio to play with).
2) Power management is wonky. It always thinks it's plugged in. It can't sense the battery so it can't display the charge state. Conky battery info is blank. So, I have no idea how much battery I have, and MX power management is obviously not conserving battery when it should.
These problems are inconvenient, but they're not crippling. The battery is the most annoying, but I'm confident I'll get them solved with the help of the MX forum.