Startup issues with Linux Mint



Thanks.
Log start from 2.9s mark.

[ 2.926219] Btrfs loaded, zoned=yes, fsverity=yes

Can you check again for earlier messages?
If you have nothing earlier, then please generate dmesg.txt after next reboot.
 
Thanks.
Log start from 2.9s mark.

[ 2.926219] Btrfs loaded, zoned=yes, fsverity=yes

Can you check again for earlier messages?
If you have nothing earlier, then please generate dmesg.txt after next reboot.
I do not have anything earlier in the log.

I'll try a reboot session and see how it goes.
 
Very oddly, it rebooted just fine. Was a bit of hangtime on the Mint screen so I thought I was in for the usual cycle of freezing and restarting.

Here's the new output.
 

Attachments

214 seconds to boot into desktop. That's not normal. Please run
systemd-analyze blame >blame.txt
and
systemd-analyze critical-chain >chain.txt and upload both txt files.
 
I ended up doing a full reinstall of Mint, and the problem persists. I'm thinking at this point it's down to the age of the laptop, even though it's only 2 or 3 years old.
 
214 seconds to boot into desktop. That's not normal. Please run
systemd-analyze blame >blame.txt
and
systemd-analyze critical-chain >chain.txt and upload both txt files.
I ran the first command on my Debian system and read thru the text file and the services and daemons that start during the boot process. Took 24.028 seconds. However the time it took to actually start was 1.002 seconds which is great.

How friend, @Fae3iSUx can the output in the .txt files assist you in determining what the hold up is in the startup process?

And, if you don't mind: is this start up issue with systemd it'self / a service or daemon that's misbehaving or simply a lack in hardware functionality due to an older pc?

From the start Post #2 our member @GatorsFan said:
Code:
 The main issue here is "Failed to start up manager"

--And I agree. Yet a fresh installation did not solve the issue.--

With the collaboration that Alienware and Microsoft and Dell have ( AI features, software integration for Windows 11, Deep Windows ecosystem, high refresh rates, and the Alienware Command Center to work within the Windows ecosystem. Perhaps this could be the culprit for the startup issues?

Two system's fighting for dominance? OR like mentioned earlier in the thread, a BIOS update is needed?
 
Last edited:
I ran the first command on my Debian system and read thru the text file and the services and daemons that start during the boot process. Took 24.028 seconds. However the time it took to actually start was 1.002 seconds which is great.

How friend, @Fae3iSUx can the output in the .txt files assist you in determining what the hold up is in the startup process?

And, if you don't mind: is this start up issue with systemd it'self / a service or daemon that's misbehaving or simply a lack in hardware functionality due to an older pc?

From the start Post #2 our member @GatorsFan said:
Code:
 The main issue here is "Failed to start up manager"

--And I agree. Yet a fresh installation did not solve the issue.--

With the collaboration that Alienware and Microsoft and Dell have ( AI features, software integration for Windows 11, Deep Windows ecosystem, high refresh rates, and the Alienware Command Center to work within the Windows ecosystem. Perhaps this could be the culprit for the startup issues?

Two system's fighting for dominance? OR like mentioned earlier in the thread, a BIOS update is needed?
It's not a dual-boot setup. And I have updated the BIOS a few days ago.
 
It's not a dual-boot setup. And I have updated the BIOS a few days ago.
Thank you.

I sure would like to know what is causing the startup issues friend.
 
So would I.

The Alienware thing you mentioned is mildly concerning, because that was one of the replacement brands I was looking into.
 
So would I.

The Alienware thing you mentioned is mildly concerning, because that was one of the replacement brands I was looking into.
Roger that.
How old is your Alienware laptop?

I don't know why network manager is taking 5 minutes to function.
What I can tell you is that I've never seen anything like it in 14 plus years of running Slackware, Debian, Linux Mint and RH based systems.

Perhaps @GatorsFan , @kc1di , @Condobloke or @Fae3iSUx knows why.
 
Last edited:
Roger that.
How old is your Alienware laptop?

I don't know why network manager is taking 5 minutes to function.
What I can tell you is that I've never seen anything like it in 14 plus years of running Slackware, Debian, Linux Mint and RH based systems.

Perhaps @GatorsFan , @kc1di , @Condobloke or @Fae3iSUx knows why.
It's two years old, Alienware m16 R2 (0C91) according to the terminal output.
 
I looked up the specs of your Alienware laptop. That's really a sweet rig!

Have you tried other Linux distributions and gotten the same results?
Is there a TPM chip soldiered on the mobo (motherboard)?
IF so, did you try disabling it?

I found the Owners Manual for you laptop. Good to have on hand.
 


Follow Linux.org

Members online

No members online now.

Top