Video Bug

[CrashedAgain]

I cna't believe I'm the only one who has experienced this bug since I have consistently experienced it on three different computers using three different Knoppix versions (3.1,3.2&3.3). I get little 'boxes' appearing in the screen. On my laptop, it is bands or splotches of color mess instead of clearly defined boxes.
Anyway, I think I have found a solution but it's in German & I need a translator. Please somebody check out:
http://www.linuxwiki.de/KDE/i810Bug
& translate to english for me.
It appears to be telling me to include the "XaaNoOffscreenPixmaps" option in XF86Config-4 which I have tried & it appears to work but I would like to know what else is being said.
Thanks

[Stephen]

I cna't believe I'm the only one who has experienced this bug since I have consistently experienced it on three different computers using three different Knoppix versions (3.1,3.2&3.3). I get little 'boxes' appearing in the screen. On my laptop, it is bands or splotches of color mess instead of clearly defined boxes.
Anyway, I think I have found a solution but it's in German & I need a translator. Please somebody check out:
http://www.linuxwiki.de/KDE/i810Bug
& translate to english for me.
It appears to be telling me to include the "XaaNoOffscreenPixmaps" option in XF86Config-4 which I have tried & it appears to work but I would like to know what else is being said.
Thanks

Have you tried Free Translation or a post to the developers list someone there may translate it for you.

[CrashedAgain]

Hadn't known about free translation. It made a rather interesting literal translation of the message which I have included below. It's good enough to get the general drift of the message. I would like to have included the screenshot of the bug from the original post but I don't know how to attch an image in this forum. Anyone interested can goto the original site above to view it.
Once again, am I the only Knoppix user to experience this bug? Then why me? I've been good, I've been trying to migrate away from Win$, honest I have!


>>>
Ugly strips in KDE-strips

There is a bow that can the representation of KDE-strips, menu bars and toolbars, roll beam and the Kontrollleiste KDE/Kicker, sometimes also the graphic contents of KDE-windows, considerably verunstalten. This bow steps only on in combination of KDE-uses and the XFree86-Treiber I810 for the of the same name chip sentence of Intel and its relative, in the moment officially only I815. in addition must obviously yet certain unknown conditions come in order to release it. Probably the bow in the driver I810 is to be sought, not in KDE. Because it emerges however in the truest sense of the word "obviously" always in KDE, it was reported as a bow always in KDE, that said there developer: "definitely need a KDE problem", "display adapter driver problem", and then the thing in the Sande passed.

Meanwhile it becomes however always narrower on circle. (The little tick, see bow, has it ventured, on my monitor to appear.) Nevertheless there are already some WorkArounds. Open question is, is current to which moment and in which version of XFREE86, 4.2.0 that bow geFixt will be. He who is interested in the dirty details of the vermin fight, can in the archive of the Xpert-MailingListe of XFREE86 under I810 + KDE display corruption look over, where appropriate also in later months: replace "June" in the Adresszeile of the browser by "July" etc.

"I have the thing however now on my screen. Make what I then now?"

Preserve quiet, eats durchatmen, the thing no holes in the screen. - There is there however a nice screen more prettily: try xlock-mesa -nolock -fashion bow once on the command line. Do not interrupt to quickly, becomes first after a while interesting, like in the correct life, has other beginning conditions also in each start. - For our actual problem however a WorkAround is here the means of the choice.

WorkAround there are three possibilities in the principle:

* If you this solution accepts half-way, you use 1024 xs 768. This solution has certain characteristics that have not the other, therefore the bow does not step up. For the transposition, the XFree86-Konfigurationsprogramm of your Linux distribution recommends itself.
* Obviously also a depth of color of 24bpp (Truecolor) can use one. That has however as a consequence, that the so named Graphics & memory controller Intel 82810, one of both parts of the i810-Chipsatzes, 50% more data process must than in 16bpp. There the i810-Chipsatz a graphic card saves is directed - and therewith costs for the total computer - it on a part of the main memory as a graphics storage. And here, at the data stream to the main memory, becomes it therefore in half-way high solutions narrow. Except in very little solutions XFREE86 will allow this attitude therefore not at all. But also then is to be feared that the remainder leads at storage bandwidth, that remains here yet to the provision of the remaining computer remaining, to achievement losses. You should select counts nevertheless this solution, like above: XFree86-Konfigurationsprogramm of your Linux distribution.
* In all felling of other remains only the possibility to disengage so named acceleration. In addition you must change the configuration file XF86Config. Caution! This file is one of the few with whose change one can grill himself parts of its hardware. After the FHS 2.2, you would have to find this file under /etc/X11/XF86Config, it can be however also yet under /etc/XF86Config. If it gives here several files of this type with different Suffixen, to XF86Config-4, one more exactly must observe the thing something else: experts ask, are except in *.bak, *.old, *.save, that backups. To change around this file you need root-rights. Best first even a security generate: cp /etc/X11/XF86Config /etc/X11/XF86Config.bak or correspondingly. Opening you then the original file XF86Config with the editor of your choice and seek you the section Device. In the principle, only the line Driver "i810 must stand between Section "Device" and EndSection", must that remainder can, however not. Let this remainder simply, is how it:

Section "Device"
BoardName "82810 CGC"
BusID "0:1:0"
Driver "i810"
identifier "Device[0]"
VendorName "Intel"
video ram 16384
options "dpms"
EndSection

Here you must insert now in addition one of the following lines.

Option "NoAccel"
option "XaaNoOffscreenPixmaps"
option "XaaNoPixmapCache"
option "XaaNoScreenToScreenCopy"

NoAccel disengages all accelerations, is therefore the wood hammer method. Open question remains first of all, which costs the other three at the least, perhaps someone can contribute in addition something else. Your Section "Device" so could look now therefore:

Section "Device"
BoardName "82810 CGC"
BusID "0:1:0"
Driver "i810"
identifier "Device[0]"
VendorName "Intel"
video ram 16384
options "dpms"
options "XaaNoOffscreenPixmaps" EndSection

Once again: you respect on that that this is the single variation, that you distinguished. Especially HorizSync and VertRefresh in the Section "monitor" may not be changed if you do not know genauestens, what you do.

Store so, file, newly start would have to run XServer, and the thing. If your monitor complied fiept or flackert or similar what not however were allowed to be, if you with the projecting warnings, you kill the server immediately: Strg-old-setback or engl. Keyboard: CTRL-old-Backspace. Produce the secured file in this case rather again and seek yourself you an expert on the spot.

-Dirk Stöffler 2002-06-16 15:27:03 Dirk Stöffler

Alternative solution

The purported bow do not know I to be sure, but in störischen notebooks, I take simply the VESA-driver and put the solution already in the LILO firmly, then klappts always! I think, would function that here also in any case.

Anm. : something contains this side too many meaningless to the left -ThomasWaldmann 2002-06-16 19:21:19

Do I not understand links nichtssagend yet correctly with? If yes, it are finally should grow already again two less, No Gschtäd, it, the sites. If no, can I "nichtssagend" in view of the potential contents of these subjects not entirely nachvollziehen. -- Dirk Stöffler 2002-06-16 19:54:05

With "nichtssagend" I meant to the left to concepts as well as: security, backup, editor, Truecolor, etc. - It no lexicon of the 10,000 words of the "computer language" should become here. Link level of somewhat higher therefore please first on one, swells otherwise that the thing unnecessarily up. -ThomasWaldmann 2002-06-19 14:44:08

[LRutker]

http://www.knoppix.net/forum/viewtopic.php?p=32654

[rohandhruva]

no, u r not alone. i face a similar problem! did u solve it? is htere any permanent solution ?
thnx,
rohan.

[CrashedAgain]

no, u r not alone. i face a similar problem! did u solve it? is htere any permanent solution ?
thnx,
rohan.

I have edited /etc/X11/Xf86Config-4 and XF86config-4.in:

Section "Device"
 ### Available Driver options are:-
        # sw_cursor is needed for some ati and radeon cards
        #Option     "sw_cursor"
        #Option     "hw_cursor"
        #Option     "NoAccel"
        #Option     "ShowCache"
        #Option     "ShadowFB"
        #Option     "UseFBDev"
        #Option     "Rotate"

# Intially I used this:
# Option       "XaaNoOffscreenPixmaps"

# Then changed to this which I copied from Mandrake 9.2 setup
 VideoRam 16384
 Option "DPMS"
 Option "XaaNoPixmapCache"

# Both seemed to work equally well.

 Identifier  "Card0"
# The following line is auto-generated by KNOPPIX mkxf86config
 Driver      "i810"
 VendorName  "All"
 BoardName   "All"

xf86config-4.in is the 'master template' used if your system generates a new xf86config-4 so edit it as well as xf86config-4.