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

maemo.org - Talk (https://talk.maemo.org/index.php)

- Alternatives (https://talk.maemo.org/forumdisplay.php?f=36)

- - Introducing ubiboot N9 (multiboot OS loader) (https://talk.maemo.org/showthread.php?t=89345)

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326669)

Fairly strange, that.

I tried several combinations, mounting with/without the ubi device attached etc, and only time that error happens is when you try to do it as user.
As root, it never gives that error.

i get the same error as user or as root

Code:

~# whoami

root

~# mount -t ubifs ubi0:var /mnt

mount: permission denied (are you root?)

Code:

~ $ whoami

user

~ $  mount -t ubifs ubi0:var /mnt

mount: permission denied (are you root?)

should I throw away my n9? :P :D

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326673)

One thing came to my mind... Yo said you booted the device at some point?

After you boot the device, you must attach the ubi device before mounting, sou you need to do this:

Code:

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

mount -t ubifs ubi0:var /mnt/

You never need to give the commands for flash_erase or ubimkvol again, but every time you want to mount it, you need to attach it before that.

i reboot after (/usr/sbin/flash_erase /dev/mtd4 0 0)
because (/usr/sbin/ubiattach /dev/ubi_ctrl -m 4) dont work

after reboot i done
/usr/sbin/ubiattach /dev/ubi_ctrl -m 4
/usr/sbin/ubimkvol /dev/ubi0 -N var -m
mount -t ubifs ubi0:var /mnt
and i got error on the mount

now i tryed to reboot again and as you said i done

Code:

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

mount -t ubifs ubi0:var /mnt/

but i have the same error on the mount

Code:

RM696-21-3_PR_001:~# /usr/sbin/ubiattach /dev/ubi_ctrl -m 4

UBI device number 0, total 1833 LEBs (473001984 bytes, 451.1 MiB), available 0 LEBs (0 bytes), LEB size 258048 bytes (252.0 KiB)

RM696-21-3_PR_001:~# mount -t ubifs ubi0:var /mnt

mount: permission denied (are you root?)

Re: Introducing ubiboot N9 (multiboot OS loader)

I also have the same error as phoenix986.

Re: Introducing ubiboot N9 (multiboot OS loader)

Are you sure you're doing this with devel-su instead of "opensh"?

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326648)

I don't understand what bugs you mean, I have been running my device always in open mode, (both PR1.2 and with PR1.3 since it came out) and I have never gotten my device crashed, not when installing anything nor ever else...

Can you point me to the cases when open mode has caused such problems?

I also follow the N9QTweak thread, and in the past I had Open Mode Kernel for NITdroid.
Many people, like me, when installing, for example, two or more tweaks or sub-tweaks at the same time, after the first, the second or randomly, the system close N9QTweak (with installation in progress, interrupted) and goes to home screen.. The same happened, randomly, with installation of apps: in a first time it seems that is installing, but randomly the installation crash and goes to desktop with apps not installed..
The above is common to all that have open Mode kernel.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Hurrian (Post 1326699)

Are you sure you're doing this with devel-su instead of "opensh"?

Yes, I typed “devel-su“, then I typed the password, and typed the command. I have tried with the open mode kernal and without.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by death_jax (Post 1326717)

OK, but those are bugs of N9QTweak, they are not related to open mode in any way, IMHO.

BTW, I am not using any modifications on my device like N9QTweak, FasterN9, OC modules, etc. Only extra "tweaks" I have are Profilematic and Home Screen Settings. I have NOT tested ubiboot with any other setup.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by byteninja2 (Post 1326719)

Yes, I typed “devel-su“, then I typed the password, and typed the command. I have tried with the open mode kernal and without.

Well, does your "dmesg" show anything relating to FS corruption or like? If you have too many ecc errors on the NAND then the mtd4 partition cannot be used and it will be mounted read-only.

I have been told that some of the NAND chips are quite error prone, and that is the reason Nokia did not use the mtd4 partitions for /var filesystem as was original intent.

There is another way to store the boot manager, using initramfs on a mmcblk0 partition. I will have to explore that as an alternative if many people start getting the write errors on mtd4.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Phoenix986 (Post 1326651)

after a reboot it worked without error

EDIT: now i get this

Code:

~ # mount -t ubifs ubi0:var /mnt

mount: permission denied (are you root?)

this is the previous

Code:

~# /usr/sbin/ubiattach /dev/ubi_ctrl -p /dev/mtd4

UBI device number 0, total 1833 LEBs (473001984 bytes, 451.1 MiB), available 1811 LEBs (467324928 bytes, 445.7 MiB), LEB size 258048 bytes (252.0 KiB)



~# /usr/sbin/ubimkvol /dev/ubi0 -N var -m

Set volume size to 467324928

Volume ID 0, size 1811 LEBs (467324928 bytes, 445.7 MiB), LEB size 258048 bytes (252.0 KiB), dynamic, name "var", alignment 1



~# mount -t ubifs ubi0:var /mnt

mount: permission denied (are you root?)

try:

Code:

opensh

aegisctl +r

then see if that worked.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326723)

The problem is not related with N9QTweak (there are many discussions about it), because I wrote that also with normal app installation there was that bug.. In addition to that, the N9QTweak use only dpkg -i command prompt, in fact when I tried to install some apps with command prompt, I had the same issue, the command prompt automatically exits before the installation was completed.

Re: Introducing ubiboot N9 (multiboot OS loader)

But I am still quite confident that those problems are not related to runnig in Open Mode. What kind of open mode are you talking about, since not all open modes are born equal? :D

The "crippled open mode" is just running the normal aegis-enabled kernel after triggering open mode either accidentally or on purpose, which may get you into all kinds of problems.
The "aegis-neutered open mode" is when you are running a specially patched kernel that allows full root access to the device.
The "full open mode" is when you have also removed the aegisfs configuration entries from your /etc/

Those problems with n9QTweak, is it so that nobody has ran into those problems when using closed mode?

One thing to remember:

Whether you use aegis-neutered kernel or not, your device will ALWAYS be in open mode after you use the flasher to load ANY kernel that is not signed by Nokia.

Even if you just load it in rescue mode, and do not flash it. Just booting a nonsigned kernel will do ti.

Once you trigger Open Mode there is ONLY ONE WAY to ever go back to closed mode, and thet is by full flashing both firmware and EMMC.

Re: Introducing ubiboot N9 (multiboot OS loader)

I consulted some highly skilled developers and both agree that with Open Mode you are less likely to get random crashes than on Closed mode.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326749)

But I am still quite confident that those problems are not related to runnig in Open Mode. What kind of open mode are you talking about, since not all open modes are born equal? :D

The "crippled open mode" is just running the normal aegis-enabled kernel after triggering open mode either accidentally or on purpose, which may get you into all kinds of problems.
The "aegis-neutered open mode" is when you are running a specially patched kernel that allows full root access to the device.
The "full open mode" is when you have also removed the aegisfs configuration entries from your /etc/

I didn't tried all mode :D, but I meant that I flashed the zImage.pr13 kernel patched for NITdroid..
If I remember correctly, also thedead1440 had that problems with that Open Mode.
In fact now I have only enabled Inception, I have the same N9QTweak enabled, and all goes well, but in Open Mode I had many installation problems..

Re: Introducing ubiboot N9 (multiboot OS loader)

Alright, so, recap, you've just flashed zImage.pr13, and are running it.

Have you heard of a directory called "/etc/aegisfs.d/" and "/etc/ssl/" ?

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Hurrian (Post 1326760)

Alright, so, recap, you've just flashed zImage.pr13, and are running it.

Have you heard of a directory called "/etc/aegisfs.d/" and "/etc/ssl/" ?

No, only /bin/evkey and /sbin/preinit files added with the decompression of sillyboot v2 archive needed for NITdroid.. No /etc/aegisfs.d/ or /etc/ssl/ folders heard so far.. For these reasons I asked if also the installation of the kernel/patched kernel needed for ubiboot multiboot OS have similar issues (maybe the problem was just the patched kernel for NITdroid), nobody else..

Re: Introducing ubiboot N9 (multiboot OS loader)

Alright, so you're in Half-openmode. You probably experience a ****ton of issues, such as bad battery life, and passwords not being saved, etc.

Please refer to these instructions by javispedro to obtain a supported Open Mode configuration.

Re: Introducing ubiboot N9 (multiboot OS loader)

this openmode bug is not some kind of random crashing bug.
this bug related to dpkg installation procedure, when all running tasks are closing after installation ends. it well-known openmode bug and noone know how to solve it. maybe related to some broken reading/writing to CAL area, but i am not sure.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Hurrian (Post 1326768)

Battery and password problem no, only random (or multiple) installation problem. If the above problems are only for Half-Open Mode, I'm happy to this, because without that maybe I'll install the ubiboot :p

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326464)

I have updated the README file to deal with the issue of L2 cache initialization in Harmattan boot.

The fix is to use the provided zImage_2.6.32.54-openmode_l2fix as the harmattan boot kernel. It is a module-compatible drop-in replacement for the vanilla aegis-neutered openmode kernel that has the L2 cache issue fixed. The patch is included as openmode_l2fix.patch

theyosh, please test your harmattan boot using the patched kernel.

Sorry for the late reply, but this kernel keeps my phone rebooting. The pulsing nokia logo is showing earlier, so looks faster. But then I get a message of battery loading and the phone reboots... And that's it... :( Tried three times... no luck.

Re: Introducing ubiboot N9 (multiboot OS loader)

But I still have some issues / questions..

First, in your movie, ubiboot shows after about 10 seconds. Mine takes about 25 seconds... What could cause this?

How can I see what kind of open mode I have? I saw some different versions / methods? How can I check what I have and if it is the right version / way.

For now, at the moment I don't have much time to test. But I will try to do my best and give feedback.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by theyosh (Post 1326896)

Do you have some tweaks/modifications installed? It might still be possible that something is affecting the boot process.

You say that there is "battery loading" message, is your USB/power cable connected during booting? It should not matter but have you tried it without the cable connected?

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by humble (Post 1326731)

try:

Code:

opensh

aegisctl +r

then see if that worked.

i can't try, i don't have opensh

Re: Introducing ubiboot N9 (multiboot OS loader)

I think I have a similar problem:

Code:

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

ubiattach: error!: cannot attach mtd4

error 1 (Operation not permitted)

yes, I'm root, and the first step completed successfully.
Any idea ?

Is my "mount" normal ?

Code:



# mount



rootfs on / type rootfs (rw)

/dev/root on / type ext4 (rw,relatime,errors=remount-ro,barrier=1,stripe=8,data=ordered)

none on /proc type proc (rw,nosuid,nodev,noexec,relatime)

none on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)

tmpfs on /tmp type tmpfs (rw,noatime,size=4096k)

tmpfs on /var/run type tmpfs (rw,nosuid,noatime,size=512k)

none on /dev type tmpfs (rw,noatime,size=10240k,mode=755)

securityfs on /sys/kernel/security type securityfs (rw,relatime)

devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)

tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noatime,size=65536k)

/dev/mmcblk0p3 on /home type ext4 (rw,noatime,errors=remount-ro,barrier=1,stripe=8,data=ordered)

/dev/mmcblk0p1 on /home/user/MyDocs type vfat (rw,nosuid,nodev,noexec,noatime,nodiratime,uid=29999,fmask=0133,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,rodir,errors=remount-ro)

none on /sys/kernel/debug type debugfs (rw,relatime)

aegisfs on /var/run/applauncherd type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.odnp-fpcd/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.odnp/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.facebook/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.mms/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.positioningd/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /var/cache/timed/aegis type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.slpgwd/layer type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /etc/ssl/certs type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

aegisfs on /home/user/.signon/private type fuse.aegisfs (rw,nosuid,nodev,relatime,user_id=30004,group_id=30010,allow_other)

cgroup on /syspart type cgroup (rw,relatime,freezer,memory,cpu)

/dev/mapper/signonfs on /home/user/.signon/signonfs-mnt type ext2 (rw,sync,noexec,relatime,errors=continue)

~ #

Re: Introducing ubiboot N9 (multiboot OS loader)

Can you post what does your "dmesg" say when you fail to attach the device?

Re: Introducing ubiboot N9 (multiboot OS loader)

I think it says nothing but here is the full log in case:

Code:

~ $ dmesg





[ 9.055419] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 9.057220] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 9.085662] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 9.109222] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 9.135742] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode



[ 9.263458] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 9.265136] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 9.273590] ramzswap: num_devices not specified. Using default: 1



[ 9.273620] ramzswap: Creating 1 devices ...



[ 9.294586] ramzswap: Disk size set to 262144 kB



[ 9.302642] Adding 262136k swap on /dev/ramzswap0. Priority:-1 extents:1 across:262136k SS



[ 9.309722] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 9.313507] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 9.845153] omap mailbox rev 4.0



[ 9.848083] DSP Bridge driver loaded



[ 12.576721] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 12.578399] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 12.590820] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 12.849670] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 12.851318] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 12.991546] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 13.811279] atmel_mxt 2-004b: firmware: requesting RM-696_Pyrenees_SMD_ES40_V1_6.bin



[ 14.235290] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 14.239013] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 14.460968] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 18.963623] omap-iommu omap-iommu.0: isp registered



[ 19.034057] omap3isp omap3isp: Revision 15.0 found



[ 19.034118] omap-iommu omap-iommu.0: isp: version 1.1



[ 19.107421] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 19.109283] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 19.121948] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 19.126159] onenand_wait: controller error!state 7 ctrl 0x0400 intr 0x8000



[ 19.126159] onenand_write_ops_nolock: writefailed -5



[ 19.134704] init: bme main process (394) killed by KILL signal



[ 19.135437] init: bme main process ended, respawning



[ 19.211761] smiapp 2-0037: firmware: requesting smiapp-sensor-0c-560f-03.bin



[ 19.339019] smia_reglist_import: meta_reglist version 0.0.51



[ 19.339050] smia_reglist_import: type 10 w 3568 h 2016 fmt 30314442 ival 100/500 pclk 249600000



[ 19.339080] smia_reglist_import: type 10 w 3568 h 2016 fmt 30314142 ival 100/1075 pclk 84000000



[ 19.339080] smia_reglist_import: type 10 w 3568 h 2016 fmt 30314442 ival 100/1500 pclk 249600000



[ 19.339111] smia_reglist_import: type 10 w 3280 h 2464 fmt 30314442 ival 100/1500 pclk 249600000



[ 19.339111] smia_reglist_import: type 10 w 3280 h 2464 fmt 30314142 ival 100/919 pclk 84000000



[ 19.339141] smia_reglist_import: type 10 w 3280 h 2464 fmt 30314442 ival 100/500 pclk 249600000



[ 19.339141] smia_reglist_import: type 10 w 3144 h 1772 fmt 30314442 ival 100/1409 pclk 128000000



[ 19.339141] smia_reglist_import: type 10 w 2728 h 2048 fmt 30314442 ival 100/1345 pclk 128000000



[ 19.339172] smia_reglist_import: type 10 w 1776 h 1008 fmt 30314142 ival 100/1000 pclk 79680000



[ 19.339172] smia_reglist_import: type 10 w 1776 h 1008 fmt 30314142 ival 100/2399 pclk 79680000



[ 19.339202] smia_reglist_import: type 10 w 1776 h 1008 fmt 30314142 ival 100/2999 pclk 79680000



[ 19.339202] smia_reglist_import: type 10 w 1632 h 1232 fmt 30314142 ival 100/1000 pclk 79680000



[ 19.339233] smia_reglist_import: type 10 w 1632 h 1232 fmt 30314142 ival 100/2999 pclk 79680000



[ 19.339233] smia_reglist_import: type 10 w 816 h 608 fmt 30314142 ival 100/1500 pclk 88533333



[ 19.339233] smia_reglist_import: type 10 w 816 h 608 fmt 30314142 ival 100/2967 pclk 88533333



[ 19.339263] smia_reglist_import: type 1 w 0 h 0 fmt 30314142 ival 1/0 pclk 0



[ 19.339263] smia_reglist_import: type 0 w 0 h 0 fmt 30314142 ival 1/0 pclk 0



[ 19.378143] ad58xx 2-000e: ad5817 2-000e (2-3) version 3 found.



[ 19.454010] smiapp 2-0010: firmware: requesting smia-sensor-0c-2134-02.bin



[ 19.523040] smia_reglist_import: meta_reglist version 0.0.51



[ 19.523071] smia_reglist_import: type 10 w 576 h 472 fmt 30314142 ival 100/2743 pclk 13770000



[ 19.523071] smia_reglist_import: type 10 w 576 h 472 fmt 30314142 ival 100/1501 pclk 13770000



[ 19.523071] smia_reglist_import: type 10 w 576 h 432 fmt 30314142 ival 100/2743 pclk 13770000



[ 19.523101] smia_reglist_import: type 10 w 576 h 432 fmt 30314142 ival 100/1501 pclk 13770000



[ 19.523101] smia_reglist_import: type 1 w 0 h 0 fmt 30314142 ival 1/0 pclk 0



[ 19.523132] smia_reglist_import: type 0 w 0 h 0 fmt 30314142 ival 1/0 pclk 0



[ 21.111358] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 21.117767] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 21.242370] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 21.319305] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 21.321533] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 21.388824] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 21.432495] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.050720] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.052398] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 25.113769] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.194152] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.210205] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 25.347991] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.460388] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.462127] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 25.668334] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.765533] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.778594] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 25.951721] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 25.983489] onenand_wait: controller error!state 7 ctrl 0x0400 intr 0x8000



[ 25.983520] onenand_write_ops_nolock: writefailed -5



[ 27.819244] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com



[ 32.970336] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 32.972106] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 32.972320] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x64



[ 33.115844] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 33.155426] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 33.157104] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 33.274475] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 34.307556] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 34.309265] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 34.325439] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 34.344451] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 34.349670] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58



[ 34.349914] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x64



[ 34.380523] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0



[ 34.433532] Netfilter messages via NETLINK v0.30.



[ 35.858581] EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended



[ 45.953247] hci_h4p hci_h4p: firmware: requesting ti1273_le.bin

[ 50.540069] wl1271_sdio mmc1:0001:2: firmware: requesting wl1271-fw.bin

[ 52.177764] init: xsession/active-syncd main process (1279) terminated with status 5

[ 53.189880] wl1271: firmware booted (Rev 6.1.1.39.339)

[ 57.638732] wl1271: down

[ 57.737030] cfg80211: Calling CRDA for country: GB

[ 57.739379] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

[ 57.741088] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58

[ 57.770019] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

[ 57.785644] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

[ 57.786743] cfg80211: Regulatory domain changed to country: GB

[ 57.786743] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

[ 57.786773] (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm)

[ 57.786773] (5170000 KHz - 5250000 KHz @ 40000 KHz), (N/A, 2000 mBm)

[ 57.786773] (5250000 KHz - 5330000 KHz @ 40000 KHz), (N/A, 2000 mBm)

[ 57.786804] (5490000 KHz - 5710000 KHz @ 40000 KHz), (N/A, 2700 mBm)

[ 57.795227] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58

[ 57.818664] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

[ 58.539794] pvr: MProgressIndica: cleaning up 146 unfreed resources

[ 58.561340] init: boot-watchdog main process (457) killed by TERM signal

[ 60.184020] wl1271: firmware booted (Rev 6.1.1.39.339)

[ 60.307220] wlan0: authenticate with 00:8e:f2:6f:f9:24 (try 1)

[ 60.313934] wlan0: authenticated

[ 60.323394] wlan0: associate with 00:8e:f2:6f:f9:24 (try 1)

[ 60.342590] wlan0: RX AssocResp from 00:8e:f2:6f:f9:24 (capab=0x11 status=0 aid=4)

[ 60.342590] wlan0: associated

[ 60.486785] wl1271: Association completed.

[ 66.407043] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

[ 66.413574] onenand_wait: correctable ECC error = 0x5555, addr1 0x4, addr8 0x58

[ 66.434936] onenand_wait: correctable ECC error = 0x5555, addr1 0xa, addr8 0x0

[ 92.448730] ip_tables: (C) 2000-2006 Netfilter Core Team

[ 103.568511] Aegis: cannot measure file orcexec.ZQ60Nd (process: camera-ui)

[ 103.569000] Aegis: cannot measure file orcexec.62SIwh (process: camera-ui)

[ 103.569183] Aegis: cannot measure file orcexec.tBObfl (process: camera-ui)



~ $

Thanks for the help :)

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by Mric (Post 1326940)

I think it says nothing but here is the full log in case:
Thanks for the help :)

To me it looks like your device has not initialized ubifs layer at all. (altough it seems the whole log is not included, or it has overflown at some point...)
What is the kernel that you are running?

What you could do, before trying to install flash the zImage_2.6.32.54-openmode_l2fix kernel as your normal boot kernel, and then try the attach and mount commands again.

So, do:

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

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by thedead1440 (Post 1326775)

coderus,

No! You probably haven't removed the aegisfs mounts and the certs too; read Hurrian's post above to learn about it. You can verify by typing df in terminal and you'll see the aegisfs mounts; if you have removed it you should have something like the following:

yes i removed aegisfs mounts. and every time i install app from store (for example) all running applications are closed.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by theyosh (Post 1326896)

There is one thing I thought about last night.

When ubiboot runs Harmattan with the 2nd stage kernel, it will be initialized with "/sbin/preinit_harmattan" file, which is a streamlined version of the original "/sbin/preinit"

Now this works well in my device, but it might be that I have misplaced something in the preinit file so that it will cause problems on other devices.

What you could do, is try copying the original preinit file as the active preinit file: "cp /sbin/preinit /sbin/preinit_harmattan" as root.
Then try to boot with ubifs again.

Re: Introducing ubiboot N9 (multiboot OS loader)

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, edited boot.conf accordingly, but no joy. Recovery mode with usbplug attached worked fine.

I seemingly went through all the steps outlined in the README. Except i haven't dealed with kernel modules, i guess these kernels are compatible with stock modules?

Gonna try again if more streamlined info becomes available. I'm glad i could easily flash it back to nitdroid kernel.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1326968)

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

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by veeall (Post 1327030)

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.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by theyosh (Post 1327034)

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" ?

Re: Introducing ubiboot N9 (multiboot OS loader)

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

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by byteninja2 (Post 1327103)

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

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1327190)

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 :)

Re: Introducing ubiboot N9 (multiboot OS loader)

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.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by byteninja2 (Post 1327577)

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...)

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1327041)

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

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by theyosh (Post 1327649)

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?

Re: Introducing ubiboot N9 (multiboot OS loader)

Okay, i flashed the zimage, and now i got farther into the steps, but now i get this: umount: can't umount /mnt: Invalid argument