|
2013-08-27
, 14:33
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#442
|
And fail.... like in the last 3 days...
Can reach Ubiboot menu, can reach repair console, cannot start any of the OS.... ?!
...
Hum.... wtf... The zImage_2.6.32.54-ubiboot-02_040613 I flashed is 7,899,680Bytes while the one I just downloaded is 6,706,056 bytes ?!
Edit: MD5S matches on the image I originally downloaded. Which file could prevent any OS to load, if corrupted ?
EDIT2: Duhhhh... I untar the preinits.tar directly in "/sbin/" not in "/"
|
2013-08-27
, 14:38
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#443
|
One of the advantages of Open mode and ubiboot should be: 'You will not need to flash the device to install and test a new kernel; just copying the kernel and modules to the device is enough.'
Download file:
zImage
ubiboot-02_040613.tar
Copy to /home/user/MyDocs/boot:
ubiboot.conf
ubiboot-02.menus.cpio
Copy to /boot (which is empty!):
zImage (changed to zImage_e-yes_nitdroid+12fix)
zImage_2.6.32.54-ubiboot-02_040613
Correct and if then further what to do?
The Following User Says Thank You to juiceme For This Useful Post: | ||
|
2013-08-27
, 15:01
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#444
|
This is how it is, when you have it working after that you need never again use flasher to update your kernels.
Correct up to now, however you do not need to put zImage_2.6.32.54-ubiboot-02_040613 into /boot/
Every other kernel you need goes to /boot/, and possinbly if you have different modules then they go to /lib/modules/<kernelname>/
However, the zImage_2.6.32.54-ubiboot-02_040613 is the ubiboot kernel, the 1st stage kernel that you need to flash to the device.
|
2013-08-27
, 15:03
|
Posts: 181 |
Thanked: 64 times |
Joined on Feb 2012
|
#445
|
|
2013-08-27
, 16:06
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#446
|
Does it mean that even if I have Open mode right now I need to flash to get the ubiboot-2 kernel?
Or even if I have the old stuff: "zImage.pr13: (not recommended) before Ubiboot was published, this was the latest zImage being used for dual-booting or multi-booting NITDroid."
It's not enough to avoid flash to get new kernel?
The Following User Says Thank You to juiceme For This Useful Post: | ||
|
2013-08-27
, 16:10
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#447
|
Yes, I can boot Harmattan , Android and Nemo 2.6.32.
Thank you !
Is it normal I cannot boot (black screen) "Unstable 3.5.3 SabreTSq" ?
I read that it could take some time, so I have plugged it and I am waiting...
|
2013-08-28
, 09:02
|
Posts: 545 |
Thanked: 560 times |
Joined on Dec 2011
@ lebanon
|
#448
|
|
2013-08-28
, 12:24
|
Posts: 545 |
Thanked: 560 times |
Joined on Dec 2011
@ lebanon
|
#449
|
|
2013-08-28
, 14:53
|
Community Council |
Posts: 4,920 |
Thanked: 12,867 times |
Joined on May 2012
@ Southerrn Finland
|
#450
|
I have earlier used this procedure for Open mode: http://forum.nitdroid.com/index.php?topic=241.0
meaning zImage.pr13 but without sillyboot and NITDroid.
Instead I have multiboot from here:
http://talk.maemo.org/showthread.php?t=86957
I have flashed to Open mode in Windows7 therefore /boot is empty (e.g. no zImage here)
Checking my N9 in terminal shows:
~ # export LANGUAGE=C
~ # accli -I
Current mode: open
IMEI: 357923045945013
Credentials:
UID::root
GID::root
GRP::root
GRP::adm
GRP::dialout
GRP:: pulse-access
~ # uname -r
2.6.32.54-dfl61-20121301
Want to change kernel to:
zImage_2.6.32.54-ubiboot-02_040613
Using this procedures:
http://wiki.maemo.org/Ubiboot#Moving...g_Filebox_Root
Download file:
zImage
ubiboot-02_040613.tar
Copy to /home/user/MyDocs/boot:
ubiboot.conf
ubiboot-02.menus.cpio
Copy to /boot (which is empty!):
zImage (changed to zImage_e-yes_nitdroid+12fix)
zImage_2.6.32.54-ubiboot-02_040613
Correct and if then further what to do?
OK
Last edited by Garp; 2013-08-27 at 12:31.