Varen

joined 1 year ago
[–] Varen@kbin.social -1 points 5 months ago (2 children)

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

[–] Varen@kbin.social 1 points 6 months ago* (last edited 6 months ago)

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.

[–] Varen@kbin.social 2 points 6 months ago (2 children)

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.

[–] Varen@kbin.social 1 points 6 months ago

Awesome! Will look to register tonight or tomorrow, when I find the time. Thanks for letting me know :)

[–] Varen@kbin.social 1 points 6 months ago (3 children)

Ok. I think Im gonna test it out aswell once migration is done

[–] Varen@kbin.social 1 points 6 months ago (5 children)

So the migration to mbin is done or just wanted to fix that first anyways? ^^

[–] Varen@kbin.social 2 points 7 months ago

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

[–] Varen@kbin.social 2 points 9 months ago

ok took me 3 days to test, apologies :D
but unfortunately, no, doesn't work. Even the "old" iso stucks at the exact same position with the exact same behavior :(

[–] Varen@kbin.social 2 points 9 months ago* (last edited 9 months ago) (1 children)

got some news. I don't think, that it might change something, but who knows.
I added in grub the option "insmod progress" (which I found by googling somewhere). It should show, if kernel and initrd do load or not and now I can see, that the vmlinuz and initrd are loading to 100% and after that it hangs. So it looks like the kernel loads but then stucks.
As said before, I don't think that this might change something in regards to further tests with my actual mobo, but I didn't want to left that out ...

[–] Varen@kbin.social 2 points 9 months ago

Oh I absolutely can relate haha
Maybe one day I‘ll be here asking dumb questions again, watch out 😁

[–] Varen@kbin.social 2 points 9 months ago (2 children)

Alright, no worries! You invested so much time and effort trying to help me out, I can‘t thank you enough for that, really really appreciate it much!

[–] Varen@kbin.social 2 points 9 months ago (4 children)

Yeah I already got one in mind and looked it up on linux-hardware.org - any other option I‘d have to make sure the next one is alright? (Besides socket and compatibility with my other hw)

 

got told to crosspost over here to reach more people:

https://kbin.social/m/linuxquestions/p/4631784

I don't know if and how crossposting functions in kbin/lemmy, so hopefully it'll work that way

view more: next ›