<vagrantc>"sudo lsmod ath9k" neither needs sudo, and is a syntax error for lsmod on top of it
<Minall>In the h-node page it says that my wifi device uses that module to work, and it is not loaded by any reason, so since it's not loaded, and my device isn't working, if I load the module it should work
<Minall>modinfo does give me output of the module, it just doesn't load
<vagrantc>usually you shouldn't need to load modules manually
<lprndn>Minall: Concerning ssdm, it's a weird service. sddm-service-type doesn't have a default config so you should add (sddm-service) instead. Or (sddm-service-type (sddm-configuration)). Does it helps?
<Minall>In other systems, to load modules at boot one has to add it to /usr/..., since guix doesn't have /usr for obvious reasons, where can I see if a module is blacklisted on guix?
<gnutec>Try install icecat on guix but the system stop and I just give up. Too big download of packages, no audio, no make. Then I back to Trisquel, but now, with Btrfs clean install. Internet 4G is expencive here in Brazil. How guix_install.sh work?
<quiliro>anyway, if the wifi works with the new usb, it could be that the module was not well read or that the wifi device has something causing it not to work...so if it works and before it did not with the same version of guix, it is probably hardware
<quiliro>but not necessarily. since you fiddle a lot with the system....
<Minall>the installation that I used was faulty, and sayed: Oh, this is a pc, it doesn't need that module, let's blacklist it or something, but the new installation will detect the wifi and don't blacklist the module
<Minall>In case I'm right, then just by adding the module correctly should be enough... but modprobe doesn't seem to work
<quiliro>Minall: the only reason to load that module manually is a bug in guix
<apteryx>Q: if you could use Guix to partition your system HD, would you rather 1) explicitly define the partitions using a 'partitions' field on the operating-system record, or 2) have Guix infer the partitions based on the file-systems defined?
<apteryx>quiliro: thanks for the input. I guess I can start with a 'partitions' field that would defaults to #f and do nothing in this case (the existing operating system configs would continue to behave the same as they do now). It'd also need some special command line flag with big warnings to be "activated"
<Marlin[m]>it complains about missing dependencies when i try to do irony-server-install
<Marlin[m]>isn't the irony-server package supposed to have everything it needs?
<ryanprior>Ah it's possible you might be able to launch the server without having to do irony-install-server, maybe there's package specific docs on that?
<ryanprior>I think irony-install-server compiles the server if it isn't already compiled, which requires that you have all the deps. But the package might propagage all those deps, it might just give you the compiled server.
<ryanprior>I haven't used irony-mode with guix yet, but that's what comes to my mind as to what might be happening?
<Marlin[m]>if i try to type stuff in irony mode, it says there's a version mismatch and asks me to compile it again
<simple_>im interessted in trying guix (currently using arch). im considering just installing the package manager and play with that or using the distro with chroot. is there a clear advantage to one of those two?
<efraim>Installing the package manager is really easy and self contained if you want to get rid of it later
<efraim>In my opinion it's the easier way to get a feel for using guix
<roptat>simple_, I agree, using the distro in a chroot is going to be very difficult, I'm not even sure it's possible
<mbakke>simple_: Once you have the package manager installed, you can experiment with Guix System using `guix system vm`.
<rekado>I found that removing a call to “free” removes a crash of the bootstrap JVM.
<rekado>it’s very ugly to do that and we should agree on whether we are okay with that sort of thing.
<pkill9>grafts confuse me, if i run `guix build love` it returns the store path without building anything, but if i run `guix build --with-graft=mesa=mesa love`, it starts downloading a mix of substitutes and sources
<rekado>my opinion as an amateur and fatalist is: this is just the bootstrap JVM, so it’s fine to have it go up in smoke as long as it gets us to the next stage.
<rekado>pkill9: grafts are very simple. “with-graft” is not.
<rekado>that would cause my-modified-mesa to be built (if it doesn’t exist yet) and then build grafted packages for every other package in the bag that needs mesa.
<rekado>pkill9: I don’t think it tries to be smart at all.
<rekado>pkill9: the request to replace a thing with itself is not a common use-case, so I don’t think we’re trying to optimize that case.
<pkill9>ok, when you say it would have to at least build the replacement, you mean the new grafted input? Why does guix try to build a bunch of other stuff in the package graph when i run `guix build --with-graft=mesa=mesa love`? (im just replacing mesa with itself as an example, or maybe that's causing it to bork?)
<rekado>pkill9: could you pass --dry-run and show us what it plans to build?
<efraim>and depending on how powerful your machine is and how expensive your internet is, you might decide to disable substitutes and build everything locally since the sources are generally smaller than the binaries and change less frequently
<gnutec>efraim: Yes! Thanks. I really don't know that. What about the audio?
<efraim>I don't know, I can't actually read Portuguese
<gnutec>efraim: The audiu doesn't work. With lspci, he is there. You have the same problem?
<efraim>The last time I played a video my audio worked, that was about 2 weeks ago