Re: xserver-xorg-video-intel: Changes to 'ubuntu'
On 01/04/2011 08:52, Bryce Harrington wrote: New commits: commit cbe6f77df3eef58b93cc7e682ea149b04e628dec Author: Bryce Harrington Date: Thu Mar 31 23:50:51 2011 -0700 Prevent filing automatic gpu lockup bug reports for 8xx. The Canonical-X team doesn't plan on doing bug work on this hardware; as it is we're just WONTFIX'ing the bugs, so why bother having them filed in the first place... Hello X Strike Force. Please, don't do like them. Keep on considering i8xx users and keep on collaborating with upstream to resolve regressions that happens from time to time. Cheers. Cesare (i855 here, that works quite well with Debian). -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d977eec.9000...@gmail.com
Re: Bug#619053: marked as done (xserver-xorg: invisible mouse cursor)
On 25/03/2011 01:29, Cyril Brulebois wrote: There have been several such reports already; there's a clear regression in stable, with a guilty commit already known. What would an extra bug buy us? I understand your point, KiBi. And i agree too that probably to you (xsf devels), there wouldn't be immediate gain. But, i think, for others (developers or users) that are searching for a problem, can be useful: helps to link together informations and to show relationships. And can be helpful for historical reasons, even to you, for example to track regressions. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d8d05c0.8060...@gmail.com
Re: Bug#619053: marked as done (xserver-xorg: invisible mouse cursor)
On 20/03/2011 22:51, Cyril Brulebois wrote: HB (20/03/2011): > the latest update in squeeze-updates made my mouse cursor > invisible. the cursor is still there (i can click etc.) but > invisible. x was working without problems before. thanks for the report, but closing, as a duplicate of #619019, filed against the kernel. I don't want to do polemics, just wondering. Why closing bug as #619053 and #619470 as duplicate, instead of reassigning and merging with #619019? Isn't it more useful to see that there are many bugs open referring to the same problem? Apart this specific case, every report could add details to help solving (from a maintainer point of view) or workaround or simply understand (from a user point of view) a problem. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d8b93e7.8030...@gmail.com
Bug#612983: xserver-xorg: X does not start
On 12/02/2011 03:22, Sridhar M.A. wrote: Kernel version (/proc/version): Linux version 2.6.37-0.dmz.7-liquorix-amd64 (Debian 2.6.37-7) (dame...@gmail.com) (gcc version 4.4.5 (Debian 4.4.5-10) ) #1 ZEN SMP PREEMPT Mon Jan 31 02:37:44 CST 2011 If were you, i would try with a standard Debian kernel. A 32 bit for starting, then amd64. Since you talked about locked keyboard, are you sure that your dmesg doesn't show oopses or other error messages? Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d57d62f.9000...@gmail.com
Bug#596356: xserver-xorg-video-intel: crash every day with intel driver, don't crash with vesa
On 13/01/2011 19:31, Yan Morin wrote: VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01) Hi Yan. Even if your system crash as the one from the original reporter, you both have very very different hardware: yours is one the older chipset supported by Intel driver and for which there are known problems; Julian has instead a very new hardware. I think you'd better to open a new bug to track your problem. And keep in mind that your platform is quite rare now, so it would be good if you will inform upstream too: http://intellinuxgraphics.org/feedback.html Xorg X server configuration file status: -rw-r--r-- 1 root root 3607 Jan 11 21:45 /etc/X11/xorg.conf From the low of my experience i can suggest you: - search for "845", "hung", "hangcheck" and similar on bugs.debian.org and on lists.freedesktop.org/archives/intel-gfx/, to find similar reports. - try to rename xorg.conf so that it won't be loaded anymore. If you don't have particular needing, now X is able set the proper configuration automatically. This probably won't resolve your specific problem. - if you are able and if you are not afraid to experiment, you can try both kernel and intel driver from experimental, so you can see if your problem are already corrected or got better. To summarize upgrade xserver-xorg-video-intel, libdrm-intel1, libdrm2 and install linux-image-2.6.37-trunk-686. DRM Information from dmesg: [1.006699] Linux agpgart interface v0.103 [1.006788] agpgart-intel :00:00.0: Intel 830M Chipset [1.007044] agpgart-intel :00:00.0: detected 8060K stolen memory [1.008884] agpgart-intel :00:00.0: AGP aperture is 128M @ 0x8800 [ 21.638642] [drm] Initialized drm 1.1.0 20060810 [ 21.771292] [drm] set up 15M of stolen space [ 21.817247] [drm] initialized overlay support [ 21.996304] fb0: inteldrmfb frame buffer device [ 21.996319] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [103690.148008] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [103690.148036] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 766371 at 766370) Maybe it's normal, but i wonder why lspci reports an i845 chipset, while this logs talks about an i830. Good luck. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3229fa.1030...@gmail.com
Bug#600802: Bug#601558: closed by Cyril Brulebois (Re: Bug#601558: SOLVED? CONFIG_FRAMEBUFFER_CONSOLE=y solved the problem)
On 10/30/2010 08:43 PM, Oliver Sander wrote: I will follow Cesare Leonardis suggestion in the 600802 thread and try the kernel and x driver from experimental. Yes, my reply was for #601558, not for #600802. Thank you Oliver for noticing my error. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ccc7393.2090...@gmail.com
Bug#600802: SOLVED! CONFIG_FRAMEBUFFER_CONSOLE=y solved the problem
On 10/30/2010 03:15 PM, wzabo...@elektron.elka.pw.edu.pl wrote: Yes, it was a kernel configuration related bug (it was submitted by someone alse as bug 601558) The problem id that when KMS is switched on (at least in Intel chipsets) the support for framebuffer console must be also switched on. I ve set two options in my kernel configuration: CONFIG_FRAMEBUFFER_CONSOLE=y CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y I suspect that this bug may have been closed too quickly. Maybe i'm missing something, but Oliver, the bug submitter, used the official Debian kernel and from /boot/config-2.6.3* i see that they have these two options already enabled, both in 2.6.32-26 and 2.6.36-1~experimental.1. Moreover Oliver and wzabolot have totally different chipsets: i830 the former and i865G+i945GM the latter. Waiting for a reply from Oliver, i suggest him to try 2.6.36 just landed to experimental and xserver-xorg-video-intel 2.13 from experimental. I know that he have already tried 2.13 from a kibi build, but the latter seems more experimental than the one from, ehm, experimental. :-) Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ccc2443.1000...@gmail.com
Bug#601434: closed by Cyril Brulebois (Re: Bug#601434: xorg kernel modesetting req in sid)
On 10/26/2010 08:51 AM, Peter wrote: I checked out the links you sent, but I don't understand why, if it worked previously, UMS is being removed as an option now. The thing is, I have to mess with it more, but I think KMS may work partly with 2.6.30 or 32 but I'm not sure. When I saw the update, I decided I should update my kernel to see if that helped. On 2.6.36, I get a black screen on boot with KMS! Could you maybe explain to me more technically why UMS is being removed? I think I have an Intel GMA 950. Hi Peter. Upstream is working on KMS and considers UMS obsolete; Debian has chosen to follow that for the sake of sustainability. Currently many problems were solved and looking at the decrease of bug reports regarding the Intel driver on the debian-x mailing list, seems that the driver is in a rather good shape now. The reasons behind the UMS/KMS choices are scattered on various mailing list. I suggest you to search on these mailing list archives: Upstream: http://lists.freedesktop.org/archives/intel-gfx/ Debian-x: http://lists.debian.org/debian-x/ Debian-kernel: http://lists.debian.org/debian-kernel/ Then i suggest you to followup to this bug using reportbug, so that important information about your hardware, your kernel and software versions are sent automatically. Because your report really lack many information. Please, at least post: - dmesg output - lspci output - linux-image version - xserver-xorg-video-intel driver version Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc75dc3.1000...@gmail.com
Bug#599812: Chrome rendering of HTML5 elements such as canvas and video crash X with xserver-xorg-video-intel
On 10/11/2010 03:43 PM, Jonathan E. Magen wrote: Package: xserver-xorg-video-intel Version: 2:2.9.1-4 Severity: important When using the Chrome 7 preview release, rendering pages with advanced HTML5 effects such as and will cause X to crash with the xserver-xorg-video-intel driver. I suspect this might be something to do with the new GPU rendering process but either way, Chrome should not be able to crash X. When X crashes, the system is completely unusable, does not respond to keypresses and must be power cycled to become usable once more. Very likely an intel driver problem. However seems already fixed. Read this: http://lists.debian.org/debian-x/2010/10/msg00057.html If you can, try yourself using the intel driver from experimental. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cb3894c.4020...@gmail.com
Bug#567475: xserver-xorg-video-intel: The latest update to testing broke some functionality on 855GM cards
Hi Michael. On 10/04/2010 08:11 PM, Michael Maurer wrote: Both versions of the package start the X-server (that is already an improvement over the current linux-image-2.6.32-5-686/xserver-xorg-video-intel combination in testing) and the issues initially reported in the bug are gone, i.e. shutdown, reboot, hibernate, logout all seem to work. The video acceleration seems to work, too. So, since the original problem were solved, maybe it would be more appropriate to close this bug and start another one. I have however had some issues with the xserver-xorg-video-intel 2.12 that don't occur with the 2.13 version. I have an i855 too and for me 2.13 was a big improvement, particularly on the stability front. I'm not a gamer and i don't use suspend/hibernate, but i use this computer everyday for many hour and i haven't seen a crash or an hang since i've installed it. Both with kernel 2.6.32 and 2.6.35. And on the speed front i haven't noted performance regression (even if seems there are). The 2.13 version doesn't have quite the same problems. It handles screen resolution changes fine, and start games like Tux Racer and Scorch3D, nevertheless I had a few crashes of the X-server with 2.13, too. This bug was a little harder to trigger, but opening enough applications including 3D ones usually did the trick and killed X. After the bug was triggered once though, trying to start a 3D application always killed X and trying to play a movie with mplayer showed a blue window instead of the movie. Good analisys. Me too now can now put Youtube video fullscreen without make X crash. Would be perfect if we could find a set of reproducible step to induce one of this bug, so that we could file a precise bug report. If you find it, let me know, so we can compare the results. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4caa3999.1080...@gmail.com
Bug#598803: xserver-xorg-video-intel: X crashes / hung gpu, now and then
CCing the kernel team for letting them know. On 10/02/2010 01:45 PM, Steinar H. Gunderson wrote: I'm seeing the issue of hung GPU, after which a lot of applications (in particular urxvt) become very messed up. Restarting X does not help for me. [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 3894 at 3893) [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Hello Steinar, can you tell us what's your chipset? I ask you because, reading from debian-x ml seems that people with chipset like i830, i845 keep on seeing this kind of problem. I have an i855 and i'm here to say to the Debian X strike force and to the debian kernel team that the combination of 2.6.32-24 (and above) and 2.12.0+shadow-2 is a great improvement for me: after about a week of hour and hour of work with this x driver and 2.6.35-rc6 i haven't seen an hang or a video problem (i scaramantically touch iron saying this). I've also noted on debian-x that complains about i855 seems to have fallen down and many bugs were closed, isn't it? I can reproduce it 100% reliably by trying to play http://www.youtube.com/watch?v=IrwjatDnLKY in Google Chrome with HTML5 enabled. I can reproduce this video without problem, also going fullscreen (in the past week this operation caused me freeze or X restarting itself). It'd be nice to know how it goes with 2.13.0-1 (just uploaded to experimental, so available in a few hours). I'm waiting to try. It's not on my mirror yet. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ca758d7.3030...@gmail.com
Bug#596901: xserver-xorg-video-intel: no cursor in X
On 09/14/2010 11:18 PM, Michal Čihař wrote: first I have to say there seem to be similar bugs reported (eg. #550701), but I believe the cause here is different. Are you sure #550701? It talks about a package called tmux... The problem is that mouse cursor is not working in X with 2.6.35 kernel which is currently available in experimental. If you mean that the mouse pointer is invisible but working, i think you are facing the same bug i've reported in #592415. And it's another issue related to i855. I've reported to the kernel because rebooting with 2.6.35-rc6, 2.6.34 and older ones, it works. But also xserver-xorg-video-intel is a good candidate to this problem. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c90102a.9000...@gmail.com
Re: X failed to work after an upgrade
On 09/11/2010 10:52 PM, Bo Jiang wrote: Hi There I am running squeeze and a recent upgrade make my X window hangs on start up, The screen dies, no log message can be found in the file. i am using the default configuration coming from the installation, it used to work fine. Xserver-xorg version 1.7.7 , Laptop Acer Travelmate 290, Does anybody have idea how to trouble shoot this problem ? At work i have a notebook belonging to the 290 series (Acer TM292LCi) and i have the same problem because it use an i855 chipset. You can find more info in various bug report, but this is the more detailed that i remember: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623 Can you confirm that your laptop has an i855 chipset? Please reboot in single user mode, save the lspci output and send it here. Or, if the problem is really the same, you can add this info in the bug report above. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c8ccb7e.6000...@gmail.com
Re: Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets
On 09/07/2010 02:27 PM, Ben Hutchings wrote: On Sun, Sep 05, 2010 at 02:25:25PM +0200, Cesare Leonardi wrote: It's both a kernel and a xserver-xorg-video-intel problem, but more the latter. The kernel team is probably waiting to know if KMS should be enabled or not for these chipsets and is working in concert with the Ubuntu one for a common solution. [...] We're not working with Ubuntu on this, though we did follow their lead in blacklisting those chips. Thanks for the explanation. That was the message where i saw some collaboration between Debian and Ubuntu on this UMS/KMS problem: http://lists.debian.org/debian-kernel/2010/09/msg00041.html Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c86bec5.3020...@gmail.com
Re: Bug#595521: i915: system locks up when starting X
On 09/04/2010 10:15 PM, Edward Allcutt wrote: By "locks up" I mean: * Screen blanks * Unresponsive to network * Unresponsive to sysrq * No disk activity * No logs written to disk after that point in time I have xserver-xorg-video-intel 2:2.12.0+legacy1-1 installed. Before rebooting today I was previously running with this version of the X driver and the previous version (2.6.32-20) of the kernel. Hi Edward. Unfortunately this is a common problem that i855 owners are facing: look at #595511. Kernel-team: to me these two bugs could be merged. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c838e91.2020...@gmail.com
Re: Bug#595511: linux-image-2.6.32-5-686: Blacklisting KMS for i8xx makes xorg intel driver unusable on these chipsets
On 09/04/2010 08:00 PM, Soenke wrote: the recent update of linux-image-2.6.32 to 2.6.32-21 disables KMS for i8xx chipsets. This causes the xorg-video-intel driver to hang on X startup on my system. Yes, the situation for your i855 and previous intel chipset is in a bad shape. For example look this (but there are other similar reports): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623 It's both a kernel and a xserver-xorg-video-intel problem, but more the latter. The kernel team is probably waiting to know if KMS should be enabled or not for these chipsets and is working in concert with the Ubuntu one for a common solution. On the X driver front, seems that the intel-gfx upstream developers are working to make KMS usable for our chipsets too, to avoid that distributions choose to fallback to UMS, to render the driver more maintenable and to make easier to port new features also to these not-so-new chipsets. From what i've read seems that on these chipsets there will be some performance penality in exchange to stability. Looking here, seems there were lot of work recentely: http://lists.freedesktop.org/archives/intel-gfx/ We will see when these changes will be released and if will be suitable for Squeeze. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c838c35.3050...@gmail.com
Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On 08/28/2010 02:10 PM, Julien Cristau wrote: Could you guys test the driver pointed at http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007910.html? (probably with the 2.6.32-20 kernel) Situation summary: - the latest intel drivers and the latest kernel kms blacklisting cause hard system freeze to many (most?) i855 owners; - these changes are, unfortunately, worse than what they want to solve; - upstream is working on a solution (slower but more stable) for these kind of problem that affects older chipset and is designed to work with KMS; - a working solution isn't there now. With these premises, shouldn't these changes be reverted, in particular the kernel blacklist? Up to now i've seen complains only from i855 owners so it can be considered to remove only this chipset, leaving blacklisted the older ones. If that helps i can ask a friend of mine to make some test with his i845. P.S.: for the record, at work i've tested another i855 notebook (Acer TM292LCi) that exibits the same hangs reported in this bug. For few week it will be available if we want test new drivers or patched one. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c8022d2@gmail.com
Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
For Chris Wilson: you can follow this bug history here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623 On 08/29/2010 05:18 PM, Julien Cristau wrote: Although it looks like they crash the X server in dri2 code when I run glxinfo, so I put xserver packages with a fix for that crash at the same place. Yes, running the glxinfo after updating only the intel-x-driver make the xserver crash, then gdm automatically restarts. In /var/log/X.log.0.old i can see this error: Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80d920b] 1: /usr/bin/X (0x8048000+0x581d5) [0x80a01d5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb786d40c] 3: /usr/lib/xorg/modules/extensions/libdri2.so (0xb785b000+0x1423) [0xb785c423] 4: /usr/lib/xorg/modules/extensions/libdri2.so (0xb785b000+0x1d6a) [0xb785cd6a] 5: /usr/bin/X (0x8048000+0x38067) [0x8080067] 6: /usr/bin/X (0x8048000+0x1e92a) [0x806692a] 7: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb75a0c76] 8: /usr/bin/X (0x8048000+0x1e511) [0x8066511] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting I've experienced this with both 2.6.32-20 and 2.6.35-rc6. Julien, many thanks for working on this and providing this experimental packages. I hope we can find a reasonable solution for Squeeze. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c7ae074.1050...@gmail.com
Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On 08/29/2010 05:18 PM, Julien Cristau wrote: There are i386 packages at http://people.debian.org/~jcristau/intel-shadow/ which work for me on minimal testing. Hi Julien. As long as you provide .deb packages, i can test whatever you want! ;-) Here is my results. Now i'm writing with: - i855 chipset - kernel 2.6.32-20 - KMS enabled with i915.modeset=1 (/etc/modprobe.d/i915-kms.conf temporarly deleted) - intel 2.12.0-2 with Chris Wilson's shadow patch, packaged from you and downloaded from http://people.debian.org/~jcristau/intel-shadow/ - a hand-created file /etc/X11/xorg.conf.d/intel-shadow.conf, containing: Section "Device" Identifier "intel" Option "shadow" EndSection If that helps, i have some packages from experimetal, notably these: firmware-linux-free 2.6.35-1~experimental.2 linux-base 2.6.35-1~experimental.2 linux-image-2.6.34-1-6862.6.34-1~experimental.2 linux-image-2.6.35-rc6-686 2.6.35~rc6-1~experimental.1 linux-image-2.6.35-trunk-6862.6.35-1~experimental.2 libdrm-intel1 2.4.21-1 libdrm2 2.4.21-1 libgl1-mesa-dri 7.8.2-2 libgl1-mesa-glx 7.8.2-2 libglu1-mesa-glx7.8.2-2 Since 2.6.32-21 has KMS disabled in the code, with the configuration above the X server doesn't start: no hangs, only an error reporting that the X server cannot be started and a message in the log reporting that KMS is required (see the "X shadow (KMS off).log"). So i've downgraded the kernel to 2.6.32-20 (from testing) and downloaded your debs to do some tests. Even if you reported hangs updating only the intel driver, i decided to start step-by-step, also because we have different chipsets. So i've installed only xserver-xorg-video-intel_2.12.0-2_i386.deb and rebooted with the "i915.modeset=1" kernel parameter. Here everything seems to works fine so far (uptime 2,30) and i haven't noted any visible slowdown in the day-to-day use under Gnome: web browsing with flash, mail, music, movies, ecc. I'm only not completely sure the patch is working properly: the X log (see "X shadow (KMS on).log") doesn't show any error about the shadow option, but doesn't neither show the "Shadow buffer allocated" message that Chris Wilson said we should expect: http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007924.html So However i've rapidly rebooted (only up to the GDM prompt) to see that the driver works even with 2.6.34, 2.6.35-rc6 and 2.6.35 (the latter yet without visible mouse pointer, as reported in #592415). I'm available to test every new update of the intel driver and i've taken the liberty to cc Chris Wilson to make him aware of these tests. Ciao. Cesare. --- X log with shadow patch and 2.6.32-21 (KMS blacklisted in kernel code) [...] (EE) open /dev/fb0: No such file or directory (EE) intel(0): No kernel modesetting driver detected. (II) UnloadModule: "intel" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found --- X log with shadow patch and 2.6.32-20 (KMS enabled with i915.modeset=1) X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 i686 Debian Current Operating System: Linux tommaso 2.6.32-5-686 #1 SMP Thu Aug 12 13:38:27 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=07b633c9-1242-48ee-a6f4-f37c43f639fd ro quiet lapic hpet=force i915.modeset=1 Build Date: 24 August 2010 02:59:40PM xorg-server 2:1.7.7-4 (Julien Cristau ) Current version of pixman: 0.16.4 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: Sun Aug 29 21:02:50 2010 (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No device specified for screen "Default Screen Section". Using the first device section listed. (**) | |-->Device "intel" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. Entry deleted from font path. (WW) The
Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
Kamen Naydenov wrote: I've installed http://snapshot.debian.org/archive/debian/20100813T030028Z/pool/main/l/linux-2.6/linux-image-2.6.32-5-686_2.6.32-20_i386.deb and X works Works because in this configuration you are using KMS. But i suppose that if you disable KMS by passing i915.modeset=1 to that kernel, your system will hang. Can you confirm? Pay attention to /etc/modprobe.d/i915-kms.conf: i don't know if it overrides the kernel parameter. Just to be sure i renamed it. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c784240.3010...@gmail.com
Bug#594623: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On 08/27/2010 11:45 PM, Julien Cristau wrote: Does the legacy driver work with UMS at all (on a different kernel, e.g.)? I've now tried to downgrade the .32 kernel to 2.6.32-20 and rebooting passing i915.modeset=0 to the kernel and without the file /etc/modprobe.d/i915-kms.conf (which contains "options i915 modeset=1"): the system hard freeze, the same with 2.6.32-21. I've also tried (don't know if it make sense) with 2.6.34-1~expermental.2, always with i915.modeset=0: same freeze. Ciao. Cesare. -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c783def.8030...@gmail.com
Bug#594623: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
Package: xserver-xorg-video-intel Version: 2:2.12.0+legacy1-1 Severity: normal I cc the kernel team, since i believe it is something that relates to them also. I have the same problem as reported by Kamen: when GDM try to start, the screen goes black and the CPU fan starts to go at full speed (as if something is hanging in a loop) and the system stops responding completely. After reboot i can see nothing in syslog or X.log. Before this version, I was using 2.12.0 from experimental with KMS and that worked well with 2.6.32, .34, .35 (but only with .35rc*, because with .35 i cannot see the mouse pointer, as explained in #592415). In the past, from time to time i experienced random system freeze or X crash due to error like this (as reported by Kamen in #580705): [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung [13983.076059] render error detected, EIR: 0x But with newer kernel and/or newer Intel X driver, the situation went better and they were rare with 2.6.34 and 35. With 2.6.35 and 2.12.0 i'm not sure if it happened at all. I guess the decision to disable KMS support for i855 was taken in concert with the kernel team, since simultaneously they disabled the support in the kernel, as we can see in the changelog for 2.6.32-21: [x86] i915: Blacklist i830, i845, i855 for KMS (Closes: #568207, #582105, #593432, #593507) For #582105 i admit i've never tried to close the lid, but the other three never happened to me. But the reporters have i830, while Kamen and i have i855. I know that these old chipset are problematic, but, speaking for *my* i855, i can say that the latest combination of kernel/x-driver/KMS worked well and i hope that the X Strike Force and Kernel Team will reconsider to enable KMS for at least i855. At least the Kernel Team, since this x-driver seems to work fine with a KMS enabled kernel (the one i'm using now). And i have a question for the X developers, since from the X.log i cannot understand: if i boot with a KMS enabled kernel, like 2.6.35-rc6, in which mode the x-driver will function? To me seems KMS/UXA. Cesare. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Feb 11 2007 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1725304 Aug 24 17:04 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) /etc/X11/xorg.conf does not exist. Kernel version (/proc/version): Linux version 2.6.35-rc6-686 (Debian 2.6.35~rc6-1~experimental.1) (b...@decadent.org.uk) (gcc version 4.4.4 (Debian 4.4.4-7) ) #1 SMP Mon Jul 26 09:46:49 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 28248 Jul 23 04:03 /var/log/Xorg.1.log -rw-r--r-- 1 root root 28275 Aug 16 03:55 /var/log/Xorg.20.log -rw-r--r-- 1 root root 27876 Aug 27 22:12 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 i686 Debian Current Operating System: Linux tommaso 2.6.35-rc6-686 #1 SMP Mon Jul 26 09:46:49 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.35-rc6-686 root=UUID=07b633c9-1242-48ee-a6f4-f37c43f639fd ro quiet lapic hpet=force i915.modeset=1 Build Date: 24 August 2010 02:59:40PM xorg-server 2:1.7.7-4 (Julien Cristau ) Current version of pixman: 0.16.4 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 Aug 27 21:20:05 2010 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (==) No Layout section. Using the first Screen section. (==) No screen section available. Using defaults. (**) |-->Screen "Default Screen Section" (0) (**) | |-->Monitor "" (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/Type1,
