Quirky Pyro64 version 0.6 (alpha) -- and Pyro32 0.5
upnorth
See here:
http://murga-linux.com/puppy/viewtopic. ... &start=150
then follow link to goingnut's post.
See here:
http://murga-linux.com/puppy/viewtopic. ... &start=150
then follow link to goingnut's post.
Tried pyro64-0.5 on a stick on a dell optiplex 755 that usually works 64bit ok.
Tried it once and tried setting the alsa up with no result so started it again. Again after booting :-
1/ no sound on startup: sound was turned off and I turned it on: tried 2 barks again with no differance.
2/ tried a av dvd and nothing happened so I looked around and found this in the /tmp/xerrs.log file.
Lines 23 to 31 are from 2barks
Lines 32 to 34 relate to trying the dvd
---------------------------------
X.Org X Server 1.19.1
Release Date: 2017-01-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.11.12 x86_64
Current Operating System: Linux pyro-05-1 4.13.9 #1 SMP Sun Oct 22 22:28:32 AWST 2017 x86_64
Kernel command line: root=PARTUUID=fc67e7dd-02 rootwait rw BOOT_IMAGE=vmlinuz
Build Date: 26 October 2017 10:35:16PM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 2 18:42:20 2017
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/usr/bin/jwm
EXIT="Exit on timeout"
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
vo_vdpau: Failed to check vdpau get/put bits native capability : VDP_STATUS_NO_IMPLEMENTATION
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
/usr/sbin/pmount: line 306: 8040 Terminated yaf-splash -bg orange -fg black -close never -fontsize large -text "$(gettext 'Please wait, probing hardware...')"
mount-FULL: /dev/sr0 is write-protected, mounting read-only
/usr/sbin/pmount: line 307: 8959 Terminated yaf-splash -bg orange -fg black -close never -fontsize large -text "$(gettext 'Please wait, probing hardware...')"
--------------------------------
so somethings missing somewhere
regards
Tried it once and tried setting the alsa up with no result so started it again. Again after booting :-
1/ no sound on startup: sound was turned off and I turned it on: tried 2 barks again with no differance.
2/ tried a av dvd and nothing happened so I looked around and found this in the /tmp/xerrs.log file.
Lines 23 to 31 are from 2barks
Lines 32 to 34 relate to trying the dvd
---------------------------------
X.Org X Server 1.19.1
Release Date: 2017-01-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.11.12 x86_64
Current Operating System: Linux pyro-05-1 4.13.9 #1 SMP Sun Oct 22 22:28:32 AWST 2017 x86_64
Kernel command line: root=PARTUUID=fc67e7dd-02 rootwait rw BOOT_IMAGE=vmlinuz
Build Date: 26 October 2017 10:35:16PM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov 2 18:42:20 2017
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/usr/bin/jwm
EXIT="Exit on timeout"
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
vo_vdpau: Failed to check vdpau get/put bits native capability : VDP_STATUS_NO_IMPLEMENTATION
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/i915_drv_video.so
libva info: va_openDriver() returns -1
/usr/sbin/pmount: line 306: 8040 Terminated yaf-splash -bg orange -fg black -close never -fontsize large -text "$(gettext 'Please wait, probing hardware...')"
mount-FULL: /dev/sr0 is write-protected, mounting read-only
/usr/sbin/pmount: line 307: 8959 Terminated yaf-splash -bg orange -fg black -close never -fontsize large -text "$(gettext 'Please wait, probing hardware...')"
--------------------------------
so somethings missing somewhere
regards
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
scsijon,scsijon wrote:Tried pyro64-0.5 on a stick on a dell optiplex 755 that usually works 64bit ok.
I think you mentioned that you have a PC with 32-bit UEFI, and 64-bit CPU.
The Pyro64 0.5 8GB image file has rEFInd, with both 32-bit and 64-bit bootloaders in it.
Would you mind writing that image to a 8GB stick and test if it boots on a 32-bit UEFI -- proper UEFI boot, not legacy-mode.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Guys,
Thanks for all the testing. I haven't had time to read the posts in detail since 0.5 released, but will do so soon.
Right now, I am doing a 32-bit x86 compile, i686, in OE. It has almost finished, and only 'arp-scan' and 'xine-ui' have failed -- I will just compile those in a running Pyro32 and create PETs.
So, expect a i686 Pyro32 soon. It is splitting my workload too much though, so might not be able to give it much attention to fix bugs -- except for bugs that are common to Pyro64.
Changing the subject, has anyone explored what's in the Package Manager, in "compat-oe" repo? All sorts of packages have been compiled in OE and are available for installation. There's gimp, firefox, mariabd, for example.
Thanks for all the testing. I haven't had time to read the posts in detail since 0.5 released, but will do so soon.
Right now, I am doing a 32-bit x86 compile, i686, in OE. It has almost finished, and only 'arp-scan' and 'xine-ui' have failed -- I will just compile those in a running Pyro32 and create PETs.
So, expect a i686 Pyro32 soon. It is splitting my workload too much though, so might not be able to give it much attention to fix bugs -- except for bugs that are common to Pyro64.
Changing the subject, has anyone explored what's in the Package Manager, in "compat-oe" repo? All sorts of packages have been compiled in OE and are available for installation. There's gimp, firefox, mariabd, for example.
[url]https://bkhome.org/news/[/url]
Yep, easy done. This should be ok as I have one of the new S.... 16gig sticks with both usb3 and micro-usb plugs in one (one each end). I will have a go tomorrow evening and let you know the results.BarryK wrote:scsijon,scsijon wrote:Tried pyro64-0.5 on a stick on a dell optiplex 755 that usually works 64bit ok.
I think you mentioned that you have a PC with 32-bit UEFI, and 64-bit CPU.
The Pyro64 0.5 8GB image file has rEFInd, with both 32-bit and 64-bit bootloaders in it.
Would you mind writing that image to a 8GB stick and test if it boots on a 32-bit UEFI -- proper UEFI boot, not legacy-mode.
By the way, even with the latest machines I played with in adelaide (loved the new B3 grapics drawing screen but not the price), they just don't have seem to have added booting from the microsd, but on some you can boot with a full size sd card in an external dongle, go figure.
regards
32bit uefi test
Sorry,BarryK wrote:
scsijon,
I think you mentioned that you have a PC with 32-bit UEFI, and 64-bit CPU.
The Pyro64 0.5 8GB image file has rEFInd, with both 32-bit and 64-bit bootloaders in it.
Would you mind writing that image to a 8GB stick and test if it boots on a 32-bit UEFI -- proper UEFI boot, not legacy-mode.
Tried, but it failed after the menu autostarted with:-
Quirky Linux - Booting OS
Starting vmlinuz
Using load options 'root-PARTUUID=fc67e7dd-02 rootwait rw'
Invalid loader file!
Error: Not Found while loading vmlinuz
"hit any key to continue"
and that was all it said,
And with a check the partuuid is correct so that is not the problem.
Tried adding qfix=nox etc and a few of your other tricks from the past, but of course as it can't find a usefull loader it just bombs.
Let me know if you have any ideas to try, i'll monitor this thread.
EDIT1: woke up with a thought to try, so tried copying the 32bit BOOTIA eufi file from sdb1 to sdb2/boot but no change, it's definately going to sdb2/boot though as it's picking that menu and not sdb1's. Also tried putting the partuuid in the sdb2/boot/ config file but that also did nothing. back to bed, mowing tomorrow the grass is too long.
Last edited by scsijon on Sat 04 Nov 2017, 16:33, edited 1 time in total.
Quirky Pyro64 version 0.5 (alpha), Oct 28, 2017
I used easydd utility to install Pyro64 to a 16gb SDHC card for use on
my Lenovo Thinkcentre.
Now have EasyOS on 32gb SDHC card plugged into usb card reader plugged into
usb 2.0 port on the back of the computer.
Pyro64 on 16gb SDHC card plugged into usb card reader plugged onto usb
2.0 on the front of the computer.
Xubuntu 17.10 64 installed to the hard drive.
my Lenovo Thinkcentre.
Now have EasyOS on 32gb SDHC card plugged into usb card reader plugged into
usb 2.0 port on the back of the computer.
Pyro64 on 16gb SDHC card plugged into usb card reader plugged onto usb
2.0 on the front of the computer.
Xubuntu 17.10 64 installed to the hard drive.
- Attachments
-
- screenshot.jpg
- (45.44 KiB) Downloaded 329 times
The 'defaultfilemanager' file is needed as well.The "Show location" option when right clicking an item in the pFind search results does not function
_____________________________________________
Gimp should be upgraded to version gimp-2.8.22
_______________________________________
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
A 32-build of Quirky Pyro!
It is version 0.5, and has the same bugs as the Pyro64 0.5.
Announcement, release notes, download:
http://bkhome.org/news/201711/quirky-py ... eased.html
It is version 0.5, and has the same bugs as the Pyro64 0.5.
Announcement, release notes, download:
http://bkhome.org/news/201711/quirky-py ... eased.html
[url]https://bkhome.org/news/[/url]
-
- Posts: 247
- Joined: Fri 31 Jan 2014, 14:12
Obese QP32
C'mon Barry, QP32 is 459Mb, that's an hour and a quarter for
me to download on adsl copper line from my local exchange.
Can't you go back to the days when you strived to
get under 100Mb, as in lean'n mean.
Please strip out all the unnecessary bloat and give us minnows
a well-earned break.
Thanks, regards.
me to download on adsl copper line from my local exchange.
Can't you go back to the days when you strived to
get under 100Mb, as in lean'n mean.
Please strip out all the unnecessary bloat and give us minnows
a well-earned break.
Thanks, regards.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Obese QP32
These days, almost half of that 459MB is drivers and firmware. A lot of the drivers would be for newer hardware.Rodney Byne wrote:C'mon Barry, QP32 is 459Mb, that's an hour and a quarter for
me to download on adsl copper line from my local exchange.
Can't you go back to the days when you strived to
get under 100Mb, as in lean'n mean.
Please strip out all the unnecessary bloat and give us minnows
a well-earned break.
Thanks, regards.
Yes, libreoffice could be replaced by abiword and gnumeric.
Could cut down the drivers and use lighter apps, remove some extra apps, but I doubt whether I could get it under 200MB though.
EDIT
Hey, hold on, where does that 459MB come from? The QP32 iso is 362MB, the .xz file is 293MB.
Last edited by BarryK on Mon 06 Nov 2017, 23:13, edited 1 time in total.
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Yes, I was able to confirm this bug! Fixed, see my blog post:upnorth wrote:running xcalc causes a drop out of x to a console window.
managed to get this when using a startup option in terminal:
Warning: Cannot convert string "calculator" to type Pixmap
http://bkhome.org/news/201711/xcalc-crash-fixed.html
[url]https://bkhome.org/news/[/url]
Indeed. Rodney makes an important point. For all the old fully working 32bit 'junk' that the majority of W+D prefers/forced to use, all that stuff for 'newer hardware' plastic tat, go-faster stripes & co. is unnecessary. The rich spoilt brats will bleat , of course, but the less well-endowed might well wish to advise them where to stick their flashing lights. 200Mb might well be acceptable?almost half of that 459MB is drivers and firmware. A lot of the drivers would be for newer hardware.
There really isn't any market for those nasty revenue-generating flimsy laptops, with their limited ports & other HW shortcomings. Clued-up folks, notably the younger set, use their Android (hopefully not the posers favourite!) smart mobiles, knowing that they can wi-fi it to a static TV, an hi-fi sound system, w.h.y. when the occasion demands. For retirees, cash-strappped and other less mobile operators, there's nothing to beat the tin box under the desk, wired NIC, running in 32bit...
But thanks a bunch anyway for Pyro32 and for humouring the rest of us.
May we all remember the good engineer's mantra: K.I.S.S.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Ah, yes, woof-CE has added more of those default* thingies:don570 wrote:The 'defaultfilemanager' file is needed as well.The "Show location" option when right clicking an item in the pFind search results does not function
https://github.com/puppylinux-woof-CE/w ... /local/bin
Well, I haven't added all of those, just added defaultfilemanager to those in woofQ.
With that file in /usr/local/bin, "Show Location" works. You have to highlight a file first, by clicking on it, then do a right-click.
[url]https://bkhome.org/news/[/url]
Re: Taking it for a spin...
Hi @Barry,
fsck was not working for f2fs on reboot or demand so..
fsck.f2fs was missing from Easy's /bin. and
modified sbin/fscheck as:
#GC f2fs
if [ "${DEV1FS}" == "f2fs" ]; then
echo "hey..a f2fs.. cool cleaning.."
fsck.f2fs -a -f /dev/${PDEV1}
else
e2fsck -p -f /dev/${PDEV1}
fi
#GC f2fs
gcav
fsck was not working for f2fs on reboot or demand so..
fsck.f2fs was missing from Easy's /bin. and
modified sbin/fscheck as:
#GC f2fs
if [ "${DEV1FS}" == "f2fs" ]; then
echo "hey..a f2fs.. cool cleaning.."
fsck.f2fs -a -f /dev/${PDEV1}
else
e2fsck -p -f /dev/${PDEV1}
fi
#GC f2fs
gcav