Rhino Linux Forums

Associated tracker issue: https://github.com/rhino-linux/tracker/issues/126

oklopfer created this issue in rhino-linux/tracker

open Important Pacstall update (February 2026) #126

A recent change in upstream Ubuntu's coreutils (via uutils) causes breakage to Pacstall, which prevents it from being able to run *any* commands. We have pushed an [emergency patch](https://github.com/pacstall/pacstall/releases/tag/6.3.9) to resolve this issue, but running `rpk update` may result in Pacstall being unable to update itself. To fix this, please run the following command to update it manually: ```bash LC_ALL=C pacstall -U ``` We apologize for any caused inconvenience.

Associated tracker issue: https://github.com/rhino-linux/tracker/issues/127

oklopfer created this issue in rhino-linux/tracker

open bug(os): wireless network issues due to upstream `linux-firmware` change #127

In a [recent update upstream](https://launchpad.net/ubuntu/+source/linux-firmware/20260123.git1b7b9f6c.0ubuntu), the `linux-firmware` package was broken out into several subpackages: ``` linux-firmware-amd-graphics linux-firmware-broadcom-wireless linux-firmware-intel-graphics linux-firmware-intel-misc linux-firmware-intel-wireless linux-firmware-marvell-prestera linux-firmware-marvell-wireless linux-firmware-mediatek linux-firmware-mellanox-spectrum linux-firmware-misc linux-firmware-netronome linux-firmware-nvidia-graphics linux-firmware-qlogic linux-firmware-qualcomm-graphics linux-firmware-qualcomm-misc linux-firmware-qualcomm-wireless linux-firmware-realtek ``` Due to the way this has currently been shipped, users may lose wireless connectivity abilities. In order to resolve this issue, either install the specific firmware packages relating to your system, or as a catch all, one may run: ```bash rpk S sudo apt install linux-firmware --install-recommends ``` Of course, this will require a functioning network connection; an ethernet connection will suffice. We will include all firmware packages in our next snapshot images, but for an individual system, this may be unnecessary; we therefore are not shipping a hotfix for this at this time, as it is a case-by-case basis. We apologize for any breakage caused by this upstream change.

In a recent update upstream, the linux-firmware package was broken out into several subpackages:

linux-firmware-amd-graphics
linux-firmware-broadcom-wireless
linux-firmware-intel-graphics
linux-firmware-intel-misc
linux-firmware-intel-wireless
linux-firmware-marvell-prestera
linux-firmware-marvell-wireless
linux-firmware-mediatek
linux-firmware-mellanox-spectrum
linux-firmware-misc
linux-firmware-netronome
linux-firmware-nvidia-graphics
linux-firmware-qlogic
linux-firmware-qualcomm-graphics
linux-firmware-qualcomm-misc
linux-firmware-qualcomm-wireless
linux-firmware-realtek

Due to the way this has currently been shipped, users may lose wireless connectivity abilities. In order to resolve this issue, either install the specific firmware packages relating to your system, or as a catch all, one may run:

rpk S
sudo apt install linux-firmware --install-recommends

Of course, this will require a functioning network connection; an ethernet connection will suffice.

We will include all firmware packages in our next snapshot images, but for an individual system, this may be unnecessary; we therefore are not shipping a hotfix for this at this time, as it is a case-by-case basis. We apologize for any breakage caused by this upstream change.

Excellent! I have created a GitHub issue for this bug, our next snapshot images will include all firmware by default.

A recent change in upstream Ubuntu's coreutils (via uutils) causes breakage to Pacstall, which prevents it from being able to run any commands. We have pushed an emergency patch to resolve this issue, but running rpk update may result in Pacstall being unable to update itself. To fix this, please run the following command to update it manually:

LC_ALL=C pacstall -U

We apologize for any caused inconvenience.

@lupetto3 it is almost certainly due to this recent change: https://www.omgubuntu.co.uk/2026/02/ubuntu-26-04-firmware-split

linux-firmware has been split into the following packages:

linux-firmware-amd-graphics
linux-firmware-broadcom-wireless
linux-firmware-intel-graphics
linux-firmware-intel-misc
linux-firmware-intel-wireless
linux-firmware-marvell-prestera
linux-firmware-marvell-wireless
linux-firmware-mediatek
linux-firmware-mellanox-spectrum
linux-firmware-misc
linux-firmware-netronome
linux-firmware-nvidia-graphics
linux-firmware-qlogic
linux-firmware-qualcomm-graphics
linux-firmware-qualcomm-misc
linux-firmware-qualcomm-wireless
linux-firmware-realtek

You will need to install whichever of those -wireless packages applies to your system. We have confirmed this with other users at least in the case of the Intel set.

@Rondarius thank you so much for testing this! So we can conclude that:

1. The WiFi issue is due to the Mobian kernels, which do not have the firmware built in directly, unlike my older okpine kernels, but mine seem to struggle with Lomiri on 2025.4, which is why we switched to the Mobian ones
2. The Lomiri black screen for 2025.4 on the PinePhone is definitely a hardware acceleration issue, the PinePhone Pro does boot it correctly

I will see what I can do about fixing both of these problems. I have not bumped my kernel in a long time, so hopefully updating it would resolve the issues, but I am so far out of the habit that it will take a bit to fix. I will also take a look if the WiFi issues can be fixed externally without new kernels, and what dependencies might still be needed to get Lomiri working on the OG PinePhone.
Once again, thank you massively!

That suggests that it may be a hardware acceleration issue then after all. I am guessing the Unicorn Mobile images should still work, will do some testing

@rondarius got it. I will try to look into it over the next few days, though it might not be until the weekend (hopefully sooner!). Thank you for reporting the issue, as we have not had a lot of users of the PinePhone images besides ourselves in testing.

A few more quick questions:

1. Do the 4 tuxes pop up at the start, before it goes black, or is it black always?
2. Did you happen to also try a Unicorn Mobile image? If that one boots correctly, then you should still be able to install Lomiri on it after.

We did have to re-split the kernels recently for these new images on the PinePhones, so my guess is that is likely where the issue is happening; that should become obvious if the Unicorn Mobile images don't work either. Unfortunately, my testing on the OG PinePhone was limited this development cycle and I was mostly focused on the PineTab2 and PinePhone Pro, so that is my fault for not thoroughly testing it more.

In any case, this will surely help us with releasing updated images, so once again thank you for the report!

Hello Rondarius, good to see you! First boot on the Lomiri images, for whatever reason, takes several minutes to fully load. The PinePhone may be extra slowed due to lacking GPU acceleration. I would try leaving it for upwards of 10 minutes, and if it still does not work, then get back to me on this thread.

Cheers!

PINK, specifically hex code #FF00FF aka RGB 255,0,255

Completely agree. We have said as a team that while Rhino Linux is not the only distro with Pacstall, it is the distro made for Pacstall. Pacstall has also developed significantly to adapt to Rhino Linux.

https://github.com/rhino-linux/rhino-setup/pull/85

oklopfer opened this pull request in rhino-linux/rhino-setup

merged fix: nix install #85

https://github.com/rhino-linux/rhino-setup/commit/60fb69103747241eba06bf2558d61fab3bea04be

0 oklopfer committed to rhino-linux/rhino-setup

fix: nix install (#85)

fix: nix install