Re: Modesetting failure with kernel 3.15; ok with kernel 3.14

[Steven Usdansky <usdanskys@xxxxxxxxx>]

modprobe nouveau modeset=1 does not work for me.

Apr 17 13:36:04 Pyrope kernel: ACPI: \_SB_.PCI0.IXVE.IGPU: failed to evaluate _DSM
Apr 17 13:36:04 Pyrope kernel: nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0aa380a2
Apr 17 13:36:04 Pyrope kernel: nouveau  [  DEVICE][0000:02:00.0] Chipset: MCP77/MCP78 (NVAA)
Apr 17 13:36:04 Pyrope kernel: nouveau  [  DEVICE][0000:02:00.0] Family : NV50
Apr 17 13:36:04 Pyrope kernel: [  104.796957] nouveau  [  DEVICE][0000:02:00.0] BOOT0  : 0x0aa380a2
Apr 17 13:36:04 Pyrope kernel: [  104.797182] nouveau  [  DEVICE][0000:02:00.0] Chipset: MCP77/MCP78 (NVAA)
Apr 17 13:36:04 Pyrope kernel: [  104.797305] nouveau  [  DEVICE][0000:02:00.0] Family : NV50
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] checking PRAMIN for image...
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] ... signature not found
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] checking PROM for image...
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] ... signature not found
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] checking ACPI for image...
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] ... signature not found
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] checking PCIROM for image...
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] ... appears to be valid
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] using image from PCIROM
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Apr 17 13:36:04 Pyrope kernel: [  104.802939] nouveau  [   VBIOS][0000:02:00.0] checking PRAMIN for image...
Apr 17 13:36:04 Pyrope kernel: [  104.803158] nouvmodprobeeau  [   VBIOS][0000:02:00.0] ... signature not found
Apr 17 13:36:04 Pyrope kernel: [  104.803279] nouveau  [   VBIOS][0000:02:00.0] checking PROM for image...
Apr 17 13:36:04 Pyrope kernel: [  104.807743] nouveau  [   VBIOS][0000:02:00.0] ... signature not found
Apr 17 13:36:04 Pyrope kernel: [  104.807863] nouveau  [   VBIOS][0000:02:00.0] checking ACPI for image...
Apr 17 13:36:04 Pyrope kernel: [  104.807980] nouveau  [   VBIOS][0000:02:00.0] ... signature not found
Apr 17 13:36:04 Pyrope kernel: [  104.808153] nouveau  [   VBIOS][0000:02:00.0] checking PCIROM for image...
Apr 17 13:36:04 Pyrope kernel: [  104.809693] nouveau  [   VBIOS][0000:02:00.0] ... appears to be valid
Apr 17 13:36:04 Pyrope kernel: [  104.809813] nouveau  [   VBIOS][0000:02:00.0] using image from PCIROM
Apr 17 13:36:04 Pyrope kernel: [  104.810515] nouveau  [   VBIOS][0000:02:00.0] BIT signature found
Apr 17 13:36:04 Pyrope kernel: [  104.810636] nouveau  [   VBIOS][0000:02:00.0] version 62.77.2f.00.06
Apr 17 13:36:04 Pyrope kernel: nouveau  [   VBIOS][0000:02:00.0] version 62.77.2f.00.06
Apr 17 13:36:04 Pyrope kernel: [  104.814419] nouveau E[   VBIOS][0000:02:00.0] 0xc9c7[ ]: unknown opcode 0x00
Apr 17 13:36:04 Pyrope kernel: [  104.814543] nouveau E[ DEVINIT][0000:02:00.0] init failed, -22
Apr 17 13:36:04 Pyrope kernel: [  104.814659] nouveau E[     DRM] failed to create 0x80000080, -22
Apr 17 13:36:04 Pyrope kernel: nouveau E[   VBIOS][0000:02:00.0] 0xc9c7[ ]: unknown opcode 0x00
Apr 17 13:36:04 Pyrope kernel: nouveau E[ DEVINIT][0000:02:00.0] init failed, -22
Apr 17 13:36:04 Pyrope kernel: nouveau E[     DRM] failed to create 0x80000080, -22
Apr 17 13:36:04 Pyrope kernel: [  104.820131] nouveau: probe of 0000:02:00.0 failed with error -22
Apr 17 13:36:04 Pyrope kernel: nouveau: probe of 0000:02:00.0 failed with error -22

On Thu, Apr 17, 2014 at 1:29 PM, Kevin Martin <ktmdms@xxxxxxxxx> wrote:

On 04/17/2014 01:26 PM, Steven Usdansky wrote:
> Not sure where to report this problem (or what I should be looking for), but when booting any of the 3.15 kernels,

> kernel-modesetting fails and X comes up with a resolution of  1024x768, rather than the 1680x1050 resolution specified in my

> xorg.conf file. xorg.conf is necessary because my monitor does not emit a proper EDID.
>
> ~$ uname -r
> kernel-3.15.0-0.rc1.git1.1.fc21.x86_64
> ~$ lspci | grep 9100
> 02:00.0 VGA compatible controller: NVIDIA Corporation C78 [GeForce 9100] (rev a2)
>
> Reverting to kernel -3.13.7-200.fc20.x86_64 avoids the problem (and problems I've been having with firefox-28 locking up with 3.14
> kernels).
>
> --
> RockDoctor
>
>

Oh good, I'm not the only one having these problems (modesetting AND firefox lockups).  I find that if I (modprobe nouveau
modeset=1) as root or sudo after logging in from a terminal and before running X I get the proper resolution, but the firefox
lockups are definitely a pain.  I'm on 3.15.0-0.rc0.git9.1.fc21.x86_64.

Kevin
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test