debian mobian not bootable after 2025-04-05 upgrade

[henrythemouse]

The installation was installed via a debian mobian-installer image close to a year ago.
There were over 600 packages to upgrade, previous upgrade was about 30 days prior.
The upgrade process took quite some time, done over ssh.
At least two times during this process, my network dropped and I restarted the upgrade.
The upgrade did finish without any errors.

When I attempt to boot now, the screen goes blank and this message appeared at the top of the screen.

Code:

[    3.010045] OF: graph: no port mode found in /12c0ff340000/typec-portc022

Then the Mobian logo appeared for a split second and disappeared.

The line above was still at the top of the screen. I've allowed the PPP to stay in this state for a couple of hours and nothing has happened.

I have access to the installation by booting into a micro sdcard (mobian) and mounting the main system. 

I'm wondering if any one has seen this message before. Can anyone give me an idea what it means and if there is a solution to this other than re-installing the system?

Thanks, any help is greatly appreciated.

[teekay]

The error appears to be related to the USB port, so it might not be related to your issues. Does dmesg show any obvious errors? I recently (last week) also full-upgraded my mobian, crossed my fingers, and everything went fine and boots fine. The cameras even sort of work now! I upgraded from a December 2024 install.

---

Also, make sure your battery isn't too low, which might cause a shutdown. Try booting up with power cable plugged in.

---

> [ 3.010045] OF: graph: no port mode found in /12c0ff340000/typec-portc022

I assume you typed this in from memory or skimming the screen quickly? The USB type-C port should be at:
/i2c@ff3d0000/typec-port@22

If your device shows "ff34" instead of "ff3d", might be an issue.

[biketool]

The installation was installed via a debian mobian-installer image close to a year ago.
There were over 600 packages to upgrade, previous upgrade was about 30 days prior.
The upgrade process took quite some time, done over ssh.
At least two times during this process, my network dropped and I restarted the upgrade.
The upgrade did finish without any errors.

When I attempt to boot now, the screen goes blank and this message appeared at the top of the screen.

Code:

[    3.010045] OF: graph: no port mode found in /12c0ff340000/typec-portc022

Then the Mobian logo appeared for a split second and disappeared.

The line above was still at the top of the screen. I've allowed the PPP to stay in this state for a couple of hours and nothing has happened.

I have access to the installation by booting into a micro sdcard (mobian) and mounting the main system. 

I'm wondering if any one has seen this message before. Can anyone give me an idea what it means and if there is a solution to this other than re-installing the system?

Thanks, any help is greatly appreciated.

if you have a pl2302 or similar USB->serial board or adapter you can make a 3.5mm trrs headphone port serial line terminal to watch the whole boot on your computer to the failure, or you can buy one in the store.  Just flip the correct paranoia switch on your PPp to get it working, this can be very useful in your case.

[henrythemouse]

The error appears to be related to the USB port, so it might not be related to your issues. Does dmesg show any obvious errors? I recently (last week) also full-upgraded my mobian, crossed my fingers, and everything went fine and boots fine. The cameras even sort of work now! I upgraded from a December 2024 install.

---

Also, make sure your battery isn't too low, which might cause a shutdown. Try booting up with power cable plugged in.

---

> [    3.010045] OF: graph: no port mode found in /12c0ff340000/typec-portc022

I assume you typed this in from memory or skimming the screen quickly? The USB type-C port should be at:
/i2c@ff3d0000/typec-port@22

If your device shows "ff34" instead of "ff3d", might be an issue.

Your are right, it reads "ff3d".

I did try booting while plugged in, result was the same.

As far as dmesg, I don't know how to get that from the old boot partition (it won't boot).
(The current boot card does show  the "ff3d" at line 148, no errors are indicated.)

I do have the boot.log from the last time the ppp booted the main installation,
it has 65 lines and does not show anything I see as unusual.

However, while inspecting the old logs I looked at dpkg.log and found that there were over
2000 entries containing "half configured" and/or "half installed". That could mean that the
upgrade did not finish. I can't think of a way to fix this.

Thanks for your response. It helped me to take a closer look.

---

The installation was installed via a debian mobian-installer image close to a year ago.
There were over 600 packages to upgrade, previous upgrade was about 30 days prior.
The upgrade process took quite some time, done over ssh.
At least two times during this process, my network dropped and I restarted the upgrade.
The upgrade did finish without any errors.

When I attempt to boot now, the screen goes blank and this message appeared at the top of the screen.

Code:

[    3.010045] OF: graph: no port mode found in /12c0ff340000/typec-portc022

Then the Mobian logo appeared for a split second and disappeared.

The line above was still at the top of the screen. I've allowed the PPP to stay in this state for a couple of hours and nothing has happened.

I have access to the installation by booting into a micro sdcard (mobian) and mounting the main system. 

I'm wondering if any one has seen this message before. Can anyone give me an idea what it means and if there is a solution to this other than re-installing the system?

Thanks, any help is greatly appreciated.

if you have a pl2302 or similar USB->serial board or adapter you can make a 3.5mm trrs headphone port serial line terminal to watch the whole boot on your computer to the failure, or you can buy one in the store.  Just flip the correct paranoia switch on your PPp to get it working, this can be very useful in your case.

Thanks for your reply. Now that I've taken a second look the issue seems to be with the upgrade process. See my reply to teekay.