You are not logged in.
I have a USB 2.0 card reader 35 in 1. The device worked for years without any problems. When I upgraded to Debian 8 or 9, it stopped working. I thought the device was defective and bought a new one.
I think the appropriate driver has been removed from the kernel. But how do I find it and what do I do then?
Please bear with me, I haven't been active for a long time. But I'll get back into it. Thanks for the tip.
I have a camera with an XD card.
The text is with Google Translate.
Offline
Hello:
Welcome to Devuan.
... USB 2.0 card reader 35 in 1.
Right.
I seem to recall that the Hama branded card readers did not play too well with Linux.
BTW: is it this one?
ALWAYS COMPATIBLE: Operating systems compatible with Windows 11/10/8/7/Vista/XP card reader if applicable. with update and Mac OS from 9.x or later. A USB cable for connecting to a PC/laptop/laptop is included.
Note that there's no mention of Linux support.
That said, let's see that we can do.
Please follow these instructions:
1.
With the reader unplugged from the box, please open a terminal and post the screen output of:
~$ uname -a
and
~$ lsusb
This will tell us what version of Devuan* you are using and what USB devices are installed in your box/laptop.
* important information you should always post.
2.
Once you have done that, without closing the teminal do ...
~$ sudo dmesg -w
... making a note of the last line of the printout for reference.
Once you have done that, plug in your USB card reader and post the output of the printout after the last line you made a note of.
That will tell us what is happening in the system when you plug in the reader.
ie: if it is recognised or not and if so, the idVendor idProduct numbers.
We'll continue once you have done all that.
Best,
A.
Last edited by Altoid (2025-03-10 18:59:49)
Online
Thanks for the reply.
1.
volker@zalman:~$ uname -a
Linux zalman 6.1.0-22-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.94-1 (2024-06-21) x86_64 GNU/Linux
volker@zalman:~$ lsusb
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1241:1177 Belkin Mouse [HT82M21A]
Bus 001 Device 003: ID 1b10:2002 DICOTA D31841 DICOTA D31841
Bus 001 Device 002: ID 04f9:0248 Brother Industries, Ltd DCP-7055 scanner/printer
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
2.
usblp0: removed
[ 1693.947970] process 'Printer/DCP7055/inf/brprintconflsr3' started with executable stack
[ 1694.176660] usblp 1-2:1.0: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0248
[ 1755.552055] usb 1-3: new high-speed USB device number 5 using xhci_hcd
[ 1755.803573] usb 1-3: New USB device found, idVendor=0dda, idProduct=2005, bcdDevice= 1.9c
[ 1755.803584] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1755.803588] usb 1-3: Product: Hama Card Reader
[ 1755.803592] usb 1-3: Manufacturer: Hama Card Reader
[ 1755.803595] usb 1-3: SerialNumber: ABCD12345683
[ 1755.829569] usb-storage 1-3:1.0: USB Mass Storage device detected
[ 1755.829823] scsi host9: usb-storage 1-3:1.0
[ 1755.829910] usbcore: registered new interface driver usb-storage
[ 1755.832642] usbcore: registered new interface driver uas
[ 1756.845648] scsi 9:0:0:0: Direct-Access Hama Card Reader CF 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.847337] scsi 9:0:0:1: Direct-Access Hama Card Reader MS 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.849084] scsi 9:0:0:2: Direct-Access Hama CardReaderMMC/SD 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.850885] scsi 9:0:0:3: Direct-Access Hama Card Reader SM 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.851102] sd 9:0:0:0: Attached scsi generic sg3 type 0
[ 1756.851204] scsi 9:0:0:1: Attached scsi generic sg4 type 0
[ 1756.851332] sd 9:0:0:2: Attached scsi generic sg5 type 0
[ 1756.851499] sd 9:0:0:3: Attached scsi generic sg6 type 0
[ 1756.852225] sd 9:0:0:0: [sdc] Media removed, stopped polling
[ 1756.852950] sd 9:0:0:1: [sdd] Media removed, stopped polling
[ 1756.854165] sd 9:0:0:2: [sde] Media removed, stopped polling
[ 1756.854922] sd 9:0:0:3: [sdf] Media removed, stopped polling
[ 1756.855479] sd 9:0:0:1: [sdd] Attached SCSI removable disk
[ 1756.858273] sd 9:0:0:3: [sdf] Attached SCSI removable disk
[ 1756.858274] sd 9:0:0:2: [sde] Attached SCSI removable disk
[ 1756.860961] sd 9:0:0:0: [sdc] Attached SCSI removable disk
[ 1809.510084] usb 1-3: reset high-speed USB device number 5 using xhci_hcd
[ 1854.634089] usb 1-3: reset high-speed USB device number 5 using xhci_hcd
Thank you for your help and greetings from Germany!
Offline
Hello:
Thanks ...
You're welcome.
Before we continue:
When posting a terminal printout, for easier reading, the text must be placed between code blocks.
eg:
code
printout text goes here
/code
That way what the reader sees is this:
printout text goes here
You can generate a pair of code blocks by clicking on [ code ] while editing / replying.
---
Now, with respect to your reader:
--- snip ---
[ 1755.552055] usb 1-3: new high-speed USB device number 5 using xhci_hcd
[ 1755.803573] usb 1-3: New USB device found, idVendor=0dda, idProduct=2005, bcdDevice= 1.9c ### <----
[ 1755.803584] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1755.803588] usb 1-3: Product: Hama Card Reader
[ 1755.803592] usb 1-3: Manufacturer: Hama Card Reader
[ 1755.803595] usb 1-3: SerialNumber: ABCD12345683
--- snip ---
1.
dmesg informs that your reader is id'd as idVendor=0dda, idProduct=2005, 0dda being the id of the OEM, Integrated Circuit Solution, Inc. and 2005 the id of their Datalux DLX-1611 16in1 Card Reader. In your case, it has been rebadged as a Hama Card Reader.
This means that you are not lacking a driver as it is recognised by the system and that the problem is (most probably) not the hardware.
--- snip ---
[ 1756.845648] scsi 9:0:0:0: Direct-Access Hama Card Reader CF 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.847337] scsi 9:0:0:1: Direct-Access Hama Card Reader MS 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.849084] scsi 9:0:0:2: Direct-Access Hama CardReaderMMC/SD 1.9C PQ: 0 ANSI: 0 CCS
[ 1756.850885] scsi 9:0:0:3: Direct-Access Hama Card Reader SM 1.9C PQ: 0 ANSI: 0 CCS
--- snip ---
Here you see the different slots where the "35" are plugged in.
ie: CF, MMC/SD, MS, SM, etc.
Up to that point it seems that everything is as expected.
Q1: are you using a laptop/portable machine?
Q2: if so, were you running on main or battery power?
Q3: was there any card in the reader when you plugged it in?
If there was a card in the reader, please remove the card and repeat 2. without any cards in the reader.
ie:
sudo dmesg -w
... then plug in the reader and post the terminal printout as indicated.
Best,
A.
Last edited by Altoid (2025-03-11 20:14:35)
Online
Thank you for the kind explanation. I learned a lot.
To the questions:
Q1: No, I use a PC.
Q2: -
Q3: No, I inserted the reader without a card
Thanks for the help!
Offline
Hello:
Thank you ...
You're welcome.
Q1: No, I use a PC.
Laptops sometimes have power issues with card readers.
Q3: No, I inserted the reader without a card
Right.
Unfortunately, I don't have good news for you.
I was looking around this morning and it seems that your hardware, while it may work properly with MS OSs, may now need a different/specific driver module with the newer Linux kernels, it seems it did have issues with 2.6.x kernels.
Not unheard of and as we have seen, this reader does not have Linux support.
You can download the manual here: https://at.hama.com/webresources/articl … en_300.pdf
Although it does not state that Linux OSs are not supported, it clearly states:
Supported OS:
Windows 8/7Vista/VP/MAC OS 10.X.
That said, I found the official Hama site and the german language support page: https://support.hama.com/
You will need the eight digit item number to search for the driver to download, if it is available.
It is probably on a sticker or printed somewhere in the case.
There is also a service and contact web page here: https://www.hama.com/de/de/service/kontakt-hotline
Maybe they can give you precise information with respect to your reader and Linux support.
I'm sorry I have not been able to help you further.
Let us know what you find out.
Best,
A.
Online
I have written to Hama and will inform you of the result.
My camera has an xD card, and it's hard to find a compatible card reader. Direct access to the camera is therefore not possible.
may now need a different/specific driver module with the newer Linux kernels,
I do not understand that. Can't you reload the old driver module?
Thanks again for your support.
Last edited by Winnetou (2025-03-12 13:00:19)
Offline
Hello:
... written to Hama and will inform ...
Good.
It will serve as a precedent to other users.
Before we continue:
When posting a quoted text, for easier reading, the text must be placed between quote blocks.
Just like when posting a printout or code but with a different block.
eg:
quote
quoted text goes here
/quote
That way what the reader sees is this:
quoted text goes here
You can generate a pair of quote blocks by clicking on [ quote ] while editing / replying.
---
... an xD card, and it's hard to find a compatible card reader.
Indeed ...
This is because on one hand, xD cards (xD-Picture Card) is a proprietary format developed by Olympus / Fujifilm and on the other, that format is now obsolete.
Proprietary is also a suitable synonym for expensive. See here: https://en.wikipedia.org/wiki/XD-Picture_Card
Same goes for the proprietary memory sticks used by Sony cameras.
Such is life ... 8^°
Direct access to the camera ...
No cable connection to a PC?
ie: serial to proprietary connector, USB to proprietary connector, USB A to USB Mini B?
I recall most if not all camera vendors either included a cable to connect to a PC.
But others had the cheek to offer you one as a very expensive accesory.
I still have a crappy Konica Minolta Dimage X31 that actually came with a cable.
But the power supply to use it without batteries and the protective pouch / case sold separately were accessories.
Edit:
I forgot to add this link: https://www.linuxquestions.org/question … ost3606104
If you have a cable for your camera it may work, this chap basically uses the camera itself as an xD card reader to unload the photos.
Clumsy but effective.
... need a different/specific driver module ...
It would be nice if that were so, but apparently not.
At least I have not found a solution on-line.
... reload the old driver module?
In an ideal world, maybe.
I will try to explain why with this example, please bear with me:
My Devuan Daedalus box runs three monitors connected to a pair of matching PCIe NVidia Quadro FX 580 cards.
It has been that way since ~2015.
I always used the proprietary NVidia drivers made available to the Linux community by NVidia, albeit with quite a few caveats as to what capabilities they would enable. Corporations such as Nvida* are never that generous.
* not the only one, the list is a very long one.
In spite of that, the cards and the drivers worked well enough with every distributon I tried till I settled on Devuan.
At first, there were no native Linux drivers to speak of until nouveau came to light.
But it was difficult / a bit buggy and lagged way behind, so the NVidia drivers were preferred choice.
Then the time came for NVidia to phase out the Quadro FX580 line (have to sell more hardware, you understand) and as a result stopped making the drivers available to the Linux community.
The driver modules used up to that point could not be used with the newer kernels because these had evolved in various ways and that brought along the need to rewrite / update the modules so as to work with the upgraded kernels, which was not possible / feasible without support from NVidia.
And that was it.
Many years ago, I had to retire a pair of very (very) expensive and prefectly working Matrox G450 PCI cards for that very same reason.
I still shed a tear when I remember ...
I hope my explanation is undertsandable.
That said, I understand that some digital cameras with xD card slots will accept adapters to SD cards.
You wilol have to check your camera's manual or ask the OEM.
Check this video: https://www.youtube.com/watch?v=U9lNxOKAPoo
Thanks again ...
You're welcome.
Do let us know if you solved your problem.
Best,
A.
Last edited by Altoid (2025-03-12 15:03:41)
Online