My Lenovo x121e laptop has a Realtek PCI card reader which is unrecognized by Mageia 1. The rts_pstor driver provided by Realtek at the following address enables support in the Mageia kernel: http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=15&PFid=25&Level=4&Conn=3&DownTypeID=3&GetDown=false Still, userspace support seems needed to automount the partition when a card is inserted. Manual mounting works after installing the aforementioned driver. Ubuntu has already added support for it: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/698006 lspci -v: 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5209 (rev 01) Subsystem: Lenovo Device 21ed Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at d0d00000 (32-bit, non-prefetchable) [size=4K] Capabilities: <access denied> Kernel driver in use: rts_pstor Kernel modules: rts_pstor
I've noticed that rts_pstor.ko.gz is present in the cauldron kernel. In addition to the kernel module, proper udev rules will be needed to modprobe the module when the device is detected. Mageia 2, alpha 1 should be out November 16th. If you'd like to help test it, try installing a cauldron version of Mageia or wait and test it with Mageia 2 alpha 1, that would help to confirm if it has the needed udev rules, or needs to have them added. I don't think the kernel 3.x will be backported to mageia 1, nor will udev rules be added for a kernel module that is not available in mageia 1. I think this bug should either be closed as invalid (since it's for a module not provided by Mageia 1), or the target should be changed to mageia 2, and testing done with Cauldron or, when it's available, alpha 1. What do you think?
CC: (none) => davidwhodgins
> If you'd like to help test it, try installing a cauldron version > of Mageia or wait and test it with Mageia 2 alpha 1, that would > help to confirm if it has the needed udev rules, or needs to have > them added. Are there some ISOs of Cauldron live CDs somewhere? I couldn't find anything from the download page at mageia.org. > I don't think the kernel 3.x will be backported to mageia 1, nor > will udev rules be added for a kernel module that is not available > in mageia 1. For the record, I didn't have to compile any kernel myself. I just used the standard Mageia 1 kernel and compiled the Realtek module separately following the (simple) instructions in the tarball. > I think this bug should either be closed as invalid (since it's > for a module not provided by Mageia 1), or the target should be > changed to mageia 2, and testing done with Cauldron or, when it's > available, alpha 1. > > What do you think? Well, I'm just a user. But with the revised release schedule, Mageia 2 is quite far away and it would be nice to find a solution to enable support for various new hardware in Mageia 1.
(In reply to comment #2) > Are there some ISOs of Cauldron live CDs somewhere? I couldn't find > anything from the download page at mageia.org. the 16 November: http://blog.mageia.org/en/2011/10/22/new-planning-for-mageia-2/ I add the kernel maintainer on this bug.
See Also: (none) => https://launchpad.net/bugs/698006Assignee: bugsquad => tmbSource RPM: (none) => kernel
Depends on: (none) => 3186
Thank you, kernel 2.6.38.8-8.mga works here. The userspace side still needs to be fixed, but mounting manually works fine.
kernel-2.6.38.8-8.mga released to updates. So now the the other parts can be checked.
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.
CC: (none) => marja11
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX