I tried to used a PCI express card NI PCIe-8361 coupled to a NI PXI-1033 electronic module. I had to use another distribution (Ubuntu) for that these cards work. This is what I got when I type "lspci -x" >02:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200A PCI Express-to-PCI Bridge (rev 03) >00: 4c 10 31 82 00 00 10 00 03 00 04 06 00 00 01 00 >10: 00 00 00 00 00 00 00 00 00 00 00 00 01 01 80 02 >20: 00 00 00 00 01 00 01 00 00 00 00 00 00 00 00 00 >30: 00 00 00 00 50 00 00 00 00 00 00 00 ff 00 00 00 > >03:0f.0 Bridge: PLX Technology, Inc. PCI9054 32-bit 33MHz PCI <-> IOBus Bridge (rev ff) >00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff As you see the "ff" values are not really good. It works fine on Ubuntu and Fedora. I do not know if this bug report will be useful as I performed this test on a "pure" Mageia 4.1; I cannot update the system after the installation. So maybe this problem has been fixed by some updates later but I cannot test that. Anyway, it is quite strange that the kernel does not recognize well this hardware since it works perfetly on similar kernel on other distributions. I did not contact the manufacturer of the card/module (PLX Technology and National Instrument) because I am not really t ease concerning hardware problems. So, if you think this bug is interesting and should be fixed, please ask me what you need. Else, I think you can close it. Reproducible: Steps to Reproduce:
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: NEW => RESOLVEDResolution: (none) => OLD