rts5139/rtsx_usb borked in 3.15+
Some time in 3.15, someone moved the rts5139 driver out of staging (I cannot find a changelog of this) and it got renamed to rtsx_usb. This, unfortunately, broke support for at least the RTS5139 card reader. I have found about zero other people on the internet having this problem (buried under all of the SVC repos that got indexed?), and was curious as to whether anyone here was having a similar problem and had fixed it.
Kernel versions tested to be experiencing the problem:
- 3.17.0-rc4
lsmod | grep rts
:
rtsx_pci 37855 0
rtsx_usb 17487 0
mfd_core 12601 3 lpc_ich,rtsx_pci,rtsx_usb
usbcore 187093 9 btusb,snd_usb_audio,uvcvideo,rtsx_usb,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd
lsusb | grep -i rts
:
Bus 001 Device 009: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Removing/reinserting the rtsx_usb module does nothing. Logs are silent when the reader is interacted with. Strange.
linux-kernel drivers kernel-modules
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
Some time in 3.15, someone moved the rts5139 driver out of staging (I cannot find a changelog of this) and it got renamed to rtsx_usb. This, unfortunately, broke support for at least the RTS5139 card reader. I have found about zero other people on the internet having this problem (buried under all of the SVC repos that got indexed?), and was curious as to whether anyone here was having a similar problem and had fixed it.
Kernel versions tested to be experiencing the problem:
- 3.17.0-rc4
lsmod | grep rts
:
rtsx_pci 37855 0
rtsx_usb 17487 0
mfd_core 12601 3 lpc_ich,rtsx_pci,rtsx_usb
usbcore 187093 9 btusb,snd_usb_audio,uvcvideo,rtsx_usb,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd
lsusb | grep -i rts
:
Bus 001 Device 009: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Removing/reinserting the rtsx_usb module does nothing. Logs are silent when the reader is interacted with. Strange.
linux-kernel drivers kernel-modules
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I have the same problem with kernel 3.16.6 and the RTS5129 card reader.
– TobiMarg
Dec 20 '14 at 16:05
On OpenSUSE this problem is fixed with kernel 3.16.7
– TobiMarg
Dec 21 '14 at 16:08
Same here on Linux Mint 17.2 under VirtualBox. It worked under Ubuntu 12.04...
– carveone
Oct 3 '15 at 13:06
As of 4.0 this appears to be fixed.
– Roman
Nov 23 '15 at 19:53
add a comment |
Some time in 3.15, someone moved the rts5139 driver out of staging (I cannot find a changelog of this) and it got renamed to rtsx_usb. This, unfortunately, broke support for at least the RTS5139 card reader. I have found about zero other people on the internet having this problem (buried under all of the SVC repos that got indexed?), and was curious as to whether anyone here was having a similar problem and had fixed it.
Kernel versions tested to be experiencing the problem:
- 3.17.0-rc4
lsmod | grep rts
:
rtsx_pci 37855 0
rtsx_usb 17487 0
mfd_core 12601 3 lpc_ich,rtsx_pci,rtsx_usb
usbcore 187093 9 btusb,snd_usb_audio,uvcvideo,rtsx_usb,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd
lsusb | grep -i rts
:
Bus 001 Device 009: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Removing/reinserting the rtsx_usb module does nothing. Logs are silent when the reader is interacted with. Strange.
linux-kernel drivers kernel-modules
Some time in 3.15, someone moved the rts5139 driver out of staging (I cannot find a changelog of this) and it got renamed to rtsx_usb. This, unfortunately, broke support for at least the RTS5139 card reader. I have found about zero other people on the internet having this problem (buried under all of the SVC repos that got indexed?), and was curious as to whether anyone here was having a similar problem and had fixed it.
Kernel versions tested to be experiencing the problem:
- 3.17.0-rc4
lsmod | grep rts
:
rtsx_pci 37855 0
rtsx_usb 17487 0
mfd_core 12601 3 lpc_ich,rtsx_pci,rtsx_usb
usbcore 187093 9 btusb,snd_usb_audio,uvcvideo,rtsx_usb,snd_usbmidi_lib,ehci_hcd,ehci_pci,usbhid,xhci_hcd
lsusb | grep -i rts
:
Bus 001 Device 009: ID 0bda:0139 Realtek Semiconductor Corp. RTS5139 Card Reader Controller
Removing/reinserting the rtsx_usb module does nothing. Logs are silent when the reader is interacted with. Strange.
linux-kernel drivers kernel-modules
linux-kernel drivers kernel-modules
asked Sep 15 '14 at 6:10
RomanRoman
113
113
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 16 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I have the same problem with kernel 3.16.6 and the RTS5129 card reader.
– TobiMarg
Dec 20 '14 at 16:05
On OpenSUSE this problem is fixed with kernel 3.16.7
– TobiMarg
Dec 21 '14 at 16:08
Same here on Linux Mint 17.2 under VirtualBox. It worked under Ubuntu 12.04...
– carveone
Oct 3 '15 at 13:06
As of 4.0 this appears to be fixed.
– Roman
Nov 23 '15 at 19:53
add a comment |
I have the same problem with kernel 3.16.6 and the RTS5129 card reader.
– TobiMarg
Dec 20 '14 at 16:05
On OpenSUSE this problem is fixed with kernel 3.16.7
– TobiMarg
Dec 21 '14 at 16:08
Same here on Linux Mint 17.2 under VirtualBox. It worked under Ubuntu 12.04...
– carveone
Oct 3 '15 at 13:06
As of 4.0 this appears to be fixed.
– Roman
Nov 23 '15 at 19:53
I have the same problem with kernel 3.16.6 and the RTS5129 card reader.
– TobiMarg
Dec 20 '14 at 16:05
I have the same problem with kernel 3.16.6 and the RTS5129 card reader.
– TobiMarg
Dec 20 '14 at 16:05
On OpenSUSE this problem is fixed with kernel 3.16.7
– TobiMarg
Dec 21 '14 at 16:08
On OpenSUSE this problem is fixed with kernel 3.16.7
– TobiMarg
Dec 21 '14 at 16:08
Same here on Linux Mint 17.2 under VirtualBox. It worked under Ubuntu 12.04...
– carveone
Oct 3 '15 at 13:06
Same here on Linux Mint 17.2 under VirtualBox. It worked under Ubuntu 12.04...
– carveone
Oct 3 '15 at 13:06
As of 4.0 this appears to be fixed.
– Roman
Nov 23 '15 at 19:53
As of 4.0 this appears to be fixed.
– Roman
Nov 23 '15 at 19:53
add a comment |
2 Answers
2
active
oldest
votes
Just an idea: partitions on memory cards are now found under names such as /dev/mmcblk0p1
. Maybe you have been waiting for /dev/sdb1
to appear? Make sure rtsx_usb
is loaded and try to mount /dev/mmcblk0p1
(or a similar name).
If that's not a solution for you, you might want to modprobe rtsx_usb
and post the related output of dmesg
? In my case, it's
usbcore: registered new interface driver rtsx_usb
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
mmcblk0: p1
Of course, you would make sure that the rtsx_usb_
-related modules aren't already loaded when you modprobe
.
Just as an additional info:
lsmod | grep rts
rtsx_usb_ms 16899 0
memstick 13696 1 rtsx_usb_ms
rtsx_usb_sdmmc 25280 0
rtsx_usb 17541 2 rtsx_usb_sdmmc,rtsx_usb_ms
mmc_core 102374 2 mmc_block,rtsx_usb_sdmmc
mfd_core 12601 2 lpc_ich,rtsx_usb
usbcore 195340 7 usblp,uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,xhci_hcd
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
add a comment |
As is pointed out in an answer to RTS5129 Card Reader with Ubuntu 15.10, asymingt wrote a temporary fix this.
Direct link to the github repo: https://github.com/asymingt/rts5139
add a comment |
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f155637%2frts5139-rtsx-usb-borked-in-3-15%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Just an idea: partitions on memory cards are now found under names such as /dev/mmcblk0p1
. Maybe you have been waiting for /dev/sdb1
to appear? Make sure rtsx_usb
is loaded and try to mount /dev/mmcblk0p1
(or a similar name).
If that's not a solution for you, you might want to modprobe rtsx_usb
and post the related output of dmesg
? In my case, it's
usbcore: registered new interface driver rtsx_usb
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
mmcblk0: p1
Of course, you would make sure that the rtsx_usb_
-related modules aren't already loaded when you modprobe
.
Just as an additional info:
lsmod | grep rts
rtsx_usb_ms 16899 0
memstick 13696 1 rtsx_usb_ms
rtsx_usb_sdmmc 25280 0
rtsx_usb 17541 2 rtsx_usb_sdmmc,rtsx_usb_ms
mmc_core 102374 2 mmc_block,rtsx_usb_sdmmc
mfd_core 12601 2 lpc_ich,rtsx_usb
usbcore 195340 7 usblp,uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,xhci_hcd
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
add a comment |
Just an idea: partitions on memory cards are now found under names such as /dev/mmcblk0p1
. Maybe you have been waiting for /dev/sdb1
to appear? Make sure rtsx_usb
is loaded and try to mount /dev/mmcblk0p1
(or a similar name).
If that's not a solution for you, you might want to modprobe rtsx_usb
and post the related output of dmesg
? In my case, it's
usbcore: registered new interface driver rtsx_usb
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
mmcblk0: p1
Of course, you would make sure that the rtsx_usb_
-related modules aren't already loaded when you modprobe
.
Just as an additional info:
lsmod | grep rts
rtsx_usb_ms 16899 0
memstick 13696 1 rtsx_usb_ms
rtsx_usb_sdmmc 25280 0
rtsx_usb 17541 2 rtsx_usb_sdmmc,rtsx_usb_ms
mmc_core 102374 2 mmc_block,rtsx_usb_sdmmc
mfd_core 12601 2 lpc_ich,rtsx_usb
usbcore 195340 7 usblp,uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,xhci_hcd
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
add a comment |
Just an idea: partitions on memory cards are now found under names such as /dev/mmcblk0p1
. Maybe you have been waiting for /dev/sdb1
to appear? Make sure rtsx_usb
is loaded and try to mount /dev/mmcblk0p1
(or a similar name).
If that's not a solution for you, you might want to modprobe rtsx_usb
and post the related output of dmesg
? In my case, it's
usbcore: registered new interface driver rtsx_usb
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
mmcblk0: p1
Of course, you would make sure that the rtsx_usb_
-related modules aren't already loaded when you modprobe
.
Just as an additional info:
lsmod | grep rts
rtsx_usb_ms 16899 0
memstick 13696 1 rtsx_usb_ms
rtsx_usb_sdmmc 25280 0
rtsx_usb 17541 2 rtsx_usb_sdmmc,rtsx_usb_ms
mmc_core 102374 2 mmc_block,rtsx_usb_sdmmc
mfd_core 12601 2 lpc_ich,rtsx_usb
usbcore 195340 7 usblp,uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,xhci_hcd
Just an idea: partitions on memory cards are now found under names such as /dev/mmcblk0p1
. Maybe you have been waiting for /dev/sdb1
to appear? Make sure rtsx_usb
is loaded and try to mount /dev/mmcblk0p1
(or a similar name).
If that's not a solution for you, you might want to modprobe rtsx_usb
and post the related output of dmesg
? In my case, it's
usbcore: registered new interface driver rtsx_usb
mmc0: new SDHC card at address e624
mmcblk0: mmc0:e624 SD04G 3.69 GiB
mmcblk0: p1
Of course, you would make sure that the rtsx_usb_
-related modules aren't already loaded when you modprobe
.
Just as an additional info:
lsmod | grep rts
rtsx_usb_ms 16899 0
memstick 13696 1 rtsx_usb_ms
rtsx_usb_sdmmc 25280 0
rtsx_usb 17541 2 rtsx_usb_sdmmc,rtsx_usb_ms
mmc_core 102374 2 mmc_block,rtsx_usb_sdmmc
mfd_core 12601 2 lpc_ich,rtsx_usb
usbcore 195340 7 usblp,uvcvideo,rtsx_usb,ehci_hcd,ehci_pci,usbhid,xhci_hcd
answered Dec 22 '14 at 10:20
leitungswasserleitungswasser
11
11
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
add a comment |
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
Nope. Dead silent.
– Roman
Feb 14 '15 at 3:33
add a comment |
As is pointed out in an answer to RTS5129 Card Reader with Ubuntu 15.10, asymingt wrote a temporary fix this.
Direct link to the github repo: https://github.com/asymingt/rts5139
add a comment |
As is pointed out in an answer to RTS5129 Card Reader with Ubuntu 15.10, asymingt wrote a temporary fix this.
Direct link to the github repo: https://github.com/asymingt/rts5139
add a comment |
As is pointed out in an answer to RTS5129 Card Reader with Ubuntu 15.10, asymingt wrote a temporary fix this.
Direct link to the github repo: https://github.com/asymingt/rts5139
As is pointed out in an answer to RTS5129 Card Reader with Ubuntu 15.10, asymingt wrote a temporary fix this.
Direct link to the github repo: https://github.com/asymingt/rts5139
answered Oct 10 '18 at 15:24
Moritz ObermeierMoritz Obermeier
111
111
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f155637%2frts5139-rtsx-usb-borked-in-3-15%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have the same problem with kernel 3.16.6 and the RTS5129 card reader.
– TobiMarg
Dec 20 '14 at 16:05
On OpenSUSE this problem is fixed with kernel 3.16.7
– TobiMarg
Dec 21 '14 at 16:08
Same here on Linux Mint 17.2 under VirtualBox. It worked under Ubuntu 12.04...
– carveone
Oct 3 '15 at 13:06
As of 4.0 this appears to be fixed.
– Roman
Nov 23 '15 at 19:53