tom_ wrote:you should insert the chip, then check the last part of dmesg
and maybe journalctl
Here's the results:
dmesg:
- Code: Select all
[ 1889.499331] mmc0: new SDHC card at address 0001
[ 1889.500662] mmcblk0: mmc0:0001 00000 7.46 GiB
[ 1889.502550] mmcblk0: p1
[ 1942.335127] mmc0: card 0001 removed
[ 1975.332642] mmc0: new SD card at address 0007
[ 1975.334183] mmcblk0: mmc0:0007 SD02G 1.84 GiB
[ 1975.336241] mmcblk0: p1
[ 1991.638121] mmc0: card 0007 removed
[ 2083.108624] mmc0: new SD card at address 0007
[ 2083.109883] mmcblk0: mmc0:0007 SD02G 1.84 GiB
[ 2083.112050] mmcblk0: p1
[ 2097.525108] mmc0: card 0007 removed
journlctl:
- Code: Select all
[root@localhost wilcal]# journalctl -a --since="13-01-02 08:40:00"
-- Logs begin at Sat, 2012-12-29 15:07:32 PST, end at Sat, 2012-12-29 16:23:49 PST. --
Jan 02 08:42:14 localhost smartd[607]: Device: /dev/sda [SAT], SMART Usage Attribute: 190 Airflow_Temperatu
Jan 02 08:42:14 localhost smartd[607]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsi
Jan 02 08:43:26 localhost kernel: mmc0: new SDHC card at address 0001
Jan 02 08:43:26 localhost kernel: mmcblk0: mmc0:0001 00000 7.46 GiB
Jan 02 08:43:26 localhost kernel: mmcblk0: p1
Jan 02 08:44:19 localhost kernel: mmc0: card 0001 removed
Jan 02 08:44:52 localhost kernel: mmc0: new SD card at address 0007
Jan 02 08:44:52 localhost kernel: mmcblk0: mmc0:0007 SD02G 1.84 GiB
Jan 02 08:44:52 localhost kernel: mmcblk0: p1
Jan 02 08:45:08 localhost kernel: mmc0: card 0007 removed
(END)
Interestingly enough a normal standard 8GB SD chips works fine. But the 1.84GB microSD
chip does not get reported. At least as far as the testing I have done. You can see the
7.46GB standard SD chip in the above code. Both chips, the standard and the micro
in an adapter, appear to have the same effect on both dmseg and journalctl.
I'm not quite ready to post a bug yet as I don't think I understand the situation enough.
Feel free to make any recommendations.