Hallo, ich habe mir den Kernel 2.6.24-rc2 aus dem openSuSE-Repo kompiliert. Allerdings läuft mein Ricoh RL5c476 II MMC/SD-Cardreader (in Dell Inspiron 6000) nicht mehr, dieser lief zuletzt einwandfrei mit Kernel 2.6.21. Nun habe ich gesehen, dass es im neuen Kernel 2.6.24 einen neuen MMC-Layer geben soll. ( http://www.linux-magazin.de/news/neuer_mmc_layer_fuer_kernel_2_6_24_angekuen... ) Meine .config fürs Kompilieren des Kernels befindet sich anbei. Mit dem "Ricoh MMC Controller Disabler" habe ich bereits rumgespielt, diese Option hat keinen Einfluss auf das Verhalten. Getestet habe ich mit zwei verschiedenen SD-Karten, die unter Kernel 2.6.21 funktioniert haben und in zwei anderen Geräten (Handy, Kamera) sowie unter Windows auch laufen. Was mache ich falsch? Viele Grüße Thomas Mayer /var/log/messages liefert: Nov 24 16:43:05 thinux kernel: [ 1358.770456] usb 4-2: USB disconnect, address 2 Nov 24 16:43:05 thinux hald[2730]: forcibly attempting to lazy unmount /dev/sdb1 as enclosing drive was disconnected Nov 24 16:43:05 thinux kernel: [ 1358.826837] scsi 2:0:0:0: rejecting I/O to dead device Nov 24 16:43:05 thinux hald: unmounted /dev/sdb1 from '/media/disk' on behalf of uid 0 Nov 24 16:43:49 thinux kernel: [ 1364.808383] mmc0: new high speed SD card at address 0002 Nov 24 16:43:50 thinux kernel: [ 1364.825810] mmcblk0: mmc0:0002 SD1GB 999936KiB Nov 24 16:43:50 thinux kernel: [ 1364.825870] mmcblk0: p1 Nov 24 16:43:50 thinux hald: mounted /dev/mmcblk0p1 on behalf of uid 1000 Nov 24 16:44:00 thinux kernel: [ 1369.395297] FAT: Filesystem panic (dev mmcblk0p1) Nov 24 16:44:00 thinux kernel: [ 1369.395304] fat_get_cluster: invalid cluster chain (i_pos 0) Nov 24 16:44:00 thinux kernel: [ 1369.395311] File system has been set read-only Nov 24 16:44:00 thinux kernel: [ 1369.396460] FAT: Filesystem panic (dev mmcblk0p1) Nov 24 16:44:00 thinux kernel: [ 1369.396466] fat_get_cluster: invalid cluster chain (i_pos 0) Nov 24 16:44:00 thinux kernel: [ 1369.396496] FAT: Filesystem panic (dev mmcblk0p1) Nov 24 16:44:00 thinux kernel: [ 1369.396500] fat_get_cluster: invalid cluster chain (i_pos 0) Nov 24 16:44:00 thinux kernel: [ 1369.397028] FAT: Filesystem panic (dev mmcblk0p1) Nov 24 16:44:00 thinux kernel: [ 1369.397033] fat_get_cluster: invalid cluster chain (i_pos 0) Nov 24 16:44:00 thinux kernel: [ 1369.397444] FAT: Filesystem panic (dev mmcblk0p1) Nov 24 16:45:17 thinux kernel: [ 593.395220] FAT: Filesystem panic (dev mmcblk0p1) Nov 24 16:45:17 thinux kernel: [ 593.395222] fat_get_cluster: invalid cluster chain (i_pos 0) Nov 24 16:45:17 thinux kernel: [ 1387.091415] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.091426] mmcblk0p1: rw=0, want=2074859, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.091433] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.091438] mmcblk0p1: rw=0, want=2074835, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.110960] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.110970] mmcblk0p1: rw=0, want=2061611, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.110977] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.110982] mmcblk0p1: rw=0, want=2061587, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.116641] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.116649] mmcblk0p1: rw=0, want=2039083, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.116656] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.116661] mmcblk0p1: rw=0, want=2039059, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.142494] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.142503] mmcblk0p1: rw=0, want=2077515, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.142510] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.142516] mmcblk0p1: rw=0, want=2077491, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.158604] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.158612] mmcblk0p1: rw=0, want=2083115, limit=1999627 Nov 24 16:45:17 thinux kernel: [ 1387.158619] attempt to access beyond end of device Nov 24 16:45:17 thinux kernel: [ 1387.158648] mmcblk0p1: rw=0, want=2083091, limit=1999627 Nov 24 16:45:25 thinux kernel: [ 1389.042526] mmc0: card 0002 removed Nov 24 16:45:25 thinux hald[2730]: forcibly attempting to lazy unmount /dev/mmcblk0p1 as enclosing drive was disconnected Nov 24 16:45:25 thinux hald: unmounted /dev/mmcblk0p1 from '/media/CASIO-DSC' on behalf of uid 0 Nov 24 16:45:54 thinux kernel: [ 1392.600328] mmc0: new SD card at address bffc Nov 24 16:45:54 thinux kernel: [ 1392.600946] mmcblk0: mmc0:bffc SD02G 1985024KiB Nov 24 16:45:54 thinux kernel: [ 1392.601272] mmcblk0: Nov 24 16:45:54 thinux hald: mounted /dev/mmcblk0 on behalf of uid 1000 Nov 24 16:46:08 thinux kernel: [ 1397.043663] mmc0: card bffc removed Nov 24 16:46:08 thinux hald[2730]: forcibly attempting to lazy unmount /dev/mmcblk0 as enclosing drive was disconnected Nov 24 16:46:08 thinux hald: unmounted /dev/mmcblk0 from '/media/Speicherk.' on behalf of uid 0 Nov 24 16:46:12 thinux kernel: [ 1397.702042] mmc0: new SD card at address bffc Nov 24 16:46:12 thinux kernel: [ 1397.702420] mmcblk0: mmc0:bffc SD02G 1985024KiB Nov 24 16:46:12 thinux kernel: [ 1397.702608] mmcblk0: Nov 24 16:46:12 thinux hald: mounted /dev/mmcblk0 on behalf of uid 1000