FBSD 11 is now RC1 and seems to work on RPi

(re-post from alt.hacker, relevant)

looks like FBSD 11.0 is now RC1.

did a test download of the image for RPi (in this case, the older 'model B'). the file was 'xz'd so needed to use 'xz' to decompress. no biggee.

Once decompressed (pretty fast), I used 'dd' to put it onto a 4G SD card, something like this (on a Linux box, actually):

dd if=fbsd11RC1.img of=/dev/sdaf bs=1M

(note you don't write to 'sdaf1' but 'sdaf' since the image has the partition tables in it). Unplug USB adn re-insert after, and you get sdaf, sdaf1, sdaf2 so it was working fine - those happened to be the drive letters that the multiple SD card adaptor caused to happen, since it supports several card types, and each port gets a letter for some reason, oh well)

Anyway...

This resulted in 2 partitions on the SD card, with the first one about

17Mb, an 'MSDOSFS' partition containing the boot files [this is how RPi works, so you have to have that]. The additional 1.1G partition was the FreeBSD UFS file system with all of the necessary stuff already installed on it.

So, I fire it up to see what happens, and one of the first things that the bootup does is grow the file system to fit the SD card (basically, rc.conf runs 'growfs'). Excellent! No need to do this manually.

Then, after 'a little hacking', I'm logged in as the 'freebsd' user. The machine name was pre-assigned to 'rpi-b' because that's the image type (an RPi 'B'). I expect the RPi 2 image will have a different name. So naturally you need to change this in rc.conf if you plan on having more than one RPi on your network.

basic information is here:

formatting link

(the important part is the default logins root:root and freebsd:freebsd which of course you should change ASAP - I did)

images are here: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/11.0/

next fun part was getting the ports, but of course the handbook lets you know how to do that [however on RPi the extract/verification process was extremely *SLOW*]

formatting link

once there, you can install the 'pkg' utility from the ports collection, specifically 'ports-mgmt/pkg', and install packages as described here:

formatting link

(note this process is ALSO really really slow, but hey, it's like a

400-something Mhz arm32 processor with 512M of RAM, so 'meh')

also I discovered that there's an error in the package configuration file. the 'url' line should read:

url: "pkg+

formatting link
${ABI}/latest"

and in /usr/local/etc/pkg.conf the 'ABI' line should be

ABI = "freebsd:11:armv6:32:el:eabi:softfp"

(so far this seems to work, though it may not be 100% correct)

of course, my OWN motivation for this is the comms/uarduno port, which was reported as 'broken' under FBSD 11 [apparently some header files have moved or something]. so now I'll be able to fix/test it without building and running it on an x86 machine, hopefully [and I'll be able to verify that it works properly on an arm-based system]. I did see a built package for it, so maybe they fixed it FOR me?

NOTE: if you're building ports on an RPi, and you need more space than the drive has, mount an NFS share to /bigdrive and do this:

make WRKDIRPREFIX=/bigdrive install

rather than just 'make install'. this should do the trick.

I also noted some minor differences in RC vars from earlier versions of FBSD, particularly the version I'm still running because I need these machines RUNNING and don't really have anything that needs patching on any of them (that wasn't already patched). but it would be simple to upgrade my old boxen if I can afford to shut them down for a bit to do so. Which I can't, not really. I'll wait until I have money to buy NEW boxen, then build them 'anew' like I did before, so I can keep the old ones around as 'beater' boxen. yeah.

until then I"ll toy with this RPi running FBSD.

--
your story is so touching, but it sounds just like a lie 
"Straighten up and fly right"
Reply to
Big Bad Bob
Loading thread data ...

o:

[CUT]

Excellent news!

Thanks for the info

Bye Jack

Reply to
jack4747

Unless you have a pi 3 :-{ Does anyone have any idea when images for the pi3 will be available? If ever?

--
Mike Scott (unet2  [deletethis] scottsonline.org.uk) 
Harlow Essex 
"The only way is Brexit" -- anon.
Reply to
Mike Scott

ritto:

you should be able to use the images for Rpi2 (you won't have wifi and bt s upport tough).

Bye Jack

Reply to
jack4747

They should really rename the images, though. Right now it's "armv6-RPI-B" and "armv6-RPI2", that should at least be "armv6-RPI1" and "armv6-RPI2". Also disappointing that they (like Raspbian) couldn't switch to armv7 for RPi 2 (and 3).

Reply to
A. Dumas

Names aside, I've just tried the arm6 fbsd12 image from freebsd.org, and the raspbsd image (fbsd11). Neither does much - I just get a colour wheel, and the pi's activity light stays firmly 'off'.

FWIW sticking the sd card into a running linux system mounts a reasonable-looking FAT32 partition, so I assume the card is ok. (I've taken out a running raspbian card, so I know the PI's ok).

Not sure what to try now. Is it really the case that current PI2 images will (should?!!) run straight off in a PI3?

--
Mike Scott (unet2  [deletethis] scottsonline.org.uk) 
Harlow Essex 
"The only way is Brexit" -- anon.
Reply to
Mike Scott

itto:

d

if the image has the last (or at least a new enough) firmware it should. At least it works for distros like OpenElec...

Bye Jack

Reply to
jack4747

On 22/08/16 14:05, snipped-for-privacy@gmail.com wrote: .....

I've been pottering a bit without luck; largely guesswork.

I have a working raspbian system, and a non-booting raspbsd. Raspian has things in the boot area named like bcm2708-rpi-b.dtb. The raspbsd has only rpi2.dtb. From what I gather, these define the devices on the particular system.

I've tried copying over bcm2708-rpi-b.dtb; I've tried copying it over and renaming as 'rpi2.dtb' (I know!!!) and I've tried copying it over and changing device_tree= in config.txt to point to it.

Nothing does anything different.

I have checked the card on my freebsd server - the file systems look good; the boot area plus a ufs partition looking like a system fs.

The file dates on raspbsd appear to post-date those of the working raspbian, so I'm assuming they're up-to-date.

There has to be some magic I'm missing :-{ Any offers please?

--
Mike Scott (unet2  [deletethis] scottsonline.org.uk) 
Harlow Essex 
"The only way is Brexit" -- anon.
Reply to
Mike Scott

From what I've seen on snipped-for-privacy@freebsd.org the answer is "not soon". There were a few posts some time ago, but recently nothing. I hope it's just because everybody is busy getting ready to release 11.0, but some of the emails suggested there are non-trivial differences between the pi2 and pi3.

hth,

bob prohaska

Reply to
bob prohaska

I've been using FreeBSD 11 on a PiZero for a month or so. I only have a serial connection (no network or usb) and would like to be able to install downloaded packages locally as you would with a .deb

Fairly new to BSD and haven't got linux to read the ufs partition. Possibly will use tar at both ends to move files across the serial port with a cksum before and after.

I'm used to aplay and arecord for audio, how can I explore the FreeBSD audio format capabilities? I'm assuming hdmi playback as with RISC OS. RISC OS is limited to 16bit wavs, will FreeBSD do 24bit? I dont believe this is terribly important due to 99% of available audio is 16bit, it could be useful for comparison purposes.

I've had an issue with the csh history arriving with different instances though always logging in as root:root but I guess it is time to upgrade to RC1 if it is newer. Would the version be reflected by the kernel version no. or would I have to refer back to the disk image name?

Thanks for any tips received, googling is not as rich as for ubuntu etc.

Ron M.

Reply to
Ron

uname -a reflects all the installed version info I installed ufs-utils in linux but all attempts with this or mount result in an error to do with the magic number problem regarding the FreeBSD partition. I have RC1 installed now, and the source package for pkg to install. I read somewhere that pkg /will/ work locally, but I haven't worked out where or what packages I can download for it to work with.

Ron M.

Reply to
Ron

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.