Swift Griggs writes:
> On Thu, 5 Jan 2017, Brad Spencer wrote:
[snip]
>> I have 3 RPI3b v1.2 boards. Two of them will not boot NetBSD 9 out of
>> 10 times. They will hang between these two lines:
>
> That sounds like a bummer. I'll watch for the same issue.
Ya,
On Thu, 5 Jan 2017, Brad Spencer wrote:
You will need to use something -currentish. I mostly run a 7.99.42
kernel with some local mods.
Thanks for the tip.
I have 3 RPI3b v1.2 boards. Two of them will not boot NetBSD 9 out of
10 times. They will hang between these two lines:
That sounds
Swift Griggs writes:
> On Thu, 5 Jan 2017, Brian Buhrow wrote:
>> I'm using NetBSD-current on an RPI3, using the RPI2 images. Everything
>> seems to work except for the wireless and bluetooth modules.
>
> Right on. I was trying a 7.x release, I think. I can't remember.
I'm sitting here complaining to the Lives group about the unsharp mask
plugin, trying to sharpen a video, on my 3B under Raspbian. Haven't
tried NetBSD on it in a couple months. I thought the WiFi worked with
plugin USB WiFi dongles though. At $5 or less they're an option.
--
Credit is the
On Thu, 5 Jan 2017, Brian Buhrow wrote:
I'm using NetBSD-current on an RPI3, using the RPI2 images. Everything
seems to work except for the wireless and bluetooth modules.
Right on. I was trying a 7.x release, I think. I can't remember. Anyhow,
I'll just use a -current image and try again. At
hello. I'm using NetBSD-current on an RPI3, using the RPI2 images.
Everything seems to work except for the wireless and bluetooth modules.
The dmesg for this is below.
Note that this is -current from the end of November 2016.
-Brian
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001,
I just picked up an RPI3. I guess I should have waited. A few congenitally
systemd-infected distros work on it, but not much else. FreeBSD was a
notable exception. It seems to work, but I managed to hork up the SD card
jacking around with ZFS before I could test X11 and other stuff. No big
On Thu, 5 Jan 2017, Patrick Welche wrote:
On Wed, Nov 30, 2016 at 11:30:51AM +, Stephen Borrill wrote:
mlelstv pointed out that because of the 64 sectPerSU RAIDframe setting (i.e.
128 sectors of data with 3 components, or 64k), the stripe unit is 32k, but
the whole stripe is 64k. By
On Wed, Nov 30, 2016 at 11:30:51AM +, Stephen Borrill wrote:
> mlelstv pointed out that because of the 64 sectPerSU RAIDframe setting (i.e.
> 128 sectors of data with 3 components, or 64k), the stripe unit is 32k, but
> the whole stripe is 64k. By starting the wedge at 64 sectors,
> this is