Support for X.Org xserver version 1.15 was added to the 173.14.* legacy driver series with version 173.14.39. Dementiev 2013-04-08 15:13:02 UTC I've got the same problem. I can't tell what mesa driver is being called. As of 304.123, custom modelines are accepted if Option "ModeValidation" "AllowNonEdidModes" is added to Section "Device", but only sometimes will it do the right thing. http://bsnux.com/aiglx-error/aiglx-error-calling-driver-entry-point-failed-ati.html
Scrolling text is just as slow as with vesa if not worse and icons don't display correctly in some apps. So it's back to Slackware 12.2. Should I recreate this report on another component (DDX) or what ? The libdrm fix is in the 2.4.35 release and I think the kernel fix is in mainline as well, so resolving this report as fixed. https://bugs.launchpad.net/bugs/1040524
EDuke32 needs r_texcompr "0" to avoid a black screen of death but then fails with an out of memory condition while loading textures. Build kernel 3.2.55 and Nvidia drivers 71.86.15 with the stock compiler (GCC 4.2.4). Before gnome3 I was running compizusing my old drivers without problems. check_crtc_state+0x6b8/0xdd0 Apr 6 17:28:42 EeePC kernel:  ?
Log in / Register Ubuntuxserver-xorg-video-nouveau package Overview Code Bugs Blueprints Translations Answers AIGLX error: Calling driver entry point failed Bug #1040524 reported by dino99 on 2012-08-23 10 This bug affects 2 This was enabled by default and also specified in the config file. [ 2211.212] (II) "dri2" will be loaded by default. [ 2211.212] (II) LoadModule: "glx" [ 2211.212] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so Gmp, mpfr, and mpc are needed to build gcc 4.8.2. (Mpfr and gcc each accepted the stock version of gmp, but mpc would not.) Slackware 12.2 comes with no version of The new compiler produced a new build error in libavdevice/xv.c, which was fixed by reversing the order of the XShm.h and Xvlib.h includes.
Apply arch patches only through 4.3. Libgl Error: Failed To Load Driver: I965 The startup of X fails with the messages [ 18.376] (EE) RADEON(0): radeon_surface_best failed [ 18.376] (EE) RADEON(0): radeon_setup_kernel_mem failed It's been suggested that my problem is related to the bug These cards are supported with the legacy ATI 9-3 Catalyst release, but that was dead-ended and requires kernel ≤ 2.6.28 and X server ≤ 1.5 to work. https://bbs.archlinux.org/viewtopic.php?id=120235 Just downgrading the kernel and X server is a nonstarter.
To those more knowledgable than I - does this seem likely? How can I find (or refine) the reason? In freedesktop.org Bugzilla #43448, agd5f (agd5f) wrote on 2012-06-06: #21 Created attachment 62674 libdrm fix slightly improved version. Revert xorg-server to previous version (184.108.40.2061-1) 2.
As of 2014-08, I have not tested Utah at all. https://bugs.freedesktop.org/show_bug.cgi?id=62914 Launchpad couldn't import bug #43448 from freedesktop.org Bugzilla. (what does this mean?) Affecting: xserver-xorg-driver-ati Filed here by: madbiologist When: 2012-06-05 Started work: 2012-06-16 Completed: 2012-06-16 Target Distribution Baltix BOSS Juju Charms (ee) Aiglx: Reverting To Software Rendering That problem went away after rebuilding ffmpeg with GCC 4.8.1. This information was last pulled on 2016-09-25.
ATI Mach64 Graphics Pro Turbo (PCI, 4 MiB) Way back when, I bought this rather pricey Mach64 card specifically because it had a working Linux driver. weblink It makes no difference whether I use the Slackware 13.37 package or my own build of Mesa 7.11.2. if CompSync or SyncOnGreen [ 2211.377] (II) RADEON(0): Max Image Size [cm]: horiz.: 41 vert.: 31 [ 2211.377] (II) RADEON(0): Gamma: 2.20 [ 2211.377] (II) RADEON(0): DPMS capabilities: StandBy Suspend Off; Maybe you can try running glxinfo in gdb, setting a breakpoint at dri2CreateNewScreen and tracing where the failure is coming from.
In freedesktop.org Bugzilla #43448, Michel Dänzer (michel-daenzer) wrote on 2011-12-06: #10 Looks like /usr/lib64/dri/r600_dri.so's dri2CreateNewScreen() hook fails, but it's not clear why. dino99 (9d9) wrote on 2012-10-23: #5 This is fixed now with xorg abi 13; marking as such. Affecting: xserver-xorg-video-ati (Ubuntu) Filed here by: Dirk Möbius When: 2012-05-21 Confirmed: 2012-05-23 Started work: 2012-06-05 Completed: 2012-06-20 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu http://bsnux.com/aiglx-error/aiglx-error-calling-driver-entry-point-failed.html CONFIG_DRM_RADEON=y, CONFIG_DRM_RADEON_UMS=n, CONFIG_FB_RADEON=n: Now there's DRI2 and GL but 2D acceleration is broken.
AO: [pulse] 44100Hz stereo 2ch float VO: [opengl] 1280x720 yuv420p intel_do_flush_locked failed: Input/output error Comment 35 Sgt. drm_ioctl+0x3be/0x440 Apr 6 17:28:42 EeePC kernel:  ? Trident TVGA 9400CXi (VLB, 1 MiB) The man page for trident (versioned xf86-video-trident 1.3.6) says: SUPPORTED HARDWARE The trident driver supports PCI, AGP and ISA video cards based on the following
Will this info help you to figure out what actually happened? Comment 28 Emil Velikov 2013-07-30 10:27:03 UTC Guys plese try xf86-video-nouveau 1.0.9 It contains the following patch which should handle the crtc->randr_crtc == NULL case as spotted by Ilia commit be44e7804862b4c276ed4d4717b1212920f428e6 With CONFIG_DRM_NOUVEAU and CONFIG_FB taken out, nouveau detects no device and exits. 2016-09: I flipped the bozo bit on Nouveau in 2014 and since then have rarely bothered to test it, Extinction events Nvidia 2012-11: Nvidia dead-ended their 71.86 and 96.43 legacy drivers. 2014-03: Nvidia dead-ended their 173.14 legacy drivers.
A few months ago they started crashing to a black screen and restarting in an infinite loop, presumably as a result of incompatibility with some routine Windows update, and nothing since Back to Windows XP. 2014-01: Slackware 14.1 and kernel 3.12.8 with an Asus GeForce2 MX400 32 MiB recently orphaned by the EOL of Nvidia's 96.43.23 fork: the Nouveau drivers appeared to Changed in xserver-xorg-video-nouveau (Ubuntu): status: Confirmed → Fix Released See full activity log To post a comment you must log in. his comment is here Dementiev 2013-04-15 07:19:34 UTC Unfortunately, I cannot use stand-alone drm module with my 3.7.10 kernel: /var/tmp/portage/x11-base/nouveau-drm-20121015/work/master/drivers/gpu/drm/drm_gem.c: In function ‘drm_gem_mmap’: /var/tmp/portage/x11-base/nouveau-drm-20121015/work/master/drivers/gpu/drm/drm_gem.c:709:19: error: ‘VM_RESERVED’ undeclared (first use in this function) /var/tmp/portage/x11-base/nouveau-drm-20121015/work/master/drivers/gpu/drm/drm_gem.c:709:19: note: each
Comment 4 Maxim P.