Fail to start

hi,



I need help. I did and update and upgrade then restarted my system. Now instead of booting to my system, I’m taken to a terminal instead of the usual login page. Please help me :sob:


  • Parrot Security 6.2 (bare metal)
  • 6.12.12-amd64
  • Lenovo Thinkpad X1 Carbon 7th Gen
  • When booting it says:

[12.531932] i801_smbus 0000:00:1f.4: SMBus is busy, can’t use it!

[FAILED] Failed to start lightdm.service - Light Display Manager.

[FAILED] Failed to start plymouth-quit.service - Terninate Plymouth Boot Screen.

  • Screenshots:

Just a couple questions ~
Is LVM enabled in your BIOS?
Is RAID enabled in your BIOS?

I can speak on the previous as much but the last kernel update is hanging serious delinquency issues on systems pushing LVM and RAID settings. (It’s definitely not fond of the TCM not being disabled and unhidden or safeboot being enabled.

Kernel panics are pretty common. My did the same until both were disabled but took some hours we crawling different fault messages and such.

I was able to boot up to the GRUB screen and if I caught it there could grab 2nd option from the bottom, enter recovery mode and would stop at the ttyl page but with a sign in prompt.
After signing in would them go into my DE.
If I le the boot proceed past the GRUB screen she would either hit the splash screen and kickour / reboot or get blocked on the ttyl screen.

Good luck, hope it helps

thanks for replying

lvm is off

tried booting into recovery

screenshots:



when I enable lvm

greetings,

yes, LVM, TPM, safeboot, fastboot, and RAID all have to be disabled on the latest kernel… any one of them can cause a panic

Rusty, I wanted to follow up on something, You may have attempted this already and you might not have.

When mine was in kernel panic, It would stop at the same black ttyl screen with micro font prompt line that’s showing in your 3rd from the top ss.

In my experience If you will log in with your admin username and root password it will boot into your regular looking desktop environment.

It will be in recovery mode but you have a GUI access to CLI, file manager, browser, etc so you can correct the misconfigs.

There’s were a couple lines in the /default/grub file that I had to correct.

if ttyl login gets you in we can go over that as well.

I would like to say, I’m not there… no harm to your system can come from logging in at ttyl prompt.

That being said, when we start adjusting config files, that’s a different story. The wrong edit can break your system completely.

So, I’m more than happy to share with you what worked for me but it’s completely “at your own risk because again I’m not there with hands on it”.

I found the kernel panic script correction online while I was dealing with the same issue. but before I just ran off jumping in config files, I spent about an hour hour and a half verifying what I was about to do.

I did attach a screenshot just to make sure that exactly What I’m talking is understood.

Let me know if that gets you in your DE Rudy.

***''Full disclosure.
I am a fairly new face in this community. And, though I’m not a newb with Debian, I don’t presume to be at the same level of the developers in here.
Out of respect for ParrotSec and other contributors that make up this community let me be clear about something >
I don’t work for ParrotSec or with any of the developers of Parrot OS/ParrotSec.
My contributions to this conversation or any other, and any possible remedies I share are solely a good-faith exchange between private individuals/friends and without presumption of acceptance of liability.

Of course, We all know that (should) goes without saying but some communities are, for good reason, very strict about such things. I did not inquired directly with ParrotSec before adding any contributions that were not beyond a requests for tech support.

1 Like