Active Topics

 


Reply
Thread Tools
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#61
I just want to see console output when my n900 is booting. Where is an appropriate place to put 'modprobe fbcon' in pre-init?
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#62
Originally Posted by pali View Post
programs poweroff, halt and reboot send signal to upstart init daemon to reboot/poweroff system. If that fails programs fallback to use script /etc/init.d/minireboot. But upstart is not running (it is started after bootmenu start booting...) so program reboot try to connect (more times) to upstart, it spends time and then it switch to fallback.

I do not know what is good way to reboot/poweroff device when upstart is not running.

PS: upstart is not possible to start - when it is started, it start booting device!
OK Thanks. I just tried again. Doing "exit" shows the Nokia log and then turns off the N900 (maybe I didn't remember well when I wrote it before..).

Now I turn it on (kbd closed), and after entering the PIN I get to the "Welcome" screen asking me to set language/region/time/date.

After that everything's OK. I guess I have to investigate who/what starts that Welcome screen and see what I can do.

Does anybody else have this problem? or can anyone else confirm they DON'T have this problem??
 
Posts: 2,154 | Thanked: 8,464 times | Joined on May 2010
#63
Originally Posted by reinob View Post
Doing "exit" shows the Nokia log and then turns off the N900 (maybe I didn't remember well when I wrote it before..).
If you press power button, press CTRL+D or type exit, script will call minireboot. (all this is handled by my script)
 

The Following User Says Thank You to pali For This Useful Post:
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#64
OK. Now I now that the problem is that /etc/X11/Xsession.d/10osso_startup_wizard is somehow deciding that I need to set my regional settings again.

Will investigate further (maybe after recovery console it thinks a new SIM is in place, who knows?).
 
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#65
@vi_
http://talk.maemo.org/showpost.php?p...3&postcount=57

I did it and it's working great.

@reinob
When You get prompt to set date and time, is there already correct date/time set, or You must set it from scratch? If the latter is true, it's not only osso-startup-wizard, but something is resetting Your date/time.

In some special cases, I remember getting startup wizard prompt, but date was *not* reset - it was matter of confirming it, cause it was correct. On the other hand, after having battery out of N900 for a long time, date is reset = startup wizard doesn't reset time on it's own upon arrival.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following User Says Thank You to Estel For This Useful Post:
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#66
Originally Posted by Estel View Post
@vi_
http://talk.maemo.org/showpost.php?p...3&postcount=57

I did it and it's working great.

@reinob
When You get prompt to set date and time, is there already correct date/time set, or You must set it from scratch? If the latter is true, it's not only osso-startup-wizard, but something is resetting Your date/time.

In some special cases, I remember getting startup wizard prompt, but date was *not* reset - it was matter of confirming it, cause it was correct. On the other hand, after having battery out of N900 for a long time, date is reset = startup wizard doesn't reset time on it's own upon arrival.

/Estel
Cheers bro, are you using multiboot or bootmenu?
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#67
@Estel,

In my case both date and time are reset (date is like 01/01/2009). I will try later deactivating the 10osso_startup_wizard script and see what date/time I get when rebooting.

Just for the record, in /var/lib/osso-startup-wizard I have:
[State]
changed-without-pin=no
last-valid-sim-id=2620....
settings-changed=yes
sim-seen=yes

I will now turn off completely. Then boot to console and while in the console check the above file. Then exit/minireboot with deactivated osso-startup-... and check the file again (possibly with a wrong date and time, but for testing it's OK).
 

The Following User Says Thank You to reinob For This Useful Post:
Posts: 1,808 | Thanked: 4,272 times | Joined on Feb 2011 @ Germany
#68
OK. When in boot console the file wasn't changed.

Now booting Maemo normally I don't get the welcome screen (yes!), BUT date and time are reset.

More specifically, I go to the date and time settings and the 24-hour clock is still checked (good), no update automatically (good), time zone is correct (good).

Only date and time are messed up (Jan 1 2009, 01:00 GMT+1)

I don't know where to look, but something is messing up the date/time. However given that at least my zone settings are being kept, I might just activate the "update automatically" (I've never wanted to use that, it seems to randomly mess-up calendar events and alarms, just like in Symbian).
 

The Following User Says Thank You to reinob For This Useful Post:
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#69
Originally Posted by explit View Post
Hello boys and girls.

For all these, who, as I have multiboot, kernel-power49 and just want to see boot messages during boot (framebuffer console) there exist a solution.


Anything you need is to load the fbcon module with the command:

modprobe fbcon


The Problem is to put the command very early at boot, so that You see all boot messages during booting (and during shutdown)

I have a multiboot installed, so this is not possible to use bootmenu.
In this case, it is possible to put this command very early to
/sbin/preinit

I put

modprobe fbcon

in the line 9 of /sbin/preinit
after the line
export PATH=/usr/sbin:/usr/bin:/sbin:/bin

For People, who has bootmenu instead of multiboot, is possible to put modprobe fbcon to /bootmenu.sh


Pali Rohar has helped to solve this problem,
Thank you very much, Pali!

But please, be careful!

Playing with /sbin/preinit or /bootmenu.sh can put Your N900 to boot loop or make some other "very bad things"


Sorry for my bad English and best greetings from Berlin/Germany
The line:

Code:
export PATH=/usr/sbin:/usr/bin:/sbin:/bin
Does not appear in /sbin/preinit...
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 
Posts: 1,163 | Thanked: 1,873 times | Joined on Feb 2011 @ The Netherlands
#70
would like to have framebuffer als enabled on boot, only installed this(recovery console) thus have bootmenu installed. Where to add modprobe fbcon exactly?

Actaully the same question as vi_


Als after using the recovery console and typing "exit" I had the welcome screen too when booting in maemo, but date was reset, IIRC.
 

The Following 2 Users Say Thank You to mr_pingu For This Useful Post:
Reply

Tags
console, console-mode, framebuffer, recovery, recovery-mode


 
Forum Jump


All times are GMT. The time now is 18:35.