Date: Tue, 22 Jun 2021 08:40:33 +0000 From: Dan Kotowski <dan.kotowski@a9development.com> To: dsl@mcusim.org Cc: Mark Millard <marklmi@yahoo.com>, freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: HoneyComb first-boot notes Message-ID: <Rv9QGaKflpIjLPsxUFG3ht12loej__FxMBy7SQ1QzDTk1NLcFjGb4ScQuF32SakZi68wjgPQpIVp2dipMoYteJIAMhSrXbPM6-mRSeL_744=@a9development.com> In-Reply-To: <YNGf999RsaTfNhcp@x230.ds> References: <8A6C415F-A57B-4F2F-861F-052B487166D6.ref@yahoo.com> <8A6C415F-A57B-4F2F-861F-052B487166D6@yahoo.com> <YNGT5hcHOBd6cU4T@x230.ds> <40AE6447-77AF-4D0E-864F-AD52D9F3346F@yahoo.com> <YNGf999RsaTfNhcp@x230.ds>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > I put an existing FreeBSD Optane into a just delivered > > > > > > > > HoneyComb, put in the RAM and the matching UEFI/ACPI > > > > > > > > image on a microsd card and put the card in the slot. > > > > > > > > I plugged in a USB3 Ethernet dongle, like I use on some > > > > > > > > other systems. Serial console via its USB port for such. > > > > > > > > (Optane instead of video card.) The UEFI/ACPI image was > > > > > > > > extracted from: > > > > > > > > https://solid-run-images.sos-de-fra-1.exo.io/LX2k/lx2160a_uefi/lx21= 60acex7_2000_700_2900_8_5_2_sd_81b4bbe.img.xz > > > > > > > > in order to match the RAM and being based on the > > > > > > > > most current vintage at: > > > > > > > > https://github.com/SolidRun/lx2160a_uefi/ > > > > > > > > It booted. > > > > > > Could you share whole dmesg? > > > > I've not done a "boot -v" . The below is actually from a > > > > captured serial console output. It is lightly edited. I > > > > have omitted nearly all loader output (and before). > > Thanks for sharing. Have you seen somewhere in output from UEFI (before > > the loader) that "DPAA2 Management Complex initialized"? > > Regards, > > Dmitry stable/13 dmesg: https://gist.github.com/agrajag9/bf6325d4f3321d8d0ee566fee= 767e0d3 current dmesg: https://gist.github.com/6d07004fb3c6f0980d5e94627aaba060 @dmitry - just ignore all the DPAA2 stuff for now. We don't support it at a= ll :'( @mark - I was given a warning about i2c from SR's @jnettlet that it's possi= ble to completely brick the system, although maybe they've solved that in t= he more recent SOC revisions? The IORT warnings might be related to SMMU. I'll have to dig up my notes, I= did a ton of work with Greg on this months ago and it seems that's been sw= apped out of brain memory onto cold storage somewhere. Possibly here? https= ://gist.github.com/agrajag9/ff3c52c11469dccb70e17a11cb9be2a9 Feel free to use/critique my KERNCONF: https://gist.github.com/agrajag9/e39= 91573a274e59f58a0b520d2dcd5d2 Fans: I've had mixed success here. Lots of people went for a full watercool= ing loop with https://www.alphacool.com/shop/gpu-water-cooler/amd-gpu/11088= /alphacool-hf-14-smart-motion-universal-copper-edition?c=3D20587 I'm just using https://www.radianheatsinks.com/product/inm37-5004-25pcu-2-6= / but others like http://www.enzotechnology.com/cnb_r1.htm Either way, welcome to the party! I've been daily-driving mine as a desktop= for a few months, although I still can't get drm-kmod's amdgpu to load pro= perly - perhaps you can? --Dan Kotowski
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Rv9QGaKflpIjLPsxUFG3ht12loej__FxMBy7SQ1QzDTk1NLcFjGb4ScQuF32SakZi68wjgPQpIVp2dipMoYteJIAMhSrXbPM6-mRSeL_744=>