Bug 77494

Summary: [NVE7] fails to load with error -22
Product: xorg Reporter: Mirko Predosin <mpredosin>
Component: Driver/nouveauAssignee: Nouveau Project <nouveau>
Status: RESOLVED WORKSFORME QA Contact: Xorg Project Team <xorg-team>
Severity: normal    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg log of kernel 3.13.9
none
dmesg log of kernel 3.12.6 none

Description Mirko Predosin 2014-04-15 18:21:16 UTC
Since kernel 3.13.9-100 nouveau fails to load with error -22.

Kernel: 3.13.9-100.fc19.i686.PAE #1 SMP Fri Apr 4 00:57:12 UTC 2014 i686 i686 i386 GNU/Linux
X.Org X Server 1.14.4
VGA compatible controller: NVIDIA Corporation GK107GL [Quadro K2000] (rev a1)


[    1.021125] nouveau  [  DEVICE][0000:03:00.0] BOOT0  : 0x0e73e0a2
[    1.021128] nouveau  [  DEVICE][0000:03:00.0] Chipset: GK107 (NVE7)
[    1.021129] nouveau  [  DEVICE][0000:03:00.0] Family : NVE0
[    1.022357] nouveau  [   VBIOS][0000:03:00.0] checking PRAMIN for image...
[    1.022363] nouveau  [   VBIOS][0000:03:00.0] ... signature not found
[    1.022364] nouveau  [   VBIOS][0000:03:00.0] checking PROM for image...
[    1.130818] nouveau  [   VBIOS][0000:03:00.0] ... checksum invalid
[    1.130821] nouveau  [   VBIOS][0000:03:00.0] checking ACPI for image...
[    1.130822] nouveau  [   VBIOS][0000:03:00.0] ... signature not found
[    1.130823] nouveau  [   VBIOS][0000:03:00.0] checking PCIROM for image...
[    1.130829] nouveau 0000:03:00.0: Invalid ROM contents
[    1.130935] nouveau  [   VBIOS][0000:03:00.0] ... appears to be valid
[    1.130937] nouveau  [   VBIOS][0000:03:00.0] using image from PCIROM
[    1.131003] nouveau  [   VBIOS][0000:03:00.0] BIT signature found
[    1.131005] nouveau  [   VBIOS][0000:03:00.0] version 80.07.9b.00.02
[    1.131181] nouveau E[   VBIOS][0000:03:00.0] 0x77df[ ]: unknown opcode 0xc4
[    1.131241] nouveau E[ DEVINIT][0000:03:00.0] init failed, -22
[    1.131298] nouveau E[     DRM] failed to create 0x80000080, -22
[    1.131631] nouveau: probe of 0000:03:00.0 failed with error -22
Comment 1 Mirko Predosin 2014-04-15 18:22:09 UTC
Created attachment 97418 [details]
dmesg log of kernel 3.13.9
Comment 2 Mirko Predosin 2014-04-15 18:27:58 UTC
It works when booting kernel 3.12.6-200.fc19.i686.PAE.

[    1.009126] nouveau  [  DEVICE][0000:03:00.0] BOOT0  : 0x0e73e0a2
[    1.009129] nouveau  [  DEVICE][0000:03:00.0] Chipset: GK107 (NVE7)
[    1.009130] nouveau  [  DEVICE][0000:03:00.0] Family : NVE0
[    1.010376] nouveau  [   VBIOS][0000:03:00.0] checking PRAMIN for image...
[    1.010382] nouveau  [   VBIOS][0000:03:00.0] ... signature not found
[    1.010383] nouveau  [   VBIOS][0000:03:00.0] checking PROM for image...
[    1.119044] nouveau  [   VBIOS][0000:03:00.0] ... checksum invalid
[    1.119046] nouveau  [   VBIOS][0000:03:00.0] checking ACPI for image...
[    1.119048] nouveau  [   VBIOS][0000:03:00.0] ... signature not found
[    1.119049] nouveau  [   VBIOS][0000:03:00.0] checking PCIROM for image...
[    1.119054] nouveau 0000:03:00.0: Invalid ROM contents
[    1.119171] nouveau  [   VBIOS][0000:03:00.0] ... appears to be valid
[    1.119173] nouveau  [   VBIOS][0000:03:00.0] using image from PCIROM
[    1.119235] nouveau  [   VBIOS][0000:03:00.0] BIT signature found
[    1.119237] nouveau  [   VBIOS][0000:03:00.0] version 80.07.9b.00.02
[    1.119374] nouveau E[   VBIOS][0000:03:00.0] 0x77df[ ]: unknown opcode 0xc4
[    1.119465] nouveau  [     PFB][0000:03:00.0] RAM type: GDDR5
[    1.119466] nouveau  [     PFB][0000:03:00.0] RAM size: 2048 MiB
[    1.119468] nouveau  [     PFB][0000:03:00.0]    ZCOMP: 0 tags
[    1.763250] nouveau  [  PTHERM][0000:03:00.0] FAN control: none / external
[    1.763275] nouveau  [  PTHERM][0000:03:00.0] fan management: disabled
[    1.763279] nouveau  [  PTHERM][0000:03:00.0] internal sensor: yes
[    1.807945] nouveau  [     DRM] VRAM: 2048 MiB
[    1.807946] nouveau  [     DRM] GART: 1048576 MiB
[    1.807948] nouveau  [     DRM] TMDS table version 2.0
[    1.807950] nouveau  [     DRM] DCB version 4.0
[    1.807952] nouveau  [     DRM] DCB outp 00: 01000f02 00020030
[    1.807953] nouveau  [     DRM] DCB outp 01: 02000f00 00000000
[    1.807954] nouveau  [     DRM] DCB outp 02: 08811fc6 0f420010
[    1.807956] nouveau  [     DRM] DCB outp 03: 08011f82 00020010
[    1.807957] nouveau  [     DRM] DCB outp 04: 02822fa6 0f420010
[    1.807958] nouveau  [     DRM] DCB outp 05: 02022f62 00020010
[    1.807959] nouveau  [     DRM] DCB conn 00: 00001030
[    1.807961] nouveau  [     DRM] DCB conn 01: 00010146
[    1.807962] nouveau  [     DRM] DCB conn 02: 00002246
[    1.809246] nouveau W[     DRM] voltage table 0xe1 unknown
[    1.809260] nouveau  [     DRM] 0 available performance level(s)
[    1.809261] nouveau  [     DRM] c:
[    1.822552] nouveau  [     DRM] MM: using COPY for buffer copies
[    2.001047] nouveau  [     DRM] allocated 1920x1080 fb: 0x80000, bo e9cce200
[    2.001081] fbcon: nouveaufb (fb0) is primary device
[    2.113501] nouveau 0000:03:00.0: fb0: nouveaufb frame buffer device
[    2.113502] nouveau 0000:03:00.0: registered panic notifier
[    2.113504] [drm] Initialized nouveau 1.1.1 20120801 for 0000:03:00.0 on mino
Comment 3 Mirko Predosin 2014-04-15 18:31:12 UTC
Created attachment 97419 [details]
dmesg log of kernel 3.12.6
Comment 4 Ilia Mirkin 2014-04-15 18:44:00 UTC
Try booting with

nouveau.config=NvBios=PROM

Or potentially try 3.15-rc1, that has a fix for PROM-loading for Kepler chips.
Comment 5 Mirko Predosin 2014-04-15 19:00:22 UTC
Booting with "nouveau.config=NvBios=PROM" resolves the issue on kernel 3.13.9-100.  Thanks!
Comment 6 Samuel Pitoiset 2015-04-07 15:33:34 UTC
I also have this card but I don't have the issue with 3.19.3-1-ARCH.

Mirko, would you try to reproduce this issue with a more recent kernel?

If you can't reproduce it, this bug report should be closed.
Thanks.
Comment 7 Samuel Pitoiset 2015-05-10 17:06:19 UTC
No answer since I asked one month ago. Let me close this old issue.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.