1:02 p.m.
Hi all. I understand that support for the virtual keyword
has been removed from the latest update of X11 server.
Obviously this is why the virtual keyword in my xorg.conf
file does nothing on Fedora 9:
*snip*
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 800 1800
EndSubSection
EndSection
Please could we have virtual support enabled again by
Fedora?
I don't know how I'll manage without a virtual screen size
larger than my physical monitor.
Do I need to post a seperate bug report for this?
Kind Regards,
Keith Roberts
-----------------------------------------------------------------
Websites:
http://www.php-debuggers.net
http://www.karsites.net
http://www.raised-from-the-dead.org.uk
The mind of the prudent is ever getting knowledge, and the
eear of the wise is ever seeking, inquiring for and craving
knowledge. Pr. 18:15 Amp
All email addresses are challenge-response protected with
TMDA [http://tmda.net]
-----------------------------------------------------------------
2:36 a.m.
On Wed, 27 Aug 2008, Adam Jackson wrote:
To: For testers of Fedora Core development releases
<fedora-test-list(a)redhat.com>
From: Adam Jackson <ajax(a)redhat.com>
Subject: Re: X11 server Virtual Desktop Support
On Wed, 2008-08-27 at 19:02 +0100, Keith Roberts wrote:
> Hi all. I understand that support for the virtual keyword
> has been removed from the latest update of X11 server.
It's a function of the driver, not the server. And you haven't
mentioned which driver.
- ajax
Thanks Adam. So does this mean that each individual driver
for each machine with a differing video card driver needs to
be updated with support for the virtual desktop code?
Keith Roberts
-----------------------------------------------------------------
Websites:
http://www.php-debuggers.net
http://www.karsites.net
http://www.raised-from-the-dead.org.uk
The mind of the prudent is ever getting knowledge, and the
eear of the wise is ever seeking, inquiring for and craving
knowledge. Pr. 18:15 Amp
All email addresses are challenge-response protected with
TMDA [http://tmda.net]
-----------------------------------------------------------------
2:56 a.m.
On Wed, 27 Aug 2008, Adam Jackson wrote:
To: For testers of Fedora Core development releases
<fedora-test-list(a)redhat.com>
From: Adam Jackson <ajax(a)redhat.com>
Subject: Re: X11 server Virtual Desktop Support
On Wed, 2008-08-27 at 19:02 +0100, Keith Roberts wrote:
> Hi all. I understand that support for the virtual keyword
> has been removed from the latest update of X11 server.
It's a function of the driver, not the server. And you haven't
mentioned which driver.
- ajax
Here are the details from my Xorg.0.log for this particular
machine:
X Window System Version 1.3.0 Release Date: 19 April 2007 X
Protocol Version 11, Revision 0, Release 1.3 Build Operating
System: Fedora 8 Red Hat, Inc. Current Operating System:
Linux karsites 2.6.25.14-69.fc8 #1 SMP Mon Aug 4 14:20:24
EDT 2008 i686 Build Date: 24 July 2008 Build ID:
xorg-x11-server 1.3.0.0-47.fc8
*snip*
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:2:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation NV31 [GeForce FX 5600XT] rev 161, Mem @
0xce000000/24, 0xb0000000/28, BIOS @ 0xcfee0000/17
(II) Loading extension XFree86-DRI
(II) LoadModule: "nv"
(II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 2.1.6
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.2
*snip*
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "GeForce FX 5600XT"
(**) NV(0): Depth 24, (--) framebuffer bpp 32
(==) NV(0): RGB weight 888
(==) NV(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
*snip*
(II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual
size)
(II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual
size)
(II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
(II) NV(0): Not using driver mode "1024x768" (width too large for virtual size)
(**) NV(0): Virtual size is 800x1800 (pitch 800)
Kind Regards,
Keith Roberts
8:49 a.m.
On Thu, 2008-08-28 at 08:56 +0100, Keith Roberts wrote:
(II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
(II) Module nv: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 2.1.6
Module class: X.Org Video Driver
ABI class: X.Org Video Driver, version 1.2
*snip*
(II) Module int10: vendor="X.Org Foundation"
compiled for 1.3.0, module version = 1.0.0
ABI class: X.Org Video Driver, version 1.2
(II) NV(0): Initializing int10
(II) NV(0): Primary V_BIOS segment is: 0xc000
(--) NV(0): Chipset: "GeForce FX 5600XT"
(**) NV(0): Depth 24, (--) framebuffer bpp 32
(==) NV(0): RGB weight 888
(==) NV(0): Default visual is TrueColor
(II) Loading sub module "vgahw"
(II) LoadModule: "vgahw"
(II) Loading /usr/lib/xorg/modules//libvgahw.so
*snip*
(II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual
size)
(II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
(II) NV(0): Not using default mode "2048x1536" (width too large for virtual
size)
(II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
(II) NV(0): Not using driver mode "1024x768" (width too large for virtual
size)
(**) NV(0): Virtual size is 800x1800 (pitch 800)
That's actually kind of weird. The pre-G80 code in the nv driver should
support virtual panning just fine. (Though I'm amazed anyone uses it.)
Can you file a bug with the complete log please?
- ajax
11:46 a.m.
On Thu, Aug 28, 2008 at 09:49:44AM -0400, Adam Jackson wrote:
That's actually kind of weird. The pre-G80 code in the nv driver should
support virtual panning just fine. (Though I'm amazed anyone uses it.)
What is so amazing??? It does need a different desktop
configuration then a default one but it is a rather effective way
to expand a "screen real-estate". I was using that for years
(mostly with radeon cards) until it stopped working from F8 on.
I assumed that it may make troubles for xrandr but I was not very
pleased that it does not work anymore.
Michal
2:57 p.m.
On Thu, 28 Aug 2008, Adam Jackson wrote:
To: For testers of Fedora Core development releases
<fedora-test-list(a)redhat.com>
From: Adam Jackson <ajax(a)redhat.com>
Subject: Re: X11 server Virtual Desktop Support
On Thu, 2008-08-28 at 08:56 +0100, Keith Roberts wrote:
> (II) Loading /usr/lib/xorg/modules/drivers//nv_drv.so
> (II) Module nv: vendor="X.Org Foundation"
> compiled for 1.3.0, module version = 2.1.6
> Module class: X.Org Video Driver
> ABI class: X.Org Video Driver, version 1.2
>
> *snip*
>
> (II) Module int10: vendor="X.Org Foundation"
> compiled for 1.3.0, module version = 1.0.0
> ABI class: X.Org Video Driver, version 1.2
> (II) NV(0): Initializing int10
> (II) NV(0): Primary V_BIOS segment is: 0xc000
> (--) NV(0): Chipset: "GeForce FX 5600XT"
> (**) NV(0): Depth 24, (--) framebuffer bpp 32
> (==) NV(0): RGB weight 888
> (==) NV(0): Default visual is TrueColor
> (II) Loading sub module "vgahw"
> (II) LoadModule: "vgahw"
> (II) Loading /usr/lib/xorg/modules//libvgahw.so
>
> *snip*
>
> (II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
> (II) NV(0): Not using default mode "2048x1536" (width too large for virtual
size)
> (II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
> (II) NV(0): Not using default mode "2048x1536" (width too large for virtual
size)
> (II) NV(0): Not using default mode "1024x768" (width too large for virtual
size)
> (II) NV(0): Not using driver mode "1024x768" (width too large for virtual
size)
> (**) NV(0): Virtual size is 800x1800 (pitch 800)
That's actually kind of weird. The pre-G80 code in the nv driver should
support virtual panning just fine. (Though I'm amazed anyone uses it.)
Can you file a bug with the complete log please?
- ajax
The above log snippets were taking from my machine running
Fedora 8. The virtual keyword works fine on F8, despite what
the messages say above. I only use virtual screens to give
me a taller screen size. I don't particularly care about
horizontal panning around the screen as well.
Are you saying that the virtual keyword is still supported
by RH in F9? Is that what you want me to file the bug report
against?
Regards,
Keith Roberts
10:15 a.m.
On Thu, 2008-08-28 at 20:57 +0100, Keith Roberts wrote:
The above log snippets were taking from my machine running
Fedora 8. The virtual keyword works fine on F8, despite what
the messages say above. I only use virtual screens to give
me a taller screen size. I don't particularly care about
horizontal panning around the screen as well.
Are you saying that the virtual keyword is still supported
by RH in F9? Is that what you want me to file the bug report
against?
If it doesn't work in F9, then a log file showing the failure mode in F9
is what I'd need to see, yes.
- ajax
2:14 p.m.
On Fri, 29 Aug 2008, Adam Jackson wrote:
To: For testers of Fedora Core development releases
<fedora-test-list(a)redhat.com>
From: Adam Jackson <ajax(a)redhat.com>
Subject: Re: X11 server Virtual Desktop Support
On Thu, 2008-08-28 at 20:57 +0100, Keith Roberts wrote:
> The above log snippets were taking from my machine running
> Fedora 8. The virtual keyword works fine on F8, despite what
> the messages say above. I only use virtual screens to give
> me a taller screen size. I don't particularly care about
> horizontal panning around the screen as well.
>
> Are you saying that the virtual keyword is still supported
> by RH in F9? Is that what you want me to file the bug report
> against?
If it doesn't work in F9, then a log file showing the failure mode in F9
is what I'd need to see, yes.
- ajax
... I seem to have got the idea from somewhere that the
virtual keyword is not supported in xorg.conf anymore. I
think it was from a post on another mailing list where I
found this link:
https://bugs.freedesktop.org/show_bug.cgi?id=11418
BTW - is this the same X11 server code that Fedora uses?
There seems to be more than 1 version of the X11 server code
available for downloading.
I did a full update of F9 and the virtual keyword is still
working OK. So I apologise for my original post comments.
My problem is with the xorg.conf file not having a monitor
section in it.
The font sizes in F6 and F8 work fine without the monitor
section and a DisplaySize keyword in xorg.conf.
----------------------------------------------------
This is my full xorg.conf I'm using now with F8:
# Xorg configuration created by pyxf86config
Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nv"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 800 1800
EndSubSection
EndSection
----------------------------------------------------
This is my xorg.conf for F9
# Xorg configuration created by system-config-display
Section "ServerLayout"
Identifier "single head configuration"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "InputDevice"
# keyboard added by rhpxl
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "gb"
EndSection
Section "Device"
Identifier "Videocard0"
Driver "nv"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Modes "800x600" "640x480"
EndSubSection
EndSection
----------------------------------------------------
I have tried changing the above F9 Section "Screen" to:
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 800 1800
Modes "800x1800" "800x600" "640x480"
EndSubSection
EndSection
But the font sizes are *way* to large. This is why I'm still
using F8.
The Xorg.0.log file (using startx -- -logverbose) tells me:
'''
(WW) No monitor specified for screen "Screen0".
Using a default monitor configuration.
'''
I think I need a Monitor section in the F9 xorg.conf to set
the font size with the DisplaySize keyword. I'm not sure how
to go about adding the Monitor section to the F9 xorg.conf
to implement this. Any suggestions would be greatly appreciated.
I enclose an attachment showing the present font sizes in mc
with a virtual setting of 800 x 1800.
Kind Regards,
Keith Roberts
11:49 a.m.
On Sat, 2008-08-30 at 20:14 +0100, Keith Roberts wrote:
... I seem to have got the idea from somewhere that the
virtual keyword is not supported in xorg.conf anymore. I
think it was from a post on another mailing list where I
found this link:
https://bugs.freedesktop.org/show_bug.cgi?id=11418
So, there's two things here.
One is the Virtual keyword in xorg.conf. At a base level, all that does
is define how much video memory to reserve for the logical screen. It's
just a size.
The second thing is what the driver does with that space. There are two
kinds of drivers, for purposes of this discussion we'll call them legacy
and randrful. Legacy drivers can, at their option, enable a panning
mode, in which the Virtual size defines the size of the root window, and
the current cursor position is used to pan a viewport onto that root
window. In randrful drivers, that functionality simply is not present.
(This is made slightly more confusing in the nv driver because it
manages to be either legacy or randrful, depending which kind of chip
it's driving. G80 and newer chips - GeForce 8xxx and newer - are
randrful, and earlier are legacy.)
BTW - is this the same X11 server code that Fedora uses?
There seems to be more than 1 version of the X11 server code
available for downloading.
Yes, it is.
I have tried changing the above F9 Section "Screen" to:
Section "Screen"
Identifier "Screen0"
Device "Videocard0"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 24
Virtual 800 1800
Modes "800x1800" "800x600" "640x480"
EndSubSection
EndSection
That "800x1800" line in the Modes line isn't going to do what you want.
A Mode in the config file is a description of the region to display and
the timings of the synchronization regions at the edges. You don't
_want_ to display 800x1800.
But the font sizes are *way* to large. This is why I'm still
using F8.
Which sounds like we're just computing the dpi from the Virtual size
instead of the default mode size. Merely a bug, but again, need to see
the log from the broken configuration to know for sure.
The Xorg.0.log file (using startx -- -logverbose) tells me:
'''
(WW) No monitor specified for screen "Screen0".
Using a default monitor configuration.
'''
I think I need a Monitor section in the F9 xorg.conf to set
the font size with the DisplaySize keyword. I'm not sure how
to go about adding the Monitor section to the F9 xorg.conf
to implement this. Any suggestions would be greatly appreciated.
Section "Monitor"
Identifier "Monitor0"
# any settings you want...
EndSection
Section "Screen"
Identifier "Screen0"
Monitor "Monitor0"
# the rest of your Screen section as above...
EndSection
- ajax
1:20 p.m.
On Mon, 1 Sep 2008, Adam Jackson wrote:
To: For testers of Fedora Core development releases
<fedora-test-list(a)redhat.com>
From: Adam Jackson <ajax(a)redhat.com>
Subject: Re: X11 server Virtual Desktop Support
On Sat, 2008-08-30 at 20:14 +0100, Keith Roberts wrote:
> ... I seem to have got the idea from somewhere that the
> virtual keyword is not supported in xorg.conf anymore. I
> think it was from a post on another mailing list where I
> found this link:
>
> https://bugs.freedesktop.org/show_bug.cgi?id=11418
So, there's two things here.
One is the Virtual keyword in xorg.conf. At a base level, all that does
is define how much video memory to reserve for the logical screen. It's
just a size.
The second thing is what the driver does with that space. There are two
kinds of drivers, for purposes of this discussion we'll call them legacy
and randrful. Legacy drivers can, at their option, enable a panning
mode, in which the Virtual size defines the size of the root window, and
the current cursor position is used to pan a viewport onto that root
window. In randrful drivers, that functionality simply is not present.
(This is made slightly more confusing in the nv driver because it
manages to be either legacy or randrful, depending which kind of chip
it's driving. G80 and newer chips - GeForce 8xxx and newer - are
randrful, and earlier are legacy.)
> BTW - is this the same X11 server code that Fedora uses?
> There seems to be more than 1 version of the X11 server code
> available for downloading.
Yes, it is.
> I have tried changing the above F9 Section "Screen" to:
>
> Section "Screen"
> Identifier "Screen0"
> Device "Videocard0"
> DefaultDepth 24
> SubSection "Display"
> Viewport 0 0
> Depth 24
> Virtual 800 1800
> Modes "800x1800" "800x600"
"640x480"
> EndSubSection
> EndSection
That "800x1800" line in the Modes line isn't going to do what you want.
A Mode in the config file is a description of the region to display and
the timings of the synchronization regions at the edges. You don't
_want_ to display 800x1800.
> But the font sizes are *way* to large. This is why I'm still
> using F8.
Which sounds like we're just computing the dpi from the Virtual size
instead of the default mode size. Merely a bug, but again, need to see
the log from the broken configuration to know for sure.
> The Xorg.0.log file (using startx -- -logverbose) tells me:
>
> '''
> (WW) No monitor specified for screen "Screen0".
> Using a default monitor configuration.
> '''
>
> I think I need a Monitor section in the F9 xorg.conf to set
> the font size with the DisplaySize keyword. I'm not sure how
> to go about adding the Monitor section to the F9 xorg.conf
> to implement this. Any suggestions would be greatly appreciated.
Section "Monitor"
Identifier "Monitor0"
# any settings you want...
EndSection
Section "Screen"
Identifier "Screen0"
Monitor "Monitor0"
# the rest of your Screen section as above...
EndSection
- ajax
Thanks for taking the time to explain all that Adam. I'll
try your suggestions and see how they work out. As soon as I
have some results I'll post again on this list.
Kind regards,
Keith Roberts
9:12 a.m.
On Mon, 1 Sep 2008, Adam Jackson wrote:
To: For testers of Fedora Core development releases
<fedora-test-list(a)redhat.com>
From: Adam Jackson <ajax(a)redhat.com>
Subject: Re: X11 server Virtual Desktop Support
*snip*
Which sounds like we're just computing the dpi from the Virtual size
instead of the default mode size. Merely a bug, but again, need to see
the log from the broken configuration to know for sure.
I have filed a bug report here:
https://bugzilla.redhat.com/show_bug.cgi?id=460895
Kind Regards,
Keith Roberts
5712
days inactive
5718
days old
12 comments
3 participants
participants (3)
-
Adam Jackson -
Keith Roberts -
Michal Jaegermann