<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Screen freezes during boot with an 3.13 kernel (Arch Linux)" href="https://bugs.freedesktop.org/show_bug.cgi?id=75511#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Screen freezes during boot with an 3.13 kernel (Arch Linux)" href="https://bugs.freedesktop.org/show_bug.cgi?id=75511">bug 75511</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>Am I correct that you have 2 ~identical GK107 cards in there? Unfortunately it appears that the VBIOS for the first one is corrupt. It's being retrieved from PCIROM, which more often than not actually doesn't have what we want (despite it passing the checksum). Note that your 2nd card appears to init correctly, and it gets its VBIOS from the PROM. Not sure where the VBIOS for your first card lives... I assume that the VBIOS error about the unknown opcode exists in 3.12 as well? Except that 3.13 made that an error. Who knows, maybe it's a legitimately unknown opcode... could you grab a copy of envytools and retrieve the VBIOSes for both of your cards with nvagetbios? i.e. nvagetbios -c 0 -s PROM > vbios-0.rom nvagetbios -c 1 -s PROM > vbios-1.rom If the first one fails, also try PRAMIN instead of PROM (I assume -c 1 will work just fine since nouveau is able to find it without problem). If that still fails, try to get it from the pci rom directly: echo 1 > /sys/bus/pci/devices/0000:01:00.0/rom cat /sys/bus/pci/devices/0000:01:00.0/rom > vbios-0.rom echo 0 > /sys/bus/pci/devices/0000:01:00.0/rom (all of this as root, obviously.)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>