Am Mi., 8. Mai 2019 um 00:51 Uhr schrieb Jason Thorpe :
>
> > On May 7, 2019, at 2:37 PM, Jared McNeill wrote:
> >
> > On Tue, 7 May 2019, Markus Kilbinger wrote:
> >
> >> - I was not able to bootarm.efi this kernel from its local ffs2 (!)
> >> netbsd partition on the sdcrad. Is bootarm.efi
> On May 7, 2019, at 4:54 PM, Andrew Luke Nesbit
> wrote:
> This is a really great thread, which I am enjoying very much.
>
> I don't use any BPi because I am a user of Orange Pi (especially the
> OPi+2E).
>
> But considering they are very close in architecture and use
> (essentially) the
On 07/05/2019 22:37, Jared McNeill wrote:
> On Tue, 7 May 2019, Markus Kilbinger wrote:
[...]
This is a really great thread, which I am enjoying very much.
I don't use any BPi because I am a user of Orange Pi (especially the
OPi+2E).
But considering they are very close in architecture and use
> On May 7, 2019, at 2:37 PM, Jared McNeill wrote:
>
> On Tue, 7 May 2019, Markus Kilbinger wrote:
>
>> - I was not able to bootarm.efi this kernel from its local ffs2 (!)
>> netbsd partition on the sdcrad. Is bootarm.efi limited to ffs1?
>
> It uses ffs support from libsa, so I would
On Tue, 7 May 2019, Markus Kilbinger wrote:
- I was not able to bootarm.efi this kernel from its local ffs2 (!)
netbsd partition on the sdcrad. Is bootarm.efi limited to ffs1?
It uses ffs support from libsa, so I would expect it to work (but can't
say that I have tried it on armv7).
- In
Am Di., 7. Mai 2019 um 12:17 Uhr schrieb Jared McNeill :
> [...]
> Now on to the modern boot method..
>
> Using U-Boot 2018.11 or later, setup a FAT partition with the following files
> on it:
>
> EFI/BOOT/bootarm.efi
> your-fdt-file.dtb
>
> U-Boot will automatically launch the UEFI
That looks much cleaner will try that.
Frank
On 05/01/19 22:58, Jared McNeill wrote:
So there is a better way to boot modern NetBSD/arm (using UEFI and
bootarm.efi). If you want to boot the old way, it goes something like
this:
setenv bootargs root=ld0a console=fb
fatload mmc 0
So there is a better way to boot modern NetBSD/arm (using UEFI and
bootarm.efi). If you want to boot the old way, it goes something like this:
setenv bootargs root=ld0a console=fb
fatload mmc 0 $kernel_addr_r netbsd-GENERIC.ub
fatload mmc 0 $fdt_addr_r $fdtfile
fdt addr $fdt_addr_r
On 01/05/2019 21:07, Frank Kardel wrote:
[snip]
[ 5.9727975] panic: usbd_transfer: not done
[ 6.0611224] cpu0: Begin traceback...
[ 6.1478907] 0x9c695b84: netbsd:db_panic+0x14
[ 6.2380975] 0x9c695b9c: netbsd:vpanic+0x194
[ 6.3276372] 0x9c695bb4: netbsd:snprintf
[ 6.4161552]
Thanks - that got me beyond screen initialization.
but
bootm 8200 - $fdt_addr_r root=ld0a console=fb
asked for the root device, swap, fs tape and init - so the parameters
probably did not reach the kernel at all.
starting X didn't show anything on the 4K screen, X seemed to be running
Remove the following devices from your kernel config and the kernel should
use simplefb instead: sunxidebe, sunxitcon, sunxihdmi, sunxidep
I just peeked at the code quickly and it looks like the DE drivers are
blindly using the display's advertised preferred mode without taking its
own
I tried -current with my Bananapi an had limited success:
Using the first steps copying the image armv7 and the 2018.05 u-boot I
found the u-boot load attempting to perform a dhcp boot as nothing was
found on the mmc drive in autoboot. Did I miss somethnig to set up there ?
I finally got a
12 matches
Mail list logo
