If I use gentoo-2.6.35-r12 with my Intel 855GM and the same kernel config as for gentoo-sources-2.6.34-r12 the screen blanks after ~15min every ~5min or 10sec. There is no relevant systemlog I can find... There are a lot of fbdev errors in Xorg.log I use no xorg.conf with hal enabled Reproducible: Always Steps to Reproduce: 1.use gentoo-sources-2/6/35-r12 with Intel 855GM 2.start X 3.wait a little Actual Results: screen goes blank from time to time for ~2-3seconds Expected Results: not go blank I'll attach Xorg.0.log, .config and emerge --info
Created attachment 255355 [details] Xorg.log with fbdev errors
Created attachment 255357 [details] kernel config
Created attachment 255359 [details] emerge --info
I have the same fbdev errors in Xorg.log with 2.6.34 without problems it also blanks on console in runlevel 1
Is there a reason why you use the fbdev instead of intel driver? Also attach dmesg.
Created attachment 255371 [details] dmesg on 2.6.35-r12 Thanks, that you have a look at this, this problem started with 2.6.35-r9 but I didn't report it then, since I wanted to wait for the final version and reverted back to 2.6.34 I had some trouble in the past, so I run Xorg on fbdev. Anyway, this also happens on console, so it's not X related. attached dmesg
This is dmesg after you got the screen blanks or not? Probably unrelated, but you may want to get rid of the APIC warnings by enabling IOAPIC in your BIOS, or if there is no such option, booting with the lapic kernel parameter.
(In reply to comment #7) > This is dmesg after you got the screen blanks or not? > > Probably unrelated, but you may want to get rid of the APIC warnings by > enabling IOAPIC in your BIOS, or if there is no such option, booting with the > lapic kernel parameter. > The dmesg was just after booting into runlevel 1 During boot, it blanked once after loading the kernel(changing the resolution on frambuffer to 1024x768, which is normal) and then while the services started a second time, before it showed the login prompt. I logged in, no blanking, and created the dmesg, then rebooted again without waiting for the next time it happens. As I said sometimes it takes up to 5-10min before it happens and then usually 1-3 times within 1min. Later I will wait after login in runlevel 1 for the blanking and then create another dmesg.
Created attachment 255421 [details] dmesg straight after blank kernel parameter: fast quiet lapic init 1 logged in, waited ~6min blank, made dmesg system logs in /var/log/messages were ~6min old do you want me to enable a certain kernel debug option?
The more I read about it, it appears the intelfb is fubar in 2.6.35 The Ubuntu guys advise to use the "intel" with Xorg and they probably use uvesafb or vesa for framebuffer.
Don't use fbdev, this Xorg driver isn't supported on top of inteldrmfb. Please try with xf86-video-intel instead. Thanks
For self reference (in layman terms): I have the Intel driver 915 and KMS enabled in the kernel: CONFIG_DRM_I915=y CONFIG_DRM_I915_KMS=y and should not disable it, right? The xf86-video-intel is the only supported driver for X on an intel GPU? The vesafb and uvesafb drivers are obsolete? I have the problem not only in X but on console (VT1 in single user mode), when there is no X running. "You should instead enable the intel DRM driver which provides a "fake" framebuffer driver (usually referred to as inteldrmfb). This will allow you to both have fbconsole running on VT1-6 and X on VT7 using the X driver xf86-video-intel." I'll disable all framebuffer drivers and drm+kms and see if the blanking still happens on console. Maybe it's unrealted to the framebuffer driver?
I guess I wasn't clear enough (but things are complex, so it's not easy to get things right on the first try, bear with me). As far as linux graphics are concerned, there are 4 kinds of drivers : Kernel DRM drivers: - i830 - i915 Kernel Frame Buffer drivers: - vesafb - uvesafb - intelfb - inteldrmfb ("fake" driver provided by inteldrm) User-Space X driver: - xf86-video-vesa - xf86-video-fbdev - xf86-video-intel User-Space Mesa driver (for 3D, just mentioning them for the sake of completeness): - i915 - i965 Up until recently, you could mix and match (almost) any of those drivers and still have something that worked more or less ok. Now, things are much simpler: - i915 for the kernel DRM driver - inteldrmfb (which is the *only* working option if you want a frame buffer driver) - xf86-video-intel - i915/i965 for mesa (depending on which hardware you own, VIDEO_CARDS=intel on mesa takes care of this for you) This is now the *only* supported option if you want something that works. Don't use xf86-video-fbdev, don't enable other frame buffer drivers in your kernel config. Thanks
Hi, I have no problems in 2.6.35-r3... Same config, same settings and fbdev on top of intel frambuffer in the kernel (i915)+KMS not sure what's wrong with 2.6.35. Unfortunately I read today on linux.com that 2.6.35 will be one of the longterm supported versions. I'll wait until 2.6.36 goes stable and then remove the ~x86 keyword again.
(In reply to comment #14) > Hi, I have no problems in 2.6.35-r3... > Same config, same settings and fbdev on top of intel frambuffer in the kernel > (i915)+KMS > not sure what's wrong with 2.6.35. Unfortunately I read today on linux.com that > 2.6.35 will be one of the longterm supported versions. > > I'll wait until 2.6.36 goes stable and then remove the ~x86 keyword again. > dammit I meant 2.6.36-r3
