artodeto's blog about coding, politics and the world

After almost ten years of great living with it, I went from a x250 to an e14.

I've manage to switch from luks zfs encryption to native encryption and from grub to zfsbootmenu. Of course I've used my archiso with build in zfs support.

Next and most important part, I had serious trouble get 3D and wifi working with my default installation. I could not find anything but I made it. And the reason why all is now working fine is simple "switch from linux-lts to linux".

So if you want to have a smooth 3D party and a working wifi, switch to latest arch linux kernel "5.19.1".

Best regards, artodeto

I am using NetworkManager to work with any kind of network connection.

I found my freedom with the nmtui and it was working fine until today. Today, I needed to connect to an eduroam WiFi. Long story short this is currently not possible that easy with nmtui or nmcli.

Since I try to keep the system footprint small, I have not installed any gui for the NetworkManager.

Thanks to GallaFrancesco, I found a way to connect to my eduroam realm.

Execute the following command in your shell.

nmcli connection add \
    type wifi con-name "eduroam" ifname $(ifconfig | grep -i w | cut -d":" -f 1) ssid "eduroam" -- \
    wifi-sec.key-mgmt wpa-eap 802-1x.eap peap \ 
    802-1x.phase2-auth mschapv2 802-1x.identity "<username>@<realm>"

After that, restart your networkmanager service with systemctl restart NetworkManager.service to ensure the eduroam connection was found.

Finally, open nmtui and activate the eduroam connection. Now, you have to provide your password.

I've created a small howto here.

yay-bin is currently not compatible with pacman 6.

If you update your system, you get the following error

pacman and yay-bin are in conflict (libalpm.so). Remove yay-bin? [y/N]

How to solve it? It is super simple, just build yay from source.

yay -S yay

Check the aur package page for an update.

As written in the official issue ticket, following the way how to solve your conflict locally.

A quick update to figure out the conflicted files. cd into your nextcloud synchronized path

#list conflicted files 
find . -iname *conflic* -type f

You can than decide which file is the one you want to keep foo.bar or foo (conflicted copy 2020-09-09 083407).bar.

See also here and here.