Date: Tue, 7 Aug 2018 14:00:02 +0200 From: Per olof Ljungmark <peo@nethead.se> To: John Kennedy <warlock@phouka.net> Cc: freebsd-arm@freebsd.org, Emmanuel Vadot <manu@bidouilliste.com> Subject: Re: usb-only rpi 3b+ (+UART foo) Message-ID: <767d4c31-e86a-442e-11a9-a12b80911ea0@nethead.se> In-Reply-To: <1c54c480-53ac-a88a-b6fb-8ae7072b19b9@nethead.se> References: <20180806042122.GD30738@phouka1.phouka.net> <0a6af236-84cc-66fb-c2fc-4e1976cbb1f7@nethead.se> <20180806151903.GF30738@phouka1.phouka.net> <4da80506-ba05-86c5-b9ff-c76e106426a2@nethead.se> <20180806220905.GG30738@phouka1.phouka.net> <1c54c480-53ac-a88a-b6fb-8ae7072b19b9@nethead.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/7/18 10:42 AM, Per olof Ljungmark wrote: > On 8/7/18 12:09 AM, John Kennedy wrote: >> On Mon, Aug 06, 2018 at 05:54:19PM +0200, Per olof Ljungmark wrote: >>> Stops after loading kernel: >>> >>> Booting [/boot/kernel/kernel] >>> Using DTB privided by EFI at 0x7ff8000. >>> EFI frambuffer information: >>> addr, size 0x3e330000, 0x8ca000 >>> dimensions 1920 x 1200 >>> stride 1920 >>> masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 >>> >>> and then nothing >>> >>> Happens for me with all stock images after July 19. >> >> I just burned the FreeBSD-12.0-CURRENT-arm64-aarch64-RPI3-20180802-r337160.img >> to an SD card and booted it up. >> >> The framebuffer information for my system is different (screen resolution? >> 1024 x 904 I think). After that, it clears the screen and goes into the >> kernel boot output that gets captured into /var/log/messages. >> > > 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 > > This is regardless of commenting out or not: > > # Multiple console (serial+efi gop) enabled. > # boot_multicons="YES" > # boot_serial="YES" > > 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. > > 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@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 Now I remembered that we have an older TV with HD (1024x768) resolution and I can indeed report the the rpi3+ boots at that resolution makes it point even more to a resolution problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?767d4c31-e86a-442e-11a9-a12b80911ea0>