Re: Intel driver problem
Apparently, if I start xdm instead of running startx, it works OK. I will now try to find out why startx fails. Thanks for your help, Dirk Julien Cristau wrote: On Tue, Jan 5, 2010 at 10:09:47 +0100, Dirk De Becker wrote: [...] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) (**) Option "xkb_rules" "evdev" (**) Option "xkb_model" "evdev" (**) Option "xkb_layout" "us" (II) Dell Dell USB Keyboard: Close (II) UnloadModule: "evdev" (II) HID 04d9:1400: Close (II) UnloadModule: "evdev" (II) HID 04d9:1400: Close (II) UnloadModule: "evdev" (II) Power Button: Close (II) UnloadModule: "evdev" (II) Power Button: Close (II) UnloadModule: "evdev" This log looks like X starts up fine, and then the session ends. Are you sure it's not your session crashing or terminating prematurely, rather than an X problem? Cheers, Julien ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg <>___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Xorg crashes...
On 01/05/10 21:34, Ryan Daly wrote: > Would anyone be able to take a look at a bug report I filed with Ubuntu? > > My Xorg server keeps terminating on me and sends me back to the login > screen. I have obtained a number of backtraces, all of which are logged > in the bug report. The link to the bug report is below. > > https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/499484 > > I appreciate anyone who can shed some light on this for me. Thanks. > -- > > > This message and any files transmitted within are intended > solely for the addressee or its representative and may > contain company sensitive information. If you are not the > intended recipient, notify the sender immediately and delete > this message. Publication, reproduction, forwarding, or > content disclosure is prohibited without the consent of the > original sender and may be unlawful. > > Concurrent Technologies Corporation and its Affiliates. > www.ctc.com 1-800-282-4392 > > ___ > xorg mailing list > xorg@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/xorg > not sure whats going on, but by looking at the log I see some userspace tools erroring out(which should not keep the screen from going forward), but I also see something about fglrx not found.. could either mean that you haven't the xorg module, as well as the kernel module, or the fglrx module is crapping out with the xserver version(had this a while ago with fglrx, ended up switching to radeon); hope this helps. Justin P. Mattock ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
RE: [Intel-gfx] [ANNOUNCE] Intel 2009Q4 release
Stefan Dirsch wrote on Wednesday, January 06, 2010 1:00 PM: > On Tue, Jan 05, 2010 at 07:42:40PM -0800, Greg KH wrote: >> On Wed, Jan 06, 2010 at 10:02:06AM +0800, Jin, Gordon wrote: >>> Hi, >>> >>> We'd like to announce Intel 2009Q4 release package >>> (http://intellinuxgraphics.org/2009Q4.html), which consists of: >>> - xf86-video-intel 2.10.0 >>> - mesa 7.7 >>> - libdrm 2.4.17 >>> - Linux kernel 2.6.32 >>> - xserver 1.7.3 is recommended to use with this release >> >> I thought some patches on top of 2.6.32 are needed to get the intel >> 2.10.0 driver to work properly on all platforms. Or is that somehow >> not the case and the discussion yesterday incorrect? Some additional patches are needed for overlay support (only useful for 8xx) -- but it's not 2.10.0 regression. And it's mentioned in the above link. > For 8xx (845G/855GM/865G) you need to apply the backported overlay > patches on top of 2.6.32 for Xvideo support, since there is no > textured video available on these platforms AFAIK. Right. > Not sure how to > enable overlay support on 8xx (default?) or switch from textured > video to overlay for the other platforms though. overlay is default on 8xx, as it's the only choice. textured video is the default on 9xx and later. Users can switch by assigning parameter for media player (e.g. tell mplayer the port number of overlay), or set PreferOverlay in xorg.conf. Gordon ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Xorg crashes...
Would anyone be able to take a look at a bug report I filed with Ubuntu? My Xorg server keeps terminating on me and sends me back to the login screen. I have obtained a number of backtraces, all of which are logged in the bug report. The link to the bug report is below. https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/499484 I appreciate anyone who can shed some light on this for me. Thanks. -- This message and any files transmitted within are intended solely for the addressee or its representative and may contain company sensitive information. If you are not the intended recipient, notify the sender immediately and delete this message. Publication, reproduction, forwarding, or content disclosure is prohibited without the consent of the original sender and may be unlawful. Concurrent Technologies Corporation and its Affiliates. www.ctc.com 1-800-282-4392 ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] Intel 2009Q4 release
On Tue, Jan 05, 2010 at 07:42:40PM -0800, Greg KH wrote: > On Wed, Jan 06, 2010 at 10:02:06AM +0800, Jin, Gordon wrote: > > Hi, > > > > We'd like to announce Intel 2009Q4 release package > > (http://intellinuxgraphics.org/2009Q4.html), which consists of: > > - xf86-video-intel 2.10.0 > > - mesa 7.7 > > - libdrm 2.4.17 > > - Linux kernel 2.6.32 > > - xserver 1.7.3 is recommended to use with this release > > I thought some patches on top of 2.6.32 are needed to get the intel > 2.10.0 driver to work properly on all platforms. Or is that somehow not > the case and the discussion yesterday incorrect? For 8xx (845G/855GM/865G) you need to apply the backported overlay patches on top of 2.6.32 for Xvideo support, since there is no textured video available on these platforms AFAIK. Not sure how to enable overlay support on 8xx (default?) or switch from textured video to overlay for the other platforms though. Best regards, Stefan Public Key available -- Stefan Dirsch (Res. & Dev.) SUSE LINUX Products GmbH Tel: 0911-740 53 0Maxfeldstraße 5 FAX: 0911-740 53 479 D-90409 Nürnberg http://www.suse.deGermany - SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) - ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] Intel 2009Q4 release
On Wed, Jan 06, 2010 at 10:02:06AM +0800, Jin, Gordon wrote: > Hi, > > We'd like to announce Intel 2009Q4 release package > (http://intellinuxgraphics.org/2009Q4.html), which consists of: > - xf86-video-intel 2.10.0 > - mesa 7.7 > - libdrm 2.4.17 > - Linux kernel 2.6.32 > - xserver 1.7.3 is recommended to use with this release I thought some patches on top of 2.6.32 are needed to get the intel 2.10.0 driver to work properly on all platforms. Or is that somehow not the case and the discussion yesterday incorrect? confused, greg k-h ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
[ANNOUNCE] Intel 2009Q4 release
Hi, We'd like to announce Intel 2009Q4 release package (http://intellinuxgraphics.org/2009Q4.html), which consists of: - xf86-video-intel 2.10.0 - mesa 7.7 - libdrm 2.4.17 - Linux kernel 2.6.32 - xserver 1.7.3 is recommended to use with this release The biggest change in this release is user-modesetting (UMS) code has been removed from xf86-video-intel driver, so it's required for kernel to support kernel-modesetting (KMS). We highly recommend kernel version 2.6.32 or later. With this transition, some rare output may fail to work due to some mode setting path handled differently under UMS and KMS. If you encounter this, please file bug referring to http://intellinuxgraphics.org/how_to_report_bug.html. For 8xx users, video overlay is now supported with KMS, if you use a new kernel. Thanks, Gordon Intel Open Source Technology Center ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: pointer acceleration property rename and docs
thanks, that woke me up. I was struggling this morning :)
On Tue, Jan 05, 2010 at 09:13:47PM +0100, Simon Thum wrote:
> another round of ptr accel patches. I didn't send to the dev list to
> maybe gather more input on the rename.
>
> First, I renamed 'constant deceleration' to 'downscaling', and adjusted
> the property and option names. I hope that it is a good name; I'm still
> open for suggestions. Many suggested 'sensitivity' but I think that
> isn't it.
>
> Only the option rename is backwards-compatible though, to avoid
> redundant input properties. Peter, is that one OK with you?
I don't think this is necessary. We're nitpicking on the wording here and
given the number of languages out there there's always going to be some
ambiguity. with this patch you're breaking user configurations for very
little benefit - especially since the same could be achieved by having
more verbose documentation.
> Next, I added the possibility to change pointer feedback controls
> through options. The InputClass stuff makes it more sensible to do this.
> TBH, I never figured why it was limited to command line options.
there's protocol requests to adjust this at runtime and those are the only
pointer-acceleration related ones supported in GUI configuration tools
today. so arguably it's not essential since we've gone for years without it.
also, aren't you trying to get people off the old scheme? not having config
options is one way to do it :)
see for more comments in-line though.
> Third, some whitespace style fixes. Nothing functional.
meh, as usual with whitespace patches. since you're the one working most of
that code - if you're happy with that go for it.
> Last but not least, the documentation should now reflect reality wrt
> pointer acceleration. Affects the xorg.conf.man and --help output.
>
> It's perfectly possible the man changes are bogus, I just copied around
> and I seem not to have broken things.
> From da0b0bb6bda12eaa7f3cece3ab72056e73afa765 Mon Sep 17 00:00:00 2001
> From: Simon Thum
> Date: Tue, 5 Jan 2010 14:46:35 +0100
> Subject: [PATCH 2/4] xfree86: set accelaration controls from options
>
> Since config backends become better integrated, we may as well
> cover all the acceleration-related settings. Previously, the only
> way to set acceleration controls (aka pointer feedback) upfront
> was command-line options to the Xorg binary.
> ---
> hw/xfree86/common/xf86Xinput.c | 33 +++--
> 1 files changed, 31 insertions(+), 2 deletions(-)
>
> diff --git a/hw/xfree86/common/xf86Xinput.c b/hw/xfree86/common/xf86Xinput.c
> index 979b265..90ed1bc 100644
> --- a/hw/xfree86/common/xf86Xinput.c
> +++ b/hw/xfree86/common/xf86Xinput.c
> @@ -199,12 +199,12 @@ ProcessVelocityConfiguration(DeviceIntPtr pDev, char*
> devname, pointer list,
>
> static void
> ApplyAccelerationSettings(DeviceIntPtr dev){
> -int scheme;
> +int scheme, i;
> DeviceVelocityPtr pVel;
> LocalDevicePtr local = (LocalDevicePtr)dev->public.devicePrivate;
> char* schemeStr;
>
> -if(dev->valuator){
> +if(dev->valuator && dev->ptrfeed){
this whitespace should be fixed as part of this patch.
> schemeStr = xf86SetStrOption(local->options, "AccelerationScheme", "");
>
> scheme = dev->valuator->accelScheme.number;
> @@ -247,6 +247,35 @@ ApplyAccelerationSettings(DeviceIntPtr dev){
>pVel);
> break;
> }
> +
> +/*
> + * process acceleration controls (or 'pointer feedback') as device
> + * options, to allow people to set acceleration preferences more
> + * flexibly than command-line trickery.
> + */
I don't think this comment is necessary since the stuff below is pretty
standard code.
> +i = xf86SetIntOption(local->options, "AccelerationNumerator",
> + dev->ptrfeed->ctrl.num);
> +if (i >= 0)
> +dev->ptrfeed->ctrl.num = i;
> +
> +i = xf86SetIntOption(local->options, "AccelerationDenominator",
> + dev->ptrfeed->ctrl.den);
> +if (i > 0)
> +dev->ptrfeed->ctrl.den = i;
> +
> +i = xf86SetIntOption(local->options, "AccelerationThreshold",
> + dev->ptrfeed->ctrl.threshold);
> +if (i >= 0)
> +dev->ptrfeed->ctrl.threshold = i;
> +
> +/* mostly a no-op anyway */
> +(*dev->ptrfeed->CtrlProc)(dev, &dev->ptrfeed->ctrl);
> +
> +xf86Msg(X_CONFIG, "%s: (accel) acceleration factor: %.3f\n",
> +local->name, ((float)dev->ptrfeed->ctrl.num)/
> + ((float)dev->ptrfeed->ctrl.den));
> +xf86Msg(X_CONFIG, "%s: (accel) acceleration threshold: %i\n",
> +local->name, dev->ptrfeed->ctrl.threshold);
> }
> }
>
> --
> 1.6.4.4
the man page additions need to be part of this patch.
> From 3ef79
pointer acceleration property rename and docs
Hi all,
another round of ptr accel patches. I didn't send to the dev list to
maybe gather more input on the rename.
First, I renamed 'constant deceleration' to 'downscaling', and adjusted
the property and option names. I hope that it is a good name; I'm still
open for suggestions. Many suggested 'sensitivity' but I think that
isn't it.
Only the option rename is backwards-compatible though, to avoid
redundant input properties. Peter, is that one OK with you?
Next, I added the possibility to change pointer feedback controls
through options. The InputClass stuff makes it more sensible to do this.
TBH, I never figured why it was limited to command line options.
Third, some whitespace style fixes. Nothing functional.
Last but not least, the documentation should now reflect reality wrt
pointer acceleration. Affects the xorg.conf.man and --help output.
It's perfectly possible the man changes are bogus, I just copied around
and I seem not to have broken things.
Cheers,
Simon
>From 6bdb4ab5abef8a2155df23281c4ca1268dc999ae Mon Sep 17 00:00:00 2001
From: Simon Thum
Date: Tue, 5 Jan 2010 11:50:05 +0100
Subject: [PATCH 1/4] dix: rename input property for 'constant deceleration' to
'downscaling'
The old name seems not to be very descriptive, let alone correct.
Leaves the old define for any outsiders which may have used it, though
I'm unaware of any. The xorg.conf option is renamed likewise, but the old option
remains effective.
---
Xi/xiproperty.c|2 +-
dix/ptrveloc.c |6 +++---
hw/xfree86/common/xf86Xinput.c |7 ---
include/xserver-properties.h |4 +++-
4 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/Xi/xiproperty.c b/Xi/xiproperty.c
index ea66c54..896d804 100644
--- a/Xi/xiproperty.c
+++ b/Xi/xiproperty.c
@@ -54,7 +54,7 @@ static struct dev_properties
{0, XI_PROP_XTEST_DEVICE},
{0, XATOM_FLOAT},
{0, ACCEL_PROP_PROFILE_NUMBER},
-{0, ACCEL_PROP_CONSTANT_DECELERATION},
+{0, ACCEL_PROP_DOWNSCALING},
{0, ACCEL_PROP_ADAPTIVE_DECELERATION},
{0, ACCEL_PROP_VELOCITY_SCALING},
{0, AXIS_LABEL_PROP},
diff --git a/dix/ptrveloc.c b/dix/ptrveloc.c
index c2f4378..b15cbf0 100644
--- a/dix/ptrveloc.c
+++ b/dix/ptrveloc.c
@@ -197,7 +197,7 @@ AccelSetDecelProperty(DeviceIntPtr dev, Atom atom,
int rc;
int nelem = 1;
-if (atom != XIGetKnownProperty(ACCEL_PROP_CONSTANT_DECELERATION))
+if (atom != XIGetKnownProperty(ACCEL_PROP_DOWNSCALING))
return Success;
vel = GetDevicePredictableAccelData(dev);
@@ -222,7 +222,7 @@ static long
AccelInitDecelProperty(DeviceIntPtr dev, DeviceVelocityPtr vel)
{
float fval = 1.0/vel->const_acceleration;
-Atom prop_const_decel =
XIGetKnownProperty(ACCEL_PROP_CONSTANT_DECELERATION);
+Atom prop_const_decel = XIGetKnownProperty(ACCEL_PROP_DOWNSCALING);
XIChangeDeviceProperty(dev, prop_const_decel,
XIGetKnownProperty(XATOM_FLOAT), 32,
PropModeReplace, 1, &fval, FALSE);
@@ -358,7 +358,7 @@ DeletePredictableAccelerationProperties(DeviceIntPtr dev)
XIDeleteDeviceProperty(dev, prop, FALSE);
prop = XIGetKnownProperty(ACCEL_PROP_ADAPTIVE_DECELERATION);
XIDeleteDeviceProperty(dev, prop, FALSE);
-prop = XIGetKnownProperty(ACCEL_PROP_CONSTANT_DECELERATION);
+prop = XIGetKnownProperty(ACCEL_PROP_DOWNSCALING);
XIDeleteDeviceProperty(dev, prop, FALSE);
prop = XIGetKnownProperty(ACCEL_PROP_PROFILE_NUMBER);
XIDeleteDeviceProperty(dev, prop, FALSE);
diff --git a/hw/xfree86/common/xf86Xinput.c b/hw/xfree86/common/xf86Xinput.c
index 57db056..979b265 100644
--- a/hw/xfree86/common/xf86Xinput.c
+++ b/hw/xfree86/common/xf86Xinput.c
@@ -121,10 +121,11 @@ ProcessVelocityConfiguration(DeviceIntPtr pDev, char*
devname, pointer list,
/* common settings (available via device properties) */
tempf = xf86SetRealOption(list, "ConstantDeceleration", 1.0);
+tempf = xf86SetRealOption(list, "Downscaling", tempf);
if(tempf > 1.0){
-xf86Msg(X_CONFIG, "%s: (accel) constant deceleration by %.1f\n",
+xf86Msg(X_CONFIG, "%s: (accel) scaling down by %.1f\n",
devname, tempf);
-prop = XIGetKnownProperty(ACCEL_PROP_CONSTANT_DECELERATION);
+prop = XIGetKnownProperty(ACCEL_PROP_DOWNSCALING);
XIChangeDeviceProperty(pDev, prop, float_prop, 32,
PropModeReplace, 1, &tempf, FALSE);
}
@@ -153,7 +154,7 @@ ProcessVelocityConfiguration(DeviceIntPtr pDev, char*
devname, pointer list,
devname, tempi);
}
-/* set scaling */
+/* set velocity scaling */
tempf = xf86SetRealOption(list, "ExpectedRate", 0);
prop = XIGetKnownProperty(ACCEL_PROP_VELOCITY_SCALING);
if(tempf > 0){
diff --git a/include/xserver-properties.h b/include/xserver-properties.h
index 626d0ad..f90378d 100644
--- a/include/xserver-properties.h
+++ b/include/xserver-properties.h
@@
Re: how to read EDID/xrandr
On Oct 12, 09 09:49:14 -0400, Alex Deucher wrote: > On Mon, Oct 12, 2009 at 9:05 AM, Éric Piel wrote: > > Op 11-10-09 03:35, Ondrej Balaz schreef: > >> Hi, > >> is it possible to get edid info (especialy vendor and product id) for > >> each of xrandr screens through X11 api? > >> > >> I'm creating utility to remember various devices connected to VGA output > >> of my laptop (their mode/resolution, position etc.). AFAIK there is no > >> better identificator than vendor+product_id pair. I can see both > >> informations for various devices in my Xorg.0.log but I don't know how > >> to "reaccess" them (if it's possible). > > Sounds like a neat utility program. Would you mind posting an > > announcement when it's working? > > > > Here, with the intel driver, I can see the edid of each screen in the > > EDID_DATA property by doing: > > xrandr --verbose > > All randr 1.2 drivers expose the edid this way. Actually, this is exposed by the Xserver itself. Please note that with RandR 1.3 this property was renamed to just EDID in the big property unification change. Matthias -- Matthias Hopf ____ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ m...@mshopf.de Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.10.0
On Tue, 5 Jan 2010 10:20:14 +0100 Tino Keitel wrote: > On Mon, Jan 04, 2010 at 14:25:19 -0800, Carl Worth wrote: > > [...] > > > New requirements of 2.10 compared to 2.9 > > > > * Linux kernel with kernel-modesetting (KMS) > > > >All user-modesetting code has now been removed from the driver. > >We highly recommend kernel version 2.6.32 or later. > > > > * Libdrm >= 2.4.16 > > 2.9.901 was reported to require the 7.7 branch of mesa. Is this still > true for the release? It seems to work here with 7.6, for what that's worth :-) -RW signature.asc Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel driver problem
On Tue, Jan 5, 2010 at 10:09:47 +0100, Dirk De Becker wrote: [...] > (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD) > (**) Option "xkb_rules" "evdev" > (**) Option "xkb_model" "evdev" > (**) Option "xkb_layout" "us" > (II) Dell Dell USB Keyboard: Close > (II) UnloadModule: "evdev" > (II) HID 04d9:1400: Close > (II) UnloadModule: "evdev" > (II) HID 04d9:1400: Close > (II) UnloadModule: "evdev" > (II) Power Button: Close > (II) UnloadModule: "evdev" > (II) Power Button: Close > (II) UnloadModule: "evdev" This log looks like X starts up fine, and then the session ends. Are you sure it's not your session crashing or terminating prematurely, rather than an X problem? Cheers, Julien ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel driver problem
Hi Daniel, Thanks for your reply. If I look at /usr/share/XKeysymDB, I do not find XF86TouchpadToggle in there, so I am not sure how I can edit this file. libX11 is the latest stable release from gentoo (1.2.2) as is xkeyboard-config (1.7). Kind regards, Dirk Daniel Stone wrote: On Tue, Jan 05, 2010 at 10:09:47AM +0100, Dirk De Becker wrote: I am trying to use the intel driver (version 2.9.1) on a gentoo system with xorg version 1.6.3.901-r2. If I startx, I get the following output on screen (and X obviously does not start): Setting master expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet Your xkeyboard-config dataset is newer than libX11; you need to build a newer libX11, or edit XKeySymDB. Cheers, Daniel <>___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Intel driver problem
On Tue, Jan 05, 2010 at 10:09:47AM +0100, Dirk De Becker wrote: > I am trying to use the intel driver (version 2.9.1) on a gentoo system > with xorg version 1.6.3.901-r2. > If I startx, I get the following output on screen (and X obviously does > not start): > Setting master > expected keysym, got XF86TouchpadToggle: line 122 of inet > expected keysym, got XF86TouchpadToggle: line 122 of inet > expected keysym, got XF86TouchpadToggle: line 122 of inet > expected keysym, got XF86TouchpadToggle: line 122 of inet > expected keysym, got XF86TouchpadToggle: line 122 of inet > expected keysym, got XF86TouchpadToggle: line 122 of inet Your xkeyboard-config dataset is newer than libX11; you need to build a newer libX11, or edit XKeySymDB. Cheers, Daniel pgpcjVQcQlai8.pgp Description: PGP signature ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: The current dualseat status for radeon?
On Tuesday 05 January 2010 08:53:15 Xavier Bestel wrote: > On Mon, 2010-01-04 at 10:20 -0800, Corbin Simpson wrote: > > Fedora has accelerated r600. > > Sorry, I thought debian unstable was more up-to-date than other stable > distros. > > Xav Well, I'm on gentoo, so what is the opinion/argumentation if I could get a nonworking radeon HD4??? card at this moment? signature.asc Description: This is a digitally signed message part. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [Intel-gfx] [ANNOUNCE] xf86-video-intel 2.10.0
On Mon, Jan 04, 2010 at 14:25:19 -0800, Carl Worth wrote: [...] > New requirements of 2.10 compared to 2.9 > > * Linux kernel with kernel-modesetting (KMS) > >All user-modesetting code has now been removed from the driver. >We highly recommend kernel version 2.6.32 or later. > > * Libdrm >= 2.4.16 2.9.901 was reported to require the 7.7 branch of mesa. Is this still true for the release? Regards, Tino ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Intel driver problem
Hi all, I am trying to use the intel driver (version 2.9.1) on a gentoo system with xorg version 1.6.3.901-r2. If I startx, I get the following output on screen (and X obviously does not start): Setting master expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet expected keysym, got XF86TouchpadToggle: line 122 of inet waiting for X server to shut down Dropping master error setting MTRR (base = 0xd000, size = 0x1000, type = 1) Invalid argument (22) Attached, you can also find my xorg.conf and my Xorg.0.log Any help is greatly appreciated. Dirk Section "Device" Identifier "Builtin Default intel Device 0" Driver "intel" EndSection Section "Screen" Identifier "Builtin Default intel Screen 0" Device "Builtin Default intel Device 0" EndSection Section "ServerLayout" Identifier "Builtin Default Layout" EndSection This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.6.3.901 (1.6.4 RC 1) Release Date: 2009-8-25 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6-dzine-mini i686 Current Operating System: Linux GE8 2.6.31-gentoo-r6-dzine-mini #1 Mon Jan 4 16:11:43 CET 2010 i686 Build Date: 04 January 2010 06:05:00PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jan 5 11:01:31 2010 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Builtin Default Layout" (**) |-->Screen "Builtin Default intel Screen 0" (0) (**) | |-->Monitor "" (**) | |-->Device "Builtin Default intel Device 0" (==) No monitor specified for screen "Builtin Default intel Screen 0". Using a default monitor configuration. (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/share/fonts/TTF/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/OTF" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/Type1/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/75dpi/" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/100dpi/ (==) ModulePath set to "/usr/lib/xorg/modules" (II) Cannot locate a core pointer device. (II) Cannot locate a core keyboard device. (II) The server relies on HAL to provide the list of input devices. If no devices become available, reconfigure HAL or disable AllowEmptyInput. (II) Loader magic: 0x3a60 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 4.0 X.Org Server Extension : 2.0 (II) Loader running on linux (--) using VT number 7 (--) PCI:*(0:0:2:0) 8086:27a2:8086:27a2 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xfdf0/524288, 0xd000/268435456, 0xfdf8/262144, I/O @ 0xff00/8 (--) PCI: (0:0:2:1) 8086:27a6:8086:27a2 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xfde8/524288 (II) Open ACPI successful (/var/run/acpid.socket) (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x (0x1) IX[B] (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.3.901, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading exte
Re: The current dualseat status for radeon?
On Mon, 2010-01-04 at 10:20 -0800, Corbin Simpson wrote: > Fedora has accelerated r600. Sorry, I thought debian unstable was more up-to-date than other stable distros. Xav ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
