Closed Thread
Thread Tools
Posts: 1,306 | Thanked: 1,697 times | Joined on Dec 2009 @ Durham North-East UK
#621
mmcblk0 is indeed the emmc in maemo, in android its the microsd
 
Dousan's Avatar
Posts: 1,161 | Thanked: 1,707 times | Joined on Jan 2010 @ Denmark
#622
Originally Posted by xgrind View Post
Hi,

Unlikely.

I have formatted the SD card twice and the FAT partition is detectable in Maemo.

mmcblk0 seems to be eMMC instead of SD card. Can dj_steve confirm?
As far as i know the mmcblk0p1/p2 is the sdcard when it's mounted in multiboot (when booting NITdroid) and the mmcblk1p1/p2 is the eMMC (when booting NITdroid). Android sees the sdcard as internal storage and the eMMC as external.

In maemo it's correct mmcblk0 is the eMMC and mmcblk1 is the sdcard.

e: Haha beat me to it steve
__________________
My Procreate art:
https://folio.procreate.art/dousan

My Søciety6:
http://society6.com/Dousan
 
xgrind's Avatar
Posts: 51 | Thanked: 8 times | Joined on Jan 2010
#623
So I guess,

I have to reformat the SD card again?

Originally Posted by dj_steve View Post
mmcblk0 is indeed the emmc in maemo, in android its the microsd
__________________
N900 on LPR1.2, overclocked to 900MHz
 
Posts: 1,306 | Thanked: 1,697 times | Joined on Dec 2009 @ Durham North-East UK
#624
check the microsd is formatted /partitioned first
 
Posts: 376 | Thanked: 56 times | Joined on Jan 2010
#625
Any ideas anyone

Ive completly reformatted the sd card and gone through all the steps again and I still get lots of errors with processess shutting down constantly making android completly unusable

I never had any of these errors with the previous build

and nothing is different at all

The errors I get are as follows, follwed by a force close option

com.android.deskclock
com.android.sipdroid
com.android.amazon.mp3
com.android.mms
com.google.android.gm
com.android.providers.calendar
com.android.bluetooth
android.process.media
com.android.email
com.android.voicedialer
com.google.android.apps.maps
com.google.android.apps.googlevoice
com.android.inputmethod.latin
com.android.quicksearchbox
com.google.process.gapps
com.android.settings
com.google.android.talk
com.android.launcher
 
Posts: 1,306 | Thanked: 1,697 times | Joined on Dec 2009 @ Durham North-East UK
#626
if you can get into adb sonic check dmesg as im beginnign to think your microsd may be dodgy
 
Posts: 9 | Thanked: 3 times | Joined on Jan 2010
#627
how to remove multiboot application?
 
Posts: 376 | Thanked: 56 times | Joined on Jan 2010
#628
Originally Posted by dj_steve View Post
if you can get into adb sonic check dmesg as im beginnign to think your microsd may be dodgy
Cheers Steve

You know what I posted that whilst I rebooted and everything at the moment appears to be working quite well

setup the wireless, gone onto google market and been browsing a few apps and downloading them (which is why ive not been back here to post been a bit busy LOL)

I think I have a couple of other sd cards knocking about (as long as the kids dont mind not using their DS's )
 
Posts: 341 | Thanked: 57 times | Joined on Nov 2009
#629
Originally Posted by dj_steve View Post
provided the ls command shows both mmcblk1p1 and mmcblk1p2 just continue with formatting then install
Alright, thanks! Well I rebooted and did what you said (both p1 and p2 showed, so I went ahead and ran the two commands in step 5 for formatting). Here's the output so far:


Code:
BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ $ sudo gainroot
Root shell enabled


BusyBox v1.10.2 (Debian 3:1.10.2.legal-1osso30+0m5) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # ls /dev/mmcblk1* 
/dev/mmcblk1    /dev/mmcblk1p1  /dev/mmcblk1p2
/home/user # mkdosfs /dev/mmcblk1p1 
mkdosfs 3.0.1 (23 Nov 2008)
6
######/home/user # mke2fs -j -m0 /dev/mmcblk1p2 
mke2fs 1.41.3.maemo0 (12-Oct-2008)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
120720 inodes, 482560 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=494927872
15 block groups
32768 blocks per group, 32768 fragments per group
8048 inodes per group
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912

Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 26 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
/home/user #
My question is that I didn't necessarily un-mount the microSD card bore running the said steps (you can see there's no un-mounting happening in the above log) ... is this ok ?
 
Posts: 341 | Thanked: 57 times | Joined on Nov 2009
#630
OK in addition to the above, I have another question ..

I followed this guide right till the end .. And right at the end, I have an error with the last unmounting command; the unmounting doesn't happen:

Code:
/ # umount /and
umount: cannot umount /and: Device or resource busy
/ #
Also, what do I do now .. ? Like, is NITDroid installed at this point !? .. Don't we have to configure the bootloader or something ?
 
Closed Thread


 
Forum Jump


All times are GMT. The time now is 13:45.