Describe the bug
My old Toshiba Satellite laptop with a new install of Bluefin Stable, fails to boot after updating to the latest image. It works fine with the installed image (43.20251119.1), but gets stuck on the Toshiba flash screen when booting on the updated image (43.20260224.1).
What did you expect to happen?
I expected to be able to reliably boot on the latest image.
Output of bootc status
apiVersion: org.containers.bootc/v1
kind: BootcHost
metadata:
name: host
spec:
image:
image: ghcr.io/ublue-os/bluefin:stable
transport: registry
signature: containerPolicy
bootOrder: rollback
status:
staged: null
booted:
image:
image:
image: ghcr.io/ublue-os/bluefin:stable
transport: registry
signature: containerPolicy
version: 43.20251119.1
timestamp: 2025-11-19T03:19:30Z
imageDigest: sha256:98b0760842cd6d835c9dd563ccb9408bbad0cda461179e0d4c48bf99777ea527
architecture: amd64
cachedUpdate: null
incompatible: false
pinned: false
softRebootCapable: true
store: ostreeContainer
ostree:
stateroot: default
checksum: 1b4ae0baf06e0cee4c31925701de358042e37903a9436bd8d9690ab9137554a4
deploySerial: 0
composefs: null
rollback:
image:
image:
image: ghcr.io/ublue-os/bluefin:stable
transport: registry
signature: containerPolicy
version: 43.20260224.1
timestamp: 2026-02-24T02:23:06Z
imageDigest: sha256:46658709b85157ed1fc4891e9e6c9ccbe9441f9cb6327802fa31d5cb1dff6877
architecture: amd64
cachedUpdate: null
incompatible: false
pinned: false
softRebootCapable: false
store: ostreeContainer
ostree:
stateroot: default
checksum: 4739211491a7711a9e6c9393bd53b7bbdf52bed8ef8b436e4d6ef2d0cb4d881b
deploySerial: 0
composefs: null
rollbackQueued: true
type: bootcHostOutput of groups
Extra information or context
Since I am unable to boot on the latest image, the bootc status text included above is generated when booted on the original image. By watching the boot messages, I can see it generally get stuck on attempts to run sysroot.mount/start. When I manage to enter emergency mode, I can save rdsosreport.txt to a usb stick. There also seems to be some reference to the AMD GPU in the boot messages, so there could be a problem with the latest AMD driver and the old GPU.
I've also included text from fastfetch: fastfetch.txt (from the original image).
Note that the behaviour while booting on the new image is quite patchy. It seems to get stuck at different points each time. When booting on the original image it works fine every time.
Describe the bug
My old Toshiba Satellite laptop with a new install of Bluefin Stable, fails to boot after updating to the latest image. It works fine with the installed image (43.20251119.1), but gets stuck on the Toshiba flash screen when booting on the updated image (43.20260224.1).
What did you expect to happen?
I expected to be able to reliably boot on the latest image.
Output of
bootc statusapiVersion: org.containers.bootc/v1 kind: BootcHost metadata: name: host spec: image: image: ghcr.io/ublue-os/bluefin:stable transport: registry signature: containerPolicy bootOrder: rollback status: staged: null booted: image: image: image: ghcr.io/ublue-os/bluefin:stable transport: registry signature: containerPolicy version: 43.20251119.1 timestamp: 2025-11-19T03:19:30Z imageDigest: sha256:98b0760842cd6d835c9dd563ccb9408bbad0cda461179e0d4c48bf99777ea527 architecture: amd64 cachedUpdate: null incompatible: false pinned: false softRebootCapable: true store: ostreeContainer ostree: stateroot: default checksum: 1b4ae0baf06e0cee4c31925701de358042e37903a9436bd8d9690ab9137554a4 deploySerial: 0 composefs: null rollback: image: image: image: ghcr.io/ublue-os/bluefin:stable transport: registry signature: containerPolicy version: 43.20260224.1 timestamp: 2026-02-24T02:23:06Z imageDigest: sha256:46658709b85157ed1fc4891e9e6c9ccbe9441f9cb6327802fa31d5cb1dff6877 architecture: amd64 cachedUpdate: null incompatible: false pinned: false softRebootCapable: false store: ostreeContainer ostree: stateroot: default checksum: 4739211491a7711a9e6c9393bd53b7bbdf52bed8ef8b436e4d6ef2d0cb4d881b deploySerial: 0 composefs: null rollbackQueued: true type: bootcHostOutput of
groupsExtra information or context
Since I am unable to boot on the latest image, the bootc status text included above is generated when booted on the original image. By watching the boot messages, I can see it generally get stuck on attempts to run sysroot.mount/start. When I manage to enter emergency mode, I can save rdsosreport.txt to a usb stick. There also seems to be some reference to the AMD GPU in the boot messages, so there could be a problem with the latest AMD driver and the old GPU.
I've also included text from fastfetch: fastfetch.txt (from the original image).
Note that the behaviour while booting on the new image is quite patchy. It seems to get stuck at different points each time. When booting on the original image it works fine every time.