Re: cosmetic udev glitches
On 03/03/2010 08:25 PM, Dan Nicholson wrote: > On Wed, Mar 3, 2010 at 4:59 PM, Thomas Jaeger wrote: >> On 03/03/2010 07:48 PM, Dan Nicholson wrote: >>> On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote: The attribute 'name' might not exist (as in the case of serial wacom devices) and it's impossible to set it in an udev rule, I believe, so we should at least fall back to the NAME property if the attribute is not available. >>> >>> Not for the parent, either? Does hal give you anything for >>> info.product/input.product? >> >> Sorry, I don't know, I don't have a working hal installation anymore. >> Here's what udev knows about the device, though: >> >> udevadm info --path=/sys/class/tty/ttyS0/ --attribute-walk >> >> ... > > But you do get NAME in the uevent? You can find this from "udevadm > info --export-db". Well, sort of. I set NAME in my own udev rule where I filter by pnp id. > Seems reasonable, though. I guess we need an additional: > > if (!name) > name = udev_device_get_property_value(parent, "NAME"); > Yup, that's what I thought, too. Tom ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: cosmetic udev glitches
On Wed, Mar 3, 2010 at 4:59 PM, Thomas Jaeger wrote:
> On 03/03/2010 07:48 PM, Dan Nicholson wrote:
>> On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote:
>>> The attribute 'name' might not exist (as in the case of serial wacom
>>> devices) and it's impossible to set it in an udev rule, I believe, so we
>>> should at least fall back to the NAME property if the attribute is not
>>> available.
>>
>> Not for the parent, either? Does hal give you anything for
>> info.product/input.product?
>
> Sorry, I don't know, I don't have a working hal installation anymore.
> Here's what udev knows about the device, though:
>
> udevadm info --path=/sys/class/tty/ttyS0/ --attribute-walk
>
> ...
>
> looking at device '/devices/pnp0/00:0a/tty/ttyS0':
> KERNEL=="ttyS0"
> SUBSYSTEM=="tty"
> DRIVER==""
>
> looking at parent device '/devices/pnp0/00:0a':
> KERNELS=="00:0a"
> SUBSYSTEMS=="pnp"
> DRIVERS=="serial"
> ATTRS{id}=="WACf004"
>
> looking at parent device '/devices/pnp0':
> KERNELS=="pnp0"
> SUBSYSTEMS==""
> DRIVERS==""
But you do get NAME in the uevent? You can find this from "udevadm
info --export-db".
Seems reasonable, though. I guess we need an additional:
if (!name)
name = udev_device_get_property_value(parent, "NAME");
--
Dan
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: cosmetic udev glitches
On 03/03/2010 07:48 PM, Dan Nicholson wrote:
> On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote:
>> The attribute 'name' might not exist (as in the case of serial wacom
>> devices) and it's impossible to set it in an udev rule, I believe, so we
>> should at least fall back to the NAME property if the attribute is not
>> available.
>
> Not for the parent, either? Does hal give you anything for
> info.product/input.product?
Sorry, I don't know, I don't have a working hal installation anymore.
Here's what udev knows about the device, though:
udevadm info --path=/sys/class/tty/ttyS0/ --attribute-walk
...
looking at device '/devices/pnp0/00:0a/tty/ttyS0':
KERNEL=="ttyS0"
SUBSYSTEM=="tty"
DRIVER==""
looking at parent device '/devices/pnp0/00:0a':
KERNELS=="00:0a"
SUBSYSTEMS=="pnp"
DRIVERS=="serial"
ATTRS{id}=="WACf004"
looking at parent device '/devices/pnp0':
KERNELS=="pnp0"
SUBSYSTEMS==""
DRIVERS==""
Tom
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: cosmetic udev glitches
On Wed, Mar 3, 2010 at 4:00 PM, Thomas Jaeger wrote: > The attribute 'name' might not exist (as in the case of serial wacom > devices) and it's impossible to set it in an udev rule, I believe, so we > should at least fall back to the NAME property if the attribute is not > available. Not for the parent, either? Does hal give you anything for info.product/input.product? -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: vesa driver reports many modes, but only allows a few
On Wed, 2010-03-03 at 15:41 -0600, Pat Kane wrote: > Could you run the configure under gdb to see if you get a better trace back? > > $gdb Xorg > :r -configure > > could be some xemu hw emulated hw weirdness... > I also loaded some debug symbols. [tcsetpgrp failed in terminal_inferior: Operation not permitted] (++) Using config file: "/root/xorg.conf.new" (EE) open /dev/fb0: No such file or directory Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) where #0 0x in ?? () #1 0x0051a72a in DoConfigure () at ../../../../hw/xfree86/common/xf86Configure.c:832 #2 0x00471c17 in InitOutput (pScreenInfo=0x7d5a80, argc=, argv=) at ../../../../hw/xfree86/common/xf86Init.c:610 #3 0x00425a25 in main (argc=2, argv=0x7fffe258, envp=) at ../../dix/main.c:203 Ross > > On Tue, Mar 2, 2010 at 1:04 PM, Ross Boylan wrote: > > On Tue, 2010-03-02 at 05:34 -0600, Pat Kane wrote: > >> On Mon, Mar 1, 2010 at 2:35 PM, Ross Boylan wrote: > >> > Do I need to create a complete xorg.conf? > >> > >> > >> The command "Xorg -configure" will create one for you. > > Hooray! With some hacking I got it working. However, I want to report > > that Xorg -configure generated a segfault, and I'd like to improve my > > understanding of how configuration works. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: cosmetic udev glitches
The attribute 'name' might not exist (as in the case of serial wacom
devices) and it's impossible to set it in an udev rule, I believe, so we
should at least fall back to the NAME property if the attribute is not
available.
Tom
On 03/02/2010 05:47 PM, Dan Nicholson wrote:
> On Tue, Mar 02, 2010 at 05:57:04PM +0100, Simon Thum wrote:
>
> Can you try the patch below that uses the name attribute instead of the
> value from the uevent? I ran it through a little test app, but not in X.
>
> Dan
>
> From c01a4e6dce7196a60b5247dde78054b27e004494 Mon Sep 17 00:00:00 2001
> From: Dan Nicholson
> Date: Tue, 2 Mar 2010 14:42:22 -0800
> Subject: [PATCH] config/udev: Get product name from attribute instead of
> uevent
>
> The input device product name in the kernel uevent has embedded quotes
> that aren't expected here. Use the sysfs name attribute instead, which
> does not suffer this problem.
>
> Signed-off-by: Dan Nicholson
> ---
> config/udev.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/config/udev.c b/config/udev.c
> index 69257e9..54306ef 100644
> --- a/config/udev.c
> +++ b/config/udev.c
> @@ -74,7 +74,7 @@ device_added(struct udev_device *udev_device)
>
> parent = udev_device_get_parent(udev_device);
> if (parent)
> -name = udev_device_get_property_value(parent, "NAME");
> +name = udev_device_get_sysattr_value(parent, "name");
> if (!name)
> name = "(unnamed)";
> else
>From 8e791dbd4ad96c64802e864ff100f6342734a40c Mon Sep 17 00:00:00 2001
From: Dan Nicholson
Date: Tue, 2 Mar 2010 14:42:22 -0800
Subject: [PATCH] config/udev: Get product name from attribute instead of uevent
The input device product name in the kernel uevent has embedded quotes
that aren't expected here. Use the sysfs name attribute instead, which
does not suffer this problem. Fall back to the NAME property if the
attribute is not available.
Signed-off-by: Thomas Jaeger
---
config/udev.c |7 +--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/config/udev.c b/config/udev.c
index 69257e9..452fb5a 100644
--- a/config/udev.c
+++ b/config/udev.c
@@ -73,8 +73,11 @@ device_added(struct udev_device *udev_device)
goto unwind;
parent = udev_device_get_parent(udev_device);
-if (parent)
-name = udev_device_get_property_value(parent, "NAME");
+if (parent) {
+name = udev_device_get_sysattr_value(parent, "name");
+if (!name)
+name = udev_device_get_property_value(parent, "NAME");
+}
if (!name)
name = "(unnamed)";
else
--
1.7.0
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: can xrandr "split" a 2560x1024 screen into two separate 1280x1024 screens?
Hi Alex (You are everywhere. ; ) ) Thank you for the suggestion, I will give it a try. Should confess I was hoping for something slightly less hackish. Eg, using nvidia drivers one can configure their "twinview" option in xorg.conf to achieve this effect. But now I am stuck with integrated Intel graphics... thanks! ~l --- On Wed, 3/3/10, Alex Deucher wrote: > > You'd need something like fake libxinerama: > http://ktown.kde.org/~seli/fakexinerama/ ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
How to configure a serial mouse
I have a old pentium 3 the not suport USP or PS2 mouses. I need to configure a serial mouse. I intall debian squeeze and the mouse is dead. Squeeze don't have xorg.conf in /etc/X11 On debian etch I easily configure my mouse editing xorg.conf using Microsoft protocol. See this for more information: http://forums.debian.net/viewtopic.php?f=6&t=49959 I hope you can help me! PLEASE -- Felipe Vencato from Brazil ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: [ANNOUNCE] libdrm 2.4.19
On Wednesday 03 of March 2010, Arkadiusz Miskiewicz wrote: > On Wednesday 03 of March 2010, Eric Anholt wrote: > > New version for new Intel API that we're about to start using in Mesa. > > Unresolved symbols found in: /home/users/arekm/tmp/libdrm-2.4.19-root- > arekm/usr/lib64/libkms.so.1.0.0 > drmIoctl > drmCommandWriteRead > drmCommandWrite > > Lack of linking with libdrm it seems. --- libdrm-2.4.19/libkms/Makefile.am~ 2010-03-02 19:10:47.0 +0100 +++ libdrm-2.4.19/libkms/Makefile.am2010-03-03 21:28:13.629525972 +0100 @@ -5,7 +5,7 @@ libkms_la_LTLIBRARIES = libkms.la libkms_ladir = $(libdir) libkms_la_LDFLAGS = -version-number 1:0:0 -no-undefined -libkms_la_LIBADD = +libkms_la_LIBADD = $(top_builddir)/libdrm.la #if HAVE_LIBUDEV #libkms_la_LIBADD += $(LIBUDEV_LIBS) -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/ ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
X doesn't start in minilinux
Hi guys, I'm building a minilinux for our library at my university. It has to have also a browser with flash, so I need a Xserver. The whole system is build of an ubuntu distro. I only copied the files I need from my distro to the sourcefolder of the miniimage, then make it to an image and boot the virtual maschine by pxe. So it is possible, that I missed a file or forgot a option in the kernel or something like that for the xserver. The server shall use vesa for the first time, but I'm not able to get it to work. Any ideas why it isn't able to find a screen? The latest XFree86 server did work on this maschine. Here's the log from /var/log/Xorg.0.log: _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/(none):0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 X.Org X Server 1.6.4 Release Date: 2009-9-27 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.24-23-server i686 Ubuntu Current Operating System: Linux (none) 2.6.31.1 #9 Wed Mar 3 21:15:10 CET 2010 i686 Kernel command line: BOOT_IMAGE=bibotestkernel.image root=/dev/ram initrd=bibotestinitrd.gz Build Date: 14 November 2009 05:48:26PM xorg-server 2:1.6.4-2ubuntu4.1 (buildd@) 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: Wed Mar 3 22:32:55 2010 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "TFT" (**) | |-->Device "VIA" (**) |-->Input Device "PS2 Mouse" (**) |-->Input Device "PS2 Keyboard " (**) Option "BlankTime" "0" (**) Option "StandbyTime" "0" (**) Option "SuspendTime" "0" (**) Option "OffTime" "0" (==) Automatically adding devices (==) Automatically enabling devices (WW) The directory "/usr/lib/X11/fonts/misc" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/misc" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/Type1" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. Entry deleted from font path. (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. Entry deleted from font path. (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist. Entry deleted from font path. (**) FontPath set to: built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled. (WW) Disabling PS2 Mouse (II) Loader magic: 0x3bc0 (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 2 (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) System resource ranges: (II) "extmod" will be loaded by default. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded by default. (II) "dri" will be loaded by default. (II) "dri2" will be loaded by default. (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions//libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.4, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions//libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.4, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (==) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions//libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.4, 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 extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "
Re: [ANNOUNCE] libdrm 2.4.19
On Wednesday 03 of March 2010, Eric Anholt wrote: > New version for new Intel API that we're about to start using in Mesa. Unresolved symbols found in: /home/users/arekm/tmp/libdrm-2.4.19-root- arekm/usr/lib64/libkms.so.1.0.0 drmIoctl drmCommandWriteRead drmCommandWrite Lack of linking with libdrm it seems. -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/ ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: can xrandr "split" a 2560x1024 screen into two separate 1280x1024 screens?
On Wed, Mar 3, 2010 at 2:38 PM, Lara Michaels wrote: > Hi everyone, > > I know how to use xrandr to position screens relative to each other when I > have two monitors plugged into my computer, but now I need something else. > Any help is much appreciated: > > Can I use xrandr to split (what it thinks is) a 2560x1024 screen into two > separate monitors? I am using a Matrox Dualhead2go, which connects into my > laptop and presents itself to the video card as a very wide 2560x1024 screen. > > I need to do this so that, eg, maximizing a window to "full screen" maximizes > to be 1280x1024, rather than spanning it over the entire two screens. > You'd need something like fake libxinerama: http://ktown.kde.org/~seli/fakexinerama/ Alex > Thank you for any help! > > ~lara > > > > > ___ > 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
can xrandr "split" a 2560x1024 screen into two separate 1280x1024 screens?
Hi everyone, I know how to use xrandr to position screens relative to each other when I have two monitors plugged into my computer, but now I need something else. Any help is much appreciated: Can I use xrandr to split (what it thinks is) a 2560x1024 screen into two separate monitors? I am using a Matrox Dualhead2go, which connects into my laptop and presents itself to the video card as a very wide 2560x1024 screen. I need to do this so that, eg, maximizing a window to "full screen" maximizes to be 1280x1024, rather than spanning it over the entire two screens. Thank you for any help! ~lara ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Boot resolution
On Wed, Mar 3, 2010 at 12:33 AM, Michael wrote: > O.K. this time I found the right kernel option. It is (simply): > > video=800x600 > > Then it works. > > Cheers > > Michael > > P.S.: Now I need to find out how to make boot messages disappear which are > visible for about two seconds between splashy stopping and xserver > starting... Boot with "quiet"? -- Dan ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
mode not found problem...
Hi, I am using Xserver for my development PC, it is PXA270 based one. I can able to run Xserver on 240x320 and 640x480 resolution properly, but while running 480x272 lcd" it making problem. How can I resolve this. Version: xserver-kdrive-1_1.4.0.90-r5 Build System : Open Embedded Error log are, /*/ r...@regulus:~# Xfbdev -br -pn -mouse tslib -hide-cursor :0 -noreset Warning: mode not found, using default error: Invalid argument Fatal server error: no screens found /*/ With Regards J.Balakrishnan. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: State of Zaphod dual screen support
the 2nd link should be: http://webcvs.freedesktop.org/xorg/xc/programs/Xserver/hw/xfree86/DebuggingHints?view=co you might find this part useful: 5. Without module support gdb is not able to print the function where an error occurred in a module. If you get a line like: (gdb) bt #0 0x823b4f5 in ?? () You may obtain the function the address belongs to by calling LoaderPrintSymbol(): (gdb) call LoaderPrintSymbol(0x823b4f5) The symbol returned might not always be the name of the function which contains the address. In case of static functions the symbol is not known to the loader. However LoaderPrintSymbol() will print the nearest known function and the offset from its start. You may easily find the exact location of the address if you do: # objdump --disassemble .o .o is the name of the object file containing the symbol printed. ... On Wed, Mar 3, 2010 at 7:03 AM, Pat Kane wrote: > Dave, > > For X server gdb help take a look at: > http://www.x.org/wiki/Development/Documentation/ServerDebugging > http://webcvs.freedesktop.org/xorg/xc/programs/Xserver/hw/xfree86/DebuggingHints > the second is a bit out of date but still useful. > > Pat > --- > > On Wed, Mar 3, 2010 at 12:24 AM, David Mohr wrote: > ... >> I don't have much experience with how gdb behaves if there are no >> debugging symbols available in _part_ of the program. Could it be that >> I can inspect the X server by setting a breakpoint somewhere and then >> continuing? >> If so, what would be a good place to put a breakpoint (I have no clue >> about X internals)? > ... > ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: State of Zaphod dual screen support
Dave, For X server gdb help take a look at: http://www.x.org/wiki/Development/Documentation/ServerDebugging http://webcvs.freedesktop.org/xorg/xc/programs/Xserver/hw/xfree86/DebuggingHints the second is a bit out of date but still useful. Pat --- On Wed, Mar 3, 2010 at 12:24 AM, David Mohr wrote: ... > I don't have much experience with how gdb behaves if there are no > debugging symbols available in _part_ of the program. Could it be that > I can inspect the X server by setting a breakpoint somewhere and then > continuing? > If so, what would be a good place to put a breakpoint (I have no clue > about X internals)? ... ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: cosmetic udev glitches
On Tue, Mar 2, 2010 at 14:47:22 -0800, Dan Nicholson wrote: > From: Dan Nicholson > Date: Tue, 2 Mar 2010 14:42:22 -0800 > Subject: [PATCH] config/udev: Get product name from attribute instead of > uevent > > The input device product name in the kernel uevent has embedded quotes > that aren't expected here. Use the sysfs name attribute instead, which > does not suffer this problem. > > Signed-off-by: Dan Nicholson Acked-by: Julien Cristau Thanks, Dan. Cheers, Julien ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: State of Zaphod dual screen support
Peter Hutterer wrote: > On Mon, Mar 01, 2010 at 12:41:02AM -0700, David Mohr wrote: >> On Sun, Feb 28, 2010 at 11:37 PM, Peter Hutterer >> wrote: >>> On Sun, Feb 28, 2010 at 11:29:12PM -0700, David Mohr wrote: I'm part of the minory who currently uses a Zaphod style dual monitor setup with separate X screens for every monitor. When I recently upgraded from 7.4 to 7.5, some utilites which I adopted[1] which manipulate the mouse cursor started malfunctioning. My two X screens are setup to be "apart" so that the mouse does not pass between them, and I use my utilities to move the mouse between the two screens. But with 7.5 every now and then a condition is triggered where the mouse cursor will just continually jump from screen to screen, keeping the X server at 100% CPU. I cannot even shut it down using CTRL-ALT-Backspace. I've noticed comments in other threads on this mailing list that Zaphod mode is not really supported any more (for completeness' sake, I'm using the binary Nvidia drivers). So my question is, is there value in trying to track down the bug in Xorg which causes the mouse to jump back and forth? >>> yes. I've seen this myself and I have not yet identified the issue. it's a >>> server bug and unrelated to the binary driver. If you can help track this >>> issue down, it would be much appreciated. >> Ok. Unfortunately I have not been able to find reliable conditions for >> triggering the bug. I'll try again and see what I can find. > > i found using a wacom tablet with a xinerama setup and then switch back and > forth triggers it eventually. the problem is the "eventually" bit... I don't have an idea whether it's related, but maybe you can add code which always clears the pointer's remainder fields, so 'eventually' may become something more specific. > >> Is there any way to get good information out of the running X instance >> once the bug has been triggered? I can only think of sending a signal >> to get a core dump, but then I'm not sure how much useful information >> that would contain. > > once it happens, gdb in and single-stepping may be the only approach. a > backtrace would be great already, just to make sure if you're seeing the > same problem as I am. > > Cheers, > Peter > ___ > 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: cosmetic udev glitches
Julien Cristau wrote:
> This is also expected at the moment. The enumeration of devices gives
> us /dev/input/event* (which evdev can handle), and
> /dev/input/{mouse,kbd}* (which it doesn't). This results in a couple
> error messages for the latter. It should be possible to tone those down
> so users don't get scared…
Thanks for the clarification! I applied Peter's MatchDevicePath
"/dev/input/event*" which is probably better than making polite drivers.
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Boot resolution
O.K. this time I found the right kernel option. It is (simply): video=800x600 Then it works. Cheers Michael P.S.: Now I need to find out how to make boot messages disappear which are visible for about two seconds between splashy stopping and xserver starting... Michael wrote: > Hello > > With all that kernel mode setting stuff I have no idea any longer where to > pose my question. So I try here, knowing that it is most probably the > wrong mailing list. > > I have an atom system here with a intel 945 graphics chip. I use kernel > 2.6.33 on a debian based linux system. > > I want to control the boot resolution of the system to always have it > 800x600. In earlier times that was easily done using the kernel option > "vga=789". Today, I cannot get it to work. The system always switches to > the highest available resolution (1600x900) directly after grub. > > I tried the following kernel options without success, all of them leading > to a resolution of 1600x900: > > - vga=789 > - vga=0 video=intelfb:800x600 > - vga=0 video=inteldrmfb:modeset=1:800x600 > - vga=0 video=inteldrmfb:modeset=0:800x600 > - vga=0 i915.modeset=0 > - vga=789 i915.modeset=0 > - vga=789 i915.modeset=1 > > Can anybody hint me what I need to do? > > Thanks, > > Michael ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Boot resolution
Hello With all that kernel mode setting stuff I have no idea any longer where to pose my question. So I try here, knowing that it is most probably the wrong mailing list. I have an atom system here with a intel 945 graphics chip. I use kernel 2.6.33 on a debian based linux system. I want to control the boot resolution of the system to always have it 800x600. In earlier times that was easily done using the kernel option "vga=789". Today, I cannot get it to work. The system always switches to the highest available resolution (1600x900) directly after grub. I tried the following kernel options without success, all of them leading to a resolution of 1600x900: - vga=789 - vga=0 video=intelfb:800x600 - vga=0 video=inteldrmfb:modeset=1:800x600 - vga=0 video=inteldrmfb:modeset=0:800x600 - vga=0 i915.modeset=0 - vga=789 i915.modeset=0 - vga=789 i915.modeset=1 Can anybody hint me what I need to do? Thanks, Michael ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
