Hello, I believe that in previous version of Mageia, I was able to read my xD card. On Mageia 3, this card is not mounted anymore. It seems that one needs to enable r852 module to manage this card. Could you do it? This is the dmesg output just after I plugged the xD card. [ 3573.017073] r852: detected xD writeable card in slot [ 3573.318098] NAND device: Manufacturer ID: 0x98, Chip ID: 0xd3 (Toshiba xD 1GiB 3,3V) [ 3573.761191] sm_ftl: Found 1024 MiB xD/SmartMedia FTL on mtd0 [ 3573.825208] smblka: smblka1 Reproducible: Steps to Reproduce:
Summary: Cannot mount xD caard => Cannot mount xD card
well it seems your card reader is detected (a 1Go one)
It is, but in the previous Mageia version, the card was appearing in the "mounting widget" of KDE SC. Now, it is not the case anymore and I did not succeed to mount it manually.
From this post (https://bbs.archlinux.org/viewtopic.php?id=87722), I think that the module "ssfdc" is not enabled. Could you enable it the kernel to check if it solves my problem?
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 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. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD
It isstill not possible to mount a xDcard on Mageia 4. This is the dmesg output I get when I plug an xD card: [ 105.493171] r852: detected xD writeable card in slot [ 105.794182] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xd3 [ 105.794191] nand: Toshiba xD 1GiB 3,3V [ 105.794196] nand: 1024MiB, SLC, page size: 512, OOB size: 16
Status: RESOLVED => REOPENEDVersion: 3 => 4Resolution: OLD => (none)
(In reply to Olivier Delaune from comment #3) > From this post (https://bbs.archlinux.org/viewtopic.php?id=87722), I think > that the module "ssfdc" is not enabled. Could you enable it the kernel to > check if it solves my problem? (In reply to Olivier Delaune from comment #5) > It isstill not possible to mount a xDcard on Mageia 4. This is the dmesg > output I get when I plug an xD card: > [ 105.493171] r852: detected xD writeable card in slot > [ 105.794182] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xd3 > [ 105.794191] nand: Toshiba xD 1GiB 3,3V > [ 105.794196] nand: 1024MiB, SLC, page size: 512, OOB size: 16 CC'ing two KDE maintainers and kernel maintainer
CC: (none) => lmenut, mageia, marja11, tmb
The modules are there... Can you mount it manually ? What happends if you modprobe ssfdc ?
I typed "modprobe ssfdc" and than I plugged the xD card. Thi is the dmesg output I get [ 198.919919] SSFDC read-only Flash Translation layer [ 212.904034] r852: detected xD writeable card in slot [ 213.205050] nand: No NAND device found [ 213.205085] r852: detected xD writeable card in slot [ 213.506094] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xd3 [ 213.506101] nand: Toshiba xD 1GiB 3,3V [ 213.506104] nand: 1024MiB, SLC, page size: 512, OOB size: 16 [ 213.549478] sm_ftl: Found 1024 MiB xD/SmartMedia FTL on mtd0 [ 213.569504] sm_ftl: media unstable, not allowing writes [ 213.571247] sm_ftl: collision of LBA 196 between blocks 334 and 335 in zone 0 [ 213.581142] sm_ftl: both blocks are valid, erasing the later [ 213.683561] sm_ftl: no free blocks in zone 0 [ 213.683622] smblka: unknown partition table [ 213.840786] sm_ftl: no free blocks in zone 63 [ 213.841728] end_request: I/O error, dev smblka, sector 2048 [ 213.841736] Buffer I/O error on device smblka, logical block 256 [ 213.842048] end_request: I/O error, dev smblka, sector 2048 [ 213.842055] Buffer I/O error on device smblka, logical block 256 [ 213.842698] end_request: I/O error, dev smblka, sector 480 [ 213.842702] Buffer I/O error on device smblka, logical block 60 [ 213.842966] end_request: I/O error, dev smblka, sector 488 [ 213.842971] Buffer I/O error on device smblka, logical block 61 [ 213.843266] end_request: I/O error, dev smblka, sector 496 [ 213.843271] Buffer I/O error on device smblka, logical block 62 [ 213.843558] end_request: I/O error, dev smblka, sector 504 [ 213.843563] Buffer I/O error on device smblka, logical block 63 [ 213.843840] end_request: I/O error, dev smblka, sector 480 [ 213.843845] Buffer I/O error on device smblka, logical block 60 [ 213.844329] end_request: I/O error, dev smblka, sector 480 [ 213.844336] Buffer I/O error on device smblka, logical block 60 [ 213.844729] end_request: I/O error, dev smblka, sector 512 [ 213.844734] Buffer I/O error on device smblka, logical block 64 [ 214.000762] sm_ftl: no free blocks in zone 4 [ 214.001247] end_request: I/O error, dev smblka, sector 4096 [ 214.001251] Buffer I/O error on device smblka, logical block 512 Maybe my xD card is a bit broken but as it works fine within a card reader I guess the xD card is not so bad...
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: REOPENED => RESOLVEDResolution: (none) => OLD