Introducing ubiboot N9 (multiboot OS loader) - Page 8 - maemo.org

Active Topics

The N900 is now 15 years old! (7)
to Nokia N900 by Danct12 - 1 day, 18 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 2 days, 14 hrs ago
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 4 days, 23 hrs ago
more...

Page 8 of 140

Thread Tools

juiceme	2013-03-05 , 13:53
Community Council \| Posts: 4,920 \| Thanked: 12,867 times \| Joined on May 2012 @ Southerrn Finland	#71

Originally Posted by veeall

I couldn't get it to work. After kernel selection everything just blacked out. I copied nitroids zImage.pr13, zImage_2.6.32.54-openmode_l2fix to /boot/Harmattan/boot,

the correct place is /boot/ when you are running Harmattan. It only becomes /boot/Harmattan/boot when you are running ubiboot.

now I am on the road but I will be available later, I started building a bit different solugion using integrated initramfs instead of ubifs. It is easier to install but not as flexible as unifs based system, for example downgrading harmattan would be a bit more work with it.

Quote & Reply |

juiceme	2013-03-05 , 14:05
Community Council \| Posts: 4,920 \| Thanked: 12,867 times \| Joined on May 2012 @ Southerrn Finland	#72

Originally Posted by theyosh

Hmm... no luck... sorry. Same behavior. When I use the L2 cache patched version it still keeps rebooting and the battery is loading message is still there.. So for me nothing changed.

With the usb adapter connected or not... does not matter

This battery thing is strange, I do not know why would it even show anytthing like that if no cable is connected...

I vaguely remember something about "act-dead" mode of the device when it is assumedly switched off but in charging mode. Since the device must run the kernel in order to charge, it really is not off but only pretending...

Is it possible that there are some problems on the kernel command line that cause it to go to act-dead mode?

can you boot to ubiboot maintanance console, telnet in and do "dmesg" and "cat /proc/cmdline" and "cat /proc/original_cmdline" ?

Quote & Reply |

byteninja2	2013-03-05 , 18:43
Posts: 106 \| Thanked: 38 times \| Joined on Oct 2012	#73

Is there any fix yet? I am still stuck with error 1.

Quote & Reply |

juiceme	2013-03-06 , 08:29
Community Council \| Posts: 4,920 \| Thanked: 12,867 times \| Joined on May 2012 @ Southerrn Finland	#74

Originally Posted by byteninja2

Is there any fix yet? I am still stuck with error 1.

Can you please clarify? By error 1, do you mean you are unable to do the ubiattach on your device?

What is the kernel you are normally running, are you in full open mode?
What does your dmesg say about ubi devices?

If you are not running an aegis-neutered kernel, you could try flashing the openmode+l2fix kernel available at the ubiboot page.

sudo flasher -a firmware.bin -k zImage_2.6.32.54openmode_l2fix --flash-only=kernel -f -R
wait for the device to boot
enter root as devel-su
/usr/sbin/ubiattach /dev/ubi_ctrl -m 4
mount -t ubifs ubi0:var /mnt

Quote & Reply |

Mric	2013-03-06 , 11:41
Posts: 117 \| Thanked: 59 times \| Joined on Nov 2012	#75

Originally Posted by juiceme

If you are not running an aegis-neutered kernel, you could try flashing the openmode+l2fix kernel available at the ubiboot page.

sudo flasher -a firmware.bin -k zImage_2.6.32.54openmode_l2fix --flash-only=kernel -f -R

wait for the device to boot

enter root as devel-su

/usr/sbin/ubiattach /dev/ubi_ctrl -m 4

mount -t ubifs ubi0:var /mnt

Sorry for late reply, this worked fine for me.

1.sudo flasher -a firmware.bin -k zImage_2.6.32.54openmode_l2fix --flash-only=kernel -f -R
2.wait for the device to boot
3.follow the instructions on the README file
/usr/sbin/flash_erase /dev/mtd4 0 0
/usr/sbin/ubiattach /dev/ubi_ctrl -m 4
/usr/sbin/ubimkvol /dev/ubi0 -N var -m
mount -t ubifs ubi0:var /mnt

Thank you JuiceMe for fixing it

Quote & Reply |

The Following User Says Thank You to Mric For This Useful Post:
juiceme

byteninja2	2013-03-08 , 01:23
Posts: 106 \| Thanked: 38 times \| Joined on Oct 2012	#76

WARNING: bad kernel format in zImage_2.6.32.54openmode_l2fix
FIASCO ERROR: zImage_2.6.32.54openmode_l2fix: No such file or directory

I get this when I do that command Mric.

Quote & Reply |

juiceme	2013-03-08 , 06:15
Community Council \| Posts: 4,920 \| Thanked: 12,867 times \| Joined on May 2012 @ Southerrn Finland	#77

Originally Posted by byteninja2

WARNING: bad kernel format in zImage_2.6.32.54openmode_l2fix
FIASCO ERROR: zImage_2.6.32.54openmode_l2fix: No such file or directory

I get this when I do that command Mric.

You mean, you get this error when flashing? Make sure you spelled the command correctly and yhat you have the correct files there.

The kernel image must be in the same directory where you give the flasher command. (and of course your firmware.bin must also be in the same directory...)

Quote & Reply |

The Following User Says Thank You to juiceme For This Useful Post:
ch88xy

theyosh	2013-03-08 , 12:06
Posts: 12 \| Thanked: 5 times \| Joined on Mar 2010 @ Holland	#78

Originally Posted by juiceme

This battery thing is strange, I do not know why would it even show anytthing like that if no cable is connected...

I vaguely remember something about "act-dead" mode of the device when it is assumedly switched off but in charging mode. Since the device must run the kernel in order to charge, it really is not off but only pretending...

Is it possible that there are some problems on the kernel command line that cause it to go to act-dead mode?

can you boot to ubiboot maintanance console, telnet in and do "dmesg" and "cat /proc/cmdline" and "cat /proc/original_cmdline" ?

Ok, attached the dmesg output in maintenance modus

and output of /proc/cmdline

Code:

init=/init ubi.mtd=4 root=ubi0:var rootfstype=ubifs rw console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output

and for /proc/original_cmdline

Code:

 init=/sbin/preinit root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=tty0 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),16384k@3840k(kernel),2048k@20224k(log),469248k@22272k(var),32768k@491520k(moslo) bootreason=sw_rst bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=01314A4D4B0001005014 imei=357923044402107 g_nokia.iSerialNumber=357923044402107 serialnumber=CTK957179 omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:init_active:output,cmt_rst_rq:88:sysfs:init_active:output,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=1 vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a product_model=N9 hwid=1603

I hope that this helps some... I am unfamiliar with the act-dead thing. I need to research that a bit more.

Some more information that could be handy:

Code:

Filesystem                Size      Used Available Use% Mounted on
ubi0:var                415.0M     20.0M    390.3M   5% /
devtmpfs                492.2M         0    492.2M   0% /dev
none                     10.0M      8.0K     10.0M   0% /tmp
none                    256.0K     12.0K    244.0K   5% /var/run

cat /etc/mtab

Code:

rootfs / rootfs rw 0 0
ubi0:var / ubifs rw,relatime 0 0
devtmpfs /dev devtmpfs rw,size=503980k,nr_inodes=125995,mode=755 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /tmp tmpfs rw,relatime,size=10240k 0 0
/proc/sys/debug /proc/sys/debug debugfs rw,relatime 0 0
none /var/run tmpfs rw,nosuid,noatime,size=256k,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0

cat /etc/fstab

Code:

none    /dev        devtmpfs            defaults    0   0
proc    /proc       proc                defaults    0   0
sysfs   /sys        sysfs               defaults    0   0
none    /tmp        tmpfs               size=10M    0   0
/proc/sys/debug /proc/sys/debug debugfs defaults    0   0
none    /var/run    tmpfs               size=256k,mode=0755,nosuid,noatime  0   0
devpts  /dev/pts    devpts              defaults    0   0
/dev/mmcblk0p1  /mnt/1    vfat          defaults,noauto 0   0
/dev/mmcblk0p2  /mnt/2    ext4          defaults,noauto 0   0
/dev/mmcblk0p3  /mnt/3    ext4          defaults,noauto 0   0
/dev/mmcblk0p4  /mnt/4    ext4          defaults,noauto 0   0

fdisk

Code:

Disk /dev/mmcblk0: 15.8 GB, 15896412160 bytes
4 heads, 16 sectors/track, 485120 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

        Device Boot      Start         End      Blocks  Id System
/dev/mmcblk0p1              17      208512     6671872   c Win95 FAT32 (LBA)
/dev/mmcblk0p2          288513      419584     4194304  83 Linux
/dev/mmcblk0p3          419585      485120     2097152  83 Linux
/dev/mmcblk0p4          208513      288512     2560000  83 Linux

Partition table entries are not in disk order

Attached Files

dmesg-maintenance.txt.zip (7.8 KB, 94 views)

Quote & Reply |

The Following User Says Thank You to theyosh For This Useful Post:
juiceme

juiceme	2013-03-08 , 12:32
Community Council \| Posts: 4,920 \| Thanked: 12,867 times \| Joined on May 2012 @ Southerrn Finland	#79

Originally Posted by theyosh

Ok, attached the dmesg output in maintenance modus

All your basic settings seem to be in order, there is no reason that I see that the 2nd stage boot should fail.

Does your boot.conf list your kernels like you have set them up, meaning, does the boot menu for harmattan for example show the labels you have in conf file?

Could you post your boot.conf and the content of the directory you have your kernels on? (default, that is the directory /boot on mmcblk0p2)
And also, the content of the directory your modules are in (/lib/modules on mmcblk0p2)

I see you have the Nemo partition set up correctly, can you boot Nemo OK?