Nouveau - May 2019 - [Bug 110797] New: No video if nomodeset is not set with GTX 460

https://bugs.freedesktop.org/show_bug.cgi?id=110797

            Bug ID: 110797
           Summary: No video if nomodeset is not set with GTX 460
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: newbytee at protonmail.com
        QA Contact: xorg-team at lists.x.org

Greetings!

I have a PC (Dell XPS 8100) with an i7 870 and a GTX 460. No parts have been
changed from its factory state aside from CMOS battery. I attempted to install
Fedora 30 on it very recently, and what I soon noticed was that unless I added
the nomodeset kernel parameter the monitor would say "No signal" soon
after
boot. With nomodeset enabled it boots as normal and everything works, except
the things that usually do not work when nomodeset is set.

Note that this occurs both with nouveau and NVIDIA's proprietary driver,
however the GPU works in Windows 10 so I do not believe that this is a hardware
fault. I have also made sure to verify that I am using the latest BIOS
available for the motherboard.

Regards, Newbyte.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/f7b17f73/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #1 from Newbyte <newbytee at protonmail.com> ---
Worth noting is that this also occurs in Arch Linux and Ubuntu. I have yet to
find a distribution where it does not.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/eafeaad9/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #2 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Can you ssh into the machine from a different computer to see if there's
anything interesting in the logs? Or alternatively maybe the logs from previous
boots are available somewhere?

Unfortunately we need more info than "it doesn't work" to properly
diagnose.

(BTW, "nomodeset" is equivalent to "don't load nouveau, or
any other graphics
drivers".)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/ebfdb60a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #3 from Newbyte <newbytee at protonmail.com> ---
Yes, I am able to access the entire filesystem. Which log(s) might be of
interest to you?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/3a14d236/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #4 from Ilia Mirkin <imirkin at alum.mit.edu> ---
Once it's booted, just run "dmesg" (remotely, obviously). If this
is a
post-facto look at the FS, then whatever file contains the kernel log (which
ends up in /var/log/messages for me, but probably not for you...)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/eed97731/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #5 from Newbyte <newbytee at protonmail.com> ---
Created attachment 144381
  --> https://bugs.freedesktop.org/attachment.cgi?id=144381&action=edit
Kernel log from boot with nouveau

Alright, here is the kernel log (dmesg) from a boot after removing akmod-nvidia
from the system, taken via ssh.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/fef5fd01/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #6 from Newbyte <newbytee at protonmail.com> ---
Created attachment 144382
  --> https://bugs.freedesktop.org/attachment.cgi?id=144382&action=edit
Kernel log from boot with akmod-nvidia

For reference, here is one with akmod-nvidia installed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/e5fd489e/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #7 from Ilia Mirkin <imirkin at alum.mit.edu> ---
You have the wrong version of nvidia blob installed for your GPU. They dropped
Fermi a while back, so you have to use some long-term-support variant.

The nouveau log indicates that there's something REALLY UNHAPPY going on.
All
those errors mean that it's basically rejecting all MMIO's. The log
probably
ran out of memory, which is why the first part isn't visible. Could you try
booting it with like

log_buf_len=2M

and see if you can capture the start of it? Once the MMIO errors start flowing,
anything that follows isn't particularly interesting.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/d156bdbf/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #8 from Newbyte <newbytee at protonmail.com> ---
Created attachment 144384
  --> https://bugs.freedesktop.org/attachment.cgi?id=144384&action=edit
Kernel log from boot with nouveau (log_buf_len=4M)

Note: I noticed that the kernel boot parameters blacklist nouveau. I attempted
to remove that, but in doing so I'm no longer able to ssh into the PC, so I
added them again (which is what this log contains).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/d24f911a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #9 from Newbyte <newbytee at protonmail.com> ---
Hello again,

It turns out I must apologise for my ignorance. I thought that removing
akmod-nvidia was sufficient to rid the blob from my system, but it so turns out
that is not the case. I apologise for any confusion this might have caused.

Removing that also caused dnf to update my grub config so that it no longer
blacklists nouveau, and I'm now in the system via ssh (turns out I needed to
be
more patient). Log will come in a moment.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/cd13bfad/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

Newbyte <newbytee at protonmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #144381|0                           |1
        is obsolete|                            |
 Attachment #144384|0                           |1
        is obsolete|                            |

--- Comment #10 from Newbyte <newbytee at protonmail.com> ---
Created attachment 144385
  --> https://bugs.freedesktop.org/attachment.cgi?id=144385&action=edit
Kernel log from boot with nouveau (earlier ones blacklisted nouveau)

I did not add log_buf_len=4M this time, I'll fetch one with that right after
this

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/4488bbf2/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #11 from Newbyte <newbytee at protonmail.com> ---
Created attachment 144386
  --> https://bugs.freedesktop.org/attachment.cgi?id=144386&action=edit
Kernel log from boot with nouveau (with 4MB buffer)

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/608c57e9/attachment-0001.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #12 from Ilia Mirkin <imirkin at alum.mit.edu> ---
So... a pretty orderly init...

[    3.909830] nouveau 0000:01:00.0: NVIDIA GF104 (0c4200a1)
[    4.070350] nouveau 0000:01:00.0: bios: version 70.04.11.00.01
[    6.154050] nouveau 0000:01:00.0: fb: 1024 MiB GDDR5
[    6.229767] [TTM] Zone  kernel: Available graphics memory: 4059620 kiB
[    6.229770] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    6.229772] [TTM] Initializing pool allocator
[    6.229781] [TTM] Initializing DMA pool allocator
[    6.229806] nouveau 0000:01:00.0: DRM: VRAM: 1024 MiB
[    6.229808] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    6.229814] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    6.229817] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    6.229821] nouveau 0000:01:00.0: DRM: DCB outp 00: 02000300 00000000
[    6.229826] nouveau 0000:01:00.0: DRM: DCB outp 01: 01000302 00020030
[    6.229827] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011380 00000000
[    6.229829] nouveau 0000:01:00.0: DRM: DCB outp 03: 08011382 00020030
[    6.229830] nouveau 0000:01:00.0: DRM: DCB outp 04: 02022362 00020010
[    6.229831] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[    6.229832] nouveau 0000:01:00.0: DRM: DCB conn 01: 00010130
[    6.229833] nouveau 0000:01:00.0: DRM: DCB conn 02: 00002261

... and then ... BAM

[    6.230590] nouveau 0000:01:00.0: bus: MMIO write of 00000002 FAULT at
13b154 [ IBUS ]
[    6.230765] WARNING: CPU: 2 PID: 482 at
drivers/gpu/drm/nouveau/nvkm/engine/disp/outp.c:191 nvkm_outp_init+0x181/0x220
[nouveau]
[    6.230765] Modules linked in: nouveau(+) raid0 hid_logitech_hidpp(+) video
mxm_wmi wmi i2c_algo_bit drm_kms_helper ttm drm crc32c_intel broadcom
bcm_phy_lib serio_raw tg3 firewire_ohci uas usb_storage firewire_core
hid_logitech_dj crc_itu_t
[    6.230774] CPU: 2 PID: 482 Comm: systemd-udevd Not tainted
5.0.17-300.fc30.x86_64 #1
[    6.230775] Hardware name: Dell Inc. Studio XPS 8100/0G3HR7, BIOS A05
07/08/2010
[    6.230822] RIP: 0010:nvkm_outp_init+0x181/0x220 [nouveau]
[    6.230823] Code: e8 48 83 c4 18 e9 78 ff ff ff 0f b6 4d 25 ba ff ff ff ff
0f bc d1 31 c9 83 78 10 01 75 03 8b 4d 2c 89 4c 24 04 e9 fc fe ff ff <0f>
0b e9
51 ff ff ff 48 8b 45 08 83 78 48 03 0f 86 43 ff ff ff 8b
[    6.230824] RSP: 0018:ffffb854013ab7e0 EFLAGS: 00010246
[    6.230825] RAX: 0000000000000000 RBX: 0000000000000000 RCX:
ffff8ee26b64b070
[    6.230825] RDX: 00000000ffffffff RSI: 0000000000000000 RDI:
ffff8ee26b64b070
[    6.230826] RBP: ffff8ee26f0d7480 R08: ffff8ee270354380 R09:
ffff8ee277003c80
[    6.230827] R10: 00000000d8000001 R11: 00000000d8000001 R12:
ffff8ee26b64b008
[    6.230827] R13: ffff8ee26f9d9800 R14: ffff8ee26b64b010 R15:
ffff8ee26ac21400
[    6.230828] FS:  00007fa18da06940(0000) GS:ffff8ee277680000(0000)
knlGS:0000000000000000
[    6.230829] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    6.230830] CR2: 00007fa18eacf020 CR3: 000000022fdac000 CR4:
00000000000006e0
[    6.230831] Call Trace:
[    6.230880]  nvkm_disp_init+0x54/0xd0 [nouveau]
[    6.230917]  nvkm_engine_init+0xaa/0x1e0 [nouveau]
[    6.230955]  nvkm_subdev_init+0xb5/0x200 [nouveau]
[    6.230993]  nvkm_engine_ref.part.0+0x3f/0x60 [nouveau]
[    6.231030]  nvkm_ioctl_new+0x121/0x200 [nouveau]
[    6.231077]  ? nvkm_udevice_map+0x50/0x50 [nouveau]
[    6.231114]  nvkm_ioctl+0xde/0x180 [nouveau]
[    6.231150]  nvif_object_init+0xdb/0x140 [nouveau]
[    6.231186]  nvif_disp_ctor+0x69/0x150 [nouveau]
[    6.231234]  nouveau_display_create+0x2d8/0x620 [nouveau]
[    6.231282]  nouveau_drm_device_init+0x15f/0x810 [nouveau]
[    6.231286]  ? pci_bus_read_config_word+0x49/0x70
[    6.231333]  nouveau_drm_probe+0x1f2/0x2e0 [nouveau]
[    6.231336]  local_pci_probe+0x43/0x90

I don't think I've seen anything of the sort. Something in the display
initialization logic gets immensely upset after getting a MMIO write fault.

Is there anything esp awkward about this GPU that would differentiate it from a
run-of-the-mill desktop GPU that a random person might have?

The PCI ID is just "GF104 [GeForce GTX 460 OEM]" which doesn't
seem too crazy.
And I don't see any PCI-ish errors about 01:00.0 (like unassigned resources
or
whatnot).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/00fe6a4a/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

--- Comment #13 from Newbyte <newbytee at protonmail.com> ---
I'm not aware of anything unusual with it, aside from what you can see
there,
that it is an (Dell) OEM card.

If it helps, here is its hardware configuration:
https://www.dell.com/support/home/us/en/19/product-support/servicetag/f0k9x4j/configuration

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190530/bd5d428f/attachment.html>

https://bugs.freedesktop.org/show_bug.cgi?id=110797

Newbyte <newbytee at protonmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #14 from Newbyte <newbytee at protonmail.com> ---
Good and bad news! Sort of. I decided to try Windows 10 again today, and it
seems as though the PC has issues there too (isn't able to get pass the
spinny
thingy with a Windows logo when booting), so I interpret this as being a
hardware issue after all.

I'll close this as invalid since the issue seems to originate from somewhere
else other than nouveau, thank you for your time.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/nouveau/attachments/20190601/50d4adff/attachment.html>