search for: pramin

...464&action=edit system logs Description of problem: Kernel regression: the system uses VESA due the following error in /var/log/Xorg.0.log (EE) [drm] KMS not enabled with older kernel 3.11.10-301 the bug did not happen. I also tried booting the system with option "nouveau.config=VBIOS=PRAMIN" but it did not solve the problem. ===Kernel Version=== kernel-3.16.2-200.fc20.x86_64 ===Fedora bugreport=== https://bugzilla.redhat.com/show_bug.cgi?id=1141898 -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachm...

From: Andrea Tacconi <tacconet at libero.it> Subject: [PATCH] drm/nouveau: fix vbios load and check functions on PowerPC On PowerPC the Bios signature reports a wrong lenght of video rom. Fix this by reading the correct size from Open Firmware. Set Pramin as primary vbios searching method, because it's the only working method on PowerPC. The nv_cksum function always fails. Fix this by Calculating and adding checksum byte at the end of vbios. Signed-off-by: Andrea Tacconi <tacconet at libero.it> --- diff --git a/drivers/gpu/drm/nouveau/no...

....0] BOOT0 : 0x049800a2 Mar 25 11:50:53 ivnb kernel: [ 2703.329293] nouveau [ DEVICE][0000:01:00.0] Chipset: G71 (NV49) Mar 25 11:50:53 ivnb kernel: [ 2703.329298] nouveau [ DEVICE][0000:01:00.0] Family : NV40 Mar 25 11:50:53 ivnb kernel: [ 2703.333377] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... Mar 25 11:50:53 ivnb kernel: [ 2703.433876] nouveau [ VBIOS][0000:01:00.0] ... checksum invalid Mar 25 11:50:53 ivnb kernel: [ 2703.433882] nouveau [ VBIOS][0000:01:00.0] checking PROM for image... Mar 25 11:50:53 ivnb kernel: [ 2703.433896] nouveau [ VBIOS][0000:01:00.0] .. . si...

-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.freedesktop.org/archives/nouveau/attachments/20090216/4db7f810/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: pramin_more_flush.diff Type: application/octet-stream Size: 2741 bytes Desc: not available Url : http://lists.freedesktop.org/archives/nouveau/attachments/20090216/4db7f810/attachment.obj

...ice not found 1 0 1 > [ 0.282688] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046800a3 > [ 0.282693] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) > [ 0.282696] nouveau [ DEVICE][0000:01:00.0] Family : NV40 > [ 0.284293] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... > [ 0.366261] nouveau [ VBIOS][0000:01:00.0] ... checksum invalid > [ 0.366266] nouveau [ VBIOS][0000:01:00.0] checking PROM for image... > [ 0.366279] nouveau [ VBIOS][0000:01:00.0] ... signature not found > [ 0.366283] nouveau [ VBIOS][0000:01:00.0...

...when enter on vt vas unable to use numbers from NumLock an only numbers from main keyboard. nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046f00a3 nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46) nouveau [ DEVICE][0000:01:00.0] Family : NV40 nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... nouveau [ VBIOS][0000:01:00.0] ... appears to be valid nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN nouveau [ VBIOS][0000:01:00.0] BIT signature found nouveau [ VBIOS][0000:01:00.0] version 05.72.22.43.00 -------------- next part -------------- A non-text attach...

...; Mar 25 11:50:53 ivnb kernel: [ 2703.329293] nouveau [ DEVICE][0000:01:00.0] > Chipset: G71 (NV49) > Mar 25 11:50:53 ivnb kernel: [ 2703.329298] nouveau [ DEVICE][0000:01:00.0] > Family : NV40 > Mar 25 11:50:53 ivnb kernel: [ 2703.333377] nouveau [ VBIOS][0000:01:00.0] > checking PRAMIN for image... > Mar 25 11:50:53 ivnb kernel: [ 2703.433876] nouveau [ VBIOS][0000:01:00.0] > ... checksum invalid > Mar 25 11:50:53 ivnb kernel: [ 2703.433882] nouveau [ VBIOS][0000:01:00.0] > checking PROM for image... > Mar 25 11:50:53 ivnb kernel: [ 2703.433896] nouveau [ VBIOS]...

...t; [ 7.569394] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x0ac080b1 > > [ 7.569460] nouveau [ DEVICE][0000:02:00.0] Chipset: MCP79/MCP7A (NVAC) > > [ 7.569530] nouveau [ DEVICE][0000:02:00.0] Family : NV50 > > [ 7.571151] nouveau [ VBIOS][0000:02:00.0] checking PRAMIN for image... > > [ 7.633082] nouveau [ VBIOS][0000:02:00.0] ... appears to be valid > > [ 7.633155] nouveau [ VBIOS][0000:02:00.0] using image from PRAMIN > > [ 7.633468] nouveau [ VBIOS][0000:02:00.0] BIT signature found > > [ 7.633533] nouveau [ VBI...

...ars to not be using the drm driver. Platform: Alpine Linux 3.10.1 Standard, kernel 4.19.58 (non-verbose log) Tiny Core Linux, kernel 4.19.10 (verbose external module log) I tried using the kernel parameter nouveau.config=NvMSI=0, but it made no difference. I also tried using nouveau.config=NvBios=PRAMIN, even though there were no "checksum invalid" errors in the dmesg output. I was unable to get a VBIOS dump, as the /sys/kernel/debug/dri folder was empty. I was also hesitant to do a git bisection, as compiling the nouveau kernel module takes upwards of 7 hours on the machine I am using...

On Tue, Feb 17, 2015 at 5:48 PM, Alexandre Courbot <acourbot at nvidia.com> wrote: > instmem for GK20A is allocated using dma_alloc_coherent(), which > provides us with a coherent CPU mapping that we never use because > instmem objects are accessed through PRAMIN. Switch to > dma_alloc_attrs() which gives us the option to dismiss that CPU mapping > and free up some CPU virtual space. > > Signed-off-by: Alexandre Courbot <acourbot at nvidia.com> > --- > drm/nouveau/nvkm/subdev/instmem/gk20a.c | 24 ++++++++++++++++++++---- > lib/i...

...d ;) >> > But why didn't you call it Dumb mode rather that Deep mode. That way, > I wouldn't have tried to use it and figure out what it does. ;p Target is supposed to be higher than initial! Initial == minimum safe timing. You just reversed the order, try: sudo nvamemtiming pramin 0x6a22 5 0 -d 3

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 M...

...ddress> <value>: like nvapoke, but repeats the write in > -an infinite loop. Needs to be manually aborted. > - > -nvagetbios [-s <extraction method>]: extracts the card's VBIOS using the > -method given as parameter and writes it to stdout. Method can be PROM or > -PRAMIN. If method is not given, defaults to something sensible. > - > -nvafuzz <address> [<byte count>]: writes random values to a register or > -a register range in an infinite loop. Needs to be manually aborted. > - > -nvascan [-as] <address> [<byte count>]: for ea...

...terrupt Link [LNK5] enabled at IRQ 16 [ 154.754844] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x01a000b1 [ 154.761111] nouveau [ DEVICE][0000:02:00.0] Chipset: nForce (NV1A) [ 154.767534] nouveau [ DEVICE][0000:02:00.0] Family : NV10 [ 154.773918] nouveau [ VBIOS][0000:02:00.0] checking PRAMIN for image... [ 154.832093] nouveau [ VBIOS][0000:02:00.0] ... appears to be valid [ 154.838624] nouveau [ VBIOS][0000:02:00.0] using image from PRAMIN [ 154.845146] nouveau [ VBIOS][0000:02:00.0] BMP version 5.14 [ 154.851300] nouveau [ VBIOS][0000:02:00.0] version 03.1a.01.03.00 [...

...rather that Deep mode. That >>> way, I wouldn't have tried to use it and figure out what it does. ;p >> >> Target is supposed to be higher than initial! Initial == minimum safe >> timing. >> >> You just reversed the order, try: >> sudo nvamemtiming pramin 0x6a22 5 0 -d 3 >> > Ok. It's intended then. Thanks! I totally agree that this tool is a little confusing. If you have suggestions on how to improve the usage doc, feel free to propose me something better :) fprintf(stderr, "\t-d timing_entry_high: For each indexes, iterate b...

...] [drm] Initialized drm 1.1.0 20060810 [ 0.623272] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x0c4100a1 [ 0.623274] nouveau [ DEVICE][0000:01:00.0] Chipset: GF104 (NVC4) [ 0.623275] nouveau [ DEVICE][0000:01:00.0] Family : NVC0 [ 0.623307] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image... [ 0.716983] nouveau [ VBIOS][0000:01:00.0] ... appears to be valid [ 0.716985] nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN [ 0.717075] nouveau [ VBIOS][0000:01:00.0] BIT signature found [ 0.717076] nouveau [ VBIOS][0000:01:00.0] version 70.04.1b.00.02...

...file base.c if (nv_rd08(bios, 0x700000) != 0x55 || nv_rd08(bios, 0x700001) != 0xaa) { It means that the address reading of 0x700000 results the kernel crash. Why does it happen? The result of the address reading of 0x619f04 is shown for the information. static void nouveau_bios_shadow_pramin(struct nouveau_bios *bios) { struct nouveau_device *device = nv_device(bios); u32 bar0 = 0; int i; unsigned int tmp_val; if (device->card_type >= NV_50) { u64 addr = (u64)(nv_rd32(bios, 0x619f04) & 0xffffff00) << 8; if (!addr) { addr...

...9394] nouveau [ DEVICE][0000:02:00.0] BOOT0 : 0x0ac080b1 >> > [ 7.569460] nouveau [ DEVICE][0000:02:00.0] Chipset: MCP79/MCP7A (NVAC) >> > [ 7.569530] nouveau [ DEVICE][0000:02:00.0] Family : NV50 >> > [ 7.571151] nouveau [ VBIOS][0000:02:00.0] checking PRAMIN for image... >> > [ 7.633082] nouveau [ VBIOS][0000:02:00.0] ... appears to be valid >> > [ 7.633155] nouveau [ VBIOS][0000:02:00.0] using image from PRAMIN >> > [ 7.633468] nouveau [ VBIOS][0000:02:00.0] BIT signature found >> > [ 7.633533]...

...fan has been added to 3.15, and indeed it seems to be recognized now (many thanks for that!). I?m attaching my dmesg and my vbios in case it helps. Note though that nvagetbios reported a warning when dumping the BIOS: > No extraction method specified (using -s extraction_method). Defaulting to PRAMIN. > Attempt to extract the vbios from card 0 (nve6) using PRAMIN > Invalid signature(0x55aa). You may want to try another retrieval method. Let me know if there?s additional information I could supply. -- You are receiving this mail because: You are the assignee for the bug. --------------...

1 patch for libnouveau_drm, 4 for drm and one work in progress patch for the ddx. Getting nv50 to run proved to be more difficult than i thought (at some point i stopped because it would require significant changes), i just have a few remarks. - Buffer object access is not guarded by fences at all, which is a major issue. You worked around that by using M2MF I suppose, but this needs a