Nah, I run my updates maybe once a week on average. If afterwards something breaks, I simply do a complete Rollback (with e. g. snapshots). If after the next update its still broken, then I start to dig in „what“ is broken and how I might fix it
But as I said, it didn‘t happen to me yet - but I‘m also fairly new to Arch as well, so that‘s at least my plan on how I would go after it.
Rolling release 🤷🏻♂️ there might be updates which cause issues where you might need to rollback, if you can handle that it shouldn‘t be a problem.
I‘m using Arch myself since about 2 months and never happened that an update break something for me - when something broke it was my own fault.
Awesome! Will look to register tonight or tomorrow, when I find the time. Thanks for letting me know :)
Ok. I think Im gonna test it out aswell once migration is done
So the migration to mbin is done or just wanted to fix that first anyways? ^^
Its working since months, so I guess you have the drivers installed. For me I needed the „wayland-protocols“ package to work on my RTX3070
And the obvious once others have pointed out, the kernel parameters
@darth
did test that as well, but didn't help as the kernel didn't boot up at all.
In the end, after also trying to reach out to ASUS Support (and ofc without any proper solution from their side), I did replace my custom built, noname, (trash) motherboard and now it works flawless.
So, I think it was something with the ACPI/DSDT Tables f'd up on the old MoBo and ASUS just couldn't (or didn't want to) fix that...
Alright, no worries! Appreciate you trying to help, thank you
Yep, saw this entries already and tried with it. To no change unfortunately.
Did some research and also found the suggest to try with
acpi=noirq noapic
but also tried to no change.
Regarding the BIOS options, I did also check for these options, bug they simply aren‘t there 🤷🏻♂️ but will look again after those. Got told that this error might be due to the acpi=off thingy
there you go:
https://pastebin.com/kNFqya2L
taken with acpi=off boot.
Since without acpi=off it's not possible to boot and there is absolutely no output after grub (as if the kernel wouldn't load at all) there simply nothing to show ...
Sure. The whole output or something like dmesg -T --level=emerg,alert,crit,err,warn ?
Iptables. Because in the end its iptables, so I learned it from the beginning „the right way“ and i am therefore not locked into one or another