Re: xstart failed wsl ubuntu 18.04.3

[Alex Deucher]

What hardware are you trying to use with X?

Alex

On Tue, Nov 16, 2021 at 5:02 AM Steen Jakobsen
 wrote:
>
> Hi
>
> I hope you can help. I have done a lot of configuration, but still something 
> is missing. I have attached logfile.
>
> Steen. Denmark

Re: Xorg framebuffer and brightness of screen

[Alex Deucher]

On Fri, Nov 12, 2021 at 11:21 PM Riza Dindir  wrote:
>
> Hello Alex,
>
> Isn't there a software based solution to set the brightness in xorg?

Not really.  You need some interface to talk to the backlight
controller, either via software via a driver or via some firmware
interface like ACPI if the platform supports it.  You can also adjust
the gamma on the display which will give the perception of changes in
brightness, but it won't actually change the levels of the backlight
itself.  That said, you need driver support to adjust the gamma as
well.

Alex

>
> Riza
>
> On Fri, Nov 12, 2021 at 11:37 PM Alex Deucher  wrote:
> >
> > On Fri, Nov 12, 2021 at 12:36 AM Riza Dindir  wrote:
> > >
> > > Hello Ken.
> > >
> > > On Fri, Nov 12, 2021 at 12:56 AM Ken Moffat  
> > > wrote:
> > > >
> > > > On Thu, Nov 11, 2021 at 10:16:18AM +0300, Riza Dindir wrote:
> > > > > Hello Ken
> > > > >
> > > > > I am using gop, and a framebuffer. When i try to use the xrandr, it 
> > > > > says
> > > > > "gamma is set to 0", or "failed to get size of gamma for output 
> > > > > default".
> > > > >
> > > > > I can set the gamma uaing xgamma and in the xorg.conf file.
> > > > >
> > > > > Riza
> > > > >
> > > > No idea what gop is - google suggests it's the american republican
> > > > party ;-)
> > >
> > > :D That is the graphics output protocol.
> > >
> > > My radeon device is not recognized by the kernel (netbsd) and I am
> > > using a framebuffer.
> > >
> > > >
> > > > Did you search for that "failed to get" message ?  Google gives me a 
> > > > lot of
> > > > different matches, some for failing to correctly add a new mode,
> > > > others for running with nvidia drivers or in virtualbox, or with out
> > > > of date manufacturer's video driver.
> > > > https://askubuntu.com/questions/441040/failed-to-get-size-of-gamma-for-output-default-when-trying-to-add-new-screen-res
> > > >
> > > > For an ubuntu-based kernel with at-the-time recent intel graphics
> > > > hardware, adding a boot arg to enable alpha-quality intel support.
> > > > https://itectec.com/ubuntu/ubuntu-xrandr-failed-to-get-size-of-gamma-for-output-default-for-mdp-type-connection/
> > > >
> > > > In short, finding the answer really does seem to depend on what
> > > > hardware and distro are in use.  I'm assuming you're using some sort
> > > > of linux.
> > >
> > > What I am trying to do is reduce the brightness of the LCD on my
> > > laptop. Since I am using a framebuffer, I thought that I could do that
> > > with the gamma values. But xrandr fails with  a message relating to
> > > the gamma values being 0 or not set.
> >
> > You might get lucky if your system supports backlight control via
> > hotkeys or some ACPI interface which your BSD supports.  If not, then
> > not.  There's no backlight control in GOP.
> >
> > Alex
> >
> >
> > >
> > > >
> > > > ĸen
> > > > --
> > > > Vetinari smiled. "Can you keep a secret, Mister Lipwig?"
> > > > "Oh, yes, sir. I've kept lots."
> > > > "Capital. And the point is, so can I. You do not need to know.”
> > >
> > > Regards,
> > > Riza

Re: Xorg framebuffer and brightness of screen

[Alex Deucher]

On Fri, Nov 12, 2021 at 12:36 AM Riza Dindir  wrote:
>
> Hello Ken.
>
> On Fri, Nov 12, 2021 at 12:56 AM Ken Moffat  wrote:
> >
> > On Thu, Nov 11, 2021 at 10:16:18AM +0300, Riza Dindir wrote:
> > > Hello Ken
> > >
> > > I am using gop, and a framebuffer. When i try to use the xrandr, it says
> > > "gamma is set to 0", or "failed to get size of gamma for output default".
> > >
> > > I can set the gamma uaing xgamma and in the xorg.conf file.
> > >
> > > Riza
> > >
> > No idea what gop is - google suggests it's the american republican
> > party ;-)
>
> :D That is the graphics output protocol.
>
> My radeon device is not recognized by the kernel (netbsd) and I am
> using a framebuffer.
>
> >
> > Did you search for that "failed to get" message ?  Google gives me a lot of
> > different matches, some for failing to correctly add a new mode,
> > others for running with nvidia drivers or in virtualbox, or with out
> > of date manufacturer's video driver.
> > https://askubuntu.com/questions/441040/failed-to-get-size-of-gamma-for-output-default-when-trying-to-add-new-screen-res
> >
> > For an ubuntu-based kernel with at-the-time recent intel graphics
> > hardware, adding a boot arg to enable alpha-quality intel support.
> > https://itectec.com/ubuntu/ubuntu-xrandr-failed-to-get-size-of-gamma-for-output-default-for-mdp-type-connection/
> >
> > In short, finding the answer really does seem to depend on what
> > hardware and distro are in use.  I'm assuming you're using some sort
> > of linux.
>
> What I am trying to do is reduce the brightness of the LCD on my
> laptop. Since I am using a framebuffer, I thought that I could do that
> with the gamma values. But xrandr fails with  a message relating to
> the gamma values being 0 or not set.

You might get lucky if your system supports backlight control via
hotkeys or some ACPI interface which your BSD supports.  If not, then
not.  There's no backlight control in GOP.

Alex


>
> >
> > ĸen
> > --
> > Vetinari smiled. "Can you keep a secret, Mister Lipwig?"
> > "Oh, yes, sir. I've kept lots."
> > "Capital. And the point is, so can I. You do not need to know.”
>
> Regards,
> Riza

Re: Xorg framebuffer and brightness of screen

[Alex Deucher]

On Wed, Nov 10, 2021 at 2:15 AM Riza Dindir  wrote:
>
> Hello All,
>
> I woukd like to know if I can adjust the screen brightness when using the 
> framebuffer device on xorg?

If it's a legacy fbdev device, it probably exposes the backlight via
the kernel backlight interface:
https://www.kernel.org/doc/Documentation/ABI/stable/sysfs-class-backlight

Alex

[ANNOUNCE] xf86-video-amdgpu 21.0.0

[Alex Deucher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Adam Jackson (2):
  kms: Handle changes to SourceValidate call chain in xserver 19
  Fix link failure with gcc 10

Alex Deucher (1):
  Bump version for the 21.0.0 release

Emil Velikov (10):
  Use ODEV_ATTRIB_PATH where possible for the device node.
  Remove drmCheckModesettingSupported and kernel module loading, on Linux
  Fixup the amdgpu_bus_id() string format
  Remove NULL check after a "cannot fail" function
  Store the busid string in AMDGPUEnt
  Reuse the existing busid string
  Use the device_id straight from gpu_info
  Kill off drmOpen/Close/drmSetInterfaceVersion in favour of drmDevices
  Introduce amdgpu_device_setup helper
  Factor out common code to amdgpu_probe()

Likun Gao (1):
  Fix drmmode_crtc_scanout_create logic

Michel Dänzer (11):
  Bail from amdgpu_pixmap_get_handle with ShadowFB
  Handle NULL fb_ptr in pixmap_get_fb
  glamor: Make pixmap scanout compatible if its dimensions are
  Drop bo/width/height members from struct drmmode_scanout
  Drop struct drmmode_scanout altogether in favour of PixmapPtrs
  Make drmmode_crtc_scanout_create/destroy static
  Fix build against ABI_VIDEODRV_VERSION 25.2
  Replace a few more instances of "master"
  Check for AMDGPU_CREATE_PIXMAP_SCANOUT in amdgpu_glamor_create_pixmap
  Drop dri.h includes
  Include xf86drm.h instead of sarea.h

Niclas Zeising (1):
  Fix return value check of drmIoctl()

Peter Hutterer (1):
  gitlab CI: update to use the latest CI templates

git tag: xf86-video-amdgpu-21.0.0

https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-21.0.0.tar.bz2
SHA256: 607823034defba6152050e5eb1c4df94b38819ef764291abadd81b620bc2ad88  
xf86-video-amdgpu-21.0.0.tar.bz2
SHA512: 
44ccc8ddc36f09d1608cf58b6cf85dda090671c46c5643e9453f7d67f4d6850c3c9753eba43539d45773198b8042898a50153b5225780e4b2852410c5521314a
  xf86-video-amdgpu-21.0.0.tar.bz2
PGP:  
https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-21.0.0.tar.bz2.sig

https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-21.0.0.tar.gz
SHA256: c3df02cc280c120d07eac01559b1e2c09890546f5044d4853209e5eff71a2f7e  
xf86-video-amdgpu-21.0.0.tar.gz
SHA512: 
c744ff096695b3d80f4dc3977f0952284e890fd72ed635a04c57806747621c32686f5982cf127de47f5895d73d7b52791a27d8eef4034e2e79547b3c8a6ee8c1
  xf86-video-amdgpu-21.0.0.tar.gz
PGP:  
https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-21.0.0.tar.gz.sig

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQQBfpGodcujISWDgPGbTuT5hHTeQAUCYQQDWgAKCRCbTuT5hHTe
QHXKAKDIw5l0TpJ8gPvB9tw50WCp2WktpgCgpuhzs+UfUrZZ76OOzRWClz0CbpA=
=0H9K
-END PGP SIGNATURE-

Re: Ryzen 4500U Integrated graphics - found no way to make it work

[Alex Deucher]

On Tue, Nov 24, 2020 at 3:53 AM Martin Wagner  wrote:
>
> Dear mailing list,
>
> for my new job I got a just as new HP Probook X360 435 G7, featuring
> the AMD CPU/GPU I named above (Ryzen 5 4500U) - and I found no way so
> far to make it work in any Linux I could think of. I get either a low
> resolution (SVGA on older kernel or current 5.8 kernel with nomodeset
> option) or a black screen on boot on any distribution I tried so far
> with a recent kernel (which is Mint, Ubuntu Mate, Fedora, openSUSE,
> Manjaro, Debian, maybe one or two I forgot).
>
> First of all: A lot of troubleshooting happened here already, there you
> can also find a ton of log outputs:
>
> https://forums.linuxmint.com/viewtopic.php?f=46&t=334399
>
> (Linux Mint is my preferred distribution pretty much since it came into
> existence.)
>
> Can you offer any way to make it work, any kind of help beyond what I
> already tried? Post #27 on that forum thread also contains an
> Xorg.0.log.old, which is one of the black screen boots of course.
>
> Please let me know if I can provide you any further information. Thank
> you.
>

Does this system have an option in the sbios to enable pre-OS or UEFI
DMA protection or something like that?  If so, can you try disabling
that?  If not, please open a bug and attach your dmesg output and xorg
log (if using X).

https://gitlab.freedesktop.org/drm/amd/-/issues

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xrandr: Games/Apps don't recognize virtual Monitor resolution

[Alex Deucher]

On Mon, Jul 13, 2020 at 12:17 PM DocMAX  wrote:
>
> Hello,
>
> i'd like to use one big screen of my 3 monitors like xinerama.
> In xinerama i get the resoultion 5860x1080 shown in my Apps/Games.
>
> In xrandr i dont get it. Here is my config:
>
>  xrandr \
>  --output DP-0 --off \
>  --output DP-1 --primary --mode 1920x1080 --pos 1970x0
> --rotate normal \
>  --output DP-2 --off \
>  --output DP-3 --mode 1920x1080 --pos 3940x0 --rotate normal
> --output HDMI-0 --off \
>  --output DP-4 --off \
>  --output DP-5 --mode 1920x1080 --pos 0x0 --rotate normal \
>  --noprimary
>  xrandr --setmonitor surround auto DP-5,DP-1,DP-3
>  xrandr -s 5860x1080
>
> Also tried to add a mode like this:
>
>  xrandr --newmode "5860x1080"  528.25  5860 6240 6864 7864 1080
> 1083 1093 1120 -hsync +vsync
>
> without luck.

xrandr doesn't do what you are looking for.  To do what I think you
want to do, you need to either hack the app to ignore xinerama
geometry hints or hack xinerama to expose the total screen size as a
single geometry.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: X-Server not start

[Alex Deucher]

On Fri, Jul 10, 2020 at 10:25 AM Michael Sorge  wrote:
>
> Hi,
>
> attached you find Xorg log file to failed start on new debian installation.
>
> Hardware is AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 2.00GHz.
>
> Is this a bug or a known problem?

Check your dmesg output to make sure the amdgpu kernel driver is
loaded.  Since you are on debian, you probably need to install the
firmware packages.

Alex


>
> Regards
>
> Michael
>
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: no screens found(EE) - Cannot use AMD R5 M330 as output to monitor

[Alex Deucher]

Most modern desktop environments set this up already.  All you need to do
is set the env var DRI_PRIME=1 when running an app and it will run on the
dGPU.  Many desktop environments also provide a GUI based option to choose
which GPU to run a particular application on.

Alex

On Fri, May 15, 2020 at 8:23 AM IL Ka  wrote:

> Then what is the right thing to do here?
> Use AMD only for rendering, but not for the output. Something like:
> $ xrandr --setprovideroffloadsink provider sink
> ?
>
>
>
>
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>  Без
> вирусов. www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#m_-1550470071674472515_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Thu, May 14, 2020 at 9:52 PM Alex Deucher 
> wrote:
>
>> On Thu, May 14, 2020 at 2:47 PM IL Ka  wrote:
>> >
>> > Here is what happened:
>> >>
>> >> [   347.043] (WW) RADEON(0): No outputs definitely connected, trying
>> again...
>> >> [   347.043] (WW) RADEON(0): Unable to find connected outputs -
>> setting 1024x768 initial framebuffer
>> >> [   347.043] (II) RADEON(0): mem size init: gart size :7fbcf000 vram
>> size: s:8000 visible:fbbe000
>> >
>> >
>> > It seems that you have 2 video cards: intel (built into CPU I believe)
>> and ATI.
>> > Intel is connected, not ATI.
>> >
>> > I think you need to enable ATI video card in your BIOS settings.
>> > There should be something like "discrete video card" or "on board video
>> card" switch.
>>
>> Not possible on this system.  The dGPU in question has no display
>> hardware at all so it cannot drive a display.  It can only support
>> render offload.
>>
>> Alex
>>
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: What is the difference between these two drivers ?

[Alex Deucher]

On Mon, May 11, 2020 at 3:30 PM Sreyan Chakravarty  wrote:
>
> Hi,
>
> Can anyone tell me what is the difference between these 2 drivers:
>
> xorg-x11-drv-amdgpu
>
> xorg-x11-drv-ati
>
>
> They both seem to be doing the same thing. Why use one instead of the
> other ?
>

They support different hardware generations.  -ati supports the
original r1xx radeons through Sea Islands asics.  -amdgpu supports
everything newer.

Alex

> --
> Regards,
> Sreyan
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Lost sliding windows w/ DVI Syncmaster monitor

[Alex Deucher]

On Thu, Apr 2, 2020 at 12:09 PM Paul Rogers  wrote:
>
> > I'm not familiar with the vesa or nouveau drivers and whether or not
> > they support panning.  One thing you could try however is to
>
> VESA has been panning all along with my VGA monitors.
>
> > temporarily disable your xorg configs and enable panning dynamically
> > at runtime using xrandr just to see if you can get it working with
> > your hardware combination.  You'll need to use a real driver rather
> > than vesa since vesa can't resize the desktop dynamically at runtime.
>
> I beg to differ.  KP+ & KP- do work with the VESA driver on my VGA monitors, 
> and this server.  It's one of my main reasons for using VESA--a key press is 
> so much faster and easier than xrandr.  My xorg.conf with this system 
> specifies VESA still, and it resizes with the keypad now.
>

Vesa doesn't support the xrandr 1.2 panning feature as far as I recall
so my suggestion would not work with vesa.

Alex

> --
> Paul Rogers
> paulgrog...@fastmail.fm
> Rogers' Second Law: "Everything you do communicates."
> (I do not personally endorse any additions after this line. TANSTAAFL :-)
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Lost sliding windows w/ DVI Syncmaster monitor

[Alex Deucher]

On Wed, Apr 1, 2020 at 4:03 PM Paul Rogers  wrote:
>
> > I don't think it has anything to do with the Samsung or the Dell, but
> > rather with
> > however you are trying to configure. How exactly are you configuring?
>
> See attachment.  Or are you asking for the build options for the server?
>
>  >> Please show us your GPU specification, thus:
>
>  >>  # inxi -Gxx
>
>
> Graphics:
>   Device-1: NVIDIA GK208 [GeForce GT 635] driver: N/A bus ID: 01:00.0
>   chip ID: 10de:1280
>   Display: server: X.Org 1.18.4 driver: vesa resolution: 1024x768~N/A
>   OpenGL: renderer: Gallium 0.4 on llvmpipe (LLVM 3.8 256 bits)
>   v: 3.3 Mesa 12.0.1 compat-v: 3.0 direct render: Yes
>

I'm not familiar with the vesa or nouveau drivers and whether or not
they support panning.  One thing you could try however is to
temporarily disable your xorg configs and enable panning dynamically
at runtime using xrandr just to see if you can get it working with
your hardware combination.  You'll need to use a real driver rather
than vesa since vesa can't resize the desktop dynamically at runtime.
Take a look at the xrandr man page.  You'll need to set the panning
option.  E.g.,
xrandr --output DVI-0 --panning ...

from the man page:
   --panning
widthxheight[+x+y[/track_widthxtrack_height+track_x+track_y[/border_left/border_top/border_right/border_bottom]]]
  This option sets the panning parameters.  As soon as
panning is enabled, the CRTC position can change with every  pointer
move.   The  first
  four  parameters  specify  the  total  panning area, the
next four the pointer tracking area (which defaults to the same area).
The last four
  parameters specify the border and default to 0. A width
or height set to zero disables panning on the according axis. You
typically  have  to
  set the screen size with --fb simultaneously.

I haven't played with panning in about 10 years so my memory is pretty
limited as to what is supported on what hardware.  Once drivers
started implementing xrandr 1.2 support, at lot of them dropped
panning support since even then it was not commonly used.

Alex

>
>
> --
> Paul Rogers
> paulgrog...@fastmail.fm
> Rogers' Second Law: "Everything you do communicates."
> (I do not personally endorse any additions after this line. TANSTAAFL 
> :-)___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Lost sliding windows w/ DVI Syncmaster monitor

[Alex Deucher]

On Wed, Apr 1, 2020 at 3:48 PM Paul Rogers  wrote:
>
> On Wed, Apr 1, 2020, at 11:25 AM, Alex Deucher wrote:
> > Panning has nothing to do with the monitor.  It comes down the the
> > hardware limitations of the underlying device and what features are
>
> I'm guessing you mean "device" as used in xorg.conf, i.e. the video card?  
> Obviously the monitor is a device.

device = video card.

>
> > exposed via the driver for that device.  The maximum framebuffer size
> > is limited by the stride coordinate limits of the display hardware on
> > the device.  The device also needs to be able to dynamically adjust
> > the offset of the display frame within the display surface.  When you
> > slide pan around with in the larger virtual desktop, the driver is
> > changing the offset of the display controller as you move around.  On
> > top of the hardware requirements, the X driver also has to expose the
> > necessary support for panning.  Not all drivers do.  Especially newer
> > drivers which support randr 1.2 or newer.
> >
> > Alex
> >
>
> Thank you, I can barely make sense of that.  But I don't see how these 
> internals help me get panning to work again on my system.

I'm just saying it's not the monitor.  It's either a problem with your
xorg configuration or the driver or underlying hardware doesn't
support panning.

Alex

>
> --
> Paul Rogers
> paulgrog...@fastmail.fm
> Rogers' Second Law: "Everything you do communicates."
> (I do not personally endorse any additions after this line. TANSTAAFL :-)
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Lost sliding windows w/ DVI Syncmaster monitor

[Alex Deucher]

On Wed, Apr 1, 2020 at 1:39 PM Paul Rogers  wrote:
>
> > The effect you like is called panning.
>
> Thank you for that.  I couldn't guess what the proper keyword would be for 
> searching, best I could think of was "sliding" and this got lots of hits on 
> vinyl windows! 8-(
>
> >
> > I don't think it has anything to do with the Samsung or the Dell, but
>
> I'm quite sure it does.  I've been doing lots of testing to identify the 
> problem.  If you want the gorey details:  I moved the HD from a box using a 
> Biostar TP43 MoBo w/ Core2-Duo "Conroe" CPU, Nvidia GeForce 6200 w/ NV44 GPU 
> PCI video, HPvs15 VGA monitor, to a Dell XPS-8700, "Haswell" CPU, GeForce 
> GT6351 w/ GK208 GPU PCIe-16 video, Samsung Syncmaster 730E monitor, with NO 
> configuration changes to X.  Panning worked in the first box, not the second. 
>  BUT, it also doesn't work with the same monitor, same software, on an Intel 
> S1200 "Sandybridge" server board with Intel's integrated graphics.  The 
> common denominator is the monitor.  I suspect the EDID is telling X something 
> different than the VGA monitor, that X is taking to mean "don't do panning", 
> that defaulted to panning on all the VGA monitors it has run on before.  I 
> can't find any likely suspects in xorg.conf.
>

Panning has nothing to do with the monitor.  It comes down the the
hardware limitations of the underlying device and what features are
exposed via the driver for that device.  The maximum framebuffer size
is limited by the stride coordinate limits of the display hardware on
the device.  The device also needs to be able to dynamically adjust
the offset of the display frame within the display surface.  When you
slide pan around with in the larger virtual desktop, the driver is
changing the offset of the display controller as you move around.  On
top of the hardware requirements, the X driver also has to expose the
necessary support for panning.  Not all drivers do.  Especially newer
drivers which support randr 1.2 or newer.

Alex

> > rather with however you are trying to configure.
>
> It worked fine before moving the HD.
>
> > How exactly are you configuring?
>
> I attached my X log.
>
> > Also, you're using a very slow generic X driver (VESA)
>
> By choice.  I don't need any advanced functions, so staying with the most 
> basic common driver gives me added flexibility to use it with different video 
> cards without reconfiguratiom.
>
> > that I suspect may not support panning.
>
> Yes, it does.  This same system worked just fine before I changed monitors as 
> described.  It continues to work on other boxen with VGA monitors.
>
> > It's also possible that the problem is your distro's build
>
> My distro, to be sure.  This is an LFS derived "distro" I hand-built, the 
> last of 9 versions since 2.4 kernels.
>
> > of 1.18.4 server or driver is broken WRT panning.
>
> My original complaint said it was working before I upgraded and got this new 
> monitor.  It's not the server unless panning is monitor/EDID dependent.
>
> > ISTR panning was broken in the server for quite some
> > time, depending on configuration method, and the patch to fix for which
> > may not have been included in your quite old 1.18.4 version.
>
> It takes me a long time to build my distro from scratch.  I could upgrade the 
> server, as long as it would retain compatibility with everything else in this 
> version of X-7.2.  I don't want to go into "dependency hell"!
>
> >
> > Please show us your GPU specification, thus:
> >
> >  # inxi -Gxx
> >
>
> [10:32 ~]# inxi -Gxx
> -su: inxi: command not found
> [10:32 ~]#
>
> The GPU ID is in the log, Nvidia GK208.
>
> --
> Paul Rogers
> paulgrog...@fastmail.fm
> Rogers' Second Law: "Everything you do communicates."
> (I do not personally endorse any additions after this line. TANSTAAFL :-)
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Debian 10.3: X does not start

[Alex Deucher]

On Fri, Mar 27, 2020 at 4:31 PM Klaus Jantzen  wrote:
>
> Thank you for your replies.
>
> After many additional tries (reinstall xserver-xorg-video-amdgpu,
> running with and without xorg.conf) I think the problem is again (I have
> found several references to this problem in other environments)
> indicated by the message
>
> [ 7.655] (EE) open /dev/dri/card0: No such file or directory
>
> How do get (where do I find) "/dev/dri/card0" ??

As suggested by several people already, please check if the kernel
driver is loaded (dmesg output).

Alex

>
> K.D.J.
>
>
> On 3/25/20 7:25 PM, IL Ka wrote:
> > In most cases there is no need to run "-configure" since X can
> > autodetect many things using defaults provided by distro.
> > Have you tried official debian wiki (it is about amdgpu, not general
> > modesetting)
> > https://wiki.debian.org/AtiHowTo  ?
> >
> > I think that "/dev/dri/card0: No such file or directory"  means there is
> > no kernel driver (no module compiled or not loaded by udev)
> > Do you run custom kernel? Have you tried to load module manually using
> > (modprobe)?
> >
> >
> > On Wed, Mar 25, 2020 at 9:00 PM Klaus Jantzen  > > wrote:
> >
> > Hello,
> >
> > I installed Debian on a PC with AMD Ryzen 5 3400 G.
> >
> > My first trials ended with a message
> >
> > "Cannot run in framebuffer mode ..." from xorg.
> >
> > Due to some research in the net I am using the following xorg.conf.
> > It is basically what I got when I did a "X -configure".
> > ==
> > Section "ServerLayout"
> >   Identifier "X.org Configured"
> >   Screen  0  "Screen0" 0 0
> >   Screen  1  "Screen1" RightOf "Screen0"
> >   InputDevice"Mouse0" "CorePointer"
> >   InputDevice"Keyboard0" "CoreKeyboard"
> > EndSection
> >
> > Section "Files"
> >   ModulePath   "/usr/lib/xorg/modules"
> >   FontPath "/usr/share/fonts/X11/misc"
> >   # FontPath "/usr/share/fonts/X11/cyrillic"
> >   FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
> >   FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
> >   FontPath "/usr/share/fonts/X11/Type1"
> >   FontPath "/usr/share/fonts/X11/100dpi"
> >   FontPath "/usr/share/fonts/X11/75dpi"
> >   FontPath "built-ins"
> > EndSection
> >
> > Section "Module"
> >   Load  "glx"
> > EndSection
> >
> > Section "InputDevice"
> >   Identifier  "Keyboard0"
> >   Driver  "kbd"
> > EndSection
> >
> > Section "InputDevice"
> >   Identifier  "Mouse0"
> >   Driver  "mouse"
> >   Option"Protocol" "auto"
> >   Option"Device" "/dev/input/mice"
> >   Option"ZAxisMapping" "4 5 6 7"
> > EndSection
> >
> > Section "Monitor"
> >   Identifier   "Monitor0"
> >   VendorName   "Monitor Vendor"
> >   ModelName"Monitor Model"
> > EndSection
> >
> > Section "Monitor"
> >   Identifier   "Monitor1"
> >   VendorName   "Monitor Vendor"
> >   ModelName"Monitor Model"
> > EndSection
> >
> > Section "Device"
> >   ### Available Driver options are:-
> >   ### Values: : integer, : float, : "True"/"False",
> >   ### : "String", : " Hz/kHz/MHz",
> >   ### : "%"
> >   ### [arg]: arg optional
> >   #Option "Accel"  # []
> >   #Option "SWcursor"   # []
> >   #Option "EnablePageFlip" # []
> >   #Option "SubPixelOrder"  # []
> >   #Option "ZaphodHeads"# 
> >   #Option "AccelMethod"# 
> >   #Option "DRI3"   # []
> >   #Option "DRI"# 
> >   #Option "ShadowPrimary"  # []
> >   #Option "TearFree"   # []
> >   #Option "DeleteUnusedDP12Displays" # []
> >   #Option "VariableRefresh"# []
> >   Identifier  "Card0"
> >   # Driver  "amdgpu"
> >   Driver  "modesetting"
> >   BusID   "PCI:9:0:0"
> > EndSection
> >
> > Section "Device"
> >   ### Available Driver options are:-
> >   ### Values: : integer, : float, : "True"/"False",
> >   ### : "String", : " Hz/kHz/MHz",
> >   ### : "%"
> >   ### [arg]: arg optional
> >   #Option "Accel"  # []
> >   #Option "SWcursor"   # []
> >   #Option "EnablePageFlip" # []
> >   #Option "SubPixelOrder"  # []
> >   #Option "ZaphodHeads"# 
> >   #Option "AccelMetho

Re: Debian 10.3: X does not start

[Alex Deucher]

On Wed, Mar 25, 2020 at 12:49 PM Klaus Jantzen  wrote:
>
> Hello,
>
> I installed Debian on a PC with AMD Ryzen 5 3400 G.
>
> My first trials ended with a message
>
> "Cannot run in framebuffer mode ..." from xorg.
>
> Due to some research in the net I am using the following xorg.conf.
> It is basically what I got when I did a "X -configure".
> ==
> Section "ServerLayout"
>  Identifier "X.org Configured"
>  Screen  0  "Screen0" 0 0
>  Screen  1  "Screen1" RightOf "Screen0"
>  InputDevice"Mouse0" "CorePointer"
>  InputDevice"Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
>  ModulePath   "/usr/lib/xorg/modules"
>  FontPath "/usr/share/fonts/X11/misc"
>  # FontPath "/usr/share/fonts/X11/cyrillic"
>  FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
>  FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
>  FontPath "/usr/share/fonts/X11/Type1"
>  FontPath "/usr/share/fonts/X11/100dpi"
>  FontPath "/usr/share/fonts/X11/75dpi"
>  FontPath "built-ins"
> EndSection
>
> Section "Module"
>  Load  "glx"
> EndSection
>
> Section "InputDevice"
>  Identifier  "Keyboard0"
>  Driver  "kbd"
> EndSection
>
> Section "InputDevice"
>  Identifier  "Mouse0"
>  Driver  "mouse"
>  Option"Protocol" "auto"
>  Option"Device" "/dev/input/mice"
>  Option"ZAxisMapping" "4 5 6 7"
> EndSection
>
> Section "Monitor"
>  Identifier   "Monitor0"
>  VendorName   "Monitor Vendor"
>  ModelName"Monitor Model"
> EndSection
>
> Section "Monitor"
>  Identifier   "Monitor1"
>  VendorName   "Monitor Vendor"
>  ModelName"Monitor Model"
> EndSection
>
> Section "Device"
>  ### Available Driver options are:-
>  ### Values: : integer, : float, : "True"/"False",
>  ### : "String", : " Hz/kHz/MHz",
>  ### : "%"
>  ### [arg]: arg optional
>  #Option "Accel"  # []
>  #Option "SWcursor"   # []
>  #Option "EnablePageFlip" # []
>  #Option "SubPixelOrder"  # []
>  #Option "ZaphodHeads"# 
>  #Option "AccelMethod"# 
>  #Option "DRI3"   # []
>  #Option "DRI"# 
>  #Option "ShadowPrimary"  # []
>  #Option "TearFree"   # []
>  #Option "DeleteUnusedDP12Displays" # []
>  #Option "VariableRefresh"# []
>  Identifier  "Card0"
>  # Driver  "amdgpu"
>  Driver  "modesetting"
>  BusID   "PCI:9:0:0"
> EndSection
>
> Section "Device"
>  ### Available Driver options are:-
>  ### Values: : integer, : float, : "True"/"False",
>  ### : "String", : " Hz/kHz/MHz",
>  ### : "%"
>  ### [arg]: arg optional
>  #Option "Accel"  # []
>  #Option "SWcursor"   # []
>  #Option "EnablePageFlip" # []
>  #Option "SubPixelOrder"  # []
>  #Option "ZaphodHeads"# 
>  #Option "AccelMethod"# 
>  #Option "DRI3"   # []
>  #Option "DRI"# 
>  #Option "ShadowPrimary"  # []
>  #Option "TearFree"   # []
>  #Option "DeleteUnusedDP12Displays" # []
>  #Option "VariableRefresh"# []
>  Identifier  "Card1"
>  # Driver  "amdgpu"
>  Driver  "modesetting"
>  BusID   "PCI:9:0:1"
> EndSection
>
> Section "Screen"
>  Identifier "Screen0"
>  Device "Card0"
>  Monitor"Monitor0"
>  SubSection "Display"
>  Viewport   0 0
>  Depth 1
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 4
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 8
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 15
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 16
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 24
>  EndSubSection
> EndSection
>
> Section "Screen"
>  Identifier "Screen1"
>  Device "Card1"
>  Monitor"Monitor1"
>  SubSection "Display"
>  Viewport   0 0
>  Depth 1
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 4
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 8
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>  Depth 15
>  EndSubSection
>  SubSection "Display"
>  Viewport   0 0
>   

Re: Can't use third monitor, Radeon HD 8830M

[Alex Deucher]

On Tue, Sep 11, 2018 at 12:24 PM Eino Virtanen  wrote:
>
> Hello everyone,
>
> I have three monitors. Each connected with DVI cables to a Radeon HD
> 8830M. Two of them are connected with a DVI-DP adapter. The problem is
> that I can only enable two of the monitors simultaneously, otherwise I
> get this error message: "xrandr: Configure crtc 0 failed"

Are you using active or passive DVI->DP adapters?  Are all of the
displays on a single GPU?  Your GPU only has two PLLs for non-DP
displays, so it can only drive two independent sets if display timing.
If you want to use more than 2 non-DP monitors, you need to use the
exact same modeline on at least two of them.  All of the modes you are
trying to set have different timings, so it's not possible:

  1680x1050 (0x81) 146.250MHz -HSync +VSync +preferred
h: width  1680 start 1784 end 1960 total 2240 skew0 clock  65.29KHz
v: height 1050 start 1053 end 1059 total 1089   clock  59.95Hz

  1920x1200 (0x8c) 154.000MHz +HSync -VSync *current +preferred
h: width  1920 start 1968 end 2000 total 2080 skew0 clock  74.04KHz
v: height 1200 start 1203 end 1209 total 1235   clock  59.95Hz

  1680x1050 (0x8f) 119.000MHz +HSync -VSync *current +preferred
h: width  1680 start 1728 end 1760 total 1840 skew0 clock  64.67KHz
v: height 1050 start 1053 end 1059 total 1080   clock  59.88Hz

Try either selecting a modeline that is common across at least two of
the displays, or use randr to add one of the 1680x1050 modelines to
the other connector and hope that the monitor will support it.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: ATI video problem - extremely slow desktop - 100% cpu load

[Alex Deucher]

On Wed, Jun 20, 2018 at 3:54 PM, Vincent Stemen  wrote:
> Hi.
>
> I also posted about this problem on the FreeBSD mailing list.
>
> FreeBSD 11.1-RELEASE
> Motherboard:gigabyte GA-78LMT-USB3 R2
> Video:  Integrated ATI Radeon HD 3000 graphics
>
> I have also tested with two additional ATI cards.
> A Radeon HD 5450 and and older card that shows as
> "RV370 [Radeon X300 SE]" in the PCI info.
>
> Same problem on all of them.
>
> System runs fine with a simple stand alone window manager such as jwm,
> openbox, etc.  But anytime I run a desktop environment that has a panel and/or
> desktop icons, the X desktop takes a very long time to start up and runs
> extremely slow and unresponsive, the pointer jumps instead of moving smoothly,
> and the main Xorg process runs at 100% load on one core.  I have tried several
> different desktops, such as xfce, enlightenment, lumina, etc.  Similar problem
> on all of them.
>
> The weird thing is that, every once in a while, when I launch X, it comes up
> quick and runs fine.  Shut down X and re-run it and it's back doing it again.
> Once it comes up working correctly, it stays working until I restart X.
>
> I have tried re-installing all the ports from X11 and the desktop environments
> from FreeBSD 11 release_1, release_2, quarterly, and latest.  Same problem
> with all of them.
>
> Does anybody have any idea what could be causing this?
>
> I don't know if for sure if this is a FreeBSD or an xorg problem.  Here are
> radeon kernel modules running when running on the Radeon HD 3000.
>
> # kldstat
>
>51 0x82431000 12b4a0   radeonkms.ko
>...
>   101 0x825b9000 103e radeonkmsfw_RS780_pfp.ko
>   111 0x825bb000 5b3f radeonkmsfw_RS780_me.ko
>   121 0x825c1000 1338 radeonkmsfw_R600_rlc.ko
>
> X is using the ati driver from the xf86-video-ati-7.9.0_1,1 package.
>
> The evidence points stongly toward it being an ATI driver problem.  If I edit
> /etc/X11/xorg.conf to use the "vesa" driver rather than the "radeon" driver 
> the
> problem goes away.
>
> But, of course, the vesa driver is low resolution and does not re-initialize 
> the
> console when I exit X.

I don't know how well the radeon driver works on FreeBSD.  If you can
test Linux and it works properly, I guess there is probably some issue
with the FreeBSD driver or some configuration problem on your end.
I'd check your xorg log and kernel output to start with to make sure
everything is loading correctly.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: DPMS in one of two monitors

[Alex Deucher]

On Wed, Jun 20, 2018 at 9:11 AM, Diego Cardinali
 wrote:
> Hello!
> I am using Lubuntu 18.04 64bit with a radeon hd4650 video card and I'm using
> a monitor on vga port and a tv on hdmi.
> I am trying to enable dpms settings only for the vga monitor while disabling
> it for the tv-hdmi
> I did some searches around and came up with this solution: create a
> 10-monitor.conf file to put in /usr/share/X11/xorg.conf.d/ with the
> following text
>
>
> Section "Monitor"
>
> Identifier   "HDMI-0"
>
> Option "RightOf" "VGA-0"
>
> Option  "DPMS" "true"
>
> EndSection
>
>
>
> Section "Monitor"
>
> Identifier   "VGA-0"
>
> Option "LeftOf" "HDMI-0"
>
> Option  "DPMS" "false"
>
> EndSection
>
>
>
>
> Section "ServerFlags"
>
> Option "StandbyTime" "1"
>
> EndSection
>
>
> I used the same identifiers xrandr uses
> I have set a low standbytime so it's easier to check if it works or not.
> At the moment it doesn't work at all, not even in the tv-hdmi output, but
> the ServerFlags section does affect the system (as far as I know checking
> with xset -q)
> You can find my Xorg.0.log at https://pastebin.com/5KB16DJ0 , where I
> noticed
>
> [27.014] (==) RADEON(0): DPMS enabled
>
> any suggestions?
> I tried with xset but it affects both the monitors
>
> Thanks in advance!


There is no way in the X server to only enable DPMS on one monitor.
It's either on or off globally.

Alex

>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Centos 7 and ATI/AMD ES1000

[Alex Deucher]

On Tue, Oct 10, 2017 at 4:40 PM, Luis Feo  wrote:
>
> Hello. I have a system in Centos 7.4, x86-64. The integrated video card is a
> ATI/AMD ES1000. I can´t get raise the Graphics User Interface. The xorg
> system fails. Do you can help me?.
>
>
> In the attachment i put the errors in Xorg.0.log file.

Please open a bug (https://bugs.freedesktop.org) and attach your full
xorg log and dmesg output along with a description of the problem.

Alex

> --
> Luis Feo.
> Instituto de Ciencias de La Tierra.
> Unidad de Informática.
> Caracas, Venezuela.
> 
> Usando el revolucionario cliente de correo electrónico de Opera:
> http://www.opera.com/mail/
>
> ---
> El software de antivirus Avast ha analizado este correo electrónico en busca
> de virus.
> https://www.avast.com/antivirus
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Dell P2715Q Monitor does not wake up after sleep (off, standby, or suspend)

[Alex Deucher]

On Fri, Aug 11, 2017 at 3:08 PM, Greg Gorsuch  wrote:
> Your description sounds about right. Since I do see a message ("Entering
> energy saver mode") come up on the monitor when I move the mouse as I
> mentioned before, this does suggest it has been awakened and becomes
> unrigistered at this point and sees no input anymore (hence the message).
> All the windows are already moved to the other monitor at this point and the
> screen saver seems like it has more or less died (though it does prompt for
> the password and allows me to log in).
>
> I did what you asked, but it didn't really give any useful info since it
> normally takes a while for the monitor to fail to come back up (maybe 5 or
> 10 minutes after I lock the screen even with the sleep time as 1 minutes or
> so).  I kind of already generated the info you may be seeking in my original
> post.
>
> I am wondering if there is some way to just "lock" the setup so that the
> monitor is always there if it is a registration problem, or change things so
> the monitor is not unrigestering itself.

Does the monitor have an option to disable input polling?  Some
monitors rotate through their inputs when they are not getting a
signal to see if one attaches so they can automatically switch to that
input.  This often confuses drivers because the input switching on the
monitor often triggers a hotplug event which looks like the display
has been disconnected to the driver since the monitor has switched to
another input.

Alex


>
>
> On Thu, Aug 10, 2017 at 9:55 AM, Thomas Lübking 
> wrote:
>>
>> On Wed, Aug 09, 2017 at 11:39:06AM -0400, Greg Gorsuch wrote:
>>>
>>> Where are the sleep logistics handled? Is it with the X server, the
>>> NVIDIA
>>> drivers, the Linux Kernel, or somewhere else? Is it possible to capture
>>> the
>>> communications on Windows 10 to identify how it is being handled. I don't
>>> get the feeling it should be that complex to fix or at least implement a
>>> work around since xrander is able to bring the monitor back online.
>>
>>
>> It sounds like when you go dpms off, the monitor unregisters and when
>> you go dpms on, the monitor re-registers.
>> Then some semi-smart randr daemon kicks in and adjusts the layout, but
>> does not so when the monitor comes back.
>>
>> Try to log the setup in the various modes:
>>
>> xset dpms force standby; sleep 10; xrandr --current > ~/randr.standby;
>> xset dpms force suspend; sleep 10; xrandr --current > ~/randr.suspend;
>> xset dpms force off; sleep 10; xrandr --current > ~/randr.off; xset
>> dpms force on
>>
>> Also try the behavior on a "naked" X11 server (no desktop session, only
>> an xterm) to see whether some client or the server adjusts the randr
>> setup.
>>
>> Cheers,
>> Thomas
>
>
>
>
> --
> Greg Gorsuch
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Getting a separate DISPLAY for each screen connected

[Alex Deucher]

On Fri, Aug 11, 2017 at 1:29 PM, Tor Rune Skoglund  wrote:
> Dear List,
>
> Been digging a lot to try to find a good solution for my problem here:
>
> We are using xorg for an "embedded" system, on which we would like to get a
> separate DISPLAY setting for each of the computer's gfx connectors. As it is
> today, by default HDMI1, HDMI2 and HDMI3 are cloned, By using xrandr and the
> left-of and right-of options on the connectors, we are able to extend the
> size to span across all the monitor connectors, and the total size of Screen
> 0 gets adjusted automatically. (Actually quite impressed by this!)
>
> However, this is actually not really what we want. We would like each HDMIx
> to be a separate display, i.e. HDMI1 should be :0.0, HDMI2 should be :0.1
> and HDMI3 should be :0.2 .
>
> This is pure X, no window manager.
>
> I guess this is a simple config option somewhere I will be very grateful
> if someone could point me in the right direction. :)

Google for zaphod or xinerama configuration.  If you read a xinerama
howto, the configuration is the same, just don't enable the xinerama
extension.  See here for a sample config:
https://wiki.archlinux.org/index.php/multihead#Xinerama

Alex

>
> System info:
>
> Intel Kaby Lake chipset: Driver loaded during kernel boot:
> # dmesg | grep i915
> [0.947501] [drm] Finished loading i915/kbl_dmc_ver1_01.bin (v1.1)
> Gentoo - kernel 4.9.41
> xorg-server verison 1.19.3
> mesa version 17.0.6
> No xorg.conf (everything autodetected)
> No errors or (relevant) warnings i /var/log/Xorg.0.log. (Except missing
> fonts warnings)
> Outputs are assigned during xinit:
> [   476.723] (--) intel(0): Output HDMI1 using initial mode 1600x1200 on
> pipe 0
> [   476.723] (--) intel(0): Output HDMI2 using initial mode 1280x1024 on
> pipe 1
> [   476.723] (--) intel(0): Output HDMI3 using initial mode 1680x1050 on
> pipe 2
> xrandr --query:
>
> # DISPLAY=:0 xrandr --query
> Screen 0: minimum 8 x 8, current 4560 x 1200, maximum 32767 x 32767
> DP1 disconnected (normal left inverted right x axis y axis)
> DP2 disconnected (normal left inverted right x axis y axis)
> DP3 disconnected (normal left inverted right x axis y axis)
> HDMI1 connected 1600x1200+1280+0 (normal left inverted right x axis y axis)
> 410mm x 310mm
>1600x1200 60.00*+
>1280x1024 60.02
>1280x960  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> HDMI2 connected primary 1280x1024+0+0 (normal left inverted right x axis y
> axis) 380mm x 300mm
>1280x1024 60.02*+  75.02
>1152x864  75.00
>1024x768  75.0360.00
>800x600   75.0060.32
>640x480   75.0059.94
>720x400   70.08
> HDMI3 connected 1680x1050+2880+0 (normal left inverted right x axis y axis)
> 470mm x 300mm
>1680x1050 59.95*+
>1280x1024 75.0260.02
>1152x864  75.00
>1024x768  75.0360.00
>800x600   75.0060.32
>640x480   75.0059.94
>720x400   70.08
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
>
> Best regards,
> Tor Rune Skoglund, t...@fourc.eu
>
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Setting new mode for 2nd monitor fails

[Alex Deucher]

On Fri, Jun 9, 2017 at 5:07 PM, Andrej van der Zee
 wrote:
> Hi Thomas,
>
> Just tried, also does not work. Anyways, I just realized that in Unity on
> Ubuntu I am running 2560x1440 on my 2nd monitor (mac retina 4k screen) but
> all icons are in right size. Somehow it sets the correct dpi I guess.
>
> Just wanted to switch to i3 and all icons are too big on my 2nd monitor. Any
> idea how I can fix I3 to have my second display use the proper icon sizes?
> Probably I am on the wrong mailing list ;-)
>
>
> $ gtf 3840 2160 60
>
>   # 3840x2160 @ 60.00 Hz (GTF) hsync: 134.10 kHz; pclk: 712.34 MHz
>   Modeline "3840x2160_60.00"  712.34  3840 4152 4576 5312  2160 2161 2164
> 2235  -HSync +Vsync

Monitor likely does not support the gtf 3840x2160 modeline, the clock
is way too high.  Try cvt.  It's also possible the monitor does not
support 3840x2160 at all, otherwise it would be exposed already.

Alex

>
> andrej:/var/log$ xrandr --newmode "3840x2160_60.00"  712.34  3840 4152 4576
> 5312  2160 2161 2164 2235  -HSync +Vsync
> andrej:/var/log$  xrandr --addmode DP1  "3840x2160_60.00"
> andrej:/var/log$ xrandr --verbose --output DP1 --mode  "3840x2160_60.00"
> screen 0: 6720x2160 1777x571 mm  96.05dpi
> crtc 1: 3840x2160_60.00  60.00 +2880+0 "DP1"
> xrandr: Configure crtc 1 failed
> crtc 0: disable
> crtc 1: disable
> crtc 2: disable
> crtc 3: disable
> screen 0: revert
> crtc 0: revert
> crtc 1: revert
> crtc 2: revert
> crtc 3: revert
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Setting new mode for 2nd monitor fails

[Alex Deucher]

On Fri, Jun 9, 2017 at 12:49 PM, Andrej van der Zee
 wrote:
> Hi,
>
> Thanks for your prompt reply. Attached dmesg and Xorg.log.

I'm not familiar with the display capabilities of various intel chips
unfortunately.  I'd guess it has something to do with the level of DP
supported by the GPU.

Alex

>
> Thanks,
> Andrej
>
> On Fri, Jun 9, 2017 at 6:46 PM, Alex Deucher  wrote:
>>
>> On Fri, Jun 9, 2017 at 12:39 PM, Andrej van der Zee
>>  wrote:
>> > Hi,
>> >
>> > My external monitors resolution is too low, but xrandr does not show any
>> > higher resolution. I am trying to create a new mode, but it falis to
>> > start
>> > like below. How can I set the resolution of my external monitor to
>> > 4096x2160?
>>
>> I suspect the driver has removed any modes that it can't support due
>> to a lack of memory bandwidth or a support level (e.g., the 4K modes
>> on your monitor require DP 1.2 and your card only supports DP 1.1).
>> What chip is this?  You'll probably want to provide your xorg log and
>> dmesg output.
>>
>> Alex
>>
>> >
>> > Thanks,
>> > Andrej
>> >
>> > $ xrandr
>> > Screen 0: minimum 8 x 8, current 5440 x 1800, maximum 32767 x 32767
>> > eDP1 connected primary 2880x1800+0+0 (normal left inverted right x axis
>> > y
>> > axis) 331mm x 207mm
>> >2880x1800 59.99*+
>> >2560x1600 60.00
>> >2048x1536 60.00
>> >1920x1440 60.00
>> >1856x1392 60.01
>> >1792x1344 60.01
>> >1920x1200 60.0059.95
>> >1920x1080 59.93
>> >1600x1200 60.00
>> >1680x1050 60.0059.9559.88
>> >1600x1024 60.17
>> >1400x1050 59.98
>> >1280x1024 60.02
>> >1440x900  59.8960.00
>> >1400x900  60.00
>> >1280x960  60.00
>> >1360x768  59.8059.96
>> >1280x800  60.00
>> >1152x864  60.00
>> >1024x768  60.00
>> >800x600   60.3256.25
>> >640x480   59.94
>> > DP1 connected 2560x1440+2880+0 (normal left inverted right x axis y
>> > axis)
>> > 597mm x 336mm
>> >2560x1440 59.95*+
>> >1280x720  59.86
>> > DP2 disconnected (normal left inverted right x axis y axis)
>> > HDMI1 disconnected (normal left inverted right x axis y axis)
>> > HDMI2 disconnected (normal left inverted right x axis y axis)
>> > HDMI3 disconnected (normal left inverted right x axis y axis)
>> > VGA1 disconnected (normal left inverted right x axis y axis)
>> > VIRTUAL1 disconnected (normal left inverted right x axis y axis)
>> >
>> > $ xrandr --newmode "4096x2160_60.00"  759.54  4096 4424 4880 5664  2160
>> > 2161
>> > 2164 2235  -HSync +Vsync
>> > $ xrandr --addmode DP1 4096x2160_60.00
>> > $ xrandr --verbose --output DP1 --mode  4096x2160_60.00
>> > screen 0: 5440x2160 1438x571 mm  96.05dpi
>> > crtc 2: 4096x2160_60.00  60.00 +0+0 "DP2"
>> > xrandr: Configure crtc 2 failed
>> > crtc 0: disable
>> > crtc 1: disable
>> > crtc 2: disable
>> > crtc 3: disable
>> > screen 0: revert
>> > crtc 0: revert
>> > crtc 1: revert
>> > crtc 2: revert
>> > crtc 3: revert
>> >
>> >
>> >
>> > ___
>> > xorg@lists.x.org: X.Org support
>> > Archives: http://lists.freedesktop.org/archives/xorg
>> > Info: https://lists.x.org/mailman/listinfo/xorg
>> > Your subscription address: %(user_address)s
>
>
>
>
> --
> Andrej van der Zee
> Oranje-Vrijstaatkade 49
> 1093KS Amsterdam
> +31-(0)6-8133-9388
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Setting new mode for 2nd monitor fails

[Alex Deucher]

On Fri, Jun 9, 2017 at 12:39 PM, Andrej van der Zee
 wrote:
> Hi,
>
> My external monitors resolution is too low, but xrandr does not show any
> higher resolution. I am trying to create a new mode, but it falis to start
> like below. How can I set the resolution of my external monitor to
> 4096x2160?

I suspect the driver has removed any modes that it can't support due
to a lack of memory bandwidth or a support level (e.g., the 4K modes
on your monitor require DP 1.2 and your card only supports DP 1.1).
What chip is this?  You'll probably want to provide your xorg log and
dmesg output.

Alex

>
> Thanks,
> Andrej
>
> $ xrandr
> Screen 0: minimum 8 x 8, current 5440 x 1800, maximum 32767 x 32767
> eDP1 connected primary 2880x1800+0+0 (normal left inverted right x axis y
> axis) 331mm x 207mm
>2880x1800 59.99*+
>2560x1600 60.00
>2048x1536 60.00
>1920x1440 60.00
>1856x1392 60.01
>1792x1344 60.01
>1920x1200 60.0059.95
>1920x1080 59.93
>1600x1200 60.00
>1680x1050 60.0059.9559.88
>1600x1024 60.17
>1400x1050 59.98
>1280x1024 60.02
>1440x900  59.8960.00
>1400x900  60.00
>1280x960  60.00
>1360x768  59.8059.96
>1280x800  60.00
>1152x864  60.00
>1024x768  60.00
>800x600   60.3256.25
>640x480   59.94
> DP1 connected 2560x1440+2880+0 (normal left inverted right x axis y axis)
> 597mm x 336mm
>2560x1440 59.95*+
>1280x720  59.86
> DP2 disconnected (normal left inverted right x axis y axis)
> HDMI1 disconnected (normal left inverted right x axis y axis)
> HDMI2 disconnected (normal left inverted right x axis y axis)
> HDMI3 disconnected (normal left inverted right x axis y axis)
> VGA1 disconnected (normal left inverted right x axis y axis)
> VIRTUAL1 disconnected (normal left inverted right x axis y axis)
>
> $ xrandr --newmode "4096x2160_60.00"  759.54  4096 4424 4880 5664  2160 2161
> 2164 2235  -HSync +Vsync
> $ xrandr --addmode DP1 4096x2160_60.00
> $ xrandr --verbose --output DP1 --mode  4096x2160_60.00
> screen 0: 5440x2160 1438x571 mm  96.05dpi
> crtc 2: 4096x2160_60.00  60.00 +0+0 "DP2"
> xrandr: Configure crtc 2 failed
> crtc 0: disable
> crtc 1: disable
> crtc 2: disable
> crtc 3: disable
> screen 0: revert
> crtc 0: revert
> crtc 1: revert
> crtc 2: revert
> crtc 3: revert
>
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: [ANNOUNCE] xf86-video-ati 7.9.0

[Alex Deucher]

On Thu, Mar 16, 2017 at 2:25 PM, Adam Jackson  wrote:
> On Thu, 2017-03-16 at 10:59 +0100, poma wrote:
>
>> There are two applicable patches within Fedora:
>> https://src.fedoraproject.org/cgit/rpms/xorg-x11-drv-ati.git/commit/fix-dri-removal.patch?id=d5f48e7d5b6c
>
> An artifact of Fedora trying to not build DRI1. It's a fix in the wrong
> place, xserver should define the appropriate symbols if any DRI is
> built.
>
>> https://src.fedoraproject.org/cgit/rpms/xorg-x11-drv-ati.git/commit/radeon-6.12.2-lvds-default-modes.patch?id=9495e5b874d8
>
> Mostly a hack for LCDs that only claim one supported resolution and
> desktop environments too chicken to let you set arbitrary modes from
> the display control panel. Again, not really thrilled with the
> implementation of it, might be better solved in another place.

Do you have a specific test case this fixes?  The kernel driver always
adds the common modes to LVDS connectors, so they should be there.

Alex

>
>> Are these patches required, if so, care to explain?
>
> "Required", no. Nice to have, arguably.
>
> - ajax
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

2017 X.Org Foundation Membership deadline for voting in the election

[Alex Deucher]

The 2017 X.Org Foundation elections are rapidly approaching. We will
be forwarding the election schedule and nominating process to the
membership shortly.

Please note that only current members can vote in the upcoming
election, and that the deadline for new memberships or renewals to
vote in the upcoming election is 05 March 2017 at 23:59 UTC.

If you are interested in joining the X.Org Foundation or in renewing
your membership, please visit the membership system site at:
https://members.x.org/

Alex Deucher, on behalf of the X.Org elections committee
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

X.Org Foundation Membership Renewal

[Alex Deucher]

On January 19th all xorg members were expired as part of the regular
process to remove inactive members.  If you would still like to be a
member of the X.Org Foundation, please renew your membership.  To
renew or to become a first time member, go to https://members.x.org/ .
For renewals, log in and click the renewal link.  For new members,
click the Join Now link.  The X.org Foundation is a non-profit
organization under the SPI umbrella which acts as a steward for the X
Window System and related projects.  Board elections are coming up so
renew or join today!

Thanks!

Alex Deucher
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xrandr: cannot find output 0x95

[Alex Deucher]

On Thu, Oct 6, 2016 at 8:25 PM, John Lewis  wrote:
> On 10/05/2016 10:02 AM, Alex Deucher wrote:
>> On Wed, Oct 5, 2016 at 7:54 AM, John Lewis  wrote:
>>> On 10/05/2016 03:08 AM, Michel Dänzer wrote:
>>>> On 04/10/16 09:40 PM, John Lewis wrote:
>>>>> It was the R7 360 that was causing the issue. Dual screens work just
>>>>> fine with Intel HD Graphics 4000.
>>>> Please attach the Xorg log file corresponding to the problem with the
>>>> Radeon GPU.
>>>>
>>>>
>>> It is now enclosed.
>> This looks wrong:
>> [383410.848] (II) modesetting(0): Output DisplayPort-3 disconnected
>> [383410.848] (II) modesetting(0): Output HDMI-3 connected
>> [383410.848] (II) modesetting(0): Output DVI-0 disconnected
>> [383410.848] (II) modesetting(0): Output DVI-0 connected
>> [383410.848] (II) modesetting(0): Using exact sizes for initial modes
>> [383410.848] (II) modesetting(0): Output HDMI-3 using initial mode 1920x1080
>> [383410.848] (II) modesetting(0): Output DVI-0 using initial mode 1920x1080
>>
>> There are two DVI-0 connectors.  Can you try the radeon driver rather
>> than modesetting?  Also please attach your dmesg output.
>>
>> Alex
>>
>>>
>>> ___
>>> xorg@lists.x.org: X.Org support
>>> Archives: http://lists.freedesktop.org/archives/xorg
>>> Info: https://lists.x.org/mailman/listinfo/xorg
>>> Your subscription address: %(user_address)s
>
> I have lshw output from when I was still using the card a week ago. I
> still need to look up how to force a driver. I won't be able to do any
> test until Saturday Night.
>

Please include your dmesg output.  In general, it's probably best to
file a bug (https://bugs.freedesktop.org) and attach the relevant
files there so we can track this in one place.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xrandr: cannot find output 0x95

[Alex Deucher]

On Wed, Oct 5, 2016 at 7:54 AM, John Lewis  wrote:
> On 10/05/2016 03:08 AM, Michel Dänzer wrote:
>> On 04/10/16 09:40 PM, John Lewis wrote:
>>> It was the R7 360 that was causing the issue. Dual screens work just
>>> fine with Intel HD Graphics 4000.
>> Please attach the Xorg log file corresponding to the problem with the
>> Radeon GPU.
>>
>>
> It is now enclosed.

This looks wrong:
[383410.848] (II) modesetting(0): Output DisplayPort-3 disconnected
[383410.848] (II) modesetting(0): Output HDMI-3 connected
[383410.848] (II) modesetting(0): Output DVI-0 disconnected
[383410.848] (II) modesetting(0): Output DVI-0 connected
[383410.848] (II) modesetting(0): Using exact sizes for initial modes
[383410.848] (II) modesetting(0): Output HDMI-3 using initial mode 1920x1080
[383410.848] (II) modesetting(0): Output DVI-0 using initial mode 1920x1080

There are two DVI-0 connectors.  Can you try the radeon driver rather
than modesetting?  Also please attach your dmesg output.

Alex

>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: compositing enabled with Radeon mobility X300

[Alex Deucher]

On Fri, Aug 5, 2016 at 5:11 AM, Jethro Tull  wrote:
> From: Michel Dänzer [mic...@daenzer.net]
> Sent: Friday, August 5, 2016 1:41 AM
> To: Jethro Tull
> Cc: x...@freedesktop.org
> Subject: Re: compositing enabled with Radeon mobility X300
>
> On 05.08.2016 06:23, Jethro Tull wrote:
>> I'm using the kernel 4.4.14 with XFCE 4.12, as written in the subject
>> my GPU is a Radeon mobility X300 and the driver used is the open
>> source "radeon".
>>
>> I noticed that enabling compositing was resulting in very slow
>> windows manipulations like dragging, resizing, browsing them with Alt
>> + tab. It takes nearly 2 seconds to display the big contextual menu
>> when starting to browse through the windows. And I also noticed that
>> using an extended desktop on a second monitor was leading to some
>> windows not being refreshed resulting in a nearly scrambled desktop
>> after some time of use with several graphical programs. I also
>> noticed some similar problems with the terminal.
>
> Please provide the corresponding Xorg log file.
>
>
> --
> Earthling Michel Dänzer   |   http://www.amd.com
> Libre software enthusiast | Mesa and X developer
>
> here it is:

Please include the full log and your dmesg output.  How many displays
are you using?  What resolution(s)?

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Can I change the X rotate the xf86-video-fbdev during execution ?

[Alex Deucher]

Runtime rotation using randr only works with randr 1.2+ capable drivers.  I
don't think the fbdev supports that.  On supported drivers:

xrandr --output  --rotate right|left|inverted|normal

Alex

On Thu, May 26, 2016 at 1:46 AM, 권태영  wrote:

>
>
> Good morning.
>
>
>
> I have a problem in using the X11.
>
>
>
>
> Below is my /etc/X11/xorg.conf.d/1-fbdev.conf.
>
>
>
> /etc/X11/xorg.conf.d/1-fbdev.conf
>
> 
>
> Section "Device"
>
>  Identifier "LCD"
>
>  Driver "fbdev"
>
>  Option "fbdev" "/dev/fb0"
>
>  Option "Rotate" "UD"
>
> EndSection
>
>
>
>
>
>
>
> I would like to change the Rotate values ??in real time (without
> restarting the X)
>
>
>
> ex)Option "Rotate" "CW"
>
>
>
>
>
> How do I apply during the execution X by changing the settings of the
> xf86-video-fbdev in real time?
>
>
>
>
>
> I looked up the relevant article in the stackoverflow question. (
> http://unix.stackexchange.com/questions/285586/can-i-change-the-x-rotate-the-xf86-video-fbdev-during-execution
> )
>
>
>
> The inexperienced English 'm sorry :)
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: https://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: how to convince Xorg server my discrete graphics Radeon 8970M card is connected when my Integrated Graphics (i915) card is also active ?

[Alex Deucher]

On Sun, Apr 24, 2016 at 1:00 PM, Jason Vas Dias
 wrote:
> I have a " CLEVO/KAPOK Computer Device [1558:5106] "
> laptop with an " Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz "
> CPU, 16GB RAM, 1TB HD, 256M SDD. and a 1920x1080 LCD panel ,
> and these graphics cards:
>
> $ lspci -nn | grep VGA
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen
> Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
> 01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
> [AMD/ATI] Neptune XT [Radeon HD 8970M] [1002:6801]
>
> I have built the latest stable versions of gcc, glibc, binutils,
> kernel (4.4+) etc,
> broadly in line with the Linux From Scratch book (LFS), and ALL xorg 
> libraries,
> protos, essential applications & utilities, and the Xorg Server + Mesa +
> xf86-video-ati + xf86-video-intel + requisite drivers from GIT checkouts
> to the latest tagged commit (stable version) - so I'm trying to run :
> linux: 4.5.2
> glibc:  2.23
> gcc  :  5.3.0
> Mesa::  11.2.0
> Xserver :  1.18.3
> xf86-video-ati :  7.7.0
> xf86-video-intel: 2.6.99.902
>
> But so far I am unable to get the 8970M Radeon card to go into graphics mode -
> the xserver quits at the error : "No modes." from hw/xfree86/xf86Crtc.c  .
>
> I have got past the firmware load stage - the card loads firmware from
> radeon/pitcairn_pfp.bin OK .
>
> So far the code has only gone into graphics mode when controlled by the FGLRX
> driver, installed into an Oracle Enterprise Linux 7 (OEL7) installation on a
> separate partition from the one I'm trying to get running .
>
> I am running Linux 4.5.2 stable with kernel arguments:
>
>   radeon.modeset=1 video=1920x1080@60e fbcon=map:01 \
>   drm_kms_helper.edid_firmware=edid/1920x1080.bin
>
> I have generated a 1920x1080.bin EDID file to be loaded by xorg.conf from
> the EDID values posted to the Xorg.0.log file by the FGLRX driver:
>
> $ tail -n +150 /var/log/Xorg.0.log | head -n 9
> [13.210] (II) fglrx(0): EDID (in hex):
> [13.210] (II) fglrx(0): 00000daeb115
> [13.210] (II) fglrx(0): 01160104902213780231d59f56589527
> [13.210] (II) fglrx(0): 1550540001010101010101010101
> [13.210] (II) fglrx(0): 010101010101963b803271383e405a3c
> [13.210] (II) fglrx(0): 690058c2101a9b2580ee70382340
> [13.210] (II) fglrx(0): 3523350058c2101a00fe0056
> [13.210] (II) fglrx(0): 434d3858024e31353648470a
> [13.211] (II) fglrx(0): 41319e02010a2025
>
>
> So I did:
>
> $ tail -n +151 /var/log/Xorg.0.log | head -n 8  |
> sed -r 's/^.*[[:space:]]+//' | tr -d '\n'  |
> perl -e 'while(<>){ while( $_ =~ /([0-9a-f][0-9a-f])/g){
> $v=eval "0x$1"; print pack("C",$v); } }'  \
>> /tmp/neptune_edid.bin
>
> so that should give me a loadable EDID ? But no attempts to force load of
> the EDID have any affect on the outcome, which is always that Xorg prints
> logs , when run with a command like :
>
> $ { echo ON >/sys/kernel/debug/vgaswitcheroo/switch;
>echo DDIS >/sys/kernel/debug/vgaswitcheroo/switch;
>Xorg  -logverbose 7 -verbose 7 :0 vt04 ||
>   { echo ON >/sys/kernel/debug/vgaswitcheroo/switch;
> echo IGP >/sys/kernel/debug/vgaswitcheroo/switch; } ; } &
>  ( sleep 3; cat /sys/kernel/debug/vgaswitcheroo/switch > \
>~/vga_switcheroo_switch_last;
>   xterm &
>  )
>
> ( this command attempts to switch to the Radeon driver with vga_switcheroo
>   when the X Server goes into graphics mode)
>
> the logs always end with :
>
> [  1503.958] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
> [  1503.958] (II) Module glamoregl: vendor="X.Org Foundation"
> [  1503.958]compiled for 1.18.3, module version = 0.6.0
> [  1503.958]ABI class: X.Org ANSI C Emulation, version 0.4
> [  1503.958] (II) glamor: OpenGL accelerated X.org driver based.
> [  1504.023] (II) glamor: EGL version 1.4 (DRI2):
> [  1504.023] (II) RADEON(0): glamor detected, initialising EGL layer.
> [  1504.023] (II) RADEON(0): KMS Color Tiling: enabled
> [  1504.023] (II) RADEON(0): KMS Color Tiling 2D: enabled
> [  1504.024] (II) RADEON(0): KMS Pageflipping: enabled
> [  1504.024] (II) RADEON(0): SwapBuffers wait for vsync: enabled
> [  1504.024] (II) RADEON(0): Initializing outputs ...
> [  1504.024] (II) RADEON(0): 0 crtcs needed for screen.
> [  1504.024] (II) RADEON(0): Allocated crtc nr. 0 to this screen.
> [  1504.024] (II) RADEON(0): Allocated crtc nr. 1 to this screen.
> [  1504.024] (II) RADEON(0): Allocated crtc nr. 2 to this screen.
> [  1504.024] (II) RADEON(0): Allocated crtc nr. 3 to this screen.
> [  1504.024] (II) RADEON(0): Allocated crtc nr. 4 to this screen.
> [  1504.024] (II) RADEON(0): Allocated crtc nr. 5 to this screen.
> [  1504.024] (WW) RADEON(0): No outputs definitely connected, trying again...
> [  1504.024] (WW) RADEON(0): Unable to find connected outputs -
> setting 1024x768 initial framebuffer
> [  1504.024] (II) RADEON(0):

Re: X.Org Endless Vacation of Code

[Alex Deucher]

On Thu, Mar 31, 2016 at 9:45 PM, Darren Parkinson
 wrote:
> Hello, I am darren Parkinson a student from Jamaica accepted and enrolled in
> Computer Science at the University of Technology in Jamaica. I am a
> self-motivated learner, I currently teach myself to code in C/C++ and find
> no problem, and I am also a team player. I have taken interest in X.Org
> Endless Vacation of Code (EVoC) program and I wish to know where I go about
> in application to the program.

Thank you for your interest!  For more information and requirements,
please see the following page:
http://www.x.org/wiki/XorgEVoC/
The most important part is to get involved in a project your are
interested in and start to learn and understand the code.  Get
involved with the community start to work on the code.  Hopefully you
will find a project that interests you and you can write up a proposal
for what you want to accomplish.  In addition, you will need to help
find a mentor from the project to help guide you.  If you have any
questions, don't hesitate to ask!

Thanks,

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: xserver-xorg-ati does not reactivate monitor after hibernate

[Alex Deucher]

On Mon, Feb 22, 2016 at 1:13 PM, Shawn H Corey  wrote:
>
> I'm running Linux Mint 17.2 with a Radeon HD 5770 card. When I restart
> the computer after hibernating, the monitor remains in low-energy mode.
> That means it is not receiving a signal from the card.
>
> I have tried pressing Ctrl+Alt+Del, which should bring up the Quit
> dialog with the Shutdown button as focus. And sure enough, after I
> press RETURN, the computer shuts down.
>
> I have also tried Ctrl+Alt+F1 but the monitor remains off. If I type
> blindly, I can log in and enter `sudo shutdown -r now` and sure enough,
> the computer reboots.
>
> Everything seems to be working but the monitor signal. What can I do to
> fix this?

File a bug:
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI
Select DRM/Radeon and attach your xorg log and dmesg output.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

GSoC Ideas!

[Alex Deucher]

Hi everyone!

It's that time of year again.  Time to start coming up with GSoC
ideas.  Martin and I are organizing this year's Xorg entry.  We need
to fill in our ideas page with some good possible projects for
students.  The project ideas should be something that a student could
accomplish over the summer so keep the scope focused.  Please use the
templates on
http://www.x.org/wiki/SummerOfCodeIdeas/ and update the wiki or post
the ideas on the mailing list.  Martin and I will update the page as
the ideas come in.

Thanks!

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Video option for a big endian machine?

[Alex Deucher]

On Wed, Feb 11, 2015 at 3:53 AM,   wrote:
> Hello.
>
> I'm looking for a PCI or AGP video card that would work on a Linux port for a 
> big endian architecture (HP PA-RISC). Unfortunately the stock video options 
> (ATI FireGL X1 and X3) give an incredibly slow unaccelerated 2D due to 
> failure to kickstart the command processor (radeon open source driver). 
> Neither folks from linux-parisc@ nor from dri-devel@ camps know how to fix 
> this.
>

The X1 and X3 are really old asics and the risc specific versions
tended to have special firmware for that platform that the open driver
does not handle properly.  You might have better luck using a more
modern GPU (e.g., an R5xx or newer based asic) with an x86 vbios.


Alex

> Are there any other options that should get a good accelerated 2D or better 
> 3D and theoretically should work on a subj (big endian byte order, looks like 
> coherent memory and all I/O is going through IOMMU chip)?
>
> How about nouveau or anything else on non-x86 arch? What people are using on 
> POWER machines for example?
>
> Thanks much for any help!
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Dual screen issues with Radeon X1250 on HP t5730

[Alex Deucher]

On Tue, Jan 20, 2015 at 5:16 AM, Jeffrey Langerak  wrote:
> Hi,
>
>> Does disabling ColorTiling2D or ColorTiling work around the problem? If
>> not, please provide the corresponding Xorg log file.
>
> Disabling the "ColorTiling" option seemed to fix the issue, according to the
> "radeon" manpage this should default to off for this chipset (RS690), but X
> will default it to on. Forcing it to "off" was sufficient and dual screen is
> now working! ColorTiling2D is a safe option for this chip and may be set to
> on.

You may have an outdated man page.  ColorTiling2D has no affect on that asic.

>
> Now that we are discussing this, are there any other options that are useful
> to place in the xorg.conf file to boost the speed of the GPU like
> acceleration enhancements?
>
> One other thing I noticed and is probably because of the VRAM limitation of
> 32MB is that when using the 2 full-HD monitors is that the display sometimes
> shows some interlacing and the monitor connected to the DVI port will loose
> the connection for about a second. Any thougths about that?

Probably underflow to the displays due to memory bandwidth contention
or a problem with the watermark setup on the displays.  Does setting
radeon.disp_priority=2 on the kernel command line in grub help?  I'm
not sure there is enough memory bandwidth to drive two full HD
displays on that asic.

Alex

>
> Someone asked about the VRAM limit, this is fixed because the machine is a
> thin client, the bios does not allow any changes herein, I can only set the
> "vmalloc" parameter when booting the kernel.
>
> Thanks again!
>
> Kind regards,
>
> Jeffrey Langerak
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Xorg 7.6_1 crashes with ATI Mach64 GR Dell FP 2001 using VGA connector

[Alex Deucher]

On Thu, Jan 15, 2015 at 11:17 PM, Felix Miata  wrote:
> x...@lists.killian.com composed on 2015-01-15 18:40 (UTC-0800):
>
>> I've got an old 1U server running openSUSE 13.2 which comes with Xorg
>> 7.6_1. Most of the time it is headless, but I would like to be able to use
>> X occasionally. Unfortunately out of the box the X server crashes.
>
>> The Monitor is a Dell 2001 FP, which is natively 1600x1200, but since this
>> is over a D-sub connector, I need to use 1024x768 (probably 60Hz, or maybe
>> 75Hz).
>
> Why is that so?
>
> My Dell 2000FP, which is natively 1600x1200, made January 2003, does all
> supported modes over both D-sub and DVI using various ATI, Intel & Nvidia
> gfxchips newer than yours. I don't have any Mach64 cards I could try though.

A lot of mach64 server chips only had 2 or 4 MB of vram.  Not enough
for 1600x1200.

>
>> This works fine in the OS install and GRUB2, but Xorg just crashes after
>> the newly installed system boots. I am looking for suggestions on xorg.conf.d
>> entries that will make it work. I have tried a lot of things, including using
>> the vesa driver and ati driver,
>
> I dont' know that mach64 was ever supported by the "ati" driver. A mach64
> driver is on the mirrors, and almost certainly requires KMS be disabled.
>

The ati driver is a wrapper that loads either radeon, r128, or mach64
depending on the pci id.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Dual screen issues with Radeon X1250 on HP t5730

[Alex Deucher]

On Wed, Jan 14, 2015 at 4:59 AM, Jeffrey Langerak
 wrote:
> Hi all,
>
> I have a HP t5730 thin client, lightly converted to a fat client sporting the 
> following specs:
>
> AMD Turion X2 TL-58 1,9GHz CPU
> 2GB 800MHz RAM
> 32MB Radeon X1250 GPU
> 8GB DOM flash disk
>
> OS'es tested:
> Ubuntu 12.04
> Ubuntu 14.04
> Ubuntu 14.10
> Bodhi Linux (testing)
> Fedora 20
> Manjaro 20 (KDE and XFCE edition)
> Point Linux (stable and testing)
> Linux Mint 17.1 (XFCE and KDE edition)
> Windows 7
> Windows 8.1
>
> Based on these specs this makes the device perfect for running Linux and is 
> running well. But...
>
> Using Windows 7 and 8.1 on the HP works as expected using 1 monitor or 2 
> monitors using the old Catalyst driver from Vista supplied by AMD.
>
> When using one of the mentioned Linux systems it works as expected by using 1 
> monitor and attaching a 2nd monitor will work but only in mirroring mode. 
> When I select that I want to extend the desktop indeed extends but the output 
> on both screens is completely garbled and completely unusable, the strange 
> part is that my cursor is the only thing being correctly rendered and works 
> on the extended desktop. The fun fact is that the symptom with the garbled 
> screen is happening on all tested Linux systems and the garbling looks 
> exactly the same, I'm suspecting a driver issue of config issue here.
>
> I've tried the radeonhd and radeon driver and both have the same issue, I've 
> even tried using a custom xorg.conf file with additional tweaks and settings, 
> even enabling or disabling compositing did not make a difference and 
> switching between rendering methods EXA and XAA resulted in the same garbled 
> output.
>
> My custom xorg.conf is below:
>
> Section "ServerLayout"
>Identifier   "Main Layout"
>Screen  "RadeonHD Screen"
>InputDevice   "USB Mouse"
>InputDevice   "Built-in Keyboard"
>Option   "AIGLX" "true"
> EndSection
>
> Section "Files"
>FontPath   "/usr/share/fonts/X11/Type1"
>FontPath   "/usr/share/fonts/X11/misc"
> EndSection
>
> Section "Module"
> Load  "i2c"
> Load  "bitmap"
> Load  "ddc"
> Load  "dri"
> Load  "extmod"
> Load  "freetype"
> Load  "glx"
> Load  "int10"
> Load  "vbe"
> EndSection
>
> Section "ServerFlags"
>Option  "EstimateSizesAggresively"   "4"
>Option  "AIGLX"  "on"
> EndSection
>
> Section "InputDevice"
>Identifier   "USB Mouse"
>Driver  "mouse"
>Option  "ZAxisMapping"   "4 5"
>Option  "Protocol"   "ImPS/2"
>Option  "Device"   "/dev/input/mice"
>Option  "Emulate3Buttons"
> EndSection
>
> Section "InputDevice"
>Identifier   "Built-in Keyboard"
>Driver  "keyboard"
>Option  "AutoRepeat"   "300 40"
>Option  "XkbModel"   "pc105"
> EndSection
>
> Section "Monitor"
>Identifier   "Built-in Monitor"
>Option  "ModelName"   "Built-in HP Monitor"
>Option "AddARGBGLXVisuals" "True"
> EndSection
>
> Section "Device"
>Identifier   "ATI Radeon Xpress 1250"
>Driver   "radeon"
>Option   "DRI"
>Option   "DRI2"
>Option   "ColorTiling"   "on"
>Option   "ColorTiling2D" "on"
>Option   "EnablePageFlip""on"
>Option   "AccelMethod"   "EXA"
>Option   "GARTSize"  "128"
>Option   "SwapbuffersWait"   "off"
>Option   "AccelDFS"  "on"
>Option   "RenderAccel"   "on"
>Option   "NoAccel"   "off"
>Option   "MigrationHeuristics"   "greedy"
>Option   "SWcursor"  "off"
>Option   "HWCursor"  "on"
>Option   "DisableGLXRootClipping""on"
>Option   "EXAPixmaps""on"
>Option   "EXAVSync"  "off"
>Option   "AllowGLXWithComposite" "on"
>Option   "DynamicClocks" "true"
>Option   "XAANoOffscreenPixmaps"
> EndSection
>
> Section "Screen"
>Identifier   "RadeonHD Screen"
>Device  "ATI Radeon Xpress 1250"
>Monitor  "Built-in Monitor"
>DefaultDepth   24
>SubSection "Display"
>   ViewPort   0 0
>   Depth  24
>EndSubSection
> EndSection
>
> Section "DRI"
>Mode   0666
> EndSection
>
> Section "Extensions"
>Option  "Composite"   "Enable"
> EndSection
>
> Some settings may be completely useless, if there are any specific settings 
> that I need to set up here, please let me know, specially if it's required 
> for multi display setup.
>
> I've examined the Xorg.log.0 file as well, but the output of the log is 
> completely the same as using 1 screen, only change is that it's detecting my 
> 2nd screen as well and is not showing any errors related to rendering or 

Re: How to configure radeonsi for clone mode?

[Alex Deucher]

On Fri, Jan 2, 2015 at 5:25 AM, Boszormenyi Zoltan  wrote:
> Hi,
>
> for an NVIDIA based Xorg setup with the proprietary driver,
> I have this file as /etc/X11/xorg.conf.d/nvidia.conf:
>
> Section "Device"
> Identifier  "NVIDIA"
> Driver  "nvidia"
> Option  "AutoServerLayout" "on"
> EndSection
>
> Section "Screen"
> Identifier  "Screen0"
> Option  "TwinView" "on"
> Option  "TwinViewOrientation" "Clone"
> Option  "AutoServerLayout" "on"
> EndSection
>
> I would like to know how to setup the "clone mode" using the
> radeon driver on a Zotac ZBOX NANO-AQ01 which uses the
> radeonsi driver and has HDMI-0 and DisplayPort-0 connectors
> according Xorg.0.log.
>
> I came up with this using "man xorg.conf":
>
> Section "Monitor"
> Identifier"HDMI-0"
> Option"AutoServerLayout" "on"
> Option"Position" "0 0"
> EndSection
>
> Section "Monitor"
> Identifier"DisplayPort-0"
> Option"AutoServerLayout" "on"
> Option"Position" "0 0"
> EndSection
>
> Section "Device"
> Identifier"RADEON"
> Driver"radeon"
> Option"AutoServerLayout" "on"
> Option"Monitor-HDMI-0" "HDMI-0"
> Option"Monitor-DisplayPort-0" "DisplayPort-0"
> EndSection
>
> However, there is a small problem. I have connected a HD-ready
> capable TV using a HDMI-DisplayPort converted to the DisplayPort
> connector (native resolution 1366x768) and a FullHD capable
> monitor using the HDMI connector. The result doesn't look good
> and confirmed by Xorg.0.log:
>
> [2853811.002] (II) RADEON(0): Output DisplayPort-0 using initial mode 
> 1360x768 +0+0
> [2853811.002] (II) RADEON(0): Output HDMI-0 using initial mode 1280x800 +0+0
>
> If I connect the FullHD-capable monitor to the DisplayPort,
> the result is more satisfying:
>
> [2854212.540] (II) RADEON(0): Output DisplayPort-0 using initial mode 
> 1920x1080 +0+0
> [2854212.540] (II) RADEON(0): Output HDMI-0 using initial mode 1920x1080 +0+0
>
> How can I setup clone mode in a way using the xorg.conf.d
> extension file to make the system recognize the best resolution
> and use that instead of limiting it to the monitor capabilities
> connected to DisplayPort? It seems it's the primary connector.
>

FWIW, static xrandr configuration is not driver specific for the open
source drivers.  It should work the same regardless of what driver you
are using.  You'll want to take a look at the xorg.conf man page.
You'll probably want to play with the following options:


   Option "Primary" "bool"
  This optional entry specifies that the monitor should be
treated  as  the  primary  monitor.  (RandR
  1.2-supporting drivers only)

   Option "PreferredMode" "name"
  This  optional  entry  specifies  a  mode to be marked
as the preferred initial mode of the monitor.
  (RandR 1.2-supporting drivers only)

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: dp blanks randomly with errors

[Alex Deucher]

On Tue, Dec 16, 2014 at 4:38 PM, Christopher Barry
 wrote:
> On Tue, 16 Dec 2014 10:49:50 -0500
> Alex Deucher  wrote:
>
>>On Sun, Dec 14, 2014 at 6:45 PM, Christopher Barry
>> wrote:
>>>
>>> Getting these errors in syslog
>>>
>>> [drm:radeon_dp_link_train_ce] *ERROR* displayport link status failed
>>> [drm:radeon_dp_link_train_ce] *ERROR* channel eq failed
>>>
>>> also, there have been a lot of 'clock recovery failed' errors as
>>> well.
>>>
>>> running debian sid, and I upgrade about every 5 days or so, so my box
>>> is quite up to date for a packaged distro. I upgraded this afternoon
>>> EST and behavior is still bad.
>>>
>>> debian packaged kernel 2.14.2
>>>
>>> X.Org X Server 1.16.2.901 (1.16.3 RC 1)
>>> Release Date: 2014-12-09
>>> X Protocol Version 11, Revision 0
>>> Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian
>>> Current Operating System: Linux monolith 3.12-1-amd64 #1 SMP Debian
>>> 3.12.9-1 (2014-02-01) x86_64
>>> Kernel command line: BOOT_IMAGE=/vmlinuz-3.12-1-amd64
>>> root=/dev/mapper/system_vg-os_lv ro quiet
>>> Build Date: 09 December 2014  10:15:28PM
>>> xorg-server 2:1.16.2.901-1 (http://www.debian.org/support)
>>> Current version of pixman: 0.32.6
>>> Before reporting problems, check http://wiki.x.org
>>> to make sure that you have the latest version.
>>>
>>>
>>> lspci -vv for video card:
>>>
>>> 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
>>> [AMD/ATI] Pitcairn PRO [Radeon HD 7850] (prog-if 00 [VGA controller])
>>> Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850
>>> 2GB GDDR5 DVI-I/DVI-D/HDMI/DP Control: I/O+ Mem+ BusMaster+
>>> SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>>> DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast
>>> >TAbort- SERR- >> >Line Size: 256 bytes
>>> Interrupt: pin A routed to IRQ 56 Region 0: Memory at d000
>>> (64-bit, prefetchable) [size=256M] Region 2: Memory at fb9c
>>> (64-bit, non-prefetchable) [size=256K] Region 4: I/O ports at b000
>>> [size=256] Expansion ROM at fb9a [disabled] [size=128K]
>>> Capabilities: [48] Vendor Specific Information: Len=08 
>>> Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI-
>>> D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0
>>> NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58]
>>> Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes,
>>> PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn-
>>> AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable-
>>> Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr-
>>> NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes
>>> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+
>>> AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s
>>> L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep-
>>> BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
>>> ExtSynch- ClockPM- AutWidDis- BWInt-
>>> AutBWInt- LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk+
>>> DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not
>>> Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion
>>> Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2:
>>> Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit
>>> Margin: Normal Operating Range, EnterModifiedCompliance-
>>> ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current
>>> De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
>>> EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
>>> Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address:
>>> fee0  Data: 4023 Capabilities: [100 v1] Vendor Specific
>>> Information: ID=0001 Rev=1 Len=010  Capabilities: [150 v2]
>>> Advanced Error Reporting UESta:  DLP- SDES- TLP- FCP- CmpltTO-
>>> CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk:
>>> DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP-
>>> ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO-
>>> CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta:
>>> RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk:

Re: dp blanks randomly with errors

[Alex Deucher]

On Sun, Dec 14, 2014 at 6:45 PM, Christopher Barry
 wrote:
>
> Getting these errors in syslog
>
> [drm:radeon_dp_link_train_ce] *ERROR* displayport link status failed
> [drm:radeon_dp_link_train_ce] *ERROR* channel eq failed
>
> also, there have been a lot of 'clock recovery failed' errors as well.
>
> running debian sid, and I upgrade about every 5 days or so, so my box
> is quite up to date for a packaged distro. I upgraded this afternoon
> EST and behavior is still bad.
>
> debian packaged kernel 2.14.2
>
> X.Org X Server 1.16.2.901 (1.16.3 RC 1)
> Release Date: 2014-12-09
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 3.2.0-4-amd64 x86_64 Debian
> Current Operating System: Linux monolith 3.12-1-amd64 #1 SMP Debian
> 3.12.9-1 (2014-02-01) x86_64
> Kernel command line: BOOT_IMAGE=/vmlinuz-3.12-1-amd64
> root=/dev/mapper/system_vg-os_lv ro quiet
> Build Date: 09 December 2014  10:15:28PM
> xorg-server 2:1.16.2.901-1 (http://www.debian.org/support)
> Current version of pixman: 0.32.6
> Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
>
>
> lspci -vv for video card:
>
> 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
> [AMD/ATI] Pitcairn PRO [Radeon HD 7850] (prog-if 00 [VGA controller])
> Subsystem: PC Partner Limited / Sapphire Technology Radeon HD 7850 2GB
> GDDR5 DVI-I/DVI-D/HDMI/DP Control: I/O+ Mem+ BusMaster+ SpecCycle-
> MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status:
> Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  SERR-  Interrupt: pin A routed to IRQ 56 Region 0: Memory at d000 (64-bit,
> prefetchable) [size=256M] Region 2: Memory at fb9c (64-bit,
> non-prefetchable) [size=256K] Region 4: I/O ports at b000 [size=256]
> Expansion ROM at fb9a [disabled] [size=128K] Capabilities: [48]
> Vendor Specific Information: Len=08  Capabilities: [50] Power
> Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1+,D2+,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable-
> DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint,
> MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1
> unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> MaxPayload 128 bytes, MaxReadReq 512 bytes
> DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+
> AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s
> L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 5GT/s, Width x16, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported,
> TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us
> to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed:
> 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating
> Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis:
> -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-,
> EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-,
> LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1
> Maskable- 64bit+ Address: fee0  Data: 4023
> Capabilities: [100 v1] Vendor Specific Information: ID=0001
> Rev=1 Len=010  Capabilities: [150 v2] Advanced Error Reporting
> UESta:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt-
> UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk:  DLP- SDES-
> TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq-
> ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
> RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta:  RxErr- BadTLP- BadDLLP-
> Rollover- Timeout- NonFatalErr+ CEMsk:  RxErr- BadTLP- BadDLLP-
> Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00,
> GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [270 v1] #19 Capabilities:
> [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue
> Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00
> Capabilities: [2c0 v1] #13
> Capabilities: [2d0 v1] #1b
> Kernel driver in use: radeon
>
> (pardon the wrapping)
>
> starting last week sometime, my displayport driven monitor (center of 3
> monitors) began randomly blanking out. The only way to (sometimes)
> correct it for maybe 2 or three hours was to power down, then power up.
> if I just rebooted, it would almost always blank in a matter of minutes
> after login.
>
> I am converting the DP into DVI with an active dongle, but this has
> worked flawlessly for me in the past.
>
> I started booting the last debian kernel, which is 3.12.2, and so far
> the blanking

[ANNOUNCE] xf86-video-ati 7.5.0

[Alex Deucher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Alex Deucher (7):
  radeon: enable hawaii accel conditionally (v3)
  radeon: fix warnings when building against older xservers
  radeon/kms: add new CIK pci ids
  radeon/kms: add new SI pci ids
  radeon/kms: fix mullins pci id
  radeon: require libdrm_radeon 2.4.58 for latest SI/CI pci ids
  radeon: bump version for release

Andreas Boll (4):
  radeon: drop redundant radeon_drm.h includes
  radeon: move RADEON_TILING_{MASK, LINEAR} from radeon_drm.h to radeon.h
  radeon: drop radeon_drm.h
  radeon: remove definitions already present in radeon_drm.h

Hans de Goede (1):
 glamor.hfigure: Include xorg-server.h before

Maarten Lankhorst (1):
  bump version post release

Michel Dänzer (4):
  Handle CRTC DPMS from output DPMS hooks
  glamor: Set environment variable RADEON_THREAD=0
  Add Emacs .dir-local.el file
  Revert "glamor: Set environment variable RADEON_THREAD=0"

Thomas DeRensis (2):
  radeon: fix a leak in radeon_vbo_get_bo()
  radeon: fix build warnings regarding const qualifier

git tag: xf86-video-ati-7.5.0

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.bz2
MD5:  29654190e37310b87e44a14c229967ee  xf86-video-ati-7.5.0.tar.bz2
SHA1: 9cfdaf0bd4a46781b5082c75ca546fc832598124  xf86-video-ati-7.5.0.tar.bz2
SHA256: ec3e6f06b6cf9a40c72aafa3448aae8b034c80b37410ca9442d5cf6806e07936
 xf86-video-ati-7.5.0.tar.bz2
PGP:  
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.bz2.sig

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.gz
MD5:  d218ad1702570c2374df6edce101cee0  xf86-video-ati-7.5.0.tar.gz
SHA1: 7c57bebb7fe0d999342db38e857de7e3b412b9a5  xf86-video-ati-7.5.0.tar.gz
SHA256: 35b2f7cda8bad68a91db43bf979e6efc6a2fa0d4beddecb9698b826bae7eab85
 xf86-video-ati-7.5.0.tar.gz
PGP:  
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.gz.sig

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlQs2i0ACgkQm07k+YR03kDNtACcDFdBO4R024eIbx77tMGdgG8A
Z1kAn31fEE8DwcHxWNBWmfW1YIcDW5GM
=i6Ke
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Alex Deucher (7):
  radeon: enable hawaii accel conditionally (v3)
  radeon: fix warnings when building against older xservers
  radeon/kms: add new CIK pci ids
  radeon/kms: add new SI pci ids
  radeon/kms: fix mullins pci id
  radeon: require libdrm_radeon 2.4.58 for latest SI/CI pci ids
  radeon: bump version for release

Andreas Boll (4):
  radeon: drop redundant radeon_drm.h includes
  radeon: move RADEON_TILING_{MASK, LINEAR} from radeon_drm.h to radeon.h
  radeon: drop radeon_drm.h
  radeon: remove definitions already present in radeon_drm.h

Hans de Goede (1):
  configure: Include xorg-server.h before
 glamor.h

Maarten Lankhorst (1):
  bump version post release

Michel Dänzer (4):
  Handle CRTC DPMS from output DPMS hooks
  glamor: Set environment variable RADEON_THREAD=0
  Add Emacs .dir-local.el file
  Revert "glamor: Set environment variable RADEON_THREAD=0"

Thomas DeRensis (2):
  radeon: fix a leak in radeon_vbo_get_bo()
  radeon: fix build warnings regarding const qualifier

git tag: xf86-video-ati-7.5.0

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.bz2
MD5:  29654190e37310b87e44a14c229967ee  xf86-video-ati-7.5.0.tar.bz2
SHA1: 9cfdaf0bd4a46781b5082c75ca546fc832598124  xf86-video-ati-7.5.0.tar.bz2
SHA256: ec3e6f06b6cf9a40c72aafa3448aae8b034c80b37410ca9442d5cf6806e07936  
xf86-video-ati-7.5.0.tar.bz2
PGP:  
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.bz2.sig

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.gz
MD5:  d218ad1702570c2374df6edce101cee0  xf86-video-ati-7.5.0.tar.gz
SHA1: 7c57bebb7fe0d999342db38e857de7e3b412b9a5  xf86-video-ati-7.5.0.tar.gz
SHA256: 35b2f7cda8bad68a91db43bf979e6efc6a2fa0d4beddecb9698b826bae7eab85  
xf86-video-ati-7.5.0.tar.gz
PGP:  
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.5.0.tar.gz.sig

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlQs2i0ACgkQm07k+YR03kDNtACcDFdBO4R024eIbx77tMGdgG8A
Z1kAn31fEE8DwcHxWNBWmfW1YIcDW5GM
=i6Ke
-END PGP SIGNATURE-
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Am I using the "ati" or "vesa" driver?

[Alex Deucher]

On Tue, Aug 5, 2014 at 10:10 AM, YuGiOhJCJ Mailing-List
 wrote:
>> > But I see a last problem: I have no 3d acceleration!
>> > As you can see here:
>> > $ cat /var/log/Xorg.0.log | grep Direct
>> > [  7567.271] (WW) RADEON(0): Direct rendering disabled
>> >
>> > The full xorg log is available here: http://pastebin.com/hSKjXsvL
>> >
>> > Do you know how to have 3d acceleration please?
>>
>> To overcome
>>
>> http://pastebin.com/raw.php?i=AwPnpSJ7
>>
>> which you pasted on IRC, you need to compile Mesa with:
>>
>>   --with-egl-platforms=drm
>
> Are you speaking about the segmentation fault + backtrace problem?
> I have built "mesa-10.0.2" with the "--with-egl-platforms=drm" option but I 
> have again this segmentation fault + backtrace problem.
> It does not solved this problem.
>
> Here is the exact configuration line I have used:
> ./configure --prefix=/usr --sysconfdir=/etc --libdir=/usr/lib 
> --mandir=/usr/man --docdir=/usr/doc/mesa-10.0.2 
> --with-dri-driverdir=/usr/lib/xorg/modules/dri --with-dri-drivers="i915,i965" 
> --enable-shared-glapi --with-egl-platforms=drm
>

You need to build the 3D driver.  Add -with-gallium-drivers=radeonsi
to your configure line.

Alex

> I am building and installing packages in this order:
> - libdrm-2.4.56
> - mesa-10.0.2
> - mesa-demos-8.1.0
> - fontsproto-2.1.3
> - glproto-1.4.17
> - libepoxy-1.2
> - xextproto-7.3.0
> - xproto-7.0.26
> - xtrans-1.3.4
> - xorg-server-1.16.0
> - glamor-egl-0.6.0
> - xf86-video-ati-7.4.0
> - xf86-video-intel-2.99.912
> - xf86-video-vesa-2.3.3
>
> Anyway, if I keep the official packages from Slackware 14.1, I have not this 
> segmentation fault + backtrace problem.
> So, currently I am using:
> - libdrm-2.4.46
> - mesa-9.1.7
> - mesa-demos-8.1.0
> - fontsproto-2.1.2
> - glproto-1.4.16
> - libepoxy-1.2
> - xextproto-7.2.1
> - xproto-7.0.24
> - xtrans-1.2.7
> - xorg-server-1.14.3
> - glamor-egl-0.6.0
> - xf86-video-ati-7.2.0
> - xf86-video-intel-2.21.15
> - xf86-video-vesa-2.3.3
>
> In this second case, the problem is that I have no direct rendering.
> As you can see here:
> $ cat /var/log/Xorg.0.log | grep Direct
> [  7567.271] (WW) RADEON(0): Direct rendering disabled
>
> The full xorg log is available here: http://pastebin.com/hSKjXsvL
>
> Maybe, it is just a permission problem, a xorg configuration problem, or 
> something like that.
>
> What can I do to get direct rendering please?
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: [Dell Vostro 3300] running bumblebee in Ubuntu 14.04 results in call trace in logs

[Alex Deucher]

On Wed, Jul 9, 2014 at 11:44 AM, Sayantan Das  wrote:
> Hi there,
>
> As per the request from Ubuntu devs, I am reporting this issue in the
> xorg mailing list. Please see the details below
>
> [1.] One line summary of the problem:
>
> [Dell Vostro 3300] running bumblebee in Ubuntu 14.04 results in call
> trace in logs
>
> [2.] Full description of the problem/report:
> While booted into the newest mainline kernel- installing bumblebee and
> nvidia-331  results in call trace.

I'm not familiar with bumblebee, but I know that when you call the
acpi methods for hybrid laptops to enable/disable the dGPU, it
generates a pci hotplug event and the pciehp or acpihp driver will
attempt to unload the driver.  The acpihp driver was changed[1] to
ignore the event, but as far as I know the pciehp driver still needs
to be fixed.

[1] - 
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f244d8b623dae7a7bc695b0336f67729b95a9736

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: usb to VGA

[Alex Deucher]

On Thu, May 29, 2014 at 10:23 AM, Michael Durkin  wrote:
> I did open it up ... and it has printed on the largest IC
>
> Fresco Logic
> FL2000

After a quick googling, I don't see any drivers for Linux.  You'll
have to talk to the manufacturer to see if they are working on a Linux
driver and if not, see if they would be able to release documentation
or sample code so you could write a driver.

Alex

>
> On Thu, May 29, 2014 at 5:58 AM, Alex Deucher  wrote:
>> On Wed, May 28, 2014 at 9:11 PM, Michael Durkin  wrote:
>>> Yea .. im looking for Xorg or KMS drivers for it ... i dont think
>>> there are any yet ... and im hopeing some one would be interested in
>>> doing so ...
>>
>> You'll need to find out what chip it uses.  There is pretty good KMS
>> support for displaylink-based devices, at least the earlier versions.
>>
>> Alex
>>
>>>
>>> On Wed, May 28, 2014 at 6:02 PM, Alan Coopersmith
>>>  wrote:
>>>> On 05/28/14 10:18 AM, Michael Durkin wrote:
>>>>>
>>>>> Would this be the right list to ask about Fresco Logic's FL2000 USB to
>>>>> VGA adapter?
>>>>>
>>>>> Iv been on a few ML now with being told its the wrong place ...
>>>>
>>>>
>>>> Depends what you want to ask - general questions about it are mostly off
>>>> topic, questions about using it with Xorg would be on topic.  (Though I
>>>> have no idea if anyone's written an Xorg or KMS driver for it, since this
>>>> is the first I've heard of it.)
>>>>
>>>> --
>>>> -Alan Coopersmith-  alan.coopersm...@oracle.com
>>>>  Oracle Solaris Engineering - http://blogs.oracle.com/alanc
>>> ___
>>> xorg@lists.x.org: X.Org support
>>> Archives: http://lists.freedesktop.org/archives/xorg
>>> Info: http://lists.x.org/mailman/listinfo/xorg
>>> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: usb to VGA

[Alex Deucher]

On Wed, May 28, 2014 at 9:11 PM, Michael Durkin  wrote:
> Yea .. im looking for Xorg or KMS drivers for it ... i dont think
> there are any yet ... and im hopeing some one would be interested in
> doing so ...

You'll need to find out what chip it uses.  There is pretty good KMS
support for displaylink-based devices, at least the earlier versions.

Alex

>
> On Wed, May 28, 2014 at 6:02 PM, Alan Coopersmith
>  wrote:
>> On 05/28/14 10:18 AM, Michael Durkin wrote:
>>>
>>> Would this be the right list to ask about Fresco Logic's FL2000 USB to
>>> VGA adapter?
>>>
>>> Iv been on a few ML now with being told its the wrong place ...
>>
>>
>> Depends what you want to ask - general questions about it are mostly off
>> topic, questions about using it with Xorg would be on topic.  (Though I
>> have no idea if anyone's written an Xorg or KMS driver for it, since this
>> is the first I've heard of it.)
>>
>> --
>> -Alan Coopersmith-  alan.coopersm...@oracle.com
>>  Oracle Solaris Engineering - http://blogs.oracle.com/alanc
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: radeon inconsistent output names

[Alex Deucher]

On Thu, May 8, 2014 at 3:42 PM, Matthew Monaco  wrote:
> Hi,
>
> My HDMI output name (ie the one I use for xrandr) changes between HDMI-0 and
> HDMI-3 from boot to boot. It doesn't toggle back and forth or anything like
> that, it's just random. This makes my xprofile script a pain for setting up my
> displays when I log in.
>
> I have an i915 which is still enabled in the bios, is the first card, has the
> kernel ttys, and is used for seat0.
>
> The radeon is used for seat1, and is the one with the issue. Is there are fix
> for this?

I think it will depend on what order the cards are initialized by X
and the kernel.

Alex

>
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape
> Verde PRO [Radeon HD 7750] (prog-if 00 [VGA controller])
> Subsystem: ASUSTeK Computer Inc. Device 0459
> Flags: bus master, fast devsel, latency 0, IRQ 44
> Memory at d000 (64-bit, prefetchable) [size=256M]
> Memory at efd0 (64-bit, non-prefetchable) [size=256K]
> I/O ports at e000 [size=256]
> Expansion ROM at efd4 [disabled] [size=128K]
> Capabilities: [48] Vendor Specific Information: Len=08 
> Capabilities: [50] Power Management version 3
> Capabilities: [58] Express Legacy Endpoint, MSI 00
> Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
> Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 
> Len=010 
> Capabilities: [150] Advanced Error Reporting
> Capabilities: [270] #19
> Kernel driver in use: radeon
> Kernel modules: radeon
>
> I'm on Linux v3.14.3, and I believe I started noticing this sometime in 
> v3.13.y.
> Also using xorg-server v1.15.1, xrandr v1.4.2, xf86-video-ati 7.3.0.
>
> Thanks!
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Lenovo X131e xorg.conf ?

[Alex Deucher]

On Mon, Mar 24, 2014 at 5:55 PM, Adrian Walker  wrote:
> Hi All,
>
> Does anyone have a working xorg.conf for a Lenovo X131e please?
>

You shoudn't need an xorg.conf for any KMS drivers.  In most cases
having a config will cause more problems than it solves.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: RADEON(0): [drm] Failed to open DRM device: No such file or directory error

[Alex Deucher]

On Sat, Mar 15, 2014 at 4:34 AM, stompdagg...@yahoo.com
 wrote:
> here is a simple test case that reproduces the issue on my machine:
> dagg@NCC-5001-D ~/workspace $ cat open_example.c
> #include 
> #include 
> #include 
> #include 
> #include 
>
> int main()
> {
> char *param1 = "ok";
> char *param2 = ".";
> int filedesc = open("/dev/dri/card1", O_RDWR, 0);
> if (filedesc) {
> param1 = "ERROR: ";
> param2 = strerror(errno);
> }
> printf("fd = %d, status = %s%s\n", filedesc, param1, param2);
> close(filedesc);
>
> return 0;
> }dagg@NCC-5001-D ~/workspace $ gcc open_example.c -o open_example &&
> ./open_example
> fd = -1, status = ERROR: Invalid argument
>

Does booting with radeon.runpm=0 on the kernel command line in grub
fix it?  If so, it should be fixed with these patches:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9babd35ad72af631547c7ca294bc2e931cc40e58
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=7848865914c6a63ead674f0f5604b77df7d3874f

Alex

>
> On Friday, March 14, 2014 4:22 PM, "stompdagg...@yahoo.com"
>  wrote:
> On Tuesday, March 11, 2014 8:45 AM, "stompdagg...@yahoo.com"
>  wrote:
>>On Tuesday, March 11, 2014 5:16 AM, Michel Dänzer 
>> wrote:
>>On Mon, 2014-03-10 at 08:23 -0700, stompdagg...@yahoo.com wrote:
>>
>>>
>>>
>>> >On Monday, March 10, 2014 5:58 AM, Michel Dänzer 
>>> wrote:
>>>
>>> >On Sam, 2014-03-08 at 11:41 -0800, stompdagg...@yahoo.com wrote:
>>> >
>>> >> >On Sat, Mar 8, 2014 at 2:56 AM, stompdagg...@yahoo.com
>>> >> >
>>> >> >> [51.829] (EE) RADEON(0): [drm] Failed to open DRM device for
>>> >> >> pci::06:00.0: No such file or directory
>>> >
>>> >'No such file or directory' sounds like something is deleting
>>> >your /dev/dri/card* files, or not creating them in the first place.
>>> >Maybe check your udev setup.
>>> >
>>> >If it only happens with a 3.13 kernel but not with a 3.12 one,
>>> another
>>> >option is to bisect the kernel.
> .>
> .> Greetings Michel,
> .>
> .> dri node do exists, see:
>>> dagg@NCC-5001-D ~ $ ll /dev/dri
>>> total 0
>>> crw-rw+ 1 root video 226,  0 Mar 10 09:27 card0
>>> crw-rw+ 1 root video 226,  1 Mar 10 09:27 card1
>>> crw-rw+ 1 root video 226,  2 Mar 10 09:27 card2
>>> crw-rw  1 root video 226, 64 Mar 10 09:27 controlD64
>>> crw-rw  1 root video 226, 65 Mar 10 09:27 controlD65
>>> crw-rw  1 root video 226, 66 Mar 10 09:27 controlD66
>>>
>>> I think that the way to find the cause on my part is to check the
>>> origin of that msg in Xorg.log.
>>>
>>> is that a xserver msg or xf86-video-ati msg?
>>
>>
>>The message is from the radeon driver, but it's because drmOpen() in
>>libdrm fails. It would indeed be interesting to track down where the 'No
>>such file or directory' error originates from.
>
> will do, when I'll have more info, I'll update.
>
> Greetings Michel,
>
> I've tried to track the source if that error, I've enabled dbg prints in
> libdrm and found this:
> (II) [KMS] Kernel modesetting enabled.
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: Searching for BusID pci::06:00.0
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 11, (OK)
> drmOpenByBusid: drmOpenMinor returns 11
> drmOpenByBusid: drmGetBusid reports pci::00:02.0
> drmOpenDevice: node name is /dev/dri/card1
> drmOpenDevice: open result is -1, (Invalid argument)
> drmOpenByBusid: drmOpenMinor returns -22
> drmOpenDevice: node name is /dev/dri/card2
> drmOpenDevice: open result is -1, (Invalid argument)
>
> looking in the code I see this:
> fd = open(buf, O_RDWR, 0);
> drmMsg("drmOpenDevice: open result is %d, (%s)\n",
> fd, fd < 0 ? strerror(errno) : "OK");
> if (fd >= 0)
> return fd;
>
> I think that the issue might be that the file cannot be opened for that mode
> as the path is printed above and it is ok.
>
> any ideas what might it be?
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
>
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: ATI oss color space compressed in the dark shades of gray

[Alex Deucher]

On Fri, Mar 14, 2014 at 9:26 AM, Alex Deucher  wrote:
> On Thu, Mar 13, 2014 at 6:34 AM, Sebastian Schultz
>  wrote:
>> Is there anything I can do to about it? Or is this an upcoming feature? Or is
>> it a bug and I should submit a report?
>
> It would be a new feature.  It's not a high priority at the moment, so
> I'm not sure how quickly we would get to it.

If you are inclined to play with this yourself, try adjusting the
registers in dce5_crtc_load_lut(), in particular
NI_OUTPUT_CSC_CONTROL.NI_OUTPUT_CSC_GRPH_MODE.  Try setting it to
NI_OUTPUT_CSC_TV_RGB or NI_OUTPUT_CSC_YCBCR_601 or
NI_OUTPUT_CSC_YCBCR_709.

Alex

>
> Alex
>
>>
>> Sebastian
>>
>>
>> Am Mittwoch, 12. März 2014, 12:18:37 schrieb Alex Deucher:
>>> On Wed, Mar 12, 2014 at 10:31 AM, Sebastian Schultz
>>>
>>>  wrote:
>>> > Hello,
>>> >
>>> > first of all: I'm using a Radeon 7750 in combination with a monitor via
>>> > display port and a tv via the HDMI port. Most of the time I do not want a
>>> > picture on the tv, only when wathcing videos, so I use xrandr scripts to
>>> > switch that display on and off. And here comes my problem:
>>> >
>>> > With the arrival of linux 3.13 to the [core]-repo of arch linux I switched
>>> > from catalyst to the open source drivers, as they finally provide a
>>> > sufficient performance. My only problem now is that the colorspace is
>>> > compressed for gray values below 16 (that means every shade of gray
>>> > having values of 0 to 16 look just black). That's only the case for my
>>> > HDMI-output connected to my TV, which worked without problems with the
>>> > catalyst drivers. Also, only the dark grays are compressed, the
>>> > near-white grays show up correct.  My Xorg.0.log shows that the TV on
>>> > HDMI-0 supports the RGB 4:4:4 encoding (just like the monitor does):
>>> > http://pastebin.com/PF6sjzu1
>>> >
>>> > I found a xrandr-command "--set "Broadcast RGB" "Full"", which can be used
>>> > with chips from Intel. Is there something similar for the open source ati
>>> > drivers?
>>>
>>> Not at the moment.
>>>
>>> Alex
>> ___
>> xorg@lists.x.org: X.Org support
>> Archives: http://lists.freedesktop.org/archives/xorg
>> Info: http://lists.x.org/mailman/listinfo/xorg
>> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: ATI oss color space compressed in the dark shades of gray

[Alex Deucher]

On Thu, Mar 13, 2014 at 6:34 AM, Sebastian Schultz
 wrote:
> Is there anything I can do to about it? Or is this an upcoming feature? Or is
> it a bug and I should submit a report?

It would be a new feature.  It's not a high priority at the moment, so
I'm not sure how quickly we would get to it.

Alex

>
> Sebastian
>
>
> Am Mittwoch, 12. März 2014, 12:18:37 schrieb Alex Deucher:
>> On Wed, Mar 12, 2014 at 10:31 AM, Sebastian Schultz
>>
>>  wrote:
>> > Hello,
>> >
>> > first of all: I'm using a Radeon 7750 in combination with a monitor via
>> > display port and a tv via the HDMI port. Most of the time I do not want a
>> > picture on the tv, only when wathcing videos, so I use xrandr scripts to
>> > switch that display on and off. And here comes my problem:
>> >
>> > With the arrival of linux 3.13 to the [core]-repo of arch linux I switched
>> > from catalyst to the open source drivers, as they finally provide a
>> > sufficient performance. My only problem now is that the colorspace is
>> > compressed for gray values below 16 (that means every shade of gray
>> > having values of 0 to 16 look just black). That's only the case for my
>> > HDMI-output connected to my TV, which worked without problems with the
>> > catalyst drivers. Also, only the dark grays are compressed, the
>> > near-white grays show up correct.  My Xorg.0.log shows that the TV on
>> > HDMI-0 supports the RGB 4:4:4 encoding (just like the monitor does):
>> > http://pastebin.com/PF6sjzu1
>> >
>> > I found a xrandr-command "--set "Broadcast RGB" "Full"", which can be used
>> > with chips from Intel. Is there something similar for the open source ati
>> > drivers?
>>
>> Not at the moment.
>>
>> Alex
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: ATI oss color space compressed in the dark shades of gray

[Alex Deucher]

On Wed, Mar 12, 2014 at 10:31 AM, Sebastian Schultz
 wrote:
> Hello,
>
> first of all: I'm using a Radeon 7750 in combination with a monitor via
> display port and a tv via the HDMI port. Most of the time I do not want a
> picture on the tv, only when wathcing videos, so I use xrandr scripts to
> switch that display on and off. And here comes my problem:
>
> With the arrival of linux 3.13 to the [core]-repo of arch linux I switched
> from catalyst to the open source drivers, as they finally provide a sufficient
> performance. My only problem now is that the colorspace is compressed for gray
> values below 16 (that means every shade of gray having values of 0 to 16 look
> just black). That's only the case for my HDMI-output connected to my TV, which
> worked without problems with the catalyst drivers. Also, only the dark grays
> are compressed, the near-white grays show up correct.  My Xorg.0.log shows
> that the TV on HDMI-0 supports the RGB 4:4:4 encoding (just like the monitor
> does): http://pastebin.com/PF6sjzu1
>
> I found a xrandr-command "--set "Broadcast RGB" "Full"", which can be used
> with chips from Intel. Is there something similar for the open source ati
> drivers?

Not at the moment.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: RADEON(0): [drm] Failed to open DRM device: No such file or directory error

[Alex Deucher]

On Sat, Mar 8, 2014 at 2:56 AM, stompdagg...@yahoo.com
 wrote:
> greetings,
>
> since I've updated my kernel to 3.13.x I'm unable to start X on my radeon
> cards.
>
> the setup works great in kernel 3.12.8, here is part of Xorg log for that
> adaper:
> [51.782] (II) [KMS] Kernel modesetting enabled.
> [51.782] (II) RADEON(0): RADEONPreInit_KMS
> [51.782] (II) RADEON(0): Creating default Display subsection in Screen
> section
> "Default Screen Section" for depth/fbbpp 24/32
> [51.782] (==) RADEON(0): Depth 24, (--) framebuffer bpp 32
> [51.782] (II) RADEON(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp
> pixmaps)
> [51.782] (==) RADEON(0): Default visual is TrueColor
> [51.782] (==) RADEON(0): RGB weight 888
> [51.782] (II) RADEON(0): Using 8 bits per RGB (8 bit DAC)
> [51.782] (--) RADEON(0): Chipset: "ATI Radeon HD 3600 XT" (ChipID =
> 0x9598)
> [51.829] (EE) RADEON(0): [drm] Failed to open DRM device for
> pci::06:00.0: No such file or directory
> [51.829] (EE) RADEON(0): Kernel modesetting setup failed
> [51.829] (II) RADEON(0): RADEONFreeScreen
> [51.829] (II) UnloadModule: "radeon"
> [51.829] (EE) Screen(s) found, but none have a usable configuration.
> [51.829] (EE)
> Fatal server error:
> [51.829] (EE) no screens found(EE)
> [51.829] (EE)
> Please consult the The X.Org Foundation support
>  at http://wiki.x.org
>
> is that a X bug? what is the right place to debug it, X or xf86-video-ati?

There's some problems with your kernel.  Check your dmesg output and
make sure the radeon kernel driver loaded properly.  Depending on your
setup you may be missing the necessary firmware files from your
initrd.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Radeon rv610 (2400HD-Pro card) question

[Alex Deucher]

On Fri, Feb 7, 2014 at 3:34 PM, Gene Heskett  wrote:
> On Friday 07 February 2014 14:46:43 Alex Deucher did opine:
>
>> On Wed, Feb 5, 2014 at 11:05 PM, Gene Heskett  wrote:
>> > Greetings;
>> >
>> > Since it appears nvidia is not supporting the econo cards in the
>> > supply pipeline, cards like the 8400 GS I just bought 2 of, I got the
>> > bright idea to swap it out for an old radeon 2400HD-Pro card I had on
>> > the shelf.  So I built a 3.13.1 32 bit kernel and rebooted after
>> > changing teh card.
>> >
>> > Color is nice, looks like a higher gamma setting.  But video speed is
>> > just as bad and the audio was about 1.5 MINUTES behind the video, as
>> > the nvidia card I took out on the news sites, so I toddled over to
>> > youtube to see. Video played at about 2x normal speeds, and the audio
>> > was still 1 minutes and change after the video.
>> >
>> > I've see stuff out of sync before, but over a minute?
>> >
>> > Called up synaptic & found there were some codecs I didn't have, so I
>>
>> > installed those, BUT another kernel rebuild reports:
>> We are going to need a bit more information.  Which driver were you
>> using fglrx or the open source driver?  What app were you using to
>> play the video?  What API (Xv, X11, VDAPU, GL, etc.).  Is the driver
>> installed and working properly?  How are you trying to play the audio?
>>  Via hdmi, via a 1/8 headphone jack, something else?  At the minimum,
>> we'd need your xorg log, dmesg output, and glxinfo output.  From your
>> second email, it sounds like something is seriously screwed up on your
>> system if gears is segfaulting.  If you previously had fglrx
>> installed, you will need to re-install several of your disto packages
>> because the closed source drivers (both nvidiia and fglrx) overwrite
>> several gl and glx libs.
>>
>> Alex
>
> No closed nvidia drivers, all nouveau. Top level apps were firefox27 or
> chromium.  And to get something that attempts to work, I've swapped back to
> the nvidia card.  I figured 2 days was long enough to wait for a reply, and
> zero traffic from the list in that 2 days, and I needed something quasi-
> usable.  If we can keep a conversation going, I will switch back.

It's up to you, I didn't have time to look at this until today.

>
> Audio is a small amplified 3 speaker set plugged into line out on the asus
> motherboards HDA Intel audio.  Too heavy on bass, but no controls.
>
> xorg.0.log attached, but as you know, that is replaced on every startx or
> equ.  So this one represents the nvidia card boot.  Looks to be an endless
> framebuffer error in places.
>
> I just reinstalled ALL the OpenGL and msa-glx stuff, no change, glxgears is
> still a segfault. I didn't uninstall the flgrx stuff, but didn't reinstall
> it either.
>
> I am also building kernels a couple times a day, trying to get a 3.13.1 to
> boot, but its hanging at top_init.  This is 3.12.9 ATM.

According to your log you are using the fbdev X driver which is
software rendering.  I suspect you were probably using the fbdev
driver for the AMD card as well.  I suspect perhaps the kernel drivers
are not loaded properly on your system.  Double check to  make sure
the kernel drivers are not blacklisted.  Note that fglrx blacklists
the open source radeon kernel driver so that it doesn't load when
fglrx is installed.  The open source radeon driver may still be
blacklisted.  Check your dmesg output to see if the kernel graphics
driver is loaded properly.  I'm not sure what's going on with the
nouveau driver.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Radeon rv610 (2400HD-Pro card) question

[Alex Deucher]

On Wed, Feb 5, 2014 at 11:05 PM, Gene Heskett  wrote:
> Greetings;
>
> Since it appears nvidia is not supporting the econo cards in the supply
> pipeline, cards like the 8400 GS I just bought 2 of, I got the bright idea
> to swap it out for an old radeon 2400HD-Pro card I had on the shelf.  So I
> built a 3.13.1 32 bit kernel and rebooted after changing teh card.
>
> Color is nice, looks like a higher gamma setting.  But video speed is just
> as bad and the audio was about 1.5 MINUTES behind the video, as the nvidia
> card I took out on the news sites, so I toddled over to youtube to see.
> Video played at about 2x normal speeds, and the audio was still 1 minutes
> and change after the video.
>
> I've see stuff out of sync before, but over a minute?
>
> Called up synaptic & found there were some codecs I didn't have, so I
> installed those, BUT another kernel rebuild reports:
>

We are going to need a bit more information.  Which driver were you
using fglrx or the open source driver?  What app were you using to
play the video?  What API (Xv, X11, VDAPU, GL, etc.).  Is the driver
installed and working properly?  How are you trying to play the audio?
 Via hdmi, via a 1/8 headphone jack, something else?  At the minimum,
we'd need your xorg log, dmesg output, and glxinfo output.  From your
second email, it sounds like something is seriously screwed up on your
system if gears is segfaulting.  If you previously had fglrx
installed, you will need to re-install several of your disto packages
because the closed source drivers (both nvidiia and fglrx) overwrite
several gl and glx libs.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: [ANNOUNCE] xf86-video-ati 7.3.0

[Alex Deucher]

I guess gmail mangled it.  Does the attached work any better?


Alex

On Sat, Jan 25, 2014 at 9:24 AM, Julien Cristau  wrote:
> Hi Alex,
>
> When trying to verify this message, I get
> gpg: BAD signature from "Alex Deucher "
> :(
>
> If this isn't just me, any chance to get the tarball checksums in a
> properly signed mail?
>
> Thanks,
> Julien
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Alex Deucher (16):
  radeon: disallow glamor on pre-R600 asics
  radeon/kms: add berlin pci ids
  radeon: enable glamor by default (v4)
  glamor: require 0.5.1 or newer
  radeon: fix limit handling for cards with >4G of ram
  radeon: add glamor Xv support (v2)
  Revert "radeon: add glamor Xv support (v2)"
  drm/radeon: fix non-glamor build
  radeon: fix the non-glamor build harder...
  radeon: enable tiling on SI by default (v2)
  radeon: add support for Hawaii
  radeon/kms: add Hawaii pci ids
  drm/radeon: fix SUMO2 pci id
  radeon/exa: Always use a scratch surface for UTS to vram
  Require glamor 0.6.0
  radeon: bump version for release

Christopher James Halse Rogers (1):
  EXA/evergreen: Paranoia around linear tiling. (v2)

Dave Airlie (1):
  radeon: use glamor Xv support if present.

Jerome Glisse (1):
  radeon/glamor: with new pixmap for dri2 drawable no need to create new 
texture

Maarten Lankhorst (1):
  bump version post release

Mark Kettenis (1):
  Fix shadowfb on big-endian machines

Michel Dänzer (3):
  DRI2: Install client callback only once
  dri2: Make last_vblank_seq local unsigned to match dpms_last_seq
  Don't require the glamoregl module to be pre-loaded with xserver >= 1.15

Robert Millan (2):
  radeon: Set first parameter of drmOpen() to NULL
  radeon: Restore kernel module load on FreeBSD.

Vadim Girlin (1):
  radeon: disable 2D tiling on buffers < 128 pixels

git tag: xf86-video-ati-7.3.0

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.3.0.tar.bz2
MD5:  f36383c590d56a9304e5cab4813a6653  xf86-video-ati-7.3.0.tar.bz2
SHA1: 946bcfcb892088a9ffecc00856a1c8e6bd47a088  xf86-video-ati-7.3.0.tar.bz2
SHA256: 107c072c4919a996e04f47afdb53d5946a3ad574f270b8c560ef8b3a032046fe  
xf86-video-ati-7.3.0.tar.bz2

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.3.0.tar.gz
MD5:  5e57dda1e4496f422b28b659fe2441fa  xf86-video-ati-7.3.0.tar.gz
SHA1: 4114c42b785f468fd8291be5c89a80e9a20f0f6a  xf86-video-ati-7.3.0.tar.gz
SHA256: fc2b0ea5af81a1b27cbe5be3408f3b3434217aef738dc95443f76a975b2698ca  
xf86-video-ati-7.3.0.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlLiijEACgkQm07k+YR03kDUKwCgutHJqTcV+QVFaS5xrGnnjVnU
ZZMAnREmhu404MXBUVuPxdk5VUS9Mral
=siq4
-END PGP SIGNATURE-
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

[ANNOUNCE] xf86-video-ati 7.3.0

[Alex Deucher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Alex Deucher (16):
  radeon: disallow glamor on pre-R600 asics
  radeon/kms: add berlin pci ids
  radeon: enable glamor by default (v4)
  glamor: require 0.5.1 or newer
  radeon: fix limit handling for cards with >4G of ram
  radeon: add glamor Xv support (v2)
  Revert "radeon: add glamor Xv support (v2)"
  drm/radeon: fix non-glamor build
  radeon: fix the non-glamor build harder...
  radeon: enable tiling on SI by default (v2)
  radeon: add support for Hawaii
  radeon/kms: add Hawaii pci ids
  drm/radeon: fix SUMO2 pci id
  radeon/exa: Always use a scratch surface for UTS to vram
  Require glamor 0.6.0
  radeon: bump version for release

Christopher James Halse Rogers (1):
  EXA/evergreen: Paranoia around linear tiling. (v2)

Dave Airlie (1):
  radeon: use glamor Xv support if present.

Jerome Glisse (1):
  radeon/glamor: with new pixmap for dri2 drawable no need to
create new texture

Maarten Lankhorst (1):
  bump version post release

Mark Kettenis (1):
  Fix shadowfb on big-endian machines

Michel Dänzer (3):
  DRI2: Install client callback only once
  dri2: Make last_vblank_seq local unsigned to match dpms_last_seq
  Don't require the glamoregl module to be pre-loaded with xserver >= 1.15

Robert Millan (2):
  radeon: Set first parameter of drmOpen() to NULL
  radeon: Restore kernel module load on FreeBSD.

Vadim Girlin (1):
  radeon: disable 2D tiling on buffers < 128 pixels

git tag: xf86-video-ati-7.3.0

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.3.0.tar.bz2
MD5:  f36383c590d56a9304e5cab4813a6653  xf86-video-ati-7.3.0.tar.bz2
SHA1: 946bcfcb892088a9ffecc00856a1c8e6bd47a088  xf86-video-ati-7.3.0.tar.bz2
SHA256: 107c072c4919a996e04f47afdb53d5946a3ad574f270b8c560ef8b3a032046fe
 xf86-video-ati-7.3.0.tar.bz2

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.3.0.tar.gz
MD5:  5e57dda1e4496f422b28b659fe2441fa  xf86-video-ati-7.3.0.tar.gz
SHA1: 4114c42b785f468fd8291be5c89a80e9a20f0f6a  xf86-video-ati-7.3.0.tar.gz
SHA256: fc2b0ea5af81a1b27cbe5be3408f3b3434217aef738dc95443f76a975b2698ca
 xf86-video-ati-7.3.0.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iEYEARECAAYFAlLiijEACgkQm07k+YR03kDUKwCgutHJqTcV+QVFaS5xrGnnjVnU
ZZMAnREmhu404MXBUVuPxdk5VUS9Mral
=siq4
-END PGP SIGNATURE-
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Quad head graphic card.

[Alex Deucher]

On Thu, Jan 23, 2014 at 5:48 PM, Grzegorz Sójka  wrote:
> On 01/23/14 23:26, Alex Deucher wrote:
>>
>> On Thu, Jan 23, 2014 at 4:57 PM, Grzegorz Sójka  wrote:
>>>
>>> Hi there,
>>>
>>> I have 4 identical monitors. So I decided to buy (not to expensive,
>>> around 100USD) quad head graphics card. I do not need anything
>>> particular. Only office applications, no gaming. The crucial thing is
>>> that I would like to be able to span a single window across all 4
>>> monitors. I found following cards:
>>> Gigabyte Radeon HD7770 OC
>
> [...]
>>
>> Any recent radeon hardware supports multiple monitors just fine with
>> the caveat that if you are using more than 2 non-displayport monitors,
>> they have to all use the same clock (you are limited to two
>> independent clocks), or you need active dp adapters.  If all of the
>> monitors are identical, it shouldn't be a problem.
>
> I mentioned the following radeon graphics adapter:
> http://www.gigabyte.com/products/product-page.aspx?pid=4278
> So definitely it is capable of driving for monitors. The question is if it
> is possible to configure X server in such a way that all 4 monitors
> connected to this particular adapter are in one logical DISPLAY.
> At the moment I use two dual head ATI FirePro 2270 graphics cards. As a
> consequence I have two logical (dual-monitors) DISPLAYS and I'm not able to
> span a single window across more than 2 monitors.

Yes, you can drive 4 displays off a single gpu and use them all as a
single desktop.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Quad head graphic card.

[Alex Deucher]

On Thu, Jan 23, 2014 at 4:57 PM, Grzegorz Sójka  wrote:
> Hi there,
>
> I have 4 identical monitors. So I decided to buy (not to expensive,
> around 100USD) quad head graphics card. I do not need anything
> particular. Only office applications, no gaming. The crucial thing is
> that I would like to be able to span a single window across all 4
> monitors. I found following cards:
> Gigabyte Radeon HD7770 OC
> Nvidia Quadro NVS440
> Nvidia Quadro NVS420
> Could you please confirm which ones of these cards may be configured as
> a single quad monitors DISPLAY?
> Note that both Nvidia cards are actually dual GPU.

Any recent radeon hardware supports multiple monitors just fine with
the caveat that if you are using more than 2 non-displayport monitors,
they have to all use the same clock (you are limited to two
independent clocks), or you need active dp adapters.  If all of the
monitors are identical, it shouldn't be a problem.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Xorg not working on PPC

[Alex Deucher]

On Wed, Jan 22, 2014 at 9:49 PM, Geoff Down  wrote:
> Hello List,
>  I'm installing Linux on a PowerMac G4. Since the installation with
>  Gnome failed with a black-and-white horizontal stripey screen and
>  frozen system, I was advised to try Xorg instead.
> My first attempt resulted in 'no screens found'. After a reinstall of
> the OS however, I now have the stripey screen again if I use 'startx'.
> Attached are the log from running 'startx', and from running 'X -cfg'.
> Here are my video card and display details.
> Chipset Model:  ATY,Rage128Pro
>   Type:   Display
>   Bus:AGP
>   Slot:   SLOT-1
>   VRAM (Total):   16 MB
>   Vendor: ATI (0x1002)
>   Device ID:  0x5046
>   Revision ID:0x
>   ROM Revision:   113-72701-130
>   Displays:
> 831W:
>   Resolution: 1360 x 768 @ 60 Hz
>   Depth:  32-bit Color
>   Core Image: Not Supported
>   Main Display:   Yes
>   Mirror: Off
>   Online: Yes
>   Quartz Extreme: Not Supported
>
> Can you help please? I'm new to Linux as well, so assume I know nothing
> about its internal workings.
> Thanks,
> Geoff Down

That's pretty old hardware.  I'm not sure to what extent anyone has
tested that hardware recently.  You might have better luck asking on a
ppc specific mailing list.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: [xorg-xgamma] Xgamma and xrandr discrepancy

[Alex Deucher]

On Sat, Dec 21, 2013 at 11:14 AM, Adrian C.  wrote:
> Hello I have a small issue with xgamma for a very long time that nobody
> could explain to me, so now I'd like to ask the developers.
>
> To get decent colors on my workstation and external monitors I want to
> apply gamma correction. For me these magic values do it "Gamma 0.75 0.65
> 0.60", I set them in xorg.conf for each monitor.
>
> If it happens that an external monitor wasn't connected when I started X
> I can attach it with xrandr. Well when I do that the colors on the
> monitor are completely off. Even though xgamma reports "-> Red 0.750,
> Green 0.650, Blue 0.600" when I check, the colors are simply wrong. I
> have to kill X, start, and everything is back to normal. These forced
> restarts partly defeat the hotplugging ideas in xrandr.
>
> Here's what Xorg.0.log has to say:
>> [ 44816.100] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0)  unless 
>> otherwise stated.
>> [ 44816.101] (II) intel(0): Output VGA1 wants gamma correction (0.8, 0.6, 
>> 0.6)
>
> Trying to correct colors my self, after using xrandr, isn't succesful.
> xgamma doesn't produce good colors. I have also tried to set gamma with
> xrandr, both when attaching the display or afterwords, i.e. by using
> this switch --gamma 0.75:0.65:0.60 or --gamma 0.8:0.6:0.6. This produces
> bad results as well. Colors are always wrong, always very washed out to
> my eye.
>
> Nothing but an X restart does it for years, across 5 portable computers
> and all forms and sizes of CRT and LCD monitors. Could anyone explain
> why? Thanks.

IIRC, xgamma doesn't work with xrandr 1.2+ capable drivers since they
support per display gamma correction and xgamma assumes only a single
display.  I believe the proper way to adjust it is to use xrandr.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: %(user_address)s

Re: Horizontal timing range S3VIRGE

[Alex Deucher]

On Thu, Nov 7, 2013 at 9:39 AM, Martin  wrote:
> IHAC,
>
> If my video card + monitor can do: "S3VIRGE(0):
> Modeline "1400x1050"x74.8  155.80  1400 1464 1784 1912  1050 1052 1064 1090
> +hsync +vsync (81.5 kHz)", shouldn't it also be able to do:
> "Modeline "1920x1080_67.50"  148.50  1920 2008 2052 2200  1080 1084 1089
> 1125 +hsync +vsync"
>
> I get: "S3VIRGE(0): Not using mode "1920x1080_67.50" (horizontal timing out
> of range)"
>
> The horizontal timing range is: "Monitor0: Using hsync range of 30.00-81.00
> kHz"  and  "Clock range:  10.00 to 270.00 MHz"
>
> I calculated that v-refresh = 67.5 Hz, H-scan lines=60.0kHz and Dot clock =
> 148.5 MHz  (for the 1920x1080 resolution)
>
> All parameters are well within the reported ranges
> Can you explain why it reports "(horizontal timing out of range)"?, the
> pixel clock is below its maximum and when I calculate the hsync range it
> fall within its range of 30.00-81.00 kHz?
>
> (I'm running at 16 bits color depth).
>
> Why is the Horizontal timing out of range and how can I verify it?

Check the source of the driver to verify for sure, but I suspect you
are hitting a hardware limit on one of the horizontal timing
registers.  My guess is the htotal register probably only has 11 bits
or something like that which would only allow for a max htotal of 2047
(or 2048 depending on how it's programmed) and your 1920x1080 modeline
has an htotal value of 2200.

Alex

>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: %(user_address)s
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: XRANDR outputs

[Alex Deucher]

On Tue, Oct 15, 2013 at 2:53 AM, Russell Shaw  wrote:
> Hi,
> After a system upgrade, xrandr no longer reports two monitors connected to
> the video card. I get:
>
> xrandr: Failed to get size of gamma for output default
> Screen 0: minimum 640 x 400, current 1600 x 1200, maximum 1600 x 1200
> default connected 1600x1200+0+0 0mm x 0mm
>1600x1200   0.0*
>1280x1024   0.0
>1152x8640.0
>1024x7680.0
>800x600 0.0
>640x480 0.0
>720x400 0.0
>

Looks like something broke during your upgrade.  It looks like ended
up with the vesa driver rather than radeon.  Check your dmesg output
and xorg log.  Make sure you have the firmware packages installed for
your distro.

Alex


>
> Both monitors (one DVI, other VGA) are showing the same image, but the
> second monitor can't handle 1600x1200.
>
>
> On debian/unstable i have:
>
> libdrm-radeon1:i386  2.4.46-3  i386
> Userspace interface to radeon-specific kernel DRM services -- runtime
>
> xserver-xorg-video-radeon  1:7.2.0-1+b2  i386
> X.Org X server -- AMD/ATI Radeon display driver
>
> xrandr 1.4
>
>
> lspci -vv
>
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
> RV610 [Radeon HD 2400 PRO/XT] (prog-if 00 [VGA controller])
> Subsystem: Gigabyte Technology Co., Ltd Device 2190
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> SERR-  Latency: 0, Cache Line Size: 32 bytes
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at d000 (64-bit, prefetchable) [size=256M]
> Region 2: Memory at fe8e (64-bit, non-prefetchable) [size=64K]
> Region 4: I/O ports at c000 [size=256]
> Expansion ROM at fe8c [disabled] [size=128K]
> Capabilities: [50] Power Management version 3
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [58] Express (v1) Legacy Endpoint, MSI 00
> DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us,
> L1 unlimited
> ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
> DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
> Unsupported-
> RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
> MaxPayload 128 bytes, MaxReadReq 128 bytes
> DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
> TransPend-
> LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1,
> Latency L0 <64ns, L1 <1us
> ClockPM- Surprise- LLActRep- BwNot-
> LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
> CommClk+
> ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
> LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+
> DLActive- BWMgmt- ABWMgmt-
> Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
> Address:   Data: 
> Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1
> Len=010 
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: 3D Acceleration support for AMD Trinity APUs?

[Alex Deucher]

On Tue, Sep 24, 2013 at 9:32 AM, Andrei Tolentino
 wrote:
> Hi, I was wondering if there is already 3D Acceleration support for the AMD
> Trinity APU line?

Yes.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Help? Xinerama with two cards

[Alex Deucher]

On Sat, Jul 13, 2013 at 1:02 AM, David Iannucci
 wrote:
> On Fri, Jul 12, 2013, at 3:56, Alex Deucher wrote:
>> > At the very least, I would really like to know the truth about
>> > (1) whether X.org has never, historically, been able to drive a dual-
>> > head setup off of two GPUs, and
>>
>> X has been able to drive multiple GPUs for years via a static
>> xorg.conf.
>
> Thanks Alex... this is good to know. If "years" = 2 or 3, then
> the information I got could have predated this situation, but if
> years means a really long time, then I was clearly misled.

10+ years.

Alex

>
>> >(2) whether xrandr 1.4 is really supposed to remedy this.
>>
>> It's a start, but it's still not there for all configurations.  The
>> provider stuff in xserver 1.14 was mainly focused on support for
>> hybrid laptops and hot-pluggable USB display adapters.
>
> I see. Helpful!
>
> Dave
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Help? Xinerama with two cards

[Alex Deucher]

On Fri, Jul 12, 2013 at 6:13 PM, Felix Miata  wrote:
> On 2013-07-11 19:04 (GMT-1000) David Iannucci composed:
>
>>> KDE 4.11 has KScreen, which is supposed to provide easy management of
>>> multi screen configuration.
>
>
>> Trying to go more minimalist, not more bloatist :-) :-)
>
>
> You might have to anyway. According to the last section on
> https://wiki.archlinux.org/index.php/Multihead#Xinerama it appears what's
> getting in the way of success is KDE itself.
>
> In spite of having seen that over an hour ago, I've been spending more time
> trying myself. With the Radeon card removed from the slot, and cables
> connected to the only two ports, the  log reports.
>
> (II) intel(0): Output VGA1 connected
> (II) intel(0): Output HDMI1 connected
> (II) intel(0): Output DP1 disconnected
>
> The motherboard has nothing like a DP connector or solder points where one
> might have been. The HDMI1 port has only a DVI-D connector, which I connect
> to the TV with a 25' DVI to HDMI cable.
>
> When I put the Radeon back in the slot, the string HDMI is nowhere to be
> found in the log, though this may be about a BIOS setting. The BIOS has 5
> video configuration options "Initiate Graphic Adapter" described asr which
> to use as primary boot device, with nothing that explains how to select the
> one most appropriate:
>
> IGD
> PCI/IGD
> PCI/PEG
> PEG/IGD
> PEG/PCI (default after clear CMOS and load optimal defaults)
>
> Below that is "Boot Display Device", which without the Radeon in the slot
> offers:
> D-SUB + HDMI
> D-SUB + DVI
> Only DisplayPort
>
> Next is "IGD Graphics Mode Select" offering either disabled or enabled
> coupled with 3 different RAM sizes.
>
> Others to config include "Video Function Configuration" for DVMT memory, PEG
> port either enabled or auto, and PAVP mode either disabled, Lite or High.
>
> WRT BIOS settings with DVI connected to Radeon and VGA connected to Intel:
> IGD with D-SUB + HDMI:  puts vt output only on VGA
> IGD with D-SUB + DVI:   puts vt output only on VGA
> PCI/IGD with D-SUB + HDMI:  puts vt output only on VGA
> PCI/IGD with D-SUB + DVI:   puts vt output only on VGA
> PCI/PEG with D-SUB + HDMI:  puts vt output only on DVI
> PCI/PEG with D-SUB + DVI:   puts vt output only on DVI
> PEG/IGD with D-SUB + HDMI:  puts vt output only on DVI
> PEG/IGD with D-SUB + DVI:   puts vt output only on DVI
> PEG/PCI with D-SUB + HDMI:  puts vt output only on DVI
> PEG/PCI with D-SUB + DVI:   puts vt output only on DVI
> summary: PEG enabled = DVI; else VGA
>
> WRT BIOS settings with VGA connected to Radeon and DVI connected to Intel:
> IGD with D-SUB + HDMI:  no vt output; VGA asleep; DVI awake but all
> black
> IGD with D-SUB + DVI:   no vt output; VGA asleep; DVI awake but all
> black
> PCI/IGD with D-SUB + HDMI:  no vt output; VGA asleep; DVI awake but all
> black
> PCI/IGD with D-SUB + DVI:   no vt output; VGA asleep; DVI awake but all
> black
> PCI/PEG with D-SUB + HDMI:  puts vt output only on VGA; DVI awake but
> all black
> PCI/PEG with D-SUB + DVI:   puts vt output only on VGA; DVI awake but
> all black
> PEG/IGD with D-SUB + HDMI:  puts vt output only on VGA; DVI awake but
> all black
> PEG/IGD with D-SUB + DVI:   puts vt output only on VGA; DVI awake but
> all black
> PEG/PCI with D-SUB + HDMI:  puts vt output only on VGA; DVI awake but
> all black
> PEG/PCI with D-SUB + DVI:   puts vt output only on VGA; DVI awake but
> all black
> summary: radeon VGA connection disables Intel DVI output
>

I'm not too familiar with Intel hardware, but I suspect the pcie lanes
are shared with display channels so if you have a pcie card in the
slot, some of the displays are not available.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Help? Xinerama with two cards

[Alex Deucher]

On Fri, Jul 12, 2013 at 1:04 AM, David Iannucci
 wrote:
> Thanks for the responses Felix and Dave.  I will rearrange the
> quotations below a bit:
>
>> I find config files easier to work with than xrandr. You might
>> want to try. My last dual head session with Intel and Radeon left
>> these behind:
>
> Thanks... checked these out. I took your advice and did my best to
> craft an xorg.conf based on your examples and other documentation I
> found, but nothing is happening on my second monitor (this doesn't
> surprise me much).
>
> I have read a few times now that Xorg is not supposed to need config
> files any more - that it's mostly self-configuring, and xrandr is the
> way to go to manipulate your display if you need to, and this appeals to
> me a lot. I never was very comfortable with xorg.conf :-)
>
> Please recall that what I'm trying to do is drive two heads off of
> _two different_ GPUs. I was told a few years ago by someone who
> seemed to know what he was talking about that X just doesn't DO that
> (at the time). My understanding was that recent changes in xrandr 1.4
> would allow it.
>
>> KDE 4.11 has KScreen, which is supposed to provide easy management of
>> multi screen configuration.
>
> Trying to go more minimalist, not more bloatist :-) :-)
>
> So here's the nutshell of what I'm left with:
>
> Xrandr shows me 3 outputs: VGA1, HDMI2, and DP1 (with only VGA1
> "connected", even though 2nd monitor is plugged into DVI port of
> Radeon). This DP1 original fooled me into thinking that the 2nd port on
> my Radeon card was a DisplayPort, but close examination shows it to be
> HDMI. So "DP1" is confusing. Between the 2 GPUs there are 4 output ports
> (two on each), so the fact that xrandr shows me 3 is a hint that my
> kernel is ok? But why not four?
>
> Finally, perhaps I failed to mention before that sometimes partial
> chunks of output (system boot messages), or a "distortion pattern" (?)
> appear on monitor 2. This is encouraging to me, but I don't know if it's
> really good news.
>
> Anyone who missed my original post can look below to see that
> xrandr --listproviders gives a sensible output.
>
> Hoping that this, my last post on the topic before giving up and
> probably buying an HDMI-VGA adaptor, will attract the attention of
> someone who knows how to troubleshoot it.
>
> At the very least, I would really like to know the truth about
> (1) whether X.org has never, historically, been able to drive a
> dual-head setup off of two GPUs, and

X has been able to drive multiple GPUs for years via a static xorg.conf.

>(2) whether xrandr 1.4 is really
> supposed to remedy this. Thanks a lot.
>

It's a start, but it's still not there for all configurations.  The
provider stuff in xserver 1.14 was mainly focused on support for
hybrid laptops and hot-pluggable USB display adapters.

Alex

> Dave
>
>
>
> On Tue, Jul 2, 2013, at 13:52, Felix Miata wrote:
>> On 2013-07-02 13:21 (GMT-1000) David Iannucci composed:
>>
>> > David Iannucci wrote:
>>
>> >> I'm trying to set up a xinerama arrangement over two graphics cards
>> >> (Intel + Radeon), taking advantage of xrandr 1.4's features which
>> >> (I understand, perhaps mistakenly, to) support this configuration.
>> >> I'm running xorg server 1.13.4 on Gentoo. It might be useful for
>> >> you to know in addition that I'm running a barebones KDE 3.5.10
>> >> desktop on it.
>>
>> >> If I do --listproviders, I get both cards listed:
>>
>> >> # xrandr --listproviders
>> >> Providers: number : 2
>> >> Provider 0: id: 0x87 cap: 0xb, Source Output, Sink Output, Sink
>> >> Offload crtcs: 3 outputs: 3 associated providers: 0 name:Intel
>> >> Provider 1: id: 0x57 cap: 0xd, Source Output, Source Offload, Sink
>> >> Offload crtcs: 6 outputs: 2 associated providers: 0 name:radeon
>>
>> >> However no use of --setprovideroutputsource or
>> >> --setprovideroffloadsink (with arguments "0 1" or "1 0") will do
>> >> what I want.  Am I completely misunderstanding this?
>>
>> >> One monitor is connected to VGA output of integrated Intel GPU, and
>> >> the other to DVI output of Radeon (HD 7570) PCI card.  I think kernel
>> >> stuff is set up properly:
>>
>> >> # lsmod | grep radeon
>> >> radeon858404  1
>> >> cfbfillrect 3714  2 i915,radeon
>> >> cfbimgblt   2039  2 i915,radeon
>> >> ttm58739  1 radeon
>> >> cfbcopyarea 3350  2 i915,radeon
>> >> drm_kms_helper 26569  2 i915,radeon
>> >> fb 33637  6
>> >> i915,fbcon,drm_kms_helper,radeon,softcursor,bitblit
>> >> backlight   4248  2 video,radeon
>>
>> >> Please document this functionality more clearly! Any help with this
>> >> will be much appreciated. I can try to end-run the problem by asking
>> >> my boss to buy me an HDMI-capable monitor, to plug into the second
>> >> port of Intel card, but I've already got the Radeon, and I'd rather
>> >> try to figure this out before throwing money at it :-) Thx.
>>
>> > S

Re: Triple monitor, one card; xrandr => xorg.conf

[Alex Deucher]

On Wed, May 29, 2013 at 1:20 AM, Nick Urbanik  wrote:
> Dear Alex,
>
> Thank you so much for taking the time to make a thoughtful reply.
>
> On 29/05/13 00:21 -0400, Alex Deucher wrote:
>>
>> On Sat, May 25, 2013 at 9:00 AM, Nick Urbanik  wrote:
>> You can skip the above lines if you just change the monitor
>> identifiers to match your output names.  Also, I'm not sure that
>> having relative locations for every monitor will work correctly.  For
>> the farthest left one, leave out the orientation.
>>
>>> EndSection
>>
>>
>> Try something like this:
>>
>>
>> Section "Device"
>>  Identifier "ati-5450"
>> EndSection
>>
>> Section "Monitor"
>>   Identifier "DVI-0"
>> EndSection
>>
>> Section "Monitor"
>>   Identifier "DisplayPort-0"
>>   Option "RightOf" "DVI-0"
>> EndSection
>
>
> Yes, that works for when lightdm starts: the screens are in the right
> order.  Its simplicity is beautiful (the xorg.conf you wrote).
>
> But when I log into XFCE 4.10, then it does as described in my last
> post on this topic: VGA-0 on the left, then DVI-0, then at 1900 pixels
> from the left of VGA-0, which takes us into the territory of DVI-0,
> then DisplayPort-0 continues, mirroring DVI-0 for all but 150 pixels
> on the left and 150 on the right.  Is it XFCE being naughty?
>
> As before, my xrandr command makes everything pop into the right place
> and behave properly, but I'd like to have things "just work".
>
> As a probably unrelated side issue, neither gdm nor Gnome 3 start up,
> regardless of presence or shape of xorg.conf.

If X comes up ok without a display manager or desktop environment,
your config should be working fine.  Different display managers and
desktop environments try and remember your display configuration in
various ways and I suspect you are running into issues with them
conflicting with your xorg.conf.  If there is a monitor config gui for
your desktop environment, I'd suggest removing your xorg.conf and
using the gui to set up and remember your monitor configuration.
Hopefully that should use the desktop specific mechanisms to remember
your configuration.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Triple monitor, one card; xrandr => xorg.conf

[Alex Deucher]

On Sat, May 25, 2013 at 9:00 AM, Nick Urbanik  wrote:
> Dear Folks,
>
> It is trivially easy to set up three monitors with an ATI 5450 video
> card.  One is plugged into the VGA, the other into the DVI, and the
> last into the DisplayPort connector.
>
> Now I want the display port monitor in the middle, as it is the most
> fabulous.
>
> This is easy with xrandr:
> xrandr --output DVI-0 --mode 1920x1200 --output DisplayPort-0 --mode
> 1920x1200 --right-of DVI-0 --output VGA-0 --mode 1600x1200 --right-of
> DisplayPort-0
>
> which works like a charm.
>
> Now trying to write that as xorg.conf.  Miserable failure.  And Gnome
> 3 is unable to start.
>
> So here is the xorg.conf I have tried so far:
>
> Section "Device"
>   Identifier "ati-5450"
>   Option "Monitor-DVI-0" "left"
>   Option "Monitor-DisplayPort-0" "middle"
>   Option "Monitor-VGA-0" "right"

You can skip the above lines if you just change the monitor
identifiers to match your output names.  Also, I'm not sure that
having relative locations for every monitor will work correctly.  For
the farthest left one, leave out the orientation.

> EndSection

Try something like this:


Section "Device"
  Identifier "ati-5450"
EndSection

Section "Monitor"
   Identifier "DVI-0"
EndSection

Section "Monitor"
   Identifier "DisplayPort-0"
   Option "RightOf" "DVI-0"
EndSection

Section "Monitor"
   Identifier "VGA-0"
   Option "RightOf" "DisplayPort-0"
EndSection

>
> Section "Monitor"
>   Identifier "left"
> EndSection
>
> Section "Monitor"
>   Identifier "middle"
>   Option "RightOf" "left"
> EndSection
>
> Section "Monitor"
>   Identifier "right"
>   Option "RightOf" "middle"
> EndSection
>
> and here is the output of xrandr:
> $ xrandr
> Screen 0: minimum 320 x 200, current 5440 x 1200, maximum 8192 x 8192
> DisplayPort-0 connected 1920x1200+1920+0 (normal left inverted right x axis
> y axis) 518mm x 324mm
>1920x1200  60.0*+
>1920x1080  60.0 1600x1200  60.0 1680x1050  60.0
> 1280x1024  60.0 1280x960   60.0 1024x768   60.0
> 800x60060.3 640x48060.0 720x40070.1  DVI-0
> connected 1920x1200+0+0 (normal left inverted right x axis y axis) 518mm x
> 324mm
>1920x1200  60.0*+
>1920x1080  50.0 60.0 1600x1200  60.0 1680x1050
> 59.9 1280x1024  60.0 1440x900   59.9 1280x960   60.0
> 1280x800   59.9 1280x720   50.0 60.0 1024x768   60.0
> 800x60060.3 56.2 720x57650.0 720x48059.9
> 640x48060.0  VGA-0 connected 1600x1200+3840+0 (normal left inverted
> right x axis y axis) 408mm x 306mm
>1600x1200  60.0*+
>1280x1024  75.0 60.0 1280x960   60.0 1152x864
> 75.0 1024x768   75.1 70.1 60.0 832x62474.6
> 800x60072.2 75.0 60.3 56.2 640x48072.8
> 75.0 66.7 60.0 720x40070.1
> Any suggestions on how to make a working xorg.conf?
>
> Fedora 18 x86_64:
> xorg-x11-server-Xorg-1.13.3-3.fc18.x86_64
> xorg-x11-drv-ati-7.0.0-0.9.20121015gitbd9e2c064.fc18.x86_64
> $ xrandr --version
> xrandr program version   1.4.0
> Server reports RandR version 1.4
> --
> Nick Urbanik http://nicku.org   ni...@nicku.org
> GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: black background and HW acceleraed rendering

[Alex Deucher]

On Fri, May 10, 2013 at 10:41 AM, Ratin  wrote:
> Hi All, I am using hardware accelerated video rendering on X windows, I want
> to set the default background color for windows to be black. It seems that
> every effort of doing that fails, i.e. when the HW accelerated video display
> queue is terminated, I end up with a green window, not black or alpha
> blended window showing whatever left at the GPU queue. I wanted to know if
> there is a way I can guarantee it will always be black when the HW backend
> process finishes with the window. Any body got any clue?

It depends on the hardware/player/API.  What combination are you using?

If you are using a video overlay with Xv for example, you can set the
colorkey to black via Xv attributes.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

X.Org Google Summer of Code

[Alex Deucher]

Just a reminder to all students and mentors planning to work on an
X.Org GSoC project this year, the deadline for applications is
tomorrow (May 3rd, 19:00 UTC).  If you are a student planning to
apply, please submit your application by the deadline.  If you are
planning to mentor a project and have not signed up as a mentor yet,
please log into melange and connect with the xorg organization as a
mentor from your dashboard.  If you have any additional questions, let
me know.

Thanks everyone!

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: modesetting rotation support

[Alex Deucher]

On Thu, May 2, 2013 at 4:51 PM, Stanislav Kogan  wrote:
> Hi.
>
>> Acceleration is required for rotation at the moment.
>
> So, if the KMS drive in question supports acceleration, then the
> modesetting will be able to do rotation?

The ddx needs to support the shadow alloc callbacks and accelerate
render transforms.

Alex

>
> --
>
> Stanislav Kogan
> <*>
> eMail: s.ko...@gmail.com
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: modesetting rotation support

[Alex Deucher]

On Thu, May 2, 2013 at 2:57 PM, Stanislav Kogan  wrote:
> Hello.
>
> I'm trying to use the modesetting driver on top of the gma500_gfx in
> kernel version 3.4.41 and have problems making the rotation work. I
> get the message that rotation and reflection isn't supported. Is this
> a limitation of the gma500_gfx kms driver or the xorg modesetting
> driver? The modesetting driver I use is the 0.5.0 version.
>

Acceleration is required for rotation at the moment.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: CentOS, radeon driver, dual monitor, fun (NOT)]

[Alex Deucher]

On Fri, Apr 26, 2013 at 2:10 PM,   wrote:
> Alex Deucher wrote:
>> On Fri, Apr 26, 2013 at 11:24 AM,   wrote:
>>> Alex Deucher wrote:
>>>> On Fri, Apr 26, 2013 at 10:56 AM,   wrote:
>>>>> Alex Deucher wrote:
>>>>>> On Fri, Apr 26, 2013 at 10:26 AM,   wrote:
>>>>>>> Well, I posted this a week ago. Does *anyone* have any suggestions
> as to what I need to do with my xorg.conf to get my user back to
> normal?
> 
>>>>
>>>> Bring up X without an xorg.conf and use xrandr or the gnome monitors
> control panel to enable multi-head.  E.g.,
>>>> xrandr --auto
>>>> xrandr --output DisplayPort-0 --right-of DisplayPort-1
>>>> etc.
> 
>
> GOT IT! FINALLY! Thank you *very* much.
>
> Here's what I did:
> rm xorg.cong, 
>
> Logged in, and tried to control the monitors with the display app, and hit
> apply several times... and it did nothing.
>
> Then, reading sideways , I opened an xterm, and did:
> xrandr --output DisplayPort-0 --rotate left --right-of DisplayPort-1
> --output DisplayPort-1 --rotate left
>
> And we got there... *but* it didn't save the whole thing, just part, I
> guess: another  and it was sideways again, but you
> *could* move the cursor all over. He logged in, and using the display app,
> rotated the windows... and this time, when he hit apply, it did it, and
> confirmed.
>
> My last question: how do we keep his configuration a) between logins, and
> b) between system reboots? What is the preferred method?

Most of the DE monitor tools will remember your settings, but if not,
something like the following in your xorg.conf:

Section "Monitor"
Identifier   "Displayport-1"
Option   "Rotate"   "Left"
EndSection

Section "Monitor"
Identifier   "Displayport-0"
Option   "Rotate"   "Left"
Option   "RightOf"  "Displayport-1"
EndSection


Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: CentOS, radeon driver, dual monitor, fun (NOT)]

[Alex Deucher]

On Fri, Apr 26, 2013 at 11:24 AM,   wrote:
> Alex Deucher wrote:
>> On Fri, Apr 26, 2013 at 10:56 AM,   wrote:
>>> Alex Deucher wrote:
>>>> On Fri, Apr 26, 2013 at 10:26 AM,   wrote:
>>>>> Well, I posted this a week ago. Does *anyone* have any suggestions as
>>>>> to what I need to do with my xorg.conf to get my user back to normal?
>>> 
>>>> Did you try Dave's suggestion?  Does it work correctly using randr
>>>> before you try the legacy screen based multi-head setup?
>>>>
>>> Which was that, to try to bring up X with no xorg.conf file? I did that
>>> days before I posted; that was an obvious thing to try. No, that didn't
>>> work, it left me, IIRC, with one screen. Xorg --configure reported it
>>> had failed, showed four monitors (?), and left me with both lit, but one
>>> completely unreachable.
>>
>> Bring up X without an xorg.conf and use xrandr or the gnome monitors
>> control panel to enable multi-head.  E.g.,
>> xrandr --auto
>> xrandr --output DisplayPort-0 --right-of DisplayPort-1
>> etc.
>>
>> Make sure that works first before trying to use zaphod mode.
>
> Wait - zaphod mode? I've never seen or used that, and my user has heard of
> it, but thought that was for multiple keyboards and mice, but one display.
> We just want the two monitors to act as one large screen.

You can do that with xrandr.  In fact xrandr is the preferred way to
handle that.  zaphod (screen based multi-head config in your
xorg.conf) is for independent multi-head (where you can't drag windows
between monitors) or for multi-card multi-head and is not as well
tested or supported as xrandr.

>>
>> Post the output of xandr without an xorg.conf here if that doesn't work.
>>
> You mean xrandr -q?

just xrandr or xrandr --verbose

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: CentOS, radeon driver, dual monitor, fun (NOT)]

[Alex Deucher]

On Fri, Apr 26, 2013 at 10:56 AM,   wrote:
> Alex Deucher wrote:
>> On Fri, Apr 26, 2013 at 10:26 AM,   wrote:
>>> Well, I posted this a week ago. Does *anyone* have any suggestions as to
>>> what I need to do with my xorg.conf to get my user back to normal?
> 
>> Did you try Dave's suggestion?  Does it work correctly using randr
>> before you try the legacy screen based multi-head setup?
>>
> Which was that, to try to bring up X with no xorg.conf file? I did that
> days before I posted; that was an obvious thing to try. No, that didn't
> work, it left me, IIRC, with one screen. Xorg --configure reported it had
> failed, showed four monitors (?), and left me with both lit, but one
> completely unreachable.

Bring up X without an xorg.conf and use xrandr or the gnome monitors
control panel to enable multi-head.  E.g.,
xrandr --auto
xrandr --output DisplayPort-0 --right-of DisplayPort-1
etc.

Make sure that works first before trying to use zaphod mode.

Post the output of xandr without an xorg.conf here if that doesn't work.

Alex

>
> Right now, so he can work, I've got it using xrandr, xinerama off, and he
> can drag a mouse between windows, but cannot drag anything else between
> them.
>
> And if the problem with xinerama wasn't clear, here's some ascii art:
>
>_  _
>| |  | | |  |
>| |  | | |  |
>| |  | | |  |
>| |__| | |__|
>|| ||
>
> That's what it looks like after moving the mouse around, with the "L"
> black, and offscreen. Again, using a mouse, we can move it up and down, so
> as to see the whole screen, but cannot move the mouse right to push the
> screen back to the left.
>
> This is what I meant about it looking as though the viewport, or whatever
> the correct X term is, is larger than the screen, though I can't imagine
> why. I've also tried putting in the absolute offset, and that makes no
> difference.
>
>mark
>> Alex
>>
>>>
>>>   mark
>>>
>>>  Original Message
>>> 
>>> Subject: CentOS, radeon driver, dual monitor, fun (NOT)
>>> From:m.r...@5-cent.us
>>> Date:Fri, April 19, 2013 14:56
>>> To:  xorg@lists.x.org
>>> --
>>>
>>> I've just joined the list in desperation, after days of fighting this.
>>>
>>> The ati & radeon drivers in CentOS (== RHEL) 6.4 are what I need to use,
>>> since neither kmod-fglrx nor the proprietary drivers from AMD/ATI have
>>> now
>>> dropped all support for "older" cards. My user has an Advanced Micro
>>> Devices [AMD] nee ATI RV620 [FirePro 2260] card, which is among those no
>>> longer supported (and it was in a machine we got in Nov!).
>>>
>>> Here's the problem: he's got two monitors. Like the rest of us, and as
>>> he
>>> was doing, he wants them side-by-side, like one large screen. I've tried
>>> Xorg --configure, which failed, and I've handcrafted some. The two best
>>> I've gotten give us a choice:
>>>a) I can enable xinerama, which I gather is xor with randr. In that
>>> case, we
>>>  get what we want... EXCEPT that you can drag things offmonitor.
>>> and if
>>>  go a tad too far, what you wind up where you can move it up and
>>> down,
>>>  off monitor, but the whole thing moves right, and won't come
>>> back. The
>>>  result is an "L" of black; in ascii art,
>>>      _
>>>   |B| |  |B|  |
>>>   |B| |  |B|  |
>>>   |B| |  |B|  |
>>>   |B| |  |B|  |
>>>   |BBB|  ||
>>>   -   -
>>>b) I can disable xinerama, in which case we can drag the mouse from
>>>monitor to monitor, but once logged in, you cannot drag a
>>> *window*
>>>from one to the other, and they seem to almost be like two
>>> sessions,
>>>with slightly different menus (he's using gnome; I installed the
>>>gconf-editor, and disabled the xrandr plugin for gnome, so what I
>>>get is all my xorg.conf file.
>>>
>>> The latter xorg.conf is as follows:
>>>

Re: CentOS, radeon driver, dual monitor, fun (NOT)]

[Alex Deucher]

On Fri, Apr 26, 2013 at 10:26 AM,   wrote:
> Well, I posted this a week ago. Does *anyone* have any suggestions as to
> what I need to do with my xorg.conf to get my user back to normal?
>
> (And please don't tell me to buy a new card: if you think we can just pop
> for one, call your US Congresscritters and tell them to repeal the
> Sequester.)


Did you try Dave's suggestion?  Does it work correctly using randr
before you try the legacy screen based multi-head setup?

Alex

>
>   mark
>
>  Original Message 
> Subject: CentOS, radeon driver, dual monitor, fun (NOT)
> From:m.r...@5-cent.us
> Date:Fri, April 19, 2013 14:56
> To:  xorg@lists.x.org
> --
>
> I've just joined the list in desperation, after days of fighting this.
>
> The ati & radeon drivers in CentOS (== RHEL) 6.4 are what I need to use,
> since neither kmod-fglrx nor the proprietary drivers from AMD/ATI have now
> dropped all support for "older" cards. My user has an Advanced Micro
> Devices [AMD] nee ATI RV620 [FirePro 2260] card, which is among those no
> longer supported (and it was in a machine we got in Nov!).
>
> Here's the problem: he's got two monitors. Like the rest of us, and as he
> was doing, he wants them side-by-side, like one large screen. I've tried
> Xorg --configure, which failed, and I've handcrafted some. The two best
> I've gotten give us a choice:
>a) I can enable xinerama, which I gather is xor with randr. In that
> case, we
>  get what we want... EXCEPT that you can drag things offmonitor.
> and if
>  go a tad too far, what you wind up where you can move it up and
> down,
>  off monitor, but the whole thing moves right, and won't come
> back. The
>  result is an "L" of black; in ascii art,
>      _
>   |B| |  |B|  |
>   |B| |  |B|  |
>   |B| |  |B|  |
>   |B| |  |B|  |
>   |BBB|  ||
>   -   -
>b) I can disable xinerama, in which case we can drag the mouse from
>monitor to monitor, but once logged in, you cannot drag a *window*
>from one to the other, and they seem to almost be like two sessions,
>with slightly different menus (he's using gnome; I installed the
>gconf-editor, and disabled the xrandr plugin for gnome, so what I
>get is all my xorg.conf file.
>
> The latter xorg.conf is as follows:
> Section "ServerFlags"
> Option"AllowMouseOpenFail" "true"
> EndSection
>  of files, and input device>
> Section "Module"
> Load  "glx"
> EndSection
>
> Section   "Device"
>   Identifier  "mycard0"
>   Driver  "radeon"
>   BusID   "PCI:2:0:0"
>   Screen  0
> EndSection
>
> Section   "Device"
>   Identifier  "mycard1"
>   Driver  "radeon"
>   BusID   "PCI:2:0:0"
>   Screen  1
> EndSection
>
> Section   "Monitor"
>   Identifier  "mymon0"
>   Option  "Monitor-DisplayPort-0"
>   Option  "Rotate" "left"
> #   Option  "Position" "0 0"
> EndSection
> Section   "Monitor"
>   Identifier  "mymon1"
>   Option  "Monitor-DisplayPort-1"
>   Option  "Rotate" "left"
> EndSection
>
> Section   "Screen"
>   Identifier  "myhead0"
>   Device  "mycard0"
>   Monitor "mymon0"
>   DefaultDepth  24
>   SubSection  "Display"
> Depth 24
> Modes "1280x1024"
>   EndSubSection
> EndSection
>
> Section   "Screen"
>   Identifier  "myhead1"
>   Device  "mycard1"
>   Monitor "mymon1"
>   DefaultDepth  24
>   SubSection "Display"
> Depth 24
> Modes "1280x1024"
>   EndSubSection
> EndSection
>
> Section "ServerLayout"
>   Identifier  "layout0"
>   InputDevice "keyboard0" "CoreKeyboard"
>   InputDevice "mouse0" "CorePointer"
>   Screen  0 "myhead0" RightOf "myhead1"
>   Screen  1 "myhead1"
>   Option  "Xinerama" "0"
> EndSection
>
> Any clues for the poor gladly accepted.
>
>  mark
>
>
>
>
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

GSoC Call for Projects and Mentors

[Alex Deucher]

As some of you may know, the X.Org Foundation was accepted as a GSoC
Project for 2013.  If you would be interested in participating as
either a mentor or a student, please sign up here:
http://www.google-melange.com/gsoc/homepage/google/gsoc2013

For students, you can see some potential projects ideas here to get you started:
http://www.x.org/wiki/SummerOfCodeIdeas

If anyone has any questions, let me know.

Thanks!

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Display Problem

[Alex Deucher]

On Thu, Mar 14, 2013 at 2:11 AM, Adit  wrote:
> hi, I'm a new user on linux, I use 1152x864 with a refresh rate of 60Hz,
> unfortunately, linux code doesn't support it natively. I've got resolution,
> But every time I have to run a command, when i boot up.
> xrandr --newmode "1152x864_60.00"  81.75  1152 1216 1336 1520  864 867 871
> 897 -hsync +vsync ; xrandr --addmode VGA1 1152x864_60.00 ; xrandr --output
> VGA1 --mode 1152x864_60.00
> this one. Can i make linux to support 60Hz resolution? My video card is
> intel's G41 I think.

You'll need to add an xorg.conf.  Add a monitor section for the
display you want to add the mode to and include a the modeline in the
monitor section.  For more details see this page:
http://wiki.debian.org/XStrikeForce/HowToRandR12

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Starting kernel module programming

[Alex Deucher]

On Fri, Mar 8, 2013 at 7:37 AM, karan garg  wrote:
> Hi guys,
>
> I am an avid linux user and have been using Linux for over two years. I did
> my RHCE two years ago, and have a fair knowledge about BASH scripting as
> well. I want to begin with kernel module programming under the XORG
> community. So please help me with how to start and proceed. I have a basic
> knowledge of C language as well.

Basically start reading the code for whatever aspect of the kernel
interests you and start asking questions.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: DVI output > monitor blinking at max res. in X session (VGA - OK, text mode OK)

[Alex Deucher]

On Sun, Feb 3, 2013 at 7:54 AM, Eduard Tibet  wrote:
> Hello!
>
> I've already post this message to other several X-related forums some
> time ago, but unfortunately I didn't get some information from there.
> Seems that other people didn't faced such problems. Searching this
> list for such problem gives some results but don't seem to be the same
> as mine.
>
> Initial state:
> I have 1 graphic card (based on ATI Radeon 9200) and 2 monitors (both
> EIZO) with Debian 6.0 powered PC (default kernel 2.6.32.5-686).
> Monitors have different resolutions: S1961 (1280x1024) and L985EX
> (1600x1200). I use only single monitor each time (the other one even
> doesn't connected to signal output). Both are works OK in console
> (text) modes at all outputs (so technically they are seems to be OK).
> S1961 works OK in all modes at all outputs in X session (DVI, VGA).
> But L985EX has very strange problem: it works OK in all modes at VGA
> output, but begins to blink when using DVI output. It seems like
> monitor probing procedure takes place (i.e.: blank screen 1-2 sec. >
> restoring image 2-3 sec. > blank screen again 1-2 sec. > restoring
> image 2-3 sec.). Other interesting thing that the frequency of such
> behaviour is mostly depends on resolution. At default (max res.)
> 1600x1200 there are no possible to do anything in X session (blanking
> and stable image are approx. 2 sec. each). If I change the resolution
> to 1280x1024 X session begin more stable (blanking for 1 sec with
> 20-30 sec. interval of stable image). If I change the resolution
> futher to 1024x768 X session begin most stable at DVI output. I don't
> face any blinking at all.

Sounds like display bandwidth issues.  You might try setting the
display priority to high:
radeon.disp_priority=2
As per your attempt 4 below.  As for the error you are getting, your
kernel may be too old to support that parameter.  A newer kernel may
work better in general.

Alex

>
> My experiments to solve the issue:
> Try 1. First I tried to use other hdd with other non X-based OS and it
> seems to be OK at 1600x1200 at DVI so it seems not to be a real
> hardware problem.
> Try 2. Then I tried to upgrade X.org to most recent version from
> debian backports repo (first - was, second - upgraded): xserver-xorg
> (7.5.8 > 7.6.8), xserver-xorg-core (1.7.7.14 > 1.10.4.1)
> xserver-xorg-video-radeon (6.13.1.2 > 6.14.2.1). Sorry for the
> packages name - they are debian specific, because I don't know how it
> called in X repo. But nothing happened.
> Try 3. I tried to play with xrandr modes, but no success.
> Try 4. I tried to put radeon.disp_priority=2 at kernel boot (as
> mentioned at [1], [2], [3]) but got an error message: "[5.433004]
> radeon: Unknown parameter `disp_priority'" (initial call string:
> [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686
> root=UUID=4ddfc6de-7006-47ae-b142-7fdf1228beae ro quiet
> radeon.disp_priority=2 )
>
> Now I don't know where to digg to solve the issue.
>
> I know that I need to provide the X.org.log and dmesg.out, but I don't
> know, if I allowed to send it directly to the list.
>
> [1] https://bugzilla.kernel.org/show_bug.cgi?id=26552
> [2] https://bugs.freedesktop.org/show_bug.cgi?id=33657
> [3] https://bugs.freedesktop.org/show_bug.cgi?id=48772
>
> --
> regards, Eduard
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Compiling xf86-video-xgi driver for ARM

[Alex Deucher]

On Tue, Jan 15, 2013 at 1:00 PM, Jeffrey Langerak
 wrote:
> at's what I am starting to conclude as well. Some of the XGI chips are
> supported by the sis driver, should that work for the Z11 as well? My
> information only tells me that it won't go any further than the Z7. Yet if X
> would tell me why the module fails at some point...
>
> I really hate this chip, the device works pretty neat, but the chip is
> impossible to work with...
>
> So my only option is to use fbdev, are there any options in xorg.conf that
> can provide some performance improvements, I've only seen a more stable
> cursor with hwcursor set to on, any further improvements are welcome.

There are databooks for the various xgi chips floating around if you
wanted to try and fix the driver yourself.  You might try the sis
driver as well.  XGI was basically the former SiS and trident graphics
teams combined into one.  Most of the chips are re-badged SiS chips,
but they did make one based on a former trident design (xg47, possibly
handled by the xf86-video-xgixp driver IIRC).

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Is it possible to force a monitor to stay in the server layout?

[Alex Deucher]

On Fri, Dec 21, 2012 at 10:52 AM, Aaron Plattner  wrote:
> On 12/21/12 06:29, Sven Berkvens-Matthijsse wrote:
>>
>> Hello,
>>
>> I can't seem to find an answer to my question anywhere on the web.
>> Either my use case is weird, or I'm not searching correctly :-)
>>
>> I have X.org server 1.11.3 running on Ubuntu. I'm using the radeon
>> driver with a Radeon HD6450. I have three monitors connected to the card
>> (all three monitors have a DVI input), and I've set up the server to
>> have all three monitors in one large desktop. This works brilliantly!
>>
>> Sometimes, I need to connect one of the monitors to another PC or other
>> equipment with a HDMI or DVI output. My problem is that if I pull out
>> one of the cables that is connected to the HD6450, that the card (and
>> the X server) will detect that the monitor has been disconnected from
>> the card. Consequently, the desktop size is modified and all my Gnome
>> panels will be jumbled. If I reconnect the monitor, it comes back
>> online, but the positioning of the windows and panels is not restored to
>> what it used to be.
>
>
> It's the X clients' job to effect that sort of policy.  In your case, it's
> probably gnome-settings-daemon.  You could try killing it as an experiment
> to see if the behavior goes away, or logging into a simpler desktop
> environment like Fluxbox that doesn't have a monitor policy daemon.
>
> I don't know offhand if gnome-settings-daemon has an option to turn off
> automatic reconfiguration of the screens.
>
>
>> What I would like is to be able to tell the X server that I don't care
>> whether monitors are disconnected or not, and that it should keep the
>> desktop size fixed, no matter which monitors are connected. My X
>> configuration file includes a full server layout section, and also
>> contains the resolutions of the monitors. Therefor, it should be
>> possible, I guess, I just don't know how. Perhaps the current software
>> is not able to handle this specific situation. I can live with it if the
>> monitors need to be connected at the time that the X server starts. As
>> long as I can disconnect them later on without the server layout and
>> desktop size changing.
>
>
> The nvidia driver has a "UseHotplugEvents" option you can use to suppress
> the RandR events that clients like gnome-settings-daemon listen for, to work
> around this sort of problem.  Maybe the radeon driver has something similar?

There's no runtime option, but you can disable udev support in the
build with the --disable-udev configure option for xf86-video-ati.  As
Aaron said, it's preferable to disable that behavior in your desktop
environment however.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: tablet as a second monitor on linux

[Alex Deucher]

On Thu, Dec 20, 2012 at 2:13 PM, Adam Groszer  wrote:
> (missed the list)
>
>
> -- Forwarded message --
> Hello,
>
> Seems like xfwm4 is the culprit, metacity handles
>
> xrandr --addmode VGA-0 1280x800
> xrandr --output VGA-0 --mode 1280x800 --right-of LVDS
>
> just fine

Ok, but those are local connectors on a single GPU, not a remote display.

Alex

>
> On Wed, Dec 19, 2012 at 2:48 PM, Alex Deucher  wrote:
>> On Wed, Dec 19, 2012 at 3:21 AM, Adam GROSZER  wrote:
>>> On 12/18/2012 08:44 PM, Alex Deucher wrote:
>>>>
>>>> On Tue, Dec 18, 2012 at 1:30 PM, Adam Groszer 
>>>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I'm trying to use an android tablet as a secondary monitor for my laptop.
>>>>> Secondary monitor as one physical would be plugged into the VGA port.
>>>>> Googling resulted in no concrete solution.
>>>>
>>>>
>>>> Does the tablet have a VGA input port and can it act as a monitor or
>>>> are you asking about using it as a virtual second monitor?  If the
>>>> latter, you can probably play with xdmx assuming you can get an
>>>> xserver running on the tablet, however, there's no real official
>>>> solution that I know of.  Anything will basically be a hack.
>>>>
>>>> Alex
>>>
>>>
>>> No VGA, I definitely need it as virtual, any communication can go only over
>>> TCP/IP.
>>>
>>> There's an xserver for android, but it's rather incomplete.
>>> Starting xfwm4 with it burps a lot of errors.
>>> As it looks the most solid way to mirror a screen to a tablet is vnc.
>>>
>>> The question is, how to create the secondary headless virtual monitor with
>>> X. I'm lost there.
>>> (Maybe I'll force with xrandr to display that secondary on the VGA against
>>> no real monitor connected.
>>> Something along:
>>> http://lists.freedesktop.org/archives/intel-gfx/2009-October/004531.html
>>> or
>>> http://askubuntu.com/questions/150879/can-i-force-vga-signal-output-even-when-xrandr-shows-disconnected
>>> Because what I actually want is like having a second monitor, but it's
>>> "attached" via vnc-TCP/IP)
>>>
>>
>> As I said, originally, you need something like xdmx:
>> http://en.wikipedia.org/wiki/Xdmx
>> It's basically a proxy xserver that connects to xservers on multiple
>> boxes and presents the result as a single xserver.
>>
>> Alex
>>
>>>>
>>>>>
>>>>> With some help of a friend, the http://pastie.org/5548492 script kind
>>>>> of works. (on xubuntu 11.10)
>>>>> Problems:
>>>>> - the XFCE top panel gets extended to the "tablet monitor"
>>>>> - the mouse pointer cannot enter the "tablet monitor"
>>>>> - both above together cause the panel to be inaccessible
>>>>>
>>>>> Any pointers are welcome, how to solve this.
>>>>>
>>>>> --
>>>>> Best regards,
>>>>>   Adam
>>>
>>>
>>> --
>>> Best regards,
>>>  Adam GROSZER
>>> --
>>> Quote of the day:
>>> It's hard to remain true to a changing self.
>
>
>
> --
> Best regards,
>  Adam
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: tablet as a second monitor on linux

[Alex Deucher]

On Wed, Dec 19, 2012 at 3:21 AM, Adam GROSZER  wrote:
> On 12/18/2012 08:44 PM, Alex Deucher wrote:
>>
>> On Tue, Dec 18, 2012 at 1:30 PM, Adam Groszer 
>> wrote:
>>>
>>> Hello,
>>>
>>> I'm trying to use an android tablet as a secondary monitor for my laptop.
>>> Secondary monitor as one physical would be plugged into the VGA port.
>>> Googling resulted in no concrete solution.
>>
>>
>> Does the tablet have a VGA input port and can it act as a monitor or
>> are you asking about using it as a virtual second monitor?  If the
>> latter, you can probably play with xdmx assuming you can get an
>> xserver running on the tablet, however, there's no real official
>> solution that I know of.  Anything will basically be a hack.
>>
>> Alex
>
>
> No VGA, I definitely need it as virtual, any communication can go only over
> TCP/IP.
>
> There's an xserver for android, but it's rather incomplete.
> Starting xfwm4 with it burps a lot of errors.
> As it looks the most solid way to mirror a screen to a tablet is vnc.
>
> The question is, how to create the secondary headless virtual monitor with
> X. I'm lost there.
> (Maybe I'll force with xrandr to display that secondary on the VGA against
> no real monitor connected.
> Something along:
> http://lists.freedesktop.org/archives/intel-gfx/2009-October/004531.html
> or
> http://askubuntu.com/questions/150879/can-i-force-vga-signal-output-even-when-xrandr-shows-disconnected
> Because what I actually want is like having a second monitor, but it's
> "attached" via vnc-TCP/IP)
>

As I said, originally, you need something like xdmx:
http://en.wikipedia.org/wiki/Xdmx
It's basically a proxy xserver that connects to xservers on multiple
boxes and presents the result as a single xserver.

Alex

>>
>>>
>>> With some help of a friend, the http://pastie.org/5548492 script kind
>>> of works. (on xubuntu 11.10)
>>> Problems:
>>> - the XFCE top panel gets extended to the "tablet monitor"
>>> - the mouse pointer cannot enter the "tablet monitor"
>>> - both above together cause the panel to be inaccessible
>>>
>>> Any pointers are welcome, how to solve this.
>>>
>>> --
>>> Best regards,
>>>   Adam
>
>
> --
> Best regards,
>  Adam GROSZER
> --
> Quote of the day:
> It's hard to remain true to a changing self.
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: tablet as a second monitor on linux

[Alex Deucher]

On Tue, Dec 18, 2012 at 1:30 PM, Adam Groszer  wrote:
> Hello,
>
> I'm trying to use an android tablet as a secondary monitor for my laptop.
> Secondary monitor as one physical would be plugged into the VGA port.
> Googling resulted in no concrete solution.

Does the tablet have a VGA input port and can it act as a monitor or
are you asking about using it as a virtual second monitor?  If the
latter, you can probably play with xdmx assuming you can get an
xserver running on the tablet, however, there's no real official
solution that I know of.  Anything will basically be a hack.

Alex

>
> With some help of a friend, the http://pastie.org/5548492 script kind
> of works. (on xubuntu 11.10)
> Problems:
> - the XFCE top panel gets extended to the "tablet monitor"
> - the mouse pointer cannot enter the "tablet monitor"
> - both above together cause the panel to be inaccessible
>
> Any pointers are welcome, how to solve this.
>
> --
> Best regards,
>  Adam
> ___
> xorg@lists.x.org: X.Org support
> Archives: http://lists.freedesktop.org/archives/xorg
> Info: http://lists.x.org/mailman/listinfo/xorg
> Your subscription address: alexdeuc...@gmail.com
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[Alex Deucher]

On Tue, Dec 11, 2012 at 5:48 AM, stompdagg...@yahoo.com
 wrote:
>>On Die, 2012-12-11 at 01:45 -0800, stompdagg...@yahoo.com wrote:
>>> >On Mon, 2012-12-10 at 11:33 -0800, stompdagg...@yahoo.com wrote:
>>> >> On Sun, Dec 9, 2012 at 12:16 PM,  
>>> wrote:
>>> >> >> When starting openSuse 12.2, the X-server terminates with a
>>> >> segmentation fault (see attached log file).
>>> >>
>>> >> >The open source driver should support your card just fine.  Can
>>> you
>>> >> >install debugging symbols and get a proper backtrace with GDB?
>>> >> >http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
>>> >>
>>> >> Alex, looking at his log, I don't see the card in the support list,
>>> >> his card is the v7700?
>>>
>>> >As you can see in the lspci output, it's a 7500, which is Turks
>>> >(Northern Islands generation) based.
>>>
>>> >If the driver didn't support the card, it would bail much earlier.
>>>
>>> looking at the xorg log, I see Turks only as part of the AMD Radeon HD
>>> 6700 Series, does this means that 7500 Series is part of the 6700
>>> Series?
>
>>It's complicated. :\
>
>>7xx0 and 6xx0 are marketing names, which are mostly irrelevant for
>>driver support, in contrast to code names such as Turks, Northern
>>Islands etc.
>
> I see, so maybe it is a good idea to fix the radeon output? if I had this
> problem, I'd assume that the driver doesn't supports the card, this would
> have wasted a lot of time.


Marketing and OEMs come up with so many different names, it's hard to
keep track.  Best bet it to look at the pci ids, or check wikipedia:
http://en.wikipedia.org/wiki/Ati_gpu

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Segmentation fault

[Alex Deucher]

On Sun, Dec 9, 2012 at 12:16 PM,   wrote:
> When starting openSuse 12.2, the X-server terminates with a segmentation 
> fault (see attached log file).

The open source driver should support your card just fine.  Can you
install debugging symbols and get a proper backtrace with GDB?
http://wiki.x.org/wiki/Development/Documentation/ServerDebugging

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: xf86-video-ati and Radeon HD 7600M Series

[Alex Deucher]

On Fri, Nov 30, 2012 at 10:27 AM,   wrote:
>
>> You might want to file a bug so we can better track this.  This thread
>> is getting unwieldy.
>> https://bugs.freedesktop.org
>> Attach your xorg log and dmesg and glxinfo output.
>>
> Will do after testing mesa 8.0.5. Against mesa with Gallium Radeon, right?
> I can try mesa git HEAD before filing too.

Mesa, drivers/gallium/r600

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: xf86-video-ati and Radeon HD 7600M Series

[Alex Deucher]

On Fri, Nov 30, 2012 at 9:44 AM, Thilo Cestonaro  wrote:
>>> And found this in Xorg.0.log:
>>> [  2219.770] (**) RADEON(G0): Option "ColorTiling2D" "False"
>>> [  2219.771] (II) RADEON(G0): KMS Color Tiling: enabled
>>> [  2219.771] (II) RADEON(G0): KMS Color Tiling 2D: disabled
>>>
>>> But it changed nothing regarding 3D glitches.
>>>
>>
>> How about disabling tiling completely?
>> Option "ColorTiling" "false"
>>
> Both ColorTiling are disabled now. But that has no effect on the 3D Glichtes.

You might want to file a bug so we can better track this.  This thread
is getting unwieldy.
https://bugs.freedesktop.org
Attach your xorg log and dmesg and glxinfo output.

>
>
>>>
 You can also try mesa 8.0.5.
>>>
>>> Should I downgrade to ver. 8.0.5?? I though that xf86-video-ati needs mesa
>>> 9.X.X ??
>>
>> xf86-video-ati 7.x needs mesa 9.x for 2D tiling.  If you disabling
>> tiling you can mix and match with older releases.
>>
>
> Ok. Will try mesa from git with tag 8.0.5  just install every lib mesa 
> builds or just specific ones?

yeah.  Just install the whole mesa package.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: xf86-video-ati and Radeon HD 7600M Series

[Alex Deucher]

On Fri, Nov 30, 2012 at 2:00 AM,   wrote:
>
>> If you are using xf86-video-ati from git, you can try disabling tiling.
>> Add:
>> Option "ColorTiling2D" "False"
>> in the device section of your xorg.conf
>
> I added a 20-radeon.conf to xorg.conf.d with this content:
> ephraim@errorl:~$ cat /usr/share/X11/xorg.conf.d/20-radeon.conf
> Section "Device"
> Identifier  "TheCard"
> Driver "radeon"
> Option "ColorTiling2D" "False"
> EndSection
>
> And found this in Xorg.0.log:
> [  2219.770] (**) RADEON(G0): Option "ColorTiling2D" "False"
> [  2219.771] (II) RADEON(G0): KMS Color Tiling: enabled
> [  2219.771] (II) RADEON(G0): KMS Color Tiling 2D: disabled
>
> But it changed nothing regarding 3D glitches.
>

How about disabling tiling completely?
Option "ColorTiling" "false"

>
>> You can also try mesa 8.0.5.
>
> Should I downgrade to ver. 8.0.5?? I though that xf86-video-ati needs mesa
> 9.X.X ??

 xf86-video-ati 7.x needs mesa 9.x for 2D tiling.  If you disabling
tiling you can mix and match with older releases.

Alex

>
> Greetings,
> Thilo
>
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: xf86-video-ati and Radeon HD 7600M Series

[Alex Deucher]

On Thu, Nov 29, 2012 at 5:18 PM,   wrote:
> Hey
>
>> So it seems to be 'just' a Mesa problem. Might be worth trying current
>> mesa Git.
>
>
> So as I should install of mesa, I upgraded to 13.04 alpha stuff, which
> includes mesa 9.0.1 ...
> sadly that didn't help.
> My current config is now:

If you are using xf86-video-ati from git, you can try disabling tiling.  Add:
Option "ColorTiling2D" "False"
in the device section of your xorg.conf

You can also try mesa 8.0.5.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: kms etc ati nouveau intel

[Alex Deucher]

On Tue, Nov 27, 2012 at 10:32 AM, Sebastian Glita  wrote:
>
> Hi,
>
> I have for some time conflicts with (I suppose) kms and git sources of 
> ati/intel/nouveau X drivers/server.
>

It's not clear what sort of problems you are having.  Please file bugs
with more details of each specific issue:
https://bugs.freedesktop.org
Make sure to attach your xorg log and dmesg output to each bug report.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

[ANNOUNCE] xf86-video-ati 7.0.0

[Alex Deucher]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

xf86-video-ati 7.0.0 is released!

This is the first KMS only release.  Major changes:
- - Enable 2D tiling by default on r6xx+ asics
  (requires mesa 9.0+).  If you are planning to
  ship xf86-video-ati 7.x with an older version of
  mesa, please disable 2D tiling.
- - xserver 1.13 support including prime
- - glamor support
- - SI support

Adam Jackson (3):
  Don't bother to include vbe.h
  Implement ->driverFunc
  Remove mibstore.h

Alex Deucher (6):
  radeon: add some new SI pci ids
  radeon: add new pci ids for SI
  man: update man pages for trinity (ARUBA)
  Revert "radeon/radeon_platform_probe: fix Zaphod mode breakage"
  man: note that 2D tiling requires Mesa 9.0 or newer
  radeon: bump version for release

Andreas Boll (1):
  radeon/man: ColorTiling2D is by default on for r6xx-cayman

Dave Airlie (42):
  radeon: drop all UMS/DRI1/XAA/overlay support.
  drop RING_LOCALS/ACCEL_PREAMBLE
  make pci chipsets static
  radeon: misc cleanups.
  radeon: drop radeon_commonfuncs.
  radeon: drop FUNC_NAME macro and ONCE_ONLY stuff
  radeon: make exa copy funcs static.
  radeon: further macro cleanups.
  radeon: drop more wrapper macros.
  radeon: move macros into radeon.h
  radeon: drop offset member of r600 accel object
  radeon: drop vb_mc_addr, not needed anymore
  radeon: drop unused txoffset vars.
  radeon: drop legacy memory, merge into radeon video
  radeon: move more functions into texture video
  radeon: drop radeonGetPixmapOffset
  radeon: drop cardType shouldn't matter to userspace.
  radeon: more unused stuff
  radeon: drop another unused struct member.
  radeon: drop some more unused macros/inlines
  radeon: avoid including large static struct twice.
  radeon: migrate remainder of radeon_driver.c to rest of driver
  radeon: fix RADEONChipsets
  radeon: fix radeonchipsets properly
  configure: bump version after release.
  configure: bump to 6.99.99
  radeon: fix conflict with fix in master.
  ati: fix stub driver loader to load all drivers properly
  radeon: damage full screen after pageflip
  radeon: add platform bus loading support.
  radeon: add shared support to pixmaps.
  radeon: add dri2 offload support.
  radeon: add pixmap sharing hooks.
  radeon: allocated shared pixmaps as untiled gtt.
  radeon: add capability and provider support
  radeon/dri2: fix build against older servers.
  radeon: fix build against older servers
  radeon: fix typo in glamor paths
  radeon: don't fail to load if we have no modes and gpu driver.
  radeon: fix build against old servers
  radeon/dri2: fix damage reporting on pageflip
  radeon/dri2: fix the window->pixmap math properly.

Ilija Hadzic (2):
  radeon/radeon_platform_probe: fix Zaphod mode breakage
  radeon/radeon_platform_probe: fix Zaphod mode breakage

Marek Olšák (2):
  radeon: log if 2D tiling is enabled
  radeon: turn on 2D tiling by default on r6xx-cayman

Michel Dänzer (8):
  Drop UMS specific parts from the radeon manpage.
  Some cosmetic fixups for the radeon manpage.
  EXA: Factor out pixmap BO allocation into a helper function.
  Initial glamor support.
  Initial SI support.
  Deal more gracefully with DRI2 being unavailable at build or run time.
  glamor: Fix DRI2 crash introduced by PRIME changes.
  glamor: Force acceleration for DRI2 copies.

Tomas Chvatal (1):
  Add switch for udev to disable automagic detection.

git tag: xf86-video-ati-7.0.0

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.0.0.tar.bz2
MD5:  7498971865dc465a4d4ebad826663d40  xf86-video-ati-7.0.0.tar.bz2
SHA1: 4e62a574b66a5071cbbfa1c67442938b42d11b43  xf86-video-ati-7.0.0.tar.bz2
SHA256: c0acc81386425651aae5dfe02d89f935bb63b2a62104da0d88deac3c773ea10e
 xf86-video-ati-7.0.0.tar.bz2

http://xorg.freedesktop.org/archive/individual/driver/xf86-video-ati-7.0.0.tar.gz
MD5:  82696c8092aabbb3816f05b9433db0b8  xf86-video-ati-7.0.0.tar.gz
SHA1: ac141f060e6fc6cd107de1d0e56144b76c626502  xf86-video-ati-7.0.0.tar.gz
SHA256: 678941d72a088898e0465bbe0e2149ec5c2bdae35612696ac8e9bd25d23b35a4
 xf86-video-ati-7.0.0.tar.gz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAlCZIMMACgkQm07k+YR03kCNxQCghElqWlh9lBUbljF9cGfCZro6
1nQAn3ZE09sMJB0HoeWNwkKmWlNMpa0M
=XVrh
-END PGP SIGNATURE-
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Resolution problem with AMD Radeon 5450/6350 and Dell U3011

[Alex Deucher]

On Tue, Oct 30, 2012 at 6:35 AM, Johan Mazel  wrote:
> Hi
> I am trying to use a Dell U3011 (30 inches IPS screen) on a Dell
> Optiplex 990 with an AMD HD 5450/6350.
> I am using Debian Testing and Ubuntu 12.10 with Xorg's ATI driver.
> The respective xserver-xorg-video-radeon package versions for these
> two OSes are: 1:6.14.4-5 and 1.6.99.99~git20120913.8637f772-0ubuntu1.
>
> Theoretically, the HD5450 is able to display the screen's native
> resolution (2560x1600) according to
> http://www.amd.com/us/products/desktop/graphics/ati-radeon-hd-3000/hd-3400/Pages/ati-radeon-hd-3400-specifications.aspx
> provided that a dual-link DVI cable is used, which is the case.
> Unfortunately, the biggest available resolution is 1600x1200 on Debian
> Testing and 1920x1200 for Ubuntu 12.10.
>
> I think there is a discrepancy between what Xorg probes through the
> graphic card as the biggest resolution available (1600x1200, starting
> line 438 in Xorg.0.log_debian_xorg) and what is actually announced by
> the monitor (2560x1600, eg.: line 587 (and further) in
> Xorg.0.log_debian_xorg).
> This discrepancy is also present in Ubuntu's Xorg log files.
>
> I am guessing that Ubuntu uses a slightly newer version of the driver
> and therefore handle slightly better the resolution.
> However, I have no idea regarding the cause of this discrepancy.

While the chip is cable of dual link, dual link is only available if
the oem wired up a dual link DVI connector on your card.  If the oem
used a single link DVI connector, you will be limited to single link
DVI.  I suspect that is what's happening.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Request for proposals to host the 2013 X.Org Developers Conference (XDC)

[Alex Deucher]

Having just finished a successful XDC in Germany, the X.Org Foundation
Board would like to request proposals to organize next year's XDC.  If
you are interested, please email the board (bo...@foundation.x.org)
with your proposal.  Some things to keep in mind:

- We generally switch between the Eastern and Western Hemispheres.
Since the 2012 XDC was in Europe, the 2013 XDC would ideally be in the
Americas.
- Target ~50-60 attendees
- Location should be near hotels/dorms/etc. and public transportation
if possible
- Availability of catering and restaurants for snacks and dinners
- Rough cost estimates
- Suggested dates (conference is usually 3 days)
- Possible cultural events nearby

Please send your initial proposals to the Board by the end of November 2012.

Thanks!

Alex Deucher
X.Org Foundation Board
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: Problems with widescreen (16:9) under CentOS 5 w/ xorg-x11-drv-i810-1.6.5-9.40.el5

[Alex Deucher]

On Sun, Sep 23, 2012 at 1:18 AM, Felix Miata  wrote:
> On 2012-09-22 23:33 (GMT-0400) Robert Heller composed:
>
>
>> These boxes are small form factor machines and only have two PCI slots
>> on a riser card. No AGP slots, so no option of alternitive video cards,
>> unless with use PCI video cards (are such cards even available?).
>
>
> http://www.ebay.com/itm/New-ATI-Radeon-9200-Features-Up-to-128MB-of-DDR-PCI-Graphics-Card-/230805145505?forcev4exp=true&forceRpt=true
> http://www.ebay.com/itm/Diamond-Multimedia-ATI-Radeon-9200SE-128MB-DDR-PCI-graphics-card-DVI-VGA-/280952813779?pt=PCC_Video_TV_Cards&hash=item416a17b8d3
>
> They do, but whether they're new enough to support 16:9 modes other than
> 1920x1080, if that, may take some digging to find out. 1920x1080 as a HDTV
> standard mode is actually quite old, while newer 1280x800, 1366x768,
> 1440x900, 1600x900 & 1680x1050 modes require newer chips to provide required
> video BIOS mode support. New PCI cards still are made, but could well be
> cost ineffective for your situation. It might be significantly cheaper to
> trade out those widescreens for widely available though sometimes tricky to
> locate 1280x1024s, if you can't make those 845Gs do what you need.

The radeon driver does not depend on the the vesa mode list.  It can
natively program just about any mode supported by the monitor.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com

Re: [ANNOUNCE] glamor 0.5.0

[Alex Deucher]

On Fri, Aug 10, 2012 at 12:59 PM, Jeremy Huddleston Sequoia
 wrote:
>
> On Aug 10, 2012, at 09:54, Alex Deucher  wrote:
>
>> On Fri, Aug 10, 2012 at 11:58 AM, Jeremy Huddleston Sequoia
>>  wrote:
>>>
>>> On Aug 10, 2012, at 03:37, Zhigang Gong  
>>> wrote:
>>>
>>>> to try a full functional xserver with glamor, it’s recommended to use the
>>>> following xserver version:
>>>>
>>>> commit a615b90cab7569fae9d123e4da1d3373c871d84b
>>>>
>>>> Author: Keith Packard 
>>>>
>>>> Date:   Wed Mar 14 11:32:36 2012 -0700
>>>>
>>>>
>>>>
>>>>   Bump version number to 1.12.99.0
>>>>
>>>>
>>>>
>>>>   Now that 1.12 has branched, reset the version on master to a
>>>>
>>>>   development number.
>>>>
>>>
>>>
>>> Why is such an old server version recommended?  Surely tip of 
>>> server-1.12-branch is superior to this branch point+1 on master?  And I'd 
>>> really expect tip of master to be a better candidate than that given the 
>>> development nature of glamor.  Can you please clarify?
>>
>> That should be fine.  The commit is question is just the most recent
>> commit on master that still works prior to the changes that broke the
>> module ordering that broke glamor.
>
> I think you're mistaken.  The commit referenced is just xorg-server-1.12.0 + 
> version change.  It is significantly before the module loading changes.

That was just an uneducated guess on my part.  Glamor does work on
older xservers...  I'll shut up now.

Alex
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: http://lists.x.org/mailman/listinfo/xorg
Your subscription address: arch...@mail-archive.com