Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 15 hrs, 20 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 11 hrs ago - more...
| The Following 3 Users Say Thank You to pali For This Useful Post: | ||
|
2011-09-22
, 02:41
|
|
Posts: 1,042 |
Thanked: 430 times |
Joined on May 2010
|
#72
|
Thanks! Trial and error mode 
|
|
2011-09-24
, 19:49
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#73
|
Fianlly managed to boot nitdroid using the u-boot+k48.bin. Nitdroid uImage is on the sdcard without using multiboot. It directly loods the kernel from ths SDcard . But I still use the maemo rootfs as a initial ramdisk and created a special script to setup the system and switch the rootfs to the sdcard.
I went tot hte u-boot console prompt. Gave the command "setenv atagaddr ${init_atagaddr}" follwoed by run emmcboot.
In the end I;d like to have an initfs on the sdcard so I can boor without using the meamo rootfs.
I went tot hte u-boot console prompt. Gave the command "setenv atagaddr ${init_atagaddr}" follwoed by run emmcboot.
In the end I;d like to have an initfs on the sdcard so I can boor without using the meamo rootfs.
|
|
2011-09-25
, 07:00
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#74
|
You can use u-boot hush script instead loading directly uImage kernel. In script you can specify cmd options (like root device)
See bootorder: http://talk.maemo.org/showthread.php...59#post1090859
See how to create boot.scr script: http://elektranox.org/n900/kernel/uboot.html
See bootorder: http://talk.maemo.org/showthread.php...59#post1090859
See how to create boot.scr script: http://elektranox.org/n900/kernel/uboot.html
|
|
2011-09-25
, 10:53
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#75
|
yes, that is what I was planning to do. But to avoid using the internal meamo rootfs i need to define a proper initrd filesystem to be loaded.
One other thing though with your u-boot version. When I go into console mode the screen gets garbled as soon as scrolling is needed. e.g. press enter a couple of times, or run the help command will make the screen unreadable.
Did you notice this an/dor know how to fix this? It would also be nice the be able to scroll back to see the earlier text, or allow output to be piped to some sorte of 'more' command...
One other thing though with your u-boot version. When I go into console mode the screen gets garbled as soon as scrolling is needed. e.g. press enter a couple of times, or run the help command will make the screen unreadable.
Did you notice this an/dor know how to fix this? It would also be nice the be able to scroll back to see the earlier text, or allow output to be piped to some sorte of 'more' command...
|
|
2011-09-25
, 11:11
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#76
|
yes, I have same problem with unreadable console after scrolling. but this must be upstream u-boot bug. I used same rx51 patches on top of one year old u-boot tree and there was not this bug...
|
|
2011-09-26
, 10:50
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#77
|
Originally Posted by mirakels
The main problem is that Nitdroid's kernel (like original Maemo's Kernel) hasn't ext2 driver statically compiled.
yes, that is what I was planning to do. But to avoid using the internal meamo rootfs i need to define a proper initrd filesystem to be loaded.
So it can't boot, I suppose, from an Ext2 InitRD.
Many months ago I have tried to make a CramFS ramdisk but I have failed to boot from it (probably my error somewhere)
|
|
2011-09-26
, 19:58
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#78
|
Originally Posted by Fabry
I guess it must be possible to build a cpio formatted ramdisk and let the kernel do the proper ramdisk filesystem handling. After all it is able to use the internal maemo flash rootfs as a root filesystem without preloading any filesystem drivers.
The main problem is that Nitdroid's kernel (like original Maemo's Kernel) hasn't ext2 driver statically compiled.
So it can't boot, I suppose, from an Ext2 InitRD.
Many months ago I have tried to make a CramFS ramdisk but I have failed to boot from it (probably my error somewhere)
|
|
2011-09-26
, 20:02
|
|
Posts: 197 |
Thanked: 101 times |
Joined on Dec 2009
@ Netherlands
|
#79
|
Originally Posted by pali
I wonder if it is upstream. It only happens when the console_scrollup() function is called. Something weird is going on when moving the data up the framebuffer.
yes, I have same problem with unreadable console after scrolling. but this must be upstream u-boot bug. I used same rx51 patches on top of one year old u-boot tree and there was not this bug...
When I change the console_newline() function to not call the scrollup function but just set console_row = 0 no screen garbling occurs.
|
|
2011-09-26
, 22:01
|
|
Posts: 362 |
Thanked: 426 times |
Joined on Nov 2010
@ Italy, Lombardia
|
#80
|
Originally Posted by mirakels
But Cpio does not involve the use of EXT2 ?
I guess it must be possible to build a cpio formatted ramdisk and let the kernel do the proper ramdisk filesystem handling. After all it is able to use the internal maemo flash rootfs as a root filesystem without preloading any filesystem drivers.
Cpio Is just a archive format, but when the kernel, during boot process, decompresses the cpio image on ramfs does not try to use EXT2 ?
And without ext2/3/4 available which happens ?
RootFS is UBIFS and UBIFS is statically compiled on kernel
It is not possible to make a ramdisk with ubifs because UbiFs needs a Nand (or NandSim) under the hood
CramFS is available on Maemo and since I not see a module for it, I suppose that is present in the kernel itself.
So a cramfs initrd is teorically bootable.
Last edited by Fabry; 2011-09-26 at 22:10.
Last edited by pali; 2012-06-06 at 14:17.