search for: _rom

https://bugs.freedesktop.org/show_bug.cgi?id=98240 Bug ID: 98240 Summary: Kernel module fails to load on HP Pavilion V3A33AV laptop. Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=93778 Bug ID: 93778 Summary: Noveau GeForce GT 640M vbios error Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=99372 Bug ID: 99372 Summary: Nvidia 640M devinit fails Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

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 vbios image. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76475 Signed-off-by: Ilia Mirkin <imirkin at alum.m...

https://bugs.freedesktop.org/show_bug.cgi?id=90626 Bug ID: 90626 Summary: HP ZBook 15 nouveau driver hangup for kernel >= 3.19 Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee:

...ch. I can confirm that now nouveau loads > correctly without errors. > Thank you > > 2014-03-27 0:37 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: >> 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 vbios image. >> >> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76475 >...

https://bugs.freedesktop.org/show_bug.cgi?id=55948 Priority: medium Bug ID: 55948 Assignee: nouveau at lists.freedesktop.org Summary: [nvd9 optimus] drm/nouveau/bios: attempt to fetch entire acpi rom image in one shot breaks module load QA Contact: xorg-team at lists.x.org Severity: major Classification:

On Tue, Aug 28, 2018 at 5:57 PM, Peter Wu <peter at lekensteyn.nl> wrote: > Just to be sure, after "sleep", do both devices report "suspended" in > /sys/bus/pci/devices/0000:00:1c.0/power/runtime_status > /sys/bus/pci/devices/0000:01:00.0/power/runtime_status > > and was this reproduced with a recent mainline kernel with no special > cmdline options? The

...ow nouveau loads >> correctly without errors. >> Thank you >> >> 2014-03-27 0:37 GMT+01:00 Ilia Mirkin <imirkin at alum.mit.edu>: >>> 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 vbios image. >>> >>> Bugzilla: https://bugs.freedesktop.org/show_b...

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 <imirkin at alum.mit.edu>: > 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 vbios image. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=76475 > Signed-off-by: Ilia...

...veau 0000:01:00.0: ... BIOS signature not found [ 2.705610] [drm] nouveau 0000:01:00.0: Checking ACPI for VBIOS [ 2.705666] ACPI Error: Field [ROMI] Base+Offset+Width 0+24+1 is beyond end of region VROM (20120320/exfldio-210) [ 2.705670] ACPI Error: Method parse/execution failed _SB_.PCI0.PEG0.GFX0._ROM, AE_AML_REGION_LIMIT (20120320/psparse-536) [ 2.759759] failed to evaluate ROM got AE_AML_REGION_LIMIT [ 2.759761] [drm] nouveau 0000:01:00.0: ... BIOS signature not found [ 2.759763] [drm] nouveau 0000:01:00.0: Checking PCIROM for VBIOS [ 2.759894] nouveau 0000:01:00.0: Invalid ROM contents [ 2.76...

Hi, On Thu, Jun 18, 2020 at 04:19:02PM -0400, Ilia Mirkin wrote: > Hi Boris, > > There was a fixup to that patch that you'll also have to revert first > -- 7dbbdd37f2ae7dd4175ba3f86f4335c463b18403. I guess there's some > subtle difference between the old open-coded logic and the helper, > they were supposed to be identical. Thanks, that's a good point. I reverted

https://bugs.freedesktop.org/show_bug.cgi?id=103033 Bug ID: 103033 Summary: nouveau can't start my discrete nvidia card (BIOS / ACPI error) Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=76475 Priority: medium Bug ID: 76475 Assignee: nouveau at lists.freedesktop.org Summary: Nouveau fails to load due to unknown opcode 0x80 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: patrick.clara at

...raphics driver could not find compatible graphics hardware. > > One trick for similar sounding problems is to change hypervisor vendor > ID but no luck here. For laptops, it appears that you have to do at least two things: - Ensure that the Subsystem Vendor/Product ID are set. - Expose a _ROM ACPI method that provides VBIOS. Perhaps you also need to provide a "_DSM" method that emulates at least the "Optimus" interface for GUID a486d8f8-0bda-471b-a72b-6042a6b5bee0. You probably lost interest here, but if you want to continue anyway this is what allowed me to instal...

On Tue, Aug 28, 2018 at 5:57 PM, Peter Wu <peter at lekensteyn.nl> wrote: > Only non-bridge devices can be passed to a guest, but perhaps logging > access to the emulated bridge is already sufficient. The Prefetchable > Base Upper 32 Bits register is at offset 0x28. > > In a trace where the Nvidia device is disabled/enabled via Device > Manager, I see writes on the enable