Displaying 20 results from an estimated 10000 matches similar to: "Where to know the BAR size of NVIDIA GPU"
2017 Nov 17
1
Blank console but X11 works on MCP79 - old regression since 3.8
On Fri, Nov 17, 2017 at 2:37 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
> On Fri, Nov 17, 2017 at 2:25 PM, Ondrej Zary <linux at rainbow-software.org> wrote:
>> On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote:
>>> On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary
>>>
>>> <linux at rainbow-software.org> wrote:
>>> > @@ -483,8
2017 Nov 17
3
Blank console but X11 works on MCP79 - old regression since 3.8
On Friday 17 November 2017 18:41:17 Ilia Mirkin wrote:
> On Fri, Nov 17, 2017 at 12:33 PM, Ondrej Zary
>
> <linux at rainbow-software.org> wrote:
> > @@ -483,8 +483,8 @@
> > nouveau 0000:02:00.0: disp: 0860: 00000000 -> 00000500
> > nouveau 0000:02:00.0: disp: 0864: 00000000
> > nouveau 0000:02:00.0: disp: 0868: 00000000 -> 04000500
>
2020 Oct 09
3
nouveau broken on Riva TNT2 in 5.9.0-rc8: GPU not supported on big-endian
On Fri, Oct 9, 2020 at 5:54 PM Karol Herbst <kherbst at redhat.com> wrote:
>
> On Fri, Oct 9, 2020 at 11:35 PM Ondrej Zary <linux at zary.sk> wrote:
> >
> > Hello,
> > I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped working:
> > [ 0.000000] Linux version 5.9.0-rc8+ (zary at gsql) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian)
2018 Jan 04
2
[PATCH] drm/nouveau/bar/gk20a: Avoid bar teardown during init
Commit bbb163e18960 ("drm/nouveau/bar: implement bar1 teardown")
introduced add a teardown helper function for BAR1. During
initialisation of the Nouveau, initially all the teardown helpers are
called once, before calling their init counterparts. For gk20a, after
the BAR1 teardown function is called, the device is hanging during the
initialisation of the FB sub-device. At this point it
2005 Jan 26
1
cant do it in CLI anymore?
Hi Floks,
This is probably really dumb but here goes:
I used to be able to place calls to my SIP phones from the CLI using the
'Dial' command for testing. I have installed asterisk on a new machine and
copied over the .confs and started it up. It all works fine. But when I try
to initiate a call from the CLI using 'Dial' it just says:
*CLI> Dial
No such command
2016 Nov 25
27
[Bug 98852] New: Nvidia graphics card fan not running or to slow, danger of overheating
https://bugs.freedesktop.org/show_bug.cgi?id=98852
Bug ID: 98852
Summary: Nvidia graphics card fan not running or to slow,
danger of overheating
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2020 Oct 09
2
nouveau broken on Riva TNT2 in 5.9.0-rc8: GPU not supported on big-endian
Hello,
I'm testing 5.9.0-rc8 and found that Riva TNT2 stopped working:
[ 0.000000] Linux version 5.9.0-rc8+ (zary at gsql) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #326 SMP Fri Oct 9 22:31:40 CEST 2020
...
[ 14.771464] nouveau 0000:01:00.0: GPU not supported on big-endian
[ 14.771782] nouveau: probe of 0000:01:00.0 failed with error -38
big-endian? WTF? The
2013 Jul 15
3
[PATCH] drm/nouveau: do not move buffers when not needed
Op 15-07-13 08:05, Ben Skeggs schreef:
> On Fri, Jul 12, 2013 at 10:45 PM, Maarten Lankhorst
> <maarten.lankhorst at canonical.com> wrote:
>> I have no idea what this bogus restriction on placement is, but it breaks decoding 1080p
>> VDPAU at boot speed. With this patch applied I only need to bump the vdec clock to
>> get real-time 1080p decoding. It prevents a lot of
2018 Jul 21
9
[Bug 107325] New: Reported temperature of nvidia card with nouveau driver is wrong
https://bugs.freedesktop.org/show_bug.cgi?id=107325
Bug ID: 107325
Summary: Reported temperature of nvidia card with nouveau
driver is wrong
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
2014 Feb 04
1
[RFC 07/16] drm/nouveau/bar/nvc0: support chips without BAR3
On Sat, Feb 1, 2014 at 1:16 PM, Alexandre Courbot <acourbot at nvidia.com> wrote:
> Adapt the NVC0 BAR driver to make it able to support chips that do not
> expose a BAR3. When this happens, BAR1 is then used for USERD mapping
> and the BAR alloc() functions is disabled, making GPU objects unable
> to rely on BAR for data access and falling back to PRAMIN.
>
>
2013 Sep 04
1
[PATCH] drm/nouveau: do not move buffers when not needed
Op 04-09-13 03:24, Ben Skeggs schreef:
> On Mon, Jul 15, 2013 at 6:39 PM, Maarten Lankhorst
> <maarten.lankhorst at canonical.com> wrote:
>> Op 15-07-13 08:05, Ben Skeggs schreef:
>>> On Fri, Jul 12, 2013 at 10:45 PM, Maarten Lankhorst
>>> <maarten.lankhorst at canonical.com> wrote:
>>>> I have no idea what this bogus restriction on placement
2008 Oct 29
2
Barplot: Vertical bars with long labels
Dear List,
I need a barplot with vertical bars. Each bar should have a label.
The problem is, that the labels are too long, so they overlap, or
only every seccond label is displayed in the output.
Here is a little syntax:
dd <- c(100,110,90,105,95)
barplot(dd,names.arg=c('Conduct Disorders','Attention Deficit',
'Eating Disorders',
2019 Sep 24
3
Is Nouveau really using the io_reserve_lru?
Hi guys,
while working through more old TTM functionality I stumbled over the
io_reserve_lru.
Basic idea is that when this flag is set the driver->io_mem_reserve()
callback can return -EAGAIN resulting in unmapping of other BOs.
But Nouveau doesn't seem to return -EAGAIN in the call path of
io_mem_reserve anywhere.
So is this unused or am I missing something?
Regards,
Christian.
2014 Mar 24
1
[PATCH 03/12] drm/nouveau/bar: only ioremap BAR3 if it exists
On Mon, Mar 24, 2014 at 05:42:25PM +0900, Alexandre Courbot wrote:
> Some chips that use system memory exclusively (e.g. GK20A) do not
> expose 2 BAR regions. For them only BAR1 exists, and it should be used
> for USERD mapping. Do not map BAR3 if its resource does not exist.
>
> Signed-off-by: Alexandre Courbot <acourbot at nvidia.com>
> ---
>
2019 Sep 16
6
[PATCH 0/2] drm/nouveau: Two more fixes
From: Thierry Reding <treding at nvidia.com>
Hi Ben,
I messed up the ordering of patches in my tree a bit, so these two fixes
got separated from the others. I don't consider these particularily
urgent because the crash that the first one fixes only happens on gp10b
which we don't enable by default yet and the second patch fixes a crash
that only happens on module unload (or driver
2013 Jun 05
7
[PATCH RFC] virtio-pci: new config layout: using memory BAR
On Wed, Jun 05, 2013 at 10:46:15AM -0500, Anthony Liguori wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
>
> > On Wed, Jun 05, 2013 at 10:08:37AM -0500, Anthony Liguori wrote:
> >> "Michael S. Tsirkin" <mst at redhat.com> writes:
> >>
> >> > On Wed, Jun 05, 2013 at 07:59:33AM -0500, Anthony Liguori wrote:
>
2013 Jun 05
7
[PATCH RFC] virtio-pci: new config layout: using memory BAR
On Wed, Jun 05, 2013 at 10:46:15AM -0500, Anthony Liguori wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
>
> > On Wed, Jun 05, 2013 at 10:08:37AM -0500, Anthony Liguori wrote:
> >> "Michael S. Tsirkin" <mst at redhat.com> writes:
> >>
> >> > On Wed, Jun 05, 2013 at 07:59:33AM -0500, Anthony Liguori wrote:
>
2014 Nov 25
3
Second copy engine on GF116
On Mon, Nov 24, 2014 at 8:33 PM, Andy Ritger <aritger at nvidia.com> wrote:
> On Fri, Nov 21, 2014 at 01:39:55AM -0500, Ilia Mirkin wrote:
>> On Fri, Nov 21, 2014 at 1:16 AM, Andy Ritger <aritger at nvidia.com> wrote:
>> > Hi Ilia,
>> >
>> > Actually 0x90b8 is different than copy engine. I'm not very familiar
>> > with it, but 0x90b8 is
2014 Mar 24
1
[PATCH 04/12] drm/nouveau/bar/nvc0: support chips without BAR3
On Mon, Mar 24, 2014 at 05:42:26PM +0900, Alexandre Courbot wrote:
[...]
> diff --git a/drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c b/drivers/gpu/drm/nouveau/core/subdev/bar/nvc0.c
[...]
> static int
> -nvc0_bar_ctor(struct nouveau_object *parent, struct nouveau_object *engine,
> - struct nouveau_oclass *oclass, void *data, u32 size,
> - struct nouveau_object
2014 May 23
3
[RFC] drm/nouveau: disable caching for VRAM BOs on ARM
On Mon, May 19, 2014 at 7:16 PM, Lucas Stach <l.stach at pengutronix.de> wrote:
> Am Montag, den 19.05.2014, 19:06 +0900 schrieb Alexandre Courbot:
>> On 05/19/2014 06:57 PM, Lucas Stach wrote:
>> > Am Montag, den 19.05.2014, 18:46 +0900 schrieb Alexandre Courbot:
>> >> This patch is not meant to be merged, but rather to try and understand
>> >> why