Solved Don' borked Asahi Linux right after a update..

[Rocketing-warp9]

Hi all,

Alrighty! Just got a new M1 MacBook Pro and put asahi linux on there, with KDE Plasma. I ran an update from discover and it froze at 11 percent after a restart as the packages were upgrading at some sort of off-line installer.( I am sorry, but for some reason I did not take any screenshots while it was updating) After a little over 10 minutes of no progress had to balk as school was approaching. Now, when I try to load, the system freezes at the starting Plymouth boot screen when I press Esc. Did I just toast it already- full reinstall?

-edit

She's Running and not Borking on startup no more! If you still want to look-- just continue on.

Thanks to all Whom helped!

 

[Fae3iSUx]

No you did not broke it, it seems there's a regression and you need to speak with Asahi developers, obtain new ISO image, maybe reinstall, and so on. Not your fault. But some advanced Linux knowledge may be required to troubleshoot.
Anyway. You bought a new computer to install Linux on it... and somehow you choose the most difficult platform possible, a Apple Mac computer?
Good luck with that.
If you can, return it, buy a Dell, HP, or whatever, smooth Linux sailing will much more likely than hacking a Mac.

 

[Rocketing-warp9]

Eh, What can I say? I like the kit! I've always liked Mac hardware for the most part, and have a few older "intel Machines around. Just like to customize linux a little more on here.

and somehow you choose the most difficult platform possible, a Apple Mac computer?

I was able to reinstall and get what I was going for on there. it works! Thanks!

 

[PuppyHome]

I was able to reinstall and get what I was going for on there. it works! Thanks!

I like your style

 

[Rocketing-warp9]

Oh boy.. Shut it' down and wound up at a Logon-loop

Partitions' whack all over. (there's 2 of' em and mOS won't resize' em.)

Welp.....

Any suggestions for bypassing the logon?

-edit: Seems to happen anytime I remotely try to update- Either through Discover or dnf.
Need to wait for A patch for these I guess.

Moral of the story- Don't update to broken packages

 

[Fae3iSUx]

Sorry to hear.
Maybe get some contact to Asahi team, their IRC or forum. Let them know about this, and start grinding towards a solution.

 

[KGIII]

Any suggestions for bypassing the logon?

While you're on the login screen, press CTRL + ALT + F3 and let us know the results. You can try other F options, but F3 is usually going to work. I know nothing about the OS you're using.

 

[Rocketing-warp9]

Alrighty! off I go!

it enter a bunch to clean my pass off-screen..
PWD ls said I was running as root.

 

[Rocketing-warp9]

As for the system, Fedora 44. I was able to get to a pure CLI-- I think something must have gone borked in Wayland.when I attempted to launch FF, complained about a missing display variable.

 

[Rocketing-warp9]

Alrighty! Did some "Yahoo-Fu" and figured I'd switch to GDM-- Which got me to a Broken KDE desktop and Gnome Desktop.
Errors every which way but loose or working, but at least I'm in!

 

[VP9KS]

Oh, if I had a dime for every time I borked an install, I would be rich! Welcome to the aw Sh#t club. Remember that is one step above the oops club, so we have another graduate. Yay!!

 

[KGIII]

I call it 'learning by breaking', and it's surprisingly effective.

 

[Rocketing-warp9]

Yep! Now just to rebuild plasma.. or Something to get it at least usable!

It keeps complaining about missing paths that go to various components.

FF leads two it... launcher menu is empty, and Icons are broke to bits..

Any suggestions?

 

[KGIII]

We're way outside of my wheelhouse. But I do have some history with Fedora.

I'd start with this, based on Google:

sudo dnf install asahi-platform-metapackage

However, that's Google. I'd still try that first. If I hadn't consulted Google, I'd suggest these commands:

Start with this and work your way down:

sudo dnf upgrade --refresh

sudo dnf check --dependencies

I assume this is still supported:

sudo rpm -Va

Let's see what that tells us.

 

[Rocketing-warp9]

Alrighty! More outputs!

Need to get internet up through the terminal first if it would let me...
It now looks like one of those windows Memes.....

And more from various parts keep popping up.

 

[Rocketing-warp9]

All the error I can sort at the moment.

 

[deb_user]

Discover is, IME, not ready for prime time. I don't use it. For a GUI package manager, Synaptic is much better. I use apt in a terminal. Discover has done unpleasant things in my Debian system. I was prepared for it, because apt had already refused to upgrade some packages, so I tried using Discover just for grins. Discover happily did the upgrades, and then I restored a timeshift backup and was back to usable. Debian Sid sometimes has dependency issues, and it is folly to blindly accept any package manager's suggestions without thinking about them. I expect that some other distros have similar issues at times, especially the nearer to the cutting edge they get. Fedora is about as close to it as it's possible to get.

 

[Rocketing-warp9]

Discover is, IME, not ready for prime time. I don't use it. For a GUI package manager, Synaptic is much better. I use apt in a terminal. Discover has done unpleasant things in my Debian system. I was prepared for it, because apt had already refused to upgrade some packages, so I tried using Discover just for grins. Discover happily did the upgrades, and then I restored a timeshift backup and was back to usable. Debian Sid sometimes has dependency issues, and it is folly to blindly accept any package manager's suggestions without thinking about them. I expect that some other distros have similar issues at times, especially the nearer to the cutting edge they get. Fedora is about as close to it as it's possible to get.

Yep! I guess just a tad bit too-cutting-edge for me sadly Thank you! Will look into synaptic once this mess is handled!

And the RPM Cmd left me this.

Edit- Ironically, the lockscreen still works fine.....

Welcome just popped up on this void..
welp! I guess I am still welcomed to my broken system!

 

[Rocketing-warp9]

After closing some errors...

Plasma DT appeared. In the middle of it-

I guess a corrupted /home folder?

 

[Rocketing-warp9]

We're way outside of my wheelhouse. But I do have some history with Fedora.

I'd start with this, based on Google:

sudo dnf install asahi-platform-metapackage

However, that's Google. I'd still try that first. If I hadn't consulted Google, I'd suggest these commands:

Start with this and work your way down:

sudo dnf upgrade --refresh

That resulted in this-

sudo dnf check --dependencies

This resulted in nothing being printed and went back to bash.