Un-fucking Arch Part 4
Part 4? I think it’s Part 4…
I had a long weekend this weekend, in order to do some family stuff, so I took Friday and Monday off. On Saturday, I found myself with some free time, so I thought “I’ll piss about with my homeprod a bit, do some container upgrades, that sort of thing” and then I thought “well I’ll do a pacman sync on my laptop first”, and when I did a reboot, everything remotely network related froze afterwards.
After some fooling around, I narrowed it down to that the wifi driver appeared to be freezing up (stuck threads) after connecting. I can use the laptop fine with an ethernet cable if I uninstalled plasma-nm which stopped it connecting. I later figured out it had nothing to do with Plasma, or NetworkManager, which I unfortunately only found out after completely ratfucking my Plasma install (it’s still not 100% where I want it, I should have documented my changes better, my main complaint at the moment is that the touchpad is still not quite right).
I triend downgrading to the LTS kernel, that didn’t help. I tried switching wifi drivers, and a bunch of other things, until Avi suggested downgrading to the kernel package that worked. I… did not even know that was a thing on Arch, in fact every experienced Arch user I asked about it always screamed at me that you always sync everything, never leave any packages un-upgraded or things will go wrong.
Anyway, that fixed it, and it turned out I ran into an issue with 6.6.5, and regrettably the issue was also backported to the 6.1 LTS kernel I tried as well. They fixed it this morning and after work I installed the 6.6.6 kernel and all was well.
For future reference, the connection file in /etc/NetworkManager/system-connections/ was what I needed to blow away to stop it attempting to connect after I added the wifi config directly into NM.
fwagglePublished:
Modified:
Filed under:
Location:
Horsham, VIC, AustraliaNavigation: Older Entry Newer Entry