Client can't see Solo Hacker

[fastchain]

Hello,
I've received Solo Hacker today, compiled (according to manual) solo2-cli, but

 afx@proton  ~/solokey/solo2-cli $ /home/afx/.cargo/bin/solo2 ls -vvvv
 DEBUG solo2::transport::pcsc > >> 00a4040009a0000008470000000100
 DEBUG solo2::transport::pcsc > RECV 2 bytes
 DEBUG solo2::transport::pcsc > << 6a82
 afx@proton ~/solokey/solo2-cli $ lsusb                              
Bus 002 Device 043: ID 17ef:1010 Lenovo ThinkPad Ultra Dock Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 016: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor
Bus 001 Device 008: ID 5986:0706 Bison Electronics Inc. ThinkPad P50 Integrated Camera
Bus 001 Device 007: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
Bus 001 Device 005: ID 0781:5571 SanDisk Corp. Cruzer Fit
Bus 001 Device 053: ID 17ef:100f Lenovo ThinkPad Ultra Dock Hub
Bus 001 Device 059: ID 0483:a2ca STMicroelectronics Solo 3.1.2
Bus 001 Device 060: ID 04e8:61f3 Samsung Electronics Co., Ltd Portable SSD T3 (MU-PT250B, MU-PT500B)
Bus 001 Device 052: ID 17ef:1010 Lenovo ThinkPad Ultra Dock Hub
Bus 001 Device 014: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo
Bus 001 Device 023: ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 afx@proton  ~/solokey/solo2-cli $ sudo /home/afx/.cargo/bin/solo2 ls -vvvv
 DEBUG solo2::transport::pcsc > >> 00a4040009a0000008470000000100
 DEBUG solo2::transport::pcsc > RECV 2 bytes
 DEBUG solo2::transport::pcsc > << 6a82

solo2 can't see the device, which is present (according lsusb)

What am I doing wrong?

 afx@proton  ~/solokey/solo2-cli $ uname -a                         
Linux proton 6.2.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 03 Mar 2023 15:58:31 +0000 x86_64 GNU/Linux

[fastchain]

I've also used this manual
https://docs.solokeys.io/udev/

[fastchain]

Yes

afx@proton $ cat /etc/udev/rules.d/70-solokeys-access.rules
# Notify ModemManager this device should be ignored
ACTION!="add|change|move", GOTO="mm_usb_device_blacklist_end"
SUBSYSTEM!="usb", GOTO="mm_usb_device_blacklist_end"
ENV{DEVTYPE}!="usb_device",  GOTO="mm_usb_device_blacklist_end"

ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a2ca", ENV{ID_MM_DEVICE_IGNORE}="1"

LABEL="mm_usb_device_blacklist_end"


# Solo bootloader + firmware access
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a2ca", TAG+="uaccess"
SUBSYSTEM=="tty", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="a2ca", TAG+="uaccess"

# ST DFU access
SUBSYSTEM=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", TAG+="uaccess"

# U2F Zero
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="8acf", TAG+="uaccess"

afx@proton  $  sudo udevadm control --reload-rules && sudo udevadm trigger        

afx@proton   $  ls /dev/solo* -liahst
6102 0 lrwxrwxrwx 1 root root 7 Mar 30 14:49 /dev/solo -> hidraw6
6103 0 lrwxrwxrwx 1 root root 7 Mar 30 14:49 /dev/solo--6 -> hidraw6
6104 0 lrwxrwxrwx 1 root root 7 Mar 30 14:49 /dev/solosecure--6 -> hidraw6


afx@proton  $  /home/afx/.cargo/bin/solo2 ls -vvvv
DEBUG solo2::transport::pcsc > >> 00a4040009a0000008470000000100
DEBUG solo2::transport::pcsc > RECV 2 bytes
DEBUG solo2::transport::pcsc > << 6a82
afx@proton  $ 

[fastchain]

btw,
when I test the key with https://demo.yubico.com I can register and authenticate. So the hardware seems to be ok and set up.

[fastchain]

I've test with solo1 cli and it was able to find the key

(solo1)  afx@proton  ~/solokey/solo1  solo1 ls
:: Solos
205B3174414E: SoloKeys Solo 3.1.2

[My1]

considering you see a serial number and the fw lists as 3.1.2 and that it even shows proper info lets me believe you have an original solo, rather than a solo2. the solo2 cli likely only works for the solo2.

[fastchain]

@My1 yep, it seems, that I was a bit confused by promotion banners. Sorry for the mess. Btw, since solo2 will be a different device, will it also have hacker version?