I went from shop to shop for days and started to feel that it had been a mistake to sell my T200. I couldn’t justify spending that much money on a machine that sold elsewhere for about $600, so I kept looking.Įverything seemed to be either too big, too small, or too expensive. The newly released (at that time) Asus UX305 looked to be perfect, except it was selling here (Thailand) for nearly $1000. At the same time, their premium models with higher resolution screens and more horsepower were selling for about twice what I wanted to pay. Acer’s more affordable line of Switch tablets had even lower resolutions than my old T200, not to mention poorer overall design. I did a lot of research before heading to the malls, but the choice wasn’t as easy as I thought.Īs the T200 was about 6 months old by that point I had assumed that Moore’s law would have taken effect and I could get everything that I wanted for the same price- or perhaps even cheaper. A touchscreen would be nice if I could get one, but it wasn’t required. I’m a teacher who frequently plans lessons on the move, so a low weight and small footprint are always a plus. My priorities were basically to find something with (1) a higher resolution screen, (2) better performance, (3) more storage, and (4) sleeker profile. The tiny 32GB of storage, leaving me with 3GB of free space, wasn’t fantastic either. One of the biggest issues was the WXGA (1366 x 768 px) screen which, when used in tablet mode with the on-screen keyboard, left only about 3 visible lines of text in any word processing programme. rEFInd documentation has more about this.The T200, my first 2-in-1 and Windows tablet, was a nice machine, but I found the performance and battery life somewhat middling. Maybe registering the refind.efi binary's hash rather than the signing key via MokManager is the way to go.
I'm sure there's a way to make it work, but I was too exhausted to dig into registering keys via EFI command line. After re-enabling secure boot, it would present me with an annoying dialog saying "Invalid signature" (as you can see at the bottom of the post), although it'd proceed booting anyways (and it didn't even complain about my signed kernel either!) I ended up disabling secure boot again because I disliked that dialog more than the red boot screen.
That's largely correct given this configuration it's possible to enable Secure Boot and still boot into rEFInd/Ubuntu (getting rid of that annoying red boot screen.)Īlthough it definitely worked at some point, after tweaking settings over and over, in the end, however, I struggled getting the firmware to verify the rEFInd's signature using my custom key I registered via MokManager.
0 kommentar(er)
