Cannot detect Solo2

[DMyachin]

➜  ~ uname -r
5.15.2-arch1-1
➜  ~ lsusb | grep -i solo
Bus 003 Device 003: ID 0483:a2ca STMicroelectronics Solo 4.1.5
Bus 001 Device 005: ID 1209:beee Generic Solo 2 Security Key
➜  ~ solo ls
:: Solos
207D329B304B: SoloKeys Solo 4.1.5
➜  ~ solo2 -V
solo2 0.0.6
➜  ~ solo2 ls
<nothing>
➜  ~ solo2 app admin uuid
Error: Could not find any Solo 2 devices connected.

[nickray]

Is pcscd running? We actually kindly got a PR from an Arch maintainer to add the dep in the PKGBUILD. I'll add a hint in the next release.

[DMyachin]

No it was not. But now I start service and reattached device

● pcscd.service - PC/SC Smart Card Daemon
     Loaded: loaded (/usr/lib/systemd/system/pcscd.service; indirect; vendor preset: disabled)
     Active: active (running) since Sat 2021-11-13 17:52:56 MSK; 29s ago
TriggeredBy: ● pcscd.socket
       Docs: man:pcscd(8)
   Main PID: 3288 (pcscd)
      Tasks: 2 (limit: 35996)
     Memory: 464.0K
        CPU: 4ms
     CGroup: /system.slice/pcscd.service
             └─3288 /usr/bin/pcscd --foreground --auto-exit

ноя 13 17:52:56 ummini systemd[1]: Started PC/SC Smart Card Daemon.
➜  ~ solo2 ls                      
➜  ~ 
➜  ~ lsusb | grep -i solo              
Bus 003 Device 003: ID 0483:a2ca STMicroelectronics Solo 4.1.5
Bus 001 Device 005: ID 1209:beee Generic Solo 2 Security Key

Still not working

Added:

➜  ~ sudo pcscd -H -d   
00000000 [139635598052352] debuglog.c:299:DebugLogSetLevel() debug level=debug
00000076 [139635598052352] utils.c:98:SendHotplugSignal() Send hotplug signal to pcscd (pid=4529)
➜  ~ solo2 ls                          
➜  ~ 

[nickray]

This is Arch Linux? Which version of pcscd is this?

[DMyachin]

Yes, it is.

➜  ~ pcscd -v    
pcsc-lite version 1.9.4.
Copyright (C) 1999-2002 by David Corcoran <corcoran@musclecard.com>.
Copyright (C) 2001-2018 by Ludovic Rousseau <ludovic.rousseau@free.fr>.
Copyright (C) 2003-2004 by Damien Sauveron <sauveron@labri.fr>.
Report bugs to <pcsclite-muscle@lists.infradead.org>.
Enabled features: Linux x86_64-pc-linux-gnu libsystemd serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/run/pcscd filter configdir=/etc/reader.conf.d

[DMyachin]

Oh, I found

yay -S ccid
........
➜  ~ solo2 ls
Solo 2 948F69C81E88B3518419C948DC76A1FA

[DMyachin]

Now the device does not enter bootloader mode.

1. Run update or admin boot-to-bootrom
2. Wait for LED changed color and Tap button on key... appears
3. Tap touch button

LED off. Error: No matching bootloader found

And another strange thing:

➜  ~ solo2 update
Downloading latest release from https://github.com/solokeys/solo2/
Downloading firmware v1.0.8...
? Multiple Solo 2 devices connected, select one or hit Escape key ›
❯ Solo 2 948F69C81E88B3518419C948DC76A1FA

But only one solo connected. Solo1 unplugged

[bornf]

... the same issue:

LED off. Error: No matching bootloader found

[nickray]

There's a typo in the udev rules included in the AUR package. Line 4 in https://github.com/solokeys/solo2-cli/blob/main/70-solo2.rules lists beee instead of b000 in the package (which will be re-released soon).

[owenvoke]

I'm receiving the same issue, however on macOS. Not sure if this is related.

➜  ~ uname -rs
Darwin 21.1.0
➜  ~ lsusb | grep -i solo
Bus 020 Device 032: ID 1209:beee 1209 Solo 2 Security Key  Serial: #REDACTED#
➜  ~ solo ls
:: Solos
➜  ~ solo2 -V
solo2 0.0.6
➜  ~ solo2 ls
<nothing>
➜  ~ solo2 app admin uuid
Error: Could not find any Solo 2 devices connected.

macOS doesn't use udev rules afaik, so not sure that change will fix it. The Solo 2 is detected by browsers and functionality such as WebAuthn.

[nickray]

The macOS situation is tricky. It uses AFAIK some version of pcsclite (which includes Solo 2 upstream) regarding the list of USB devices recognized as PCSC devices, but with delay. We will likely soon add support for some commands over CTAPHID (in addition to over CCID).

[nickray]

For Arch Linux, please give the AUR package for v0.0.7 a spin.

[DMyachin]

For Arch Linux, please give the AUR package for v0.0.7 a spin.

error: failed to get `anyhow` as a dependency of package `solo2 v0.0.7 (/home/umnik/.cache/yay/solo2-cli/src/solo2-cli-0.0.7)`

Caused by:
  attempting to make an HTTP request, but --frozen was specified
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: solo2-cli

But solo2-cli-git works. New behavior:

➜  ~ solo2 update
Downloading latest release from https://github.com/solokeys/solo2/
Waiting for key to enter bootloader mode...
Error: No usable bootloader has UUID 948F69C81E88B3518419C948DC76A1FA

➜  ~ solo2        
solo2 0.0.7
SoloKeys Developers

[nickray]

Yes, the git package did not install the udev rules (I updated).
The regular AUR package didn't quite work, please try... again @DMyachin? Version 0.0.7-3 will hopefully finally work.

[DMyachin]

➜  ~ solo2 ls
Solo 2 948F69C81E88B3518419C948DC76A1FA (firmware 1:20200101.7)
➜  ~ solo2 update 
Downloading latest release from https://github.com/solokeys/solo2/
Fetched firmware version 1:20200101.8
Tap button on key to confirm, or replug to abort...
Bootloader detected. The LED should be off.
Writing new firmware...
Done. Rebooting key.  The LED should turn back on.
➜  ~ solo2 ls    
Solo 2 948F69C81E88B3518419C948DC76A1FA (firmware 1:20200101.8)
➜  ~ solo2   
solo2 0.1.0

Fixed for me!