search for: keeptti

On Dec 9, 2019, at 17:54, Kay Schenk <kay.schenk at gmail.com> wrote: > > Yes, those consoles are available but they are NOT my original text mode login console which used to be vt1 and is now taken over by Gnome. What they do is bring me to a login prompt -- this is NOT what I want. This change to vt1 for my GUI, in this case, Gnome is a change with version 7 of CentOS due to some

Hi, I am trying to use a G94GL based card (Quadro FX1800) on an arm64/aarch64 based board. As the board is running linux-4.1.8, I had to apply the following patches to get the kernel module / drm working: https://lkml.org/lkml/2015/5/15/83 https://lists.freedesktop.org/archives/dri-devel/2015-July/085449.html So far everything seems to work, the card modesets correctly, and the kernel log also

Very odd. Perhaps you're trying to run X as non-root and don't have proper permissions on /dev/dri/card0? It seems like something in https://cgit.freedesktop.org/nouveau/xf86-video-nouveau/tree/src/nv_driver.c#n400 is failing. Not sure what it would be though. HasKMS is returning successfully (since no error is printing and you see the interface version). Will require you to do some

Alan Coopersmith (1): xinit 1.4.0 Emil Velikov (1): autogen.sh: use quoted string variables Gaetan Nadon (3): Remove SCO support for SHELL_CMD and startx man page. Remove support for ancient A/UX 3.0 support Remove left over $(launchagents_DATA) in CLEANFILES Hans de Goede (2): startx: Pass -keeptty when telling the server to start on the current tty

On 12/9/19 5:06 PM, Jonathan Billings wrote: > On Dec 9, 2019, at 17:54, Kay Schenk <kay.schenk at gmail.com> wrote: >> Yes, those consoles are available but they are NOT my original text mode login console which used to be vt1 and is now taken over by Gnome. What they do is bring me to a login prompt -- this is NOT what I want. This change to vt1 for my GUI, in this case, Gnome is

> Am 07.12.19 um 19:23 schrieb Kay Schenk: > > Hello all-- > > > > It seems using ctrl-alt-F1 to exit from GUI back to MY OWN > > SESSION'S > > command line does not work for me. It does nothing. > > > > Is this something that needs to be explicitly enabled? I start GUI > > using > > "startx". > > > > Also, any

Here's 1.18 RC1. Let's figure out when to release this during XDC. Aaron Plattner (3): xfree86: Fix xf86_check_platform_slot's handling of PCI xfree86: Add GPU screens even if there are no active GDevs xfree86: Bump video driver ABI version to 20 Adam Jackson (27): glamor: Fix up indentation xf86Crtc: right-of placement by default. dmx: Fix the

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

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

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

Hello, I'm new here, and I hope I can get any help. At first I thought this is a support mailing list, but it looks more like one for developers. I'm using Nouveau in ubuntu bionic. My problem is, when I connect a second Monitor to my Laptop on DVI-D connector, the monitor is not detected, Nouveau reports it as "disconnected". The Hardware works, because the BIOS uses the

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

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

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.

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

Hi, It would seem like it (attachments are from 4.9-rc1, btw), but it doesn't look like there is any support in the Xorg driver. How can I help with that? Best regards, Sune Mølgaard Translucent ApS On 2016-04-22 09:33, Pierre Moreau wrote: > Hello, > > A patch was merged yesterday to recognise GM108 (see >

Thanks to Thierry for finding this - applying index e14643615698..00eeaaffeae5 100644 --- a/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c +++ b/drivers/gpu/drm/nouveau/nvkm/engine/device/base.c @@ -2369,7 +2369,7 @@ nv13b_chipset = { .imem = gk20a_instmem_new, .ltc = gp100_ltc_new, .mc = gp10b_mc_new, - .mmu = gf100_mmu_new, + .mmu = gp10b_mmu_new,

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

Dear Devs, The support for multiple xscreens (i.e. no xinerama, just separate :0.0 and :0.1 displays) in nouveau is broken. It would be great if someone could confirm this. It is easily done, by commenting the "xinerama" option from the xorg.conf file: https://nouveau.freedesktop.org/wiki/MultiMonitorDesktop/ With the nvidia proprietary drivers separate xscreens work fine. Could