App windows won't fill screen in tahr 605 (Realy Solved)

Booting, installing, newbie
Message
Author
User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#61 Post by bigpup »

I was looking for info more like this from menu>System>Pup-Sysinfo>Devices>Display>Video info

example:
Chip description:
VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1)

Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1360x768
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): nvidia
Loaded modules: dbe dri2 fb fbdevhw glx kbd mouse ramdac wfb

Actual rendering on monitor:
Resolution: 1360x768 pixels (461x260 millimeters)
Depth: 24 planes
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#62 Post by number77 »

Hows this?
▶—— Video ——◀

Display Specifications:
• Monitor Name: Panasonic-TV
• Monitor VertRefresh: 50.0 times/s
• Screen Dimensions: 1920x1080 pixels (507x285 millimeters)
• Screen Depth: 24 bits (planes)

Xorg Startup Log (/var/log/Xorg.0.log):
• Xorg Driver in use: intel
• Loaded Modules: dbe dri2 extmod glx kbd mouse
• X.Org version: 1.15.1

OpenGL 2D/3D Rendering:
• Direct Rendering: Yes
• Vendor: Intel Open Source Technology Center
• Renderer: Mesa DRI Intel(R) Sandybridge Desktop x86/MMX/SSE2
• Version: 3.0 Mesa 10.1.3

VGA controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09)
• Kernel Driver: i915
• Memory Used: 480.31 KB
• Path: /lib/modules/3.14.56/kernel/drivers/gpu/drm/i915/i915.ko
• Description: Intel Graphics

I have also tried zenialdog openbox_jwm as its supposed to be like ubuntu. No luck there either

theru
Posts: 163
Joined: Thu 23 Jul 2015, 16:40
Location: Heers, Belgium

#63 Post by theru »

When I ran xrandr on my system I got an interesting result:

Code: Select all

DVI-0 disconnected primary
VGA-0 connected
What if your HDMI port isn't set as primary? Would that be the cause of your problems?

If you run the following command:

Code: Select all

xrandr | grep primary
Does it give the correct port?

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#64 Post by number77 »

theru wrote:When I ran xrandr on my system I got an interesting result:

Code: Select all

DVI-0 disconnected primary
VGA-0 connected
What if your HDMI port isn't set as primary? Would that be the cause of your problems?

If you run the following command:

Code: Select all

xrandr | grep primary
Does it give the correct port?
There is only one hdmi socket on the pc, I think the motherboard has at least 2 without any sockets.
Doesn't make any difference to the problem

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#65 Post by bigpup »

number77,

That video info tells me some of what I wanted to know.
You are using the Intel i915 driver.
Your hardware IS THE Intel 2nd Generation Core Processor Family Integrated Graphics.

However, menu>System>Pup-sysinfo>Devices>Display>Video info will tell me something I also want to know.

Please post the output from it.!!!!

rcrsn51 seems to have had the same issue on his computer.
He asked you for some specific info, but you have not provided it!


It is hard to help someone if they refuse to answer the exact questions we ask or if someone suggests something and they do not do exactly what is suggested!!!

Your problem is not what you think you have or think what is being used.
It is what Puppy thinks you have and are using.
That is going to be the clue to maybe fixing this issue!!!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#66 Post by number77 »

Maybe this is the information.
VIDEO REPORT: tahrpup, version 6.0.5

Chip description:
VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Drivers requested to be loaded: intel

Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): intel
Loaded modules: dbe dri2 extmod glx kbd mouse

Actual rendering on monitor:
Resolution: 1920x1080 pixels (507x285 millimeters)
Depth: 24 planes

...the above also recorded in /tmp/report-video

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#67 Post by number77 »

rcrsn51 wrote:@77: When you run xrandr, what device (or devices) is flagged as active - has a * beside it?

I get EXACTLY the same behaviour as you with my Atom machines who think that they are connected to a laptop screen instead of a VGA monitor. I need to run a script that forces them to use VGA.
Sorry I didn't answer you but I didn't understand, no device was flagged, a resolution was though: 1920x1080 at 50 fps

theru
Posts: 163
Joined: Thu 23 Jul 2015, 16:40
Location: Heers, Belgium

#68 Post by theru »

I've done some more testing with a netbook connected to an external monitor. I had the same problems until I shut down the built-in screen and restarted the window manager.

If you post the output of xrandr and tell us which window manager you're using then I may be able to make a script.

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#69 Post by number77 »

theru wrote:I've done some more testing with a netbook connected to an external monitor. I had the same problems until I shut down the built-in screen and restarted the window manager.

If you post the output of xrandr and tell us which window manager you're using then I may be able to make a script.
Hello theru
That would be good.
xrandr:
root# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 32767 x 32767
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 698mm x 392mm
1920x1080 50.0 + 60.0* 59.9 24.0 24.0
1920x1080i 60.1 50.0 60.0
1280x720 60.0 50.0 59.9
1440x576i 50.1
1440x480i 60.1 60.1
720x576 50.0
720x480 60.0 59.9
640x480 60.0 59.9
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*
800x600 60.3 56.2
848x480 60.0
640x480 59.9
VIRTUAL1 disconnected (normal left inverted right x axis y axis)
Desktop on it is perfect and fills the screen correctly, it is only any program that I open that is limited to the small size, about half size.

User avatar
Flash
Official Dog Handler
Posts: 13071
Joined: Wed 04 May 2005, 16:04
Location: Arizona USA

#70 Post by Flash »

Number77, you forgot to say which window manager you're using.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#71 Post by bigpup »

Have you tried to use a different HDMI port?
HDMI 1 or 3?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#72 Post by number77 »

Flash wrote:Number77, you forgot to say which window manager you're using.
How do I find that out, I thought xrandr print out would do that.

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#73 Post by number77 »

bigpup wrote:Have you tried to use a different HDMI port?
HDMI 1 or 3?
There is only one hdmi port on the pc, I assumed that was named hdmi2. There are others on the motherboard but with no connections and very inaccessible.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#74 Post by bigpup »

number77 wrote:
Flash wrote:Number77, you forgot to say which window manager you're using.
How do I find that out, I thought xrandr print out would do that.
If it is Tahrpup 6.0.5.
It is probably using JWM.
That is the window manager it comes with.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

theru
Posts: 163
Joined: Thu 23 Jul 2015, 16:40
Location: Heers, Belgium

#75 Post by theru »

HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 698mm x 392mm
1920x1080 50.0 + 60.0* 59.9 24.0 24.0
1920x1080i 60.1 50.0 60.0
1280x720 60.0 50.0 59.9
1440x576i 50.1
1440x480i 60.1 60.1
720x576 50.0
720x480 60.0 59.9
640x480 60.0 59.9
...
DP3 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*
800x600 60.3 56.2
848x480 60.0
640x480 59.9
Only 1 screen connected yet xrandr shows 2 ports being connected, one outputting 1920x1080, the other 1024x768.

My experience is that by default the same output is mirrored on both screens but the windows won't expand beyond the borders of the smaller screen.

Assuming the DP3 entry is a false positive it's easy to turn it off:

Code: Select all

xrandr --output DP3 --off
This should turn off the fake screen. It can be checked by running xrandr without any options.

After that all that's left to do is to restart the window manager.

Assuming you are using jwm:

Code: Select all

jwm -restart
A more generic way to restart the window manager is to go to the logout screen and click on Restart window manager.

All new windows opened after this point should resize correctly.

These changes only last for the current session and are reverted every time the computer or xorg server is restarted. So it needs to be run when xorg server is started but before the window manager is loaded.

Since this command is basically a single line I found it better to add it to an existing script. I found a really short one that's called early on.

On my pc the script /root/.xset.sh (hidden file, click the eye icon to reveal) only contains one line:

Code: Select all

xset m 20/10 4 c off r rate 660 25 s off -dpms
The only thing that needs to be done is adding a new line and type the following:

Code: Select all

xrandr --output DP3 --off
When that's done the pc should behave normally every time it's booted.

User avatar
rufwoof
Posts: 3690
Joined: Mon 24 Feb 2014, 17:47

#76 Post by rufwoof »

In the past I've coded something like

Code: Select all

<StartupCommand>sleep 5;xrandr --output HDMI2 --mode 1920x1080 --output DP3 --off</StartupCommand>
into jwm configuration (I use ~/.jwmrc but for standard puppy's you'll probably have to use another included file for that to remain consistently coded i.e. perhaps in ~/.jwm/jwmrc-personal).

The sleep just gives the system a bit of time to settle down before triggering the settings/change. You could also just run

Code: Select all

xrandr --output HDMI2 --mode 1920x1080 --output DP3 --off
from within a terminal

Another way is to encode things in /etc/X11/xorg.conf by adding appropriate Monitor and Screen sections ... something like

Code: Select all

Section "Monitor"
   Identifier   "HDMI2"
   VendorName   "Monitor Vendor"
   ModelName    "Monitor Model"
   Option "PreferredMode" "1920x1080"
EndSection

Section "Screen"
	Identifier "HDMI2"
	SubSection "Display"
            Modes      "1920x1080"
	EndSubSection
EndSection

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#77 Post by number77 »

xrandr --output DP3 --off
Doesnt turn DP3 off.
xrandr still says its there.

Is there any way to force DP3, which doesnt exist, to run on same resolution as hdmi screen. 1920x1080x50.

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#78 Post by number77 »

theru wrote:
HDMI2 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 698mm x 392mm
1920x1080 50.0 + 60.0* 59.9 24.0 24.0
1920x1080i 60.1 50.0 60.0
1280x720 60.0 50.0 59.9
1440x576i 50.1
1440x480i 60.1 60.1
720x576 50.0
720x480 60.0 59.9
640x480 60.0 59.9
...
DP3 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*
800x600 60.3 56.2
848x480 60.0
640x480 59.9
Only 1 screen connected yet xrandr shows 2 ports being connected, one outputting 1920x1080, the other 1024x768.

My experience is that by default the same output is mirrored on both screens but the windows won't expand beyond the borders of the smaller screen.

Assuming the DP3 entry is a false positive it's easy to turn it off:

Code: Select all

xrandr --output DP3 --off
This should turn off the fake screen. It can be checked by running xrandr without any options.

After that all that's left to do is to restart the window manager.

Assuming you are using jwm:

Code: Select all

jwm -restart
A more generic way to restart the window manager is to go to the logout screen and click on Restart window manager.

All new windows opened after this point should resize correctly.

These changes only last for the current session and are reverted every time the computer or xorg server is restarted. So it needs to be run when xorg server is started but before the window manager is loaded.

Since this command is basically a single line I found it better to add it to an existing script. I found a really short one that's called early on.

On my pc the script /root/.xset.sh (hidden file, click the eye icon to reveal) only contains one line:

Code: Select all

xset m 20/10 4 c off r rate 660 25 s off -dpms
The only thing that needs to be done is adding a new line and type the following:

Code: Select all

xrandr --output DP3 --off
When that's done the pc should behave normally every time it's booted.
It works 100%, I forgot to restart the windows manager. When I did everything full screen.
Thats brilliant theru thanks.
I just have to follow the instructions and make it permenant.
Thanks once more.

theru
Posts: 163
Joined: Thu 23 Jul 2015, 16:40
Location: Heers, Belgium

#79 Post by theru »

Glad to hear it's working.

When you run xrandr you see a list of available resolutions with a * after the one the screen is currently set to. There is no * when the screen is disabled.

I have noticed that the file xset.sh is rewritten when you run menu -> desktop -> pupx set properties of x and change some settings there. While that won't happen often it still means it's a less than ideal place to make the settings permanent.

The xset.sh command is called by /root/.xinitrc. The xinitrc file is less likely to be rewritten unexpectedly. However you can't just insert the xrandr command anywhere so if you decide to try it it would be best to backup the file first.

The xset.sh command is only called once in xinitrc so it's easy to locate using the find command in a text editor. On my system it's this block of text:

Code: Select all

if [ -f /root/.xset.sh ];then
 #this is created by /usr/bin/pupx...
 eval "/root/.xset.sh"
Just above that entry the xrandr command can be safely inserted.

It will probably look like this:

Code: Select all

xrandr --output DP3 --off 

if [ -f /root/.xset.sh ];then
 #this is created by /usr/bin/pupx...
 eval "/root/.xset.sh"
Feel free to send me your xinitrc if you don't feel comfortable to make the changes yourself.

number77
Posts: 804
Joined: Fri 22 Oct 2010, 19:30

#80 Post by number77 »

Where is xinitrc, a search says it is in /root/.xinitrc. Even with the eye pressed I can't find it in root.

Post Reply