Hi, > Am 04.01.2019 um 07:05 schrieb Andreas Kemnade <[email protected]>: > > On Thu, 3 Jan 2019 23:08:11 +0100 > "H. Nikolaus Schaller" <[email protected]> wrote: > >> Hi, >> I have built a new debian image for Phosh (debootstrapped + letux-minimal + >> purism-sources-list + letux-phosh): >> >> http://download.goldelico.com/letux-debian-rootfs/?C=M;O=D >> >> which can be installed (togehter with the letux-4.19.12 kernel) through >> >> makesd phosh >> >> or for a two-partition system like the Pyra or OpenPandora >> >> makesd pyra-4gb -r phosh >> >> (assuming the latest makesd: run "makesd -u" to be sure). >> >> There is now a user "purism" with default password "123456" which should also >> be the PIN for the initial unlocking screen. >> >> This is of course not safe at all but good enough for initial experiments... >> Phosh is still under heavy development and Debian/Buster is not yet stable >> anyways. >> >> Well, it boots but running phosh on the Pyra fails: >> >> root@letux:~# phosh >> 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output Virtual-1 >> with mode [email protected] >> 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with >> mode [email protected] >> 2018-12-21 18:54:53 - [backend/session/logind.c:363] Failed to get seat id: >> No data available >> 2018-12-21 18:54:53 - [backend/session/direct.c:159] Could not get current >> tty number: Inappropriate ioctl for device >> 2018-12-21 18:54:53 - [backend/session/session.c:76] Failed to load session >> backend >> 2018-12-21 18:54:53 - [backend/backend.c:250] Failed to start a DRM session >> 2018-12-21 18:54:53 - [rootston/main.c:26] could not start backend >> root@letux:~# cat /etc/debian_version >> buster/sid >> root@letux:~# uname -a >> Linux letux 4.19.12-letux+ #3090 SMP PREEMPT Mon Dec 24 13:47:00 CET 2018 >> armv7l GNU/Linux >> root@letux:~# >> >> There is only a (properly rotated!) login: with blinking cursor shown on the >> display. >> >> Trying the same on GTA04A4 has exactly the same error messages but the >> display is even completely inactive. >> > Does the phosh service start or are you seeing just gdm stuff? > The further is working for we, the latter not. > In my installation I had to do a manual > systemctl start phosh
Ah, good. It works :) Takes approx 1 minute on GTA04 but then I get this screen: Yeah! Touch is not properly working as Mark already reported. On the Pyra, "systemctl start phosh" makes the text framebuffer console cursor stop blinking and "systemctl stop phosh" makes it blink again. Xwayland is running but screen remains black. Maybe Xwayland can't handle our TILER rotation properly. > > since is was not configured to run at startup. So we should add some autostart to the rootfs image. Maybe someone can provide a phosh.service file so that I can add it to /etc/systemd/system/ in the letux-phosh.deb package. BR and happy testing, Nikolaus
_______________________________________________ Community mailing list [email protected] http://lists.goldelico.com/mailman/listinfo.cgi/community http://www.tinkerphones.org
