[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #17 from bmaass bma...@math.uni-bremen.de 2009-02-13 02:32:16 PST --- Created an attachment (id=22894) -- (http://bugs.freedesktop.org/attachment.cgi?id=22894) randr12 and patches register dump Patch 0001 didn't do anything visibly, patch 0002 fixes the problem (more in a second) and I couldn't see if patch 0003 improved anything over 0002. The fix is that I finally get a picture (can see xterms, xclock, interact with them), but it's still horribly wrong somehow. Looks like the picture is missing vertical lines, but somehow still not everywhere (TWM resize lines may disappear, but there are no gaps in the windows themselves). This is consistent over all modes I've tried (2560x1600, 1920x1200, 1280x800) and doesn't show up on a screenshot. It also doesn't get restored back to normal when quitting the X server: the brokenness remains when using the console afterwards. -- Configure bugmail: http://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
[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #18 from Stuart Bennett sb...@cam.ac.uk 2009-02-13 03:12:12 PST --- (In reply to comment #17) Created an attachment (id=22894) -- (http://bugs.freedesktop.org/attachment.cgi?id=22894) [details] randr12 and patches register dump Thanks. Some quick questions to help in making the next patch, and some other things to try in the future: This register dump is with all three patches, or just the first two? Patch 0001 didn't do anything visibly, patch 0002 fixes the problem (more in a second) and I couldn't see if patch 0003 improved anything over 0002. Just to clarify, you tried 0003 on top of 0002, but could see no difference? The fix is that I finally get a picture (can see xterms, xclock, interact with them), but it's still horribly wrong somehow. Looks like the picture is missing vertical lines, but somehow still not everywhere (TWM resize lines may disappear, but there are no gaps in the windows themselves). Hmm, might be interesting to see a picture should you have a digital camera, but don't worry if it's not convenient. This is consistent over all modes I've tried (2560x1600, 1920x1200, 1280x800) and doesn't show up on a screenshot. It also doesn't get restored back to normal when quitting the X server: the brokenness remains when using the console afterwards. Is it worse than the picture degradation (bad resolution?) which isn't recovered even when killing X you mentioned previously, or the same? One other thing that would be interesting to know next time you test (using a clean checkout (no patches)), if you add `Option FPScale off' in the driver section of your xorg.conf, and set 1280x800, whether that works any better. -- Configure bugmail: http://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
Re: [Nouveau] [PATCH 3/3] nv50: support frontbuffer fallbacks
These patches are workarounds, and therefore will not be applied to git. I made them out of curiosity. Maarten. On Fri, Feb 13, 2009 at 10:19 AM, Hervé Cauwelier herve.cauwel...@free.fr wrote: Maarten Maathuis a écrit : [snip] I can't tell you about the technical quality of this patch but it made my day. When I saw frontbuffer I thought about my bug #20066 and applied your three patches in another branch. Gnome-terminal is now fast as expected, with the nouveau module loaded. It will be fine enough for me now. I'll report if it crashes. Notice that the second patch contains white space. Hervé ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #19 from bmaass bma...@math.uni-bremen.de 2009-02-13 05:21:59 PST --- (In reply to comment #18) (In reply to comment #17) This register dump is with all three patches, or just the first two? All three. Do you want one with just 1+2? Just to clarify, you tried 0003 on top of 0002, but could see no difference? Exactly. I started seeing something with 1+2 and 1+2+3 didn't visibly change anything. Hmm, might be interesting to see a picture should you have a digital camera, but don't worry if it's not convenient. I'm pretty happy you're taking so much time helping me, so I certainly won't complain about small inconveniences. I'll have to charge the camera's batteries first, though. :-) Is it worse than the picture degradation (bad resolution?) which isn't recovered even when killing X you mentioned previously, or the same? It is the same, only that before I couldn't see it in X but only after killing it. But it is exactly the same. One other thing that would be interesting to know next time you test (using a clean checkout (no patches)), if you add `Option FPScale off' in the driver section of your xorg.conf, and set 1280x800, whether that works any better. I'll try that and report back along with the promised photo. -- Configure bugmail: http://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
[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #20 from bmaass bma...@math.uni-bremen.de 2009-02-13 07:51:05 PST --- BIG CORRECTION!!! As the picture error didn't get corrected when killing the server, I didn't notice that patches 1+2+3 actually give a GOOD PICTURE, until I retested after a reboot. Your other suggestion, concerning FPScale, didn't seem to have any effect. I tested: patches 1+2+3, FPScale on: good picture patches 1+2, FPScale on: bad picture patches 1+2, FPScale off: bad picture no patches, FPScale on: no picture no patches, FPScale off: no picture Are you still interested in a photo of the screen distortion? -- Configure bugmail: http://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
[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #21 from Stuart Bennett sb...@cam.ac.uk 2009-02-13 10:04:50 PST --- (In reply to comment #20) BIG CORRECTION!!! As the picture error didn't get corrected when killing the server, I didn't notice that patches 1+2+3 actually give a GOOD PICTURE, until I retested after a reboot. Ok, that's more like I expected (sorry, should have noted the reboot requirement) :-) Your other suggestion, concerning FPScale, didn't seem to have any effect. I tested: Even at 1280x800? interesting patches 1+2+3, FPScale on: good picture patches 1+2, FPScale on: bad picture patches 1+2, FPScale off: bad picture no patches, FPScale on: no picture no patches, FPScale off: no picture Are you still interested in a photo of the screen distortion? No, that's fine, I've a better idea of the problem now. I'll try to come up with some more things next week. -- Configure bugmail: http://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
[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #22 from bmaass bma...@math.uni-bremen.de 2009-02-13 10:14:59 PST --- (In reply to comment #21) No, that's fine, I've a better idea of the problem now. I'll try to come up with some more things next week. That's fine, the patched version is working good so far, so no big hurry here. :-) -- Configure bugmail: http://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
[Nouveau] [Bug 20006] powerpc64: Black screen using RandR12
http://bugs.freedesktop.org/show_bug.cgi?id=20006 --- Comment #23 from Maarten Maathuis madman2...@gmail.com 2009-02-13 10:23:27 PST --- The patched version is just a hack, try hotplugging a (2nd) dvi monitor and see the failure ;-) -- Configure bugmail: http://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
Re: [Nouveau] running x.org on powerpc64 with nvidia6200
On Fri, 13 Feb 2009 18:36:06 +0300 Alexey Kardashevsky aik.r...@gmail.com wrote: I am newbie in this topic and I have problems trying to bring x.org up on the hardware I have: IBM QS22 BladeServer (PowerPC64 architecture) with PCI-Express connected nVidia 6200 video card. Since this is a ppc64, architecture related bugs in Nouveau may occur. I don't really know the situation here. OS: Fedora 10-ppc: Linux localhost.localdomain 2.6.27.5aik #1 SMP Tue Feb 10 14:55:56 EST 2009 ppc64 ppc64 ppc64 GNU/Linux I downloaded and compiled DRM driver (git clone git://anongit.freedesktop.org/git/mesa/drm) and loaded it: [r...@localhost ~]# modprobe drm [r...@localhost ~]# modprobe nouveau [r...@localhost ~]# dmesg | tail -n 3 nouveau 0005:01:00.0: enabling device (0140 - 0142) [drm] Detected an NV44 generation card (0x044300b2) [drm] Initialized nouveau 0.0.12 libdrm-2.4.4-28-geb78c53aa1a980e60 on minor 0 [r...@localhost ~]# lsmod | grep no nouveau 351856 0 drm 249176 1 nouveau [r...@localhost ~]# lspci -v [...] 0005:01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 LE] (rev a1) (prog-if 00 [VGA controller]) Hmm, note the bus id. Subsystem: ASUSTeK Computer Inc. Device 827b Flags: bus master, fast devsel, latency 0, IRQ 106 Memory at 3d08000 (32-bit, non-prefetchable) [size=16M] Memory at 3d0c000 (64-bit, prefetchable) [size=512M] Memory at 3d08100 (64-bit, non-prefetchable) [size=16M] Expansion ROM at 3d08200 [size=128K] Capabilities: [60] Power Management version 2 Capabilities: [68] Message Signalled Interrupts: Mask- 64bit+ Count=1/1 Enable- Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel ? Capabilities: [128] Power Budgeting ? Kernel driver in use: nouveau [r...@localhost ~]# ls -la /dev/fb* crw--- 1 root root 29, 0 2009-02-13 10:19 /dev/fb This is offb, right? If it is nvidiafb, you need to use... can't recall, see here: http://nouveau.freedesktop.org/wiki/Kernel_Framebuffer_Driver The device you should get from nouveau DRM is /dev/dri/card0. Then, I've tried configuring x.org: * [r...@localhost ~]# X -configure -verbose 255 Should this really work? I've no idea. Ok, with no hope, I'm trying to start the X: * [r...@localhost ~]# X -config xorg.conf.new -verbose 255 (II) config/hal: initialized X.Org X Server 1.5.3 Release Date: 5 November 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.18-92.1.10.el5 ppc Current Operating System: Linux localhost.localdomain 2.6.27.5aik #1 SMP Tue Feb 10 14:55:56 EST 2009 ppc64 Build Date: 16 November 2008 08:30:07PM Build ID: xorg-x11-server 1.5.3-5.fc10 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Feb 13 10:26:48 2009 (++) Using config file: xorg.conf.new (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Automatically adding devices (==) Automatically enabling devices (==) Including the default font path catalogue:/etc/X11/fontpath.d,built-ins. (**) FontPath set to: catalogue:/etc/X11/fontpath.d, built-ins, catalogue:/etc/X11/fontpath.d, built-ins (**) ModulePath set to /usr/lib/xorg/modules (WW) AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled. (WW) Disabling Mouse0 (WW) Disabling Keyboard0 (II) No APM support in BIOS or kernel (II) Loader magic: 0x101e59a4 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (--) using VT number 7 (--) PCI:*(5...@1:0:0) nVidia Corporation NV44 [GeForce 6200 LE] rev 161, Mem @ 0x1020bd9c/976, 0x1020bd9c/976, 0x1020bd9c/976, BIOS @ 0x/270581148 (II) LoadModule: nouveau (II) Loading /usr/lib/xorg/modules/drivers//nouveau_drv.so (II) Module nouveau: vendor=X.Org Foundation compiled for 1.4.99.906, module version = 0.0.10 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 4.1 (II) NOUVEAU driver (II) NOUVEAU driver for NVIDIA chipset families : RIVA TNT(NV04) RIVA TNT2 (NV05) GeForce 256 (NV10) GeForce 2 (NV11, NV15) GeForce 4MX (NV17, NV18) GeForce 3
Re: [Nouveau] running x.org on powerpc64 with nvidia6200
Thanks for the prompt reply. My comments are below. Pekka Paalanen wrote: 0005:01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 LE] (rev a1) (prog-if 00 [VGA controller]) Hmm, note the bus id. I actually did, but I have no idea how to interpret this. x86 linux show only 3 numbers for every device, but this server has 6 PCI roots with separate bus numbering so if we want to use 3 numbers system, the bus-id needs to be fixed somehow... [r...@localhost ~]# ls -la /dev/fb* crw--- 1 root root 29, 0 2009-02-13 10:19 /dev/fb This is offb, right? If it is nvidiafb, you need to use... can't recall, see here: http://nouveau.freedesktop.org/wiki/Kernel_Framebuffer_Driver The device you should get from nouveau DRM is /dev/dri/card0. Note this place. I'll ask later :) (II) Primary Device is: PCI 0...@05:00:0 Above it says bus id (5...@1:0:0) and here 0...@05:00:0... could that be the problem? I'd like anybody to tell what do they write (or see after auto-config) as PCI-id for their videos on ppc. I think that it might be a problem. Section Device Driver nouveau VendorName nVidia Corporation BoardName NV44 [GeForce 6200 LE] BusID PCI:1:0:0 And this is a third bus id, different from the two above? It's confusing at least. Try without any BusID in config? For example? What string would at least look correct? I did try a lot of them but to no avail. 3. what am I doing wrong in my expirements? I can see 4 types of drivers: - original drivers coming with the fedora10 kernel (I got rid of them before started playing with nouveau because they did not create even /dev/fb*); That's the kernel framebuffer driver device, which is usually harmful to accelerated X.org drivers, but since you have ppc, you probably need something. The offb driver in kernel should work. Is /dev/dri/card0 the only device node needed for X? Do not we need /dev/fb(0) as well? Or we need both, do we? - drm drivers (which are replacement for the original onesm right?) Original what? Original I meant is the .ko which appears after compiling the Linux kernel with the nVidia driver enabled as a module. My point was that there can be only it OR drm driver loaded. At least, the original drriver does not start (and does not create /dev/fb - I am not sure tha it has to, but anyway) because it fails on reading the nVidia registers in the very beginning (while executing its _probe) - all the memory space mapped via PCI BAR0 is empty. DRM modules are the kernel part of the Nouveau driver. Without them you don't get any acceleration. These are not kernel framebuffer drivers (yet, at least). But is the original (from the linux kernel tree) driver required to make things working at all? - x.org drivers (which I've not changed/replaced) nouveau_drv.so, required, from git. It is accessed via /dev/dri/card0, right? - mesa drivers - what is their role - I still do not understand. 3D acceleration. Not in any usable state at this time, and not included in any Mesa release yet. You can just forget it and enjoy software OpenGL rendering. Cool! There are already too many things so excluding any of them is helpful :-) Actually I start thinking that I need to look for the linux capable to start with X on PlayStation3. It can have clues... ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] running x.org on powerpc64 with nvidia6200
On Fri, 13 Feb 2009 22:49:59 +0300 aik aik.r...@gmail.com wrote: Pekka Paalanen wrote: 0005:01:00.0 VGA compatible controller: nVidia Corporation NV44 [GeForce 6200 LE] (rev a1) (prog-if 00 [VGA controller]) Hmm, note the bus id. I actually did, but I have no idea how to interpret this. x86 linux show only 3 numbers for every device, but this server has 6 PCI roots with separate bus numbering so if we want to use 3 numbers system, the bus-id needs to be fixed somehow... I've absolutely no experience about ppc, ppc64, or multiple PCI roots, so take my advice with a grain of salt. Section Device Driver nouveau VendorName nVidia Corporation BoardName NV44 [GeForce 6200 LE] BusID PCI:1:0:0 And this is a third bus id, different from the two above? It's confusing at least. Try without any BusID in config? For example? What string would at least look correct? I did try a lot of them but to no avail. I mean literally, remove the BusID line. Or is that something that is clearly not going to work? I've never dealt with server hardware. 3. what am I doing wrong in my expirements? I can see 4 types of drivers: - original drivers coming with the fedora10 kernel (I got rid of them before started playing with nouveau because they did not create even /dev/fb*); That's the kernel framebuffer driver device, which is usually harmful to accelerated X.org drivers, but since you have ppc, you probably need something. The offb driver in kernel should work. Is /dev/dri/card0 the only device node needed for X? Do not we need /dev/fb(0) as well? Or we need both, do we? Normally, as I said, having /dev/fb* is harmful, becuase it means the kernel fb driver is active (if using udev). On x86 it is definitely not needed. I don't know how ppc changes this, since there is no VGA text mode to begin with and you need some fb driver to have a text console at all. If you don't need /dev/fb* to have a text console, then you don't need it. Period. Original I meant is the .ko which appears after compiling the Linux kernel with the nVidia driver enabled as a module. nvidiafb.ko is a kernel fb driver. Especially nvidiafb.ko breaks things. My point was that there can be only it OR drm driver loaded. At least, Yes, nvidiafb.ko and Nouveau break each other. the original drriver does not start (and does not create /dev/fb - I am not sure tha it has to, but anyway) because it fails on reading the nVidia registers in the very beginning (while executing its _probe) - all the memory space mapped via PCI BAR0 is empty. DRM modules are the kernel part of the Nouveau driver. Without them you don't get any acceleration. These are not kernel framebuffer drivers (yet, at least). But is the original (from the linux kernel tree) driver required to make things working at all? No. nvidiafb.ko and drm.ko from the Linux kernel break Nouveau. If you need to have some kernel fb driver to have a text console, use offb (vesafb should work with Nouveau, too, but don't all ppc's have OF?). You need drm.ko and nouveau.ko from DRM git repository. - x.org drivers (which I've not changed/replaced) nouveau_drv.so, required, from git. It is accessed via /dev/dri/card0, right? Which it? nouveau_drv.so, also known as the nouveau DDX, accesses the 2D hardware acceleration features via /dev/dri/card0. /dev/dri/card0 is created, when nouveau.ko is loaded and it recognizes the card. -- Pekka Paalanen http://www.iki.fi/pq/ ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] RAOF ppa failing to configure xf86-video-nouveau due to libdrm_nouveau
RAOF as noted on IRC earlier today ppa is currently failing to configure xf86-video-nouveau; `checking for LIBDRM_NOUVEAU... configure: error: Package requirements (libdrm_nouveau) were not met: No package 'libdrm_nouveau' found` Effects both 8.04 and 8.10. First observed because updated drm without matching dri causes loss of xv, NoAccel Regards, Mark Carey ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] running x.org on powerpc64 with nvidia6200
2009/2/13 Alexey Kardashevsky aik.r...@gmail.com: I am newbie in this topic and I have problems trying to bring x.org up on the hardware I have: IBM QS22 BladeServer (PowerPC64 architecture) with PCI-Express connected nVidia 6200 video card. OS: Fedora 10-ppc: Linux localhost.localdomain 2.6.27.5aik #1 SMP Tue Feb 10 14:55:56 EST 2009 ppc64 ppc64 ppc64 GNU/Linux How many PCI domains does that machine have ? Current libpciaccess is broken, in that PCI cards only work in the first domain. So the solution is to put the card in a slot from the first domain if possible. You are screwed otherwise (well, you could replace the hardcoded first domain in pciaccess with the right domain and it might work, I don't know...) Stephane ___ Nouveau mailing list Nouveau@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 16176] X fails to start with GeForce 9600 with ``Failed to allocate memory for framebuffer!
http://bugs.freedesktop.org/show_bug.cgi?id=16176 --- Comment #24 from Adam Petaccia a...@tpetaccia.com 2009-02-13 16:01:30 PST --- Created an attachment (id=22918) -- (http://bugs.freedesktop.org/attachment.cgi?id=22918) Working Xorg log Starts up perfectly now. Switching to VT and back fails, and changing resolutions sort of works, but leaves artifacts and displaces the mouse. I will open up new bugs :-) -- Configure bugmail: http://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
