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

Also, I just got near a computer, so when I get some time maybe today, I'll patch the CONFIG_CMDLINE_OVERRIDE option to my sources and recompile it (and modules) for you.

So, here you are :)

This archive has the modules and the kernel to be flashed like a regular kernel to boot SailfishOS directly from mmcblk0p4 (No uboboot required for this now...)
http://www.swagman.org/juice/SFOS_boot_for_p4.tar

Before using, untar the modules under /lib/modules/2.6.32.54 of your sailfish partition.
Then, flash the kernel with "sudo flasher -a firmware.bin -k zImage_2.6.32-54_boot4 --flash-only=kernel -f -R"

Have fun :D

Hi.
I can't wait to test it!
I think I'll get back home early tomorrow just to try it. Hopefully the only problem left will be to repartition to use the whole 16GB of disk space.
Thank you again and I'll report as soon as I test it.
Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1421894)

No problem :)

If you get that working, it's no big deal to now make a kernel that boots SFOS from any partition you'd like, as I have the patched kernel tree done. You can partition your device however you like, for example everything as one partition :D

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.
Unfortunately this didn't work either... :confused: I tried with&without RR mode enabled.
I think I'll 'take a look' inside. I'll buy a pair of screwdrivers to see if something is wrong....
I'll keep you informed.

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1422058)

Hmm, how did it work, did you see anything on the device when you flashed & booted it?
Did it just hang, or did it reboot?

If you have your SaifishOS FS image correctly extracted to your mmcblk0p4 and if you correctly untarred the kernel modules also there, it sure has to work.

In fact I cannot see how it is possible for it not to work.
If you can boot with ubiboot, then there is absolutely no way why you should not boot with SailfishOS. It just has to work.

Now, I have to believe you have something wrong with your Sailfish installation, there is nothing else that can go wrong now, sorry.

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.

All I can say is that it just hungs up. I have to press the power button for 8 seconds to reboot it.
I think I'll start from scratch and also tear it apart ....

Thank you for your patience.

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

It works fine. Thank you!

Quote:

Originally Posted by juiceme (Post 1421865)

Re: Introducing ubiboot N9 (multiboot OS loader)

https://db.tt/IA08mHNr
You can download the file from this URL.

Quote:

Originally Posted by imyaman (Post 1422135)

It works fine. Thank you!

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.

O.K, I'm back :)
After giving up for one day, I decided today to try and install nitdroid, following Coderus instructions from almost 2 years ago..... and it worked.
This is allowing me to check that WiFi, audio, tactile screen, charging, etc. are working fine.
I think I'll tinker a bit more with it (I don't like Android , that's why I'm in this forum ;) ) ,and try to install Sailfish again later.
I'll keep you updated of my progress.

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1422462)

It's good you managed to install something, at least. :)
Did you set Nitdroid up with ubiboot or sillyboot?
(why I am asking, is because if you used ubiboot then you should be able to boot Sailfish also with it...)

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.

Well, I did it with sillyboot. I've seen it has two files, and one of them is a binary file so that I'll take a look at the preinit file to see if I can find out something.

Indeed, I untarred the sailfish image in the same place as the nitdroid to see if if worked, but it didn't.....

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1422476)

Well, sillyboot and ubiboot are pretty much 2 different kinds of beasts, not to be confused to eachother :D
(not even very close relatives...)

sillyboot is just a modification of the Harmattan preinit environment; it uses the one and only kernel flashed to mtd2 and acts on the system initialixation level: Before the preinit calls /sbin/init the control is transferred to chrooted android initialization.
What this means, is that if you want to use both Harmattan and Nitdroid, you must have a specially crafted kernel that can run both OS'es.
There are 2 variants of sillyboot, one, the original has the evkey interface where selection is by volume keys, and the other has the evtap interface with touchscreen control.
With sillyboot you cannot boot any "true" OS that has not been heavily modified to be able to run under chroot and with the default kernel. That means, no Sailfish there, ever.
ubiboot on the other hand is a true boot loader; it has it's own kernel and root file system with a ton of extra niceties added. With ubiboot you can boot pretty much anything that comes to your mind. (mostly Linux, yes, but with some tweaks it would be possible to load also BSD, Darwin, maybe even WinCE to your N9 :p)
You get total control on what arguments to give to the 2nd-level kernel, so it is easy to start any kind of OS you desire on it

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.

Provided that I'm stuck.... I was wondering:

What if I rewrite all the /dev/mtd* of the broken device with fresh data from my working device?.
I can't stop thinking there must be something root with those partitions. The flasher even tells me that going from
40.2012.21-3.454.6 (Vietnam with preinstalled apps)to 40.2012.21-3.480.1 (Switzerland country variant) is a downgrade!

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1422646)

Well, at first, it probably does not help, but rather it will make your device unusable. it is possible you will not be able to boot anything on it, and not flash it any longer.

Second, it is almost impossible to do; to be able to have write access to some of those areas you need to be in Closed Mode as they are locked in Open Mode. However, in Closed Mode you cannot do it as Aegis will block you for lack of credentials.
(You might be able to break something permanently with Inception, though, if you really tried....)

I still think the best option is to use ubiboot, you should be able to boot Sailfish that way, there has to be something wrong with your SailfishOS installation.

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.

Sure, there has to be something wrong. However, I tried all the Sailfish images recommended in the Maemo Wiki, and I'm always using the specific Ubiboot version ONLY for Sailfish. I can almost do all the processes with my eyes closed, Ubiboot starts fine, etc. but the next step nothing happens......

What the heck!. I'll give it another try this weekend, the device is not working already!

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1422725)

And with the SailfishOS-flashable boot-from-mmcblk0p4-kernel I made, same thing with that too...?

Now there does exist some things you could do, I presume you have not yet tried to boot the device with serial console connected, that'd give you the clue why it is borking...?

---------- edit ----------

See the pinout of N9 serial connector here:
http://talk.maemo.org/showpost.php?p...2&postcount=93

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.
Do you mean I can watch the boot messages in the screen of the device, or should I connect a serial console to the SIM slot ?
About the specially krafted kernel, just the same...
Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1422750)

Hi.
Do you mean I can watch the boot messages in the screen of the device, or should I connect a serial console to the SIM slot ?
About the specially krafted kernel, just the same...
Regards.

I did not manage to get a good update for the screen, the messages written there do not come out nicely/reliably. Something to do with the framebuffer device needing regular refresh for displaying text.

You need to connect a rs232-levelshigter/USB adapter to the simslot pins, to just watch the messages it is enough to connect to the TxD and GND pins which are nearest to the edge.
It is fairly easy just to hold a 2-pin connector pingead there by hand, not needing an adapter even if you just want a quick look what happens there.

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.
I ordered one of these level changers to see the console boot messages. In the meantime I flashed nitdroid ...
I`ll post again when I get the logs.
Thank you.
Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi

Can some one explain me how to copy paste the X-terminal output from nokia N900/N9 in the forum. Observed couple of codes are written in square box in many posts and reply's.

Also how to display or project the N900/N9 terminal in to the PC screen. Please help me. This thread is most active one.. so posted here. sorry for inconvinence.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by kumardodla (Post 1423008)

Hi.

Also how to display or project the N900/N9 terminal in to the PC screen. Please help me. This thread is most active one.. so posted here. sorry for inconvinence.

Go Here
http://everythingn9.com/how-to-use-p...-the-nokia-n9/

Re: Introducing ubiboot N9 (multiboot OS loader)

the first one is quite easy! just copy stuff from the terminal to the forum post page and wrap around the CODE tags...

second on you can achieve by using ssh to connect to your N9
look here

Re: Introducing ubiboot N9 (multiboot OS loader)

hi @juiceme bro
i want to install latest kernel [linux_2.6.32.61-plus-20131128.tar] with ubiboot. need some help

1.''add the kernel filename to ubiboot.conf''

now should i replace 'zImage_2.6.32.54-openmode_l2fix'
with 'zImage_2.6.32.61-plus_20131128' in ubiboot.conf file?

2.''Gone are the days of flashing kernels!''
original kernel+ this one ?

asking bcoz in kernel thread it is explained for advanced users.

Just add a new line with label and path to kernel and you are done

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by arifkhan123 (Post 1423055)

On your Harmattan section of ubiboot.conf, you have 6 slots available for your kernels.
You can put the new kernel you want to on any of the lines.

Remember that you have the setting "G_OS2_NUM=..." also there, that tells ubiboot how many lines to show on the device screen.

Quote:

Originally Posted by arifkhan123 (Post 1423055)

2.''Gone are the days of flashing kernels!''
original kernel+ this one ?

asking bcoz in kernel thread it is explained for advanced users.

Yes, if you want to have for example just the original kernel and the new kernel plus, your config could maybe look something like this:

# The second OS is usually Harmattan.
# This section lists the Harmattan specific switches and kernels
G_OS2_NUM=2
G_OS2_AUTOBOOT=0
G_OS2_PARTITION=2
G_OS2_NAME="Harmattan"
G_OS2_1_LABEL="my original kernel"
G_OS2_1_FILE="/boot/Harmattan/boot/2.6.32.54-dfl61-20121301"
G_OS2_2_LABEL="2.6.32.61 kernel +"
G_OS2_2_FILE="/boot/Harmattan/boot/zImage_2.6.32.61-plus-20131114"
G_OS2_3_LABEL=""
G_OS2_3_FILE=""
G_OS2_4_LABEL=""
G_OS2_4_FILE=""
G_OS2_5_LABEL=""
G_OS2_5_FILE=""
G_OS2_6_LABEL=""
G_OS2_6_FILE=""

And again, of course remember to set up the modules before booting, or else you will fail to boot the new kernel (but of course this will not affect your old kernel, you can always boot with that if you fail to boot the new one...)

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1422754)

Hi.
I received the rs232 adapter. I'v been able to partially get the bootlog messages from the serial console. There's an error message trying to write nand :confused: and something about CAL...
Can anyone decypher what this messages mean?. Do I have a hardware problem?

Here's the bootlog, keep in mind it is partial (it is not easy to keep the cables connected to the pins inside the SIM tray. :)

Code:

preinit: /var is still in rootfs. No changes

preinit: R&D mode enabled with flags: serial-console

preinit: Bootmode = 'normal', Bootreason = 'pwr_key'

preinit: Press any key for interactive startup

Mounting a tmpfs over /dev...done.

done.

aegis start/running

udev start/running, process 194

[    7.428649] hci_h4p hci_h4p: Registering HCI H4P device

[    7.435272] CMT driver

[    7.439880] input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input4

[    7.448181] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input5

[    7.546997] twl5031_aci twl5031_aci: found twl5031 ACI v.16

[    7.621826] lp5521 2-0032: lp5521 programmable led chip found

[    7.624816] Registered led device: lp5521:channel0

[    7.914093] OMAP SSI hw driver loaded

[    7.916534] input: SPI vibrator as /devices/platform/omap2_mcspi.2/input/input6

[    7.920532] wl1273_fm_module_init

[    7.926757] Loading BCM4751 GPS driver

[    7.941162] SGX clock rate 195 MHz

[    8.111785] lis3lv02d: 8 bits sensor found

[    8.166564] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input7

[    8.360168] NET: Registered protocol family 35

[    8.366912] HSI/SSI char device loaded

[    8.373565] SSI protocol aka McSAAB added

[    8.415466] ssi_protocol ssi_protocol: WAKELINES TEST OK

[    8.428588] wl1271: loaded

[    8.428680] wl1271: initialized

[    8.436798] netlink: 5 bytes leftover after parsing attributes.

udevtrigger stop/waiting

aegis-session start/running

Current time settings:

 Real time clock (UTC) : Tue May 13 21:35:24 2014  0.000000 seconds

 System time (UTC)     : Tue May 13 21:35:24 UTC 2014

 Current time zone     : N/A (using )

 Local time            : Tue May 13 21:35:24 UTC 2014

timeconfig start/running

rc-default: bootstate USER, going for runlevel 2

rc-default start/running

runlevel event: switching to 2

run-parts: /etc/network/if-post-up.d: No such file or directory

Starting dbus

dsme start/running, process 393

Entering state 'USER'.

klogd stop/waiting

DSME 0.63.0 starting up

syslogd stop/pre-start, process 414

syslogd stop/pre-start, process 414

new state: USER

Restoring alarm queue head failed

ttyS0 start/running, process 428

Got D-Bus dir inotify watch event

dbus start/running, process 387

[    9.696319] mmc_queue_do_make_request process sfdisk (pid 441), read to sector 0, sectors 8

                end: (c,h,s) expected (1023,3,16) found (1023,63,32)

                start: (c,h,s) expected (1023,3,16) found (1023,63,32)

                end: (c,h,s) expected (1023,3,16) found (1023,63,32)



MeeGo 1.2 Harmattan (none) /dev/ttyS0



(none) login: /sbin/tune2fs

Home filesystem state ok

product = RM-696

[    9.850585] EXT4-fs (mmcblk0p3): recovery complete

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

sysconfig-middle start/running

gconfd start/running, process 478

no-bme start/running, process 482

[   10.158111] g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008

[   10.161071] g_file_storage gadget: Number of LUNs=1 Number of buffers=16

select-usb-module start/running

/sbin/waitfordsme (pid 488): Wait for DSME socket...

/sbin/waitfordsme: OK: send to DSME socket succeeded

mount-home start/running

tracker-init stop/waiting

rich-core-pattern start/running

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

[   45.327697] onenand_write_ops_nolock: write failed -5

CAL ERROR: nand_write: write (4096 bytes at around 001e0000): Input/output error

poweron-timer: cal write failed

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.

I finally got a complete sequence (ubiboot + Harmattan). The problem mentioned before no longer appears, but the device is stuck in the last message... :confused:

I think I need to sleep ;)

EDIT: I had to remove the ubibbot part because the post was too long. I'll try to repeat the process tomorrow.
Regards.

Code:

[   19.917358] Starting new kernel

[   19.917449] Bye!

Uncompressing Linux... done, booting the kernel.

[    0.000000] Initializing cgroup subsys cpu

[    0.000000] Linux version 2.6.32.54-dfl61-20121301 (juice@alaspin) (gcc version 4.4.1 ('cs2009q3-hard-67-sb16') ) #1 PREEMPT Sat Mar 2 3

[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f

[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

[    0.000000] Machine: Nokia RM-696 board

[    0.000000] Reserving 14680064 bytes SDRAM for VRAM

[    0.000000] Memory policy: ECC disabled, Data cache writeback

[    0.000000] OMAP3630 ES1.2-hs (l2cache iva sgx neon isp 192mhz_clk )

[    0.000000] SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000

[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 254976

[    0.000000] Kernel command line: init=/sbin/preinit_harmattan root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 8

[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)

[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

[    0.000000] allocated 5242880 bytes of page_cgroup

[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups

[    0.000000] Memory: 1002MB 2MB = 1004MB total

[    0.000000] Memory: 1008256KB available (4652K code, 464K data, 152K init, 0K highmem)

[    0.000000] SLUB: Genslabs=9, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[    0.000000] Hierarchical RCU implementation.

[    0.000000] NR_IRQS:402

[    0.000000] Clocking rate (Crystal/Core/MPU): 38.4/390/600 MHz

[    0.000000] Reprogramming SDRC clock to 390400000 Hz

[    0.000000] GPMC revision 5.0

[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts

[    0.000000] Total of 96 interrupts on 1 active controller

[    0.000000] OMAP GPIO hardware version 2.5

[    0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz

[    0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms

[    0.000000] Console: colour dummy device 80x30

[    0.000122] Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720)

[    0.039184] Security Framework initialized

[    0.039215] Aegis: init vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a

[    0.039337] Mount-cache hash table entries: 512

[    0.039703] Initializing cgroup subsys memory

[    0.039733] Initializing cgroup subsys freezer

[    0.039794] CPU: Testing write buffer coherency: ok

[    0.040283] devtmpfs: initialized

[    0.044616] regulator: core version 0.5

[    0.044799] NET: Registered protocol family 16

[    0.045562] RM-696 board, rev 1507

[    0.046539] MUX: setup H16_34XX_SDRC_CKE0 (0xfa002262): 0x0100 -> 0x0000

[    0.046569] MUX: setup H17_34XX_SDRC_CKE1 (0xfa002264): 0x0100 -> 0x0000

[    0.046569] SmartReflex class 1.5 driver: initialized

[    0.049438] OMAP DMA hardware revision 5.0

[    0.049499] Reserving DMA channels 0 and 1 for HS ROM code

[    0.052337] bio: create slab <bio-0> at 0

[    0.052825] regulator: VSDIO: 1800 mV normal standby

[    0.052947] regulator: vbat: 3700 mV 

[    0.053039] regulator: VEMMC: 2900 mV normal standby

[    0.054321] i2c_omap i2c_omap.1: bus 1 rev4.0 at 2900 kHz

[    0.069305] twl4030: PIH (irq 7) chaining IRQs 368..375

[    0.069335] twl4030: power (irq 373) chaining IRQs 376..383

[    0.069763] twl4030: gpio (irq 368) chaining IRQs 384..401

[    0.070587] regulator: VUSB1V5: 1500 mV normal standby

[    0.070770] regulator: VUSB1V8: 1800 mV normal standby

[    0.070953] regulator: VUSB3V1: 3100 mV normal standby

[    0.072113] twl4030_usb twl4030_usb: Initialized TWL4030 USB module

[    0.072875] regulator: VPLL1: 1800 mV normal standby

[    0.074249] regulator: VIO: 1800 mV normal standby

[    0.074462] regulator: VMMC1: 1850 <--> 3150 mV normal standby

[    0.074737] regulator: VDAC: 1800 mV normal standby

[    0.075012] regulator: VAUX2: 1800 mV normal standby

[    0.075469] regulator: VINTANA1: 1500 mV normal standby

[    0.075927] regulator: VINTANA2: 2750 mV normal standby

[    0.076385] regulator: VINTDIG: 1500 mV normal standby

[    0.076660] regulator: VPLL2: 1800 mV normal standby

[    0.076934] regulator: VMMC2: 3000 mV normal standby

[    0.077209] regulator: VSIM: 1800 mV normal standby

[    0.077514] regulator: VAUX1: 2800 mV normal standby

[    0.077789] regulator: VAUX3: 2800 mV normal standby

[    0.078094] regulator: VAUX4: 2800 mV normal standby

[    0.078491] i2c_omap i2c_omap.2: bus 2 rev4.0 at 400 kHz

[    0.086059] i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz

[    0.087310] Bluetooth: Core ver 2.15

[    0.087432] NET: Registered protocol family 31

[    0.087463] Bluetooth: HCI device and connection manager initialized

[    0.087463] Bluetooth: HCI socket layer initialized

[    0.087738] cfg80211: Calling CRDA to update world regulatory domain

[    0.087890] Switching to clocksource 32k_counter

[    0.088684] musb_hdrc: version 6.0, musb-dma, peripheral, debug=0

[    0.088897] musb_hdrc: USB Peripheral mode controller at fa0ab000 using DMA, IRQ 92

[    0.089294] NET: Registered protocol family 2

[    0.089416] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)

[    0.089782] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)

[    0.093109] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)

[    0.094512] TCP: Hash tables configured (established 131072 bind 65536)

[    0.094512] TCP reno registered

[    0.094665] NET: Registered protocol family 1

[    0.095184] dspbridge_init: 600000 bytes @ bea00000

[    0.095275] hs_init: omap_hs driver

[    0.096038] sec_init: omap_sec driver

[    0.105377] fuse init (API version 7.13)

[    0.105834] msgmni has been set to 1969

[    0.106079] Aegis: Netlink socket created

[    0.106109] restok: ready

[    0.106140] creds: ready

[    0.106140] credp: active

[    0.108795] io scheduler noop registered

[    0.108795] io scheduler anticipatory registered

[    0.108795] io scheduler deadline registered

[    0.109069] io scheduler cfq registered (default)

[    0.109558] OMAP DSS rev 2.0

[    0.109649] OMAP DISPC rev 3.0

[    0.109680] OMAP VENC rev 2

[    0.109863] OMAP DSI rev 1.0

[    0.118225] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled

[    0.119323] serial8250.2: ttyS0 at MMIO 0x49020000 (irq = 74) is a TI16750

[    0.740783] console [ttyS0] enabled

[    0.749420] brd: module loaded

[    0.752197] loop: module loaded

[    0.753723] OneNAND driver initializing

[    0.754455] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base f0040000, freq 83 MHz

[    0.765289] Muxed OneNAND 512MB 1.8V 16-bit (0x50)

[    0.769866] OneNAND version = 0x0232

[    0.773437] 6 cmdlinepart partitions found on MTD device omap2-onenand

[    0.779937] Creating 6 MTD partitions on "omap2-onenand":

[    0.785339] 0x000000000000-0x000000100000 : "bootloader"

[    0.790954] 0x000000100000-0x0000003c0000 : "config"

[    0.795867] 0x0000003c0000-0x0000013c0000 : "kernel"

[    0.800842] 0x0000013c0000-0x0000015c0000 : "log"

[    0.808654] mtdoops: Attached to MTD device 3

[    0.809661] 0x0000015c0000-0x00001e000000 : "var"

[    0.814666] 0x00001e000000-0x000020000000 : "moslo"

[    0.820007] tun: Universal TUN/TAP device driver, 1.6

[    0.824340] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>

[    0.846405] input: ECI Accessory as /devices/virtual/input/input0

[    0.847442] twl4030_rtc twl4030_rtc: rtc core: registered twl4030_rtc as rtc0

[    0.854705] i2c /dev entries driver

[    0.858093] Linux media interface: v0.10

[    0.861663] Linux video capture interface: v2.00

[    0.867523] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec

[    0.873016] HACK: TWL5031 WDT can't be disabled. Automatic WDT refresh started

[    0.879516] cpuidle: using governor ladder

[    0.883514] cpuidle: using governor menu

[    0.888793] omap_sham_mod_init: loading omap-sham driver

[    0.892883] omap-sham omap-sham: hw accel on OMAP rev 0.9

[    0.899444] Advanced Linux Sound Architecture Driver Version 1.0.21.

[    0.931671] input: Atmel mXT Touchscreen as /devices/platform/i2c_omap.2/i2c-2/2-004b/input/input1

[    0.935363] atmel_mxt: Atmel mXT Touchscreen v1.6 (0x29b82f) var:0x1 bld:0xab

[    0.944702] tpa6130a2 2-0060: UNTESTED version detected (3)

[    0.948028] No device for DAI omap-mcbsp-dai-0

[    0.952301] No device for DAI omap-mcbsp-dai-1

[    0.956787] No device for DAI omap-mcbsp-dai-2

[    0.961181] No device for DAI omap-mcbsp-dai-3

[    0.965667] No device for DAI omap-mcbsp-dai-4

[    0.970184] mmc0: hardware reset done

[    1.030883] asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok

[    1.033569] input: dfl61-twl4030 Jack as /devices/platform/soc-audio.0/sound/card0/input2

[    1.040039] DFL61 TWL SoC init done (config 4)

[    1.044067] asoc: tlv320dac33 <-> omap-mcbsp-dai-1 mapping ok

[    1.049987] ALSA device list:

[    1.052093]   #0: dfl61-twl4030 (twl4030)

[    1.056091]   #1: dfl61-dac33 (tlv320dac33)

[    1.060852] misc iphb: Module registered in 2.6.32.54-dfl61-20121301, built Mar  2 2013 23:06:19

[    1.069183] TCP cubic registered

[    1.072326] NET: Registered protocol family 17

[    1.076812] NET: Registered protocol family 15

[    1.081268] Bluetooth: L2CAP ver 2.14

[    1.084869] Bluetooth: L2CAP socket layer initialized

[    1.089965] Bluetooth: SCO (Voice Link) ver 0.6

[    1.094451] Bluetooth: SCO socket layer initialized

[    1.099578] Bluetooth: RFCOMM TTY layer initialized

[    1.104278] Bluetooth: RFCOMM socket layer initialized

[    1.109375] Bluetooth: RFCOMM ver 1.11

[    1.113189] Power Management for TI OMAP3.

[    1.118499] SmartReflex device[1] initialized

[    1.121704] SmartReflex device[2] initialized

[    1.126800] input: gpio-keys as /devices/platform/gpio-keys/input/input3

[    1.137573] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3

[    1.156402] panel-nokia-dsi display0: skipping HW reset

[    1.183227] panel-nokia-dsi display0: pyrenees panel revision fe.91.96

[    1.185150] regulator_init_complete: incomplete constraints, leaving rm696_vmmc1 on

[    1.193481] asoc: WL1273 BT/FM codec <-> omap-mcbsp-dai-2 mapping ok

[    1.199432] Waiting for root device /dev/mmcblk0p2...

[    1.502929] mmc0: new high speed MMC card at address 0001

[    1.503631] mmcblk0: mmc0:0001 HYNIX  14.8 GiB 

[    1.507720]  mmcblk0:mmc_queue_do_make_request process kmmcd (pid 15), read to sector 0, sectors 8

[    1.518096]  p1 p2 p3 p4

[    1.538757] EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended

[    1.568725] EXT4-fs (mmcblk0p2): recovery complete

[    1.568847] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode

[    1.574890] VFS: Mounted root (ext4 filesystem) on device 179:2.

[    1.580963] Freeing init memory: 152K

[    1.585968] mmc1: card claims to support voltages below the defined range. These will be ignored.

[    1.612152] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)

[    1.613220] mmc1: new SDIO card at address 0001

[    1.635223] Aegis: Invoking userspace helper

[    1.729553] Aegis: vhash code matched to validator-init

[    3.351409] Aegis: Creating new mount point hashlist edc50000

validator-init: done (0,0x0,0x1c7,0x7)[    3.421447] Aegis: enabled (config data protection)

[    3.421844] Aegis: hashlist initialized preinit_harmattan



preinit: Root filesystem state ok

[    5.321594] omap_device: smartreflex.0: new worst case activate latency 0: 30517

preinit: /var is still in rootfs. No changes

[    5.338195] omap_device: smartreflex.1: new worst case deactivate latency 0: 30517

[    5.392791] omap_device: smartreflex.0: new worst case activate latency 0: 61035

preinit: R&D mode enabled with flags: serial-console

preinit: Bootmode = 'normal', Bootreason = 'pwr_key'

preinit: Press any key for interactive startup

Mounting a tmpfs over /dev...done.

done.

aegis start/running

udev start/running, process 194

[    7.311187] hci_h4p hci_h4p: Registering HCI H4P device

[    7.345245] input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input4

[    7.377716] CMT driver

[    7.385742] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input5

[    7.460968] twl5031_aci twl5031_aci: found twl5031 ACI v.16

[    7.627777] wl1273_fm_module_init

[    7.629425] Loading BCM4751 GPS driver

[    7.744720] input: SPI vibrator as /devices/platform/omap2_mcspi.2/input/input6

[    7.760162] lis3lv02d: 8 bits sensor found

[    7.815002] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input7

[    7.979125] OMAP SSI hw driver loaded

[    7.984558] SGX clock rate 195 MHz

[    8.401885] NET: Registered protocol family 35

[    8.405761] HSI/SSI char device loaded

[    8.415618] SSI protocol aka McSAAB added

[    8.461151] ssi_protocol ssi_protocol: WAKELINES TEST OK

[    8.481292] wl1271: loaded

[    8.481384] wl1271: initialized

[    8.486663] netlink: 5 bytes leftover after parsing attributes.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1425224)

Hi.

I finally got a complete sequence (ubiboot + Harmattan). The problem mentioned before no longer appears, but the device is stuck in the last message... :confused:

I think I need to sleep ;)

Thanks, your log looks pretty good which means you have a steady hand if you took it by holding connector pins to the pads under the simtray :)

Now, it is odd if your kernel output stops just like that, so that there's no panic message.

It should continue with something like this, like the green part in the log below. (taken from one of my devices)

aegis start/running
udev start/running, process 194
[ 6.530670] hci_h4p hci_h4p: Registering HCI H4P device
[ 6.534698] CMT driver
[ 6.538116] input: TWL4030 Keypad as /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input4
[ 6.579986] input: twl4030_pwrbutton as /devices/platform/i2c_omap.1/i2c-1/1-0049/twl4030_pwrbutton/input/input5
[ 6.659973] twl5031_aci twl5031_aci: found twl5031 ACI v.16
[ 6.716339] wl1273_fm_module_init
[ 6.719512] Loading BCM4751 GPS driver
[ 6.864105] OMAP SSI hw driver loaded
[ 6.901611] input: SPI vibrator as /devices/platform/omap2_mcspi.2/input/input6
[ 6.986755] lis3lv02d: 8 bits sensor found
[ 6.989257] SGX clock rate 195 MHz
[ 7.041595] input: ST LIS3LV02DL Accelerometer as /devices/platform/lis3lv02d/input/input7
[ 7.158721] HSI/SSI char device loaded
[ 7.164184] NET: Registered protocol family 35
[ 7.170104] SSI protocol aka McSAAB added
[ 7.188232] wl1271: loaded
[ 7.188293] wl1271: initialized
[ 7.211242] ssi_protocol ssi_protocol: WAKELINES TEST OK
[ 7.220916] netlink: 5 bytes leftover after parsing attributes.
[ 7.666229] i2c_omap i2c_omap.2: controller timed out
[ 7.709289] lp5521 2-0032: lp5521 programmable led chip found
[ 7.711883] Registered led device: lp5521:channel0
udevtrigger stop/waiting
aegis-session start/running
Current time settings:
Real time clock (UTC) : Fri May 24 11:16:25 2013 0.000000 seconds
System time (UTC) : Fri May 24 11:16:25 UTC 2013
Current time zone : /usr/share/zoneinfo/Europe/Helsinki
Local time : Fri May 24 14:16:25 EEST 2013
timeconfig start/running
rc-default: bootstate USER, going for runlevel 2
rc-default start/running
runlevel event: switching to 2
Starting dbus
run-parts: /etc/network/if-post-up.d: No such file or directory
dsme start/running, process 402
Entering state 'USER'.
klogd start/running, process 414
DSME 0.63.0 starting up
syslogd start/running, process 435
kernel.dmesg_restrict = 0
ttyS0 start/running, process 444
new state: USER
[ 8.486419] g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008
[ 8.493041] g_file_storage gadget: Number of LUNs=1 Number of buffers=16
select-usb-module start/running
/sbin/waitfordsme (pid 452): Wait for DSME socket...
Got D-Bus dir inotify watch event
dbus start/running, process 393
/sbin/waitfordsme: OK: send to DSME socket succeeded[ 8.543395] mmc_queue_do_make_request process sfdisk (pid 453), read to sector 0, sectors 8

end: (c,h,s) expected (1023,3,16) found (1023,63,32)
start: (c,h,s) expected (1023,3,16) found (1023,63,32)
end: (c,h,s) expected (1023,3,16) found (1023,63,32)
/sbin/tune2fs

MeeGo 1.2 Harmattan (none) /dev/ttyS0

(none) login: Home filesystem state ok
sysconfig-middle start/running
gconfd start/running, process 475
no-bme start/running, process 478
[ 9.469055] EXT4-fs (mmcblk0p3): recovery complete
[ 9.473846] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode
mount-home start/running
bme start/running, process 465
Ram size = 1008656 kB
Enable compressed swap on RAM with size 262144 kilobytes
dsme-thermal start/running
[ 11.216918] ramzswap: num_devices not specified. Using default: 1
[ 11.217468] ramzswap: Creating 1 devices ...
disksize_kb: 262144[ 11.239562] ramzswap: Disk size set to 262144 kB

[ 11.252319] Adding 262136k swap on /dev/ramzswap0. Priority:-1 extents:1 across:262136k SS
CHECK_MALF starting
tracker-init stop/waiting
MALF_CHECK_DONE
rich-core-pattern start/running
Starting SGX Driver

Now, the thing that should follow the point where your device hangs is the timeout of the OMAP i2c bus 2 controller, followed by initialization of the RGB-LED driver lp5521.
One way forward would be now to check from kernel sources what's happening at that point in initialization, maybe add some more debug and try again, to see if the exact hangpoint can be found.

One another thing, BTW.
There is the kernel command line on the log, on the 13th row. Did you cut off the rest of the line or is it in reality so short?

In your log it is just
[ 0.000000] Kernel command line: init=/sbin/preinit_harmattan root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 8

It should in reality be something like this:
[ 0.000000] Kernel command line: init=/sbin/preinit_harmattan root=/dev/mmcblk0p2 rootwait rootflags=errors=remount-ro rootfstype=ext4 rw mtdoops.mtddev=log mtdoops.record_size=65536 console=ttyS0,115200n8 mtdparts=omap2-onenand:1024k(bootloader),2816k@1024k(config),1638 4k@3840k(kernel),2048k@20224k(log),469248k@22272k( var),32768k@491520k(moslo) bootreason=32wd_to bootmode=normal nolo=2.3.6 product_name=RM-696 dbi-type=V5JW dbi-vendor=1 dbi-size=73 dbi-uid=01314A4D4A0025414314 imei=357923042386401 g_nokia.iSerialNumber=357923042386401 serialnumber=CON727735 omap_sec.kci=958 gpio=cmt_apeslpx:93:sysfs:output,cmt_en:23:sysfs:i nit_active:output,cmt_rst_rq:88:sysfs:init_active: output,sleep_ind:92:sysfs:output omapdss.def_disp_enabled=0 vhash=285e93eebfdded180a3ffdf0a42c0d09b0d8ce8a product_model=N9 hwid=1603

Re: Introducing ubiboot N9 (multiboot OS loader)

One thing I forgot to ask; If I recall correctly you also had trouble booting Sailfish via ubiboot, right?

So could you also please try to get same kind of boot log out of that, since the kernels are fairly different; it might be that looking at that log also will yield more insight into the problem... :)

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.
I also thought about it :)
Here you go.
This looks similar (in the sense that stops at one point with no kernel panic...)
I'll check the ubiboot kernel command lines to see if there's something wrong.

Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1425316)

Looking at the SailfishOS logfile, it actually seems it boots correctly to initialize the system. I bet if you had also the RxD line connected to your serial dongle you could actually login as root.

Does the screen still show nothing when you boot to SailfishOS?
What about if you connect the USB cable to a computer, does it make any difference? What gets recognized in the PC side when you try that?

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1425231)

I compiled a test kernel with some more printouts around the suspect areas to find what happens in the hanging.

The kernel image is here: http://www.swagman.org/juice/debug_f...32_l2fix_debug (md5sum=6218bd1c976d66bed03044f5ee19d0c6)
Modules to go are here: http://www.swagman.org/juice/debug_f...fl61_debug.tar (md5sum=302dce1c409ac3200c2ce3d45c702863)

You need to untar the modules under your Harmattan /lib/modules, but there's no need to depmod them, I already built the dependencies.
Then, boot up the kernel with ubiboot and check with serial console what it looks like.

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.
After a few more tests and a lot of time spent, I decided to sell the thing for parts. I ran out of time &patience....
Should someone be interested, you can see the auction here:
http://m.ebay.es/itm/291147632821?nav=SEARCH

I`m sorry but I can`t test the new kernel Juiceme has just posted.

Thankyou specially to Juiceme for his brilliant support, I didn`t expect to learn & hack as much as I did with his help.
Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by pasko (Post 1425489)

Oh dear, I kind of hoped we'd crack this with your aid.
Too bad, I hope you'll be getting a Jolla or a Neo900 as a replacement device :D

Re: Introducing ubiboot N9 (multiboot OS loader)

Hi.
Sure, the only restriction will be: WP , IOS or Android are excluded.
Sincerely, thank you for your help..

Regards.

Blank screen, only android booting

Hi!

I proudly changed my system (preinits, ubiboot files) from the preconfigured Harmattan/Sailfish dual-boot to real ubiboot-multiboot.
I did not reflash my device!

Harmattan works perfectly like before, Nitdroid boots also.

Sailfish used to work greatly in previous configuration, but now suffers missing a port of the screen, 2cm to the right, leaving a black margin. Moreover, it is unusably lagging responsive now, and screen does not turn off. Kernel is the same i used previously!

See also appended picture.

http://i61.tinypic.com/x6lwft.jpg

I just realized that Harmattan shows a black screen only after boot, but it worked the first time after performing the modifications.
I noticed once after starting ubiboot in maintenance mode and booting into Harmattan, it switched of regularly, i.e. the front light on for some seconds.

kindly check my log, dmesg and ini files!

I was also wondering how to access the kernel loading location from ubiboot maintenance mode. There is rootfs/boot holding my Harmattan and Nitdroid kernel. However, the ubiboot.conf points to a different location?!

Thank you VERY MUCH for going to help!

Re: Introducing ubiboot N9 (multiboot OS loader)

you should use ubiboot for sailfishos or copy config values from nemo to sailfishos entries

vram=6m omapfb.vram=0:6M

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by coderus (Post 1431282)

you should use ubiboot for sailfishos or copy config values from nemo to sailfishos entries

vram=6m omapfb.vram=0:6M

That was a good hint! Harmattan, Nitdroid, Sailfish work seamlessly fine! (=
Spasiba!!!

Re: Introducing ubiboot N9 (multiboot OS loader)

Quote:

Originally Posted by juiceme (Post 1425505)

Oh dear, I kind of hoped we'd crack this with your aid.
Too bad, I hope you'll be getting a Jolla or a Neo900 as a replacement device :D

Hi.
Finally I bought a used N9 in good condition. As soon as I have some spare time I'll be back again!
Regards.

Re: Introducing ubiboot N9 (multiboot OS loader)

Still dudnt get to make that serial adapter :)
But, now at least I have the soldering iron hehe.
And, somewhere, the USB-RS232 adapter.
Would also love to see if it really is impossible to get that USB console up - I got some parts for that, which I hope would work.
They should, they are from mainland China LOL