Created attachment 344569 [details] Xorg.log when KMS enabled Description of problem: * xvinfo shows adapter unavailable , XV could not be used * disabling KMS, xvinfo show adapter, but not usable, crashes Xorg Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.7.0-4.fc11.i586 xorg-x11-server-common-1.6.1-11.fc11.i586 xorg-x11-drivers-7.3-11.fc11.i586 xorg-x11-server-Xorg-1.6.1-11.fc11.i586 How reproducible: Always Steps to Reproduce: 1. Install F11 preview, 2. xvinfo 3. adapter not found 1. disable KMS 2. xvinfo 4. Play video using XV, fails with BadAlloc 5. Try playing video using XV again, Xorg crashes Actual results: not working Expected results: stuff should work Additional info:
kernel version: kernel-2.6.29.3-140.fc11.i586
Could we get also /var/log/Xorg.0.log from crashing Xorg? But otherwise yes, assigning to developers.
Created attachment 345701 [details] Xorg.log after XV crash with KMS disabled
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created attachment 347442 [details] Xorg.0.log from a system without nomodeset This is intended just as an additional datapoint. Same behaviour then described by the original poster.
This is just a "me too". I do see exactely the same behaviour on a system with onboard 855 graphics. This renders the system useless, as it is my Kitchen-TV and the application tvtime is crashing due to xv not working. System is F11 with current patches up to June 11th. I have upload my Xorg.0.log just as an additional data point. Additionally I do have one bonus: Without an xorg.conf file, the X server only gets 1024x768 resolution instead of the correct 1280x1024. This can be corrected through the xorg.conf file. The boot screen though (if enabled) sticks at the erroneous 1024x768.
Actually the wrong resolution that I am seeing during graphical boot might be related to a falsely reported LVDS-1 output device which is not in the system (which is built of a AOpen Centrino Motherboard i855GMEm-LFS) Here a reference that other systems do have the same issue: http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg02729.html xrandr output: [michaelc@vdr ~]$ xrandr Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 4096 x 4096 VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 337mm x 270mm 1280x1024 75.0*+ 60.0 1024x768 75.1 70.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 59.9 720x400 70.1 70.1 LVDS1 connected (normal left inverted right x axis y axis) 1024x768 60.0 + 60.0 800x600 60.3 640x480 59.9 VGA1 is the connected 1280x1024 LCD, LVDS1 is not existing (not even as a connector)
I Have found a solution for the problem of LVDS1 to appear falsely. There is already a blacklist mechanism implemented for apple computers. It is in the drm-intel-lying-systems-without-lvds.patch patch. I have extended the list to my AOpen Board. The new version of the patch is uploaded here. This fixes my problem of a wrong resolution during KMS boots. But unfortunately not the xv problem (nor a problem that pictures display with gthumb give wierd pattern on the screen) I assume that there is some memory misdetection happening ..
Created attachment 350493 [details] drm-intel-lying-systems-without-lvds.patch with exteions for AOpen i855GMEm-LFS Board This is my changed drm-intel-lying-systems-without-lvds.patch with extension for the AOpen i855GMEm-LFS Motherboard to ignore the falsely reported LVDS1 video. A Kernel built with this patch is going to the correct resolution for my screen during system startup. Unfortunately this does not fix other problems I still have with the i855 graphics (missing xv and gthumb picture display corruptions)
XVideo crashes my system too, Intel 855GM, I have just installed today and boom, no video playback at all; maplayer crashes X, gstreamer ends with The program 'gstreamer-properties' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 65 error_code 11 request_code 132 minor_code 19) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) I have tried everything I know: 1) disable kernel mode setting 2) changing accel method (EXA/XAA) 3) change video ram settings 4) disable DRI Nothing seem to work. As work around I am using X11 (very very slow). Please someone fix this! kernel-PAE-2.6.29.5-191.fc11.i686 xorg-x11-drv-intel-2.7.0-7.fc11.i586
Very similar to bug 505285
Hello, Just as an additional datapoint: I have just checked with the F12 Alpha Live CD and even though my problem with the misdetected LVDS connector seems to be fixed, XVideo is still not working. Cheers Michael
Hello, just found this reference: https://bugs.freedesktop.org/show_bug.cgi?id=20901 This seems to be the work to fix the problem. Cheers, Michael
xv also does not work on i865G when KMS is enabled - there are no xv adapters. When KMS is disabled, there's "Intel(R) Video Overlay" and xv works fine.
For i865G, it's still the same with desktop-i386-20090917.16.iso - no xv adapters.
Unfortunately on my i855GM system disabling KMS does not help. Booting with "nomodeset" and then running tvtime (which uses xv) crashes the X-Server with the following trace: EE) intel(0): Failed to pin xv buffer Backtrace: 0: /usr/bin/Xorg(xorg_backtrace+0x3b) [0x812d8eb] 1: /usr/bin/Xorg(xf86SigHandler+0x9e) [0x80c0e0e] 2: [0x440400] 3: /usr/lib/libdrm_intel.so.1(drm_intel_gem_bo_start_gtt_access+0x44) [0x1a4184] 4: /usr/lib/xorg/modules/drivers//intel_drv.so [0xe86756] 5: /usr/bin/Xorg [0x80d74ee] 6: /usr/lib/xorg/modules/extensions//libextmod.so(XvdiPutImage+0x186) [0x11be36] 7: /usr/lib/xorg/modules/extensions//libextmod.so [0x11fb28] 8: /usr/lib/xorg/modules/extensions//libextmod.so(ProcXvDispatch+0x3a) [0x120b3a] 9: /usr/bin/Xorg(Dispatch+0x35f) [0x80869df] 10: /usr/bin/Xorg(main+0x395) [0x806bbf5] Fatal server error: Caught signal 11. Server aborting Unfortunately this means no videos on this system now for more then 3 months.
This still does not work on i865G in desktop-i386-20091001.15.iso.
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages. For packages from updates-testing repository you can use command yum upgrade --enablerepo='*-updates-testing' Alternatively, you can also try to test whether this bug is reproducible with the upcoming Fedora 12 distribution by downloading LiveMedia of F12 Beta available at http://alt.fedoraproject.org/pub/alt/nightly-composes/ . By using that you get all the latest packages without need to install anything on your computer. For more information on using LiveMedia take a look at https://fedoraproject.org/wiki/FedoraLiveCD . Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
Still does not work on i865G with desktop-i386-20091102.16.iso
I'm using F12 on a notebook with a i855 video card. Xv doesn't work for me too. Xvinfo tells me: xvinfo X-Video Extension version 2.2 screen #0 no adaptors present and in Xorg.log I have: (WW) intel(0): Disabling Xv because no adaptors could be initialized. I have installed all the latest updates: kernel: 2.6.31.5-122.fc12.i686 Xorg: xorg-x11-server-Xorg-1.7.1-7.fc12.i686 driver: xorg-x11-drv-intel-2.9.1-1.fc12.i686
F12 with latest kernel-2.6.32.3-17 and lots of updates-testing still no xv. comments on upstream bug #13 tell this will be fixed in 2.6.33 kernel and 2.9.10 xorg-x11-drv-intel. Should we wait for F13?
the kernel side shuold be there in that kernel I think we need to package 2.10 or backport the overlay bits to 2.9.
We need 2.6.33-rc4 and xorg-x11-drv-intel-2.10, I believe the bits are there. Let's wait for F13.
Hello, I just did some tests: - "backported xorg-x11-drv-intel-2.10" (which was a simple rpmbuild of the FC13 SRPM, no code changes - installed kernel-2.6.32.7-37.fc12.i686 Result: XVideo is back on 855GM! Unfortunately I am seeing other Xserver crashes from time to time (not XVideo related). But at least this is a prove that things are progressing. Finally ...
That's cool. unfortunately I am blocked by bug 561970 on 2.6.32/33.
With gfx_test_week_20100414_i686.iso, xv adapter is present ("Intel(R) Video Overlay") on i865G. But playing a video produces only black rectangle. However, when the video player window is dragged using mouse, the video appears - and plays until the mouse button is released.
Speaking off Totem? I can see similar problem, however mplayer (with xv) looks good.
Yes, it was Totem. It works with another VGA card.
I haven't tested the F13 stuff yet, but the problem seen in the comments directly above seems identical to a Banshee-specific problem[1] I ran into on Ubuntu before switching to Fedora (where xv broke altogether with KMS). [1] https://bugzilla.gnome.org/show_bug.cgi?id=562826
Shouldn't we move this one to F13 or Rawhide? Personally I had the problem on F-13.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.