https://bugs.freedesktop.org/show_bug.cgi?id=46557
--- Comment #17 from Salah Coronya <salah.coro...@gmail.com> 2012-06-17 13:12:54 PDT --- The above "workaround" works. Framebuffer is OK, X is good, glxgears runs without having to specify mem=2G (this is against the nouveau git). I think it is buggy hardware - its just the blob and Windows driver know about it and only do 31-bit DMA (or maybe they just get lucky). Attempting to set dma_bits=31 in nouveau_vram_init cause nouveau_sgdma_init to mail to map the page, and attempting to allocate a suitable page using pci_alloc_consistent / dna_alloc_coherent or alloc_page GFP_DMA flag causes BUGs and paging faults. If I specify if I specify both nouveau.vram_pushbuf=1 AND nouveau.vram_notify=1 (just one alone does not work), it "soft of" works without mem=2G. The framebuffer is OK. X is still distorted but not as badly and isn't locked up, and the dmesg is no longer filled with errors, but glxgears does not work (it doesn't crash but just shows crazy flashing triangles). -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
