Since switching to the xf86-video-intel driver, I am seeing pixel corruption in xterm windows. This did not happen while using the xf86-video-i810 driver. The pixel corruption consists of collections of lit pixels where there are no characters and, occasionally, also unlit pixels where there are characters. These corrupted areas scroll with the xterm. The corruption happens only on wide xterms, seemingly when columns >= 158, which is often the case for me as I use a 1600x1200 display and an xterm font size that can fit up to 175 columns in a maximized xterm window. It also seems to happen only at the left of the screen. I have also noticed that if I move a large xterm window so that it is partially off the screen, the pixel corruption ceases once there are under 158 columns of the xterm window on the screen. As I mentioned, my display is 1600x1200. An xterm window of 158 columns is 1440 pixels wide. The height of the window makes no difference. An example of the corruption can be seen here: http://opal.com/jr/xterm-corruption.gif I have marked the corruption using red ovals. There are many red ovals! (NB: download and view this at full size to avoid further distortion due to your browser shrinking the image.) Running an xterm from a remote host back to the local display also results in the same corruption. Is there a known solution for this? FreeBSD-7.0BETA1.5 xorg-7.3_1 xf86-video-intel-2.1.1 xterm-229 Thanks, -jr
In case it helps, the same problem has been observed on FreeBSD 6.3-STABLE Xorg-6.9.0 i810_drv.so, module version = 1.4.1, Chipset 852GM/855GM, 1400 x 1050 xterm-222
I probably have a related problem. I am using X.org 1.3.0 on a Vaio UX1XN with an Intel 945 type chipset. I have a row of stray pixels on screen line 736 (counting from 0). This happens in dual head mode, but in single head mode I also have this, albeit on another line, since the internal display has only 600 lines. This line is annoying, since it destroys the rendering when I e.g. scroll a webpage in Konqueror.
Just found that this problem goes away if I change the BIOS PnP-OS setting from YES to NO.
(In reply to comment #3) > Just found that this problem goes away if I change the BIOS PnP-OS setting from > YES to NO. > Sadly, though, it is now back. BIOS settings are unchanged. So, ignore that.
Further investigation has unearthed that this problem happens when the CPU frequency is lowered to low levels. FreeBSD has a utility, powerd, which adjusts the CPU frequency based on system load. When the CPU frequency is set low, these pixel corruptions happen. When the CPU freq is high they do not happen: everything is normal. Disabling powerd and manually adjusting the CPU frequency gives these results: # sysctl dev.cpu.0.freq_levels dev.cpu.0.freq_levels: 3176/-1 2779/-1 2382/-1 1985/-1 1588/-1 1191/-1 794/-1 397/-1 CPU freq from 3176 to 1191 causes no problems. CPU freq at 794 or 397 causes pixel corruptions.
Reassign freebsd-only bug away from me.
This was a problem on FreeBSD-6.3. Disabling powerd (so that CPU is always at full speed) was a good work-around. That host is now on FreeBSD-7.2 with xorg-7.4 and associated versions. Problem no longer exists.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.