r/linuxhardware • u/Zancuno • 2h ago
Discussion Linux journey on a DT Research DT311
For Preface, I am still a new Linux user (1 year). I am not a certified programmer. I am used to digging in the web for answers. This current journey is something I struggled to find information on and thus feel like I need to contribute it to search-ability.
First I will introduce you to the device in question before story time.
This is the DT Research DT311 base model tablet (DT311bu according to firmware). What even is DT Research? Good question, I didn't know either.
DT Research is an enterprise company that makes devices for medical, science, military, government, and business. This is one of their "rugged" tablets designed for function and durability.
The DT311 has a magnesium chassis with ABS plastic pieces. The cooling fan/vent is water sealed, a seal is inside the two halves of the tablet to keep the elements out. The screen is not your smash-able iPhone screen.
The gimmick features of the device are:
- It has a full slot smart card/payment card reader
- It has a NFC chip reader
- It has a sim card slot for cellular connection
- It has a hot-swappable battery that is either 45 watt hour or 60 watt hour that you can have spares charging. A smaller internal battery will keep the device on while doing the swap.
This is where mine ends but some models have GPS functionality, and barcode scanners.
The hardware people care about:
- Intel i5-5200u CPU at 2.2GHz - 2.7GHz turbo. Intel Integrated Graphics, 2 cores, 4 threads (i7-5200u models exist somewhere out there).
- Uses mSATA (not m.2 or NVMe) storage, mine 128GBs (64GBs -512GBs, with chinese manufacturers allowing up to 2TB as the standard has been left in the dust) with 2 storage slots, leaving one open for upgrade (panel with screws to reveal).
- 16GBs of soldered DDR3 RAM (models can range from 4GBs to 16GBs, with 8GBs the common).
- x86 Windows based Tablet with an InsydeH20 BIOS that is modified by DT Research using the divided up BIOS menus you'd see on a Microsoft Surface tablet.
- Uses an eeprom chip to retain BIOS data with no CMOS battery.
- eGalax touch screen using EETI drivers that transmits electrical signals between the eGalaxPen (AAAA battery) on close contact to transfer data instead of connecting via Bluetooth, USB, or Network.
- A single audio jack behind a side door for plugging an aux jack into.
- A single USB port inside the side door.
- A power port inside the side door.
- 11.9" screen at 1920x1080p
-------------------------------------------------------------------------------
Story time now
I have been looking to replace my 2016 iPad Pro (2.16GHz) for a long time now, it only has 2GBs of RAM and that has caused me working on any intensive art project to come with lag or crashing, demotivating. I don't earn a lot, and iPad prices are overly absurd these days, even worse now with the current price hikes. So I have been hunting for over a year now, just window shopping. Android just doesn't have what I want program wise (being able to draw directly on 3D models instead of a flat texture is rare and ProCreate gives that), so having to give up on the apple ecosystem, I looked at x86 tablets and 2-in-1 laptops.
My budget was only $200USD and filled with hopes and broken dreams looking for someone to sell off a beloved device that isn't busted. So looking up x86 tablets deep in web searching, I ran across something I didn't know existed, rugged tablets.
A little bit of digging and I discovered that DT Research tablets are being sold in bulk by resellers and at very cheap considering the specs they give. I bought mine for $152USD wanting that 16GBs of RAM. Knowing it was integrated graphics and it would have to share the RAM with that, I opted for 16GBs instead of 8GBs. The charger and accessories were not included but easy enough to get with typing in model numbers. My plan was to put Arch Linux on it to give the CPU as much room as possible given the limited speeds. It technically is a v3 CPU but I haven't learned how to switch kernel to an optimized branch for that yet so forgive me.
Now this story time I am typing is important because the issues begin here and there was no concrete answers, so I am not typing all of this just to share but so others can find this with a web search and have information, unlike me.
The seller put windows 11 on it... yes it has a TPM2 chip and is compatible with Windows 11, but that hogs too much resources for my liking, especially for the CPU limitations. So I had hope the BIOS was unlocked... hah
So funny story, DT Research does not have any drivers or bios download pages, not even downloads for their proprietary software to update the BIOS and remap the buttons on the front of the tablet. All of it is locked behind buying directly from them to get the software and shipping the device back to manufacturer to update the BIOS, lovely... So they have done some... things to the InsydeH20 bios (10 character password btw but for foreshadowing, does not give a challenge key to throw into a generator to unlock)..
Now first let me make it clear that one USB port is probably making you scratch your head on how I even got so far. Well it has a proprietary port on the bottom side that you can slot a proprietary keyboard (ACC-003-07) into or slot it in a dock to obtain 4 USB, ethernet, and display outs.
So the Insyde boot screen does not show any key hints on how to get into the BIOS..
Okay I'll use windows 11 to boot into the BIOS... password locked... oh no..
This causes an entire week of pain of reaching out to the seller, DT Research, and plunging deep into the web for answers on how to get past this. No BIOS tool can recognize the BIOS to dump. The normal Insyde tools people use in the dark do not work. Of course Insyde does not offer downloads and this isn't a lenovo or dell I can use a downloadable tool on.
Because I have no key hints, that also caused a great deal of confusion trying out all of the function keys and well as holding down the Fn button to press to try to enter bios.
My search history broke hundreds of pages with different word combinations in search engines to find answers. I wanted to avoid the reality of having to learn how to hack the hardware itself to get in... but this is reality after all.
If this thing is locked down, you only have 3 options:
- You short two very specific eeprom connectors with a piece of metal and keep shorting it while the device is on to bypass BIOS password and unlock everything... very cumbersome and precise. You have to hold the short till you change the password.
- Get a BIOS reader/flasher and dump the bios and then open it up in something like UEFItool or hex editor to hope the password is in plain text or you can decode it.
- Use a BIOS reader/flasher to dump a copy of the BIOS, modify the password out, and reflash the BIOS with no manufacturer supplied backup to save you.
But things were.... strange.. after an entire week of pain looking for answers... I remembered someone saying Fn + ESC to enter BIOS and.... I dropped the Fn.. I spammed ESC
I broke, I WAS IN. The BIOS suddenly opened up before my eyes.
For some reason or another rebooting into BIOS via shitdows was causing a BIOS lockdown.
and.... funny story... there was no BIOS Password... AT ALL The BIOS was fully unlocked the entire time... but something DT Research has done to it is... funky.. probably to discourage people.
So using windows to go into BIOS causes a lockdown. Touching the secure boot separate BIOS menu (because the bios is oddly divided into 4 distinct pages Continue, Boot Order, Secure Boot Option, and OSC/BIOS settings) causes a lockdown... which requires... booting into windows... restarting, and using ESC to unlock again. No.. uh.. just hitting enter on password prompt is not valid and will demand a restart after 3 attempts. Just hitting ESC to enter BIOS after touching the Secure Boot menu will not unlock... it for some reason needs to load an OS before you can spam ESC again to enter the unlocked OS.
What did DT Research do?
Anyways, I was IN. So I grabbed my Ventoy USB with arch linux iso already ready to go. I plugged it in, shifted the boot order and restarted and.. compatibility error. BIOS blacklisted running that USB... so... this modified InsydeH20 bios does not work with Ventoy. Use a more classical one iso USB boot maker instead....
heh..
except in my... stupidity I decided not to do that. Just use Rufus or Balena Etcher please.
Ahem so back in the bios I decided to... look at the boot type assigned in the BIOS and saw three options. These options were: Dual Boot, UEFI, and Legacy.
I tried to search for this "Dual Boot" option online and no matter my search words, I could not find an answer, just a bunch of results for dual booting linux with windows.
So... I assumed, assumed important here, that changing it to Dual Boot would result in both UEFI and Legacy boot being available at the same time. I hit save on this BIOS option...
Uhh you may not want to do this? Maybe? I can't tell due to my own blunder. I would suggest NOT to do this but I can no longer test what not doing it does.
What I can tell you is what happens next..
So... I reboot... and suddenly I am staring at this Intel GE boot controller using command line. If I wait long enough, I boot into the Insyde BIOS if I hit ESC... BUT everything is locked down asking for a password that doesn't exist and empty is not valid. If I allow the boot to continue without smashing ESC, I am met with no bootable drives found because Windows 11 refuses to boot unless the BIOS is set to UEFI boot mode... which I can't get into now.
So... I'm stuck and I cannot find the command line arguments for this Intel GE command line to boot back into win11 and get my BIOS back open.. from the DT Research modification weirdness. Trying to use the setup tool that Intel GE is giving me... results in nothing... So I am trapped in an impossible loop... until..
So... there is no bootable device right? I reach for my USB again and turn the tablet back on with the ventoy USB plugged in..
The LED on the USB Flashes.
Ventoy opened... I'M IN.
So disregarding my concerns over how even Linux may not boot after this, I run the arch linux iso anyways.
I setup my wi-fi connection and I run archinstall for the very first time ever. (yes, first)
Arch install works fine.. mostly. I install everything, set all of my stuff up. I choose SDDM as my greeter and Gnome as my DE.
I turn my tablet off when installation is finished, and I turn it back on, Arch Linux awakens.
Fuck yes
Oh No...
So SDDM is refusing to let me log in... cue me looking online MORE. So I had a hard time finding the button combination to launch TTY to get command line on SDDM. I believe it was Fn+F4.. unfortunately I haven't reconfirmed this yet but it was Fn + a function key somewhere between F3 and F6 using this proprietary keyboard for (ACC-003-07) the DT311.
So.. Arch Install did NOT create my HOME directory... it exists, but the folders do not. So after command line creating the folder, transferring login details to it, and updating the user permissions for it... I restarted the PC and was able to log in.
Congratulations, I now have a working Gnome Arch Linux install on a tablet where there is no info on how to do this.
Why?.. why? am I pressing so hard on the screen to do anything?... why is the stylus not behaving correctly?
So eGalax support for Linux specifically has been abandoned by EETI since 2019 and it was built for x-org. There is open source drivers already inside the linux kernel itself but it's not behaving correctly on Wayland.
So a little information about this eGalax type tablet screen. The screen is everything. The screen is a screen, a touch input, a mouse pointer, a tablet, and a pen. Yes the device, THAT device, is every single one of those. So... what's the stylus then? Well the stylus itself requires NO drivers. It simply transmits electrical signals when close to the screen to the screen itself to tell the screen itself where it is, is it touching, how hard, and if a button on the stylus is pressed. That AAAA battery is just to help create the electric charge to pass this.
umm xwayland... doesn't like this.
Now the linux kernel drivers are giving me screen, touch, tablet, and pen. According to the x-org logs, it is failing to make the device for mouse pointer.. still can use it though but I am fighting it. Also I cannot use the buttons (2) on the stylus.
So... EETI has a proprietary driver, I install that. So touch... improves dramatically. I do not have to fight the screen anymore... but the stylus is not working now. According to the x-org logs.. Tablet, Pointer, Eraser, and Pen are failing to become virtual devices to have stylus input.
So this is where I am at now. I am having to figure out either how to get this driver working or... figure out how to get the linux kernel drivers to behave.
Anyways, this has been my journey with the base model DT311 tablet and linux on it so far. I am hoping that posting this info here will make it show up on search results for anyone who also tries to touch this device or similar.
If you have anything you think could help, let me know.