View Full Version : Which OS is best suited for N770?
Which OS is best suited for N770?
What is the latest version of ITOS 2006 and ITOS 2007?
I am a newbie.. just bought N770 and 2GB Mobile MMC.. Could someone please suggest me the best way to go?
My current OS versions is ITOS 1.2006.26-8
I have also downloaded the latest ITOS 2007 HE (SU-18_2007HACKER_2.2006.47-17_PR_F5_MR0_ARM.bin) from Nokia site.
I really got confused, whether to flash with OS 2006 edition v. 3.2006.49-2 or the Hacker edition? Which one is latest??
Some people are talking about http://fanoush.wz.cz/maemo/ kernel patches. Do I need to install these patches on 2006 version OS or 2007 OS?
Please help me................
Milhouse
2007-07-23, 11:36
1.2006.26-8 was/is the first version of OS 2006, and is pretty old (August 2006 I think). You definately want to upgrade this - it doesn't even support 2GB MMC.
If you want good stability and the device working as more-or-less promised, upgrade to OS 2006 3.2006.49-2 (this is the final version of OS 2006). This version does support 2GB MMC.
If you want to test the bleeding edge and don't care if stuff doesn't work a bit or not at all, upgrade to the Beta of OS 2007HE which is currently 2.2006.47-17 - this is pretty much a proof of concept rather than a finished article.
There are various patches on fanoush's site, but if you are referring to the high speed MMC patches, install these on OS 2006. They may possibly work on OS 2007HE as well, as I believe OS 2007HE is using the same kernel as OS 2006 (although I could be wrong, in which case you could end up with a non-booting device - just replace the original OS 2007HE kernel from the FIASCO image in that case, or reflash to recover).
A newer version of OS 2007 HE is due in the coming weeks.
I can confirm that fanoush's high-speed MMC kernel zImage-su-18-200639-2gb-mmcplus52Mhz-multiblockw.zip works fine with the current HE 2.2006.47-17, but it depends very much on the MMC brand/model. I have 2GB Kingston with MMC4 support. Follow the instructions on the fanoush's site and test the kernel before flashing at least one day. Or wait for the new HE :-)
Hi Milhouse,
Thank you so much.
I feel that better way to go with dual boot with latest ITOS 2006 and ITOS 2007 hack... and find out the best suited platform for my activities.
Thanks namorvx...
I really wanted to have this patch installed ... I will try it out soon.
How do i know that whether my MMC will support MMC4 or not?
Anyways.. which MMC specification is the latest supported for N770 to get the best performance?
Your suggestions are more appreciated.....
The tiny problem is that even if a card claims MMC4.1 support, it needn't run properly on the high-speed MMC kernel. You have to test it with your card(s). But I can tell you that high-speed mode with multiblock writes is significantly faster then the standard 12MHz one. Give the modified kernel a try. Good luck!
This site is incredible! You guys have answered my question before I even posed / posted it!
How do i know that whether my MMC will support MMC4 or not?
The card has 13 contacts (two rows). Plain MMC has 7.
Anyways.. which MMC specification is the latest supported for N770 to get the best performance?
MMC4.1 i.e all MMCmobile cards currently on market.
MMC4.2 is newest and adds >=4GB support just like SDHC but I think you can't buy such cards yet. These won't work with current kernels but patch is trivial so once they are on market support can be added.
As for performace - unless you want to flash kernel which support high speed MMC modes it doesn't matter which card you have in N770.
If you decide to use such kernel than is matters if the card supports only 26Mhz mode (all mmcmobile/mmcplus cards must support this) or can run at 52Mhz too (this mode is optional). You can find this only by testing. There are mmcmobile cards that support only 26Mhz mode (i.e. only half of maximum speed possible in N770).
Also it depends if the card is stable with N770 or not. For me the Kingston 2GB works fine and can do the fastest mode. I am not sure about other cards. Definitely there is some reason why Nokia restricts MMC clock to 12Mhz in their N770 kernel so YMMV.
If you decide to use such kernel than is matters if the card supports only 26Mhz mode (all mmcmobile/mmcplus cards must support this) or can run at 52Mhz too (this mode is optional). You can find this only by testing. There are mmcmobile cards that support only 26Mhz mode (i.e. only half of maximum speed possible in N770).
For testing we have to use command "flasher -l -b ..." as per http://fanoush.wz.cz/maemo/. Is this flasher Fanoush's flasher http://fanoush.wz.cz/maemo/#kernelflasher or is it the flasher from nokia site. The nokia site seems to work only from linus laptop over cable. But I do not have linux laptop. Can I use Fanoush's flasher to test ?
Can I use Fanoush's flasher to test ?
No. Linux is already running on the tablet when you run my flasher so it is too late to load Linux kernel to RAM. You can only flash it permanently and reboot. Nokia flasher talks to bootloader before Linux is booted so it can do such things.
Use linux live CD or vmware player to run nokia linux flasher.
Hi Fanoush,
Thanks a lot.
Use linux live CD or vmware player to run nokia linux flasher.
Fanoush, I downloaded Knoppix LIVE CD and burned onto a CD. I tried to run it on my Dell M70 but it freezes and the I googled and found that Knoppix on Dell M70 has that problem. SO I tried it on my old Dell Latitude CPi and booted using Live CD. It booted fine. I did "sudo -" to become root and ran the linux flasher. It stopped at "Sutable USB device not found, waiting". At this point, I connected the charger to N770 which was alread connected to USB via cable. But the flasher didn't buzz, it was still waiting. Do you have any idea what could be wrong ?
Thanks and appreciate all your help.
Fanoush, I tried LIVE CD on Dell inspiron 6000 and it said "Sending kernal image .....". Look like, it sent the the image.
Now when send was complete. I pushed the power button on n770 (with charger connected and also usb cable to laptop connected). The n770 booted fully. Then I removed the usb cable.
Is the kernel loaded ? How can I find whether the new kernel is running or the old one ?
BTW I am also able to access the original 64 MB MMC card which came with n770. That makes me wonder if I am running the new kernel. As the new kernel was supposed to be giving problem to MMC card which came with 770.
Thanks and appreciate all your help.
Is the kernel loaded ? How can I find whether the new kernel is running or the old one ?
BTW I am also able to access the original 64 MB MMC card which came with n770. That makes me wonder if I am running the new kernel. As the new kernel was supposed to be giving problem to MMC card which came with 770.
you can check in xterm
cat /proc/version
I am not sure about the specific kernel you have so post result here, you either should see fanoush@colinux or maemo@ubuntu-maemo there for my kernel. Next reboot brings nokia kernel back so you can see if it is different.
Also you can test read speed (as root)
Nokia-N770-48:~# time dd if=/dev/mmcblk0 of=/dev/null bs=4096 count=40000
40000+0 records in
40000+0 records out
real 0m 29.43s
user 0m 0.03s
sys 0m 1.75s
that's 160MB in 30 seconds ~= 5MB/s speed, original kernel does ~1.3MB/s
As for the 64MB card, yes some people reported it working, my device is early one from 2005 maybe later they shipped better cards.
Thanks Fanoush.
Here is some info. The tablet I have is
Product SU-18
hw-build 1802
nolo 0.9.14
The OS ver is 49-2. I put the kernel which is prepared by you (zImage-yuv420). The command 'cat /proc/version' gives
Linux version 2.6.16.27-omap1 (maemo@unbuntu-maemo) (gcc version 3.4.4 (release) (CodeSourcery) ARM 2005sq3-2)) #34 PREMPT Tue May 22 13:15:14 CEST 2007
The dd command gives following o/p
time dd if=/dev/mmcblk0 of=/dev/null bs=4096 count=40000
15680+0 redords in
15680+0 records out
real 0m 23.12s
user 0m 0.06s
sys 0m 1.67s
Now since my card is 64 MB, hence it read only 15680 records.
Edited Post (after few minutes of original post)
I rebooted, and then it said bifh1@doree instead of maemo@unbuntu-maemo. Also 'dd' took 44.4 sec (for 64 MB) instead of 23.12 sec.
Wow your kernel gives twice the speed !!!
Now one more question, if I flash your kernel permanently with your flasher utility and in future if I want to go back to original kernel, then will I be able to flash just the kernel or will I have to re-image the whole os ?
Where can I find the original kernel ? (I am sure I am being paranoid and I will not need it).
You have done wonderfull job. It is excellent.
Thanks and looking forward for your reply.
So is the above kernel, is yours ?
Yes.
The speed is 15680*4=62MB / 23s = 2.7MB/s (i.e half of speed of my test run above) This looks like mmcmobile card capable of 26Mhz mode.
In general this speed test may be less accurate on first run since some part may be already cached in RAM from previous random reading so the speed might be inflated. To be sure you can run it more times and take 2nd or third result. The data size must be greater that available free RAM. 62MB is probably OK for N770, 32 not, for N800 at least 128 MB should be read, preferably more.
Thanks Fanoush for qucik reply.
Just one more question, if I flash your kernel permanently with your flasher utility and in future if I want to go back to original kernel, then will I be able to flash just the kernel or will I have to re-image the whole os ?
Where can I find the original kernel ? (I am sure I am being paranoid and I will not need it).
Thanks for wonderfull job with kernel.
Just one more question, if I flash your kernel permanently with your flasher utility and in future if I want to go back to original kernel, then will I be able to flash just the kernel or will I have to re-image the whole os ?
Yes, as long as your system boots you can use this utility to flash any kernel including the original one. The original one can be extracted from full firmware image via Nokia linux flasher (flasher-2.0 -u -F SU-18....bin and take the zImage file) and then flashed without touching rest of the system.
Fanoush,
My 2GB card arived today. I wanted to make the system dual bood. I followed the instruction as given here (http://maemo.org/community/wiki/HowTo_EASILY_Boot_From_MMC_card) with the exception I used following for partition.
# sfdisk /dev/mmcblk0
/dev/mmcblk0p1:1,52500,6
/dev/mmcblk0p2:52501,,
/dev/mmcblk0p3:
/dev/mmcblk0p4:
The full process seem to go fine including the OS close. I cloned the 2006 49.2 which is original OS which it came with.
When I boot from mmc partition 2 ext 3, the lower blue bar goes upto 3/4 length and then I get the screen with applets for a fraction of second and then it reboots. Any idea why it cood be happening ?
I searched the forum but couldn't find any solution. Thanks for all your help. I have been bugging more than I should.
I rebooted from flash and mounted mmcblk0p2 ro mmc2. The df shows 294MB there with 145 MB used and 134 free. /mtdblock4 (internal fash) has 126 MB of which 83MB is used and 43 MB free. Shoud I delete everything and do tar again ? If yes then can you please help me with commands ? Thanks
Shoud I delete everything and do tar again ?
Yes, delete means running the mke2fs again, then mount it and then do the tar thing again. make sure you use GNU tar, not the default busybox tar. Also use the kernel with fast mmc speed and multiblock writes enabled, tar copy is a good test to check if that kernel is stable (and the copy will run much faster too). Don't forget to run umount before rebooting. If the copy still doesn't work, run the tar line without 'v', it should print only errors and there should be only one warning on the end about old timestamp. Also check kernel log via 'dmesg' command after copy is done, you shouldn't see any I/O errors there.
Yes, delete means running the mke2fs again, then mount it and then do the tar thing again. make sure you use GNU tar, not the default busybox tar. Also use the kernel with fast mmc speed and multiblock writes enabled, tar copy is a good test to check if that kernel is stable (and the copy will run much faster too). Don't forget to run umount before rebooting. If the copy still doesn't work, run the tar line without 'v', it should print only errors and there should be only one warning on the end about old timestamp. Also check kernel log via 'dmesg' command after copy is done, you shouldn't see any I/O errors there.
Thanks Fonoush.
The tar in /temp-tar/ is GNU tar.
The kernel is yours (zImage-yuv420.zip). I flashed your kernel using your flasher util. 'cat /proc/version' shows 'unbuntu@maemo....'.
I will do all of the above and post result here. Just one question before I do that. Should the /dev/mmcblk0p2 be mounted to /media/mmc2 before the last reboot (for boot from patition 2) or not ?
Thanks
The tar in /temp-tar/ is GNU tar.
yes, just make sure you are actually using it when copying :-)
Should the /dev/mmcblk0p2 be mounted to /media/mmc2 before the last reboot (for boot from patition 2) or not ?
No, anything you mounted by hand should be unmounted before reboot.
While doing /tar-temp/bin/tar ...., xterm died. dmesg has an error Out of memory: kill process 1195 (osso-xterm) score 4586 and and children.
Out of memory: Killed process 1261 (sh)
/opt has only following dirs (bin dev etc lib lost+found mnt opt srv sys tmp usr var) where as /floppy has many more. So looks like tar didn't do it job fully. It is breaking somewhere in 'usr' dir as that appears last in 'ls -altr /opt/*'.
Or is there any solution to out of memory ?
EDIT:
Now my n770 is continuously rebooting. It asks fro for from where to boot, I select flash then it shows white screen and then reboots and ask for where to boot from and is in continuous loop. Looks like I screwed something. I will reflash it with original 49.2 image and start again :-(
Fanoush,
I flashed with original 49.2 image and it started boot fine. I re did everything (applications etc). I am currently cloning the system using /tar-temp/. I did skip initfs though.
Can I do the initfs # tar zxvf initfs_flasher.tgz
# cd initfs_flasher/
# ./initfs_flash
after I did cloning ?
Thanks.
Fanoush,
My tar died again. Here is dump of dmesg
ering down
[ 3200.311828] aic23 powering up
[ 3200.316070] aic23_init_power() done
[ 3208.997833] aic23 powering down
[ 3209.322631] aic23 powering up
[ 3209.326873] aic23_init_power() done
[ 3211.695098] aic23 powering down
[ 3243.409942] aic23 powering up
[ 3243.414886] aic23_init_power() done
[ 3245.782409] aic23 powering down
[ 3277.041839] aic23 powering up
[ 3277.047027] aic23_init_power() done
[ 3279.411773] aic23 powering down
[ 3311.503082] aic23 powering up
[ 3311.508056] aic23_init_power() done
[ 3313.876190] aic23 powering down
[ 3345.151672] aic23 powering up
[ 3345.156707] aic23_init_power() done
[ 3347.528198] aic23 powering down
[ 3354.991271] aic23 powering up
[ 3354.995544] aic23_init_power() done
[ 3357.466339] aic23 powering down
[ 3415.075927] hwa742: setting update mode to disabled
[ 3415.075958] omapfb_notifier_cb(): event = DISABLED
[ 3422.865936] hwa742: setting update mode to manual
[ 3422.865997] omapfb_notifier_cb(): event = READY
[ 3425.973937] aic23 powering up
[ 3425.978637] aic23_init_power() done
[ 3428.346710] aic23 powering down
[ 3455.814788] aic23 powering up
[ 3455.819427] aic23_init_power() done
[ 3458.185638] aic23 powering down
[ 3499.690307] aic23 powering up
[ 3499.695312] aic23_init_power() done
[ 3502.060638] aic23 powering down
[ 3559.773101] hwa742: setting update mode to disabled
[ 3559.773162] omapfb_notifier_cb(): event = DISABLED
[ 3769.414642] hwa742: setting update mode to manual
[ 3769.414733] omapfb_notifier_cb(): event = READY
[ 3771.053741] aic23 powering up
[ 3771.058013] aic23_init_power() done
[ 3773.426696] aic23 powering down
[ 3829.489898] hwa742: setting update mode to disabled
[ 3829.489959] omapfb_notifier_cb(): event = DISABLED
[ 3924.717163] hwa742: setting update mode to manual
[ 3924.717254] omapfb_notifier_cb(): event = READY
[ 3928.424713] aic23 powering up
[ 3928.429443] aic23_init_power() done
[ 3930.794555] aic23 powering down
[ 3961.356597] aic23 powering up
[ 3961.361206] aic23_init_power() done
[ 3963.728424] aic23 powering down
[ 4021.288879] hwa742: setting update mode to disabled
[ 4021.288940] omapfb_notifier_cb(): event = DISABLED
[ 4072.375213] hwa742: setting update mode to manual
[ 4072.375305] omapfb_notifier_cb(): event = READY
[ 4072.769927] aic23 powering up
[ 4072.774566] aic23_init_power() done
[ 4077.247711] aic23 powering down
[ 4124.802917] oom-killer: gfp_mask=0x200d2, order=0
[ 4124.802978] [<c0025890>] (dump_stack+0x0/0x14) from [<c0070910>] (out_of_memory+0x40/0x1d8)
[ 4124.803161] [<c00708d0>] (out_of_memory+0x0/0x1d8) from [<c0071e10>] (__alloc_pages+0x240/0x2c4)
[ 4124.803344] [<c0071bd0>] (__alloc_pages+0x0/0x2c4) from [<c009d404>] (pipe_writev+0x1c4/0x390)
[ 4124.803497] [<c009d240>] (pipe_writev+0x0/0x390) from [<c009d5f4>] (pipe_write+0x24/0x2c)
[ 4124.803649] [<c009d5d0>] (pipe_write+0x0/0x2c) from [<c008ec50>] (vfs_write+0xe8/0x1a8)
[ 4124.803802] [<c008eb68>] (vfs_write+0x0/0x1a8) from [<c008edcc>] (sys_write+0x48/0x74)
[ 4124.803955] [<c008ed84>] (sys_write+0x0/0x74) from [<c001fde0>] (ret_fast_syscall+0x0/0x2c)
[ 4124.804107] r6 = 00002800 r5 = 00033000 r4 = 00002800
[ 4124.804168] Mem-info:
[ 4124.804229] DMA per-cpu:
[ 4124.804290] cpu 0 hot: high 18, batch 3 used:1
[ 4124.804351] cpu 0 cold: high 6, batch 1 used:5
[ 4124.804412] DMA32 per-cpu: empty
[ 4124.804443] Normal per-cpu: empty
[ 4124.804504] HighMem per-cpu: empty
[ 4124.804565] Free pages: 1368kB (0kB HighMem)
[ 4124.804656] Active:5302 inactive:5377 dirty:5175 writeback:178 unstable:0 free:342 slab:2432 mapped:5242 pagetables:228
[ 4124.804840] DMA free:1368kB min:1024kB low:1280kB high:1536kB active:21208kB inactive:21508kB present:65536kB pages_scanned:12348 all_unreclaimable? no
[ 4124.804962] lowmem_reserve[]: 0 0 0 0
[ 4124.805053] DMA32 free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
[ 4124.805175] lowmem_reserve[]: 0 0 0 0
[ 4124.805267] Normal free:0kB min:0kB low:0kB high:0kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
[ 4124.805389] lowmem_reserve[]: 0 0 0 0
[ 4124.805511] HighMem free:0kB min:128kB low:128kB high:128kB active:0kB inactive:0kB present:0kB pages_scanned:0 all_unreclaimable? no
[ 4124.805633] lowmem_reserve[]: 0 0 0 0
[ 4124.805694] DMA: 82*4kB 8*8kB 5*16kB 0*32kB 0*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 1368kB
[ 4124.805908] DMA32: empty
[ 4124.805938] Normal: empty
[ 4124.805999] HighMem: empty
[ 4124.806060] Swap cache: add 0, delete 0, find 0/0, race 0+0
[ 4124.806121] Free swap = 0kB
[ 4124.806182] Total swap = 0kB
[ 4124.806213] Free swap: 0kB
[ 4124.810424] 16384 pages of RAM
[ 4124.810485] 575 free pages
[ 4124.810546] 1991 reserved pages
[ 4124.810577] 2432 slab pages
[ 4124.810638] 6542 pages shared
[ 4124.810668] 0 pages swap cached
[ 4124.810882] Out of Memory: Kill process 937 (maemo-launcher) score 5789 and children.
[ 4124.810974] Out of memory: Killed process 937 (maemo-launcher).
[ 4124.811096] Out of memory: Killed process 934 (maemo-launcher).
[ 4124.811187] Out of memory: Killed process 939 (maemo-launcher).
[ 4131.292816] aic23 powering up
[ 4131.297424] aic23_init_power() done
[ 4132.452545] hwa742: setting update mode to disabled
[ 4132.452606] omapfb_notifier_cb(): event = DISABLED
[ 4134.622741] aic23 powering down
[ 4160.250091] hwa742: setting update mode to manual
[ 4160.250152] omapfb_notifier_cb(): event = READY
[ 4160.718322] aic23 powering up
[ 4160.722869] aic23_init_power() done
[ 4163.085968] aic23 powering down
[ 4166.827423] aic23 powering up
[ 4166.831634] aic23_init_power() done
[ 4171.521148] aic23 powering down
[ 4185.240722] aic23 powering up
[ 4185.245239] aic23_init_power() done
[ 4188.295043] aic23 powering down
[ 4189.009674] aic23 powering up
[ 4189.014709] aic23_init_power() done
[ 4192.606658] aic23 powering down
[ 4194.390197] aic23 powering up
[ 4194.395050] aic23_init_power() done
[ 4196.755615] aic23 powering down
[ 4197.780975] aic23 powering up
[ 4197.785186] aic23_init_power() done
[ 4203.186187] aic23 powering down
[ 4204.751556] aic23 powering up
[ 4204.756500] aic23_init_power() done
[ 4207.122802] aic23 powering down
[ 4212.114166] aic23 powering up
[ 4212.118438] aic23_init_power() done
[ 4216.021850] aic23 powering down
[ 4217.626739] aic23 powering up
[ 4217.631530] aic23_init_power() done
[ 4220.000274] aic23 powering down
[ 4220.434051] aic23 powering up
[ 4220.438323] aic23_init_power() done
[ 4222.802520] aic23 powering down
[ 4225.430480] aic23 powering up
[ 4225.434692] aic23_init_power() done
[ 4227.795379] aic23 powering down
[ 4228.585815] aic23 powering up
[ 4228.590118] aic23_init_power() done
[ 4230.950897] aic23 powering down
[ 4231.455139] aic23 powering up
[ 4231.460327] aic23_init_power() done
[ 4233.829650] aic23 powering down
[ 4234.717834] aic23 powering up
[ 4234.722076] aic23_init_power() done
[ 4238.258453] aic23 powering down
[ 4238.781951] aic23 powering up
[ 4238.786163] aic23_init_power() done
[ 4241.146789] aic23 powering down
[ 4244.384399] aic23 powering up
[ 4244.389343] aic23_init_power() done
[ 4246.756408] aic23 powering down
[ 4253.853820] aic23 powering up
[ 4253.858337] aic23_init_power() done
[ 4256.224426] aic23 powering down
[ 4259.151611] aic23 powering up
[ 4259.155853] aic23_init_power() done
[ 4261.525390] aic23 powering down
[ 4267.280334] aic23 powering up
[ 4267.284576] aic23_init_power() done
[ 4269.646240] aic23 powering down
[ 4281.851562] aic23 powering up
[ 4281.855804] aic23_init_power() done
[ 4299.216644] aic23 powering down
[ 4301.670471] aic23 powering up
[ 4301.674682] aic23_init_power() done
Q1. Any idea how do I fix this ?
Q2. Can I do Initfs_flasher after doing tar ? (I want to make sure that I am able to clone the system before I make tablet as dula boot) ?
Note: I am running your kernel zImage-yuv420.
Thanks and appreciate all your help.
Q1. Any idea how do I fix this ?
There is not enough free memory and oom-killer kills your xterm before the job is done. You may enable swap file or close unneeded applications. You may also try it over ssh so osso-xterm does not take memory. I'd start with enabling swap - control panel->Memory->Virtual. You may also just try second time in a row and hope oom killer will pick something else or memory is not that tight second time (strange but possible).
Q2. Can I do Initfs_flasher after doing tar ? (I want to make sure that I am able to clone the system before I make tablet as dula boot) ?
You can do it anytime it is not related to the cloning. It won't be much useful without system on mmc but it won't hurt.
As for the corrupted flash and reboot loop you mentioned - did you unmount both /floppy and /opt before reboot? Anything you mounted by hand should be unmounted before reboot.
Thanks fanoush,
First thing first. I enabled virtual memory to 64 MB and tar went fine. I booted from block 2 ext 2 and it boot just fine. Success at last. Thanks to your patiently answering my questions.
I'd start with enabling swap - control panel->Memory->Virtual.
Q1. I saw following error in dmesg after tar was successful.FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mckblk0p
Q2. Do you know what it is ? Should I do anything about it ?
As for the corrupted flash and reboot loop you mentioned - did you unmount both /floppy and /opt before reboot? Anything you mounted by hand should be unmounted before reboot.
I did.
Q3. I didn't even give following command '# chroot /mnt/initfs cal-tool --set-root-device ask:mmc2' and still I am able to dual boot. Do I need to give command ? Or can I just forget it ?
Thanks.
Thanks to your patiently answering my questions.
Well each time I hope it is the last one and everything is clear so this helps me to stay calm and answer again ;-)
Q1. I saw following error in dmesg after tar was successful.FAT: bogus number of reserved sectors
VFS: Can't find a valid FAT filesystem on dev mckblk0p
Q2. Do you know what it is ? Should I do anything about it ?
You tried to mount something as FAT filesystem but it is not FAT formatted. It is harmless.
Q3. I didn't even give following command '# chroot /mnt/initfs cal-tool --set-root-device ask:mmc2' and still I am able to dual boot. Do I need to give command ? Or can I just forget it ?
It shows boot menu on each boot, sets mmc2 as default option and after timeout boots it automatically. It may be the best setup some people want.
Thank Fanoush for all your answers.
I forgot to run the initfs update before cloning the whole system, now i cannot boot into the mmc card. anything can be done to help? I'M thinking to reclone the /mnt/initfs directory only. any suggestions?Thanks.
I forgot to run the initfs update before cloning the whole system, now i cannot boot into the mmc card. anything can be done to help? I'M thinking to reclone the /mnt/initfs directory only. any suggestions?Thanks.
Chyang. When I did the whole process second time, I intestionally did initfs_flash thingy after I cloned the whole system. Just boot from internal flash (anyway you have no choice yet). Then do Initfs_flah thingy and do shoutdown -r now . During boot now you will choice to boot from external mmc.
vBulletin® v3.8.8, Copyright ©2000-2024, vBulletin Solutions, Inc.