I'm trying to build a newly sync'd RockPro64 kernel and userland:
./build.sh -U -u -j6 -O ../obj -m evbarm -a aarch64 kernel=ROCKPRO64
distribution
I can successfully build tools and the kernel (copied GENERIC64 to
ROCKPRO64). Here's the error when I try a distribution build:
obj ===>
Thanks .mgr for guidence here.
Looks like I didn't correctly get latest updates on src. To test:
I renamed current failed src and obj, to src.old and obj.old.
I rsync'd latest (11-Sep) and did a tools, kernel, and release build; it
succeeded and all good as you said.
I took latest src with copy
I want to configure a static IPv6 along with a DHCP IPv4 on my Rock64
running NetBSD10_beta. However, I'm not able to get the default route for
IPv6 set on boot.
Here are my interface specific dhcpcd.conf entries:
interface awge0
noipv6rs
static ip6_address=2001:x:x:x/64
Entries in rc.conf:
> This feels like a slightly odd way to do things. If you want a static
> ip6, why don't you create ifconfig.awge and put in
>
> inet6 2001:x:x:x/64
>
Agree, that was an odd way for me to do both DHCP IPv4 and static IPv6.
This is simplicity winning again: An ifconfig.awge0 with static
>
> On my Windows machine, at least, I can get higher screen refresh rates
> from the DP port than HDMI.
>
On that note, I found this Hackaday post useful:
https://hackaday.com/2023/07/11/displayport-a-better-video-interface/
> As another test you could "boot -a" the netbsd10 kernel and then point
> it to a netbsd-10 installed USB or PCMCIA drive as a root filesystem.
> While you probably already have everything after the boot pretty much
> covered, it's always nice to see it come up and run completely from a
>
.
NetBSD 5.1.0_PATCH (ROCK) #5: Tue Dec 21 08:31:59 PST 2010
joelp@baker.westlab:/usr/obj/sys/arch/i386/compile/ROCK
total memory = 81660 KB
avail memory = 75672 KB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
> Any chance that BIOS can do netboot? It's a long shot perhaps,
> but I've owned several non-Intel machines of approximately that
> vintage that I've successfully netbooted NetBSD onto, for
> reasons similar to yours: the other possibilities required
> no-longer-functioning hardware.
>
>
>
> I have been doing inplace upgrades on systems for years, almost entirely
> successfully. My scripts are in pkgsrc/sysutils/etcmanage, which in
> addition to etcmanage has BUILD-NetBSD and INSTALL-NetBSD. This will
> seem like a lot, but I find once I'm set up, updating is very easy and
>
> Hi I would say to take to hard drive out and use some other computer to
> install NetBSD 10 on it or use qemu.
> to use qemu install the drive in a linux machine with the linux boot drive
> and run "qemu-system-i386 -cpu pentium -m 64 -cdrom
> NetBSD-10.0rc1-i386.iso -hda /dev/oldlaptopsdisk"
>
> On Thu, Dec 21, 2023 at 4:07â¯AM wrote:
>>
>> > Hi I would say to take to hard drive out and use some other computer
>> to
>> > install NetBSD 10 on it or use qemu.
>> > to use qemu install the drive in a linux machine with the linux boot
>> drive
>> > and run "qemu-system-i386 -cpu pentium -m
11 matches
Mail list logo
