Help - Search - Members - Calendar
Full Version: Sd Card On 3.5.4 On Collie
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > Angstrom & OpenZaurus
maskedbeagle
Hi All - Ive got a couple of collies - I've just been playing installing oz3.5.4RC - and like a few people on the openzaurus wordpress site, neither of my collies can use any of my sd cards - I've browsed round here a bit, and couldn't find a mention of this phenomonon - even in pinned 3.5.4 bugs and work arounds. Does anyone one know a solution for this?
thx
simcop2387
you need to install sharp-sdmmc-support i think it was, use bitbake to do this
chasetec
QUOTE(maskedbeagle @ Dec 20 2005, 07:11 AM)
Hi All - Ive got a couple of collies - I've just been playing installing oz3.5.4RC - and like a few people on the openzaurus wordpress site, neither of my collies can use any of my sd cards - I've browsed round here a bit, and couldn't find a mention of this phenomonon - even in pinned 3.5.4 bugs and work arounds. Does anyone one know a solution for this?
thx
*

Using the older 3.5.4 RC I could use my SD card on my Collie but with the latest 3.5.4 test release I can't use it either. I don't really have time to setup a development environment or start messing around with bitbake as someone else in this thread mentioned, I just wanted to help test and file bug reports. The SD card is a standard feature on every Collie so there is no reason support for it should be removed from the images, hopefully it's just a mistake that will get corrected.
cesarcardoso
IIRC you can get from sharp-sdmmc-support from 3.5.3. Hrw?
chasetec
QUOTE(cesarcardoso @ Feb 2 2006, 01:24 PM)
IIRC you can get from sharp-sdmmc-support from 3.5.3. Hrw?
*


Looking into it a little further the sharp-sdmmc-support is still included in the image but it's not working(at first).

ipkg status sharp-sdmmc-support
CODE
Package: sharp-sdmmc-support
Version: 2.4.18-rmk7-pxa3-embedix-r21
Depends: kernel (2.4.18-rmk7-pxa3-embedix), update-rc.d, libc6 (>= 2.3.5+cvs20050627)
Status: install ok installed
Architecture: collie

ipkg files sharp-sdmmc-support
CODE
Package sharp-sdmmc-support (2.4.18-rmk7-pxa3-embedix-r21) is installed on root and has the following files:
/etc/init.d/sd
/lib/modules/2.4.18-rmk7-pxa3-embedix/kernel/drivers/block/sharp_mmcsd_m.o
/sbin/sdmgr
/etc/sdcontrol


Doing a /etc/init.d/sd status returns nothing. I tried a /etc/init.d/sd start followed by a modprobe sharp_mmcsd_m. Doing a lsmod at that point showed the driver as loaded but unused(I didn't do a lsmod before). I rebooted with a reboot command and now the SD slot works everytime but I tried rebooting before and it didn't help. So it works now but I guess I'll reflash and see if I can duplicate the behavior.
chasetec
After flashing the SD card slot does not work, nor will it work after rebooting without manually loading the module at least once.

lsmod on first boot:
CODE
Module                  Size  Used by    Not tainted
sa1100_bi              22924   0 (unused)
net_fd                 16636   0 (unused)
usbdcore               22504   0 [sa1100_bi net_fd]
ipv6                  152344  -1


Relevent lines of dmesg after first boot(because this is where we should see something):
CODE
bi_device_event: call udc_all_interrupts
IrDA: Registered device irda1


Doing a lsmod sharp_mmcsd_m(still not working):
CODE
Module                  Size  Used by    Tainted: P  
sharp_mmcsd_m          25792   0 (unused)
sa1100_bi              22924   0 (unused)
net_fd                 16636   0 (unused)
usbdcore               22504   0 [sa1100_bi net_fd]
ipv6                  152344  -1


The only lines that occur at the end of dmesg after doing the lsmod sharp_mmcsd_m:
CODE
mmcda: mmcda1
SD Driver Initialized.
sharp_mmcsd 0.21 27 Sep 2002


After a reboot with the reboot command the SD slot works. lsmod shows:
CODE
Module                  Size  Used by    Tainted: P  
sharp_mmcsd_m          25792   2
sa1100_bi              22924   0 (unused)
net_fd                 16636   0 (unused)
usbdcore               22504   0 [sa1100_bi net_fd]
ipv6                  152344  -1


And comparing the output of dmesg to the dmesg after the first boot these are the changes:
CODE
bi_device_event: call udc_all_interrupts
Partition check:
mmcda: mmcda1
SD Driver Initialized.
sharp_mmcsd 0.21 27 Sep 2002
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
MSDOS FS: IO charset utf8
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 3c:01.
FAT: freeing iocharset=utf8
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
EXT2-fs: Unrecognized mount option user
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
EXT2-fs: Unrecognized mount option user
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
cramfs: wrong magic
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
MSDOS FS: IO charset utf8
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 3c:01.
FAT: freeing iocharset=utf8
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
jffs2: attempt to mount non-MTD device 3c:01
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
EXT2-fs: Unrecognized mount option user
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
EXT2-fs: Unrecognized mount option user
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
cramfs: wrong magic
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
jffs2: attempt to mount non-MTD device 3c:01
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Can't find a Minix or Minix V2 filesystem on device 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
FAT: bogus logical sector size 0
VFS: Can't find a valid FAT filesystem on dev 3c:01.
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
VFS: Disk change detected on device mmcd(60,1)
mmcda: mmcda1
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
IrDA: Registered device irda1


Not really sure why this is....
Hrw
shit.. that problem is strange for me... My collie worked with 16M mmc, 64/256/1024M sd cards with all 3.5.4-test images.

OK. looked at problem. It does not work on first start because /etc/init.d/sd use modprobe to load modules. But depmod is started later so modprobe is unable to find module to load. I'll try to fix it.
burned
I should've known any problems I was having with 3.5.4 would already be on the forums, well-documented... hooray for SD card working again (soon as I follow these instructions)!
samac
Hi I also got my SD card working with these instructions although the card does not show on the panel applet in opie 3.5.4.

I get the following message when trying to insert the card

QUOTE
Error while ing card in socket #1


The card shows as storage in system info and is writeable.

Samac
Hellmark
QUOTE(samac @ Mar 21 2006, 07:24 AM)
Hi I also got my SD card working with these instructions although the card does not show on theĀ  panel applet in opie 3.5.4.
I get the following message when trying to insert the card
QUOTE
Error while ing card in socket #1

The card shows as storage in system info and is writeable.
Samac
*



I just installed 3.5.4, and immediately, my SD card kinda sorta worked, but I am having the same issue, where it doesnt show on the applet, and it pukes the "Error while ing..." if I try to tell it to insert. Kind of a pain in the butt if you ask me.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.