search for: aterm

...cently got e.g. trivial/tri to work. Trivial/tri-repeat is a version of trivial/tri, that cycles the colors and renders as fast as possible (RAFAP). Another RAFAP application is glxgears, which still shows only a black window. When a RAFAP application is running, moving focus to a terminal window (aterm, xterm) sometimes paints a rectangle filled with a solid color into the terminal window. Examples of this are seen in the attached screenshot. The color of the solid color fill (SCF) is not random: the aterm cursor is a yellow block, the irc client has a blue status bar that updates occasionally, a...

...ot;exa: preparation for reintroducing driver-controlled pixmaps" As you see from the screen capture, which oddly enough looks just like what I saw with my eyes, the 2d rendering is quite broken. More specifcally, pixmap handling, it seems. I should have a nice background picture, and only one aterm window drawn. There really is just one aterm, I moved it a few times. With commit 60c8bb1391a51188a4981b4936c190c149b79b7f "default to autodetecting whether to enable the driver's kms paths", I tried to disable UTS, DFS and EXA render, but none of them changed anything. Currently I&...

...er it's still dithered to 8bpc, not "real" 10bpc. > > - things generally work in X -- dri2 and dri3, xv, and obviously > > regular X rendering / acceleration > > - lots of X software can't handle 30bpp modes (mplayer hates it for > > xv and x11 rendering, aterm bails on shading the root pixmap, probably > > others) > > > > I'm also told that with DP, it should actually send the higher-bpc > > data over the wire. With HDMI, we're still stuck at 24bpp for now > > (although the hardware can do 36bpp as well). This is wh...

...up smoother than an 8bpc gradient. However it's still dithered to 8bpc, not "real" 10bpc. - things generally work in X -- dri2 and dri3, xv, and obviously regular X rendering / acceleration - lots of X software can't handle 30bpp modes (mplayer hates it for xv and x11 rendering, aterm bails on shading the root pixmap, probably others) I'm also told that with DP, it should actually send the higher-bpc data over the wire. With HDMI, we're still stuck at 24bpp for now (although the hardware can do 36bpp as well). This is why my gradient result above was still dithered. Th...

...SERVE, -1, 0) = -1 E??? (errno -2147483648) old_mmap(0x110000, 267321344, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x110000 open("?L$@?t$|?L$t$`?4$?", O_RDONLY) = -1 ENOENT (No such file or directory) .... and from now on only monkey characters because my aterm font crases:( plese can u help me with this problem anyone?? Ups almost forgot: Linux mihaiv 2.4.26-gentoo-r11 #1 Mon Nov 15 09:49:54 EET 2004 i686 Intel(R) Pentium(R) 4 CPU 1.70GHz GenuineIntel GNU/Linux now if there is anything more that you want/need to know please let me know I've tr...

...l dithered to 8bpc, not "real" 10bpc. >> > - things generally work in X -- dri2 and dri3, xv, and obviously >> > regular X rendering / acceleration >> > - lots of X software can't handle 30bpp modes (mplayer hates it for >> > xv and x11 rendering, aterm bails on shading the root pixmap, probably >> > others) >> > >> > I'm also told that with DP, it should actually send the higher-bpc >> > data over the wire. With HDMI, we're still stuck at 24bpp for now >> > (although the hardware can do 36bpp a...

...> gradient. However it's still dithered to 8bpc, not "real" 10bpc. > - things generally work in X -- dri2 and dri3, xv, and obviously > regular X rendering / acceleration > - lots of X software can't handle 30bpp modes (mplayer hates it for > xv and x11 rendering, aterm bails on shading the root pixmap, probably > others) > > I'm also told that with DP, it should actually send the higher-bpc > data over the wire. With HDMI, we're still stuck at 24bpp for now > (although the hardware can do 36bpp as well). This is why my gradient > result...

...t; gradient. However it's still dithered to 8bpc, not "real" 10bpc. > - things generally work in X -- dri2 and dri3, xv, and obviously > regular X rendering / acceleration > - lots of X software can't handle 30bpp modes (mplayer hates it for > xv and x11 rendering, aterm bails on shading the root pixmap, probably > others) > > I'm also told that with DP, it should actually send the higher-bpc > data over the wire. With HDMI, we're still stuck at 24bpp for now > (although the hardware can do 36bpp as well). This is why my gradient > result...

...iled; code 0x80040154. Click Retry to try again, Ignore to procedd anyway (not recommended), or Abort to cancel installation." I clicked on Ignore after Retry just kept repeating this message. So far that seems to have completely hung the installation process. Here is what is going on in my aterm: Please use the registry key HKEY_CURRENT_CONFIG\Software\Fonts\LogPixels to set the screen resolution and remove the "Resolution" entry in the config file err:ntdll:RtlpWaitForCriticalSection section 0x40b468 "?" wait timed out in thread 000a, blocked by 0009, retrying (60 sec...

...installed R and found R did not react on my command plot (I use command line in terminal). It did not give me any error message, either. All it did was just giving out a new command prompt--no reaction to the plot command. I suppose whenever I gives out a command of plot, it will invoke the AquaTerm for a small graph, as I experience in octave. What can I do for it? Many thanks, Minyu Chen