usb-only rpi 3b+ (+UART foo)

[Per olof Ljungmark]

On 8/7/18 2:19 PM, John Kennedy wrote:
> On Tue, Aug 07, 2018 at 10:42:26AM +0200, Per olof Ljungmark wrote:
>> Aha.
>>
>> So , I can confirm r337160 *does* boot, but with the following
>> differences from the July 19 snapshot:
>>
>> - There is no output on the big HDMI connector after the above message
>> - Booting only finishes if I do *not* attach the HDMI connector
>> - There are no active LED's at the ethernet connector, but it actually
>> works and finishes the boot *if* HDMI is disconnected
> 
> Well, I'm definitely getting output on my HDMI connection all through the boot
> since I haven't figured out how to get the serial output working flawlessly.
> 
> I haven't seen my ethernet activity LEDs working ever, but I've only had this
> thing since the ~rpi3-20180709-r336134.img timeframe.  That's come up on this
> list before.
> 
>> dmesg at successful boot shows display set to 656x416, so is 1920 x 1200
>> the problem then? Wish I had another less capable monitor sitting here.
> 
> Hmm.  Well, in screwing around with X in the past, I've seen all kinds of screen
> screwups but that just leaves the screen unusable, not the OS hung.  And by
> unusable, I just mean using a resolution that the monitor won't sync to, so the
> game is to limit it to something that will work.
> 
>> Aug  7 08:26:26 generic kernel: fb0: <BCM2835 VT framebuffer driver> on simplebus0
>> Aug  7 08:26:26 generic kernel: fbd0 on fb0
>> Aug  7 08:26:26 generic kernel: VT: Replacing driver "efifb" with new "fb".
>> Aug  7 08:26:26 generic kernel: random: harvesting attach, 8 bytes (4 bits) from fbd0
>> Aug  7 08:26:26 generic kernel: fb0: 656x416(656x416 at 0,0) 24bpp
>> Aug  7 08:26:26 generic kernel: fb0: fbswap: 1, pitch 1968, base 0x3eb33000, screen_size 818688
>> Aug  7 08:26:26 generic kernel: random: harvesting attach, 8 bytes (4 bits) from fb0
> 
> kernel: FreeBSD 12.0-CURRENT #10 r337273+da001c8d4b45(master): Sun Aug  5 11:50:29 PDT 2018
> kernel:     warlock at rpi3.phouka.net:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64
> ...
> kernel: fb0: <BCM2835 VT framebuffer driver> on simplebus0
> kernel: fbd0 on fb0
> kernel: VT: Replacing driver "efifb" with new "fb".
> kernel: fb0: 1824x984(1824x984 at 0,0) 24bpp
> kernel: fb0: fbswap: 1, pitch 5472, base 0x3e6cd000, screen_size 5428224
> 
> I've just got that piped into a Samsung TV-monitor that has been a accidental
> trooper.  The text-character "dimension" is a bit odd (228x61), but it works.
> 
>> I suppose I should get myself a serial console connection...
> 
> Heh.  That's why I got mine.  I've been resorting to iPhone burst photos to try
> and get a good picture of what's going on, at least so I can retype it.

Well, the pi booted with HD 1024x768 but not 1920x1200. You don't happen
to have a 1920x1200 monitor available? Would be nice to know if it's
only me.

Anyway, I'm setting up a build enviroment but don't think I will have
anything to report until tomorrow.