Desktop is not using full screen space

Hi, Need help with the following problem: Desktop is not using full available screen space. The system was working fine in Debian Etch. Then it was upgraded to Debian Lenny. Hardware remains the same, no changes were made. After the upgrade to Lenny, the picture doesn't use the whole available

Re: Intel Graphics question

On Thu, 19 Feb 2009 22:11:37 -0500, Joseph Smith wrote: > > > > On Fri, 20 Feb 2009 10:19:49 +0800, Zhenyu Wang > wrote: >> On 2009.02.20 07:43:21 +0800, Joseph Smith wrote: >>> >>> Hello, >>> I am a coreboot (http://www.coreboot.org) developer working mostly > Intel >>> chipsets. Currentl

next release of xineramaproto

Given that last years changes to xineramaproto appear to impact a number of applications (on my system anyway), could anyone tell me when the next release of xineramaproto will occur? ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedes

Re: Intel Graphics question

On Fri, 20 Feb 2009 10:19:49 +0800, Zhenyu Wang wrote: > On 2009.02.20 07:43:21 +0800, Joseph Smith wrote: >> >> Hello, >> I am a coreboot (http://www.coreboot.org) developer working mostly Intel >> chipsets. Currently I am working an set-top-box with an Intel chipset. I > am >> looking into i

Re: [intel 845G/GL] Status of xorg, xf86-video-intel, etc on 845

dolphinling wrote: > All the Xorg.0.logs from this are available at > http://dolphinling.net/xorglogs/ Oops, I meant to put my xorg.confs and kernel .configs there too. They're there now. -- dolphinling ___ xorg mailing list

Re: Intel Graphics question

On 2009.02.20 07:43:21 +0800, Joseph Smith wrote: > > Hello, > I am a coreboot (http://www.coreboot.org) developer working mostly Intel > chipsets. Currently I am working an set-top-box with an Intel chipset. I am > looking into implementing LVDS and TV-OUT support for various Intel GMCH's > for s

[PATCH] 64-bit issues in libx11

It seems xcb/x11 have some bugs related to sizeof(long), in concrete using 32 bit variables for dpy->request et al in AMD64. This patch fixes some crashes for me. diff -ur libx11-1.1.99.2/src/xcb_io.c libx11-1.1.99.2-a/src/xcb_io.c --- libx11-1.1.99.2/src/xcb_io.c2008-11-04 20:52:54.0

Re: Questions on How Xorg handle ACPI

On Fri, Feb 20, 2009 at 09:34:38AM +0800, Sheldon Zhao wrote: >So, vbetool saves and restores the video card state, and the Xorg don't >even know a S3/S4 happen? Either vbetool or the kernel graphics drivers. X only sees a VT switch. -- Matthew Garrett | mj...@srcf.ucam.org ___

Re: Questions on How Xorg handle ACPI

2009/2/18 Matthew Garrett > On Wed, Feb 18, 2009 at 10:41:31AM +0800, sheldon wrote: > > >I'm trying to find how Xorg handles ACPI (s3 and s4). It seems that > Xorg > >handles S3/S4( suspend and resume) is just the same as it process VT > >switching, for both the flow is WaitFofSomet

Re: Severe memory leaks make X.org unuseable

The resource usage has not changed much after it has been running. Though you are right, I think you are saying that the two 131 mb allocations are not actually real ram usage, but instead are just mappings of the video hardware address space. So basically that is not space consumed in RAM. This

Re: Severe memory leaks make X.org unuseable

milnser43...@yahoo.com wrote: > At the same time important backwards compatability upon which many of our > applications depend, have been removed including PEX, Ximage, MIT-SUNDRY, > XFree86-Misc, among others creating a massive incompatability headache. A > prime principle of the X.org project

Intel Graphics question

Hello, I am a coreboot (http://www.coreboot.org) developer working mostly Intel chipsets. Currently I am working an set-top-box with an Intel chipset. I am looking into implementing LVDS and TV-OUT support for various Intel GMCH's for set-top-boxes and possibly laptops starting right from the firm

Re: Severe memory leaks make X.org unuseable

On Thu, 2009-02-19 at 06:50 -0800, milnser43...@yahoo.com wrote: > > You forgot to volunteer to maintain them - not that I find > > you believable. The idea that anyone uses PEX is rather > > implausible. > > The number of apps which PEX, MIT_SUNDRY, and Ximage is probably a > rather small number

Re: Severe memory leaks make X.org unuseable

On Thu, 2009-02-19 at 07:58 -0800, milnser43...@yahoo.com wrote: > 2898 131072 0 - 131072 rwx /dev/mem > [...] > 30A51000 131072 4 - 131072 rwx /dev/mem > [...] > Total Kb 277656940862607908 You have what I assume is the card's video memory mapped

Re: libX11-6.2.1 and pkg-config 0.23

Pedro Izecksohn wrote: > It came from http://xlibs.freedesktop.org/release/ > BTW: What is the logic behind xlibs version numbers? xlibs hasn't been used in many years - it was a brief experiment, long ago abandoned.The libraries that are currently maintained and relased are at: http:/

[intel 845G/GL] Status of xorg, xf86-video-intel, etc on 845

I've been trying to run the latest xorg components on an i845 for a while now, and I haven't found a good set of component versions + configurations that works well. Here's info on the most recent release + current git versions of stuff. If there's anywhere else I should put this (e.g. individual p

Re: openSUSE 11.1 and Intel graphics chip

Maybe try the http://lists.freedesktop.org/mailman/listinfo/intel-gfx list? Maarten. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg

Re: libX11-6.2.1 and pkg-config 0.23

On Thu, Feb 19, 2009 at 10:58 AM, Pedro Izecksohn wrote: > It came from http://xlibs.freedesktop.org/release/ > > BTW: What is the logic behind xlibs version numbers? Right, the old xlibs releases. You want the newer xorg releases. You can find them all here: http://xorg.freedesktop.org/releases

Re: libX11-6.2.1 and pkg-config 0.23

It came from http://xlibs.freedesktop.org/release/ BTW: What is the logic behind xlibs version numbers? On 2/19/09, Dan Nicholson wrote: > On Thu, Feb 19, 2009 at 10:45 AM, Pedro Izecksohn > wrote: >> Who will fix it up there? Who has git write permission? >> >> How none saw this before me?

Re: libX11-6.2.1 and pkg-config 0.23

On Thu, Feb 19, 2009 at 10:45 AM, Pedro Izecksohn wrote: > Who will fix it up there? Who has git write permission? > > How none saw this before me? The original developers did not try configure? Oh, I just looked in git and it's already been fixed for a while. It should be in libX11-1.1.5. Wher

Re: libX11-6.2.1 and pkg-config 0.23

Who will fix it up there? Who has git write permission? How none saw this before me? The original developers did not try configure? This bugs affects thousands advanced users. On 2/19/09, Dan Nicholson wrote: > On Thu, Feb 19, 2009 at 12:21 AM, Pedro Izecksohn > wrote: >> In libX11-6.2

Re: openSUSE 11.1 and Intel graphics chip

A few day ago I posted this problem. I am totally stuck and cannot get the xserver working. Can anyone help me on this issue or at least point me to a resource that will be of assistance. Sincerely, Dave - Original Message > From: Dave > To: xorg@lists.freedesktop.org > Sent: Sat

Re: libX11-6.2.1 and pkg-config 0.23

On Thu, Feb 19, 2009 at 12:21 AM, Pedro Izecksohn wrote: > In libX11-6.2.1: > > The configure piece below is wrong, (or pkg-config is buggy) because > > pkg-config --cflags xproto > > prints a line-feed only and keysymdef.h exists in my system and it is in > the right place. > > I'm using pkg-

Re: Severe memory leaks make X.org unuseable

On Thu, 2009-02-19 at 06:18 -0800, milnser43...@yahoo.com wrote: > Earlier on freebsd 7.0 pmap back in Nov. was not available and would > not compile right. But now it seems to have compiled on 7.1 and is > working ok. It reports memory allocations but does not report line > numbers. I am going to

Ximage's byte_order field

Am I allowed to change the value of the XImage byte_order field? And if I do, will subsequent XPutImage() calls do the "right thing"? Does the value of byte_order default to the client's byte order? I have a memory based frame buffer from another app that I'd like to use XCreateImage() and XPut

Re: Severe memory leaks make X.org unuseable

On Thu, 2009-02-19 at 09:18 +, John Tapsell wrote: > 2009/2/19 Maciej Grela : > > 2009/2/19 milnser43...@yahoo.com : > >> There are very serious and severe memory leaks under X.org with the savage > >> driver. I am on FreeBSD. This is a very serious problem as it consumes all > >> system memo

Re: Severe memory leaks make X.org unuseable

On Thu, Feb 19, 2009 at 06:50:38AM -0800, milnser43...@yahoo.com wrote: > I dont think that backwards compatability code should be removed "just > because we dont dont think anyone uses it anymore", or "because we can". As > far as I am aware these extensions were not causing any problems and I c

Re: Severe memory leaks make X.org unuseable

--- On Thu, 2/19/09, Jim Gettys wrote: > From: Jim Gettys > Subject: Re: Severe memory leaks make X.org unuseable > To: milnser43...@yahoo.com > Cc: xorg@lists.freedesktop.org > Date: Thursday, February 19, 2009, 9:58 AM > On Thu, 2009-02-19 at 06:50 -0800, milnser43...@yahoo.com > wrote: >

Re: Severe memory leaks make X.org unuseable

Alan Cox wrote: > On Wed, 18 Feb 2009 18:22:21 -0800 (PST) >> At the same time important backwards compatability upon which many of our >> applications depend, have been removed including PEX, Ximage, MIT-SUNDRY, >> XFree86-Misc, > > You forgot to volunteer to maintain them - not that I find you

Re: Severe memory leaks make X.org unuseable

On Thu, 2009-02-19 at 06:50 -0800, milnser43...@yahoo.com wrote: > > The number of apps which PEX, MIT_SUNDRY, and Ximage is probably a rather > small number but certainly there have been apps written to use it. As for > Xfree86-misc, I have heard that some modern screensavers use it to provid

Re: [PATCH] xorg-macros.m4.in minor fix for incorrect warning message

On Wed, Feb 18, 2009 at 2:52 PM, Dan wrote: > Hi - > > One of the warnings in xorg-macros.m4.in is wrong, it prints out the > wrong version when it says "requires version x.x". Patch pasted below > against http://cgit.freedesktop.org/xorg/util/macros/tree/xorg-macros.m4.in > - not a proper git pat

Re: very slow performance of glxgears (68 fps)

On Thu, 2009-02-19 at 20:46 +0600, Mikhail Gusarov wrote: > Twas brillig at 09:44:35 19.02.2009 UTC-05 when j...@freedesktop.org did gyre > and gimble: > > JG> So if memory is right by the pixels the concept of vertical retrace > JG> may become moot, conceivably, someday. > > It is already, fo

Re: Severe memory leaks make X.org unuseable

--- On Thu, 2/19/09, Alan Cox wrote: > From: Alan Cox > Subject: Re: Severe memory leaks make X.org unuseable > To: milnser43...@yahoo.com > Cc: xorg@lists.freedesktop.org > Date: Thursday, February 19, 2009, 5:47 AM > On Wed, 18 Feb 2009 18:22:21 -0800 (PST) > "milnser43...@yahoo.com" > wrot

Re: very slow performance of glxgears (68 fps)

Twas brillig at 09:44:35 19.02.2009 UTC-05 when j...@freedesktop.org did gyre and gimble: JG> So if memory is right by the pixels the concept of vertical retrace JG> may become moot, conceivably, someday. It is already, for e-ink displays. -- pgplvbV1kRRYF.pgp Description: PGP signature _

Re: very slow performance of glxgears (68 fps)

On Thu, 2009-02-19 at 13:03 +0100, Matthias Hopf wrote: > On Feb 18, 09 12:58:49 -0500, Jim Gettys wrote: > > On Wed, 2009-02-18 at 10:49 -0700, McDonald, Michael-p7438c wrote: > > > Dumb question: Do LCD/Plasma/OLED/... Actually have vertical retrace? > > > Does the vblank interval approach 0? >

Re: Severe memory leaks make X.org unuseable

Earlier on freebsd 7.0 pmap back in Nov. was not available and would not compile right. But now it seems to have compiled on 7.1 and is working ok. It reports memory allocations but does not report line numbers. I am going to paste a dump of what it provides of the X.org process here. I have al

Re: Severe memory leaks make X.org unuseable

On Thu, 19 Feb 2009, John Tapsell wrote: > 2009/2/19 Maciej Grela : >> 2009/2/19 milnser43...@yahoo.com : >>> There are very serious and severe memory leaks under X.org with the >>> savage driver. I am on FreeBSD. This is a very serious problem as it >>> consumes all system memory adn causes oth

Re: libX11-6.2.1 and pkg-config 0.23

Bill Crawford wrote: > In theory a lot of them shouldn't need to, because they're installed in a > subdirectory of /usr/include, and you're intended to include > ... I guessed that also, but couldn' get it nailed down. Anyway, it looks more like the OP's script is broken. ___

Re: libX11-6.2.1 and pkg-config 0.23

On Thursday 19 February 2009 12:09:30 Simon Thum wrote: > Sorry for the noise. I haven't found the issue, but a majority of .pc's > in my system doesn't output cflags. So it's something configuration- or > pkc-config related. In theory a lot of them shouldn't need to, because they're installed in

Re: Help please, with compile drm

Thank you all for your comments! On Tue, Feb 17, 2009 at 10:39 PM, Dan Nicholson wrote: > On Mon, Feb 16, 2009 at 10:22 PM, tac wrote: > > ps. I was running into this when I type make install from the source: > > Making install in libdrm > > make: Fatal error in reader: Makefile, line 658: Unex

Re: libX11-6.2.1 and pkg-config 0.23

Simon Thum wrote: > Pedro Izecksohn wrote: >> pkg-config --cflags xproto >> >> prints a line-feed only and keysymdef.h exists in my system and it is in >> the right place. > Same here, on my local system (gentoo + X11 overlay). In my git tree it > gives a good-looking -I arg. Sorry for the noise.

Re: very slow performance of glxgears (68 fps)

On Feb 18, 09 12:58:49 -0500, Jim Gettys wrote: > On Wed, 2009-02-18 at 10:49 -0700, McDonald, Michael-p7438c wrote: > > Dumb question: Do LCD/Plasma/OLED/... Actually have vertical retrace? > > Does the vblank interval approach 0? > > LCD: yes > Plasma: yes > OLED: ? (still mostly v

Re: very slow performance of glxgears (68 fps)

On Feb 18, 09 14:40:34 +, John Tapsell wrote: > > So it is a validation tool, but not a benchmark. > > > > A benchmark - by definition - gives you performance figures that can be > > compared with other systems, which gives you a reasonable notion of > > which of the systems is better. > > Rig

Re: Severe memory leaks make X.org unuseable

On Wed, 18 Feb 2009 18:22:21 -0800 (PST) "milnser43...@yahoo.com" wrote: > There are very serious and severe memory leaks under X.org with the savage > driver You forgot to attach the fixes > At the same time important backwards compatability upon which many of our > applications depend, have

Re: Severe memory leaks make X.org unuseable

On Thu, 19 Feb 2009 09:18:39 + John Tapsell wrote: > 2009/2/19 Maciej Grela : > > 2009/2/19 milnser43...@yahoo.com : > >> There are very serious and severe memory leaks under X.org with the savage > >> driver. I am on FreeBSD. This is a very serious problem as it consumes all > >> system me

Re: Severe memory leaks make X.org unuseable

2009/2/19 Maciej Grela : > 2009/2/19 milnser43...@yahoo.com : >> There are very serious and severe memory leaks under X.org with the savage >> driver. I am on FreeBSD. This is a very serious problem as it consumes all >> system memory adn causes other applications to crash. It is totally >> unus

Re: libX11-6.2.1 and pkg-config 0.23

Pedro Izecksohn wrote: > pkg-config --cflags xproto > > prints a line-feed only and keysymdef.h exists in my system and it is in > the right place. Same here, on my local system (gentoo + X11 overlay). In my git tree it gives a good-looking -I arg. Though I never had problems building anything.

Re: Severe memory leaks make X.org unuseable

2009/2/19 milnser43...@yahoo.com : > There are very serious and severe memory leaks under X.org with the savage > driver. I am on FreeBSD. This is a very serious problem as it consumes all > system memory adn causes other applications to crash. It is totally unuseable > and intolerable and is si

libX11-6.2.1 and pkg-config 0.23

In libX11-6.2.1: The configure piece below is wrong, (or pkg-config is buggy) because pkg-config --cflags xproto prints a line-feed only and keysymdef.h exists in my system and it is in the right place. I'm using pkg-config --version 0.23 # # Find keysymdef.h # KEYSYMDEF="" for flag in