Hi aTc, ED did give me the link to download the latest Pyra OS.
Well, since I am a fan of "not invented here", I did not use the install.sh script, but did repack/rename the rootfs and copied to my download server.
The I flashed an SD card with ./makesd:
DEV=/dev/sdb ./makesd pyra -c none -r http://download.goldelico.com/letux-debian-rootfs/latest-pyra.tbz
This installs the latest letux kernel (which is 4.10.5) and u-boot.
Pyra boots fine up to login:
But then I am stuck... What is the default root user/password setup?
And I have no X11. This may come from installing my letux-kernel or some differences to the zmatt kernel you use. But without root login I can't debug...
Another potential channel would be to log in through g_ether (which runs and is found by the host). But what is the IP address if the usb0 interface? And again user/password are needed :)
BR, Nikolaus
root/root
tip: if you have qemu-arm-static installed on your host system and the sdcard mounted at /mnt/tmp (fill in different path to taste) you can "enter" the image with:
systemd-nspawn --bind-ro=/usr/bin/qemu-arm-static --tmpfs=/run/lock -M pyra -a -D /mnt/tmp
now you can just change the root password with "passwd", or create new user accounts. even installing packages using apt-get works fine
Am 29.03.2017 um 22:08 schrieb Matthijs van Duin matthijsvanduin@gmail.com:
root/root
Ah, that was too easy for my around-the-corner-thinking-attitude :)
Now I could look into Xorg.0.log and it is something like
[ 114.574] (==) Depth 24 pixmap format is 32 bpp [ 114.575] (EE) FBTURBO(0): FBIOPUT_VSCREENINFO: Invalid argument [ 114.575] (EE) FBTURBO(0): mode initialization failed
DSS itself seems to work (cat /dev/urandom >/dev/fb0 fills the screen with colored noise).
tip: if you have qemu-arm-static installed on your host system and the sdcard mounted at /mnt/tmp (fill in different path to taste) you can "enter" the image with:
systemd-nspawn --bind-ro=/usr/bin/qemu-arm-static --tmpfs=/run/lock -M pyra -a -D /mnt/tmp
Interesting trick to remember in case I need it!
now you can just change the root password with "passwd", or create new user accounts. even installing packages using apt-get works fine
Ok, now I was able to enable g_ether networking and get new things onto the Pyra (except that I can't ssh from outside into the Pyra)
One tiny observation:
root@localhost:~# apt-get update Err:1 http://uevm stretch InRelease Could not resolve 'uevm' ... root@localhost:~# more /etc/apt/sources.list.d/multistrap-pyra.list deb [arch=armhf] http://uevm stretch main deb-src http://uevm stretch main root@localhost:~#
Seems to be a bug to assume a host named 'uevm' exists...
BR and thanks, Nikolaus
On 03/30/2017 07:40 PM, H. Nikolaus Schaller wrote:
Am 29.03.2017 um 22:08 schrieb Matthijs van Duin matthijsvanduin@gmail.com:
root/root
Ah, that was too easy for my around-the-corner-thinking-attitude :)
Now I could look into Xorg.0.log and it is something like
[ 114.574] (==) Depth 24 pixmap format is 32 bpp [ 114.575] (EE) FBTURBO(0): FBIOPUT_VSCREENINFO: Invalid argument [ 114.575] (EE) FBTURBO(0): mode initialization failed
DSS itself seems to work (cat /dev/urandom >/dev/fb0 fills the screen with colored noise).
It's either the kernel, or your install script might have added/overwritten some xorg config files.
Ok, now I was able to enable g_ether networking and get new things onto the Pyra (except that I can't ssh from outside into the Pyra)
ssh as root is disabled by default in debian. you can change it in /etc/ssh/sshd_config
One tiny observation:
root@localhost:~# apt-get update Err:1 http://uevm stretch InRelease Could not resolve 'uevm' ... root@localhost:~# more /etc/apt/sources.list.d/multistrap-pyra.list deb [arch=armhf] http://uevm stretch main deb-src http://uevm stretch main root@localhost:~#
Seems to be a bug to assume a host named 'uevm' exists...
Well it works fine here :) It's just the local repo I use to create the image. I still have to convert the official one to stretch.
I should have an updated image soon.
Am Fri, 31 Mar 2017 02:03:22 +0200 hat aTc atc@k-n-p.org geschrieben:
Ok, now I was able to enable g_ether networking and get new things onto the Pyra (except that I can't ssh from outside into the Pyra)
ssh as root is disabled by default in debian. you can change it in /etc/ssh/sshd_config
Alternatively, you can also ssh as your user and use sudo su. The user created by the FirstRunWizard is in the sudoers file.
On 30 March 2017 at 19:40, H. Nikolaus Schaller hns@goldelico.com wrote:
[ 114.574] (==) Depth 24 pixmap format is 32 bpp [ 114.575] (EE) FBTURBO(0): FBIOPUT_VSCREENINFO: Invalid argument [ 114.575] (EE) FBTURBO(0): mode initialization failed
Fixed in the latest version of my patch/tiler-fbdev (along with the output-disabling issue)
Am 31.03.2017 um 02:24 schrieb Matthijs van Duin matthijsvanduin@gmail.com:
On 30 March 2017 at 19:40, H. Nikolaus Schaller hns@goldelico.com wrote: [ 114.574] (==) Depth 24 pixmap format is 32 bpp [ 114.575] (EE) FBTURBO(0): FBIOPUT_VSCREENINFO: Invalid argument [ 114.575] (EE) FBTURBO(0): mode initialization failed
Fixed in the latest version of my patch/tiler-fbdev (along with the output-disabling issue)
Works with letux-4.11-rc4 (I had to make a tiny fix to get patch/tiler-fbdev compiled).
Now I get the Pyra logo and start message :) Touch is working so I can tap the Ok and get the window where it asks for the user name. One comment: the font is far too tiny.
But keyboard isn't. evtest /dev/input/keyboard also shows no activity so that I think it is a driver problem. There were some recent patches [1] for 4.11-rc.
So we can indeed mix PyraOS and Letux kernels by simply using the makesd script.
Since letux-4.11-rc4 is ahead of the latest default/stable kernel we have to specify it explicitly on the makesd command:
DEV=/dev/sdb ./makesd pyra -c none -r http://download.goldelico.com/letux-debian-rootfs/latest-pyra.tbz -m letux-4.11-rc4 -F -k letux-4.11-rc4 -d letux-4.11-rc4
BR, Nikolaus
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?id=r...
Am 02.04.2017 um 21:00 schrieb H. Nikolaus Schaller hns@goldelico.com:
Am 31.03.2017 um 02:24 schrieb Matthijs van Duin matthijsvanduin@gmail.com:
On 30 March 2017 at 19:40, H. Nikolaus Schaller hns@goldelico.com wrote: [ 114.574] (==) Depth 24 pixmap format is 32 bpp [ 114.575] (EE) FBTURBO(0): FBIOPUT_VSCREENINFO: Invalid argument [ 114.575] (EE) FBTURBO(0): mode initialization failed
Fixed in the latest version of my patch/tiler-fbdev (along with the output-disabling issue)
Works with letux-4.11-rc4 (I had to make a tiny fix to get patch/tiler-fbdev compiled).
Now I get the Pyra logo and start message :) Touch is working so I can tap the Ok and get the window where it asks for the user name. One comment: the font is far too tiny.
But keyboard isn't. evtest /dev/input/keyboard also shows no activity so that I think it is a driver problem. There were some recent patches [1] for 4.11-rc.
Was an easy fix.
We now have to explicitly specify IRQ falling edge in the DT. We had rising edge which was wrong, but ignored and overwritten by the old driver. I have included this patch in the letux-4.11-rc5 build.
So we can indeed mix PyraOS and Letux kernels by simply using the makesd script.
Since letux-4.11-rc4 is ahead of the latest default/stable kernel we have to specify it explicitly on the makesd command:
DEV=/dev/sdb ./makesd pyra -c none -r http://download.goldelico.com/letux-debian-rootfs/latest-pyra.tbz -m letux-4.11-rc4 -F -k letux-4.11-rc4 -d letux-4.11-rc4
BR, Nikolaus
Kernel mailing list Kernel@pyra-handheld.com http://pyra-handheld.com/cgi-bin/mailman/listinfo/kernel
Am 03.04.2017 um 19:28 schrieb H. Nikolaus Schaller hns@goldelico.com:
Works with letux-4.11-rc4 (I had to make a tiny fix to get patch/tiler-fbdev compiled).
Now I get the Pyra logo and start message :) Touch is working so I can tap the Ok and get the window where it asks for the user name. One comment: the font is far too tiny.
But keyboard isn't. evtest /dev/input/keyboard also shows no activity so that I think it is a driver problem. There were some recent patches [1] for 4.11-rc.
Was an easy fix.
We now have to explicitly specify IRQ falling edge in the DT. We had rising edge which was wrong, but ignored and overwritten by the old driver. I have included this patch in the letux-4.11-rc5 build.
So we can indeed mix PyraOS and Letux kernels by simply using the makesd script.
Since letux-4.11-rc4 is ahead of the latest default/stable kernel we have to specify it explicitly on the makesd command:
DEV=/dev/sdb ./makesd pyra -c none -r http://download.goldelico.com/letux-debian-rootfs/latest-pyra.tbz -m letux-4.11-rc4 -F -k letux-4.11-rc4 -d letux-4.11-rc4
I found a minute to start flashing a new SD card [1] and another one to run through the setup assistant. Keyboard works now.
Here some experience: * font is really small * keyboard works * I could register a user+password, choose timezone (well Munich is not included but that is Debian), and ssh firewall * then it said "done" * the enter key appears non-responsive for the "done" but touch was * what was not clear to me is that this triggers a reboot starting to turn everything off - user could be warned in the "Done" window. * reboot runs the kernel into "clock: dpll_abe_ck failed transition to 'locked'" bug so it does not properly reboot * therefore I forced shutdown and rebooted * it was quite unexpected that the vibramotor did rumble for a second :) * but the PyOS desktop came alive * one observation is that the modem power driver starts the modem by default. This is because rfkill wwan isn't soft-blocked initially. It should also be blocked on poweroff since the modem is powered independently of the OMAP (to allow for deep shutdown). I have the same and added some initd script to "rfkill block wwan" on poweroff.
So my impression is very good. We are almost there with the setup-assistant (even when mixing my kernel with your rootfs).
Hope this feedback helps for improvements.
BR, Nikolaus
[1]: KERNEL=letux-4.11-rc5; DEV=/dev/sdb ./makesd pyra -c none -r http://download.goldelico.com/letux-debian-rootfs/latest-pyra.tbz -m $KERNEL -F -k $KERNEL -d $KERNEL
On 04/04/2017 09:30 PM, H. Nikolaus Schaller wrote:
I found a minute to start flashing a new SD card [1] and another one to run through the setup assistant. Keyboard works now.
Here some experience:
- font is really small
- keyboard works
- I could register a user+password, choose timezone (well Munich is not included but that is Debian), and ssh firewall
- then it said "done"
- the enter key appears non-responsive for the "done" but touch was
- what was not clear to me is that this triggers a reboot starting to turn everything off - user could be warned in the "Done" window.
- reboot runs the kernel into "clock: dpll_abe_ck failed transition to 'locked'" bug so it does not properly reboot
- therefore I forced shutdown and rebooted
- it was quite unexpected that the vibramotor did rumble for a second :)
- but the PyOS desktop came alive
- one observation is that the modem power driver starts the modem by default. This is because rfkill wwan isn't soft-blocked initially. It should also be blocked on poweroff since the modem is powered independently of the OMAP (to allow for deep shutdown). I have the same and added some initd script to "rfkill block wwan" on poweroff.
So my impression is very good. We are almost there with the setup-assistant (even when mixing my kernel with your rootfs).
I uploaded a new image a few days ago, (to the same place : http://packages.pyra-handheld.com/images/stretch/pyra-debian-stretch-mate.ta... ) which fixes a few issues.
The first-run-wizard (setup-assistant), is just a temporary hack copied mostly from the pandora. It will (should) be completely replaced by a real gui setup program, once we find someone with time to write it.
A proper xkb keymap for the keyboard is also beeing worked on.
You have to manually load the "xmodmap .Xmodmap" when logged into the mate desktop. Lightdm should be loading any .Xmodmap automatically, but fails for some reason. xmodmap isn't the right solution for it anyway.
Matt posted a mail here about the abe pll lockup last week.