(old)Puppy Linux Discussion Forum

# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2

Chip description:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series]
Display controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series] (Secondary)

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): ati
Loaded modules: dbe dri2 exa extmod fb fbdevhw glx kbd mouse radeon ramdac

Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
326 frames in 5.0 seconds = 65.138 FPS
376 frames in 5.0 seconds = 75.029 FPS
376 frames in 5.0 seconds = 75.030 FPS
376 frames in 5.0 seconds = 75.026 FPS
376 frames in 5.0 seconds = 75.032 FPS

-Computer-
Processor : AMD Athlon(tm) 64 Processor 3400+
Memory : 967MB (205MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Fri 30 Aug 2013 01:29:06 AM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on ATI RS480
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ATIIXP - ATI IXP

Two questions to do with the default version of jwm:
1) How do I tell which version of jwm is installed?
2) It seems that this version of jwm does not allow windows to maximise or open up any bigger than the actual desktop size (which might seem practical, but is different to what I have experienced on other puppies). This is problematic on my netbook because some large dialog windows are taller than my 1024x600 screen, and have to be manually dragged upwards and the manually resized by grabbing the bottom right corner then dragged up again before i can see the buttons at the bottom of the dialog window.
Is this behaviour able to be changed by some setting within jwm?
On other puppies the window manager seems to allow the same dialogs to open up (or be maximised to...) full window height (even if that is bigger than desktop size) and all i need to do is to drag the window upwards and I can see the buttons without resizing.

The pic shows an example of a dialog window that becomes truncated and distorted by being forced to fit between the top of the screen and the jwm tray (I could set the tray to auto hide and that does give some benefit, but still does not allow the window to be any bigger than the bottom of the screen). I really want to allow the dialogs to default to their normal native size.

Hi,

jwm -h when typed in your terminal will show your JWM version.

If you visit Joe's Change Log I vaguely recall v 851 (or other recent change) refers to your second item.

My regards

Greengeek wrote:
> The pic shows an example of a dialog window that becomes truncated and distorted by being forced to fit between the top of the screen

Yeah the GTK dialog does that. That's why I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.

Or the GTK programmer should have calculated the Height and Width of the window as a proportion : (H-50)x(w-50) or something like that, instead of a predefined HxW. The H and W of a screen can be extracted as variables from /etc/xorg.conf and then processed with the expr utility. It's a little work, but it's not hard to do.

BFN.

musher0

Please disregard ... I deleted the savefile, rebooted, & created a new one ... all is well.

Fresh manual frugal install and all is well.

# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2

Chip description:
VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
Depth (bits, or planes): 24
Modules requested to be loaded: dbe

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb fbdevhw glx kbd mouse shadowfb

Actual rendering on monitor:
Resolution: 1440x900 pixels (380x238 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video
# glxgears
1156 frames in 5.0 seconds = 231.026 FPS
1342 frames in 5.0 seconds = 268.347 FPS
1354 frames in 5.0 seconds = 270.615 FPS
1330 frames in 5.0 seconds = 265.875 FPS
1355 frames in 5.0 seconds = 270.978 FPS

-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 3373MB (220MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Sat 31 Aug 2013 02:17:09 AM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
EDIT:
Added screenshot.

Jasper wrote:jwm -h when typed in your terminal will show your JWM version.
If you visit Joe's Change Log I vaguely recall v 851 (or other recent change) refers to your second item.

Thanks Jasper. That command shows that UpupRaring3992 has jwm 835 so I decided to "borrow" a jwm from a different puppy and it has solved my problem.

I wasn't sure of the proper way to do this, but I just grabbed the /usr/bin/jwm file from a Puppy MagooV6 install (seems to be jwm version 574) and copied it into UpupRaring instead of the default file. (It sounds like a major step backwards to go from 835 to 574, but I can't figure out the changelog info to decide which versions are the best so I'm just happy that it has cured my problem anyway).

musher0 wrote:Yeah the GTK dialog does that. That's why I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.

What is "less"?. Is that something like yad?

Here is jwm binary version 855.
The pet installs just /usr/bin/jwm binary.

To test with small resolution problems.

greengeek wrote:

musher0 wrote:...
I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.

What is "less"?

http://linux.die.net/man/1/less

pemasu wrote:Here is jwm binary version 855.
To test with small resolution problems.

Thanks Pemasu. I tried the 855 pet but it has not changed the symptom unfortunately. It seems like Joe Wing has been making some changes to jwm to make various oversized dialog windows fit into the smaller resolution but I think it just makes some of the window layouts become distorted. The recent changes seem to have been good for Abiword dialogs though - they do seem to fit better.

I will stick with 574 for now, even though this older version does allow some of the Abiword dialogs to be offscreen and oversized, but will try to find some other jwm versions aswell and see if I can hit on one that is best overall.

In my particular modified 3992 puplet (switchpup) it is easier for me to "drag" an oversized window than to go through the extra steps required by the smaller yet distorted window.

Comparison of 574 and 855 below:

Greengeek. Joe Wing reads his mail. You could post to him your expriments with problem report. For example by pointing to your posts.
Just right click the Posted icon and copy the url link.

http://joewing.net/projects/jwm/
joewing@joewing.net

http://murga-linux.com/puppy/viewtopic. ... 045#723045

People with those small resolution netbooks etc are best to test the changes in different jwm versions. I dont have small size laptops. Only 15.6 ".

cinclus_cinclus wrote:

greengeek wrote:

musher0 wrote:...
I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.

What is "less"?

http://linux.die.net/man/1/less

Thanks for the reference, cinclus_cinclus.

@greengeek:

You'll find the latest version of less at http://www.greenwoodsoftware.com/less/.

Less is a console text reader, like cat or more. But much more powerful. For ex.,

• it can also be used as a launcher.
  Or you can ask it to highlight some text.
  You can have it display a footer if you need to.
  You can display the text it carries in a regular X-window through a command such as

  Code: Select all

  urxvt [some urxvt parameters] -e less [some less paramaters] text.txt

  You can then trigger that reader script with a right-click on a lot of document and text files.
  It can read some executable codes, at least the text part, which most text editors can't do.
  You can hook it up to an editor to help you review your editing / writing as you go.
  It also has a couple of plugins that allow you to read html, doc or rtf files, or the contents of an archive.

I could go on.

From what I know of yad, it's a X-dialog kind of program. It shows user options and command buttons in a graphic environment.

Less is completely different. It's a console app, but it's very adaptable and very rich in features.

BFN.

musher0

a few backgrounds.

Hi,
just for information...
here have made a «skizofrenic» wheezy-raring putting the raring-3.9.9.2 kernel in place of the wheezys ones ... seems working ok so far ...
cheers, charlie

charlie6 wrote:Hi,
just for information...
here have made a «skizofrenic» wheezy-raring putting the raring-3.9.9.2 kernel in place of the wheezys ones ... seems working ok so far ...
cheers, charlie

Was there a strategic advantage to this - or was it just to see if you could?

Have you tried loading any new apps to see what happens?

gtk-3 all programs can not use X Input Method
abiword and Gnumeric can not enter CJK

gtk-3 all programs can not use X Input Method
abiword and Gnumeric can not enter CJK

.

Careful, there, JamesC. People may think you're a lewd penguin...

On a serious note, I came on the thread today to report a bug. But not one of pemasu's,
don't worry.

See attached picture.

The solution is to use the older resizepfile script, not the new one. (Sorry WXYZ and co.)

Or to bypass the script altogether and type directly in console:

cd /mnt/home
echo xyz000 > pupresize.txt

xyz being any number. With today's large hard drives, any number below 1 Gb should be safe to enter. So you could have
echo 999999 > pupresize.txt
or
echo 389000 > pupresize.txt
You don't need to have multiples of 16Mb.

The enlarger script integrated in the Puppy at boot time is healthy. It will pick up the
number in the /mnt/home/pupresize.txt file and add the specified number of megabytes
to the personal pupsave file.

I hope this helps.

musher0