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 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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.
So there is still a config issue and I have no idea what a "seat id" should be...
BR, Nikolaus
On 1/3/19, H. Nikolaus Schaller hns@goldelico.com 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 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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.
So there is still a config issue and I have no idea what a "seat id" should be...
BR, Nikolaus
Hi Nikolaus!
How are you trying to run Phosh? It needs to be run on the tty, so just launching via ssh won't work. You should either configure something like systemd service to run it, or use something like openvt.
Also, Phosh should be run as a normal user, not as root.
Actually, I should probably just look around for some SD card to install it on... :)
Thanks!
Hi Sebastian,
Am 04.01.2019 um 00:20 schrieb Sebastian Krzyszkowiak dos@dosowisko.net:
unfortunatley, the mail wasn't delivered earlier...
On 1/3/19, H. Nikolaus Schaller hns@goldelico.com 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 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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.
So there is still a config issue and I have no idea what a "seat id" should be...
BR, Nikolaus
Hi Nikolaus!
How are you trying to run Phosh? It needs to be run on the tty, so just launching via ssh won't work. You should either configure something like systemd service to run it, or use something like openvt.
Also, Phosh should be run as a normal user, not as root.
This issue is already solved and Phosh is now running automatically after boot... It still needs better config for touchscreen and other components (Mark has provided some but I haven't integrated it yet).
Actually, I should probably just look around for some SD card to install it on... :)
Yes, you are welcome to this game! Just "makesd phosh".
BR, Nikolaus
H. Nikolaus Schaller wrote on Thu, Jan 03, 2019:
root@letux:~# phosh 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output Virtual-1 with mode 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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
I don't have any device to play with and never tried phosh, but the wlroots logind code here is pretty trivial, sd_session_get_seat() failed so looking at systemd code it looks like /run/systemd/sessions/<whatever your session is> doesn't have a SEAT value i.e. `loginctl list-sessions` would not match up your current session with a systemd "seat".
There can be many reasons for that but I'd wager something is missing in your pam, is there a line 'session optional pam_systemd.so' in the pam used at login?
Basically you need to make systemd understand that logging in from the tty means having physial access, with the seat lies all kinds of permissions to use the graphic cards and input devices etc.
On Thu, 3 Jan 2019 23:08:11 +0100 "H. Nikolaus Schaller" hns@goldelico.com 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 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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
since is was not configured to run at startup.
Regards, Andreas
Hi,
Am 04.01.2019 um 07:05 schrieb Andreas Kemnade andreas@kemnade.info:
On Thu, 3 Jan 2019 23:08:11 +0100 "H. Nikolaus Schaller" hns@goldelico.com 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 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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
On Fri, 4 Jan 2019 09:56:42 +0100 "H. Nikolaus Schaller" hns@goldelico.com wrote:
Maybe someone can provide a phosh.service file so that I can add it to /etc/systemd/system/ in the letux-phosh.deb package.
There is already /lib/systemd/system/phosh.service
it just needs to be enabled.
Regards, Andreas
Hi Andreas,
Am 04.01.2019 um 12:57 schrieb Andreas Kemnade andreas@kemnade.info:
On Fri, 4 Jan 2019 09:56:42 +0100 "H. Nikolaus Schaller" hns@goldelico.com wrote:
Maybe someone can provide a phosh.service file so that I can add it to /etc/systemd/system/ in the letux-phosh.deb package.
There is already /lib/systemd/system/phosh.service
Ah, nice.
it just needs to be enabled.
which means to set a symlink
/etc/systemd/system/phosh.service -> /lib/systemd/system/phosh.service
after installing phosh. Right?
BR, Nikolaus
Am 04.01.2019 um 13:15 schrieb H. Nikolaus Schaller hns@goldelico.com:
Hi Andreas,
Am 04.01.2019 um 12:57 schrieb Andreas Kemnade andreas@kemnade.info:
On Fri, 4 Jan 2019 09:56:42 +0100 "H. Nikolaus Schaller" hns@goldelico.com wrote:
Maybe someone can provide a phosh.service file so that I can add it to /etc/systemd/system/ in the letux-phosh.deb package.
There is already /lib/systemd/system/phosh.service
Ah, nice.
it just needs to be enabled.
which means to set a symlink
/etc/systemd/system/phosh.service -> /lib/systemd/system/phosh.service
after installing phosh. Right?
No...
This just makes a tty0 text console appear after reboot.
The right thing to do seems to be to simulate:
root@letux:~# systemctl enable phosh.service Created symlink /etc/systemd/system/graphical.target.wants/phosh.service -> /lib/systemd/system/phosh.service. root@letux:~#
BR, Nikolaus
Hi,
On 2019/01/04 9:56, H. Nikolaus Schaller wrote:
Hi,
Am 04.01.2019 um 07:05 schrieb Andreas Kemnade <andreas@kemnade.info mailto:andreas@kemnade.info>:
On Thu, 3 Jan 2019 23:08:11 +0100 "H. Nikolaus Schaller" <hns@goldelico.com mailto:hns@goldelico.com> 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).
Very cool!
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
Phosh should be run as user purism.
2018-12-21 18:54:53 - [rootston/config.c:370] Configured output Virtual-1 with mode 720x1440@0.000000 2018-12-21 18:54:53 - [rootston/config.c:370] Configured output X11-1 with mode 768x1024@0.000000 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.
The service file is /lib/systemd/system/phosh.service (see dpkg -L phosh). I wonder, why it's not already activated - should be handled in the phosh.postinst script via the deb-systemd-* stuff. A "sudo systemctl enable phosh" helped in my case.
The service starts phosh as user purism via the shell script /usr/bin/phosh using /dev/tty7.
BTW: You can put your modified rootston.ini in /etc/phosh/rootston.ini to customize your settings. But phosh should start with the default config from /usr/share/phosh/rootston.ini as well.
The rootston.ini for the GTA04 looks like this (with xwayland disabled,currently):
#[core] #xwayland=false
[cursor:seat0] map-to-output = DPI-1 #geometry = 480x640 theme = default
[output:DPI-1] #x = 480 #y = 640 mode = 480x640 #scale=1
[device:TSC2007 Touchscreen] map-to-output = DPI-1 #tap_enabled = true #geometry = 480x640
[keyboard] meta-key = Logo
[bindings] Alt+Tab = next_window Logo+Up = maximize Alt+F4 = close #Ctrl+a = alpha
There are still some other issues (with apt/apt-key) in this image, but they are probably related to the current updates of Debian Buster. I didn't have these issues before updating around Christmas.
Regards, Mark
-
Andreas Kemnade -
Dominique Martinet -
H. Nikolaus Schaller -
Mark Müller -
Sebastian Krzyszkowiak