The time now is Mon 18 Jan 2021, 13:05
All times are UTC - 4 |
Author |
Message |
Sage
Joined: 04 Oct 2005 Posts: 5547 Location: GB
|
Posted: Tue 13 Sep 2016, 03:02 Post subject:
|
|
Quote: | 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!
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Wed 14 Sep 2016, 06:49 Post subject:
|
|
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
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Wed 14 Sep 2016, 10:00 Post subject:
|
|
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.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
greengeek

Joined: 20 Jul 2010 Posts: 5834 Location: Republic of Novo Zelande
|
Posted: Wed 14 Sep 2016, 15:53 Post subject:
|
|
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.
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 5524 Location: Ontario
|
Posted: Wed 14 Sep 2016, 20:37 Post subject:
|
|
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/all/fonts-freefont-ttf/download
___________________________________________
newest version of pmusic works well.
pmusic 5.2
___________________________________
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Thu 15 Sep 2016, 06:18 Post subject:
|
|
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: | <Key keycode="111">exec:screeny</Key> |
That file is in the 'jwmconfig2' PET.
So, I guess that I will just remove that line.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 5524 Location: Ontario
|
Posted: Thu 15 Sep 2016, 18:15 Post subject:
|
|
Bug report...
I reported this to Zigbert.
http://murga-linux.com/puppy/viewtopic.php?p=923588#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....
Description |
My package works OK
|

Download |
Filename |
pmusic-v7-5.2.0.pet |
Filesize |
160.8 KB |
Downloaded |
641 Time(s) |
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Thu 15 Sep 2016, 20:10 Post subject:
|
|
don570 wrote: | Bug report...
I reported this to Zigbert.
http://murga-linux.com/puppy/viewtopic.php?p=923588#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.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Fri 16 Sep 2016, 21:00 Post subject:
|
|
Version 8.0.11 pre-alpha is released, see my blog announcement:
http://barryk.org/news/?viewDetailed=00405
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 5524 Location: Ontario
|
Posted: Sat 17 Sep 2016, 12:35 Post subject:
|
|
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.php?p=917998&sid=e74165695afcf39f9d9a97ced152f2d1
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: | 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
Description |
Causes error message during installation.
|

Download |
Filename |
wallmaker-1.8.9.3.pet |
Filesize |
10.26 KB |
Downloaded |
652 Time(s) |
Last edited by don570 on Sat 17 Sep 2016, 12:48; edited 3 times in total
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 5524 Location: Ontario
|
Posted: Sat 17 Sep 2016, 12:41 Post subject:
|
|
I noticed that there was a desktop file
/usr/share/applications/mtPaint-snapshot-screen-capture.desktop
but no mtpaintsnapshot.sh
______________________________________
|
Back to top
|
|
 |
don570

Joined: 10 Mar 2010 Posts: 5524 Location: Ontario
|
Posted: Sat 17 Sep 2016, 14:05 Post subject:
close to getting a Nexus 7 to boot maru OS |
|
Preetam and Tyler Martin seem close to getting a Nexus 7 to boot maru OS
https://groups.google.com/forum/#!topic/maru-os-dev/zdT_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.
Quote: | 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/maru-os-dev/tjJvMHP-_OI
Quote: |
So it looks like the HDMI monitor was connected successfully over MHL, and Maru responded by trying to start the desktop...but it failed. |
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Sat 17 Sep 2016, 22:23 Post subject:
|
|
I'm on the track of getting bluetooth working, in the Pi3. Making progress, will report back.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Sat 17 Sep 2016, 22:26 Post subject:
|
|
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.php?p=917998&sid=e74165695afcf39f9d9a97ced152f2d1
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: | 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.
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 9400 Location: Perth, Western Australia
|
Posted: Mon 19 Sep 2016, 04:56 Post subject:
|
|
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
_________________ https://bkhome.org/news/
|
Back to top
|
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|