Re: 2020-01-25-netbsd-raspi-earmv6hf.img (Re: Raspberry Pi update please.)

[Rob Newberry <robthedude%mac.com@localhost>]

>> I'm seeing similar issues with aarch64.
>> 
>> A GENERIC64 kernel boots.  But if I enable Raspberry Pi WiFi (tweak to GENERIC64, add appropriate firmware files), then it fails to boot -- it hangs/dies just before finishing startup.  Looks like it never really starts up "init" or at least never begins running rc.d scripts.
>> 
>> Here's the final bits of output when it fails:
> [...]
>> 	[   6.2546645] mue0 at uhub2 port 1
>> 	[   6.2546645] mue0: vendor 0424 (0x424) product 7800 (0x7800), rev 2.10/3.00, addr 4
>> 	[   6.5446960] mue0: LAN7800 id 0x7800 rev 0x2
>> 	[   6.5546989] ukphy0 at mue0 phy 1: OUI 0x00800f, model 0x0013, rev. 2
>> 	[   6.5546989] ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
>> 	[   6.5657407] mue0: Ethernet address b8:27:eb:8e:50:6c
> 
> Just to make sure, as the Pi 3A+ (which this thread is about) does not
> have ethernet - is this really a Pi 3A+ (which this thread is
> about) with a mue(4) plugged into the USB port or is this a Pi 3B+?
> 
> If it is the latter, I am not sure if this is related.

Yes, I misspoke -- might not be related.  

My device is a Raspberry Pi 3 Model B+.  It runs GENERIC64 kernel fine, but will not finish booting if I add the bwfm wireless as documented.

Rob