search for: vbioses

Is there any method to dump vbioses of NVIDIA Pascal cards(not use nvflash), such as P100/P4? I used nvagetbios, but it just report a error "Card has second bios", what does this mean? Thanks, Zongyong Wu -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/arc...

On Sat, Aug 31, 2013 at 9:58 AM, Martin Peres <martin.peres at free.fr> wrote: > From: Martin Peres <martin.peres at labri.fr> > > Some vbioses have extra useless entries after "the end" of the table. This is > problematic since all of the vbios I found with this issue redefine the > pwm freq divider to insane levels (52750 Hz instead of 2500), thus breaking > fan management. > > The first solution to solve this me...

From: Martin Peres <martin.peres at labri.fr> Some vbioses have extra useless entries after "the end" of the table. This is problematic since all of the vbios I found with this issue redefine the pwm freq divider to insane levels (52750 Hz instead of 2500), thus breaking fan management. The first solution to solve this mess would be to change th...

...e two things are unrelated. The PCIR section is normally embedded in the vbios and tells you how long the vbios is, and allows you to have multiple elements appended at the end (which nouveau has recently acquired some support for). The checksum failures just happen, pretty sure that the OF-sourced vbioses just don't have a checksum byte at all. And they cause nouveau to try to load a vbios from a different source, which almost invariably fails to actually parse properly. (Why? Because you should just use the one from OF, duh!) -ilia

On Fri, 20 Mar 2009 00:06:39 -0500 Jason Detring <detringj at gmail.com> wrote: > Speaking of contributing, would you like a tester for Nouveau on > SPARC64? I have access to an Ultra 45 and a pair of PCI boards (TnT2, > GeForce 6200, both with x86 VBIOSes unfortunately). I don't own any > PCI-E boards yet, but that can change if there's interest. I have no idea about non-x86/ppc support. Anyone? -- Pekka Paalanen http://www.iki.fi/pq/

Hi Nouveau developers, We've posted a short document about disabling display underflow reporting on GK104, which is needed due to an incorrect setting in some production GK104 VBIOSes: ftp://download.nvidia.com/open-gpu-doc/gk104-disable-underflow-reporting/1/gk104-disable-underflow-reporting.txt Thanks, - Andy

Some, mostly Fermi, vbioses appear to have zero max voltage. That causes Nouveau to not parse voltage entries, thus users not being able to set higher clocks. When changing this value Nvidia driver still appeared to ignore it, and I wasn't able to find out why, thus the code is ignoring the value if it is zero. CC: Maar...

...s, and sets the size of the vbios.rom debugfs file so that nvbios can easily be used to parse the vbios even on systems where the normal BIOS retrieval methods (for example, laptops that need ACPI to access the vbios for the nvidia GPU) won't work. This should make it a little easier to collect vbioses. Lyude Paul (2): drm/nouveau: Add strap_peek to debugfs drm/nouveau: Add size to vbios.rom file in debugfs drivers/gpu/drm/nouveau/nouveau_debugfs.c | 46 ++++++++++++++++++++--- 1 file changed, 41 insertions(+), 5 deletions(-) -- 2.17.1

...or an on-board small microcontroller which provides certain security assertions (the 'PMU'). This system allows a GPU programming sequence to be shared by multiple entities that would not otherwise be able to execute common code. This series adds support to nouveau for two opcodes seen on VBIOSes prior to the locked-down PMU taking over responsibility for executing devinit scripts. Documentation for these two opcodes can be found at: https://github.com/envytools/envytools/pull/189 Rhys Kidd (2): drm/nouveau/bios/init: handle INIT_RESET_BEGUN devinit opcode drm/nouveau/bios/init: ha...

Hello, Some users have been complaining for years about their GPU sounding like a jet engine at take off. Last year, I finally laid my hand on one of these GPUs and have been trying to fix this issue on and off since then. After failing to find anything in the HW, I figured out that the duty cycle set by nvidia's proprietary driver would be way under the expected value. By randomly changing

Hi List, I'm stuck how to get a dual head monitor solution to work with Nouveau, running openSUSE 13.1 on my hp8710w mobile workstation equipped with a Nvidia graphical card. Beyond the built-in WUXGA display, an external WQHD monitor is connected to the HDMI port on the graphical card and/or to the dual link DVI-D on a hp docking station. To compare with SLED11/Nvidia driver running in

Turns out some VBIOSes don't actually set the bit in question in 2240c. Use the nv50-style detection to try avoiding running the vbios twice. Fixes: a6a0f67ca7aa ("drm/nouveau/devinit/gf100-: detect if BIOS invoked devinit") Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97620 Cc: stable at vger.ke...

Turns out some VBIOSes don't actually set the bit in question in 2240c. Use the nv50-style detection to try avoiding running the vbios twice. Fixes: a6a0f67ca7aa ("drm/nouveau/devinit/gf100-: detect if BIOS invoked devinit") Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=97620 Cc: <stable at vge...

From: Mark Menzynski <mmenzyns at redhat.com> [ Upstream commit a1af2afbd244089560794c260b2d4326a86e39b6 ] Some, mostly Fermi, vbioses appear to have zero max voltage. That causes Nouveau to not parse voltage entries, thus users not being able to set higher clocks. When changing this value Nvidia driver still appeared to ignore it, and I wasn't able to find out why, thus the code is ignoring the value if it is zero. CC: Maar...

From: Mark Menzynski <mmenzyns at redhat.com> [ Upstream commit a1af2afbd244089560794c260b2d4326a86e39b6 ] Some, mostly Fermi, vbioses appear to have zero max voltage. That causes Nouveau to not parse voltage entries, thus users not being able to set higher clocks. When changing this value Nvidia driver still appeared to ignore it, and I wasn't able to find out why, thus the code is ignoring the value if it is zero. CC: Maar...

From: Mark Menzynski <mmenzyns at redhat.com> [ Upstream commit a1af2afbd244089560794c260b2d4326a86e39b6 ] Some, mostly Fermi, vbioses appear to have zero max voltage. That causes Nouveau to not parse voltage entries, thus users not being able to set higher clocks. When changing this value Nvidia driver still appeared to ignore it, and I wasn't able to find out why, thus the code is ignoring the value if it is zero. CC: Maar...

From: Mark Menzynski <mmenzyns at redhat.com> [ Upstream commit a1af2afbd244089560794c260b2d4326a86e39b6 ] Some, mostly Fermi, vbioses appear to have zero max voltage. That causes Nouveau to not parse voltage entries, thus users not being able to set higher clocks. When changing this value Nvidia driver still appeared to ignore it, and I wasn't able to find out why, thus the code is ignoring the value if it is zero. CC: Maar...

...M64 works fine (or at least did recently, I think I last tested after 3.10 or so). Another user's NV04 also worked OK on linux-3.9 (from bug 68854), although it was the Creative Labs one. However he also had the resolution issue (maxing out at 1024x768). You have one of the (infamous?) BMP v0 vbioses, may be interesting to attach it to this bug, although I sincerely doubt that is the source of the issues (before BMP v2 or so, we just ignore it entirely). Without nouveau loaded, you can get it from /sys/kernel/debug/dri/0/vbios.rom . The unfortunate reality here is that you are in posession of...

The important thing for display detection/setting proper modes/etc is the kernel -- what kernel version are you using? Separately, there has been a fix that affected VBIOSes found in NV96 cards, and it would not be a stretch to believe that a similar VBIOS script could be found in a NV92 card. However the NV96 error condition was different (everything detected fine, but no actual image displayed, whereas for you it's not even showing anything as connected, which co...

...years about their GPU sounding like > a jet engine at take off. Last year, I finally laid my hand on one of > these GPUs and have been trying to fix this issue on and off since then. Some early feedback: can you tell us the exact SKUs you have? And are these production boards with production VBIOSes? Normally, it's just our bringup boards that we'd expect to be noisy like this, so we're looking for a few more details. thanks, John Hubbard NVIDIA > > After failing to find anything in the HW, I figured out that the duty > cycle set by nvidia's proprietary driver w...