Day #18 of FreeBSD 15.0 on my Framework 12" (AKA my FreeBSD Journey)
Today was an interesting day! I learned so much!! Some good face-palm moments, too.
These are the three areas I worked on… | Deb Goodkin
Day #18 of FreeBSD 15.0 on my Framework 12" (AKA my FreeBSD Journey)
Today was an interesting day! I learned so much!! Some good face-palm moments, too.
These are the three areas I worked on today.
Sleep Test
I couldn’t update the power settings because the system settings were wonky, with messages saying “unable to load plasma plugin.” But I was able to put the laptop to sleep by selecting Sleep in the KDE menu (I couldn’t find an official name for it).
It went to sleep, and the power button light blinked slowly, which indicated it was in sleep mode. I hit a few different keys to wake it up, but nothing happened. I had to push the power button to get it out of that mode, which caused the system to shut down. I powered it back up, and everything worked. Apparently, this is a known problem.
Work Calls
I used my laptop for three conference calls today on whereby, Meet, and Teams.
I met with Mark Phillips, our technical marketing manager, who was using a FreeBSD Framework 13” AMD on his end. We used whereby, which is his preferred conference call software. It worked perfectly! I shared photos from both sides of our call.
My next meeting was on Meet. I messed up and didn’t allow proper access to my headset. So, when I joined the call, I didn’t have audio. Since this meeting was with another company, I quickly switched to the Mac for the call. I can subject my team members to testing my laptop, but not other companies!
My third meeting was using Teams. I was able to join, and my headset connected correctly. I did not have access to my camera, and I don’t know why. I’ve heard this may work better on Chromium (I was using Firefox). I was in this meeting for 1.5 hours and never had an issue, besides the camera. I’ll try it from Chromium next time.
Boot Environments
After the package upgrade last night, the KDE settings were wonky with the unable to load plasma plugin messages. So, I set the before_upgrade boot environment to be active, so it would boot into that in the morning to revert the upgrade. What I didn’t realize was that boot environment was already active, so it represented the current boot environment, which included the pkg upgrade. I assumed the before_upgrade was fixed and wouldn’t be updated, but I was wrong. After powering up the laptop this morning, the KDE settings were correct. Maybe the shutdown/power on fixed the plugin incompatibility that it was reporting last night. Note to self: Before any major upgrade, save the current boot environment!
WiFi
I decided to switch back to iwlwifi to see if I would encounter the same issues from earlier this month. I switched because the developer working on this heard about my wifi issues, but those were mostly related to iwx. I had switched to iwx after experiencing freezing issues during my Galene call. Anyway, I’ll try out my meetings with iwlwifi tomorrow and report any issues I find.
One positive note about switching to iwlwifi is that Chromium now works!
```
env ABI=FreeBSD:15:amd64 IGNORE_OSVERSION=yes pkg -c /mnt/upgrade/ install -r FreeBSD-base FreeBSD-pkg-bootstrap
```
Then upgrade the base packages
```
env ABI=FreeBSD:15:amd64 IGNORE_OSVERSION=yes pkg -c /mnt/upgrade/ upgrade -r FreeBSD-base
```
Check, if FreeBSD-set-base is installed:
```
env ABI=FreeBSD:15:amd64 IGNORE_OSVERSION=yes pkg -c /mnt/upgrade/ install -r FreeBSD-base FreeBSD-set-base
```
upgrade all other packages
```
env ABI=FreeBSD:15:amd64 IGNORE_OSVERSION=yes pkg -c /mnt/upgrade/ upgrade
```
Temporarily activate boot env and reboot
```
bectl activate -t 15.0
shutdown -r now
```](https://media.bsd.cafe/bsdmmedia01/media_attachments/files/115/674/160/876/526/884/original/ff7283dad4ab279f.png)
