Quirky Xerus 8.1.4 for Raspberry Pi2 and 3

For talk and support relating specifically to Puppy derivatives
Message
Author
Sage
Posts: 5536
Joined: Tue 04 Oct 2005, 08:34
Location: GB

#31 Post by Sage »

don't think I could destroy a working C-64
Generally, agree with your sentiment, t. However, one still occasionally encounters retro kit that is physically broken, eg keyboards, for which a super glue repair can be very acceptable, missing keys also fixable with ingenuity in some cases, or have electrical issues, eg leads pulled out, also fixable with a soldering iron. Some of these may be ideal candidates for an RPi transplant. Slightly off topic, there are community FIXIT groups springing up around the globe where folks bring their bent and broken commodities to a volunteer team of experts for advice and repair. Much of this is electrical/electronic goods. The throw-away society has left us without the knowledge, skills and, most importantly, the incentive to stop planet violation. Incumbent on all of us to stop landfill - now!

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#32 Post by BarryK »

A little progress report.

I got Abiword to run, after adding lots of dependencies.

This is using the official Abiword DEB, but it needs GTK3, as does Gnumeric.

I am thinking that I should compile Abiword and Gnumeric for GTK2, can eliminate a heap of deps, and won't need the gtk3 libs at all. As I have done in past x86(_64) Quirkies.

What I am trying to fix, before doing another upload, is the keyboard layout. So far, it has me baffled.

At the commandline, X not running, the arrow keys work. You can type something, then use the left-arrow and right-arrow.
However, start X, then the arrow keys cease to work.

The package selection, and all the infrastructure, is identical to my x86_64 Quirky Xerus, so why the keyboard layout is broken is a total mystery to me.

I have of course been trying various things to identify the cause of the problem, to no avail yet.

I looked at Jame's Fatdogarm, the arrow keys are working.

One other thing that I have done, is compile Busybox statically. This is required for the recovery snapshot mechanism. I posted about it here:
http://barryk.org/news/?viewDetailed=00403
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#33 Post by BarryK »

Another little progress report.

I have got the arrow keys to work.

Well, kind of. The left, right and down keys work, but the up-arrow key launches 01micko's "Screeny" screen capture app.

Up until now, I have stuck with the old 'mouse' and 'keyboard' xorg drivers, instead of 'evdev'.

The reason is, 'evdev' requires udev. the xorg-server uses udev to determine input devices.
However, by using the old mouse and keyboard drivers, these can be "hardcoded" into /etc/X11/xorg.conf or in /etc/X11/xorg.conf.d/, and udev is not needed.

This is if I wanted to build a distro without udev. Which has become just about impossible to do these days.

So, I should go with the flow. 01micko with Slacko Puppy, and jamesbond with Fatdog, have gone over to using evdev for input, and udev for providing all the input info.

So, with Quirky running in my Pi2, I made the required changes. The difference is, as I mentioned above, the arrow keys now work, with that one caveat.

Tomorrow, I will probably put this change permanently into woofQ.

Note, I am still intending to keep a skeleton /etc/X11/xorg.conf, but mouse and keyboard setup will now be in /etc/X11/xorg.conf.d/10-evdev.conf

Scripts that need to modify the mouse or keyboard, such as the keyboard country layout, will operate on the latter file.

I will probably rethink this tomorrow morning.
[url]https://bkhome.org/news/[/url]

User avatar
greengeek
Posts: 5789
Joined: Tue 20 Jul 2010, 09:34
Location: Republic of Novo Zelande

#34 Post by greengeek »

BarryK wrote:but the up-arrow key launches 01micko's "Screeny" screen capture app..
I had a similar issue on a recent slacko (the 32bit one which runs without xorgwizard) and found that the screenshot app was bound to key 111 instead of key 107. I guess this is machine /keyboard specific.

Couldn't figure out why the up arrow key became keycode 111 but didn't look any further at that point - I just used xev to confirm the correct keycode then made the appropriate change to the keybinding in /root/.jwm/jwmrc-personal.

It was a touchscreen dell duo netbook which I havent used with other puppies yet so maybe I should do a bit more testing and see if it has a weird keyboard layout or whether this oddity is related to the fact there is no xorg.conf any more.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#35 Post by don570 »

fonts-freefont-ttf_20120503-1_all.deb needs to be install if
omxplayer shows text subtitles on screen.

Easy to install

https://packages.debian.org/uk/wheezy/a ... f/download

___________________________________________

newest version of pmusic works well.

pmusic 5.2

___________________________________

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#36 Post by BarryK »

greengeek wrote:
BarryK wrote:but the up-arrow key launches 01micko's "Screeny" screen capture app..
I had a similar issue on a recent slacko (the 32bit one which runs without xorgwizard) and found that the screenshot app was bound to key 111 instead of key 107. I guess this is machine /keyboard specific.

Couldn't figure out why the up arrow key became keycode 111 but didn't look any further at that point - I just used xev to confirm the correct keycode then made the appropriate change to the keybinding in /root/.jwm/jwmrc-personal.

It was a touchscreen dell duo netbook which I havent used with other puppies yet so maybe I should do a bit more testing and see if it has a weird keyboard layout or whether this oddity is related to the fact there is no xorg.conf any more.
/root/.jwm/jwmrc-personal has this line:

Code: Select all

<Key keycode="111">exec:screeny</Key>
That file is in the 'jwmconfig2' PET.
So, I guess that I will just remove that line.
[url]https://bkhome.org/news/[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#37 Post by don570 »

Bug report...

I reported this to Zigbert.
http://murga-linux.com/puppy/viewtopic. ... 588#923588

When I tried to install the newest pmusic 5.2 in quirky alpha
I got a warning message that the install didn't succeed.
So I extracted the pet package with uextract and removed the pinstall.sh file
and made my own pet package (dir2pet). This package installed without complaint.

Zigbert says that Barry wrote the pinstall script. Very strange.
What is happening?
__________________________________

Here is the modified pet package that works....
Attachments
pmusic-v7-5.2.0.pet
My package works OK
(160.8 KiB) Downloaded 570 times

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#38 Post by BarryK »

don570 wrote:Bug report...

I reported this to Zigbert.
http://murga-linux.com/puppy/viewtopic. ... 588#923588

When I tried to install the newest pmusic 5.2 in quirky alpha
I got a warning message that the install didn't succeed.
So I extracted the pet package with uextract and removed the pinstall.sh file
and made my own pet package (dir2pet). This package installed without complaint.

Zigbert says that Barry wrote the pinstall script. Very strange.
What is happening?
__________________________________

Here is the modified pet package that works....
Thanks for the report, I'm onto it.

Note, you can install a PET from the commandline. This might help discover any errors. For example:

# petget `pwd`/pmusic-5.2.0.pet

...assuming the terminal is open in same folder as the PET.
...this does exactly what ROX-Filer does, when you click on a PET.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#39 Post by BarryK »

Version 8.0.11 pre-alpha is released, see my blog announcement:

http://barryk.org/news/?viewDetailed=00405
[url]https://bkhome.org/news/[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#40 Post by don570 »

After investigating the bug further...
The error definitely is not the pinstall.sh script.

I came across a similar problem a couple of months ago and reported to
uextract developer

http://murga-linux.com/puppy/viewtopic. ... ced152f2d1

He said the problem was due to an old version of bash 3.0 that BarryK uses,
whereas 01micko and others have moved on to a newer version.
A simple change of a sed command solved the problem.

Code: Select all

petget pmusic-5.2.0.pet

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Here is another pet package that causes the same error message...
It was created in Slacko which is also used by Zigbert. That may be the the culprit
Attachments
wallmaker-1.8.9.3.pet
Causes error message during installation.
(10.26 KiB) Downloaded 570 times
Last edited by don570 on Sat 17 Sep 2016, 16:48, edited 3 times in total.

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#41 Post by don570 »

I noticed that there was a desktop file

/usr/share/applications/mtPaint-snapshot-screen-capture.desktop

but no mtpaintsnapshot.sh

______________________________________

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

close to getting a Nexus 7 to boot maru OS

#42 Post by don570 »

Preetam and Tyler Martin seem close to getting a Nexus 7 to boot maru OS
https://groups.google.com/forum/#!topic ... dT_qHydRXA
However only 2013 Google version of Nexus 7 has a Slimport which is needed to
see the linux screen. Tyler says that android works on his smartphone.
He still needs to boot up the linux kernel.

Tyler Martin
16 Sep (20 hours ago)
That's really weird. They are definitely in vendor/asus folder.

EDIT: Figured it out. device.mk was point to vendor/asus/flo/device-vendor.mk (which doesn't exist) instead of vendor/asus/flo/flo-vendor.mk. I'll have a new build to test tomorrow.
________________________________________________


Also a Sony Xperia Z3 Compact model
https://groups.google.com/forum/#!topic ... jJvMHP-_OI
So it looks like the HDMI monitor was connected successfully over MHL, and Maru responded by trying to start the desktop...but it failed.

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#43 Post by BarryK »

I'm on the track of getting bluetooth working, in the Pi3. Making progress, will report back.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#44 Post by BarryK »

don570 wrote:After investigating the bug further...
The error definitely is not the pinstall.sh script.

I came across a similar problem a couple of months ago and reported to
uextract developer

http://murga-linux.com/puppy/viewtopic. ... ced152f2d1

He said the problem was due to an old version of bash 3.0 that BarryK uses,
whereas 01micko and others have moved on to a newer version.
A simple change of a sed command solved the problem.

Code: Select all

petget pmusic-5.2.0.pet

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Here is another pet package that causes the same error message...
It was created in Slacko which is also used by Zigbert. That may be the the culprit
Ah yes, 01micko now supports xz compressed PET packages in Slacko. Quirky only supports gz compressed PETs.

That's the reason for the failure.

It is on my to-do list, to support xz-compressed PETs, dunno when I'll get around to it though.

Note, Slacko supports both gz and xz PETs, so PET creators probably should stick with gz for support for older pups and derivatives.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#45 Post by BarryK »

I have thrown in a lot more firmware, so users won't have to go hunting for it.

The next release is going to be very interesting, there will be a surprise :o
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#46 Post by BarryK »

BarryK wrote:
don570 wrote:After investigating the bug further...
The error definitely is not the pinstall.sh script.

I came across a similar problem a couple of months ago and reported to
uextract developer

http://murga-linux.com/puppy/viewtopic. ... ced152f2d1

He said the problem was due to an old version of bash 3.0 that BarryK uses,
whereas 01micko and others have moved on to a newer version.
A simple change of a sed command solved the problem.

Code: Select all

petget pmusic-5.2.0.pet

gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Here is another pet package that causes the same error message...
It was created in Slacko which is also used by Zigbert. That may be the the culprit
Ah yes, 01micko now supports xz compressed PET packages in Slacko. Quirky only supports gz compressed PETs.

That's the reason for the failure.

It is on my to-do list, to support xz-compressed PETs, dunno when I'll get around to it though.

Note, Slacko supports both gz and xz PETs, so PET creators probably should stick with gz for support for older pups and derivatives.
OK, this is one of those things I really do need to fix, so I have.

The next release should allow you to install xz-compressed PETs when you click on them.
[url]https://bkhome.org/news/[/url]

User avatar
BarryK
Puppy Master
Posts: 9392
Joined: Mon 09 May 2005, 09:23
Location: Perth, Western Australia
Contact:

#47 Post by BarryK »

don570 wrote:I noticed that there was a desktop file

/usr/share/applications/mtPaint-snapshot-screen-capture.desktop

but no mtpaintsnapshot.sh

______________________________________
Oops. Thanks for that report, now fixed.
[url]https://bkhome.org/news/[/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#48 Post by don570 »

Several times Rox has launched a window with no top menu bar and
the window can't be closed or moved.
I have to relaunch X windows at the start menu to fix the problem.
I never saw this problem in fatdog arm, but the version of rox
in fatdog arm has other bugs.

_______________________________________

cd to / ---> there is a lot of folders beginning with the word 'Debian'
Very strange.

___________________________________________________

Using my raspberry pi2 board I can't make alsamixer or amixer work.
When I try to launch them I get the 'No such file or directory' error.

This makes me think that they were compiled on the wrong platform.
Is the sound chip on the raspberry pi3 board different than the pi2 board??

Retrovol only shows a blank window so it's not useful.

But oddly I can get sound to play by installing my omxplayer 3.7 pet package.
It plays both sound and video files nicely.
I included the free fonts package so that subtitles will show.

download available

http://www.mydrive.ch
User: porteus@don570
Password: porteus

___________________________________________________

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#49 Post by don570 »

I use the HDMI input of my TV set for video. With the default config.txt
file that is supplied I get strange in and out pulses of the video.

So I switch the config.txt file to the same one i use in fatdog arm...
The resolution is small but the screen is stable.

Code: Select all

disable_overscan=0
start_x=1
gpu_mem=128
hdmi_group=1
hdmi_mode=4
# Safest video mode
#hdmi_safe=1

#  If audio stutters uncomment the next line to output sound to stereo jack...
#hdmi_ignore_edid_audio=1

# Berryboot settings, do not change
#initramfs berryboot.img

#[pi2]
#kernel=kernel_rpi2_aufs.img

initramfs initrd.rpi2
[pi2]
kernel=vmlinuz.rpi2

# Warning: CMA does not work properly in newer firmware versions
#
#cma_lwm=16
#cma_hwm=32
#cma_offline_start=16

I need the following line to get clean audio (no stuttering)
hdmi_ignore_edid_audio=1

______________________________________________________

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#50 Post by don570 »

To my surprise I can use my wacom tablet with quirky alpha..

I use the boot manager app to make sure that the wacom driver is loaded

and then set the preferences of mtpaint to control the pressure
(set the pen and pad to 'Screen')

and the pressure of the pen is felt...

I assume that GIMP and Blender can work with my tablet as well.
____________________________________________
Attachments
screenshot-wacom.png
screenshot of mtpaint program
(1.54 KiB) Downloaded 1202 times

Post Reply