Hello. I downloaded Liquorix when I read, it solves a problem with some software (cameras etc.). I got in my laptop built-in SD card reader, listed by lsusb:Is there any chance to compile its driver into Liquorix kernel? There are some solutions on the internet, but I'm not very advanced user, neither programmer, and all my efforts to run this device failed. I suppose it's because I use 64-bit architecture (and kernels), and the solution was for 32-bit. I tried the device on Windows 7 to check if it's broken or so, but it works fine. On my Linux (Linux Mint Debian Edition 64 bit) all I can see in disk manager is unformatted 512 bytes long space for any SD card, and sometimes 388 GB (!) long for my old 32 MB MMC card. And the device can be seen (e.g. in disk manager or via lsusb) only when the card is inserted, opposing to any other USB reader I use.
Back to top

This module is already part of the Linux kernel, in the staging tree. What happens if you type, modprobe keucr?


Back to top

Nothing:

[new user link]

Of course I remembered to use sudo, and result of modinfo keucr is the same as yours, before and after modprobe. :(

Now I see it's not a Liquorix or not Liquorix issue… I should look for help maybe on other places, but if You can and want to help me, I'll be glad.
Back to top

Your picture indicates to me that it's being detected, but that's all.

What happens if you look for the drive or SD card using gparted? It could just be that it's not exposing itself to udev properly and you'll have to mount any card inserted manually. If that's the case, you should try listing the contents of /dev to see if you see anything new after plugging in your SD card.
Back to top

hi

a google came up with the link below but a short summary without quote boxes with some culling
-----------------------------------------------------

The drive is identified as 0cf2 ENE UB6250 id: 6250

the module is present in eneub6250.ko-ums
/Lib/modules/3.2.0-0.bpo.1-486/kernel/drivers/usb/storage/ums-eneub6250.ko
(this was kernel quoted above....yours will differ)

But missing the firmware, as reported by udev in / dev / .udev / firmware-missing


that expects a file named x2fsd_init1.bin
this leads to an error of I / O and the creation of the only device sdb, however unreadable.

so try downloading the firmware

dl.dropbox.com/u/1379722/linux-firmware/kernel-firmware-20111025git-1.7.1.noarch.rpm

then unpack the rpm and extract the firmware to the target folder for firmware



and the translated page is

translate.google.co.nz/translate?hl=en&sl=it&u=http://forum.debianizzati.org/viewtopic.php%3Fnomobile%3D1%26f%3D24%26t%3D45485%26start%3D15&ei=3ThVT83KPIHBiQfY0rz4Cw&sa=X&oi=translate&ct=result&resnum=2&ved=0CDMQ7gEwAQ&prev=/search%3Fq%3D3.2.0-0.bpo%2Bums_eneub6250%26hl%3Den%26client%3Dfirefox-a%26hs%3D2UM%26rls%3Dorg.mozilla:en-US:official%26prmd%3Dimvns
Back to top

Nice find aus9, that's that last piece to the puzzle. He has the module but is missing the firmware to utilize the hardware.
Back to top

Great job, Guys. That was it! Now it works, thanks a lot! :)
Back to top