Install ICS on internal flash? Was stuck - now SOLVED!

[offbeatdave]

Having spent a while learning to installing Ubuntu stuff on internal flash (and having spent almost as long reflashing following errors until I got it right), I figured I'd have a go at popping the ICS image on it.

I repartitioned flash, popped the files from ICS on mmcblk0p1, copied the DATA stuff to mmcblk0p2, copied the SD card to mmcblk0p3, modified the grub.cfg to point root to /dev/mmcblk0p1

Code: Select all

set timeout=0

menuentry "Android" {
	linux /android/kernel quiet acpi_sleep=s3_bios,s3_mode rootdelay=1 LANG=en SRC=android root=/dev/mmcblk0p1 DATA=/dev/mmcblk0p2 SDCARD=/dev/block/mmcblk0p3 DPI=120 ETH_MAC=00:11:22:33:44:55
	initrd /android/initrd.img
}

When I get to detecting Androidx86... I get no further until I pop my Android USB stick in, whereupon it detects /dev/sda2 and continues to boot from the USB. I am guessing that somewhere, the Android image needs to be directed to boot from mmcblk0p1 (a bit like linux in its etc/fstab file) but that this is built into the image?

Any pointers much appreciated.

[offbeatdave]

Can anyone put an end to my tinkering and tell me what I'm doing wrong or if it can't be done?

I've tried various things in the grub.cfg file such as root=/dev/mmcblk0p1, root=/dev/ram0 and even missing out the root= bit altogether but I can't detect Android-x86 until I plug in a use stick.

[offbeatdave]

Grr. Tinkering is soooo frustrating at times but (usually) rewarding! Not feeling very rewarded at the moment though so giving up for the night.

[swifty]

You might want to boot to ics from USB and confirm that you can see /dev/mmcblk0p* from terminal... it may not have any support for the internal flash.

[offbeatdave]

Thanks. I'll have a look at this shortly. It's so frustrating as I can setup 1.2.x to boot internally with a grub.cfg of

Code: Select all

set timeout=0

menuentry "Android" {
	linux /android/kernel RAMZ=409600 video=efifb:off acpi_sleep=s3_bios,s3_mode rootdelay=1 LANG=en SRC=android DATA=dev/mmcblk0p2 SDCARD=/dev/block/mmcblk0p3 DPI=160 ETH_MAC=00:11:22:33:44:55
	initrd /android/initrd.img
}

with no problems at all.

[offbeatdave]

You might want to boot to ics from USB and confirm that you can see /dev/mmcblk0p* from terminal... it may not have any support for the internal flash.

...and I might do this by...

Am gradually getting out of my depth again and having to rapidly learn to swim a new stroke once more!

[offbeatdave]

Given that I can't suss it out but can get other versions running I'm presuming it can be done yet, unless you Android experts want to tell me otherwise!

[verg0]

Id too like to see ICS on the internal flash, maybe a modified version of the joggler reflashing tool could help here!...

[markeh]

Apologies for going off topic a little, but the first post mentioned installing ubuntu to the internal flash? Can this be done? Is there a guide anywhere?

[roobarb!]

Apologies for going off topic a little, but the first post mentioned installing ubuntu to the internal flash? Can this be done? Is there a guide anywhere?

Yup. The wiki is your friend.

That article could do with a little revision, though; I've never had an issue with arbitrarily resizing the internal partitions.

[sjjg]

OK, I spent some time looking at this today. mmcblk0 (i.e internal memory) does not appear either in /dev or /dev/block when the device is booted from a sda device or when switching to the tempfs that is created when the boot process goes looking for an ext2 partition to work with. (You get to the tempfs by adding DEBUG=1 to the kernel cmdline in grub and pressing Alt+2 or Alt+3 when it searches for a partition).

When in debug mode running

Code: Select all

cat /proc/devices

brings up block devices, including some labelled 'sd'... I think that we're getting this behaviour either because:

i) The SD 'auto-mount' feature is cacking things up. (Would still have to appear in /dev though?)

or

ii) The kernel hasn't been compiled correctly. We don't have the kernel config though, so there's no real way to tell for sure. My best guess is that something that needed to have been compiled in to the kernel either wasn't or was set to be compiled as a module. There don't seem to be any kernel modules in this release (perhaps this is standard for android?).

I've run out of time now, but it would be great if someone could take up the slack! I am pleased with the performance via usb and I'd like to ditch the stick asap!

[verg0]

+1 "Ditch the stick!"

[sjjg]

OK spent some more time on this today. My conclusion is that either:

The kernel has been compiled without mmc_block and sdhci modules or it lacks the SCH15 modules required to interface with everything successfully. One way or another we're not going to get internal booting with this kernel.

Ideally we'd have the kernel config file so that we could have a play with compilation. I am able to compile kernels, but they won't boot on the Joggler. I've tried using a kernel config file from a joggler kernel that I know works, but the ICS build doesn't seem to want to take either froyo or ubuntu kernel configs.

Hopefully mijuu will supply the information we need.

[offbeatdave]

Not had a chance to try this yet but...

http://translate.google.co.uk/translate ... %3Dimvnsfd

Fingers crossed...

[offbeatdave]

Yipee! Done it! See my post at http://www.jogglerwiki.com/forum/viewto ... =504#p8533