Re: [Nix-dev] 5 somewhat related questions

2017-06-22 Thread David Izquierdo

I'll try to answer what I think I know...

On 22/06/17 20:40, Klaas van Schelven wrote:

Hello Nixians,

I've installed NixOs a number of days ago. So far I really like it!

I've read the documentation I could find, but I'm left with a number of
questions; not so much "how to do X" but rather of a slightly more
philosphofical (or cultural, a.k.a. "best practices") nature. I hope
someone can enlighten me on the "Nix Way".

1. In NixOs /etc/nixos/configuration.nix is the single configuration file
that determines the state of the system as a whole. How does this file
relate to the existence of the nix-env command, either executed as root or
by a single non-privileged user? In particular, I would assume that any
nix-env is undone by the time the system is rebuilt from the configuration
file. Assuming this is the case: should the usage of nix-env not be
actively discouraged in NixOs? (perhaps it is, and I simply did not find
the reference)
They're mostly independent, but AFAIK nix-env binaries have priority 
over conf.nix. Nothing gets undone, since whatever you install to your 
user profile stays in the nix store (because your user profile is a gc 
root). For me, the use of n-e is because it's faster to test or use 
oneshot software installing it imperatively than adding-then-removing to 
conf.nix. I guess `nix-shell -p` would be more "correct", but it's a 
matter of not forgetting you've used it.

2. (Context: Assuming for a moment there _is_ in fact a use-case for
nix-env; e.g. the scenario where you're not running NixOs, but are using
Nix on top of another distribution). nix-env uses an "imperative style" of
manipulating your environment, i.e. using a sequence of commands in a
particular order. I understand that after each succesful manipulation the
_resulting_ environment becomes available as a separate generation. As far
as I understand there's even a "half-product", the so called "derivation"
that is available per generation, although I did not study those yet. My
question is, however, whether the original commands that led to these
constructions can somehow be retrieved. The reason for this question is the
observation that the sequence of nix-env (and potentially other similar)
commands can be seen as a transactional log that could simply be replayed
to reconstruct the resulting generations (assuming that the commands fully
express the information needed to construct the associated environments;
this assumption might not actually hold in practice. Question 2b: does the
assumption hold?).

3. In the scenario where I use the single configuration file
/etc/nixos/configuration.nix but I'm also subscribed to a channel, the
state of this channel may influence the outcome of nixos-rebuild (This is
by design, it allows us to stay up to date with e.g. security updates). The
consecutive states of the channel, as seen by my system when rebuilding,
are valuable pieces of information in their own right when I want to debug
a problem. Take the following example:

t=0, my system is good.
t=1, I want to install some extra package, I modify configuration.nix, and
run nixos-rebuild
t=2, system broken.

I understand that I always have the ability to roll back the system _as a
whole_, even using Grub if needed. This is awesome of course. The question
is: do I also have the ability to debug the parts that lead to that whole?
In particular: the precise state of the channel[s] on each rebuild? And
preferably also: the state of /etc/nixos/configuration.nix on each build?

I think you want `nix-channel --rollback`, and 
`system.copySystemConfiguration = true` (for c.nix). Note however that 
at some point it will probably be in your best interest to modularise 
your c.nix into several files, and that option only copies c.nix, not 
any imports. You can check this message for a fairly elegant method to 
have your /etc/nixos tree be a part of each generation.

4. Is a "single declarative file per user" (e.g. for dotfiles, but
potentially also to make it possible to declare which user-specific
packages are installed) available? I understand there some options exist,
but how do they relate? Is there convergence on a "one way to do it"?

5. In the commit linked below, the nix file for VTE 2.91 adds the following
2 propagatedBuildInputs: pcre2 & gnutls. As far as I understand this might
be not good practice. The reason I've added them is because pkg-config,
when run in the build context of xfce.terminal, cannot otherwise find the
package vte-2.91 because of a dependency error. Ignoring for a moment the
rationale of the commit itself (I've been convinced that adding this
particular version of xfce4-terminal to the repo by itself is not a good
idea) can someone tell me what the proper way to handle this particular
situation would be?

Re: [Nix-dev] Trying to install the SailfishOS SDK

2017-06-18 Thread David Izquierdo
I was recently looking for info on this too. I'll ask a more general 
question: Is there any other piece of softrware in nixpkgs that's based 
on a QtInstallerFramework? The installer for Sailfish SDK is one, and, 
even though it runs via steam-run (and promptly detects my lack of 
VirtualBox), I'd prefer to properly package it. I suspect the secret 
sauce will be, unsurprisingly, in the AUR. I'll have a go in the 
following weeks at replicating the PKGBUILD in nix and see how it works out.

On 17/06/17 22:26, David wrote:

On Thu, 19 Jan 2017 21:13:55 +0100
Christoph-Simon Senjak  wrote:

I am trying to write a package for the SailfishOS SDK.

I am sorry for the necrobump but... is there any news on this?
nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] PulseAudio

2017-05-09 Thread David Izquierdo
I don't know how to see that process' logs. Maybe some magic journalctl 
option. Is it possible that it's starting as a systemd user service? 
Then `journalctl --user -eu pulseaudio` would work... But starting pulse 
like that doesn't seem to work for me.

On 09/05/17 21:13, Mark Gardner wrote:


On Tue, May 9, 2017 at 2:59 PM, David Izquierdo <> wrote:

If you run `pulseaudio -k`, does it kill it?

$ pulseaudio -k
E: [pulseaudio] main.c: Failed to kill daemon: No such process

​But the daemon is running as me:
$ ps aux | grep pulseaudio
2572  0.0  0.0 490632 10540 ?Sl   14:55   0:00 /nix/store/
a72z0gasiv1145ygyijzgdra921pkk60-pulseaudio-10.0/bin/pulseaudio --start
2604  0.0  0.0 118264  5756 ?S14:55   0:00 /nix/store/

Once dead, what does it log if you run `pulseaudio` and then try to use
pavucontrol or other program?

​I killed it by hand:
​$ sudo kill 2572 2604
$ mpv foobar.mp3  # plays
$ pavucontrol  # Works!

Going to try a reboot to see if it still works... Back to the previous
behavior until I kill them then start up something that uses pulseaudio.

Making progress. Thanks David.

nix-dev mailing list

Re: [Nix-dev] PulseAudio

2017-05-09 Thread David Izquierdo
If you run `pulseaudio -k`, does it kill it? Once dead, what does it log 
if you run `pulseaudio` and then try to use pavucontrol or other program?

On 09/05/17 20:58, Mark Gardner wrote:

On Tue, May 9, 2017 at 2:32 PM, Sergiu Ivanov  wrote:

I suppose you tried rebooting after installing the packages?

​Yes. I did that before doing the above actions. I even upgraded to 17.03
(from 16.09) in case that helped. It didn't.

I'm afraid I'm running out of ideas, sorry :-( Off the top of my head, I
don't think the no-longer-available wiki page had many more details
relevant to your situation.

​Thanks for your help.


nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] [NixOS] How to incorporate my Bash script in configuration.nix?

2017-05-09 Thread David Izquierdo
I would have gone to Slightly uglier looking (bigger 
attrset), but should run after the kernel has loaded its modules. I'd 
say it would be ideal to have it be "PartOf =" and/or 
"Before = dhcpd.service" (or whatever networking thingy you use).

On 09/05/17 13:26, Strahinja Popovic wrote:

Thanks for help Peter,

But I have in dmesg now:

[2.027361] stage-2-init:
line 136: /sys/bus/usb/drivers/rt2800usb/new_id: No such file or directory

How to make it to wait for kernel module?

On Tue, May 9, 2017 at 9:44 AM, Peter Hoeg  wrote:


   I have made my USB WiFi to work,

   but I have to call this script whenever I restart the computer.

you can do it this way:

system.activationScripts = {
  rt2800usb = {
text = ''
  echo "0b05 17e8" > /sys/bus/usb/drivers/rt2800usb/new_id
deps = [];


nix-dev mailing list

nix-dev mailing list

[Nix-commits] [NixOS/nixpkgs] b8463e: pythonPackages.markupsafe: 0.23 -> 1.0

2017-04-30 Thread David Izquierdo
  Branch: refs/heads/staging
  Commit: b8463e97b63ebd5fa05c14e9f9c52edc9274e753
  Author: David Izquierdo <>
  Date:   2017-04-30 (Sun, 30 Apr 2017)

  Changed paths:
M pkgs/top-level/python-packages.nix

  Log Message:
  pythonPackages.markupsafe: 0.23 -> 1.0

nix-commits mailing list

Re: [Nix-dev] Can't install NixOS on an NVME drive

2017-04-19 Thread David Izquierdo
If that was indeed the problem, the way to "keep" windows working is to 
reinstall it in AHCI mode. Its recovery tools may or may not be able to 
fix that too.

On 19/04/17 09:55, Julien Tanguy wrote:

Hello Liam,

For NixOS to work, you have to change the SSD controller from RAID ON to
AHCI. This effectively *breaks *the windows install. As of today I haven't
found a better way to switch to windows than to change this SSD setting
each time I want to boot to another OS.

I wrote something about my NixOS install for a Dell XPS 15, you can read
about it here
Domen Kožar pointed me out on Twitter to another config, with a more
elaborate setup with LUKS and such :

I hope you find what you need.

On Tue, Apr 18, 2017 at 4:35 PM Liam Wigney  wrote:

Hey all,

I've been trying to install NixOS on the new XPS 13 but I've found that
NixOS can't find the drive in /dev/. There's no listing for /sdax or /nvmex.

I've looked online and found that changing some bios settings (Something
about raid) makes it show up, however doing that stops windows booting.

I'm thinking this could be related to the lenovo controversy
The comments say that a Linux compatible driver should be available now but
do I have to enable it somehow? How would I do this for the LiveCD?

I'm brand new to Nix and NixOS so I'm sorry if I missed anything.

nix-dev mailing list

nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] Managing /home during system activation

2017-04-16 Thread David Izquierdo
That's stupid genius in my eyes. What I'd been doing is to find a way to 
make software look in /etc/xdg before ~/.config, with... varying degrees 
of success. Is there anywhere we could read your implementation?

On 15/04/17 19:36, Peter Jones wrote:

I'd like to manage files in my home directory during system activation.
Sort of like nix-home[1] but during activation so NixOps can also deploy
things such as my shell configuration.  I have an idea, and I'm
wondering how terrible it is.

Based on the way etc activation works, I would build a directory in the
nix store and fill it with symlinks to other parts of the store:

/nix/store/xxx-home-pjones/.zshrc -> /nix/store/xxx-zshrc/zshrc

Then, set up a UnionFS mount so that /nix/store/xxx-home-pjones gets
overlaid on top of /home/pjones.  This means I don't have to search
through /home looking for links to an old generation to deactivate it,
and rolling back just mounts a previous generation on top of /home.

So, how bad is this idea?



nix-dev mailing list

Re: [Nix-dev] Editor for the configuration file

2017-04-04 Thread David Izquierdo
My WiFi module lives within networking.wireless. I don't have any 
reference to either wpa_supplicant or networkmanager.

On 04/04/17 20:22, Andreas Meyer wrote:


ah it is nano. I was trying vi and vim and emacs.

One more question for now. To bring up WLAN do I have to enable
wpa_supplicant and networkmanager in the configuration.nix ?


Daniel Peebles  schrieb am 04.04.17 um 14:12:51 Uhr:

nano should be preinstalled on all NixOS systems. Is it not?

On Tue, Apr 4, 2017 at 2:00 PM, Andreas Meyer  wrote:


Wanted to look into NixOS but cannot get the network to run
without having an editor. Any chance in this?



nix-dev mailing list


nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] how to 'just run binaries' in nixos

2017-03-23 Thread David Izquierdo
I hereby propose the tool to be renamed and refactocopied to 
`ubuntu-run`, since it will end up being the target runtime anyway :P

On 23/03/17 18:10, Moritz Ulrich wrote:

Azul  writes:

thanks all,

*steam-run* just works

Maybe we should create an alias or a separate incarnation of the same
tool with more dependencies included for "most" software? I'm sure many
newcomers would welcome to be able to run their games or other prebuilt
binaries without having to write Nix in their first days of using NixOS?

I would have liked a tool like this when I got started.

nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] Google Summer of Code 2017

2017-03-15 Thread David Izquierdo

Oh dear, I had been thinking about 1 and 2 lately...

On systemd, I don't think that it's worth it to even try to port 
dependent software. Nix is smart enough to warn about/fix dependencies. 
And "porting" the actual unit files sounds easy IMO, systemd has good 
documentation on unit files that can be easily mapped to alternative 
complementary software (one example I've used recently: `timeout` 
instead of "RuntimeMaxSec"). I don't think indirection would be 
necessary, since the declarative style of units is already really really 
nice to us. Simply moving the relevant options out of the systemd 
namespace and into a more general place (services.service.$NAME?).

BSDs... I thought they had official support... They don't, according to 
the Nix manual's Supported Platforms chapter. I guess once it exists AND 
systemd becomes optional, it's solved itself. And I don't see why Nix 
wouldn't just-work on a BSD when it's supported on Linux and MacOS.

Now, literally all of the above has been pulled out of my backend, and 
from a few months worth of NixOS usage and learning. I hope someone with 
actual knowledge can fix this, and better outline how deep into NixOS's 
internals one would have to plumb to implement this.

On 13/03/17 18:23, Anderson Torres wrote:

2017-01-08 18:40 GMT-02:00 Profpatsch :

On 17-01-04 09:42pm, Vladimír Čunát wrote:

On 01/04/2017 08:51 PM, Peter Simons wrote:

Another very important topic that needs to be addressed in Nix / Hydra
is the question of how to deal with code that wants to import build
products into the ongoing evaluation. [...]

That feels rather vague topic ATM.  My experience is that this kind of
"figure it out how to..." tasks isn't very suitable for similar "project
proposals" like for GSoC.  Still, if we could converge on some more
concrete plan beforehand, maybe the actual implementation would make a
good topic...

I would suggest three big fat proposals:

1 - The most flamewar-igniting one: getting rid of systemd dependency!
It would be very nice if the init system was selectable, with a sane
default (as openrc).
It would be hard as hell to port certain software as Gnome stack, but
I think it can be solved.

2 - Another for the even more courageous would be run a Nixos+kNetBSD
(or kFreeBSD), as in Debian. It would be the definitive test for
portability and independence of Nix model.

3 - Another set of defaults for the stdenv, as musl+clang.

Sounds more like a task for a master’s thesis (or adventurous
bachelor’s thesis) to me.

Proudly written in Mutt with Vim on NixOS.
Q: Why is this email five sentences or less?
May take up to five days to read your message. If it’s urgent, call me.
nix-dev mailing list

nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] Move NodeJS to separate overlay repository?

2017-03-11 Thread David Izquierdo
Couldn't this become a kind of dependency hell? I remember from Gentoo 
that having dependencies across overlays is not a fun problem to solve. 
However, Exherbo mostly solved this by having overlays be analogous to 
packages, they become a kind of dependency that must be explicitly 
user-solved before continuing. In the default ebuild tree they have 
indexes of every package in each registered overlay.

I think this should only be done if there's nothing anywhere else 
depending on a derivation from this overlay-to-be.

On 11/03/17 09:12, Wout Mertens wrote:

Hi all,

now that we got these wonderful overlays as a Chrismas gift (, I
was wondering if we can move some things out of nixpkgs into their own

There are a few package groups that I believe are not used in NixOS core
(boot, containers, ...) and are not updated as much as they could be. Node,
Haskell, others?

Specifically, nodePackages is always out of date, and it would be nice if
there could be a repository or maybe just a local process that updates them
separately and adds a lot more builds.

Furthermore, building node packages from scratch is ok, because that's what
npm does anyway. So any caching offered by Hydra is a bonus, not a

For example, maybe the overlay could be auto-generated every hour from npm?
And then some service fetches it to /etc/nixos/overlays/nodePackages?

Does this seem like a fair assessment? What should be done to achieve this?


nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] 'nixos-stable' channel?

2017-03-08 Thread David Izquierdo
I think It could be worthwhile to look at openSUSE's Tumbleweed setup 
for rolling releases. They use openQA for automatic testing of every 
package in the distribution, and then release the binaries as snapshots 
for users to update. Pretty similar to how nixpkgs git -> Hydra -> cache 
works, with an additional testing phase. I _think_ they provide it 
hosted, and if it's similar to OBS, they actively encourage community 
members and distros to use their infrastructure.

On 06/03/17 12:24, Kevin Cox wrote:

On 06/03/17 06:54, Sander wrote:

Moving a symlink twice a year?
Good point. I guess it would be worth trying out and we can see how 
many people use this.

I was thinking something more rolling would be nice too. Like a 
lightly tested. Although that would definitely have more maintenance 

nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] 'nixos-stable' channel?

2017-03-05 Thread David Izquierdo
I think it would be handy though. After all, this is NixOS we're talking 
about. We already have system.stateVersion for protecting stateful data, 
and fixing the rest of the system is only a rollback away. Why not make 
the alias/symlink without making it the default?

On 05/03/17 19:37, Nathan Bijnens wrote:

I think that's dangerous. You will be upgrading without being aware of any
breaking changes.


On Sun, Mar 5, 2017, 17:15 Sander  wrote:

Graham Christensen wrote (ao):

NixOS 17.03 has entered Beta. This means we now have 3 versions of NixOS
being developed:

  - 16.09 (stable)
  - 17.03 (beta)
  - unstable

Would it make sense to have a 'nixos-stable' channel that points to
whatever channel is stable?

nix-dev mailing list

nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] NixOS 16.09 and Firefox Nightly

2017-03-05 Thread David Izquierdo
AFAIK those restrictions were recently dropped, Debian's firefox is now 
branded Firefox instead of Iceweasel. It probably should be changed in 
nixpkgs too to prevent further confusion.

On 05/03/17 16:16, Graham Christensen wrote:

Hi Mark,

As I understand it, what we ship in 16.09 is indeed the stable version
of Firefox. However, since we build it ourselves the licensing
restrictions of Mozilla require us to not call it "Firefox" but instead
force us to call it "Nightly."

Can you confirm that the version of Firefox you're running matches the
currently available, stable, Firefox?

Graham Christensen
NixOS Security Team
nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] Can't launch XFCE from SDDM?

2017-03-05 Thread David Izquierdo
SDDM is problematic to me with i3 too. Right now, if I try to login to 
i3 via SDDM I'm returned to SDDM (I don't have plasma enabled). Logs 
didn't look like anything was wrong to me.

On 05/03/17 04:38, laverne wrote:


I have the following lines in my /etc/nixos/configuration.nix

   services.xserver.displayManager.sddm.enable = true;

   services.xserver.desktopManager.kde5.enable = true;

I just tried *adding* this one:

   services.xserver.desktopManager.xfce.enable = true;

and then `nixos-rebuild switch`

Now SDDM offers kde5, xterm, and xfce (instead of just kde5 and xterm). 
However, selecting xfce still takes me to the KDE desktop.

These lines from the system log seem relevant:

Mar 04 21:10:37 laverne-pc systemd[1]: Started User Manager for UID 1000.

Mar 04 21:10:37 laverne-pc sddm-helper[4290]: Starting: 
/nix/store/h2m02ai92x3rycygqpq57x7pbwv9znqg-xsession 'xfce'"

Mar 04 21:10:37 laverne-pc sddm-helper[4300]: Adding cookie to 

Mar 04 21:10:37 laverne-pc sddm[750]: Session started

Mar 04 21:10:37 laverne-pc xsession[4300]: removed 

Mar 04 21:10:38 laverne-pc xsession[4300]: Loading stage  "initial" 260

Mar 04 21:10:38 laverne-pc xsession[4300]: startkde: Starting up...

(My mail client wraps that oddly)

What is with the weird call to the xsession script? Is it actually calling the 
script and passing the script name as it's first argument with 'xfce' as the 
second argument? I'm not very good at reading Bash scripts, but I'm pretty sure 
that the script never uses its second argument (esp. if the first starts with a 

I'm running NixOS 16.09.1803.40de598.

Does anyone else have SDDM + XFCE working on 16.09? I would also be willing to 
give the 17.03 beta a try if folks think this will work better there.



nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] Best Practices on Modularizing Configuration.nix?

2017-02-27 Thread David Izquierdo
My setup is also very similar. I have a configuration.nix with all the 
common setup, which imports hosts/current.nix, which is a (.gitignored) 
symlink to the appropiate host.nix. Then, the host.nix imports from 
modules/*.nix. I also have an etc with generic (not written in Nix) 
configuration files that get imported via builtins.readFile (shell RCs, 
for example) or referred to by *.configFile (i3 config).

I'm planning a slight refactor in which the symlink is actually 
configuration.nix, so that I can make certain reusable declarations into 
a module (I like specific users, UIDs, passwords, and hostnames for each 
host, right now there's a lot of identical lines, varying only the 

I _do_ sync the config tree to my server, since it also serves as a 
general purpose remote computer, and I end up using it a lot when not on 
a machine I own.

On 27/02/17 15:28, Tomasz Czyż wrote:

Hey Mark,

I use almost the same setup and for 1.5y works very well.

I have "modules" and "hosts" directories. Each "host" contains
configuration about hardware/disk setup and includes set of modules from
"modules". On each host there is a symlink to correct
"hosts/.nix" file.

I found this setup pretty robust on dev machines.
On servers I use nixops which pushes configuration so I don't manage
/etc/nixos there.


2017-02-27 14:15 GMT+00:00 Mark Gardner :

Now that I am putting NixOS on more and more machines, I would like to
modularize and share parts of the config to maximize reuse and ensure
uniformity. My approach is to consider the sub-config files as traits or
roles and combine them together to create configuration.nix for a specific
machine, like this:

- cfg/common.nix  # common config
- cfg/desktop.nix  # xorg and related
- cfg/laptop.nix  # related to all laptops
- cfg/work.nix  # work location related
- cfg/mylaptop.nix  # specific laptop related

I import from these to make up configuration.nix. For example, on my
laptop, configuration.nix contains:

{ config, pkgs, ... }:

   imports =

So far, this seems like a good approach. Except that each machine has its
own configuration.nix that I would like to keep in the git repository too
but of course I can't have different top level files with the same name. To
solve this, I could moved the current configuration.nix inside of cfg (as
cfg/mylaptop.cfg.nix perhaps) or merge with the existing cfg/mylaptop.nix
then making configuration.nix a symlink to it. That way the only thing to
do by hand is create the symlink to select a particular configuration. Is
this reasonable? Is there a better way to do it?

How do you modularize your configuration and put it into a repo such that
you can easily create a configuration for a new machine (and put it in the
repo too) without a lot of hand work?

Mark Gardner

nix-dev mailing list

nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] How to ensure that a directory exists via configuration.nix

2017-02-10 Thread David Izquierdo

Is there any reason not to use `mkdir -p`, to spare yourself the if?

On 10/02/17 17:06, Mark Gardner wrote:

Once again, thanks Layus!

For the benefit of others, here is what I put in my configuration.nix:

   system.activationScripts = {
   mnt = {
 text = ''if [ ! -d /mnt ] ; then mkdir /mnt; fi";
 deps = [];


nix-dev mailing list

nix-dev mailing list

Re: [Nix-dev] PCI Expresscard not working under NixOS

2017-02-07 Thread David Izquierdo
And while you're at it, you should probably check `lspci -k` on the 
working system to see what kernel module it uses, in case it's missing 
from NixOS.

On 07/02/17 12:26, Tomasz Czyż wrote:
What about doing quick check and running ubuntu from livecd/usb to 
confirm if card still is alive?

2017-02-07 2:23 GMT+00:00 Roger Qiu >:

It might be a missing driver. Ultimately is the kernel, its
drivers and modules that deal with hardware and IO. You might need
to google around and ask specifically for the given pci expess
hardware serial code and model.

On 07/02/2017 9:39 AM, "Christoph-Simon Senjak"
> wrote:


On 06.02.2017 06:36, Roger Qiu wrote:

When you plug something in, the kernel log should show
something. If it
doesn't then the kernel doesn't know about it, nothing in
the userspace
can help.

How can that be?

Make sure you're running those commands before you plug
the usb in.


Also I used to have faulty usb cables, but even then the
kernel showed
something. Usually repeating messages because the usb
cable kept
dropping out and coming back in.

What happens if you plug those devices directly?

The kernel does not notice the expresscard itself when I plug
it in. My usb hard disk works perfectly under the other ports.

Ah, and fun fact: When plugging in the expresscard, I can
reproducibly scramble my sound output for a second (the music
repeats for a second after I plug it in). Still, the kernel
says nothing. And no device nodes appear.

On 06/02/2017 2:55 PM, "Christoph-Simon Senjak"

>> wrote:


On 06.02.2017 04:46, Peter Hoeg wrote:


My USB 3.0 Expresscard does not work under
NixOS, it used to
under other distros. I already tried to add

Can you be a little more specific about "does not

Nothing happens. Like, really nothing. No new hub is
shown in lsusb
(as it was under Ubuntu). Devices I plug in are not
shown. Nothing.

When you plug it in, what messages are you seeing
while running
these 2
commands in separate terminals:

journalctl -k -f


udevadm monitor

Nothing. No output.

Regards, CSS
nix-dev mailing list



nix-dev mailing list

Tomasz Czyż

nix-dev mailing list

nix-dev mailing list