Thread: how to troubleshoot boot sequence?
View Single Post
charlie is offline charlie
2008-02-05 , 21:20
Posts: 13 | Thanked: 6 times | Joined on Feb 2008 @ UK
#10
Well, sure enough X is exiting - here's the evidence from syslog:

Code:
Feb  5 20:28:06 Nokia-N810-50-2 DSME: Closed a client connection
Feb  5 20:28:06 Nokia-N810-50-2 DSME: process '/usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolisten tcp' with pid 1014 exited with return value: 1
Feb  5 20:28:06 Nokia-N810-50-2 DSME: '/usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolisten tcp' exited with RESET policy -> reset
Feb  5 20:28:06 Nokia-N810-50-2 DSME: Here we will request for sw reset
Feb  5 20:28:06 Nokia-N810-50-2 DSME: Here we could do some bookkeeping..
Feb  5 20:28:06 Nokia-N810-50-2 user: Starting temp-reaper-startup.sh
Feb  5 20:28:06 Nokia-N810-50-2 DSME: Accepted new client connection
Feb  5 20:28:06 Nokia-N810-50-2 DSME: Closed a client connection
I've attached a zip containing the full syslog from this boot (truncated at the point where matchbox is repeatedly restarted).

Manually starting X (executing "/usr/bin/Xomap -mouse tslib -nozap -dpi 96 -wr -nolisten tcp") produces the following:

Code:
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Multiple names for keycode 138
>                   Using <I138>, ignoring <PROP>
> Warning:          Multiple names for keycode 140
>                   Using <I140>, ignoring <FRNT>
> Warning:          Multiple names for keycode 211
>                   Using <I211>, ignoring <AB11>
Errors from xkbcomp are not fatal to the X server
X appears to continue running, however there are no visible changes on the tablet screen at this point and nothing further is reported to the shell connection.

Any other suggestions, or should I give up on this installation and roll back to a previous backup?
Attached Files
File Type: zip BootResults.zip (8.3 KB, 262 views)