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)
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.
(11-03-2019, 06:33 PM)elewarr Wrote: [ -> ]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
, I downloadedÂ
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.