<samplet>vagrantc: I think the CPUs have the microcode built-in, so if you are willing to treat it just as hardware that you can’t update, it works with free software. At least, that is the rational why old ThinkPads “Respect Your Freedom” even though they require microcode.
<samplet>AIUI, lots of devices have all kinds of non-free firmware. Right now, the FSF only takes issue with the kind that has to be explicitly loaded. (The rest is considered unfortunate but tolerable.)
<vagrantc>i *thought* some of the newer ones *required* getting regular updates ... but i guess i don't know how that could even be technically enforced
<samplet>It could be. I don’t pay much attention to new processors these days. I suppose you could have a two-stage thing where a small processor loads the microcode for the “real” processor. (I hope no one from Intel is listening!)
<Marlin[m]>Aren't there any workarounds or recommendations for newer amd cards? I'd love to run guix on bare metal, but it linux libre always breaks on my pc
<Marlin[m]>i'm mostly stuck with debian and the firmware package atm
<Marlin[m]>and libre compatible hardware is way too expensive where i live, at least for desktops
<fosterite>Hello, I did `guix package -i stumpwm` but it's not showing up in the desktop session list at the login screen. I see that the stumpwm package makes an xsession, but I don't know how to check if it's in the right place
<Marlin[m]>any way i can compile a different kernel on guix?
<brendyyn>calher: thats what the debate is about. there is no proof that there is a violation, but also no proof that there isnt
<calher>I'll use it to run proprietary web applications.
<rekado_>Marlin[m]: yes, you can compile a different kernel and specify it in the operating system configuration.
<rekado_>calher: if you’re interested (and have lots of time) you can read up all about this on the various mailing lists. It was a bit of a meandering discussion, and in the end it’s all about Russel’s teapot.
<calher>rekado_, is that some sort of term related to Bertrand Russell?
<g_bor[m]>I am trying to update ovmf. The proble is that the new version depends on openssl, bundles it as a git submodule, and insists on building in as part of the build. What would be the proper process here. I also have a similar problem with nominatim, which bundles osm2pgsl, and the build heavily depends on it. It seems that in these cases I can't get by without pathcing the build system if I want to unbundle. Wdyt?
<nckx>g_bor[m]: The latest Borg does the same thing. I'm patching the build system, but it's not enjoyable.
<g_bor[m]>nckx: Ok, I did dig into the source a bit, and ovmf needs a very specially built version of openssl. So it would be needed to path the build system in nontrivial ways, and create a special openssl package, with all the magic already implemented in the EDK II build, and that version is not useful for general use, so could not replace the system openssl. What is your recommendation?
<g_bor[m]>Some of the main differences are some architecture specific flags, optimizing for image size, disabling syslog.
<g_bor[m]>I believe it would be not so hard to define a version openssl with that...
<g_bor[m]>EDK II is a very special build system, I am not into it very much... I guess for now I will send a working patch, and mark it as help needed.
<nckx>g_bor[m]: I'm surprised (well, that's not the right word…) that patching the EDK build system is the most work here, not creating the openssl variant itself :-/
<nckx>In the end, you're the one doing the work so you get to decide. I'd be less weary of using the bundled library ‘for now’ (examples of ‘XXX TODO unbundle some day’ abound it Guix) if the library in question weren't openssl.
*nckx is all for Doing Things Properly, until it amounts to telling volunteers to do a lot more work…
<devilishtype> nckx hey get back to work while you're chatting you can't be contributing to the project >:|
<nckx>devilishtype: I'm not contributing as it is; turns out that typing Scheme with one hand is much harder than telling people what to do on IRC. :'-(
<devilishtype>oh man, this is going to turn into an interesting discussion if whether that's a paraphilia or not.
*nckx knew the moment they hit Return that they had made a Mistake.
<nckx>Of course a search returns the tantalising snippet ‘Running startx complains about a missing X, since xinit looks for X in its /gnu/store directory instead of my profile one. Anyone knows how to fix…’
<bt`>At current when using Guix my system just bakes until it crashes if I close the lid. It's not a issue on other distributions, just some strange interaction between my librebooted x60s and Guix. Along with my graphics issues which I still haven't figured out.
<nckx>So I just started the Guix System installer in a VM, and ‘grep CPUFREQ /run/booted-system/kernel/.config’ (that last file name is a free life hack for y'all on Guix) and it's built in, so (as I suspected) acpi-cpufreq isn't relevant here.
<nckx>devilishtype: YES! I was literally just distracted by that warning in my dmesg.
<nckx>It's just funny because the difference between ‘ondemand’ and ‘conservative’ is so preciously subtle, and then here's this ‘performance’ thing that one might assume is ‘biased somewhat towards high frequencies’ but nope, it's oven time.
<nckx>(bt`: That being ‘solved’, I'm still interested in your new thermald build, and could you run it again with ‘--rounds=10 --check’, please and thank you so, and you should probably set up suspend on lid-close if you want it.)
*nckx AFK for a while because OMG does their hand hurt.