Quirky Pyro64 version 0.6 (alpha) -- and Pyro32 0.5

[FeodorF]

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).

[FeodorF]

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.

[FeodorF]

Tried on some laptops
...
Galculator needs libquadmath.so.0
...
.

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/lib64

[L18L]

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"

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"

[FeodorF]

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.

[BarryK]

Thus I wrote

Code: Select all

 Section "Device"
    Identifier "gma500_gfx"
    Driver     "modesetting"
    Option     "SWCursor"       "ON" 
 EndSection
 

to /etc/X11/xorg.conf.d

EDIT: to a new file /etc/X11/xorg.conf.d/20-gpudriver.conf

OK, I will put that in!

[BarryK]

Note, the next build will have fixed galculator, and ddcprobe now present.

[don570]

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

Code: Select all

X

gives me warning about my xorg.conf file needing a fix for screen section
or device section

_______________________________________________________

[L18L]

@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:

I haven't tried modesetting.

Try it please:

Code: Select all

echo ' Section "Device"
    Identifier "i915"
    Driver     "modesetting"
    Option     "SWCursor"       "ON"
 EndSection ' > /etc/X11/xorg.conf.d/20-gpudriver.conf

(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:

Code: Select all

 drm_kms_helper.edid_firmware=edid/1920x1080.bin

to append line of syslinux.cfg

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

Best of luck

[L18L]

Is there any way of removing the top menus in mped text editor
since these are confusing?

It has not at all been possible for me to make any use of mp (in xorgwizard).

Compiled Ye olde Minimum Profit, result:

- Menu is ok

- no unicode (öäüßÄÖÜ° for German, other languages [just es it nl ] will have others)

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

[don570]

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.

_____________________________________________

[L18L]

I can only use mp editor in nox

If I recall correctly I have been using editor vi
(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

[FeodorF]

If anybody needs some screen drivers for further testing of 'pyro64-0.2' you'll find them at: 'Slacko64-6.3.2'

[FeodorF]

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

• 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

[BarryK]

Compiled Ye olde Minimum Profit, result:

- Menu is ok

- no unicode (öäüßÄÖÜ° for German, other languages [just es it nl ] will have others)

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

Version 3.3.18b was the last in the 3.x series. I wonder if that improved unicode support?

[BarryK]

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 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.

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!

[don570]

Version 3.3.18b was the last in the 3.x series. I wonder if that improved unicode support?

It's easy to check if a text editor supports unicode.
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.
___________________________________________________________

[musher0]

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.

[L18L]

Version 3.3.18b was the last in the 3.x series. I wonder if that improved unicode support?

This was the first one I have compiled and checked (Menu items contain utf8).

Then compiled 3.3.17 because you named it in your blog.

Then compiled 5.2.10

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.

No problem here:
Key labelled "Ende" moves cursor to end of line
Key labelled "Pos1" moves cursor to beginning of line
without any configuration, OOTB.

[L18L]

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 did not use that script.
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 poulsbo graphics (gma500) running modesetting driver.

For intel i915 gpu it must stay unchanged or not exist, tested on my 2 boxes.