I got curious about the Raspberry Pi serial connection recently so went about getting it to work on mine. It’s mostly for fun but I can see the benefit when I want to find out the IP address of my Pi without having a monitor and keyboard on hand. Plus, I this would benefit the classes I plan on running as I may not have extra monitor and keyboard for the classes.
A new install of ArchLinux on my Qotom went fine until I enabled the SSH server and rebooted it. I had an issue whereby I could not remotely connect to the SSH server until I logged in the first time. After doing some reading online, I saw on a forum someone mentioning the SSH server is probably lacking sufficient entropy to start. So I tried it on my Arch install and voila, it worked.
My recent kernel upgrade for my ArchLinux server failed because my /tmp folder was full and the package manager couldn’t use the /tmp folder to build the necessary modules and tools. Despite knowing this, I decided to reboot the server anyway and that’s when I saw the dreaded kernel panic message making my server completely unusable. However, I knew my data was still safe on the server, it just couldn’t boot up so I did what any geek would do, I decided to fix it.
I’m working on a new project involving a Raspberry Pi Zero W running ArchLinux ARM. The Pi Zero W, being with only 512MB RAM is having issues performing a task I need that must be done in memory using the vendors command line app. I could rewrite the vendor’s app to be able to run on the 512MB RAM but I’m keeping that for the future. Aside this, there might be other apps that need a little more RAM.
Once my ArchLinux Raspberry Pi was up and running with the wireless connection, I now configured to do roaming profiles. Since I will be using this Raspberry Pi in a few locations, having them connect to different wireless networks is a must. The steps to get roaming working is as follows Using the instructions from wireless, create as many profiles as you want however, DO NOT start or enable any of the proiles.
Once all the necessary configuration for ArchLinux ARM is up and running, it’s time to access it over the network. Since I’m on an DHCP network, its best if I can access the Pi without needing to know the IP in advance. This is where mDNS comes in useful. mDNS in short allows you to resolve the name of your machine without needing a nameserver or extra domain. Just by appending .
After installing ArchLinux ARM on my Raspberry Pi Zero W and getting the wireless up and running, I reset my keyring using pacman-key --init because pacman told me so. However, this messed up my entire keyring for ARM packages and nothing could get it working again. After some Googling, I found a solution provided by some kind soul who encountered a similar problem. The command to fix your keyring for ArchLinux ARM is
- OLDER POSTS
- page 1 of 3