Description of problem: I'm instaling 1-beta2 from iso image. There were a message "insmod'ing module sdhci_pci failed [...]" (see attachment). I was able to boot and start working. Version-Release number of selected component (if applicable): How reproducible: Single installation. Steps to Reproduce: 1. 2. 3.
Created attachment 355 [details] sdhci_pci installation errror
CC: (none) => pterjan, tmb
Could you _attach_ the output of lspcidrake -v? eg the "lspci.txt" file resulting from running the following command: lspcidrake -v > lspci.txt
Keywords: (none) => NEEDINFOCC: (none) => thierry.vignaudAssignee: bugsquad => thierry.vignaud
I don't remember for sure what box I had this problem on. There may be a few attachments.
Created attachment 711 [details] The box I used to test all Cauldron installation media
Created attachment 712 [details] The box I could have the problem
The "box I could have the problem" is the only one with sdhci_pci listed. Does it have sdhci_pci loaded? Does "modprobe sdhci_pci" failed on it?
# modprobe sdhci_pci #
(In reply to comment #7) > # modprobe sdhci_pci > # Is that a replay ? :)
I've just issued command from Mageia1 running on the box I had this bug. It looks like I had the same issue when I tried to replay.
(In reply to comment #7) > # modprobe sdhci_pci > # @ Thierry Is that enough reply? In other words: can the NEEDINFO keyword be removed?
CC: (none) => marja11
I would like to have your /root/drakx/report.gz from this machine
Created attachment 1413 [details] Copy of /root/drakx/reportbug.gz
There'll be a workaround in next installer
Keywords: NEEDINFO => (none)
(In reply to comment #13) > There'll be a workaround in next installer @ Palm please test with Mageia 2 rc wether this got fixed for you http://blog.mageia.org/en/2012/05/09/almost-there-download-mageia-2-rc-new-date-for-final-release/
Keywords: (none) => NEEDINFO
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD