View Single Post
Old 01-30-2013, 11:51 AM   #45
ah-
Connoisseur
ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.ah- knows the square root of minus one.
 
Posts: 64
Karma: 7786
Join Date: Jan 2012
Device: Kobo Touch
Ok, with devcap-daemon working the framework seems to start.

The screen stays black, and strace says it waits for a futex, so I guess it requires some other service to start up properly. But I'll investigate that later.

Edit:
After a bit more poking around and especially executing /etc/upstart/firstboot and prereg.conf manually as well as unpacking more cramfs.img from /etc/loopbacktab and setting the framebuffer to 8bit thanks to your framebuffer_configure it now really starts , still with tons of errors but I get a white window and touching the screen results in messages in the log. I see exceptions about missing images, but I haven't found out yet which images are missing and why.

Starting the onscreen keyboard (/usr/bin/kb) leads to the same error and is a lot less complex, so probably investigating that is easier.

Edit 2:
So it seems that this is just what you hinted at in the first posts, the screen update is different. I'm still looking at it, but I suspect awesome (the window manager) to be somehow responsible for it. Starting it pretty much corrupts the display, but upon a closer look the onboard keyboard letters are there in between the corruption.

Edit 3:
And it somewhat works :)
Attached Thumbnails
Click image for larger version

Name:	Foto am 30.01.13 um 22.54 #2.jpg
Views:	535
Size:	75.3 KB
ID:	100358  

Last edited by ah-; 01-30-2013 at 04:57 PM.
ah- is offline   Reply With Quote