Mer launch on Freescale i.MX53 QSB

[Simonas L.]

Dear all,

I have had success in first boot steps of KDE Active Plasma on i.MX53 QSB
[1]

rootfs was built on 20th Dec 2011 using Mer's build system with the
KickStart file [2], using Archos G9 KickStart [3] as a reference.
For boot-loader and kernel I used Ubuntu's MX5 prebuilt images [4]

X Server loaded correctly with omapfb driver.

Sadly KDE did not complete booting and the splash/background image [1]
switched to black-screen and popped an error [5] for just a couple of
seconds, which description approx. boils down to:
 KDE Power Management System could not be initialized.
 The backend reported the following error: No valid Power Management
backend plugins are available.
Log [8] line presumably being: kded(1139): KDE Power Management System init
failed!
Afterwards the screen remained black, X server running, no further
activities, no mouse pointer visible.

Keyboard works fine in the console, mouse is powered OK as well (plugged
directly into QSB, i.e. no external powered USB hub used)

I remember on the very first boot the error above was preceded with "KWin"
crashing dialog (similar if not identical to [6]), dismissed with "Close"

Links are provided to .Xorg.log.0 [7] and .xsession-errors [8]

Hope you can help me out to carry on with this. Thank you!


[1] http://static.inky.ws/image/1054/image.jpg
[2] http://pastebin.com/kugMgzrG
[3]
http://share.basyskom.com/contour/Deployment/mer_arm_install_archive/archos-generation-9/2011-12-16-17-25-basyskom-plasma-active-testing-mer-armv7l-archos-gen9-mmcblk1p-raw.ks(thanks
to vgrade from irc://
freenode.net/active)
[4]
http://cdimage.ubuntu.com/releases/oneiric/release/ubuntu-11.10-preinstalled-desktop-armel+mx5.img.gz
[5] http://static.inky.ws/image/1055/image.jpg
[6] http://www.dedoimedo.com/images/computers_years/2011_1/sabayon-crash.jpg
[7] http://pastebin.com/1j8ZGs8B
[8] http://pastebin.com/5LJXyKb2

-- 
Simonas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/active/attachments/20111231/e0acff0e/attachment.html>