HAIKU OS

Since my studies in the nineties, I was an admirer of BeOS, the BeBox and everything close to this sort of technology. I never could afford a multi-processor machine like the BeBox, so it was remaining a dream, until BeOS and BeBox suddenly disappeared from the scene. This was long before Linux was a thing. 

Beos, was resurrected by the company Yellowbites http://yellowbites.com/beos.html and never gained the success it might have deserved. 

Some fans (no me though) persisted and created a binary compatible clone of BeOS, called HAIKU.
I followed that project on and off, until the Beta1 release. This is when I decided to try HAIKU on hardware myself. When saying on hardware, I mean on hardware, not in a virtual machine.

In my yard of "no longer used, but too good to be scrapped" computers, I found an AMD C-Series APU board with 4GB. This boardd, with a 500GB HDD was the perfect candidate for an installation of HAIKU OS R1/Beta1.
I played with it for a while, and put it aside when other stuff came up. That was many months ago.

Today, I remembered the little box and got it running again. A presumable simple software update, which I expected to have happened over the many months, failed. Hmmmm, strange! What's going on? Oh, there is a Beta2 version available, which does not install with the SoftwareUpdater provided in the GUI. If only I had read this https://www.haiku-os.org/get-haiku/r1beta2/ before ;-)

Anyway, this is what I am presently doing/waiting to finish. The manual upgrade from Beta1 to Beta2. I liked Beta1 a lot, so my expectations are high for Beta2.

When I was playing with Beta1 before, I had plans to port the f2c Fortran to C converter to HAIKU. The sources are still in my home directory. The intent is still present. I might need to check if there is a newer version of f2c before I start the project.

This post was written using the HAIKU machine with the browser WebPositive, while the machine was upgrading from Beta1 to Beta2.

UPDATE:
The machine is not running HAIKU R1/Beta2.

Old Laptop with Raspberry Pi Desktop

Some months ago, I wrote about running FreeDOS on semi-old hardware. What do I mean by semi-old, for DOS, this hardware would have been hyper-modern, while the hardware would severely struggle running modern operation systems. In order to transfer data into the DOS partition of those old laptops and netbooks, I used a Linux Mint installation on a separate partition. The netbooks performed sufficiently satisfactory to leave those as is. However, the HP Compaq nx6110, which had the best hardware support under FreeDOS was just a pain to use with Linux Mint. 

When installing my Raspberry Pis, I noted that another OS was available for download from the Raspberry Pi Foundation, namely a PC/Mac hardware version of  their Debian GNU/Linux adaptation. Seen that on a RPi1B+ this OS run fine, I thought to give a try to install it alongside the FreeDOS partition. Before you try, this did not work... I could not boot later on.

As a test, I decided to overwrite the FreeDOS partition and install the Raspberry Pi Desktop on the entire disk. That in fact did work, i.e. it booted.

Nothing is straight forward in this world. Neither was the install of RPi Desktop. As I wrote, it booted, but, it did not show the menu-bar. Pretty useless at that stage. 

Solution: 

• press <ctrl><alt>t which will open a terminal
• now delete the directory ~/.config/lxpanel -- if you want to play it safe do this:
• cd .config
• rm -rf lxpanel
• now manually start lxpanel in the background by typing: lxpanel &
• you can now restart your computer by either typing reboot in the terminal of use the item in the menu

You might notice that the panel looks different to the rest of the GUI decorations. This can be changed by right-clicking on the panel and open the Panel Settings. In Panel Settings there is a tab Appearance. Click the radio-button which reads "System theme" . That should do the trick.

Another problem I ran into is hardware related to this particular laptop, namely the built-in broadcom b43 WiFi adapter. This is not generic to RPi Desktop, therefore, I wont further discuss the topic here.

RPi Desktop packaged in February 2020, hence, I highly recommend doing a full system update/upgrade.

Here is the easy way, in a terminal type

• sudo apt-get update - this updates the package manager's database
• sudo apt-get full-upgrade - this does what you believe it to do and may take a while
• reboot

Personally, I like the package manager "synaptic". Install it by typing sudo apt-get install synaptic in a terminal window. Once synaptic is installed, open it, it should be in the Preferences menu, and hit the "Reload" button. This again refreshes the database content. Hit the "Mark all Upgrades" button and when it is done the "Apply" button. After a reboot, very likely a kernel was installed, you might find the Raspberry Pi Bookshelf and other goodies in the menues.

My experience with RPi Desktop OS on this old Celeron M laptop is pretty good. Even Chromium performs OK-ish. However, Chromium likes to do stuff in the background, which drains resources and gives a slightly sluggish experience at times. It is certainly advisable to install a more lightweight browser.

LibreOffice and Thonny work nicely. Samba (smb) works out of the box and is integrated in the file manager pcmanfm.  The openbox window manager leaves enough resources for other processes so that working in GUI applications results in acceptable performance. However, using a single CPU core laptop with just 512MB RAM, one should be cautious about the available resources, i.e. not too many heavy applications open at the time.

Classic work in terminal windows, such as writing code in a text editor, using make and running executable, is really no problem what so ever.

Earlier, years ago, I used this particular laptop with a pure Debian installation, which to the time was a good daily worker. Not much has changed, beyond the added tools.

So, if you are looking for an alternative OS for old hardware, give it a thought, maybe RPi Desktop is a solution for you.

Raspberry Pi 400 as Desktop Replacement

The audio issues from the former posts set aside, after some time using the RPi400 I came to the conclusion that is can be a pretty good desktop replacement for some regular stuff.

First to mention, I am not a gamer, not at all. My use of computers is somewhere between doing online social media things, regular office work and programming.

Besides watching videos, which requires audio, bringing us back to the audio issue, all other of my online needs are served fine by the RPi400.

On audio, I found a USB audio dongle which does play audio fine. However, the alsamixer is not able to control this particular device, therefore, the audio volume cannot be adjusted from the OS. My speaker has got a volume potentiometer, therefore, this is not a big deal in my daily life. However, it is not a solution for getting decent Bluetooth support.

The keyboard is good, although it appears to be a little bit smaller than others, which it is not. However, for unknown reasons, sometimes a keystroke is not recognized, in particular lighter keystrokes. From my experience, I create more typos than I used to with other keyboards. The solution that I found is stronger hammering on the keys, which however slow me down a little bit. Anyway, this is something I can live with and learn to adapt to.

The mouse is very lightweight. In the beginning that felt strange or even cheap. However, this strange feeling, in my view, came from the original mouse sensitivity settings in the GUI (openbox). In the "Preferences" menu, under "Keyboard and Mouse", I reduced the "Acceleration" from 5.0 to somewhere between 2.0 and 3.0. With less acceleration, the mouse feels a lot more comfortable to me. Also, the lack of weight does not play a role any longer, at least to my taste.

My RPi400 is configure to boot from USB. I am not repeating the method here, it can be found easily with any internet search engine. My choice was a SSD in a USB3 case. This gives a real speed boost over the SD-card as mass storage. Further, it allows for a lot more storage than on an SD-card.

Another advantage of an SSD is the safety of your data, due to the controller built in an SSD drive.

If I recommend any change or addition to a RPi400, this would be the one, get a USB3 SSD drive.

Networking works fine in principle. 

Nothing to report about Ethernet, it just works.

WiFi, however, suffers a little bit from the design of the RPi400. Don't get me wrong, it does work, however, there is an issue worth to mention. The SoC is cooled by a big aluminium plate, which sits under essentially the entirety of the keyboard. In terms is passive cooling, this is excellent! However, this also provides a decent shield for the 2.4 GHz and 5 GHz WiFi signals. My RPi3B+ in a plastic case, receives my WiFi access point a lot better than the RPi400 in the exact same place on my desk. Network throughput is therefore lower with the RPi400. In case I am running a system upgrade, I therefore have an Ethernet cable handy, so that in case, I can full bandwidth if needed.

I am a longtime Linux user. Therefore, I am used to a certain set of tools. Up to know, I was able to find everything I needed in the repositories for  Raspberry Pi OS (raspian buster).

For reasons of accessibility of RPi specific tools, such as Bookshelf and Mathematica, I opted for the 32-bit version of the OS. 

One of the first tools I installed in addition to the preinstalled programs was synaptic. This package manager give an easy overview of what is available and what is already installed. It makes it very easy to add applications you will find helpful in your daily computing routine.

While my RPi400 suffices my present needs, in the future it is very likely that it will be extended by means of a powered USB3 hub, e.g. for card-readers, webcams, DVD-RW drives, etc.

Raspberry Pi 400 audio issues update

Bluetooth remains still unsolved beyond what I was writing earlier.

In order to get some sort of audio output, I changed back to the only HDMI monitor having speakers in my possession. After the removal of pulseaudio (apt remove pulseaudio), the monitor is perfectly fine to use for sound playback, however, the audio from those tiny speakers is pretty poor. I guess, it is what it is.

Hopefully the Raspberry Pi Foundation will solve the Bluetooth issues with the RPi400 as soon as possible.

Raspberry Pi 400 audio problems - USB not the solution

In my earlier post, I as speculating if the use of a USB sound card would be a possible solution to the audio problems of the Raspberry Pi 400.

Well, it is not!

The audio was playing, however, at a terrible quality, not worth further talking about.

While the RPi400 was never meant to be used in my amateur radio setting, it now shows clearly to not be suitable for such use at all. The only thing still untested would be SDR devices such as the SDR-Play RSP1A.

Seen that a simple audio dongle does not work well, I have serious doubts about any of the SDRs being better supported,

If the Raspberry Pi Foundation is reading, please consider adding an AV jack to a future version of the RPi400. The form-factor of the device is excellent, having it performing similar to a RPi3B+ in respect to audio would make this device usable for not just the ham radio community but also so many more folks looking for some audio abilities of a device.

Raspberry Pi 400 (audio issues)

So, the RPi400 came in. First of all, is it worth the money? Yes it is. The device itself has a good, i.e. reasonable, weight to it, thanks to the internal heat-sink. The keys feel very good and typing is on those is a pleasure. The mouse, meeeeh, well, feels a bit cheap, works well though. In my view, the cheap feel of the mouse comes from its lack of weight. Reducing the mouse acceleration to 3 already helped a lot. I might be temped to open the mouse up and add some weight to it, e.g. by gluing steel nuts to the inside of the case.

I love the size of the device, just perfect. Have a look at my before (Raspberry Pi 3B+) and after setup.

The old and the new

The photographs show my old RPi3B+ setup with a 3.5" external mechanical 320GB USB2 HDD and the RPi400 with a 128GB Kingston SSD in a USB3 enclosure.

The RPi400, having USB3 ports, can benefit from the SSD in a USB3 enclosure. Further, the RPi400 can boot from USB devices. Therefore, the speed of the combination is really close to a decent desktop PC. 

Now, I am appear to be full of praise for the new device. However, beyond the disappointment with the mouse, there is something else which is close to being a deal breaker, at least when running Raspberry Pi OS. That deal breaker being the difficulties of connecting audio output devices, aka speakers.

The RPi400 does not have an analog AV output, which all the other Raspberry Pis have. Hence, there is not way of connecting a wired audio connection, e.g. active speakers, to the RPi400. Lets forget about HDMI for a minute... Well, no problem, you may think, the RPi400 got Bluetooth... RIGHT! Yes, it got Bluetooth, however, the implementation in Raspberry Pi OS does not connect to BT audio sinks as easily.

It took me the better part of the evening, despite the posts about the issue I found on divers fora, to get a BT speaker connected. And even then, the result is less than perfect. My way is sufficiently satisfying to me, however, this might not be the case for someone expecting an OOB experience.

Here is what I had to do to get to the point of semi-happiness:

1. in a terminal type: sudo apt install pulseaudio-bluetooth-module
2. add "Volume Control" to the TaskBar, next to "Volume Control (ALSA/BT)" 

Item 1 will add all the necessary programs and drivers to the system.

Item 2 will give you control over the volume of the audio played out. Somehow, the ALSA/BT panel item does no longer function with BT devices, however, it is necessary to select a BT device as an audio sink. Controlling the volume itself is now done with the 'other' volume control icon, but not in a way that is desirable... Right click on the icon and " Launch Mixer". This will open a terminal with alsamixer. While this works, perfect it is not.

A possible solution could be using a different OS. However, this comes with some drawbacks itself. Raspberry Pi OS is optimized for the hardware and comes with some very interesting software packages, e.g. Mathematica or the RPi Bookshelf.

Another solution would be to add a USB sound card to the mix. However, the RPi400 only having 3 available USB ports, of which one might be used for the mouse and another one for the USB-boot-device, there isn't a lot of wiggle room, unless adding a USB-hub. 

In the near future, I will have a look at other operation systems on the RPi400. One of my present favorites might be Ubuntu Mate 20.10.

Raspberry Pi 3B+ USB Boot

Earlier, I describe the use of BerryBoot with an external USB HDD with a RPi (1) B+. To be honest, this was a terrible user experience. While everything worked, this setup was tantalisingly slow. I mean really really slow. 
My assumption is that the USB2 implementation of the RPi1B+ does not reach USB2 speeds, not even close. Presumably the USB ports a run by the CPU, which in itself is relatively low power already. Consequently, I abandoned the idea of running the RPi1B+ from a USB drive.

As an experiment, I used the exact same external USB-HDD and microSD-card with my RPi3B+. What a difference! This setup really resembles a usable desktop computer. 
In my experience, the Raspberry Pi 3 B+ appears to be able to run the USB2 ports at USB2 speeds.
While booting and running of the microSD-card appears to be a little bit more snappy, the combo of BerryBoot and the externally powered 3.5" HDD on USB2 delivers an acceptable user experience.

The obvious advantage of this particular install is the amount of storage available, in my case more than 300GB.  The amount is only dependent on the HDD in the enclosure.

Raspberry Pi OS on USB

Lately, for various reasons, I got into using Raspberry Pis, in particular in combination with the GPIO.
What puts me off by a bit is the fact that the regular RPis used (micro) SD cards. While reading from an SD card might not be that bad, but writing to it, over and over again, will destroy over a short period of time. Thereby destroying the data you stored on it.

For my projects, therefore, another solution had to be found.

In this series of posts, I will document my experiences using various methods and devices to avoid the wear and tear of an SD card.

This first episode reflects on using BerryBoot to boot from and load the OS from USB connected devices.

Using and installing BerryBoot is very simple. Download the archive provided in the above mention link. Make sure you picked the file that fits your Raspberry Pi. 
During writing this article, it appears that the BerryBoot image now changed to a single archive for all variants of the RPi. I have not tested this, since I just a few hours prior to the writing of this post, downloaded the archive for Pi0 to Pi3+ boards.
Anyway, I stick with what I have and what worked for me earlier.

In my present test, I am using a Raspberry Pi 1 B+ with a 2GB micro-SD card as a boot device and a USB-2 HDD enclosure with a 320GB 3.5" hard-disk. The enclosure came with a 2TB disk, which is used in something else by now.
Further, the enclosure is powered externally by a 12V wall-ward. This, of course, is important, since a Raspberry Pi would never be able to provide the power for any HDD.

Following the procedure as set out on the BerryBoot page, an OS will be written to the USB attached device. I opted for a full install of Raspberry Pi OS, as it is presently called.
After having booted "into" the HDD, the experience is certainly less snappy, compared to running the OS from the SD card. However, the mere difference is storage space should put up some questions: 8GB SD card vs. 320GB HDD.
Initially, no swap space was created. So, I decided for creating a swap-file on the root directory of the hard-drive. That did not work. It appears that under BerryBoot, using a swap file is impossible.

A solution to the missing swap-file is to install zram-tools, which will enable a virtual swap into compressed memory.

In following posts, I will discuss various other options for booting a Raspberry Pi from USB devices.