Thread
:
Building an updated kernel (problems)
View Single Post
Capn_Fish
2010-04-13 , 12:32
Posts: 140 | Thanked: 13 times | Joined on Mar 2008
#
10
Well, hopefully this'll be the last issue (wireless potentially aside).
Every kernel I've tried that's not the Diablo one doesn't boot fully (to either Maemo or Mer). It looks like it will (see previous post), but then shuts down. From the Mer boot output, it seems to not even always be at the same point.
I'm in R&D mode ("sudo flasher --enable-rd-mode --set-rd-flags=no-omap-wd,no-lifeguard-reset,no-ext-wd" is the command I've used), since, if I'm not, it just reboots pretty much right away.
For what it's worth, Maemo shuts down very shortly after getting to the desktop when in R&D mode as well, when using the standard 2.6.21 kernel.
So what am I doing wrong? My impression was that disabling all the watchdogs and lifeguard reset should prevent this.
EDIT: It would seem that xserver-xomap doesn't work with the updated kernels...
EDIT2: Disabling the watchdog prevent shutdown option (in the kernel, 2.6.33 w/patches from linked thread) lets me at least stop the rebooting when Xomap fails to start, but isn't helpful aside from that.
__________________
Nokia N810 (Some mutation of Mer)
Last edited by Capn_Fish; 2010-04-13 at
21:19
.
Quote & Reply
|
Capn_Fish
View Public Profile
Send a private message to Capn_Fish
Find all posts by Capn_Fish