waleee-cl has quit [Quit: Connection closed for inactivity]
<colemickens>
I'm connected to a network, but there's nothing in the /etc/NM/sys-conn/BSSID file, and nothing in `nmcli --show-secrets connection show id $example | fgrep 802-1x.password`.
<colemickens>
no idea how I'm connected to it :S
<colemickens>
Oh! I bet this is an IWD thing.
<colemickens>
yup, /var/lib/iwd/{bssid}.psk contains it.
<colemickens>
+1 for runtime data out of /etc :D
<colemickens>
well, I guess thats arguable.
drakonis has quit [Ping timeout: 250 seconds]
ajs124 has joined #nixos-chat
endformationage has quit [Ping timeout: 265 seconds]
rardiol has quit [Ping timeout: 268 seconds]
cransom has quit [Ping timeout: 268 seconds]
cransom has joined #nixos-chat
Guanin has quit [Ping timeout: 240 seconds]
<NinjaTrappeur>
I'm about to renew my desktop's graphics card, is anybody familiar with the current state of the nvidia vs amd drivers on NixOS? Should I avoid either of these brands? (I don't mind using a proprietary blob)
<NinjaTrappeur>
r/either/one/g
<ar>
i have a radeon vii, and it works. had a vega64, and rx480 before that, also worked (with nixos). had r9-280x before that, on gentoo, also worked
<ar>
and no screwing around with blobs being incompatible with a particular X/kernel version
<etu>
The AMD drivers are open source and built into the kernel/mesa. So with a modern card you may need modern versions of said things.
<etu>
While the blobs as ar states can be incompatible and stuff.
<ar>
haven't tried the new 5700/5700xt cards, and i'll probably end up skipping those as they're not really faster than vii
<ar>
(though a lot more efficient, even if at half the vram)
Jackneill has joined #nixos-chat
<NinjaTrappeur>
Right, did not know that. Thanks.
__Sander__ has joined #nixos-chat
__monty__ has joined #nixos-chat
rardiol has joined #nixos-chat
__Sander__ has quit [Quit: Konversation terminated!]
<gchristensen>
hrm. I need to force some udev-executed programs to run sequentially
<gchristensen>
to assign devices sequential numbers
<joepie91>
NinjaTrappeur: another +1 here for AMD. the amdgpu drivers are open-source, and even the proprietary amdgpu-pro(?) drivers afaik are built against the same stable API so that *even there* you don't get aforementioned X/kernel version compat issues anymore
<joepie91>
(you used to get those for the proprietary drivers)
<joepie91>
(but that was resolved with the amdgpu switchover)
<joepie91>
I haven't actively checked up on nvidia for the past 2 years or so, but last I checked they still built binary blobs against specific kernel/Xorg versions
<joepie91>
and the open-source drivers for nvidia are... not great
<qyliss>
Nvidia aren't good players in Linux, and it shows for users -- new graphics stuff (I'm especially thinking Wayland compositers) has either taken years to support Nvidia's proprietary drivers, or flat-out refused to ever implement them.
<qyliss>
So even if you personally don't care about proprietary blobs, your experience is still going to suffer because of them.
<joepie91>
^
<NinjaTrappeur>
Right, thanks for the heads up.
<joepie91>
same story with things like WebGL and Vulkan actually
<ajs124>
gchristensen: which kind of devices? And why does it need to be run sequentially to assign those numbers?
<gchristensen>
block devices
<gchristensen>
and, well, something needs to be sequential. I guess I could have some file I read and lock
<NinjaTrappeur>
wow, yeah, seems like wlroots doesn't support the nvidia proprietary driver. (or the other way around)
<NinjaTrappeur>
too bad, the nvidia GPU seemed more power efficient :/ (at least on paper)
<gchristensen>
nvidia GPUs are really nice
<ajs124>
What are you doing that needs sequential numbers assigned to block devices, if I might ask?
<joepie91>
NinjaTrappeur: note that power consumption numbers originating from Windows may not necessarily hold up under Linux
<joepie91>
due to power management differences in drivers etc.
<gchristensen>
abstracting away physical devices to devices by category and number
<gchristensen>
basically, I have N servers with 12 storage drives, 2 cache drives, 1 boot drive. they all enumerate slightly differently under by-id, by-label, by-uuid, by-path, and even worse of all /dev/sdXY
<gchristensen>
I can examine them and determine if tehy're storage, cache, or boot based on if they're NVME, SSD, HDD and what their capacity is
<ajs124>
And where is the number supposed to come from/why is it important?
<NinjaTrappeur>
joepie91: ack. Well, looks like I'm good to go into yet another rabbit hole. Thanks for the infos.
<joepie91>
#nixos-chat, handing people rabbit-holes since 20XX :P
<NinjaTrappeur>
:P
<gchristensen>
so at the time of installation I want to create some udev rules which make links at /dev/disk/by-intent/{storage,cache,boot}{n} so then my install instructions can be: zpool create tank raidz1 /dev/disk/by-intent/storage{1,2,3} raidz1 /dev/disk/by-intent/storage{4,5,6} raidz1 /dev/disk/by-intent/storage{7,8,9} raidz1 /dev/disk/by-intent/storage{10,11,12} cache /dev/disk/by-intent/cache1 log
<gchristensen>
/dev/disk/by-intent/cache2 and then every device gets the exact same tank configuration with all the correct drives, without having to customize it per chassis
<gchristensen>
or more precisely, the installation instructions will convert a /dev/disk/by-intent/{type}{n} in to a /dev/sdXY and then in to /dev/disk/by-id/{id} path, and pass those paths to the system configuration
<ajs124>
How about type%e. Or is that racy?
Guanin has joined #nixos-chat
<gchristensen>
ooh I'll take a look
<gchristensen>
what is %e, ajs124?
<gchristensen>
dudle is so slow :|
<ajs124>
man 8 udev says it basically does what you want. if there is a device with that name already, it adds a number or if it ends a number, increments by 1
<gchristensen>
oh cool
waleee-cl has joined #nixos-chat
endformationage has joined #nixos-chat
<adisbladis>
ar: I'm running a 5700XT on Nixos :)
<adisbladis>
There are still some bugs, like the occasional non-recoverable freeze
<adisbladis>
NinjaTrappeur: I'd stay away from Nvidia (or anything not in mainline mesa really)
<NinjaTrappeur>
adisbladis: ack, seems like there's a consensus around that here. I'll probably go with a rx590 in the end.
<adisbladis>
NinjaTrappeur: Not a bad choice :)
<adisbladis>
I almost went for one of those too
<NinjaTrappeur>
:)
rardiol has quit [Ping timeout: 250 seconds]
rardiol has joined #nixos-chat
noonien has joined #nixos-chat
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #nixos-chat
Shoubit has quit [Remote host closed the connection]
Shoubit has joined #nixos-chat
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #nixos-chat
avn has quit [Remote host closed the connection]
drakonis has joined #nixos-chat
<drakonis>
i forgot now, but one of our dudes here's running weechat from half a decade ago
<drakonis>
profpatsch whenever he shows up in here
ravndal has quit [Quit: WeeChat 2.6]
ravndal has joined #nixos-chat
Jackneill has quit [Read error: Connection reset by peer]
<qyliss>
fwiw Gitiles (Google's Git web software) will give you tarballs
<samueldr>
gchristensen: I tried (nix-less) to build a GSI using "supposedly reproducible" docker builds, and it was ~40GIB for the .git metadata without git-lfs files
<gchristensen>
lmao
<ajs124>
samueldr: I looked though some of it, but not that much.
<ajs124>
How does he clone the repo?
<samueldr>
the final with-build (that failed to run correctly) size of the folder was ~300GiB
<ajs124>
Doesn't matter, I won't touch this code. Unless it breaks. Which it seems to have done. Seems like I'll just have a vulnerable phone from now one.
<ajs124>
It does? I think I never looked at the website much >.<