similar to: missing firmware report

We've seen a number of power management and secboot issues with the Pascal-series mobile GPUs. Without a command line it is hard to debug remotely, but see, as one possible example: https://bugs.freedesktop.org/show_bug.cgi?id=100228 Can you try booting with a kernel command line that includes "nouveau.runpm=0" as a debugging step. On Mon, 17 Sep 2018 at 17:46, don fisher <hdf3

I had desire for a light laptop, so purchased an Alienware 13. I am currently unable to display on the external monitor, leaving me with the small 13" display. I am ignorant of how to proceed. I assume the Nouveau driver is being used, but am not sure. I it Intel or Nouveau? When I boot the following appears in dmesg: nouveau: detected PR support, will not use DSM nouveau

I do not know how to debug this situation. Nothing appears in /var/log/messages. I miss the serial port:-( I executed a journalctl -r, and saw an error: kernel: nouveau 00001:01:00.0; Refused to change power state, currently in D3 The last message before reboot was: kernel: watchdog: Bug: soft lockup - CPU#0 stuck for 22s! [ntpd:3265] I have a pair of these Alienware 13 laptops, and would be

When I execute xrandr I receive, omitting the details of resolution options, Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS-1 unknown connection (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) HDMI-2 connected 1920x1080+0+0 (normal left inverted right

I have an Alienware laptop that has Nvidia GTX 880M hardware driven by this driver. I recently purchased an ASUS_VN289H monitor. When my system gives a blanking command, the monitor returns some sort of lost signal message which causes the monitor to unblank and the time out I requested is cancelled. This is probably more of an HDMI question than specific to this hardware, but I was wondering

Alienware 17 r5 also with same graphics (GP106M and Intel 3e9b) does boot from same disk. I look in hwinfo --gfxcard and it says both the Intel (on i915) and the Nvidia (nouveau) are both present. What command tells me which driver is being used? Thanks. Don

The symbol is not used outside of the file, so mark it static. Fixes the following warning: ./drivers/gpu/drm/nouveau/nvkm/engine/disp/gv100.c:591:1: warning: symbol 'gv100_disp_core_mthd_base' was not declared. Should it be static? Signed-off-by: ruanjinjie <ruanjinjie at huawei.com> --- drivers/gpu/drm/nouveau/nvkm/engine/disp/gv100.c | 2 +- 1 file changed, 1 insertion(+), 1

On Tue, 17 Sep 2019 at 01:18, Thierry Reding <thierry.reding at gmail.com> wrote: > > From: Thierry Reding <treding at nvidia.com> > > The engine field in the FIFO fault information registers is actually 9 > bits wide. Looks like this is true for fault buffer parsing too. > > Signed-off-by: Thierry Reding <treding at nvidia.com> > --- >

Dear R-help, I wonder if you could give me some suggestions in how to do a union join of two data frames as follow: -> union join the common column, and insert a 0 if one is missing. I made a function to perform the following, and I know it may not that quite welly written, but it works. Any suggestions are welcome, many thanks. Anthony > q1 =

On Tue, 17 Sep 2019 at 01:18, Thierry Reding <thierry.reding at gmail.com> wrote: > > From: Thierry Reding <treding at nvidia.com> > > The fault information register contains data about the aperture that > caused the failure. This can be useful in debugging aperture related > programming bugs. Should this be parsed for fault buffer entries too? > >

On Thu, Apr 30, 2020 at 12:15:28AM -0400, Ilia Mirkin wrote: > Hi Alexey, > > On Fri, Apr 24, 2020 at 10:52 PM Alexey Dobriyan <adobriyan at gmail.com> wrote: > > > > gp104 refuses to switch to "graphic" mode and show anything past > > this line: > > > > fb0: switching to nouveaufb from EFI VGA > > > > Machine is fine, as

On 01/26/2016 02:40 PM, Ilia Mirkin wrote: > What you're asking for isn't particularly clear... when DPMS is > enabled, instead of suspending the monitor says "no signal" as if it > had been unplugged? Or is something else going on? Then you talk about > passing signals "up the chain" and "filtering"? What signals? What > chain? > > Can

https://bugs.freedesktop.org/show_bug.cgi?id=100567 Bug ID: 100567 Summary: Nouveau system freeze fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hola Fernando, yo en mi trabajo tengo un asus i7(pensaba que era i5) con 4 gb de RAM (windows7) en casa tengo uno portatil con 16 gb funcionando con ubuntu marca dell (alienware). Sinceramente, mi experiencia me dice que no hay color de una marca buena a una normal. De hecho el alienware corre más rápido que un sobremesa mac que tenemos en el laboratorio de caracteristica similares. Problema,

Hi all, On my recent MSI Apache Pro laptop with Intel Skylake + GP106M Nvidia chip, i am unable to use the external HDMI and DP outputs. The outputs are available thru xrandr and can be activated, but the connected monitors always show a black screen. Note that the integrated LCD is connected to the Skylage GPU, while the HDMI and DP outputs are connected to the NVIDIA GP106M GPU. The

Hello, I have an Alienware 8 laptop that contains dual GeForce GTX 880M graphics GPUs with 16GB of video ram, as I understand it. I am running opensuse 3.2. At some times, like once every 10 boots or so, my system will hang on boot. Black screen shown. I looked at my /var/log/messages and there are numerous nouveau errors. I have attached a section of this output. I am willing to perform any

On 06.05.24 20:23, Dan Moulding wrote: > After upgrading to rc7 from rc6 on a system with NVIDIA GP104 using > the nouveau driver, I get no display output from the kernel (only the > output from GRUB shows on the primary display). Nonetheless, I was > able to SSH to the system and get the kernel log from dmesg. I found > errors from nouveau in it. Grepping it for nouveau gives me

While certain modeset operations on gv100+ need us to temporarily disable the LUT, we make the mistake of sometimes neglecting to reprogram the LUT after such modesets. In particular, moving a head from one encoder to another seems to trigger this quite often. GV100+ is very picky about having a LUT in most scenarios, so this causes the display engine to hang with the following error code: disp:

From: Thierry Reding <treding at nvidia.com> Hi Ben, these are a couple of patches that are in preparation for adding GV11B support. The fundamental issue that these are trying to solve is that the GV11B is the first Tegra incarnation of the GPU where the aperture really matters. All prior generations would accept any of them. For dGPUs we usually allocate memory in VRAM, so the default

https://bugs.freedesktop.org/show_bug.cgi?id=109407 Bug ID: 109407 Summary: GTX 1050 fails to initialise acceleration Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at