Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Can't read SD cards on Realtek Semiconductor Corp. USB2.0CRW
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1593
Location: PB, Germany

PostPosted: Mon Apr 27, 2020 12:06 pm    Post subject: Can't read SD cards on Realtek Semiconductor Corp. USB2.0CRW Reply with quote

Hi, I can't read any SD card here.

The reader device should be this one:
Code:
0bda:0181 Realtek Semiconductor Corp. USB2.0-CRW

The SD cards are readable without issues on other systems.
Code:
- Last output repeated 258 times -
Apr 27 13:14:11 [kernel] sd 6:0:0:2: [sdf] 987136 512-byte logical blocks: (505 MB/482 MiB)
                - Last output repeated 3 times -
Apr 27 13:14:12 [kernel] scsi_io_completion_action: 3 callbacks suppressed
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Apr 27 13:14:12 [kernel] print_req_error: 3 callbacks suppressed
Apr 27 13:14:12 [kernel] blk_update_request: I/O error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr 27 13:14:12 [kernel] Buffer I/O error on dev sdf, logical block 0, async page read
                - Last output repeated twice -
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Apr 27 13:14:12 [kernel] blk_update_request: I/O error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr 27 13:14:12 [kernel] Buffer I/O error on dev sdf, logical block 0, async page read
Apr 27 13:14:12 [kernel] ldm_validate_partition_table(): Disk read failed.
                - Last output repeated twice -
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Apr 27 13:14:12 [kernel] blk_update_request: I/O error, dev sdf, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr 27 13:14:12 [kernel] Buffer I/O error on dev sdf, logical block 0, async page read
Apr 27 13:14:12 [kernel]  sdf: unable to read partition table
Apr 27 13:14:12 [kernel] udevd[7461]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/host6/target6:0:0/6:0:0:2/block/sdf/queue/iosched/slice_idle} for writing: Permission denied
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:12 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:12 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
                - Last output repeated 6 times -
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:13 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr 27 13:14:13 [kernel] Buffer I/O error on dev sdf, logical block 123376, async page read
Apr 27 13:14:13 [kernel] udevd[7461]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/host6/target6:0:0/6:0:0:2/block/sdf/queue/iosched/slice_idle} for writing: Permission denied
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:13 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
                - Last output repeated twice -
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:13 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr 27 13:14:13 [kernel] Buffer I/O error on dev sdf, logical block 123376, async page read
Apr 27 13:14:13 [kernel] udevd[7461]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/host6/target6:0:0/6:0:0:2/block/sdf/queue/iosched/slice_idle} for writing: Permission denied
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:13 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:13 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
                - Last output repeated twice -
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:14 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Apr 27 13:14:14 [kernel] Buffer I/O error on dev sdf, logical block 123376, async page read
Apr 27 13:14:14 [kernel] udevd[7461]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/host6/target6:0:0/6:0:0:2/block/sdf/queue/iosched/slice_idle} for writing: Permission denied
                - Last output repeated 2 times -
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 Sense Key : Hardware Error [current]
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 Add. Sense: No additional sense information
Apr 27 13:14:14 [kernel] sd 6:0:0:2: [sdf] tag#0 CDB: Read(10) 28 00 00 0f 0f 80 00 00 08 00
Apr 27 13:14:14 [kernel] blk_update_request: I/O error, dev sdf, sector 987008 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
                - Last output repeated twice -
Apr 27 13:14:14 [kernel] Buffer I/O error on dev sdf, logical block 123376, async page read
Apr 27 13:14:14 [kernel] udevd[7461]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/host6/target6:0:0/6:0:0:2/block/sdf/queue/iosched/slice_idle} for writing: Permission denied
                - Last output repeated twice -
Apr 27 13:14:14 [kernel] Buffer I/O error on dev sdf, logical block 123376, async page read

_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
dr_wulsen
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2013
Posts: 132
Location: Austria

PostPosted: Mon Apr 27, 2020 6:58 pm    Post subject: Reply with quote

Hi Massimo,

I can only guess here that enabling the kernel option "CONFIG_USB_STORAGE_REALTEK" could help.
In my mind I imagine this solving the udevd[7461]: error opening ATTR{/sys/devices/pci0000:00/0000:00:14.0/usb3/3-9/3-9:1.0/host6/target6:0:0/6:0:0:2/block/sdf/queue/iosched/slice_idle} for writing: Permission denied issue.

A ~500MB SD Card is quite odd to me, but your kernel reports [kernel] sd 6:0:0:2: [sdf] 987136 512-byte logical blocks: (505 MB/482 MiB).
Is that the actual size?
_________________
There's no stupid questions, only stupid answers.
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1593
Location: PB, Germany

PostPosted: Tue Apr 28, 2020 11:27 am    Post subject: Reply with quote

I have built ums_realtek but it does not change anything, it does not seem to be related to my hardware.
I found a Micro SD, that is working on that device in the Micro SD slot. Using the same SD via adapter in the SD slot, I get the same failure. I guess the slot is broken then, what do you think?
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7677
Location: Saint Amant, Acadiana

PostPosted: Tue Apr 28, 2020 12:09 pm    Post subject: Reply with quote

I think you should boot some good liveCD and see what it can do with your card reader.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
dr_wulsen
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2013
Posts: 132
Location: Austria

PostPosted: Tue Apr 28, 2020 12:20 pm    Post subject: Reply with quote

I did have a similar issue back sometime, I just remembered.
Even it does not seem like an USB issue but rather originate from the card or reader, you can try a different USB port and cable if available.

Of course, booting a good live media can exclude a lot of kernel/software mis-configurations in a quick way.
_________________
There's no stupid questions, only stupid answers.


Last edited by dr_wulsen on Tue Apr 28, 2020 1:46 pm; edited 1 time in total
Back to top
View user's profile Send private message
Banana
Guru
Guru


Joined: 21 May 2004
Posts: 446
Location: Germany

PostPosted: Tue Apr 28, 2020 1:28 pm    Post subject: Reply with quote

And then? How to do know which option is the right one you need to make in the local installation?
_________________
My personal space
Back to top
View user's profile Send private message
dr_wulsen
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2013
Posts: 132
Location: Austria

PostPosted: Tue Apr 28, 2020 1:31 pm    Post subject: Reply with quote

@banana: and then we know there is some fruit hanging, which we may reach.
If it doesn't work with the live media, most likely there is nothing to gain, even with an allyesconfig ;)
_________________
There's no stupid questions, only stupid answers.
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1593
Location: PB, Germany

PostPosted: Tue Apr 28, 2020 1:57 pm    Post subject: Reply with quote

I definitely agree with testing hardware issues with live cds. That was a good hint. I'm going to check that first.
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
Banana
Guru
Guru


Joined: 21 May 2004
Posts: 446
Location: Germany

PostPosted: Tue Apr 28, 2020 5:13 pm    Post subject: Reply with quote

dr_wulsen wrote:
@banana: and then we know there is some fruit hanging, which we may reach.
If it doesn't work with the live media, most likely there is nothing to gain, even with an allyesconfig ;)

It was more a question on how to proceed and not to question the method itself. Ruling out and cornering the problem is always a good strategy.

So, if you know the live DVD does work, how to know which setting or module is the right one.
_________________
My personal space
Back to top
View user's profile Send private message
dr_wulsen
Tux's lil' helper
Tux's lil' helper


Joined: 21 Aug 2013
Posts: 132
Location: Austria

PostPosted: Tue Apr 28, 2020 7:01 pm    Post subject: Reply with quote

@banana: that's a valid point, my guess would be a diff of the 'drivers' section of both kernels (plus time)
or of couurse the magic-all-knowing deus-ex machina, someone like neddy seagoon here on the forums. but i'm just taking it step by step, hoping for the best.
Far as I can see, you're from Germany, which part, if I may ask?
_________________
There's no stupid questions, only stupid answers.
Back to top
View user's profile Send private message
Jaglover
Watchman
Watchman


Joined: 29 May 2005
Posts: 7677
Location: Saint Amant, Acadiana

PostPosted: Tue Apr 28, 2020 7:07 pm    Post subject: Reply with quote

First you look at dmesg, all hardware initialization is there. If still in doubt then have a look at lsmod output. LiveCD won't have such hardware support compiled in, it has to be module(s). It won't be hard to narrow it down, most modules have self explanatory names. And modinfo can tell more if needed.
_________________
Please learn how to denote units correctly!
Back to top
View user's profile Send private message
Banana
Guru
Guru


Joined: 21 May 2004
Posts: 446
Location: Germany

PostPosted: Tue Apr 28, 2020 7:27 pm    Post subject: Reply with quote

dr_wulsen wrote:
or of couurse the magic-all-knowing deus-ex machina, someone like neddy seagoon here on the forums. but i'm just taking it step by step, hoping for the best.

What would we be all without him ;-)
dr_wulsen wrote:
Far as I can see, you're from Germany, which part, if I may ask?

Northern part of Baden Württemberg

Jaglover wrote:
First you look at dmesg, all hardware initialization is there. If still in doubt then have a look at lsmod output. LiveCD won't have such hardware support compiled in, it has to be module(s). It won't be hard to narrow it down, most modules have self explanatory names. And modinfo can tell more if needed.

thx, will keep that in mind. Looking for loaded modules sounds a very good idea.
_________________
My personal space
Back to top
View user's profile Send private message
coderanger
Tux's lil' helper
Tux's lil' helper


Joined: 19 Sep 2018
Posts: 105
Location: Ukraine

PostPosted: Tue Apr 28, 2020 8:27 pm    Post subject: Reply with quote

I'm not good in reading the Kernel Scrolls, but 0x0181 is not defined on this page /usr/src/linux/drivers/usb/storage/unusual_realtek.h
Not sure if it should be there, and what UNUSUAL_DEV actually is, but...
Code:
UNUSUAL_DEV(0x0bda, 0x0177, 0x0000, 0x9999,
                "Realtek",
                "USB Card Reader",
                USB_SC_DEVICE, USB_PR_DEVICE, init_realtek_cr, 0),

UNUSUAL_DEV(0x0bda, 0x0184, 0x0000, 0x9999,
                "Realtek",
                "USB Card Reader",
                USB_SC_DEVICE, USB_PR_DEVICE, init_realtek_cr, 0),
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1593
Location: PB, Germany

PostPosted: Wed Apr 29, 2020 6:25 am    Post subject: Reply with quote

Testing with latest OpenSuse TW Live with systemd, it's almost the same issue:
Code:
kernel: sd 7:0:0:2: [sdg] 1002496 512-byte logical blocks: (513 MB/490 MiB)
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: ldm_validate_partition_table(): Disk read failed.
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 18 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 3, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 0, async page read
kernel:  sdg: unable to read partition table
kernel: scsi_io_completion_action: 6 callbacks suppressed
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 0f 4b 80 00 00 08 00
kernel: print_req_error: 6 callbacks suppressed
kernel: blk_update_request: I/O error, dev sdg, sector 1002368 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: buffer_io_error: 3 callbacks suppressed
kernel: Buffer I/O error on dev sdg, logical block 125296, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 0f 4b 80 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 1002368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 0f 4b 80 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 1002368 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 125296, async page read
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 0f 4b 80 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 1002368 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
kernel: sd 7:0:0:2: [sdg] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 7:0:0:2: [sdg] tag#0 Sense Key : Hardware Error [current]
kernel: sd 7:0:0:2: [sdg] tag#0 Add. Sense: No additional sense information
kernel: sd 7:0:0:2: [sdg] tag#0 CDB: Read(10) 28 00 00 0f 4b 80 00 00 08 00
kernel: blk_update_request: I/O error, dev sdg, sector 1002368 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
kernel: Buffer I/O error on dev sdg, logical block 125296, async page read

As this also happens with the working Micro-SD in the SD-adapter, I guess it's not about a faulty SD medium but rather the reader device. I can't imagine this is just a bad USB connector, as other slots and also the builtin USB loop-through are working. I'm going to replace the reader..
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
coderanger
Tux's lil' helper
Tux's lil' helper


Joined: 19 Sep 2018
Posts: 105
Location: Ukraine

PostPosted: Wed Apr 29, 2020 8:59 am    Post subject: Reply with quote

According to the git log https://github.com/torvalds/linux/commits/master/drivers/usb/storage/unusual_realtek.h the device id's were added one by one. Looks like they were added when someone bought card reader, observed it's not working, added it's device id, tested it's working and finally committed into the kernel sources.

I would try adding this device id 0x0181 into that file, recompile the module and test if the device is picked up by the driver and if it works at the end. If it works then you can make a commitment into linux project, if not - then yes, it's better to get different device which is proven to work with linux.
Code:
UNUSUAL_DEV(0x0bda, 0x0181, 0x0000, 0x9999,
                "Realtek",
                "USB Card Reader",
                USB_SC_DEVICE, USB_PR_DEVICE, init_realtek_cr, 0),
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1593
Location: PB, Germany

PostPosted: Wed Apr 29, 2020 9:38 am    Post subject: Reply with quote

No difference either. After 'modprobe ums-realtek' it's still the same. But anyway, if I can read on the Micro SD slot without having that module loaded, than I don't think it's the module for my device.
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum