View Single Post
Posts: 187 | Thanked: 121 times | Joined on Jun 2011 @ Subang Jaya, Selangor Darul Ehsan, Malaysia
#607
please let me know if I should post this over the nitdroid thread.

I have managed to get nitdroid to boot using u-boot by referring to this thread and the guide posted here. Before this I use multiboot and saw u-boot may be a better choice so I attempted to shift over. Everything sort of work as well as using multiboot, but unfortunately WiFi doesn't.

The main question is that whether the user experience is expected to be different when booting using multiboot vs. u-boot? I have attempted a nearly-identical setup with the only difference being the uImage offered by vakkov@nitdroid-forum for u-boot (tried with and without the additional patches).

My current setup mostly follows the above mentioned guide, but without all the patches (i.e. original init.nokia.rc, init_subsys, camd). The whole installation currently stays in a 8GB mini-SDHC card (class 4) partitioned to 2, where mmcblk1p1 (2GB) with FAT filesystem, and mmcblk1p2 (remaining capacity) in ext3. Instead of using boot.scr, I managed to make it boot by following the guide posted #324, with the following bootmenu settings

Code:
ITEM_NAME="NITDroid"
ITEM_KERNEL="uImage"
ITEM_DEVICE="${EXT_CARD}p1"
ITEM_FSTYPE="fat"
ITEM_CMDLINE="snd-soc-rx51.hp_lim=42 snd-soc-tlv320aic3x.hp_dac_lim=6 console=tty1 root=/dev/mmcblk1p2 rw rootdelay=5 init=/init panic=30 debug"
ITEM_REUSEATAGS=1
and the nitdroid and kernel modules installed are from N12_UMay.tar.bz2 and nitdroid-kernel-2.6.28-07_7-rc7_armel.deb

P/S: btw the multiboot approach I tried was done through the nitdroid-installer script