I managed to get 13.0 installed in an ARM parallels VM, but the network interface doesn’t seem to be supported.
I used ISO images to copy the parallels-tools source and managed to build if_pvmnet.ko, but it doesn’t want to attach.
Has anyone gotten this working yet?
I've got a VM over at rootbsd (NetActuate now), and it's been running fine forever. Today, they had an emergency maintenance, and since then booting has failed with repeated lines of "Solaris: WARNING: can't open objset 54, error 5" followed by "Mounting from zfs:tank failed, error 5." and then...
I have my ruby default version explicitly set to 2.7 in make.conf:
DEFAULT_VERSIONS+=ruby=2.7
pkg version -vIL= says:
ruby-2.7.1_1,1 > succeeds index (index has 2.6.6_1,1)
ruby27-bdb-0.6.6_8 ? orphaned: databases/ruby-bdb
ruby27-gems-3.0.6...
It actually had a qualified name at one point. I flattened it with pkg set as one attempt at fixing this. I can put it back, but either way it still claims to be orphaned.
Why is it preferred to make a local conf file instead of just editing /etc/pkg/FreeBSD.conf?
Not questioning it... you wouldn't have suggested if it there wasn't a good reason - just want to understand why.
I don't know for certain, but I'm fairly confident this isn't a problem with the Raspberry Pi firmware itself. The video console works, and forcing the HDMI hotplug should result in the video always being selected. But something about the FreeBSD boot code that's layered on top seems to be...
I believe the configuration of the frame buffer in this regard is the same on all Pi platforms. config.txt, I believe, is a set of parameters for the firmware (the files loaded from the FAT partition). So I think your solution will be found in config.txt, at least if it's the text console screen...
I've got 10.1-RELEASE running on a Raspberry Pi B+, and things are coming along reasonably. But one issue is confounding me a bit. The serial port is being used as the console. I've got hdmi_force_hotplug=1in config.txt, and with an HDMI monitor hooked up I can plainly see the kernel probing...
The question wasn't about ports, it was about upgrading the base from 10.0 to 10.1 without having to just wipe the SD card and start over again.
Which is what I wound up doing in the meantime.
I'm going to take a wild guess that freebsd-update isn't going to support ARM. Is there any reasonable path other than just downloading a 10.1 image and starting from scratch?
I'll take that to the bank. I was able to find some driver source out on the net somewhere that showed the right values in the usbdevs entry and reference to that entry in a table in if_urtwn.c, so... yay! :D
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.