Re: visual resizing and positioning of displays
On Thu, 2010-01-07 at 18:43 +, allcoms wrote: Isn't gnome-display-properties sufficient? Which additional features would you need? No, gnome-display-properties isn't sufficient to my needs as it does neither of the two features I am looking for which are: 1- Visual resizing (as in 'graphically' adjusting the screens outer borders) and 2- Visual positioning (centering) of the full screen gdp is of course just a simple gui to xrandr, which doesn't do what I require. nvidias X setup tool is also lacking such functionality and as I say the only tool I've seen do this under linux is tied into suse's vast yast config monster which is prob hundreds of meg with all its dependencies when all I'd ever want from it is the visual screen setup tool. Are you looking for something like a modern version of xvidtune tied into xrandr which can tweak monitor timings? 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: Multiseat with VGAArbiter on 2 Radeon cards - found KMS
On Tue, 2009-12-22 at 17:49 +, Steffen Schaumburg wrote: Ok I just realised that KMS has to be activated in staging. So I tried that now, but without success :( So I tried 3 kernel configs now. In common they have: Kernel 2.6.32 (gentoo-sources) xorg-server 1.7.3 using the xorg radeon/ati driver identical xorg.conf and kdmrc (attached) Both boot in text mode fine The differences (all configs are attached): 1) had KMS and DRM off 2) DRM on 3) DRM and KMS on Now the results vary quite a bit. All of them start booting in textmode on the monitor connected to the primary graphics card. 1 and 2 continue to boot and allow me to do a text login. However with KMS on by default the monitor suddenly goes black (but not into standby) during boot, I think when it starts loading the modules but I'm not quite sure, it's hard to tell because the messages come so fast at that point. However I can still login blindly. If I try to start KDM nothing changes on the screens. As said 1 and 2 let me login normally so here's what happens from then: With the kernel without DRM I can start KDM and it displays on the screen connected to the secondary card (note: this is the first entry in kdmrc). I can then login and work on that monitor just fine, in fact I'm writing this email from it. With the kernel with DRM it's not so good. The second monitor turns on but both just go blank and stay blank. Note that in all of the scenarios I can always cause an orderly shutdown by pressing the power button. Any ideas? Thanks, Steffen Okay I tried turning off arbiter by just editing .config (CONFIG_VGA_ARB=n) but when I type my usual make make modules_install it changes it back automatically. I tried rebooting into this new kernel anyways but it continues to load arbiter as evidenced in the boot messages and as expected it still doesn't work. I haven't been able to turn off arbiter in make menuconfig as its automatically turned on by other options so it doesn't even show up in there. You don't want to turn it off. It is needed to cleanly boot with two VGA cards. Does anyone have any ideas what I'm doing? Or is anyone out here running a multiseat setup with radeon cards? I'd be very very grateful if you could send me your xorg.conf, ?dm config (e.g. /usr/share/config/kdm/kdmrc), the version numbers of your xorg-server, typeversion of driver (at this stage I'd even try the proprietary drivers) and what you use to launch X as well as its version. So any tips, no matter how unlikely you think they are to work, would be greatly appreciated. Given how you've mentioned DRM failing, have you checked it's successfully loading the microcode for both cards? DRM should be working with multiple cards. I have a dual Radeon system RV280 (PCI) + R420 (AGP), I too was having some problems bringing it up successfully. What I found is I had to go with what the DRM driver determines to be the card order (PCI as primary), not what the BIOS has set (AGP as primary). It is apparently essential to have the cards initialised in this order. Until you get it working, you probably want to use -retro so you can tell you've got the server running properly. I haven't yet tried multi-seat, but have it working with multi-screen, I had hoped to find some way of binding input devices to a single screen, but the code isn't yet in place, so I'll be trying multi-seat again. (I previously had it working with the old UMS drivers.) I've attached the drm log from my boot with two working Radeons + KMS. I won't be about for a couple of weeks so I won't be able to help further until then. [drm] Initialized drm 1.1.0 20060810 [drm] radeon kernel modesetting enabled. [drm] radeon: Initializing kernel modesetting. [drm] register mmio base: 0xCFFC [drm] register mmio size: 65536 [drm] GPU reset succeed (RBBM_STATUS=0x0140) [drm] GPU not posted. posting now... [drm] Generation 2 PCI interface, using max accessible memory [drm] radeon: VRAM 128M [drm] radeon: VRAM from 0x to 0x07FF [drm] radeon: GTT 512M [drm] radeon: GTT from 0x2000 to 0x3FFF [drm] radeon: irq initialized. [drm] Detected VRAM RAM=128M, BAR=128M [drm] RAM width 64bits DDR [drm] radeon: 128M of VRAM memory ready [drm] radeon: 512M of GTT memory ready. [drm] GART: num cpu pages 131072, num gpu pages 131072 [drm] radeon: cp idle (0x02000603) [drm] Loading R200 Microcode [drm] radeon: ring at 0x2000 [drm] ring test succeeded in 0 usecs [drm] radeon: ib pool ready. [drm] ib test succeeded in 0 usecs [drm] DFP table revision: 4 [drm] Radeon Display Connectors [drm] Connector 0: [drm] VGA [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60 [drm] Encoders: [drm] CRT1: INTERNAL_DAC1 [drm] Connector 1: [drm] DVI-I [drm] DDC: 0x64 0x64 0x64 0x64 0x64 0x64 0x64 0x64 [drm] Encoders: [drm] CRT2: INTERNAL_DAC2 [drm] DFP1: INTERNAL_TMDS1 [drm] fb mappable at 0xB804 [drm]
Re: pci_enable_device for pciaccess?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dave Airlie wrote: On Tue, May 20, 2008 at 1:36 PM, Tiago Vignatti vigna...@c3sl.ufpr.br wrote: Dave Airlie escreveu: Okay I've been playing with getting posting working again in master, Yay! I can make it work on Linux if I use the OS to enable the device in /sys before trying to POST it. However I really think this should be pciaccess functionality, so I'd like to add a pci_enable_device function to libpciaccess and call it from the server before trying to POST secondary cards. +1 Long term the posting should be done before X starts but I want to fix the regression for Fedora. Before X starts? I'd imagine a situation where someone insert a new display or that fancy usb video cards while the X is running. So in this case a hook inside the server is also needed. No in this case I would expect the kernel to set the device up before handing it to X via d-bus or whatever, including posting it. Yes, this is what I initially thought as well. So I started nuking int10 module inside the server and transformed in a library (which differs from mjg56's version which is not updated and synchronized with last xorg modifications). Maybe we could link it against the libpciaccess to do the POST/setup. I don't know, you can say it better. http://cgit.freedesktop.org/~vignatti/libx86/ (The X server side modification to use this library is trivial. Just link it against the library and git-rm hw/xfree/int10 basically) Yeah ideally we could do something like that inside pciaccess, but posting really requires VGA arbitration so we can route the buses correctly before POST. I'm resurrecting this old thread since multiple cards are still not working for most people, see: http://bugs.freedesktop.org/show_bug.cgi?id=18160 I'm wondering how this is all tying into the KMS work, has any more work been done on the VGA arbiter? Is there likely to be a solution for people with multiple graphics cards on any near horizon? Is there a external standalone utility that can POST additional cards so that KMS/DDX driver can then subsequently take over. (To be run from initramfs perhaps?) Is VGA arbitration essential? -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmx9Y4ACgkQGcb56gMuC61bMACffu/jloi9F5ZBQpfSlCCrzAR2 TUMAnixpTxvvwR0RU4jVKZ1ZQqDBwqR7 =9AQ5 -END PGP SIGNATURE- ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Blind people do not connect screens
On Tue, 2009-03-03 at 21:01 +0100, Samuel Thibault wrote: Hello, Some blind people report that Xorg refuses to start when no screen is connected to their machine. Of course they could configure their xorg.conf to use the dummy driver, but then they'd have to modify it back when using a screen etc. and distributions are more and more going towards full autodetection anyway. I don't know which way would be fine: - have drivers not fail when no screen is connected, but use some default sane resolution. Needs cooperation from all drivers. - have X.org fallback to dummy when no screen is connected. If screen detection works correctly, shouldn't harm sighted users. Needs information feedback from drivers to tell so. - have X.org fallback to dummy when the autodetect driver does not work. May make sighted users wonder why their screen is black, but well. - introduce an xorg.conf option to enable some behavior above. Doesn't really match nowadays' no xorg.conf moto. - introduce an option similar to -allowMouseOpenFail. Not really convenient to automatically configure in a generic-purpose distribution. I guess the ideal would be to have full hotplug video driver support like the HAL input driver hotplug, and use the dummy driver if there are no valid screens. It would also be handy for docking stations and dual video laptops of course... Something tells me it wouldn't be easily implemented though! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
int10 using vbios from wrong card
While trying to figure out where my VGA-SCART video output has disappeared, I noticed my secondary Radeon 9250 is being booted with the VBIOS from the primary X800 as can be seen in the attached log. Older logs from working versions seem to show the same thing, so that's not necessarily caused my immediate problem of no modes on VGA-0... 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.99.1 Release Date: (unreleased) X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.29-rc4-00058-g4c098bc x86_64 Current Operating System: Linux eater 2.6.29-rc4-00058-g4c098bc #24 PREEMPT Tue Feb 10 13:52:49 GMT 2009 x86_64 Build Date: 20 February 2009 02:41:45PM 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.1.log, Time: Fri Feb 20 19:15:07 2009 (==) Using config file: /etc/X11/xorg.conf (++) ServerLayout mythtv0 (**) |--Screen MythScrn0 (0) (**) | |--Monitor TV (**) | |--Device ATI9250 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option IsolateDevice PCI:0:6:0 (II) Isolating PCI bus 0:6:0 (**) Option Xinerama false (**) Option AutoAddDevices no (**) Not 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/TTF/ does not exist. Entry deleted from font path. (WW) The directory /usr/share/fonts/OTF does not exist. Entry deleted from font path. (**) FontPath set to: /usr/share/fonts/misc, /usr/share/fonts/75dpi, /usr/share/fonts/100dpi, /usr/share/fonts/Type1, /usr/share/fonts/misc/, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/, built-ins (==) ModulePath set to /usr/lib64/xorg/modules (**) Extension Composite is enabled (**) Extension DAMAGE is enabled (WW) Ignoring unrecognized extension XVideo-MotionCompensation (II) Loader magic: 0x7dc540 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 5.0 X.Org XInput driver : 5.0 X.Org Server Extension : 2.0 (--) using VT number 1 (--) PCI:*(0...@0:6:0) ATI Technologies Inc RV280 [Radeon 9200 PRO] rev 1, Mem @ 0xb800/134217728, 0xcff8/65536, I/O @ 0xdc00/256, BIOS @ 0x/131072 (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) MX[B] [5] -1 0 0x000f - 0x000f (0x1) MX[B] [6] -1 0 0x000c - 0x000e (0x3) MX[B] [7] -1 0 0x - 0x0009 (0xa) MX[B] [8] -1 0 0x - 0x (0x1) MX[B] [9] -1 0 0x000f - 0x000f (0x1) MX[B] [10] -1 0 0x000c - 0x000e (0x3) MX[B] [11] -1 0 0x - 0x0009 (0xa) MX[B] [12] -1 0 0x - 0x (0x1) MX[B] [13] -1 0 0x000f - 0x000f (0x1) MX[B] [14] -1 0 0x000c - 0x000e (0x3) MX[B] [15] -1 0 0x - 0x0009 (0xa) MX[B] [16] -1 0 0x - 0x (0x1) MX[B] [17] -1 0 0x000f - 0x000f (0x1) MX[B] [18] -1 0 0x000c - 0x000e (0x3) MX[B] [19] -1 0 0x - 0x0009 (0xa) MX[B] [20] -1 0 0x - 0x (0x1) IX[B] [21] -1 0 0x - 0x (0x1) IX[B] [22] -1 0 0x - 0x (0x1) IX[B] [23] -1 0 0x - 0x (0x1) IX[B] [24] -1 0 0x - 0x (0x1) IX[B] [25] -1 0 0x - 0x (0x1) IX[B] [26] -1 0 0x - 0x (0x1) IX[B] [27] -1 0 0x - 0x (0x1) IX[B] [28] -1 0 0x - 0x (0x1) IX[B] [29] -1 0 0x - 0x (0x1) IX[B] (II) LoadModule: extmod (II) Loading /usr/lib64/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor=X.Org Foundation compiled for 1.6.99.1, 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: dbe (II) Loading /usr/lib64/xorg/modules/extensions/libdbe.so
Re: multiseat login problems: MDM?
On Wed, 2008-11-26 at 19:58 +, Kārlis Repsons wrote: On Wednesday 26 November 2008 19:49:12 you wrote: On Sun, Nov 23, 2008 at 4:37 PM, Kārlis Repsons [EMAIL PROTECTED] wrote: What should I do to get multiseat work in a case when * some user logs out * some seat doesn't receive login timely (and its X server gets terminated..) ? Are you using mdm? Not yet. When a user logs out mdm should show the display manager's login screen again. Would be nice... The thing is: I can't make it work on gentoo easily. My distro's devs are not going to support it as well, because latest upgrade of mdm is 2+ years old. (http://bugs.gentoo.org/45833) That bug about is the wrong MDM (Mandrake Display Manager). If you want to use MDM (Multiseat Display Manager) in gentoo, you should create an ebuild for it. Maybe I try dedicating a day just for MDM and succeed, but there are questions like: 1. should I patch libX11(-6)? 2. is /etc/init.d/mdm non-executable in debian? 3. ... others I can't think of right now. Well, let me know, what you think about those things first! You really don't want to be using the debian packaged version on Gentoo! ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Mouse button problems using Logitech NX80
On Tue, 2008-11-11 at 01:54 +0100, Matija Šuklje wrote: Dne ponedeljek 10. novembra 2008 je Dan Nicholson napisal(a): Try a newer version of xf86-input-evdev. I had the same issue and ended up getting a patch committed to the kernel to have the inputs swapped. I later found out that evdev-2.x did the right thing with a vanilla kernel. I just got fed up and upgraded to xf86-input-evdev-2.0.7 and now: * tilting works as it should (probably due to the ZAxisMapping line) * Emulate3Button works (so I can at least have the same functionality as having button 2) But still the ButtonMapping doesn't work (I think it was said 2.1 will support that), so I have two extra buttons that do nothing and have to emulate the middle button. But so far, so good :] Try stopping X and running evtest from the console. You should find the pushing the wheel to the right results in a positive value for the HWHEEL button. I still can't find 'evtest', so I suppose it's not part of the evdev package. On Gentoo, you'll find it in games-util/joystick. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: 3d very slow on 945GM using intel driver
On Mon, 2008-10-20 at 17:05 -0700, Keith Packard wrote: On Mon, 2008-10-20 at 15:11 +0200, Adam Lantos wrote: Same here w/i915. and glxgears shows only 70-75 fps... 70-75fps sounds like sync to vblank ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: 3d very slow on 945GM using intel driver
On Mon, 2008-10-20 at 17:17 -0700, Keith Packard wrote: On Tue, 2008-10-21 at 01:09 +0100, Steven J Newbury wrote: On Mon, 2008-10-20 at 17:05 -0700, Keith Packard wrote: On Mon, 2008-10-20 at 15:11 +0200, Adam Lantos wrote: Same here w/i915. and glxgears shows only 70-75 fps... 70-75fps sounds like sync to vblank Not if it changes; vblank glxgears should be wired to the refresh rate. Yes, of course, but I assumed Adam meant 70-75 as in a value around that. I could easily be wrong in that assumption, it's clear he's having other problems. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: Multiple Monitors, Same Workspaces
On Fri, 2008-09-19 at 10:01 -0500, Clayton Shepard wrote: I will play with this more, but I still am skeptical that it will do what I am describing. In the past when I tried this it seemed as though either each monitor displayed a separate set of workspaces (you couldn't have both monitors sharing workspaces), the application bar extended across both monitors as one one workspace, or the second monitor just added extra resolution to the workspace you were on. Then most likely you didn't compile your apps and toolkit with Xinerama support. ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
Re: multihead / dual input howto (two local users, keyboards etc.)?
On Tue, 2008-09-09 at 15:07 +0100, Simos Xenitellis wrote: I would say it is more of an issue that many tasks based on open-source software can be achieved, it just requires the person(s) to lead the effort. Apart from the core functionality/programming that takes place in Xorg, it's an issue of packaging and making it easy for the users to install and use. Looking at http://brainstorm.ubuntu.com/ it shows that Multiseat has a page at http://brainstorm.ubuntu.com/idea/3442/ with over 300 'votes'. Top issues have over 5000 such votes. It looks to be a trend; there is amazing core functionality in X.Org, which requires packaging and dissemination to the end-users. This does mean that the developers have even more tasks to do; other people should lead the effort to bring this functionality to the end-users. Simos On Tue, Sep 9, 2008 at 2:10 PM, Tomasz Chmielewski [EMAIL PROTECTED] wrote: Simos Xenitellis schrieb: Do a search for multiseat. I think it shows more results. I have not tried this, so it's good to post a summary on the list once you have some results. It still wonders a bit why i.e. Linux distributors still don't offer an easy to use tool for setting up a multiseat workstation. It's a clear advantage over Windows, where setting up a multiseat is just impossible because of design. Use it in self-service Kiosks, libraries, schools etc. I once saw a commercial multiseat Kiosk distribution running Linux[1], where they had this feature made perfectly. First, you equip your workstation in multiple graphic cards, keyboards etc. (obvious step). When the distribution boots, it automatically configures all graphic cards. Because there can be many keyboards and monitors, it can confuse the user which device belongs where, and therefore, on each monitor, it displays something like: Press F4 and left-click your mouse if you're sitting in front of this workstation. or Press F2 and lefte-click your mouse if you're sitting in front of this workstation. This way, it knows that a given keyboard is attached to a given monitor. Smart! [1] http://www2.userful.com/products/userful-multiplier/how-its-done, available as a free download I the biggest thing needed currently from an Xorg perspective, with respect to multiseat, would be the ability to have a HAL policy tie specific devices to specific displays - unless I'm missing something? ___ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg
