similar to: Strangeness on X11 screen capture

Displaying 20 results from an estimated 300 matches similar to: "Strangeness on X11 screen capture"

2019 Jul 16
0
Question on screen capture from command line
I am trying to get the screen capture to work from command line (remotely). I am getting the wrong screen shot. This is what xrandr is giving me... xrandr --query Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right
2017 Aug 16
0
Dualhead issue
On Wed, Aug 16, 2017 at 4:33 PM, Ralf Mardorf via Syslinux <syslinux at zytor.com> wrote: > On Wed, 16 Aug 2017 12:46:46 -0700, H. Peter Anvin via Syslinux wrote: >>Is that true for vesamenu only, or even for text mode syslinux? > > Hi, > > I'm using menu.c32 (text mode only), this is the complete config: What about the simpler case without a menu? PROMPT 1
2017 Aug 17
1
Dualhead issue
On Wed, 16 Aug 2017 17:34:45 -0400, Gene Cumm wrote: >PROMPT 1 >TIMEOUT 600 >DEFAULT Pussytoes > >LABEL Pussytoes > MENU LABEL Arch Linux Rt ^Pussytoes > LINUX ../vmlinuz-linux-rt-pussytoes > APPEND root=LABEL=archlinux ro > INITRD ../initramfs-linux-rt-pussytoes.img > >Do you see anything with just this? Hi, I'll test it ASAP, but I doubt that
2016 Oct 27
0
GM108GLM?
Hello, The idea was to use the modesetting DDX instead of Nouveau’s one for Maxwell+ as EXA was [broken][1]. But you can give a try at Ilia’s [patches][2], which fix the Nouveau DDX for GM10x and GM20x (I don’t think it has been tested on a GM108 yet). Best regards, Pierre Moreau [1]: https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=3e2e0faa2ee1cce9c1bb5c7ad80d0592460f3edc
2014 Oct 08
1
A little help with default resolution of CentOS7 and Panasonic TV
Hi, everyone. tldr: How in the heck do I force CentOS7 to boot to a low/conservative GDM resolution? Hoping someone can lend a hand getting CentOS7 to sync to my Panasonic Vierra 42' TV. It worked fine in CentOS6.5 but since installing I boot to a GDM background with no login prompt. I can SSH into the node and configure multiuser runlevel but that's not fun at all. ;) Here's the
2017 Aug 16
0
Dualhead issue
On 08/15/17 04:53, Ralf Mardorf via Syslinux wrote: > Hi, > > my primary monitor is a LCD HDMI2 and the secondary monitor is a CRT > VGA1. The CRT monitor is only turned on on demand, but always connected > by VGA. > > The BIOS is shown on both monitors, but the syslinux menu only on the > CRT, as long as the CRT is connected by VGA. Even if it's turned off, > the
2016 Dec 08
0
GM108GLM?
hi, give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with 4.9, so 4.10 is required. Greetings. On 7 December 2016 10:26:44 a.m. GMT+01:00, "Sune Mølgaard" <smo at translucent.dk> wrote: >Hi again, > >It works :-) > >Reclocking, however, is another kettle of fish. > >Trying #echo 0f > /sys/kernel/debug/dri/0/pstate
2017 Aug 15
2
Dualhead issue
Hi, my primary monitor is a LCD HDMI2 and the secondary monitor is a CRT VGA1. The CRT monitor is only turned on on demand, but always connected by VGA. The BIOS is shown on both monitors, but the syslinux menu only on the CRT, as long as the CRT is connected by VGA. Even if it's turned off, the syslinux menu isn't shown on the LCD connected by HDMI. [root at archlinux ~]# pacman -Q
2016 Dec 08
0
GM108GLM?
also you can't change the clocks when there is nothing running on the GPU. I have some patches pending for this in another series, but maybe I may be able toe extract those fixes. Changing the clocks while something is running shouldn't cause any troubles. Alternatively if you don't care about power consumption, you can boot with nouveau.runpm=0 so that the gpu is always on.
2016 Dec 08
0
GM108GLM?
you can boot with nouveau.config=NvBoost=2 to enable higher clocks, but that won't fill in the difference compared to Intel. For this there are some changes needed on the mesa side regarding scheduling. Also keep in mind, that PCIe is an important bottleneck here, because the GPU can't push frames fast enough through the bus, that's why any "high FPS" benchmark will be in
2012 Jan 04
3
CentOS 6 and screenshot of website
Hi, How one is supposed to do screenshots of a website with CentOS 6? The usual and normal ways I know doing it is: http://www.coderholic.com/pywebshot-generate-website-thumbnails-using-python/ https://github.com/AdamN/python-webkit2png/ But then from some reason RedHat doesn't support them: gnome-python2-extras: * Thu Jul 15 2010 Christopher Aillon <caillon at redhat.com> -
2014 Nov 10
2
Non-Gnome desktop
So, 1. I installed a minimal CentOS-7. 2. I then installed epel-release. 3. I then installed etckeeper from epel. 4. I then ran yum update -y. 5. I then rebooted (kernel update). 6. I then ran "yum groups install "X Window System" 7. I then ran "yum groups "MATE Desktop" 8. I then ran startx. Result: Graphical destop wallpaper appears, spinning disc in center for
2016 Dec 07
2
GM108GLM?
Hi again, It works :-) Reclocking, however, is another kettle of fish. Trying #echo 0f > /sys/kernel/debug/dri/0/pstate hangs X. Trying the same with no X running reveals: Dec 7 10:08:42 dell-smo kernel: [ 728.831020] nouveau 0000:08:00.0: clk: unable to find matching pll values a number of time as then soft lockup. Very much akin to
2016 Dec 08
2
GM108GLM?
Hi, With drm-next from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-next/2016-12-08/ I don't get the error messages, but I still get a soft cpu lockup. What info would you need from me to get it working? Best regards, Sune Mølgaard On 2016-12-08 08:10, Karol Herbst wrote: > hi, > > give the drm-next kernel tree a try. Sadly the reclocking improvements didn't land with
2016 Dec 08
2
GM108GLM?
Aha! That seems to do it. If I interpret correctly, it doesn't set it quite to full power, though, but it's certainly an improvement: 07: core 405 MHz memory 810 MHz 0a: core 270-1124 MHz memory 1600 MHz 0f: core 270-1124 MHz memory 2002 MHz AC DC * AC: core 1012 MHz memory 2002 MHz A short run of glmark2 shows aver 100% improvement to ~550 FPS. Interestingly, it's still nowhere
2018 Dec 05
0
[PATCH 1/4] drm/edid: Pass connector to AVI inforframe functions
On 04.12.2018 20:02, Ville Syrjälä wrote: > On Tue, Dec 04, 2018 at 08:03:53AM +0100, Andrzej Hajda wrote: >> On 03.12.2018 22:48, Ville Syrjälä wrote: >>> On Thu, Nov 29, 2018 at 09:46:16AM +0100, Andrzej Hajda wrote: >>>> Quite late, hopefully not too late. >>>> >>>> >>>> On 21.11.2018 12:51, Ville Syrjälä wrote:
2017 May 04
2
NV130 - gtx 1050 ti
This is probably the problem May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 May 3 16:44:45 kernel: [ 7.068401] nouveau E[ DRM] failed to create 0x80000080, -22 May 3 16:44:45 kernel: [ 7.068723] nouveau: probe of 0000:08:00.0 failed with error -22 I can make this card available - if you can tell me an older card that can do the
2018 Dec 05
0
[PATCH 1/4] drm/edid: Pass connector to AVI inforframe functions
On Wed, Dec 05, 2018 at 08:40:34AM +0100, Andrzej Hajda wrote: > On 04.12.2018 20:02, Ville Syrjälä wrote: > > On Tue, Dec 04, 2018 at 08:03:53AM +0100, Andrzej Hajda wrote: > >> On 03.12.2018 22:48, Ville Syrjälä wrote: > >>> On Thu, Nov 29, 2018 at 09:46:16AM +0100, Andrzej Hajda wrote: > >>>> Quite late, hopefully not too late. > >>>>
2004 May 23
5
OpenSSH v3.8p1 fails to interoperate for GSSAPI (Kerberos) and X-Windows
Versions: openssh-3.8p1-33, heimdal-0.6.1rc3-51, XFree86-4.3.99.902-40, tk-8.4.6-37, all from SuSE 9.1 (unhacked); back-version peers have openssh-3.5p1, XFree86-4.3.0-115, etc. from SuSE 8.2. Symptoms: 1. When the client and server versions are unequal, the Kerberos ticket is not accepted for authentication. All the clients have PreferredAuthentications gssapi-with-mic, gssapi, others. 2.
2017 May 04
0
NV130 - gtx 1050 ti
Hello, Acceleration for Pascal cards is coming in Linux 4.12, support for Pascal cards in xorg-video-nouveau is in 1.0.15, and if I remember correctly, on the Mesa-side, you will need >=17.0. Pierre On 02:04 am - May 04 2017, Karl Schmidt wrote: > This is probably the problem > May 3 16:44:45 kernel: [ 7.068336] nouveau E[ DEVICE][0000:08:00.0] unknown chipset, 0x137000a1 > May