Re: Hosed 810's internal 2G flash drive...

2008-02-12 Thread Tilman Vogel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eero Tamminen schrieb: Better to first check from mount output which MMC is which, one could easily confuse them when needing to use /media/mmc*/ path for one and /dev/ device name for another command. Having swap as file on corrupted mmc file

Re: Hosed 810's internal 2G flash drive...

2008-02-12 Thread Eero Tamminen
Hi, ext Tilman Vogel wrote: -BEGIN PGP SIGNED MESSAGE- Michael R. Head schrieb: I've tried umounting it and running fsck.vfat on it (over ssh), but I get a malloc error: Nokia-N810-50-2:~# fsck.vfat /dev/mmcblk0p1 dosfsck 2.11, 12 Mar 2005, FAT32, LFN alleged total clusters:

Re: Hosed 810's internal 2G flash drive...

2008-02-09 Thread Tilman Vogel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael R. Head schrieb: I've tried umounting it and running fsck.vfat on it (over ssh), but I get a malloc error: Nokia-N810-50-2:~# fsck.vfat /dev/mmcblk0p1 dosfsck 2.11, 12 Mar 2005, FAT32, LFN alleged total clusters: 999603

Re: Hosed 810's internal 2G flash drive...

2008-01-21 Thread Eero Tamminen
Hi, ext Michael R. Head wrote: I've been heavily using my 810 since I got it, and have had a few crashes. Recently, I've noticed that the 810's internal 2G drive is now readonly. I've tried reflashing the OS with RX-44_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin, but it's still coming up

Re: Hosed 810's internal 2G flash drive...

2008-01-21 Thread Michael R. Head
On Mon, 2008-01-21 at 10:22 +0200, Eero Tamminen wrote: Hi, ext Michael R. Head wrote: dosfsck 2.11, 12 Mar 2005, FAT32, LFN alleged total clusters: 999603 malloc:Input/output error Just connect the USB cable to the device and fix the FAT from your desktop computer. Cool tip!

Re: Hosed 810's internal 2G flash drive...

2008-01-20 Thread Michael Wiktowy
On Jan 20, 2008 1:54 PM, Michael R. Head [EMAIL PROTECTED] wrote: I've tried reflashing the OS with RX-44_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin, but it's still coming up read-only. I wouldn't expect reflashing the firmware to fix a problem on the internal flash drive. That process does