Deutsch   English   Français   Italiano  
<878rulutfc.fsf@s02.forall>

View for Bookmarking (what is this?)
Look up another Usenet article

Path: ...!news.mixmin.net!proxad.net!feeder1-2.proxad.net!cleanfeed2-a.proxad.net!nnrp1-2.free.fr!not-for-mail
From: Valrik <nospam@valrik.invalid>
Newsgroups: fr.comp.os.linux.configuration
Subject: =?utf-8?Q?Probl=C3=A8me?= de reconnaissance d'un lecteur de carte
 =?utf-8?Q?m=C3=A9moire=2E?=
Date: Tue, 08 Feb 2022 19:03:51 +0100
Message-ID: <878rulutfc.fsf@s02.forall>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux)
Cancel-Lock: sha1:QX0OB32e/A76FiHGC/Ty7QQquwc=
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Lines: 147
Organization: Guest of ProXad - France
NNTP-Posting-Date: 08 Feb 2022 19:03:51 CET
NNTP-Posting-Host: 91.172.153.64
X-Trace: 1644343431 news-1.free.fr 28592 91.172.153.64:64893
X-Complaints-To: abuse@proxad.net
Bytes: 6966


Post=C3=A9 sur https://www.debian-fr.org/ et fr.comp.os.linux.configuration

J'essaie de remettre en service un lecteur Akasa AK-ICR-07U3 suite =C3=A0
une panne importante sur un station qui a occasionn=C3=A9 le changenent,
entre autres, de la carte m=C3=A8re. Bien qu'interne, ce type de lecteur se
branche sur un port USB externe.

La distribution reste la m=C3=AAme, =C3=A0 savoir, une Debian Buster.
/!\ : uname -a=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20
Linux s01 4.19.0-18-amd64 #1 SMP Debian 4.19.208-1 (2021-09-29) x86_64 GNU/=
Linux
Ce mat=C3=A9riel a fonctionn=C3=A9 avec cette distribution.

j'ai cherch=C3=A9 longtemps sur internet une solution, mais je n'ai rien
trouv=C3=A9 de probant. Il y a bien cela :
https://www.cs.sfu.ca/~ggbaker/personal/cf-linux
Mais, le document semble dat=C3=A9.

J'ai fait pas mal de manipulations. En voici quelques unes.
 - Monter une carte m=C3=A9moire dans l'emplacement : rien dans /dev
 - udevadm monitor : rien ne se passe.
 - Brancher le clavier sur le port usb du lecteur : pas de probl=C3=A8me,
   clavier fonctionnel.
 - lsusb et usb-devices, lecteur branch=C3=A9 ou pas :
/!\ : lsusb # Avec lecteur de cartes m=C3=A9moire branch=C3=A9.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/!\ : usb-devices # Avec lecteur de cartes m=C3=A9moire branch=C3=A9.
T:  Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D  1 Spd=3D480 MxC=
h=3D12
D:  Ver=3D 2.00 Cls=3D09(hub  ) Sub=3D00 Prot=3D01 MxPS=3D64 #Cfgs=3D  1
P:  Vendor=3D1d6b ProdID=3D0002 Rev=3D04.19
S:  Manufacturer=3DLinux 4.19.0-18-amd64 xhci-hcd
S:  Product=3DxHCI Host Controller
S:  SerialNumber=3D0000:00:14.0
C:  #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D0mA
I:  If#=3D0x0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub  ) Sub=3D00 Prot=3D00 Driver=
=3Dhub

T:  Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D05 Cnt=3D01 Dev#=3D  4 Spd=3D1.5 MxC=
h=3D 0
D:  Ver=3D 1.10 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D  1
P:  Vendor=3D1e54 ProdID=3D2030 Rev=3D01.50
S:  Manufacturer=3DTypeMatrix.com
S:  Product=3DUSB Keyboard
C:  #Ifs=3D 2 Cfg#=3D 1 Atr=3Da0 MxPwr=3D100mA
I:  If#=3D0x0 Alt=3D 0 #EPs=3D 1 Cls=3D03(HID  ) Sub=3D01 Prot=3D01 Driver=
=3Dusbhid
I:  If#=3D0x1 Alt=3D 0 #EPs=3D 1 Cls=3D03(HID  ) Sub=3D01 Prot=3D00 Driver=
=3Dusbhid

T:  Bus=3D02 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D  1 Spd=3D5000 Mx=
Ch=3D 8
D:  Ver=3D 3.00 Cls=3D09(hub  ) Sub=3D00 Prot=3D03 MxPS=3D 9 #Cfgs=3D  1
P:  Vendor=3D1d6b ProdID=3D0003 Rev=3D04.19
S:  Manufacturer=3DLinux 4.19.0-18-amd64 xhci-hcd
S:  Product=3DxHCI Host Controller
S:  SerialNumber=3D0000:00:14.0
C:  #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D0mA
I:  If#=3D0x0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub  ) Sub=3D00 Prot=3D00 Driver=
=3Dhub

/!\ : lsusb # Avec lecteur de cartes m=C3=A9moire NON branch=C3=A9.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1e54:2030 TypeMatrix 2030 USB Keyboard
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

/!\ : usb-devices # Avec lecteur de cartes m=C3=A9moire NON branch=C3=A9.
T:  Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D  1 Spd=3D480 MxC=
h=3D12
D:  Ver=3D 2.00 Cls=3D09(hub  ) Sub=3D00 Prot=3D01 MxPS=3D64 #Cfgs=3D  1
P:  Vendor=3D1d6b ProdID=3D0002 Rev=3D04.19
S:  Manufacturer=3DLinux 4.19.0-18-amd64 xhci-hcd
S:  Product=3DxHCI Host Controller
S:  SerialNumber=3D0000:00:14.0
C:  #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D0mA
I:  If#=3D0x0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub  ) Sub=3D00 Prot=3D00 Driver=
=3Dhub

T:  Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D  5 Spd=3D1.5 MxC=
h=3D 0
D:  Ver=3D 1.10 Cls=3D00(>ifc ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D  1
P:  Vendor=3D1e54 ProdID=3D2030 Rev=3D01.50
S:  Manufacturer=3DTypeMatrix.com
S:  Product=3DUSB Keyboard
C:  #Ifs=3D 2 Cfg#=3D 1 Atr=3Da0 MxPwr=3D100mA
I:  If#=3D0x0 Alt=3D 0 #EPs=3D 1 Cls=3D03(HID  ) Sub=3D01 Prot=3D01 Driver=
=3Dusbhid
I:  If#=3D0x1 Alt=3D 0 #EPs=3D 1 Cls=3D03(HID  ) Sub=3D01 Prot=3D00 Driver=
=3Dusbhid

T:  Bus=3D02 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D  1 Spd=3D5000 Mx=
Ch=3D 8
D:  Ver=3D 3.00 Cls=3D09(hub  ) Sub=3D00 Prot=3D03 MxPS=3D 9 #Cfgs=3D  1
P:  Vendor=3D1d6b ProdID=3D0003 Rev=3D04.19
S:  Manufacturer=3DLinux 4.19.0-18-amd64 xhci-hcd
S:  Product=3DxHCI Host Controller
S:  SerialNumber=3D0000:00:14.0
C:  #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D0mA
I:  If#=3D0x0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub  ) Sub=3D00 Prot=3D00 Driver=
=3Dhub

Les petites diff=C3=A9rences sont dues d=C3=A9placement d'un port =C3=A0 l'=
autre du clavier.

 - Charger des modules au petit bonheur la chance : c'=C3=A9tait vou=C3=A9 =
=C3=A0 l'=C3=A9chec=E2=80=A6
/!\ : awk '/^modprobe[[:space:]]+[[:alpha:]]+/' fa00-bash_history_root # =
=C2=AB .bash_history =C2=BB de Root.
modprobe usb-storage=20
modprobe usb-serial-simple=20
modprobe usb
modprobe rtsx_usb
modprobe rtsx_usb_ms=20
modprobe rtsx_usb_sdmmc=20
modprobe acard-ahci=20
modprobe rc-avermedia-cardbus=20
modprobe rtsx_usb
modprobe rtsx_usb
modprobe rtsx_usb_ms=20
modprobe rtsx_usb_sdmmc=20
modprobe rtsx_pci
modprobe rtsx_pci_ms=20
modprobe rtsx_pci_sdmmc=20
modprobe acard-ahci=20
modprobe usb-storage=20
modprobe usb_f_mass_storage=20
modprobe usb-storage=20
modprobe sg_usb
/!\ :=20

La possibilit=C3=A9 d'une panne mat=C3=A9rielle ne peut =C3=AAtre totalemen=
t exclue,
mais je suis persuad=C3=A9 qu'elle elle tr=C3=A8s improbable.  Je fais plut=
=C3=B4t
l'hypoth=C3=A8se du pilote idoine non charg=C3=A9. Mais lequel ?

Voil=C3=A0, je pense avoir fait le tour du sujet=E2=80=A6

Merci de votre attention.