libinput, which I believe, claims there is a kernel bug with the
synaptics driver touchscreen in use.
This is the recommended fix according to PostmarketOS.
* https://wiki.postmarketos.org/wiki/Troubleshooting:touchscreen#sec_touchscreen:_kernel_bug
I have not seen any issues from using this fix.
The error:
```
synaptics: kernel bug: device has min == max on ABS_MT_WIDTH_MAJOR
```
According to the touchscreen documentation of the kernel, I don't think
that it is an issue to remove this information from touch events.
The `-I` was accidentally left over.
I prefer assuming `<nixpkgs>` resolves to what is needed (a recent
nixos-unstable checkout) rather than forcing the users to checkout
nixpkgs into this project as I personally do.
Close#22Close#25
The gist of it:
* The "adb" function is not available (-22, EINVAL) on asus-z00t
* Enabling both adb and ffs breaks asus-flo
* Enabling ffs is fine with asus-flo.
So I guess it's ffs that enables adb!
While it's not as useful as the other splashes, this may help showing
issues with early post-framebuffer init. E.g. network or adbd in
stage-1.
The hollow logo is simple to describe, compared to a black and white
one, compared to a full colour one.
This is to allow platforms where the virtual console is not available to
graphically show the state of the system; is it stuck in stage-1, early
stage-2 or is it about to get into systemd's init?
This is still a big hack, though but relatively clean.
Otherwise, passing configuration to the NixOS modules system would
become harder, for "outside-in" builds, and would make it harder to
integrate into a nixos-rebuild type build.
I *think* there is a new check that wasn't previously (in 19.03) part of
e2fsck. This is now causing the check to fail.
FIXME : figure out a way to disable the check, or make the image comply.
