similar to: [Bug 28891] New: [GeForce FX 5200] Broken KMS support (corrupted cursor)

Arjen, all I don't know if there is some prohibition against it, but the packages.html link for SuSE RPMs should be changed from: http://software.opensuse.org/ To something useful that will get the site visitors to the actual rpms. For the packages that were part of the distribution: http://download.opensuse.org/distribution/ or for updated packages on build service:

Hallo. Here is a simplification of the automake stuff for nut 2.2.2. The idea is simple: libcommon.a contains stuff for the binaries libparseconf.la contains stuff for binaries and shared library Both are NOINST, automake understands perfectly our intentions. The rest is only a removal of the implicitly defined stuff. On top of the parallel build patch I got build success on all platforms

https://bugs.freedesktop.org/show_bug.cgi?id=44054 Bug #: 44054 Summary: Gnome shell videobug on GeForce FX 5200 & Nouveau Classification: Unclassified Product: Mesa Version: 7.11 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=93613 Bug ID: 93613 Summary: 3D acceleration/OpenGL corrupts output on GeForce FX-5200 Product: Mesa Version: 10.3 Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=39530 Summary: Also after installing Obermayrs drm-nouveau driver booting succeeds only with nomodeset Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component:

http://bugs.freedesktop.org/show_bug.cgi?id=15280 Summary: Wrong resolution/black screen with NV34 [GeForce FX 5200] Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at

Hi there, I have just decided to try this new driver stuff (used 2.6.27 earlier and a proprietary nvidia driver) but the monitor (Samsung 214T) becomes black and the power LED starts flashing (standby) after loading nouveau module (from a fresh 2.6.33). For now I am trying framebuffer only. The monitor is connected with a single link DVI cable. lspci -nn 03:00.0 VGA compatible controller

Stan, I'm very pleased to see you back to work with us on enhancing nut in that many areas ;-) 2008/4/30 Stanislav Brabec <sbrabec at suse.cz>: > Stanislav Brabec wrote: > > > Please note that 2.2.2-pre3 installs hald addons by default to / on > > openSUSE 11.0 beta 2 x86_64. Not a big problem. > > Here is a patch, which fixes openSUSE 11.0 beta 2 x86_64:

Dear Stanislav, thanks for your patch. The problem with your "recommended" pkgconfigdir is that in many cases, it does not work. Namely, when ${prefix} is not one of the standard places such as /usr. As I understand it, the whole point of a tool like pkgconfig is to allow other software to automatically detect the install location of NUT, especially when that location is not one of

Hi, I just installed the latest nouveau driver from git to try if it works and after modifying my xorg.conf and switching to xorg-x11 opengl startx changes screenmode (screen gets black) and nothing more happens. I can ssh from another maschine and see that X takes 100% CPU but nothing more happens. I am on Gentoo Linux, followed the guide from the Wiki, have Xorg-x11-7.2, tuxonice patched

https://bugs.freedesktop.org/show_bug.cgi?id=35514 Summary: Black screen with nouveau on a GeForce 8600M GT, either LiveCD or fresh install Product: xorg Version: 7.6 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: high Component: Driver/nouveau

On 05.01.2016 04:08, Thomas Richter wrote: > Hi folks, > > I don't seem to be able to enable the DVI-I output of an old FX 5200 > behind a KVM switch. Autodetection works fine if the FX 5200 DVI output > is switched to the monitor, but when it is not, I have not found a way > to force-enable it. > > Here is what I tried: > > *) used the

On 05.01.2016 14:47, Thomas Richter wrote: > Am 05.01.2016 um 11:41 schrieb poma: > >> >> append to kernel cmdline: >> drm_kms_helper.edid_firmware=DVI-I-1:edid/edid.bin >> >> $ cat /proc/cmdline >> ... drm_kms_helper.edid_firmware=DVI-I-1:edid/edid.bin ... >> > > Well, no banana. Yes, the kernel loads the edid, but the screen keeps >

Hi, > > Try your luck here > http://lists.freedesktop.org/mailman/listinfo/dri-devel The major problem is that there is no way to tell the nouveau kernel module to enforce a specific output. There is a video=XXX kernel parameter, but this only applies to the VGA framebuffer but not to the nouveau framebuffer. > BTW what is actual KVM switch device, vendor/product? This is an

http://bugs.freedesktop.org/show_bug.cgi?id=10858 Summary: glxgears with mesa-git on PCI 10de0322 (NV34) GeForce FX 5200 crashes X Product: xorg Version: 7.2 Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Am 05.01.2016 um 11:41 schrieb poma: > > append to kernel cmdline: > drm_kms_helper.edid_firmware=DVI-I-1:edid/edid.bin > > $ cat /proc/cmdline > ... drm_kms_helper.edid_firmware=DVI-I-1:edid/edid.bin ... > Well, no banana. Yes, the kernel loads the edid, but the screen keeps blank if I switch the monitor to the system after bootstrap. )-: [ 20.319271] [drm] Got

nut hardcodes systemdsystemshutdowndir to ${libdir}/systemd/system-shutdown. This is not valid: - Executable helpers are installed to ${libexecdir}, which is different from ${libdir} on bi-arch systems. - Even if nut will use ${libexecdir}, it could be different from systemd libexecdir. That is why it is better to check systemd.pc for the correct path. That path is stored as systemdutildir.

Hi folks, I don't seem to be able to enable the DVI-I output of an old FX 5200 behind a KVM switch. Autodetection works fine if the FX 5200 DVI output is switched to the monitor, but when it is not, I have not found a way to force-enable it. Here is what I tried: *) used the video=DVI-I-1:1280x1024-24 at 60e kernel parameter (framebuffer still sits at 1024x768) *) used "options

I am trying to figure out why the ttm_bo_vm_fault is stitching pages from the GART instead of the pages allocated via DRM_NOUVEAU_GEM_NEW. And also why OUR_RINGp is writing 16, 256 and 512 bytes of zero filled data *1 in the GART? Perhaps I should mention that I know _why_ it is taking the pages from the GART and giving them to the userland - but I don't know if that is correct way of doing

Hello again, everyone. I'm the same "Fernando Negro" that sent a message entitled "GeForce 8400 GS", three days ago. ( http://lists.freedesktop.org/archives/nouveau/2013-October/014660.html) I'm sorry for having to open a new topic, in here... But, due to all the experiments with installing new distros and drivers on my computer, I ended up loosing access to the