Vieweing the video again, it's obvious that pkg+http is used for accessing the package repository for 14.0, at 3:09, while pkg+https is used for 14.1, at 5:42. In other words, correct time is more critical for 14.1 than it is for 14.0.
Well, why not use FreeBSD's built-in time sync features? One to sync the time at boot (required in this case, since regular NTP won't start if the date is way off) and then the service to keep it in sync while running: sysrc ntpdate_enable="YES" sysrc ntpd_enable="YES"
I use that naturally on every BSD box I use, what threw me was all the previous installs to the Pi worked out of the box, and this one was a non-starter.... until the date issue was recommended . I view FreeBSD on X86/64 as a separate thing to the PI, as it should be good to go straight away as it is for a different client market.... someone casually trying out FreeBSD would be greatly put off by the experience.... it's a given for the PC or Server that some configuration is in order, but for the PI it should be already configured to a certain degree.....
ntpd -q -g on the command line after network connection is made. Works on wired ethernet connection fine, yet I have problems using a USB wifi dongle with an access point wifi connection problem. I have to manually connect to wifi access point then issue : ntpd -q -g command to set date and time to current value.
Someone help and work with me to port Openbsd or Netbsd cy43455 43456 wifi driver to FreeBSD. I am reading Joseph Kongs book on FreeBSD device drivers and also ran the sample freebsd dummy device driver example. openbsd bwn device driver
arm is likely the future of most computing, so arm is really important to get right. That said, I have a freebsd install on my raspi 3 working as a nice little server and it works flawlessly.
Oh I think OpenBSD also has wifi support for the Raspberry PI and specifically the PI 400. I'm all for using the best OS for the job while honoring your personally held beliefs.
Great video as always. Wondering if you can do one for NetBSD 10 on R Pi 400. Huge improvements on the ARM ports are one of the big changes amongst the many in the new release. Thanks.
Makes me wonder if 14.1 is okay on amd64 systems. I had trouble upgrading to 14.0 a few months back, but that was likely my fault. I'm still finding things that were installed but aren't now.
TBH I've become a massive fan of these cheap mini PC's that are out there. The N100 CPU is amazing, and many of these boxes workout cheaper than a RPI5, more compatible, less hassle to setup, the list goes on.
Same. I have one of these running Proxmox and I love it to death! Both cheaper and faster than the top performing SBCs, compatible with everything, no need to buy cases, etc. How can one not love them?
I agree with your pain points. I mean the RPI4 has been out for quite some time so basic things like wifi should be working. I have some RISC-V SBCs that function better than FreeBSD on the RPI4
There is a bug in firefox build later versions that does not include libm.so . So you need to have "LD_PRELOAD=/lib/libm.so.5" exported in you shell environment.
My main issue with the BSD's and ARM is the lack of GPU support. I can live with a dongle for wifi but we really need GPU support for a descent desktop.
I have struggling the last weekend with the pkg problem, and yesterday after try and error, I discovered, as it is done in the video the date must be setted otherwise it will not work. I try tu use USB tethering , however the DHCP settings reset after each reboot.
I've been told the date thing was the result of a fix to allowing wrong date, but perhaps NTPdate should have been set to automatically allign time.... I
I tried to install FreeBSD on a Raspberry Pi 400 a couple years ago and there was definitely some strange behavior, one being it failed to correctly set the resolution on my monitor.
14.0 breaks the standard for pkg/https because of the date being wrong. One should always run ntpd / ntpdate on raspberry pi whether linux or bsd :) It looks like 14..1 fixed that gaping security hole (wrong time)
I hadn't thought of it like that.... I suppose it makes sense.... but all the previous installs for as far as I can remember for the PI, it always went without a hitch....until this one. Oh well, the next time I will be prepared :-)
Well, to be fair things like full blown Firefox and worse: trying to run TH-cam on top of it which is a very javascript heavy website can be very taxing on the puny ARM CPUs of these small SBCs, particularly the old ones. It is not for nothing that the standard DE on RaspberryPi OS is not XFCE but based on something even smaller such as LXDE/LXQt. And running TH-cam using something like Minitube, VLC or mpv (with yt-dlp installed) should be doable.
Fair point..... I also think Chromium uses GPU acceleration in Raspberry PI OS, which FreeBSD doesn't and won't likely to, as it uses software only which, as you say will struggle....
Come on... the pkg thing is minor. Has nothing really to do with Freebsd but rather when certain keys or certificates were generated. The presumed system time is older than when keys were generated and packages signed. Being that is relevant the first thing you should be setting up is NTP to retrieve the time and date. I've had web sites not work for the same reason on a laptop whose battery backup died.
Vieweing the video again, it's obvious that pkg+http is used for accessing the package repository for 14.0, at 3:09, while pkg+https is used for 14.1, at 5:42. In other words, correct time is more critical for 14.1 than it is for 14.0.
Well, why not use FreeBSD's built-in time sync features? One to sync the time at boot (required in this case, since regular NTP won't start if the date is way off) and then the service to keep it in sync while running:
sysrc ntpdate_enable="YES"
sysrc ntpd_enable="YES"
I use that naturally on every BSD box I use, what threw me was all the previous installs to the Pi worked out of the box, and this one was a non-starter.... until the date issue was recommended .
I view FreeBSD on X86/64 as a separate thing to the PI, as it should be good to go straight away as it is for a different client market.... someone casually trying out FreeBSD would be greatly put off by the experience.... it's a given for the PC or Server that some configuration is in order, but for the PI it should be already configured to a certain degree.....
Don't forget sysrc ntpd_sync_on_start="YES" is a thing.
ntpd -q -g on the command line after network connection is made. Works on wired ethernet connection fine, yet I have problems using a USB wifi dongle with an access point wifi connection problem.
I have to manually connect to wifi access point then issue :
ntpd -q -g command to set date and time to current value.
Someone help and work with me to port Openbsd or Netbsd cy43455 43456 wifi driver to FreeBSD. I am reading Joseph Kongs book on FreeBSD device drivers and also ran the sample freebsd dummy device driver example.
openbsd bwn device driver
Nice video 🙂
I hope that you are doing well and getting/feeling better
Thank you, yes.... I recently went for a checkup and the Bells Palsy seems to clearing up nicely....give it another two weeks they said...
Thanks for the video Christopher ! Seems like it needs a little polishing, at least for ARM version.
Hi Jeff, it does need a bit of love....
And then we all remembered BSD is for racks, and the 'sport' of getting it to run at all on an SOC device is what keeps us alive.
I think FreeBSD needs to get the Arm thing off to a tee as that will be a big player in the tech space....
arm is likely the future of most computing, so arm is really important to get right.
That said, I have a freebsd install on my raspi 3 working as a nice little server and it works flawlessly.
@@RoboNuggie But Raspberry pi IS not the BEST ARM processor to use with. I think It needs some driver twerking as well.
Oh I think OpenBSD also has wifi support for the Raspberry PI and specifically the PI 400. I'm all for using the best OS for the job while honoring your personally held beliefs.
❤
❤
Great video as always.
Wondering if you can do one for NetBSD 10 on R Pi 400. Huge improvements on the ARM ports are one of the big changes amongst the many in the new release.
Thanks.
That's very much a possibility - it won't be for a while, but I'll put it in the ideas list!
Makes me wonder if 14.1 is okay on amd64 systems. I had trouble upgrading to 14.0 a few months back, but that was likely my fault. I'm still finding things that were installed but aren't now.
TBH I've become a massive fan of these cheap mini PC's that are out there. The N100 CPU is amazing, and many of these boxes workout cheaper than a RPI5, more compatible, less hassle to setup, the list goes on.
O meed to have a look at one of these...
Same. I have one of these running Proxmox and I love it to death! Both cheaper and faster than the top performing SBCs, compatible with everything, no need to buy cases, etc. How can one not love them?
I agree with your pain points. I mean the RPI4 has been out for quite some time so basic things like wifi should be working. I have some RISC-V SBCs that function better than FreeBSD on the RPI4
It is head-scratching as to why progress has been slow....I've yet to look at RISC-V.... I need to :-)
There is a bug in firefox build later versions that does not include libm.so . So you need to have
"LD_PRELOAD=/lib/libm.so.5" exported in you shell environment.
Ah, interesting....... I'll give that a try! Thank you....
I'm actually a little disappointed that the RPi400 doesn't have a Real Time Clock (RTC) in it - there's plenty of room.
Well, yes... as it was deemed a desktop replacement it should have had one....
My main issue with the BSD's and ARM is the lack of GPU support. I can live with a dongle for wifi but we really need GPU support for a descent desktop.
rk3399 have a bsd gpu support.
I have struggling the last weekend with the pkg problem, and yesterday after try and error, I discovered, as it is done in the video the date must be setted otherwise it will not work.
I try tu use USB tethering , however the DHCP settings reset after each reboot.
I've been told the date thing was the result of a fix to allowing wrong date, but perhaps NTPdate should have been set to automatically allign time.... I
I tried to install FreeBSD on a Raspberry Pi 400 a couple years ago and there was definitely some strange behavior, one being it failed to correctly set the resolution on my monitor.
That can be a funny one, I learned you have to edit a config file in the PI's Boot partition....
14.0 breaks the standard for pkg/https because of the date being wrong. One should always run ntpd / ntpdate on raspberry pi whether linux or bsd :)
It looks like 14..1 fixed that gaping security hole (wrong time)
I hadn't thought of it like that.... I suppose it makes sense.... but all the previous installs for as far as I can remember for the PI, it always went without a hitch....until this one.
Oh well, the next time I will be prepared :-)
Well, to be fair things like full blown Firefox and worse: trying to run TH-cam on top of it which is a very javascript heavy website can be very taxing on the puny ARM CPUs of these small SBCs, particularly the old ones. It is not for nothing that the standard DE on RaspberryPi OS is not XFCE but based on something even smaller such as LXDE/LXQt. And running TH-cam using something like Minitube, VLC or mpv (with yt-dlp installed) should be doable.
Fair point..... I also think Chromium uses GPU acceleration in Raspberry PI OS, which FreeBSD doesn't and won't likely to, as it uses software only which, as you say will struggle....
Come on... the pkg thing is minor. Has nothing really to do with Freebsd but rather when certain keys or certificates were generated. The presumed system time is older than when keys were generated and packages signed. Being that is relevant the first thing you should be setting up is NTP to retrieve the time and date. I've had web sites not work for the same reason on a laptop whose battery backup died.
Freebsd is for x86 pensioners.
lol, well....