similar to: [Bug 97620] New: [REGRESSION] KMS having issues after kernel upgrade (4.5.1-1 to 4.6.4-1)

It is not advisable to perform devinit if it has already been done. VBIOS will very likely have invoked devinit if the GPU is the primary graphics device, but there is no accurate way to detect this fact yet. This patch adds such a method for gf100 and later chips, by means of the NV_PTOP_SCRATCH1_DEVINIT_COMPLETED bit. This bit is set to 1 by devinit, and reset to 0 when the GPU is powered.

NVIDIA GPUs include a common scripting language (devinit) that can be interpreted by a number of "engines", e.g. within a kernel-mode software driver, the VGA BIOS 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

No problem. I applied the patch (plus the other for the MXM issue), replaced the preexisting nouveau.ko.gz in /lib/mod/? with the new gzipped one, and rebuilt the initramfs. (With an updated DRIVER_DATE define just to be sure.) The HDMI output works fine. Attached are the dmesg outputs before and after, grepped for 'nouveau'. As you can see, there's no real change. On Sun, Jan 19,

I have searched the internet, and have tried some things I have found, but cannot resolve my issue. Hoping to find some help here. I have a peer to peer network static IP on all workstations, approximately 100 computers running Windows XP pro, and Windows 2000 pro. My desktop, Ubuntu, and one Linux Server, running Red Hat 9. The RH9 machine has Samba v2.27 running as WINS. It is set as

Also make nv_lockvgac work for nv50+ devices. This should fix IO_CONDITION and related VBIOS opcodes that read/write the crtc regs. See https://bugs.freedesktop.org/show_bug.cgi?id=60680 Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Ben, is this what you had in mind? I haven't gotten a chance to test this yet since your tree doesn't build against mine (which is largely

https://bugs.freedesktop.org/show_bug.cgi?id=56461 Priority: medium Bug ID: 56461 Assignee: nouveau at lists.freedesktop.org Summary: NV11 black screen & kernel hang on loading nouveaufb QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: chris at

Hi again, I got a new dmesg log with the debug parameters, but I guess I could not isolate VESA. I blacklisted it at /etc/modprobe.d/blacklist.conf but comparing those logs I see no difference... Is it possible to isolate VESA somehow without removing it? The new logs are here, I'm posting full content because I'm not sure what information is more relevant...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- I decided to let the user still specify config=BLA=1 to override the hw disable in case we get something wrong or for double-checking stuff, but I suspect it won't really be used much. I'm not terribly fond of the message text, if you come up with something better, feel free to drop it in.

Hi! I have a rather decent notebook (Toshiba Satellite P105-S9722) with Nvidia GeForce Go 7900 GS video card. I installed latest debian system with kernel 3.13-1-amd64 on it, but unfortunately nouveau driver doesn't work. When I load nouveau module following messages will appear in syslog: Mar 25 11:50:53 ivnb kernel: [ 2703.329287] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x049800a2

On 9 February 2014 02:57, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Sat, Feb 8, 2014 at 10:38 AM, Daniel J Blueman <daniel at quora.org> wrote: >> Interestingly, there was graphical failure booting 3.6.11, even >> nvidia-current fails to initialise, but these two issues could be due >> to running the Xorg stack in Ubuntu 14.04 pre-release. Using >>

https://bugs.freedesktop.org/show_bug.cgi?id=60680 Priority: medium Bug ID: 60680 Assignee: nouveau at lists.freedesktop.org Summary: HDMI is connected and has mode, TV says "no signal" QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

On 12/02/14 05:38, Alexandre Courbot wrote: > Upcoming mobile Kepler GPUs (such as GK20A) use the platform bus instead > of PCI to which Nouveau is tightly dependent. This patch allows Nouveau > to handle platform devices by: > > - abstracting PCI-dependent functions that were typically used for > resource querying and page mapping, > - introducing a nv_device_is_pci()

On Thu, Nov 29, 2018 at 12:21:31AM +0100, Karol Herbst wrote: > this was already debugged and there is no point in searching inside > the Firmware. It's not a firmware bug or anything. > > The proper fix is to do something inside Nouveau so that we don't > upset the device and being able to runtime resume it again. > > The initial thing we do inside Nouveau to cause

Hello everyone, The code is at /core/subdev/bios/init.c. When the executable is 0,these functions that parse the VBIOS init table seems to do nothing except the parsing. And in my opinion,init_exec_force does nothing,too! Then I tried to test it on my computer,when the VBIOS parser tries to change a MMIO register or call a function of struct nouveau_devinit (such as devinit->pll_set,etc.),it

On Mon, Feb 10, 2014 at 8:50 PM, Thierry Reding <thierry.reding at gmail.com> wrote: > On Mon, Feb 10, 2014 at 02:53:00PM +0900, Alexandre Courbot wrote: > [...] >> diff --git a/drivers/gpu/drm/nouveau/core/engine/device/base.c b/drivers/gpu/drm/nouveau/core/engine/device/base.c > [...] >> +resource_size_t >> +nv_device_resource_start(struct nouveau_device *device,

http://bugs.freedesktop.org/show_bug.cgi?id=23223 Summary: Regression: Nvidia Geforce 7300 (NV4B) fails to suspend Product: xorg Version: 7.2 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

CCing linux-pci and Bjorn Helgaas. Maybe we could get better insights on how a reasonable fix would look like. Anyway, to me this entire issue looks like something which has to be fixed on a PCI level instead of inside a driver, so it makes sense to ask the pci folks if they have any better suggestions. Original cover letter: While investigating the runpm issues on my GP107 I noticed that

https://bugs.freedesktop.org/show_bug.cgi?id=88868 Bug ID: 88868 Summary: PowerPC e5500, kernel crash, GT520, GT610 Product: xorg Version: unspecified Hardware: PowerPC OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

System was booted with PCI graphics card first in VGA text mode. Loading nouveau from there on causes the following BUG, after what kernel produces trace over trace until overflowing its stack. (trace captured via netconsole) [ 154.323717] wmi: Mapper loaded [ 154.735793] nouveau 0000:02:00.0: enabling device (0004 -> 0006) [ 154.743189] ACPI: PCI Interrupt Link [LNK5] enabled at IRQ 16 [

The INA3221 is usually found on mid and high end kepler+ gpus Marins Patch implements the new iccsense subdev and all needed bits for the INA3221 power sensor. My Patch implements the hwmon power1 interface to expose the current power consumption through hwmon (and can be read out via sysfs or the sensors tool) Please test these patches for Fermi+ GPUs, that nothing gets messed up and works as