Yes, it works without the workaround... and thanks for the suspend patch
which works fine as well :-)
On 05.04.2014 18:18, Ilia Mirkin wrote:
> On Sat, Apr 5, 2014 at 7:53 AM, Claas Lorenz
> wrote:
>> Hi, same for me. The screen does not freeze anymore and the boot
> Great! And that's without th
Hi, same for me. The screen does not freeze anymore and the boot
succeeds. But now I have this kernel message during boot (for the second
card):
[ 24.382045] pci_pm_runtime_suspend():
nouveau_pmops_runtime_suspend+0x0/0xe0 [nouveau] returns -22
Do you want to have the complete dmesg log? I thin
On Sat, Apr 5, 2014 at 7:53 AM, Claas Lorenz wrote:
> Hi, same for me. The screen does not freeze anymore and the boot
Great! And that's without the nouveau.config=NvBios= stuff that you
added as a workaround, right?
> succeeds. But now I have this kernel message during boot (for the second
> ca
I have tested this patch. I can confirm that now nouveau loads
correctly without errors.
Thank you
2014-03-27 0:37 GMT+01:00 Ilia Mirkin :
> There appear to be a crop of new hardware where the vbios is not
> available from PROM/PRAMIN, but there is a valid _ROM method in ACPI.
> The data read from
On Thu, Mar 27, 2014 at 9:37 AM, Ilia Mirkin wrote:
> There appear to be a crop of new hardware where the vbios is not
> available from PROM/PRAMIN, but there is a valid _ROM method in ACPI.
> The data read from PCIROM almost invariably contains invalid
> instructions (still has the x86 opcodes),
There appear to be a crop of new hardware where the vbios is not
available from PROM/PRAMIN, but there is a valid _ROM method in ACPI.
The data read from PCIROM almost invariably contains invalid
instructions (still has the x86 opcodes), which makes this a low-risk
way to try to obtain a valid vbio
