Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 18 hrs, 59 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days, 7 hrs ago - more...
|
2012-07-09
, 09:08
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#342
|
If mmcblk0p1 is not valid fat partition, bootmenu script will not be read.
Benefit of loading always is that you can specify "default" menu entry which will be first in list and will be booted when timer expires or auto booted with closed keyboard.
Omap bootreason atag comes from NOLO and now u-boot can parse original atags and create its own. But there is no reason shutdown. Only ACK_DEAD which means shutdown or charger attached. And show u-boot menu in charger attached mode is usefull too.
Benefit of loading always is that you can specify "default" menu entry which will be first in list and will be booted when timer expires or auto booted with closed keyboard.
Omap bootreason atag comes from NOLO and now u-boot can parse original atags and create its own. But there is no reason shutdown. Only ACK_DEAD which means shutdown or charger attached. And show u-boot menu in charger attached mode is usefull too.
| The Following 4 Users Say Thank You to pali For This Useful Post: | ||
|
|
2012-07-09
, 15:28
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#343
|
Great to see the option to load a kernel by default.
Installed the two new packages and changed the atags.
When rebooting with keyboard closed, I still get the u-boot menu and a 30 seconds timeout. Is this expected behaviour? I would expect it to instantly load the default kernel...
Installed the two new packages and changed the atags.
When rebooting with keyboard closed, I still get the u-boot menu and a 30 seconds timeout. Is this expected behaviour? I would expect it to instantly load the default kernel...
| The Following User Says Thank You to ade For This Useful Post: | ||
|
|
2012-07-09
, 15:43
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#344
|
Yes, this is bug. It should boot without delay. I found problem that I forgot to call "setenv bootdelay 0" if keyboard is closed. Now compiling new version.
|
|
2012-07-09
, 15:53
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#345
|
fixed and -flasher and -bootimg packages updated.
| The Following 3 Users Say Thank You to pali For This Useful Post: | ||
|
|
2012-07-09
, 16:03
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#346
|
Originally Posted by pali
Are you sure you have updated the two packages? I still get the 30 seconds timeout, and looking at the timestamp of the packages it could be the "old" ones.
fixed and -flasher and -bootimg packages updated.
| The Following User Says Thank You to ade For This Useful Post: | ||
|
|
2012-07-09
, 20:52
|
|
Posts: 323 |
Thanked: 180 times |
Joined on Oct 2009
@ Gent, Belgium
|
#349
|
Forgive me for not seeing 'it' but whatever I change, the .item filename itself or the description inside the .item file, I don't manage to get my preferred kernel listed before the auto-added 'u-boot attached' Maemo kernel.
So the ultimate list shown and used is not alphabetically sorted or the 'first-one-in-the-list' logic should skip the first, auto-added entry.
Am I seeing it wrong somewhere ?
Thanks for the new version ! Great to still see progress on all fronts.
So the ultimate list shown and used is not alphabetically sorted or the 'first-one-in-the-list' logic should skip the first, auto-added entry.
Am I seeing it wrong somewhere ?
Thanks for the new version ! Great to still see progress on all fronts.
|
|
2012-07-09
, 21:27
|
|
Posts: 1,100 |
Thanked: 2,797 times |
Joined on Apr 2011
@ Netherlands
|
#350
|
Originally Posted by Netweaver
You will have to create a symbolic link in /etc/defaults/ named bootmenu.item to your preferred kernel item file
Forgive me for not seeing 'it' but whatever I change, the .item filename itself or the description inside the .item file, I don't manage to get my preferred kernel listed before the auto-added 'u-boot attached' Maemo kernel.
So the ultimate list shown and used is not alphabetically sorted or the 'first-one-in-the-list' logic should skip the first, auto-added entry.
Am I seeing it wrong somewhere ?
Thanks for the new version ! Great to still see progress on all fronts.
Could be for example:
bootmenu.item -> /etc/bootmenu.d/20-Maemo5-kernel-power-2.6.28.10-power50.item
| The Following 4 Users Say Thank You to ade For This Useful Post: | ||
thanks for making it always better and better and continuation!
But one question: what is the benefit of loading bootmenu.scr always? Especially what will happen, if mmcblk0p1 is screwed (and it can not be read)?
And one more: when I poweroff (and when I do it, I do it often with keyboard out in x-term) then u-boot will load and wait for 30 s. The display is dark, so I do not notice it as I want to start again. Any chance to detect boot reason=shutdown and shorten th timeout?
Just a little personal liking request, so feel free to ignore
Oh and btw, I just reread first post and checked your repo.
Could you please provide also your u-boot.bin again?
Because I merged that with kp50 kernel, so my attachboot is kp50. (I am sure it would be possible to extract it from u-boot flasher kernel, but ...) Sorry, it is there (and has already been).
Last edited by peterleinchen; 2012-07-09 at 12:58.