OpenBSD on Pinebook - improving user experience

[elewarr]

News:
- PWM driver was updated, now it should handle any periods (in nanoseconds), previous version was buggy and didn't support higher periods (but it was enough for the backlight): https://github.com/elewarr/openbsd-arm64...c4b0b09716

[elewarr]

News:
- more PWM driver updates - it relies on new pwm_* methods recently introduced to OpenBSD kernel, yay!
- sxipwm and pwmbl drivers sent to tech@ (still work in progress but I'm quite happy about current state of sxipwm)

[elewarr]

News:
- sxipwm/pwmbl drivers are now officially in OpenBSD!
- I prepared a new image with OpenBSD 6.6 (snapshot), introducing FVWM2 (based on this: https://github.com/addy-dclxvi/almighty-dotfiles)

https://wiki.pine64.org/index.php/1080P_...se#OpenBSD

[elewarr]

News:
Updated the pinebook image with latest updates (kernel and packages): https://wiki.pine64.org/index.php/1080P_...se#OpenBSD (image still uploading).
I modified u-boot configuration for pinebook a bit and it seems some boot reliability issues I had in the past are now gone.

[tllim]

News:
Updated the pinebook image with latest updates (kernel and packages): https://wiki.pine64.org/index.php/1080P_...se#OpenBSD (image still uploading).
I modified u-boot configuration for pinebook a bit and it seems some boot reliability issues I had in the past are now gone.

Thanks on the update.

[rogerroger]

News:
Updated the pinebook image with latest updates (kernel and packages): https://wiki.pine64.org/index.php/1080P_...se#OpenBSD (image still uploading).
I modified u-boot configuration for pinebook a bit and it seems some boot reliability issues I had in the past are now gone.

Hi @elewarr , I downloaded 

• https://www.dropbox.com/s/79hpdpehrbbk98...ha256?dl=0 (sha256)
  
• https://www.dropbox.com/s/yas1glfvvucb9a...g.tgz?dl=0 (image)
  

from the wiki; I renamed it to fit better in my system (and modified the shasum accordingly); it downloaded correctly, but the file is corrupt:

Code:

$ shasum -c pinebook-openbsd-elewarr-2019-11-04.img.tgz.sha256 pinebook-openbsd-elewarr-2019-11-04.img.tgz: OK $ tar -zxvf pinebook-openbsd-elewarr-2019-11-04.img.tgz pinebook-2019-11-04.img gzip: stdin: Input/output error tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now

did Dropbox clip it?

I tried to use it anyway

Code:

$ time sudo dd if=pinebook-2019-11-04.img of=/dev/mmcblk0 bs=1M 6733+1 records in 6733+1 records out 7060880896 bytes (7.1 GB, 6.6 GiB) copied, 1240.21 s, 5.7 MB/s real 20m40.229s user 0m0.143s sys 0m18.783s

and it booted up to xenodm I like the default background you picked. Maybe there's some small set of corrupt and missing files as the end of the disk, but they don't seem to be impeding operation at all.