Re: Multi-monitor configuration - related question

[Christopher Barry]

On Mon, 7 Feb 2022 02:05:28 +
Michael Faynberg  wrote:

>Dear Madam/Sir,
>
>I have an XLib-based application (however old), which is running by
>opening a terminal session from a Windows client computer on an
>OpenVms server. It is running OK unless the client machine has
>multiple monitors. In that case we experience the following problems:
>
>1.   I cannot drag the top window completely from one monitor to
>another: however I try, the part of this window still stays "stuck" to
>the original monitor;
>
>2.   When one is trying to maximize the top window, it extends to
>the full screen meaning the bounding rectangle of all the monitors
>present - but I would like to restrict it so that it would occupy the
>physical screen rather than the logical one. I cannot locate any way
>for doing that though. I can not determine:
>
>a.   The index (for example, or some sort of identification) of
>the current monitor, where "current" means the monitor the top program
>window is located at;
>
>b.  The dimensions of the current monitor;
>   The calls to the XHeightOfScreen() and XWidthOfScreen()
> return the size of the logical screen without the taskbar, which
> makes the situation even more confusing... How can I find out then
> where the taskbar is located and what is its width - for that matter?
> If I could answer these questions at list I would have tried to
> implement some empirical logic assuming that all monitors attached
> are of the same size... which is certainly not guaranteed but can be
> tolerated at the moment if there is no better solution.
>
>Anyway, I will greatly appreciate your help on this issue!
>
>Best regards,
>
>Mike Faynberg
>mfaynb...@hotmail.com
>
>

Something you might want to consider is running a Virtual Machine on
the Windows box (VirtualBox is free and pretty good). You can install
and run Linux in the VM, it will get a single virtual monitor, and you
can maximize this on a single Windows monitor.

From the VM you can connect to your OVMS server and run the app in the
VM. You'll only have the real estate of the single monitor, but it
won't be as confusing or weird.

Good Luck,
-C

Re: X does not start any more since upgrading to Debian 9.1 with NVIDIA GeForce 7100

[Christopher Barry]

On Mon, 2 Oct 2017 19:39:41 +0200
"Andreas Köhler"  wrote:
...snip

>Your card is only supported up to the 304 legacy drivers series.
>It is recommended to install the
>nvidia-legacy-304xx-driver
>package.

snip...

^
did you try that? if yes, and it failed as well, maybe try the
proprietary nvidia driver from their site (if you are ok with non-free,
of course)

--
Regards,
Christopher Barry
___
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-amdgpu 1.4.0

[Christopher Barry]

On Fri, 8 Sep 2017 16:54:22 +0900
Michel Dänzer  wrote:

>I'm pleased to announce the 1.4.0 release of xf86-video-amdgpu, the
>Xorg driver for AMD Radeon GPUs supported by the amdgpu kernel driver.
>This release supports xserver versions 1.13-1.19.
>
>Highlights:


Thanks so much to all of you for your excellent work on these drivers.
It is exactly because of your OpenSource driver work that I will only
buy AMD GPU hardware for my needs (I'm a heavy Blender user on a triple
head system).

I hope that perspective and understanding makes it into the
consciousness of many hardware manufacturers who unfortunately still
tend to cling to their often inferior proprietary solutions.

High quality OpenSource drivers are not a threat to their business
models, but rather are a differentiator that not only opens up the
market for them, but also builds long term customer loyalty.

Thanks again,

--
Regards,
Christopher Barry
___
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-amdgpu 1.2.0

[Christopher Barry]

t;  Fix handling of configure option --with-xorg-conf-dir
>  Untangle HAS_XORG_CONF_DIR / --with-xorg-conf-dir lines in
> configure.ac Add support for ScreenPtr::SyncSharedPixmap
>  Rotate and reflect cursor hotspot position for drmModeSetCursor2
>  Enable HW cursor support with PRIME slave output & Xorg >
> 1.18.99.901 Order unique chipsets according to first appearance in
> ati_pciids.csv Sayōnara, AM_MAINTAINER_MODE!
>  Don't rely on randr_crtc->scanout_pixmap in
> drmmode_set_scanout_pixmap Always call PixmapStopDirtyTracking in
> drmmode_set_scanout_pixmap Consume all available udev events at once
>  present: Check tiling info for flips
>  Require xserver 1.10 or newer
>  Check Xorg version at runtime instead of build time in two places
>  Refactor amdgpu_mode_hotplug
>  Use pAMDGPUEnt to find both screens of a GPU in
> amdgpu_mode_hotplug manpage updates for the 1.2.0 release
>  Bump version for 1.2.0 release
>
>Qiang Yu (3):
>  Remove RR_Capability_SinkOutput for GPU without CRTC.
>  Fix amdgpu_mode_hotplug crash on multi GPU platform.
>  DRI2: Fix amdgpu_dri2_exchange_buffers width/height copy'n'paste
> error
>
>Ronie Salgado (1):
>  Add SI PCI IDs
>
>Tom St Denis (1):
>  dri3: Return NULL from amdgpu_dri3_pixmap_from_fd if calloc
> fails.
>
>git tag: xf86-video-amdgpu-1.2.0
>
>https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-1.2.0.tar.bz2
>MD5:  f4e335b580336e03eeef10b08b68d757  xf86-video-amdgpu-1.2.0.tar.bz2
>SHA1: 434ab94fcda4070c333c208ffdc19c31341c01c1
>xf86-video-amdgpu-1.2.0.tar.bz2 SHA256:
>275b1aac5f127f55ba3d7480a1df89eace1d02650e24e46908067fc875e76c8f
>xf86-video-amdgpu-1.2.0.tar.bz2 PGP:
>https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-1.2.0.tar.bz2.sig
>
>https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-1.2.0.tar.gz
>MD5:  70e0986074c510778f1a644dc63ecca7  xf86-video-amdgpu-1.2.0.tar.gz
>SHA1: b918e7c6b670ce104292146b0774a6a67ad76761
>xf86-video-amdgpu-1.2.0.tar.gz SHA256:
>99c572cda61007e6da7740a2eb5eb46ea882cc9a51db2c14bb07ba92660deb7a
>xf86-video-amdgpu-1.2.0.tar.gz PGP:
>https://xorg.freedesktop.org/archive/individual/driver/xf86-video-amdgpu-1.2.0.tar.gz.sig
>
>

All,

Just a big THANK YOU for everything you do to make this driver
fantastic. I use it with 3 19200 x 1200 monitors on a Micro-Star
International Co., Ltd. [MSI] Hawaii PRO [Radeon R9 290/390], and it
just works rock solidly. I use it heavily with blender. Thanks!

Cheers.

--
Regards,
Christopher Barry


pgprZ_PO1iYDd.pgp
Description: OpenPGP digital signature
___
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: Video projector not detected anymore (under Xorg 1.18.4)

[Christopher Barry]

On Thu, 3 Nov 2016 17:05:22 +0100
Philippe Dosch  wrote:

>Le 03/11/2016 à 16:12, Łukasz Maśko a écrit :
>> Dnia czwartek, 3 listopada 2016 15:41:52 Philippe Dosch pisze:  
>>> Hi Folks,
>>>
>>> I'm assistant professor and I teach with the same video projectors
>>> since years (with each of the last three kubuntu releases on my
>>> laptop). I have a strange trouble since my last kubuntu update (2
>>>
>>> weeks ago). Now I'm under kubuntu 16.10, with a 1.18.4 Xorg
>>> server:  
>>
>> Hello!
>> I have exactly the same problem and it lies in the kernel itself,
>> probably in i915 driver, not in X. The change was introuced in
>> kernel 4.7.0, the last of the 4.6.x line (4.6.7) works fine. The
>> changes deal with detection of external Display Port and as a result
>> I get first an error like this:
>>
>> [drm:intel_dp_start_link_train [i915]] *ERROR* failed to update link
>> training  
>
>Hi Dnia,
>
>I have the same message several times at boot time (also found in
>dmesg). But in my case, my troubles are related to the VGA port, not
>the display port.
>
>> at the kernel start (visible in dmesg). And then this output is not
>> recognized anymore. I have filed a bug report
>> https://bugs.freedesktop.org/show_bug.cgi?id=97397  
>
>I saw your post, but it is related to the display port and I don't
>know if the DP trouble makes some side effects with the VGA port.
>
>> Maybe you can confirm it or append yours so we make developers fix
>> this? I have no idea how to fix this myself. I'm just keeping kernel
>> 4.6.7 to use when I want to do my presentations.  
>
>It's an idea, maybe I could downgrade to a 4.6.x kernel to see what
>happens.
>

It's probable that you already have the last kernel already installed
and selectable via GRUB. Do you see the GRUB menu on boot? If not, I
believe if you hold the shift key down just as soon as it's out of the
BIOS it will show the GRUB boot menu and you can select the previous
kernel.



-C


--
Regards,
Christopher Barry
___
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: Installed Nvidia GT630 and S server fails to boot up.

[Christopher Barry]

On Mon, 24 Oct 2016 14:16:35 +0900
aki  wrote:

>I have a mother board with an intel graphics card, and add a GeForce
>GT 630 to the expansion slot. Windows recognized it and installed
>proper drivers but Mint gives me an error and stalls.
>Error mess. said " FAILED TO START THE X SERVER (YOUR GRAPHICAL 
>INTERFACE). IT IS LIKELY THAT IT IS NOT SET CORRECTLY." it asks too to 
>view the server output choosing NO, next appear "THE X SERVER IS NOW 
>DISABLED. RESTART MDM WHEN IT IS CONFIGURED CORRECTLY" after that a 
>black screen. Press Ctrl + Alt + Del Mint logo seems on screen and 
>restart, i think, because i heard the "Beep" alarm when yo put the
>power on, but after that only black screen, nor windows nor mint boots
>up. Try to boot mint from live DVD, and after the same errors, it 
>stops(Loops) at the User and passwor request onthe command promt.
>By the way, the GeForce is not recognized by my BIOS/UEFI and by GRUB, 
>For access Bios/UEFI settings i must to remove the GeForce and go back 
>to the intel card.
>
>I tried NOMODESET, and do not work. "nomodeset" i read somewhere
>bypass graphics card's driver and use bios settings, that is the
>problem my bios not recognized the graphic card (May be there are some
>hidden bios settings i did not found yet), reading some cases in
>Asus/nvidia forums, there are a lot of cases of Asus firmware
>incompatibility with other graphics card than the onboard one, but
>this cases are all worst than mine at least i have error messages.
>With nomodeset i have black screen from start to end, but i think boot
>process are going because, there are some i/o to the hard disk, but
>not sure of what was going on. I am watching if force install device
>drivers without the card physicaly installed is possible, or a way to
>bypass the open source drivers and directly install the propietary
>drivers on first bootup. My graphic card(All my hardware) is, i think,
>old enough to be supported by the standard open source drivers (Bought
>it more than 3 years ago), and neither the live/installation DVD are
>working. Where is the problem? I have no idea. May be the Bios/Uefi
>firmware, i have a very bad experience with it, I was trying to setup
>Linux/Win doble boot, once Grub is installed all boot procs
>disappeared. Linux standalone, do not work, reinstalled win stand
>alone and worked. Then flashed the firmware and all goes like the
>tutorials: install, select OS, press enter and go. But on the other
>side, Windows graphics drivers are doing fine, they installed
>automatically, and for now nothing of troubling. This is the boot
>log(Xorg.0.log):
>
>http://pastebin.com/pMzJgs2S
>

Is there an option in the BIOS to disable or deprioritize the builtin
gpu?

Write down the keys required to reverse that action, (you may be
able to reset defaults with a single F-key or key combo) then
deprioritize or disable the builtin gpu and power-cycle it - not just
reboot. If it still has no video, you'll need to enter the BIOS blind
and reset it with the keys you wrote down. 

I have had to do a similar thing before myself to get an add in
PCIE card to work correctly. It's a bit hairy, but doable. :)

Good luck!

-C



--
Regards,
Christopher Barry
___
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: proper release of edid-decode with versioning, proper changelog etc.

[Christopher Barry]

On Fri, 30 Sep 2016 23:14:03 +0200
Tormod Volden  wrote:

>On Fri, Sep 30, 2016 at 3:37 PM, shirish शिरीष wrote:
>> Hi all,
>>
>> Please CC me if somebody answers, thank you.
>>
>> I filed a bug to update edid-decode in debian. See
>> https://bugs.debian.org/839152
>>
>> The answer I was given by the maintainer is as follows -
>>
>> I'm not sure putting git-generated ChangeLog is in any way
>> beneficial to the users. I think it's better to talk to upstream to
>> convince them to
>> do proper releases and release notes/changelogs.   
>
>edid-decode is a developer tool that works standalone without
>dependencies (or reverse ones) and wouldn't benefit much from proper
>releases. As you can see in the changelog, changes are very
>incremental and there are likely no reason to keep "users" at a
>certain version instead of just using the latest code. Releases could
>nudge downstream packagers to update their packages though...
>
>The Debian maintainer should just make a snapshot release from time to
>time, and whenever the code hasn't been worked on for a while, is
>probably a good time to pick.

Or, that'd be the right time for devs to create a git tag named the
incremented version at that working state.

checkout in-between tags, and you're on your own.

>
>The git log is in the case of edid-decode a pretty good changelog. I
>don't think anybody cares enough to spend time on making a shorter
>version.
>
>I don't know why the Debian maintainer refuses to add a git log, which
>would be better than nothing. Maybe he is overloaded (60+ packages)
>and focuses on more critical packages. Luckily, it is easy to
>contribute to Debian. If you attach a debdiff or patch to your bug
>report, he would be pretty stubborn to not accept it.
>
>Of course, I am sure anyone is welcome to prepare an x.org edid-decode
>release too :)
>
>>
>> From the nature of the git page, it's not easy to have any idea as to
>> when there is possibility of having a versioning and a proper release
>> as such.  
>
>I think edid-decode never had a version or release and there is no
>plan for it, although I can't speak for the developers.
>
>Regards,
>Tormod


--
Regards,
Christopher Barry
___
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 cut and paste

[Christopher Barry]

On Fri, 16 Sep 2016 15:24:53 +0200
Thomas Lübking  wrote:

>On Fri, Sep 16, 2016 at 02:32:39AM -0400, Christopher Barry wrote:
>
>>Thanks Thomas for the xev tip! It appears to be my mouse button
>>is just getting flaky. It's the wheel and it clicks in too, and it's
>>tired. Time for a new G602 (or whatever replaced it).  
>
>If your rodant has many buttons and you only use three, you can use
>xinput or xmodmap to map them around. In theory, I've 2 on the wheel as
>well, but that's nasty, because you often click the wheel along the
>button. So I mapped it to the thumb button (and also because very long
>ago, one of my mice had the "middle" button there ;-)
>
>Cheers,
>Thomas

Hey, Thanks again Thomas.

I Just realized I had sent directly to you and not the list, so
reposting for anyone else who this may help.

--
Regards,
Christopher Barry
___
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 cut and paste

[Christopher Barry]

Hi,

For some reason my X cut/paste stopped working. No idea why. I've
restarted, still the problem persists.

Where to look to fix? it's /really/ painful not having it.


Thanks

--
Regards,
Christopher Barry
___
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: display/GFX issue with Ubuntu 16.04 not seen in 14.04

[Christopher Barry]

On Tue, 23 Aug 2016 06:53:13 -0400
Jim Abernathy  wrote:

>On 08/19/2016 10:17 AM, Jim Abernathy wrote:
>> Not having much luck with the Distro forums on this issue so I
>> thought I'd ask for advice here.
>>
>> I've been running Ubuntu 14.04.5 for some time on Intel Core i5 GFX 
>> without any issues.  My display is HDMI from the PC to an Onkyo A/V 
>> receiver then to a Sony KDL-XBR6.
>>
>> When I try a fresh install of 16.04.1, I get a display that blanks
>> out for 3-5 seconds at random times depending on what is being
>> displayed at the time.  I also have small abouts of video noise that
>> is random horizontal lines about 1 pixel tall scattered through the
>> page.
>>
>> I noticed that 14.04.05 uses X server 1.17.2 and 16.04.1 uses 1.18.3.
>>
>> When I do the command xrandr --verbose I see some small differences 
>> between 14.04 and 16.04, but it's things like 2 digits displayed 
>> instead of 1.  i.e. 60.0 vs. 60.00. I'm only concerned with 1080P HD.
>>
>> I've tried this on different computers all with Intel GFX. same
>> results.
>>
>> This does not occur on other monitors or TVs.
>>
>> I'd blame it on Sony and Onkyo if they didn't work so well with 
>> Windows, all versions, and ubuntu all versions except 16.04.
>>
>> It's almost like the auto detection software in the newest version
>> of X is off just enough to make my display flaky.  Kind of like the
>> old analog CRT TVs that were sensitive to small tweaks to the
>> horizontal and vertical adjustments.
>>
>> Any help would be appreciated.
>>
>> Jim A
>>  
>
>Can someone let me know where I can ask questions regarding problems 
>with X??  I thought this forum would be the place?
>
>Jim A
>

Jim,

From the data above, I do not think it's possible to troubleshoot very
effectively. It also seems like (to me anyway) that you have a fairly
non-standard kind of configuration going on.

If I understand it, you have a media-center type PC with an integrated
Intel graphics card on an core i5 processor. Using an HDMI cable, you're
plugging into an Onkyo A/V receiver (you do not mention the model),
which in turn connects to a Sony KDL-XBR6 LCD TV.

What happens when you connect your PC to a the Sony directly or to
a normal PC LCD monitor? Does that work? 

Are you using an xorg configuration file, or are you allowing automatic
setup via kernel mode switching? If you a have config file(s), what
happens when you move them out of the way temporarily and allow
automatic config?

What's in your /var/log/Xorg.0.log?


People here help quite readily if they have data to act upon.

--
Regards,
Christopher Barry
___
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: High CPU usage - slow/lag/skip problem

[Christopher Barry]

On Wed, 10 Aug 2016 19:16:57 -0400
Zurd  wrote:

>Hi, me again, I'm bumping this. I realized I have a big post but I
>wanted to put as much information as possible. All I want to know is
>how to minimize the xrandr calls so that there's less EDID information
>in Xorg.0.log.
>
>My system is not slow yet but it should happen soon. My Xorg log is at
>23M in just 6h12m. I don't think this is normal.
>
>
>On Sun, Aug 7, 2016 at 10:54 PM, Zurd  wrote:
>
>> Hi all! I have a problem where Xorg is taking around 30% CPU usage
>> and it create a slow/lag problem for a fraction of a second about
>> every second. There's no crash but it's quite annoying. Sometimes a
>> click is not registered.
>>
>> It can happen 5 minutes after I boot or after 5 hours. I haven't
>> been able to know why, it's random. It looks like the same problem
>> as this:
>> https://lists.freedesktop.org/archives/xorg/2011-September/053299.html
>>
>> He sums it up quite well by saying:
>> "I can notice the lag in response time. Video playback also becomes
>> impossibly slow at this point."
>>
>> I started a thread on the linux mint forums with a lot of my hardware
>> information:
>> https://forums.linuxmint.com/viewtopic.php?f=47&t=226421
>>
>> Problem started with a new clean install of Linux Mint 18 and I
>> haven't been able to solve it. So I went back with Linux Mint 17.2
>> that I had before and that there was no issue but now the problem is
>> also there. I now have a good theory on why I have a high cpu usage
>> of Xorg and it's because of my ultra widescreen monitor. When I
>> installed Linux Mint 17.2, I had a regular widescreen monitor and
>> Xorg was configured with it. Then I switched to my new ultra
>> widescreen and everything was well. Until I decided to completely
>> format and install the new Linux Mint 18.
>>
>> My monitor is an LG 29UM58-P, resolution is 2560x1080.
>>
>> So now I'm wondering if the problem is about EDID:
>> https://wiki.ubuntu.com/X/Troubleshooting/HighCPU
>> "An example we saw is where a daemon process does polling on X
>> calls, such as to watch for if a monitor is present. These xrandr
>> calls can be expensive because they do a probe and analysis of the
>> monitor's firmware. So as a result the daemon drives X's CPU
>> utilization through the roof (and causes a bunch of EDID stuff to
>> fill up the Xorg.0.log). The solution in these cases is to make the
>> daemon stop doing the expensive polling so frequently (there are
>> cheaper X calls they can use)."
>>
>> This whole paragraph on EDID/polling/xrandr is quite interesting but
>> there's no information on how to troubleshoot or solve that problem
>> which is why I'm posting here. Anyone can shed some lights?

Based on the above, could it be possible that a utility daemon, e.g.
something that's part of the distro itself (not part of X, per se), is
the culprit here?

Try using ps to see if you can glean some more info.

(or use 'pstree -paul' for a nice view of processes if you have it
installed [pkg: 'psmisc' in Debian derivatives])

both of the above are terminal programs by the way...

>>
>> I have a feeling it's about EDID because in my log file
>> /var/log/Xorg.0.log, I see a bunch of
>> [   434.373] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> connected
>> [   434.373] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> Internal TMDS
>> [   434.373] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> 340.0 MHz maximum pixel clock
>> [   434.373] (--) NVIDIA(GPU-0):
>> [   434.907] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> connected
>> [   434.907] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> Internal TMDS
>> [   434.907] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> 340.0 MHz maximum pixel clock
>> [   434.907] (--) NVIDIA(GPU-0):
>> [   434.940] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> connected
>> [   434.940] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> Internal TMDS
>> [   434.940] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> 340.0 MHz maximum pixel clock
>> [   434.940] (--) NVIDIA(GPU-0):
>> [   435.474] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> connected
>> [   435.474] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>> Internal TMDS
>> [   435.474] (--) NVIDIA(GPU-0): LG Electronics LG ULTRAWIDE (DFP-1):
>&

Re: wrong display size

[Christopher Barry]

On Tue, 14 Jun 2016 11:10:57 +0200
Sebastian Gutzwiller  wrote:

>Hi all
>
>I have a LCD display (115 mm x 86 mm) with VGA resolution (640 x 480) 
>connected over LVDS with an Intel Atom N450.
>
>After upgrading from Ubuntu 10.04 to 14.04  I only see the upper left 
>detail of the whole screen (see attachment 'display_picture.jpg').
>
>The Xorg log (see attachment 'Xubuntu.14.04.4.LTS.Xorg.0.log')
>reported a physical screen size of 270 mm x 203 mm which is pretty
>much the size of the whole screen.
>
>Any suggestions?
>
>Cheers Sebastian
>
>

I like the arandr applet for setting display stuff. it will generate a
script to re-use which is handy. I use the script from lightdm, and
also in my window manager (enligtenment) to setup my three monitors
when I start up.

Give it a shot.


--
Regards,
Christopher Barry
___
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: Remote OpenGL

[Christopher Barry]

On Fri, 27 May 2016 09:54:28 -0700
Alan Coopersmith  wrote:

>On 05/26/16 06:56 PM, Christopher Barry wrote:
>> I have certain software that must use opengl, and it runs on
>> windows. I had to stand up a separate box just for that application,
>> as I run Linux everywhere else. I could not make it work in a KVM VM
>> due to no opengl capability in KVM (I won't use vmware).  
>
>Have you considered VirtualBox with it's OpenGL passthrough?  I don't
>know if it will work for this situation, but it might.
>
>https://www.virtualbox.org/
>https://www.virtualbox.org/manual/ch04.html#guestadd-video
>
>(Disclaimer: while I don't work on VirtualBox, I work for the company
>  who makes it and sells optional support & addons for it, though the
>  core software is free.)
>

Thanks Alan,

Apparently it does not require a dedicated GPU for this, and instead
asks the host OS to do the work on it's GPU. Seems cool and I will
experiment with it. On a scale of 1-10, what's your guess of it's
stability?

Thanks a lot!

--
Regards,
Christopher Barry
___
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: Remote OpenGL

[Christopher Barry]

On Thu, 26 May 2016 21:56:21 -0400
Christopher Barry  wrote:

>On Thu, 26 May 2016 23:43:05 +
>"Cook, Rich"  wrote:
>
>>The point here is that today it is being *disabled* and in the future
>>it is completely *going away.*  Anyone care to argue with that?  I'd
>>love to be wrong about it.  
>>  
>>> On May 26, 2016, at 3:56 PM, Adam Jackson  wrote:
>>> 
>>> On Thu, 2016-05-26 at 09:14 +0200, Laurent Lamalle wrote:
>>>> Hello,
>>>> 
>>>> I have just discovered, through the x11-us...@lists.apple.com
>>>> mailing list, that Xorg deprecated some software component (IGLX?)
>>>> necessary for remote OpenGL viewing.
>>> 
>>> As I just said:
>>> 
>>> https://lists.freedesktop.org/archives/xorg/2016-May/058072.html
>>> 
>>> Another awkward thing about this, I suppose, is that on OSX the X
>>> server is started implicitly on demand and there's no reasonable way
>>> to configure things like command line options. And, that there's no
>>> direct rendering support to be had on OSX. So we could probably
>>> reasonably change those defaults for that platform, since the
>>> opportunity for privilege escalation is lower as X11.app runs
>>> unprivileged.
>>> 
>>> - 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
>>  
>
>This thread got me thinking.
>
>If it does go away, possibly this could be useful for what you're
>doing? https://github.com/VirtualGL/virtualgl
>
>I'm also interested in how you're using iglx. Can you point me to how
>it's used? 
>
>I have certain software that must use opengl, and it runs on windows. I
>had to stand up a separate box just for that application, as I run
>Linux everywhere else. I could not make it work in a KVM VM due to no
>opengl capability in KVM (I won't use vmware).
>
>Do you think with either iglx, or maybe the software linked above this
>would work for my needs, and then I can get rid of this extra physical
>box generating heat and sucking electricity for a single application?
>
>
>Thanks!
>
>--
>Regards,
>Christopher Barry

pardon the self reply, but I don't think either will help me
unfortunately.


--
Regards,
Christopher Barry
___
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: Remote OpenGL

[Christopher Barry]

On Thu, 26 May 2016 23:43:05 +
"Cook, Rich"  wrote:

>The point here is that today it is being *disabled* and in the future
>it is completely *going away.*  Anyone care to argue with that?  I'd
>love to be wrong about it.  
>
>> On May 26, 2016, at 3:56 PM, Adam Jackson  wrote:
>> 
>> On Thu, 2016-05-26 at 09:14 +0200, Laurent Lamalle wrote:  
>>> Hello,
>>> 
>>> I have just discovered, through the x11-us...@lists.apple.com
>>> mailing list, that Xorg deprecated some software component (IGLX?)
>>> necessary for remote OpenGL viewing.  
>> 
>> As I just said:
>> 
>> https://lists.freedesktop.org/archives/xorg/2016-May/058072.html
>> 
>> Another awkward thing about this, I suppose, is that on OSX the X
>> server is started implicitly on demand and there's no reasonable way
>> to configure things like command line options. And, that there's no
>> direct rendering support to be had on OSX. So we could probably
>> reasonably change those defaults for that platform, since the
>> opportunity for privilege escalation is lower as X11.app runs
>> unprivileged.
>> 
>> - 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  
>

This thread got me thinking.

If it does go away, possibly this could be useful for what you're doing?
https://github.com/VirtualGL/virtualgl

I'm also interested in how you're using iglx. Can you point me to how
it's used? 

I have certain software that must use opengl, and it runs on windows. I
had to stand up a separate box just for that application, as I run
Linux everywhere else. I could not make it work in a KVM VM due to no
opengl capability in KVM (I won't use vmware).

Do you think with either iglx, or maybe the software linked above this
would work for my needs, and then I can get rid of this extra physical
box generating heat and sucking electricity for a single application?


Thanks!

--
Regards,
Christopher Barry
___
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 primary in multihead xorg.conf causes disregard of DisplaySize

[Christopher Barry]

On Wed, 10 Feb 2016 02:05:03 -0500
Felix Miata  wrote:

>Sent too soon, and probably to the wrong place. I tried equivlent
>xorg.conf files with Nvidia G84 and nouveau, and with ATI Cedar and
>radeon. Neither have any such shortcoming, so I have to suspect this
>should have gone to intel-gfx as a driver bug. Anyone here agree, or
>know a config solution?
>
>Felix Miata composed on 2016-02-09 23:33 (UTC-0500):
>
>> Using the following, I get the display positions the way I want
>> them, but the DPI I want is disregarded. If I comment the primary
>> option line, DPI is obeyed, but the wrong display is primary. Am I
>> doing something wrong, missing something, is a ServerLayout section
>> required, or is there a bug here?  
>
>> # 50-device.conf
>> Section "Device"
>>  Identifier  "IGMA"
>>  Driver  "intel"
>>  Option  "monitor-VGA1"  "analog"# Intel
>> analog Option"monitor-HDMI1" "digital"   # Intel
>> HDMI aka DVI #
>> Option   "monitor-DP1"   "apple" # Intel
>> DisplayPort EndSection  
>
>> # 50-monitor1.conf
>> Section "Monitor"
>>  Identifier  "analog"
>>  Option  "Primary"   "true"
>>  Option  "PreferredMode" "1680x1050"
>>  DisplaySize 761 228 # 120 DPI @ 3600x1080
>> EndSection  
>
>> # 50-monitor2.conf
>> Section "Monitor"
>>  Identifier  "digital"
>>  Option  "PreferredMode" "1920x1080"
>>  Option  "RightOf"   "analog"
>> EndSection  
>
>> # 50-screen1.conf
>> Section "Screen"
>>  Identifier  "ScreenLeft"
>>  Device  "IGMA"
>>  Monitor "analog"
>> EndSection  
>
>> # 50-screen2.conf
>> Section "Screen"
>>  Identifier  "ScreenRight"
>>  Device  "IGMA"
>>  Monitor "digital"
>> EndSection  
>
>> TIA  

if kms is an option, I'm using xrandr to accomplish essentially this
for a triple-head setup in this script I use from lightdm.conf as:

display-setup-script=/usr/bin/xrandr-screen-layout
greeter-setup-script=/usr/bin/xrandr-screen-layout

where the script looks like (single line):
xrandr --output DisplayPort-0 --mode 1920x1200 --pos 1920x0 --rotate
normal --output DVI-1 --mode 1920x1200 --pos 0x0 --rotate normal
--output DVI-0 --mode 1920x1200 --pos 3840x0 --rotate normal --output
HDMI-0 --off

Not sure if that's helpful for you or not.

--
Regards,
Christopher Barry
___
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: Diagnosing first vs subsequent performance

[Christopher Barry]

On Tue, 19 Jan 2016 09:03:49 -0700
Lloyd Brown  wrote:

>Hi, all. 
>
>I hope this isn't too dumb of a question, but I'm having trouble
>finding anything on it so far.  Not sure if my google-fu is just not
>up to the task today, or if it's genuinely an obscure problem.
>
>I'm in the middle of setting up an HPC node with 2 NVIDIA Tesla K80s (4
>total GPUs), for some remote rendering tasks via VirtualGL.  But I've
>got some strange behavior I can't yet account for, and I'm hoping
>someone can point me in the right direction for diagnosing it.
>
>In short, for accounting reasons, we'd prefer to have each GPU be
>attached to a separate Xorg PID.  So I've built some very simple
>xorg.conf files (example attached), and I can launch Xorg instances
>with a simple syntax like this:
>
>> Xorg :0 -config /etc/X11/xorg.conf.gpu0
>
>When I run my tests, I'm also watching the output of "nvidia-smi" so I
>can see which Xorg and application PIDs, are using which GPUs.
>
>The first time I do something like "DISPLAY=:0.0 glxgears", I do *not*
>see that process (eg. glxgears) show up in the output of "nvidia-smi",
>and I see performance numbers consistent with CPU-based rendering.  If
>I cancel (Ctrl-C), and run the exact same command again, I *do* see the
>process in the output of "nvidia-smi", on the correct GPU, and I see
>faster performance numbers consistent with GPU rendering.
>
>If I switch to a different display (eg "DISPLAY=:3.0"), I see the same
>behavior: slow the first time, fast on 2nd and subsequent instances. 
>The same behavior even repeats when I switch back to a previously-used,
>but not most-recently-used, DISPLAY.
>
>I see similar behavior with other benchmarks (eg. glxspheres64,
>glmark2): slow first time on a display, faster after that.
>
>I have a sneaking suspicion that I'm just doing something really stupid
>with my configs, but right now I can't find it.  I don't see anything
>relevant in the Xorg.log files, or stdout/stderr from the servers, but
>I can post those too, if needed.
>
>Any pointers where to go from here, would be appreciated.
>
>Thanks,
>Lloyd
>
>
>Other (possibly relevant) Info:
>OS Release: RHEL 6.6
>Kernel: 2.6.32-504.16.2.el6.x86_64
>Xorg server 1.10.4 (from RHEL RPM)
>NVIDIA Driver 352.55
>
>Note: The attached example is for only one GPU.  The others configs are
>exactly the same, with the exception of the PCI BusID, inside the GPU
>device section.  I can verify via nvidia-smi, that the separate Xorg
>PIDs are attached to the correct GPUs.
>
>

This may or may not be useful, so sorry if I'm speaking out of turn,
but is it not possible to supply only the snippet of config that is
unique (e.g. the Device section), and allow X to do the rest? If it is,
this might be a way to remove other config data that could be part of
the issue. Again, just guessing, and might be a quick and easy test.

--
Regards,
Christopher Barry





___
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: can't start XWindows: fresh install Kubuntu 14.04 (15.10 same problem)

[Christopher Barry]

On Sat, 7 Nov 2015 19:48:30 +0100
Gregor Leskovšek  wrote:

>Hi! I am Gregor Leskovšek from Slovenia and need help has problem with
>xserver in Kubuntu on my new Intel S5000PSL second hand bought server.
>I can not start plasma or failsafe or get in desktop environment.
>When I login (right password) the xserver starts loading but then after
>10-15 seconds I get back login screen
>I have Radeon EAH4350 SILENT/DI/512MD2(LP) (or smth like it used from
>another (brothers) computer) and Intel S5000 PSL Xeon motherboard.
>
>I am unable to start XWINDOWS. In text mode I reinstalled plasma and
>kubuntu desktop (I do not know if there is a trick, because that
>should be a bunch of packets but it processed only few lets say 3-5, I
>did it so: sudo apt-get purge plasma-desktop kubuntu-desktop; sudo
>apt-get install plasma-desktop kubuntu-desktop)
>
>I have attached the log file.
>I think the problem is here(see the excerpt from log below ...) (but I
>am a newbie), before I managed to install Kubuntu 14.04 x64 to server,
>but I got only one VGA port without the Radeon and I had to use
>800x600 resulotion, so I could not use it, maybe also other things are
>in game - I also updated BIOS before that.
>
>[  6301.752] reporting 3 5 23 173
>[  6301.752] (II) RADEON(0): Allocate new frame buffer 2704x1050
>stride 2752 [  6301.752] (II) RADEON(0): VRAM usage limit set to
>4194303K [  6301.831] reporting 3 5 23 13
>[  6301.832] reporting 3 5 23 173
>[  6301.865] reporting 3 5 23 173
>[  6301.866] reporting 3 5 23 173
>[  6301.866] have a master to look out for
>[  6301.866] adjust shatters 0 2704
>[  6301.866] (EE)
>[  6301.866] (EE) Backtrace:
>[  6301.866] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7fbe14d20848]
>[  6301.866] (EE) 1: /usr/bin/X (0x7fbe14b77000+0x1ad539)
>[0x7fbe14d24539] [  6301.866] (EE)
>2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbe13c73000+0x10340)
>[0x7fbe13c83340] [  6301.866] (EE)
>3: /usr/lib/xorg/modules/drivers/radeon_drv.so
>(0x7fbe0e5d7000+0x1e15e) [0x7fbe0e5f515e] [  6301.866] (EE)
>4: /usr/bin/X (PixmapShareToSlave+0x24) [0x7fbe14be87c4] [  6301.866]
>(EE) 5: /usr/bin/X (RRCrtcSet+0xb05) [0x7fbe14c89755] [  6301.866]
>(EE) 6: /usr/bin/X (ProcRRSetCrtcConfig+0x358) [0x7fbe14c8a478]
>[  6301.866] (EE) 7: /usr/bin/X (0x7fbe14b77000+0x55f0e)
>[0x7fbe14bccf0e] [  6301.867] (EE) 8: /usr/bin/X
>(0x7fbe14b77000+0x59d9a) [0x7fbe14bd0d9a] [  6301.867] (EE)
>9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
>[0x7fbe126b3ec5] [  6301.867] (EE) 10: /usr/bin/X
>(0x7fbe14b77000+0x451ee) [0x7fbe14bbc1ee] [  6301.867] (EE)
>[  6301.867] (EE) Segmentation fault at address 0x07 [  6301.867] (EE)
>Fatal server error:
>[  6301.867] (EE) Caught signal 11 (Segmentation fault). Server
>aborting [  6301.867] (EE)
>[  6301.867] (EE)
>Please consult the The X.Org Foundation support
> at http://wiki.x.org
> for help.
>[  6301.867] (EE) Please also check the log file at
>"/var/log/Xorg.1.log" for additional information.
>[  6301.867] (EE)
>[  6302.027] (EE) Server terminated with error (1). Closing log file.
>
>Please help me, I am desperate to put my and my clients websites back
>on net. Thanks, Gregor Leskovšek from Slovenia
>
>> When the sun rises I receive and when it sets I forgive! :-)  
>http://gleskove.oreillystudent.com :-) Always warmly / S prisrčnimi
>pozdravi!
>http://lilaum.com  Gregor Leskovšek ;-)

Do you have an /etc/X11/xorg.conf file? If so, move it somewhere so it
does not get run. Also, if there is a /etc/X11/xorg.conf.d/ directory,
and there are files in it, mv that directory somewhere too.

e.g.
$ cd /etc/X11
$ sudo mv xorg.conf xorg.saved
$ sudo mv xorg.conf.d xorg.conf.d-saved

The idea is to allow X to try to completely configure itself.

either restart X or reboot and see what that does.

-C
___
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: fresh install Kubuntu 14.04 (15.10 same problem) XServer never starts

[Christopher Barry]

On Sat, 7 Nov 2015 20:59:52 +0100
Gregor Leskovšek  wrote:

>Dear Christopher,
>it seems that packages that Kubuntu installed for Radeon are in
>conflict with innate GPU in the motherboard.
>Do You think there is a way that I use this Radeon with this server?
>Any other ideas greatly appreciated. Thanks, Gregor
>
>

Seems like you have an unworkable pkg combination somehow. Not being
there, it's difficult for me to say what would be the best way forward
for you, given the data I have. However, generally speaking, try to
simplify as much as possible. If getting your webserver back up and
running on this server is paramount, you should be able to do that from
the Linux console. Once that's up, and people are off your back, you can
focus on getting the GUI up and running with a lot less stress. Most
sysadmin do not even install X on webservers - it's not needed at all
and is just overhead.


For us to help better, what exactly are you trying to do? You have done
at least two complete reinstalls of two versions of the operating system
on this server.

Was all of this running before at some point on this server? If so, what
Linux distro/version was running on this server?

-C
___
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: fresh install Kubuntu 14.04 (15.10 same problem) XServer never starts

[Christopher Barry]

Hi Gregor, please see inline below:

On Sat, 7 Nov 2015 18:59:51 +0100
Gregor Leskovšek  wrote:

>>
>> When I login (right password) the xserver starts loading but then
>> after 10-15 seconds I get back login screen
>> I have Radeon EAH4350 SILENT/DI/512MD2(LP) (or smth like it used from
>> another (brothers) computer) and Intel S5000 SPL Xeon motherboard.
>>
>> I am unable to start XWINDOWS. In text mode I reinstalled plasma and
>> kubuntu desktop (I do not know if there is a trick, because that
>> should be a bunch of packets but it processed only few lets say 3-5,
>> I did it so: sudo apt-get purge plasma-desktop kubuntu-desktop; sudo
>> apt-get install plasma-desktop kubuntu-desktop)

Try this:
sudo apt-get update

Then:
sudo apt-get -s --reinstall install xorg* xserver* plasma-desktop \
kubuntu-desktop

to do a dry run of what will happen, and if it looks good, remove the
-s from the command and re-run it.

It's a massive hammer, but it will reinstall everything related to X
and plasma/kubuntu.

If there's errors after it installs some stuff, run:

sudo apt-get -f install

and it should figure it out. You may need to do that a couple of times.


Good luck.


>>
>> I have attached the log file.
>> I think the problem is here(see the excerpt from log below ...) (but
>> I am a newbie), before I managed to install Kubuntu 14.04 x64 to
>> server, but I got only one VGA port without the Radeon and I had to
>> use 800x600 resulotion, so I could not use it, maybe also other
>> things are in game - I also updated BIOS.
>>
>> [  6301.752] reporting 3 5 23 173
>> [  6301.752] (II) RADEON(0): Allocate new frame buffer 2704x1050
>> stride 2752
>> [  6301.752] (II) RADEON(0): VRAM usage limit set to 4194303K
>> [  6301.831] reporting 3 5 23 13
>> [  6301.832] reporting 3 5 23 173
>> [  6301.865] reporting 3 5 23 173
>> [  6301.866] reporting 3 5 23 173
>> [  6301.866] have a master to look out for
>> [  6301.866] adjust shatters 0 2704
>> [  6301.866] (EE)
>> [  6301.866] (EE) Backtrace:
>> [  6301.866] (EE) 0: /usr/bin/X (xorg_backtrace+0x48)
>> [0x7fbe14d20848] [  6301.866] (EE) 1: /usr/bin/X
>> (0x7fbe14b77000+0x1ad539) [0x7fbe14d24539] [  6301.866] (EE)
>> 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbe13c73000+0x10340)
>> [0x7fbe13c83340] [  6301.866] (EE)
>> 3: /usr/lib/xorg/modules/drivers/radeon_drv.so
>> (0x7fbe0e5d7000+0x1e15e) [0x7fbe0e5f515e] [  6301.866] (EE)
>> 4: /usr/bin/X (PixmapShareToSlave+0x24) [0x7fbe14be87c4]
>> [  6301.866] (EE) 5: /usr/bin/X (RRCrtcSet+0xb05) [0x7fbe14c89755]
>> [  6301.866] (EE) 6: /usr/bin/X (ProcRRSetCrtcConfig+0x358)
>> [0x7fbe14c8a478] [  6301.866] (EE) 7: /usr/bin/X
>> (0x7fbe14b77000+0x55f0e) [0x7fbe14bccf0e] [  6301.867] (EE)
>> 8: /usr/bin/X (0x7fbe14b77000+0x59d9a) [0x7fbe14bd0d9a] [  6301.867]
>> (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
>> [0x7fbe126b3ec5] [  6301.867] (EE) 10: /usr/bin/X
>> (0x7fbe14b77000+0x451ee) [0x7fbe14bbc1ee] [  6301.867] (EE)
>> [  6301.867] (EE) Segmentation fault at address 0x07
>> [  6301.867] (EE)
>> Fatal server error:
>> [  6301.867] (EE) Caught signal 11 (Segmentation fault). Server
>> aborting [  6301.867] (EE)
>> [  6301.867] (EE)
>> Please consult the The X.Org Foundation support
>> at http://wiki.x.org
>>  for help.
>> [  6301.867] (EE) Please also check the log file at
>> "/var/log/Xorg.1.log" for additional information.
>> [  6301.867] (EE)
>> [  6302.027] (EE) Server terminated with error (1). Closing log file.
>>
>> Please help me, I am desperate to put my and my clients websites
>> back on net. Thanks, Gregor Leskovšek from Slovenia
>>  
>> > When the sun rises I receive and when it sets I forgive! :-)  
>> http://gleskove.oreillystudent.com :-) Always warmly / S prisrčnimi
>> pozdravi!
>>  
>http://lilaum.com  Gregor Leskovšek ;-)
>>  



--
Regards,
Christopher Barry

Earborg
 t: +1 (267) 242 9306
 e: christopher.ba...@earborg.com
 a: 1709F Green Street
Philadelphia, PA 19130



___
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

ABI mismatch

[Christopher Barry]

Hi all,

I've gotten everything to compile now, but getting this error on start.

What does this mean (log attached)


Thanks,
-C[14.205] 
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[14.205] 
X.Org X Server 1.17.99.901 (1.18.0 RC 1)
Release Date: 2015-09-01
[14.205] X Protocol Version 11, Revision 0
[14.205] Build Operating System: Linux 4.0.0-2-amd64 x86_64 
[14.205] Current Operating System: Linux monolith 4.0.0-2-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22) x86_64
[14.205] Kernel command line: BOOT_IMAGE=/vmlinuz-4.0.0-2-amd64 root=/dev/mapper/system_vg-os_lv ro radeon.dpm=0
[14.205] Build Date: 17 October 2015  06:57:39PM
[14.205]  
[14.205] Current version of pixman: 0.33.3
[14.205] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[14.205] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[14.205] (==) Log file: "/opt/xorg-X11R7.6-170-gb8aac01/var/log/Xorg.0.log", Time: Sat Oct 17 19:15:57 2015
[14.206] (==) Using config file: "/etc/X11/xorg.conf"
[14.206] (==) Using config directory: "/etc/X11/xorg.conf.d"
[14.206] (==) Using system config directory "/opt/xorg-X11R7.6-170-gb8aac01/share/X11/xorg.conf.d"
[14.206] (==) No Layout section.  Using the first Screen section.
[14.206] (==) No screen section available. Using defaults.
[14.206] (**) |-->Screen "Default Screen Section" (0)
[14.206] (**) |   |-->Monitor ""
[14.206] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[14.206] (**) |   |-->Device "radeon"
[14.206] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[14.206] (==) Automatically adding devices
[14.206] (==) Automatically enabling devices
[14.206] (==) Automatically adding GPU devices
[14.206] (==) Max clients allowed: 256, resource mask: 0x1f
[14.206] (==) FontPath set to:
	/opt/xorg-X11R7.6-170-gb8aac01/share/fonts/X11/misc/,
	/opt/xorg-X11R7.6-170-gb8aac01/share/fonts/X11/TTF/,
	/opt/xorg-X11R7.6-170-gb8aac01/share/fonts/X11/OTF/,
	/opt/xorg-X11R7.6-170-gb8aac01/share/fonts/X11/Type1/,
	/opt/xorg-X11R7.6-170-gb8aac01/share/fonts/X11/100dpi/,
	/opt/xorg-X11R7.6-170-gb8aac01/share/fonts/X11/75dpi/
[14.206] (**) ModulePath set to "/opt/xorg/lib/xorg/modules"
[14.206] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[14.206] (II) Loader magic: 0x80ac60
[14.206] (II) Module ABI versions:
[14.206] 	X.Org ANSI C Emulation: 0.4
[14.206] 	X.Org Video Driver: 20.0
[14.206] 	X.Org XInput driver : 22.1
[14.206] 	X.Org Server Extension : 9.0
[14.207] (++) using VT number 7

[14.207] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[14.207] (II) xfree86: Adding drm device (/dev/dri/card0)
[14.209] (--) PCI:*(0:2:0:0) 1002:67b1:1462:2015 rev 128, Mem @ 0xd000/268435456, 0xcf80/8388608, 0xfbbc/262144, I/O @ 0xb000/256, BIOS @ 0x/131072
[14.209] (II) Open ACPI successful (/var/run/acpid.socket)
[14.209] (II) "glx" will be loaded by default.
[14.209] (II) LoadModule: "dri2"
[14.209] (II) Module "dri2" already built-in
[14.209] (II) LoadModule: "glamoregl"
[14.209] (II) Loading /opt/xorg/lib/xorg/modules/libglamoregl.so
[14.212] (II) Module glamoregl: vendor="X.Org Foundation"
[14.212] 	compiled for 1.17.99.901, module version = 1.0.0
[14.212] 	ABI class: X.Org ANSI C Emulation, version 0.4
[14.212] (II) LoadModule: "glx"
[14.212] (II) Loading /opt/xorg/lib/xorg/modules/extensions/libglx.so
[14.213] (II) Module glx: vendor="X.Org Foundation"
[14.213] 	compiled for 1.17.99.901, module version = 1.0.0
[14.213] 	ABI class: X.Org Server Extension, version 9.0
[14.213] (==) AIGLX enabled
[14.213] (II) LoadModule: "radeon"
[14.213] (II) Loading /opt/xorg/lib/xorg/modules/drivers/radeon_drv.so
[14.213] (II) Module radeon: vendor="X.Org Foundation"
[14.213] 	compiled for 1.17.2, module version = 7.5.99
[14.213] 	Module class: X.Org Video Driver
[14.213] 	ABI class: X.Org Video Driver, version 19.0
[14.213] (EE) module ABI major version (19) doesn't match the server's version (20)
[14.213] (II) UnloadModule: "radeon"
[14.213] 

Re: EGL init problem

[Christopher Barry]

On Fri, 16 Oct 2015 16:11:53 +0900
Michel Dänzer  wrote:

>On 16.10.2015 15:55, Christopher Barry wrote:
>> On Fri, 16 Oct 2015 15:32:38 +0900
>> Michel Dänzer  wrote:
>> 
>>> On 16.10.2015 14:47, Christopher Barry wrote:
>>>>
>>>> mesa/mesa build failed again.
>>>> config.log attached 
>>>>
>>>> This time, fresh clone, the values from modules-file are indeed
>>>> picked up in the ./configure line.
>>>>
>>>> however, later, all of the internal LLVM vars have no values, which
>>>> seems a bit suspect, since I'm feeding it the path.
>>>
>>> Does /opt/lib/llvm/bin/llvm-config exist? If yes, what does
>>>
>>> /opt/lib/llvm/bin/llvm-config --version
>>>
>>> say?
>>>
>>>
>> 
>> $ ls -la /opt/lib/llvm
>> lrwxrwxrwx 1 cbarry cbarry 11 Oct 11 12:53 /opt/lib/llvm ->
>> llvm-3.8.0/
>> 
>> $ which llvm-config
>> /opt/lib/llvm/bin/llvm-config
>> $ llvm-config --version
>> 3.8.0
>> 
>> $ ldconfig -p | grep llvm
>>libclang.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libclang.so
>>libLTO.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libLTO.so
>>libLLVM-3.8.so (libc6,x86-64)
>> => /opt/lib/llvm-3.8.0/lib/libLLVM-3.8.so
>> 
>> the PATH and my settings in in configure used the symlink - ldconfig
>> was using the actual dirname. I have edited
>> the /etc/ld.so.conf.d/00-xorg.conf file to be the symlink path, ran
>> ldconfig, and verified it changed:
>> 
>> $ ldconfig -p | grep llvm
>>libclang.so (libc6,x86-64) => /opt/lib/llvm/lib/libclang.so
>>libLTO.so (libc6,x86-64) => /opt/lib/llvm/lib/libLTO.so
>>libLLVM-3.8.so (libc6,x86-64) => /opt/lib/llvm/lib/libLLVM-3.8.so
>> 
>> Re-running the build now to retry the failed modules...
>
>I doubt that'll make a difference, in which case you should probably
>take this to the mesa-...@lists.freedesktop.org mailing list.
>
>Actually from your last config.log it looks like something went
>seriously bonkers in that configure run, e.g. several of the *_FALSE
>and *_TRUE variables are both empty. Can you also provide the
>corresponding stdout/stderr output of configure?
>
>

Yes, I'm logging the build, but it's still going.
I'll push it up tomorrow.

Actually, scrolling up and pasting just config part to pasteall:
http://www.pasteall.org/61741


-C

___
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: EGL init problem

[Christopher Barry]

On Fri, 16 Oct 2015 02:55:13 -0400
Christopher Barry  wrote:

>On Fri, 16 Oct 2015 15:32:38 +0900
>Michel Dänzer  wrote:
>
>>On 16.10.2015 14:47, Christopher Barry wrote:
>>> 
>>> mesa/mesa build failed again.
>>> config.log attached 
>>> 
>>> This time, fresh clone, the values from modules-file are indeed
>>> picked up in the ./configure line.
>>> 
>>> however, later, all of the internal LLVM vars have no values, which
>>> seems a bit suspect, since I'm feeding it the path.
>>
>>Does /opt/lib/llvm/bin/llvm-config exist? If yes, what does
>>
>> /opt/lib/llvm/bin/llvm-config --version
>>
>>say?
>>
>>
>
>$ ls -la /opt/lib/llvm
>lrwxrwxrwx 1 cbarry cbarry 11 Oct 11 12:53 /opt/lib/llvm -> llvm-3.8.0/
>
>$ which llvm-config
>/opt/lib/llvm/bin/llvm-config
>$ llvm-config --version
>3.8.0
>
>$ ldconfig -p | grep llvm
>   libclang.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libclang.so
>   libLTO.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libLTO.so
>   libLLVM-3.8.so (libc6,x86-64)
> => /opt/lib/llvm-3.8.0/lib/libLLVM-3.8.so
>
>the PATH and my settings in in configure used the symlink - ldconfig
>was using the actual dirname. I have edited
>the /etc/ld.so.conf.d/00-xorg.conf file to be the symlink path, ran
>ldconfig, and verified it changed:
>
>$ ldconfig -p | grep llvm
>   libclang.so (libc6,x86-64) => /opt/lib/llvm/lib/libclang.so
>   libLTO.so (libc6,x86-64) => /opt/lib/llvm/lib/libLTO.so
>   libLLVM-3.8.so (libc6,x86-64) => /opt/lib/llvm/lib/libLLVM-3.8.so
>
>Re-running the build now to retry the failed modules...

..And, what I discovered by looking in mesa/mesa/config.log after
re-starting the build, is that the options get reset to just the prefix=
param, and all other params are missing from that log file now. This is
when re-running the build.sh script with the --resumefile parameter.
Apparently it does not re-read the modules file? dunno, I'll
investigate the script in the morning.

I gotta crash now though, it's 3:00am here. Thanks for looking at all
this mess with me, I really do appreciate it. Hopefully the llvm ld path
issue was the primary culprit...

-C

___
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: EGL init problem

[Christopher Barry]

On Fri, 16 Oct 2015 15:32:38 +0900
Michel Dänzer  wrote:

>On 16.10.2015 14:47, Christopher Barry wrote:
>> 
>> mesa/mesa build failed again.
>> config.log attached 
>> 
>> This time, fresh clone, the values from modules-file are indeed
>> picked up in the ./configure line.
>> 
>> however, later, all of the internal LLVM vars have no values, which
>> seems a bit suspect, since I'm feeding it the path.
>
>Does /opt/lib/llvm/bin/llvm-config exist? If yes, what does
>
> /opt/lib/llvm/bin/llvm-config --version
>
>say?
>
>

$ ls -la /opt/lib/llvm
lrwxrwxrwx 1 cbarry cbarry 11 Oct 11 12:53 /opt/lib/llvm -> llvm-3.8.0/

$ which llvm-config
/opt/lib/llvm/bin/llvm-config
$ llvm-config --version
3.8.0

$ ldconfig -p | grep llvm
   libclang.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libclang.so
   libLTO.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libLTO.so
   libLLVM-3.8.so (libc6,x86-64) => /opt/lib/llvm-3.8.0/lib/libLLVM-3.8.so

the PATH and my settings in in configure used the symlink - ldconfig
was using the actual dirname. I have edited
the /etc/ld.so.conf.d/00-xorg.conf file to be the symlink path, ran
ldconfig, and verified it changed:

$ ldconfig -p | grep llvm
   libclang.so (libc6,x86-64) => /opt/lib/llvm/lib/libclang.so
   libLTO.so (libc6,x86-64) => /opt/lib/llvm/lib/libLTO.so
   libLLVM-3.8.so (libc6,x86-64) => /opt/lib/llvm/lib/libLLVM-3.8.so

Re-running the build now to retry the failed modules...
___
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

doc creation errors and warnings

[Christopher Barry]

Hi, here's a section of my build log to show error pattern:

http://www.pasteall.org/61740

my source is in /usr/src/x
my target is /opt/xorg-X11R7.6-170-gb8aac01/

Why would the html doc build be looking in /usr/share/doc for .db files?

further down in the log, pdf creation fails with a big java backtrace
too.

Could I be missing a dependency I'm unaware of? Possibly some XML lib
or something?


Thanks,
-C
___
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: EGL init problem

[Christopher Barry]

On Fri, 16 Oct 2015 13:03:14 +0900
Michel Dänzer  wrote:

>On 16.10.2015 12:43, Christopher Barry wrote:
>> On Fri, 16 Oct 2015 11:50:27 +0900
>> Michel Dänzer  wrote:
>> 
>>> On 15.10.2015 22:33, Christopher Barry wrote:
>>>> On Thu, 15 Oct 2015 11:16:03 +0900
>>>> Michel Dänzer  wrote:
>>>>
>>>>> On 15.10.2015 02:47, Christopher Barry wrote:
>>>>>> On Wed, 14 Oct 2015 10:35:23 +0900
>>>>>> Michel Dänzer  wrote:
>>>>>>
>>>>>>> On 14.10.2015 04:14, Christopher Barry wrote:
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> Can someone help me with the correct incantation to compile X
>>>>>>>> git-master for hw-accel with an AMD R9 380?
>>>>>>>>
>>>>>>>> Using --modfile w/ build.sh, and have tried the following (each
>>>>>>>> on a single line in the modules-file):
>>>>>>>>
>>>>>>>> mesa/mesa --enable-dri --enable-dri3 --enable-glx
>>>>>>>> --enable-glx-tls --enable-egl --enable-gbm
>>>>>>>> --enable-shared-glapi --enable-gallium-llvm
>>>>>>>> --enable-llvm-shared-libs --enable-r600-llvm-compiler
>>>>>>>> --with-llvm-prefix=/opt/lib/llvm/ --with-egl-platforms=x11,drm
>>>>>>>> --with-dri-drivers=r300,r600,radeon,svga,swrast
>>>>>>>> --with-gallium-drivers=r300,r600,radeonsi,svga,swrast
>>>>>>>>
>>>>>>>> xserver --enable-glamor
>>>>>>>>
>>>>>>>>
>>>>>>>> I get the following errors in my log Xorg.0.log:
>>>>>>>>
>>>>>>>> (EE) RADEON(0): glamor detected, failed to initialize EGL.
>>>>>>>> (EE) AIGLX: reverting to software rendering
>>>>>>>
>>>>>>> Please provide the full Xorg.0.log file.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> Thanks  Michel,
>>>>>>
>>>>>> I recompiled with --with-dri-drivers=''.
>>>>>>
>>>>>> log attached
>>>>>
>>>>> [...]
>>>>>
>>>>>> [ 9.337] couldn't get display device
>>>>>
>>>>> This means gbm_create_device() returns NULL. I suspect it may not
>>>>> be picking up some of your self-built Mesa binaries, e.g.
>>>>> libgbm.so.1. I'd try running Xorg in strace to see where it's
>>>>> picking that up from.
>>>>>
>>>>
>>>> Here's what the linker is returning - I *think* that should tell us
>>>> without tracing.
>>>>
>>>> [-][~]:: ldconfig -p | grep libgbm
>>>> libgbm.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgbm.so.1
>>>> libgbm.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgbm.so
>>>>
>>>> So, correct you are. It's showing the libs only in the standard
>>>> packaged X location.
>>>>
>>>> Doing a find for the libs in /opt, which is where I'm putting
>>>> stuff:
>>>>
>>>> [-][~]:: find /opt/ -type f -name "*libgbm*"
>>>> /opt/xorg-orig/lib/libgbm.so.1.0.0
>>>> /opt/xorg-orig/lib/libgbm.la
>>>>
>>>> ...and they're found /only/ in the first build of xorg I did a
>>>> month or more ago, which I've since renamed to xorg-orig.
>>>>
>>>> The xorg I'm running now is rooted in /opt/xorg-new, which does not
>>>> have these libs at all. What switch am I missing that is not
>>>> getting them built? Does a different module in modules-file need a
>>>> parameter to build gbm? I do have --enable-gbm set for mesa/mesa,
>>>> so I'm confused as to why they are not getting built.
>>>> mesa/mesa/config.log has HAVE_GBM_FALSE='' and HAVE_GBM_TRUE='#'
>>>> set.
>>>>
>>>> I've attached that config.log as well for your perusal if it might
>>>> be helpful.
>>>
>>>From the top of config.log:
>>>
>>>> Invocation command line was
>>>>
>>>>   $ ./configure --prefix=/opt/xorg-new
>>>
>>> So your parameters aren't getting passed to Mesa's configure.
>>>
>>>
>> 
>> Yeah, I saw that and wondered myself. I figured because they were set
>> as parameters to mesa in the --modfile file that build.sh uses, that
>> they must get passed in somewhere else. I've used the modules file
>> method before, and the params in the file were used, so it used to
>> work anyway.
>
>I don't know any other way of passing arguments to configure scripts,
>and there's no other trace in config.log of --enable-gbm or
>--with-egl-platforms=x11,drm being passed in.
>
>I think you need to look into how build.sh is supposed to pass the
>arguments to Mesa's configure script and why it's not happening.
>
>

It's a pretty big script, and I will investigate if it fails again from
a completely new clone. For now, I'm hoping that'll jiggle the handle...

Any thoughts on verbose debug logging? Is there a global for that?

Thanks,
-C
___
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: EGL init problem

[Christopher Barry]

On Fri, 16 Oct 2015 11:50:27 +0900
Michel Dänzer  wrote:

>On 15.10.2015 22:33, Christopher Barry wrote:
>> On Thu, 15 Oct 2015 11:16:03 +0900
>> Michel Dänzer  wrote:
>> 
>>> On 15.10.2015 02:47, Christopher Barry wrote:
>>>> On Wed, 14 Oct 2015 10:35:23 +0900
>>>> Michel Dänzer  wrote:
>>>>
>>>>> On 14.10.2015 04:14, Christopher Barry wrote:
>>>>>> Hi
>>>>>>
>>>>>> Can someone help me with the correct incantation to compile X
>>>>>> git-master for hw-accel with an AMD R9 380?
>>>>>>
>>>>>> Using --modfile w/ build.sh, and have tried the following (each
>>>>>> on a single line in the modules-file):
>>>>>>
>>>>>> mesa/mesa --enable-dri --enable-dri3 --enable-glx
>>>>>> --enable-glx-tls --enable-egl --enable-gbm --enable-shared-glapi
>>>>>> --enable-gallium-llvm --enable-llvm-shared-libs
>>>>>> --enable-r600-llvm-compiler --with-llvm-prefix=/opt/lib/llvm/
>>>>>> --with-egl-platforms=x11,drm
>>>>>> --with-dri-drivers=r300,r600,radeon,svga,swrast
>>>>>> --with-gallium-drivers=r300,r600,radeonsi,svga,swrast
>>>>>>
>>>>>> xserver --enable-glamor
>>>>>>
>>>>>>
>>>>>> I get the following errors in my log Xorg.0.log:
>>>>>>
>>>>>> (EE) RADEON(0): glamor detected, failed to initialize EGL.
>>>>>> (EE) AIGLX: reverting to software rendering
>>>>>
>>>>> Please provide the full Xorg.0.log file.
>>>>>
>>>>>
>>>>
>>>> Thanks  Michel,
>>>>
>>>> I recompiled with --with-dri-drivers=''.
>>>>
>>>> log attached
>>>
>>> [...]
>>>
>>>> [ 9.337] couldn't get display device
>>>
>>> This means gbm_create_device() returns NULL. I suspect it may not be
>>> picking up some of your self-built Mesa binaries, e.g. libgbm.so.1.
>>> I'd try running Xorg in strace to see where it's picking that up
>>> from.
>>>
>> 
>> Here's what the linker is returning - I *think* that should tell us
>> without tracing.
>> 
>> [-][~]:: ldconfig -p | grep libgbm
>> libgbm.so.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgbm.so.1
>> libgbm.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgbm.so
>> 
>> So, correct you are. It's showing the libs only in the standard
>> packaged X location.
>> 
>> Doing a find for the libs in /opt, which is where I'm putting stuff:
>> 
>> [-][~]:: find /opt/ -type f -name "*libgbm*"
>> /opt/xorg-orig/lib/libgbm.so.1.0.0
>> /opt/xorg-orig/lib/libgbm.la
>> 
>> ...and they're found /only/ in the first build of xorg I did a month
>> or more ago, which I've since renamed to xorg-orig.
>> 
>> The xorg I'm running now is rooted in /opt/xorg-new, which does not
>> have these libs at all. What switch am I missing that is not getting
>> them built? Does a different module in modules-file need a parameter
>> to build gbm? I do have --enable-gbm set for mesa/mesa, so I'm
>> confused as to why they are not getting built. mesa/mesa/config.log
>> has HAVE_GBM_FALSE='' and HAVE_GBM_TRUE='#' set.
>> 
>> I've attached that config.log as well for your perusal if it might be
>> helpful.
>
>From the top of config.log:
>
>> Invocation command line was
>> 
>>   $ ./configure --prefix=/opt/xorg-new
>
>So your parameters aren't getting passed to Mesa's configure.
>
>

Yeah, I saw that and wondered myself. I figured because they were set
as parameters to mesa in the --modfile file that build.sh uses, that
they must get passed in somewhere else. I've used the modules file
method before, and the params in the file were used, so it used to work
anyway.

I'm going to delete the whole tree again and start over and see what
that does...

I Really appreciate you helping on this Michel. Thank You.

How should I go about generating the most verbose debug logging
available for everything? Is there an over-arching env var I can set
for that?

Thanks,

 -C






___
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: EGL init problem

[Christopher Barry]

On Wed, 14 Oct 2015 10:35:23 +0900
Michel Dänzer  wrote:

>On 14.10.2015 04:14, Christopher Barry wrote:
>> Hi
>> 
>> Can someone help me with the correct incantation to compile X
>> git-master for hw-accel with an AMD R9 380?
>> 
>> Using --modfile w/ build.sh, and have tried the following (each on a
>> single line in the modules-file):
>> 
>> mesa/mesa --enable-dri --enable-dri3 --enable-glx --enable-glx-tls
>> --enable-egl --enable-gbm --enable-shared-glapi --enable-gallium-llvm
>> --enable-llvm-shared-libs --enable-r600-llvm-compiler
>> --with-llvm-prefix=/opt/lib/llvm/ --with-egl-platforms=x11,drm
>> --with-dri-drivers=r300,r600,radeon,svga,swrast
>> --with-gallium-drivers=r300,r600,radeonsi,svga,swrast
>> 
>> xserver --enable-glamor
>> 
>> 
>> I get the following errors in my log Xorg.0.log:
>> 
>> (EE) RADEON(0): glamor detected, failed to initialize EGL.
>> (EE) AIGLX: reverting to software rendering
>
>Please provide the full Xorg.0.log file.
>
>

Thanks  Michel,

I recompiled with --with-dri-drivers=''.

log attached

-C
[ 8.953] 
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
[ 8.953] 
X.Org X Server 1.17.99.901 (1.18.0 RC 1)
Release Date: 2015-09-01
[ 8.953] X Protocol Version 11, Revision 0
[ 8.953] Build Operating System: Linux 4.0.0-2-amd64 x86_64 
[ 8.953] Current Operating System: Linux monolith 4.0.0-2-amd64 #1 SMP Debian 4.0.8-2 (2015-07-22) x86_64
[ 8.953] Kernel command line: BOOT_IMAGE=/vmlinuz-4.0.0-2-amd64 root=/dev/mapper/system_vg-os_lv ro radeon.dpm=0
[ 8.953] Build Date: 13 October 2015  04:33:08PM
[ 8.953]  
[ 8.953] Current version of pixman: 0.33.3
[ 8.953] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[ 8.953] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 8.953] (==) Log file: "/opt/xorg-new/var/log/Xorg.0.log", Time: Wed Oct 14 13:40:23 2015
[ 8.994] (==) Using config file: "/etc/X11/xorg.conf"
[ 8.994] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 8.994] (==) Using system config directory "/opt/xorg-new/share/X11/xorg.conf.d"
[ 9.144] (==) No Layout section.  Using the first Screen section.
[ 9.144] (==) No screen section available. Using defaults.
[ 9.144] (**) |-->Screen "Default Screen Section" (0)
[ 9.144] (**) |   |-->Monitor ""
[ 9.152] (==) No device specified for screen "Default Screen Section".
	Using the first device section listed.
[ 9.152] (**) |   |-->Device "radeon"
[ 9.152] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[ 9.152] (==) Automatically adding devices
[ 9.152] (==) Automatically enabling devices
[ 9.152] (==) Automatically adding GPU devices
[ 9.153] (==) Max clients allowed: 256, resource mask: 0x1f
[ 9.171] (==) FontPath set to:
	/opt/xorg-new/share/fonts/X11/misc/,
	/opt/xorg-new/share/fonts/X11/TTF/,
	/opt/xorg-new/share/fonts/X11/OTF/,
	/opt/xorg-new/share/fonts/X11/Type1/,
	/opt/xorg-new/share/fonts/X11/100dpi/,
	/opt/xorg-new/share/fonts/X11/75dpi/
[ 9.171] (**) ModulePath set to "/opt/xorg/lib/xorg/modules"
[ 9.171] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 9.171] (II) Loader magic: 0x80ab20
[ 9.171] (II) Module ABI versions:
[ 9.171] 	X.Org ANSI C Emulation: 0.4
[ 9.171] 	X.Org Video Driver: 20.0
[ 9.171] 	X.Org XInput driver : 22.1
[ 9.171] 	X.Org Server Extension : 9.0
[ 9.172] (++) using VT number 7

[ 9.172] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 9.172] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 9.174] (--) PCI:*(0:2:0:0) 1002:67b1:1462:2015 rev 128, Mem @ 0xd000/268435456, 0xcf80/8388608, 0xfbbc/262144, I/O @ 0xb000/256, BIOS @ 0x/131072
[ 9.174] (II) Open ACPI successful (/var/run/acpid.socket)
[ 9.174] (II) "glx" will be loaded by default.
[ 9.174] (II) LoadModule: "dri2"
[ 9.174] (II) Module "dri2" already built-in
[ 9

EGL init problem

[Christopher Barry]

Hi

Can someone help me with the correct incantation to compile X
git-master for hw-accel with an AMD R9 380?

Using --modfile w/ build.sh, and have tried the following (each on a
single line in the modules-file):

mesa/mesa --enable-dri --enable-dri3 --enable-glx --enable-glx-tls
--enable-egl --enable-gbm --enable-shared-glapi --enable-gallium-llvm
--enable-llvm-shared-libs --enable-r600-llvm-compiler
--with-llvm-prefix=/opt/lib/llvm/ --with-egl-platforms=x11,drm
--with-dri-drivers=r300,r600,radeon,svga,swrast
--with-gallium-drivers=r300,r600,radeonsi,svga,swrast

xserver --enable-glamor


I get the following errors in my log Xorg.0.log:

(EE) RADEON(0): glamor detected, failed to initialize EGL.
(EE) AIGLX: reverting to software rendering


What am I doing wrong?

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

Re: Dual 4K slowness due to xorg threading concept?

[Christopher Barry]

On Fri, 02 Oct 2015 09:44:19 +0200
Thomas Wunder  wrote:

>Hi all,
>
>Recently I got a new workstation consisting of these components:
>Two 4K Monitors (DP 1.2 at 60Hz), i7-5820K (not yet overclocked), MSI
>X99A- based mainboard, Radeon R7 250.
>This is the software I'm running on it (Debian Jessie):
>Linux 3.16.0 Debian build 4, fglrx 14.9, xorg 7.7, (KDE 4.12)
>
>Problem:
>"Graphics stuff" seems to work smoothly on lower resolutions (e.g. 2x 
>2560x1600). On high resolution (2x 3840x2160) still everything 
>(moving/resizing windows, playing videos, scrolling through lists,
>text views or consoles, opening menus) goes smoothly but only as long
>as single windows are really small (and as long as there are not too
>many of them). As soon as a window becomes half the size of a screen
>or even full screen, operations mentioned before become horribly slow
>(K-Menu takes up to 8 secs to even open up) and CPU usage of the Xorg
>process is vastly increasing (to about 100%). I don't really have an
>idea of what's going wrong here. There are no apparent errors etc.
>The only thing that seems really suspect to me is the 100% CPU which I
>would attribute to a (multi-)threading issue... I'd really appreciate
>if you could give me a hand and point me to the right direction to get
>things working.
>
>Cheers
> Thomas

http://gpu.userbenchmark.com/Compare/AMD-R9-380-vs-AMD-R7-250/3482vsm8217

Get a real card would be my advice.
___
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: Color Management

[Christopher Barry]

On Mon, 21 Sep 2015 19:26:38 +0200
Martin Kaffanke  wrote:

>Hi there, 
>
>Is there a way to make colors on the display looking the same as on
>the printer, by printing a Page and compare the screen on sight? 
>
>Martin 

This is usually done in the monitor's OSD color temp controls


--
Regards,
Christopher Barry
___
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: building / configuring X correctly

[Christopher Barry]

On Thu, 6 Aug 2015 12:51:06 +0900
Michel Dänzer  wrote:

>On 06.08.2015 12:13, Christopher Barry wrote:
>> On Thu, 6 Aug 2015 11:29:16 +0900
>> Michel Dänzer  wrote:
>> 
>>> On 06.08.2015 09:04, Christopher Barry wrote:
>>>>
>>>> Greetings,
>>>>
>>>> I got a new video card (radeon r9 390) to replace my aging hd7850
>>>> and it caused total system lockups in debian sid after just a few
>>>> minutes in Blender. I decided to try to compile X and friends from
>>>> source to get the latest of everything (using build.sh). I compiled
>>>> and installed the latest LLVM and glamor as well. I've used
>>>> multiple sources of information from the web, but I'm stymied at
>>>> this point.
>>>>
>>>> Bottom line: I get no hw acceleration, only two of my three
>>>> monitors are displaying, and it's not clear to me if I have
>>>> radeonsi running right or not or at all.
>>>>
>>>> I'm hoping someone can spot something obviously wrong I'm doing.
>>>> There's a bunch of different log and system output data in the
>>>> linked zipfile that may prove useful in understanding what's not
>>>> right. 
>>>>
>>>> https://filetea.me/t1sY8IXSi6CTVivPu7e3oRTsw
>>>>
>>>> The build log shows a bunch of attempts at getting mesa to compile,
>>>> but indeed it finally did. I'm not sure my options are correct
>>>> though.
>>>
>>> Looks fine to me.
>>>
>>>
>>>From Xorg.0.log:
>>>
>>>> [ 9.806] couldn't get display device
>>>> [ 9.806] (EE) RADEON(0): glamor detected, failed to initialize
>>>> EGL.
>>>
>>> glamor fails to initialize EGL, so you're currently not using any
>>> hardware acceleration. Can try running Xorg with the environment
>>> variable EGL_LOG_LEVEL=debug and get the stderr output from that?
>>>
>>>
>> 
>> 
>> I honestly didn't really know how to do what you asked, but I tried
>> this:
>> 
>> export EGL_LOG_LEVEL=debug; Xorg :1 -terminate \
>> 2>&1 >> /tmp/egl-debug.log & sleep 2 ; DISPLAY=:1 xterm
>
>Yeah, that's basically what I had in mind.
>
>
>> Nothing got output to /tmp/egl-debug.log, and these errors were in
>> the new Xorg.1.log:
>
>The permission errors aren't in the Xorg.0.log you referenced before,
>so I don't think they're relevant.
>
>
>It looks like libgbm fails to initialize. According to the ldconfig.log
>you referenced, libgbm.so.1 isn't getting picked up from /opt/xorg,
>fixing that might help.
>
>

OK, cool. Seems I'm actually closer than I thought :)

Thanks so much for the realtime help Michael!

Cheers
___
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: building / configuring X correctly

[Christopher Barry]

On Thu, 6 Aug 2015 11:29:16 +0900
Michel Dänzer  wrote:

>On 06.08.2015 09:04, Christopher Barry wrote:
>> 
>> Greetings,
>> 
>> I got a new video card (radeon r9 390) to replace my aging hd7850
>> and it caused total system lockups in debian sid after just a few
>> minutes in Blender. I decided to try to compile X and friends from
>> source to get the latest of everything (using build.sh). I compiled
>> and installed the latest LLVM and glamor as well. I've used multiple
>> sources of information from the web, but I'm stymied at this point.
>> 
>> Bottom line: I get no hw acceleration, only two of my three monitors
>> are displaying, and it's not clear to me if I have radeonsi running
>> right or not or at all.
>> 
>> I'm hoping someone can spot something obviously wrong I'm doing.
>> There's a bunch of different log and system output data in the
>> linked zipfile that may prove useful in understanding what's not
>> right. 
>> 
>> https://filetea.me/t1sY8IXSi6CTVivPu7e3oRTsw
>> 
>> The build log shows a bunch of attempts at getting mesa to compile,
>> but indeed it finally did. I'm not sure my options are correct
>> though.
>
>Looks fine to me.
>
>
>From Xorg.0.log:
>
>> [ 9.806] couldn't get display device
>> [ 9.806] (EE) RADEON(0): glamor detected, failed to initialize
>> EGL.
>
>glamor fails to initialize EGL, so you're currently not using any
>hardware acceleration. Can try running Xorg with the environment
>variable EGL_LOG_LEVEL=debug and get the stderr output from that?
>
>


I honestly didn't really know how to do what you asked, but I tried
this:

export EGL_LOG_LEVEL=debug; Xorg :1 -terminate \
2>&1 >> /tmp/egl-debug.log & sleep 2 ; DISPLAY=:1 xterm

Nothing got output to /tmp/egl-debug.log, and these errors were in the
new Xorg.1.log:
egrep '(EE)|(WW)' /opt/xorg/var/log/Xorg.1.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 15142.204] (EE) /dev/dri/card0: failed to set DRM interface version
1.4: Permission denied
[ 15142.565] (EE) RADEON(0): glamor detected, failed to initialize EGL.
[ 15143.352] (WW) RADEON(0): Direct rendering disabled
[ 15143.357] (EE) AIGLX: reverting to software rendering
[ 15143.446] (EE) /dev/dri/card0: failed to set DRM interface version
1.4: Permission denied

Not sure why it's permission denied, I'm in the video group,
and /opt/xorg/bin/Xorg is mode 6755. Must be how I'm invoking it...


___
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

building / configuring X correctly

[Christopher Barry]

Greetings,

I got a new video card (radeon r9 390) to replace my aging hd7850 and it
caused total system lockups in debian sid after just a few minutes in
Blender. I decided to try to compile X and friends from source to get
the latest of everything (using build.sh). I compiled and installed the
latest LLVM and glamor as well. I've used multiple sources of
information from the web, but I'm stymied at this point.

Bottom line: I get no hw acceleration, only two of my three monitors
are displaying, and it's not clear to me if I have radeonsi running
right or not or at all.

I'm hoping someone can spot something obviously wrong I'm doing. There's
a bunch of different log and system output data in the linked zipfile
that may prove useful in understanding what's not right. 

https://filetea.me/t1sY8IXSi6CTVivPu7e3oRTsw

The build log shows a bunch of attempts at getting mesa to compile, but
indeed it finally did. I'm not sure my options are correct though.

I was using the resume feature and the modfile feature as well as -c
(clean) in build.sh, but it does not clean prior to a rebuild oddly. I
looped there failing for quite a while, until I just manually cleaned
and it compiled. I'm working on a patch for that now.

Anyway, thanks for having a look. If more/different data is needed
please advise.

Cheers
___
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: Ask for step-by-step instructions to connect between local X server and remote display manager via XDMCP

[Christopher Barry]

On Wed, 31 Dec 2014 09:07:22 -0500
Heng Zhou  wrote:

>Please leave the slot to
>other experts. Thanks.

Aye Aye, Captain.

Good Luck.
___
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: Ask for step-by-step instructions to connect between local X server and remote display manager via XDMCP

[Christopher Barry]

On Tue, 30 Dec 2014 21:05:18 -0500
Heng Zhou  wrote:

>I want set up an environment in which a local X server is connecting a
>remote display manager via XDMCP protocol, just like the second
>picture in the wikipedia item "X display manager" (
>http://en.wikipedia.org/wiki/X_display_manager_%28program_type%29)
>shows. The specific configuration is described in the following.
>
>A computer is running ubuntu 14.04 LTS in front of me. Call it "local
>machine".
>
>A headless server is running ubuntu 14.04 LTS at another geographical
>place. Call it "remote machine". The remote machine has no graphics
>card, no attached monitor, but I have full control over it.
>Concretely, it is an Amazon EC2 ubuntu instance.
>
>The local machine has a physical graphics card and an attached
>monitor. It is running ordinary ubuntu desktop so the X Window System
>-- X.Org Server -- is running after boot, presumably.
>
>The remote machines has installed LightDM, the display manager of
>ubuntu. And I am sure it is running over there by checking the results
>returned by command ps aux|grep lightdm.
>
>That's the configuration of the local and remote machines. Now I need
>to follow the steps in the wikipedia item "X display manager" (please
>see the link above) to try to connect the local X server with the
>remote display manager LightDM. What I wish to happen should be,
>according to my understanding of the wikipedia webpage, as follows:
>
>(1) The local machines run a XDMCP Chooser program to select the
>display manager running now on the remote machine to connect.
>
>(2) The X server on the local machine uses XDMCP protocol to shake
>hands with the remote display manager LightDM.
>
>(3) The remote display manager LightDM should respond as expected:
>
>a) it connects to the local X server as a client
>
>b) display a login GUI on the local machine, with the assistance of the
>local X server
>
>c) start an X session after I log in
>
>d) run X applications like xterm in the session as directed; display
>its graphical output on the local machine, using the local X display
>server.
>
>e) If possible, I hope in addition to show the unity desktop on the
>local machine, just like a normal ubuntu desktop, but the executable
>code is actually running on the remote machine.
>
>That's all I want. But I have no idea how all these can be done. I
>searched the internet and found something like
>http://wiki.ubuntu.com/xdmcp and
>http://danilodellaquila.com/blog/how-to-remote-login-via-xdmcp-in-ubuntu,
>but they are either too old or too too old, and therefore useless for
>my configuration. So I wonder if anyone familiar with XDMCP and having
>a workable experience could please share his/her ideas on how to
>setting up this environment. Please be specific. Thanks a lot. If you
>need any other info, please ask.
>
>PS: The display manager on the remote machine doesn't have to be
>LightDM. I specifies it just because it's light weight and I'm
>familiar with ubuntu desktop. You can use other option, say, GDM, if
>you are working or once worked with it, to set up the environment.
>
>Looking forward to any workable instructions. Thanks.


See: http://ltsp.org/

--
-C
___
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

[Christopher Barry]

On Tue, 16 Dec 2014 17:04:02 -0500
Alex Deucher  wrote:

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

Re: dp blanks randomly with errors

[Christopher Barry]

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

dp blanks randomly with errors

[Christopher Barry]

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-  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 has not re-appeared. I think I probably need to run this
kernel for a couple of days to verify that it is somehow related to a
software change to be sure my dongle is not really flaking out,
but thought I would post a heads up here in case anyone might know of
any changes that may have caused this behavior.

-C
___
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