Quirky Pyro64 version 0.6 (alpha) -- and Pyro32 0.5
Success!
Used the 4install-Quirky-to-partition script and the pyro64-0.2.usfs.xz file.
Superb script Barry!
Had to add the wifi file: /lib/firmware/rtlwifi/rtl8712u.bin
I used the rtl8712u.bin from slacko64-6.3.2-uefi.iso (zdrv_slacko64_6.3.2.sfs).
Used the 4install-Quirky-to-partition script and the pyro64-0.2.usfs.xz file.
Superb script Barry!
Had to add the wifi file: /lib/firmware/rtlwifi/rtl8712u.bin
I used the rtl8712u.bin from slacko64-6.3.2-uefi.iso (zdrv_slacko64_6.3.2.sfs).
- Attachments
-
- Pyro64.png
- (71.01 KiB) Downloaded 691 times
Success!
Did a 4install-Quirky-to-partition again.
Used the xorg.conf and xorg.conf.Intel_r_Eaglelake_Graphics_ChipX203H from my Xerus64-8.0.0 built to make it work.
Did a 4install-Quirky-to-partition again.
Used the xorg.conf and xorg.conf.Intel_r_Eaglelake_Graphics_ChipX203H from my Xerus64-8.0.0 built to make it work.
- Attachments
-
- Pyro64.png
- (59.04 KiB) Downloaded 682 times
To fix the 'galculator' problem, you can grab the 64-bit libquadmath.so from Slacko64-6.3.2.-uefi.iso at: puppy_slacko64_6.3.2.sfs /usr/lib64Philh wrote:Tried on some laptops
...
Galculator needs libquadmath.so.0
...
.
- Attachments
-
- libquadmath-64bit.png
- (4.48 KiB) Downloaded 609 times
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Quirky Pyro64 version 0.2 (alpha)
Getting accelerated graphics with modesetting driver
My first attempts have resulted in:Direct Rendering Yes
Note the correction in my post as for adding file 20-gpudriver.conf please.
Next installation on another USB stick I have copied ddcprobe first of all, resulted in DIRCT RENDERING No
A miracle...
Repeated installation
changed resolution manually in xorg.conf
Got a running X system with DIRCT RENDERING No
Then copied ddcprobe and used xorgwizard again choosing modesetting.
It is Direct Rendering Yes
Thought I share this.....
EDIT
...and no changes made in xorg.conf for "glx" and "dri"
My first attempts have resulted in:Direct Rendering Yes
Note the correction in my post as for adding file 20-gpudriver.conf please.
Next installation on another USB stick I have copied ddcprobe first of all, resulted in DIRCT RENDERING No
A miracle...
Repeated installation
changed resolution manually in xorg.conf
Got a running X system with DIRCT RENDERING No
Then copied ddcprobe and used xorgwizard again choosing modesetting.
It is Direct Rendering Yes
Thought I share this.....
EDIT
...and no changes made in xorg.conf for "glx" and "dri"
Code: Select all
# This loads the GLX module (if present). xorg 7.4/5 need explicit disable to disable...
# Disable "glx" #LOADGLX
# This loads dri module (if present). 7.4 loads it by default, have to disable...
# Load "dri" #LOADDRI
# Disable "dri"
- Attachments
-
- capture22298.png
- (22.03 KiB) Downloaded 584 times
Success!
Found an old ext2 formated usb stick with about 7.6 usable GBs left.
Did a 4install-Quirky-to-partition with the pyro64-0.2.usfs.xz file once more.
To make it boot I used Grub4dos from a Precise Puppy 5.7.1.iso cd.
Added 'ddcprobe' as advised by L18L.
Found an old ext2 formated usb stick with about 7.6 usable GBs left.
Did a 4install-Quirky-to-partition with the pyro64-0.2.usfs.xz file once more.
To make it boot I used Grub4dos from a Precise Puppy 5.7.1.iso cd.
Added 'ddcprobe' as advised by L18L.
- Attachments
-
- usb-ext2.png
- (55.52 KiB) Downloaded 558 times
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Quirky Pyro64 version 0.2 (alpha)
OK, I will put that in!L18L wrote: Thus I wroteto /etc/X11/xorg.conf.dCode: Select all
Section "Device" Identifier "gma500_gfx" Driver "modesetting" Option "SWCursor" "ON" EndSection
EDIT: to a new file /etc/X11/xorg.conf.d/20-gpudriver.conf
[url]https://bkhome.org/news/[/url]
Added 'ddcprobe' as advised by L18L
This gave the correct resolution of my monitor on xorgwizard list
however I still can't get to disktop
Typing in console
gives me warning about my xorg.conf file needing a fix for screen section
or device section
_______________________________________________________
This gave the correct resolution of my monitor on xorgwizard list
however I still can't get to disktop
Typing in console
Code: Select all
X
or device section
_______________________________________________________
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
@don570, I did not find anything on the web ("no screens found" gpudriver) to solve your special problem with screen..
Thus only some "wild guesses" for you: (i915 should be your gpu)
You might change "modesetting" to "intel" or "i915" ?
________________
EDIT (May, 28)
No, Identifier has to stay "gma500_gfx"
or
no 20-gpudriver at all for intel i915 gpu
________________
maybe also append:
to append line of syslinux.cfg
and/or add/change your modeline "1920x1080" in xorg.conf.
FYI: tail of my xorg.conf:
Best of luck
Thus only some "wild guesses" for you:
Try it please:I haven't tried modesetting.
Code: Select all
echo ' Section "Device"
Identifier "i915"
Driver "modesetting"
Option "SWCursor" "ON"
EndSection ' > /etc/X11/xorg.conf.d/20-gpudriver.conf
You might change "modesetting" to "intel" or "i915" ?
________________
EDIT (May, 28)
No, Identifier has to stay "gma500_gfx"
or
no 20-gpudriver at all for intel i915 gpu
________________
maybe also append:
Code: Select all
drm_kms_helper.edid_firmware=edid/1920x1080.bin
and/or add/change your modeline "1920x1080" in xorg.conf.
FYI: tail of my xorg.conf:
Code: Select all
#everything past here is auto-generated by Puppy's Xorg Wizard...
Section "ServerLayout"
Identifier "Default Layout"
Screen "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
VertRefresh 59-76
Option "PreferredMode" "1920x1080"
EndSection
Section "Modes"
Identifier "Modes0"
EndSection
Section "Device"
Identifier "card0"
Driver "modesetting" #card0driver
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1920x1080"
EndSubsection
EndSection
#PuppyHardwareProfile=Intel_R_XX_Graphics_ChipsetLSL3230T
Last edited by L18L on Sun 28 May 2017, 09:45, edited 1 time in total.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Ye olde Minimum Profit
It has not at all been possible for me to make any use of mp (in xorgwizard).don570 wrote:Is there any way of removing the top menus in mped text editor
since these are confusing?
Compiled Ye olde Minimum Profit, result:
- Menu is ok
- no unicode (öäüßÄÖÜ° for German, other languages [just es it nl ] will have others)
mp-3.3.17/TODO wrote:Pending Enhancements
--------------------
* 1007: Add Unicode support.
EDIT
mp-5.2.10 ' s TODO contains:
Code: Select all
Closed
----------
* 1276: Fix win32 processing of Unicode characters
(Mon, 27 Jul 2009 16:52:20 +0200).
Wait and see..
EDIT ...2 minutes later
SUCCESS
see capture2630
- Attachments
-
- capture4342.png
- no unicode
äöüäöüẞ - (16.53 KiB) Downloaded 417 times
-
- capture2630.png
- has unicode
- (33.52 KiB) Downloaded 412 times
mp in repository
I can only use mp editor in nox
version 3.2.13 is old so it supports only ascii characters.
http://distro.ibiblio.org/quirky/quirky ... -64.tar.xz
____________________________________
nano when it compiled for minimum size only supports ascii characters too.
_____________________________________________
version 3.2.13 is old so it supports only ascii characters.
http://distro.ibiblio.org/quirky/quirky ... -64.tar.xz
____________________________________
nano when it compiled for minimum size only supports ascii characters too.
_____________________________________________
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: mp in repository
If I recall correctly I have been using editor vidon570 wrote:I can only use mp editor in nox
(write: "esc : w") (quit: "esc : q")
My intel experience
My Pyro64 is on 8G USB stick
I have put it into my other box Acer Aspire R3-131T
Booted to command line
launched xorgwizard
chose intel ...
..and got a graphical desktop (1366x768) on that computer
drm_kms_helper did not hurt
unchanged 20-gpudriver.conf did not hurt
I like Quirky Pyro64
If anybody needs some screen drivers for further testing of 'pyro64-0.2' you'll find them at: 'Slacko64-6.3.2'
- Attachments
-
- drivers.list.png
- (29.47 KiB) Downloaded 534 times
Success!
Adding direct rendering to pyro64-0.2:
Slacko64-6.3.2.sfs/usr/lib64/libGLEW.so.1.9.0
Slacko64-6.3.2.sfs/usr/bin/glxinfo
Slacko64-6.3.2.sfs/usr/bin/glxgears
Adding direct rendering to pyro64-0.2:
Slacko64-6.3.2.sfs/usr/lib64/libGLEW.so.1.9.0
Slacko64-6.3.2.sfs/usr/bin/glxinfo
Slacko64-6.3.2.sfs/usr/bin/glxgears
- f.e. /usr/bin/glxinfo
...
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) 965Q
OpenGL version string: 2.1 Mesa 17.0.2
OpenGL shading language version string: 1.20
...
- Section "Device"
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "Accel" # [<bool>]
#Option "AccelMethod" # <str>
#Option "Backlight" # <str>
#Option "CustomEDID" # <str>
Option "DRI" # <str>
#Option "Present" # [<bool>]
#Option "ColorKey" # <i>
#Option "VideoKey" # <i>
#Option "Tiling" # [<bool>]
#Option "LinearFramebuffer" # [<bool>]
#Option "HWRotation" # [<bool>]
#Option "VSync" # [<bool>]
#Option "PageFlip" # [<bool>]
#Option "SwapbuffersWait" # [<bool>]
#Option "TripleBuffer" # [<bool>]
#Option "XvPreferOverlay" # [<bool>]
#Option "HotPlug" # [<bool>]
#Option "ReprobeOutputs" # [<bool>]
#Option "XvMC" # [<bool>]
#Option "ZaphodHeads" # <str>
#Option "VirtualHeads" # <i>
#Option "TearFree" # [<bool>]
#Option "PerCrtcPixmaps" # [<bool>]
Identifier "card0"
Driver "intel" #card0driver
EndSection
- Attachments
-
- IntelDRI.png
- (27.49 KiB) Downloaded 484 times
-
- GLXinfo.png
- (4.27 KiB) Downloaded 497 times
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Ye olde Minimum Profit
Version 3.3.18b was the last in the 3.x series. I wonder if that improved unicode support?L18L wrote:don570 wrote:Compiled Ye olde Minimum Profit, result:
- Menu is ok
- no unicode (öäüßÄÖÜ° for German, other languages [just es it nl ] will have others)mp-3.3.17/TODO wrote:Pending Enhancements
--------------------
* 1007: Add Unicode support.
EDIT
mp-5.2.10 ' s TODO contains:Code: Select all
Closed ---------- * 1276: Fix win32 processing of Unicode characters (Mon, 27 Jul 2009 16:52:20 +0200).
Wait and see..
EDIT ...2 minutes later
SUCCESS
see capture2630
[url]https://bkhome.org/news/[/url]
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Re: Ye olde Minimum Profit
The reason that I did not use that version, is could not figure out how to fix the <home> and <end> keys. They did not move the cursor to beginning and end of a line.L18L wrote:mp-5.2.10 ' s TODO contains:Code: Select all
Closed ---------- * 1276: Fix win32 processing of Unicode characters (Mon, 27 Jul 2009 16:52:20 +0200).
Wait and see..
EDIT ...2 minutes later
SUCCESS
The 5.x series does not use /etc/mprc or ~/.mprc, has some other way of configuring.
L18L, if you can solve that one, I will definitely consider moving to 5.2.10!
[url]https://bkhome.org/news/[/url]
It's easy to check if a text editor supports unicode.Version 3.3.18b was the last in the 3.x series. I wonder if that improved unicode support?
Just create a UTF-8 text file with strange foreign characters inside.
Then open the file with your text editor and
see if the foreign characters (such as öäüßÄÖÜ°) show in the window.
Compile with source...
http://distro.ibiblio.org/quirky/quirky ... 18b.tar.gz
______________________________________________
I did a full install of pyro to a partition using Barry's script,
but still getting message that Screen section of my xorg.conf
is not correct whereas xorgwizard message says everything is fine.
___________________________________________________________
Hello all.
Perhaps try Joe's Own Editor instead?
I've been using it for a few years on various Puppies and I never had a
UTF-8 problem with it, in or out of Xorg.
It's been around since 1988, development is still active, and it's almost
as powerful as geany.
Best regards.
Perhaps try Joe's Own Editor instead?
I've been using it for a few years on various Puppies and I never had a
UTF-8 problem with it, in or out of Xorg.
It's been around since 1988, development is still active, and it's almost
as powerful as geany.
Best regards.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: Ye olde Minimum Profit
This was the first one I have compiled and checked (Menu items contain utf8).BarryK wrote:Version 3.3.18b was the last in the 3.x series. I wonder if that improved unicode support?
Then compiled 3.3.17 because you named it in your blog.
Then compiled 5.2.10
No problem here:The reason that I did not use that version, is could not figure out how to fix the <home> and <end> keys. They did not move the cursor to beginning and end of a line.
Key labelled "Ende" moves cursor to end of line
Key labelled "Pos1" moves cursor to beginning of line
without any configuration, OOTB.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
dri for intel i915 and gma500
I did not use that script.don570 wrote:I did a full install of pyro to a partition using Barry's script,
but still getting message that Screen section of my xorg.conf
is not correct whereas xorgwizard message says everything is fine.
I have been using:
Code: Select all
xz --decompress --stdout pyro64-0.2-8gb.img.xz > /dev/sdb
sync
Result of latest experiment:
/etc/X11/xorg.conf.d/20-gpudriver.conf must be and stay
Code: Select all
Section "Device"
Identifier "gma500_gfx"
Driver "modesetting"
Option "SWCursor" "ON"
EndSection
For intel i915 gpu it must stay unchanged or not exist, tested on my 2 boxes.