|
Bugzilla – Full Text Bug Listing |
| Summary: | Lenovo N100 3000 5-in-1 memory card reader don't working | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Petr Novák <su.petr> |
| Component: | Kernel | Assignee: | Oliver Neukum <oneukum> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | lmb, su.petr |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
tree /sys/block > block.txt
Dmesg debug - acpi and mmc Ubuntu > SuSE merged config SuSE kernel dmesg Whole process repeated again with all reports dmesg -s 64000 |
||
|
Description
Petr Novák
2006-12-12 16:22:21 UTC
I forgot: mount /dev/mmc /mnt mount: /dev/mmc is not a valid block device. mount /dev/mmc0 /mnt mount: /dev/mmc0 is not a valid block device. PS: On openSUSE 10.2 GM freshly installed. What is the output of 'tree /sys/block' with a card plugged into the device? Petr, please provide the needed information, else we cannot help you. Information not provided for >1 month. Please reopen with the requested information if the problem persists. Created attachment 116009 [details]
tree /sys/block > block.txt
Sorry, for the long delay. I did not notice, that this bug was reopen. No progression from that time, but I attached asked info.
I reopened this issue with needed info (https://bugzilla.novell.com/attachment.cgi?id=116009&action=view). Was my reports usefull? Still does not work in fresh openSUSE 10.3 Alpha 3. Has this bug some activity progress? Please do not change the assignee randomly. I have absolutely no idea about USB ;-) What makes you think we are talking USB? The readers show up on lspci. Neither do I have any idea about MMC readers. What kind of card is this? It is the: 05:04.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller (rev 01) 05:06.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 05:06.1 Generic system peripheral [Class 0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 05:06.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) 05:06.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 0a) 05:06.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 05) I tried: MMC card from Nokia 6230 and MSPRO Duo card from SonyEricsson P990i. Booth without success. Lars: Excuse for that mistake. Please recompile your kernel with "MMC debugging" and provide dmesg. Created attachment 133019 [details]
Dmesg debug - acpi and mmc
Hello, I attached dmesg output with acpi and mmc enabled kernel. Excuse for Ubuntu kernel, but if I recompile this kernel (http://ftp.opensuse.org/pub/opensuse/repositories/Kernel:/HEAD/openSUSE_Factory/i586/kernel-source-2.6.21_rc7_git4-14.1.i586.rpm) my notebook Lenovo 3000 N100 did not boot. I tried a lot of tests with different SuSE kernels and initrd.imgs, but anything did not boot (during the boot I only saw first row: Uncompressing OK, booting linux... and this blank and black screen had shown forever without any progress). Ubuntu (initrd.img) or Frugalware (without initrd.img) customly by me recompiled kernels booting good. Created attachment 133020 [details]
Ubuntu > SuSE merged config
Created attachment 133021 [details]
SuSE kernel dmesg
I do not know where is the magic switch in config for notebooks booting, but if I used config from Ubuntu on SuSE kernel, compiled SuSE factory kernel was booted well (initrd.imgs have same config). OK, new reports are above. Did you do #16 with a card inserted into the slot? Yes, every reports were made with inserted card into the slot before booting the OS. Do You know now, what is wrong in my dmesg (e.g. general interrupt delivery problem)? Thank You very much for helping. PS: Have You got some advice to #17? According to your dmesg it works. Can you check the device node's major:minor? Hello Oliver, as I understood well, i checked the correct number at /proc/devices (number 252 from the line of MMC). mknod /dev/mmc b 252 0 mknod /dev/mmc0 b 252 1 mount /dev/mmc /mnt mount: /dev/mmc is not a valid block device. mount /dev/mmc0 /mnt mount: /dev/mmc0 is not a valid block device. Same as at the beginning :'(. Could you provide /proc/interrupts before and after you try to mount? Hello Oliver, I repeated the whole process and recorded it with script command. Please, look at attachement mmc_bug.txt. Created attachment 142431 [details]
Whole process repeated again with all reports
I sent another useful report. I recompiled kernel with mmc and acpi debug option. And so compiled mmc and acpi into kernel natively (not as loadable module). There is dnesg -s 64000. All behavior is same, dmesg do not know anything about removing , inserting mmc card. Interrupts do not change during removing, inserting mmc card. And so no new devices found in /dev beginning with letter m against previous large script report. Created attachment 142436 [details]
dmesg -s 64000
In this case something major is wrong with the hardware. I can only guess. Could you try with acpi=off Yes, I tried it also without success. Could you try pci=routeirq on the kernel command line? 5 weeks without response |