Yes, I've exchanged a few emails with DeRaadt. Things were in their
infancy back then, the Pi hadn't been out that long, I'm not real
surprised that FreeBSD wasn't perfect. I don't think they supported
the Pi's camera then (which I think was more expensive than the Pi
itself) so that was another reason I went back to Raspbian.
Many times when I've looked into things like network card driver
source code in OpenBSD I find a NetBSD copyright. I think I've
downloaded NetBSD 3 times over the years then didn't have spare
hardware to try it on. But SD cards are like swappable hard drives,
much more flexible.
So back to trying to work around this. I gather NetBSD uses
ifconfig.interfacename files like OpenBSD uses hostname.interfacename
files. The hostname.em0 for my ethernet card looks like:
inet 192.168.0.7 255.255.255.0
I seem to be able to mount NetBSD's partition on the SD with the SD in
a USB reader plugged into my OpenBSD laptop. If I could make an
ifconfig.interfacename file then I could bring the Pi up in NetBSD and
ssh to it. I can't read what the standard name of the Pi's ethernet
interface is though. Could somebody clue me in?
On 5/10/16, Joe Nosay <superbisquit%gmail.com@localhost> wrote:
> Sometimes the ports need tweaking. At times the BSDs work together - at
> least Net and Free do, DeRaadt isn't much on working with others. Talk to
> the developers on both sides to see if they are able to help you with a
> solution.
>
> On Tue, May 10, 2016 at 11:30 AM, Alan Corey <alan01346%gmail.com@localhost> wrote:
>
>> It seemed OK, that was on the model B a couple years ago. I was
>> disappointed that many ports in the ports tree wouldn't build though.
>> And I had a problem with the SD card socket so the whole Pi was
>> unreliable, I didn't use it for a year.
>>
>> On 5/10/16, Joe Nosay <superbisquit%gmail.com@localhost> wrote:
>> > How was the performance of FreeBSD upon the Pi?
>> >
>> > On Tue, May 10, 2016 at 1:22 AM, Alan Corey <alan01346%gmail.com@localhost>
>> > wrote:
>> >
>> >> I'm running 2016-05-14-netbsd-raspi-earmv6hf.img.gz on a Raspberry Pi
>> >> 3b and it seems to almost ignore the video modes in config.txt.
>> >> Mostly it does 1920x1080@60 except sometimes it looks like the same
>> >> mode but out of focus. The monitor (Dell s2409w) says it's
>> >> 640x480@60.
>> >>
>> >> My EDID is apparently not readable under Raspbian because unless I
>> >> specify a mode I get a black screen. I normally use hdmi_group=2,
>> >> hdmi_drive=2, hdmi_mode=24 on the 3b but my model B was different.
>> >> I'm not sure how universal HDMI modes are, apparently not very.
>> >>
>> >> I tried the group 2 mode 16 suggested in a comment in config.txt and
>> >> it gives me the same 1920x1080. I've tried about 4 modes including
>> >> hdmi_safe and the numbers from what Raspbian defines that as, plus my
>> >> 2/2/24. I'm not sure how it can look out of focus on an LCD monitor,
>> >> it looks OK with other things fed into it, including the Pi in
>> >> Raspbian. Sometimes it's just not readable. I can't ssh into it
>> >> because I can't read the interface name so I can set it to a usable
>> >> IP.
>> >>
>> >> I've recently discovered the monitor says it's 640x480 though. I've
>> >> had X running a couple times, the characters in xterm are hard to
>> >> read. How can I have tiny characters yet the monitor sees it as
>> >> 640x480? Maybe a dot clock thing. It's like looking at a photograph
>> >> of a 1920x1080 that's only 640x480, you can't actually read anything.
>> >>
>> >> I've never used NetBSD before, but I've used OpenBSD for 15 years
>> >> (i386). Unfortunately they won't touch the Pi because they don't like
>> >> the BLOBs. This is my 2nd Pi, I got my model B in 2013 and ran
>> >> Raspbian and FreeBSD on it.
>> >>
>> >> Alan Corey
>> >>
>> >> --
>> >> Credit is the root of all evil. - AB1JX
>> >>
>> >
>>
>>
>> --
>> Credit is the root of all evil. - AB1JX
>>
>
--
Credit is the root of all evil. - AB1JX