Re: problem accessing SD Card SanDisk SDSDQ-8192-E11M
On Mon, Sep 8, 2008 at 11:03 AM, Kevin Squire <[EMAIL PROTECTED]> wrote: > Hi, > >> I have problems accessing my 8Go SD Card > > For my disk, my thoughts are that the first sector is bad. I'll try > to confirm this later today (don't have anything else available that Confirmed, bad disk--can't read it with anything else (and in fact, trying to read it on my Ubuntu system puts sd_mod into a state where it won't read another disk). Kevin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: problem accessing SD Card SanDisk SDSDQ-8192-E11M
Hi, > I have problems accessing my 8Go SD Card Just to echo, I've had the same problem, and found exactly the same thing--I can't read the card right after boot, could eventually get it recognized, but had a hard time getting it recognized again and an impossible time trying to boot off of it. My card is a SDSDQ-8192 (at least that's what I ordered--any way to verify this?). Have you looked at dmesg after the read fails? In my case, I found something like: end_request: I/O error, dev mmcblk0, sector 0 end_request: I/O error, dev mmcblk0, sector 8 end_request: I/O error, dev mmcblk0, sector 16 end_request: I/O error, dev mmcblk0, sector 24 That I could eventually read it means that it's not totally fried, but for me at least that means that there's problems right at the beginning of the disk, where the boot sector is. Formatting the disk directly (mkfs.ext2 /dev/mmcblk0) seemed to confirm this--I got "short read" or "short write" errors for the first sector, though it formatted the rest of the disk fine (even when fdisk had troubles reading it). I did try setting the clock lower, (e.g., sd_max_clk=500, even 250), but that didn't help. For my disk, my thoughts are that the first sector is bad. I'll try to confirm this later today (don't have anything else available that can read the disk right now). The other possibility is the driver, but right now I'm thinking that's unlikely, as others have seemed to have gotten this disk working. (At least it's listed at http://wiki.openmoko.org/wiki/Supported_microSD_cards.) Suggestions for you: 1) check dmesg after you try to access the disk 2) lower the sd_max_clk further 3) format the disk without partitioning 4) test the disk in another reader 5) ??? 6) profit (maybe you can resell the disk on e-bay? ;-) Good luck, and please post again if you find anything. Kevin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: dfu-util upload problems
> Hi, > > I have a little problem with dfu-util and my new Freerunner. > > I thought I'd make a backup of my Neo's filesystem before flashing new > images onto it, so I tried to use dfu-util in upload mode to transfer > the content of the Neo's flash to my desktop PC. Backing up the kernel > partition works, but when I back up the rootfs partition dfu-util > transfers about 247MB and then dies with "dfu_upload error -84", while > the phone immediately reboots. It always dies at the same position, but > I'm not sure whether the backup is complete or not. Just wanted to say that I'm having the same problem (and same questions): I was able to upload 258076672 bytes (=246 Mb), but then dfu-util dies with "dfu_upload error -16", and the FreeRunner reboots. This is on Mac OS X. > Further details: I've tried it on my desktop and on my laptop PC, with > Ubuntu 7.10, Ubuntu 8.04 and a grml live-cd, with various dfu-util > binaries and one built from SVN, but the error appeared every time. The > phone was hooked up directly to the host (no hub or something), U-Boot > version on the phone is the originally installed 1.3.2-moko12 from May > 9. > > Any ideas what's wrong? At least one other person (you?) has indicated a similar problem at http://wiki.openmoko.org/wiki/Pre-Flash_Backup. Any ideas, anyone? Thanks, Kevin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
