[XFree86] Kde (3.1.3) desktop does not resize to match the screen when changed in portrait mode.
Does anyone have any experience of using the Rotate option in Linux? I am using the Mandrake 9.2 distribution, with XFree86 ver 4.3.(0 I think) I am using the NV drivers in order to use the flatscreen in portrait mode. I can rotate the image so it is the correct way up when in portrait mode by adding Rotate CCW to my /etc/X11/XF86Config-4 file But the kde desktop does not resize to match the new resolution (change from 1024 * 768 = 768 * 1024). Do I need to change my Xserver provided with Mandrake to the Xkdrive implementation? If you think this is the wrong place to ask, then please help me to work out where to ask. Many thanks in advance. Gareth Deli Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: suggested fix by Mark for :- Kde (3.1.3) desktop does not resize to match the screen when changed in portrait mode.
Many many thanks Mark :o) :o) :o) I have tried this so many times, and it has never worked... I was putting the option Randr false in the driver section underneath the line Rotate ccw, so when I moved it to the ServerFlags section it worked exactly how it should! :o) I feel so stupid now - I must have mis-read the documentation about 100 times + to miss that. You dont happen to know the best way to allow me to be able to quickly switch between accelerated mode (using the NVIDIA driver) and the portrait mode (using the NV driver) is do you? The only way I can think of is to have 2 copies of the XF86Config-4 file, and to copy the correct one in place (perhaps using a script), logout, and restart the Xserver. Many thanks Gareth Deli [EMAIL PROTECTED] --- Mark Vojkovich [EMAIL PROTECTED] wrote: With the CCW option, the server should look exactly like it has a 768x1024 root window from the client's point of view. What does xdpyinfo say about the screen dimensions. Mark. PS. You have to disable the RandR extension to make rotation work properly. That's Option RandR FALSE in the Section ServerFlags, I think. On Fri, 9 Jan 2004, [iso-8859-1] Gareth wrote: Does anyone have any experience of using the Rotate option in Linux? I am using the Mandrake 9.2 distribution, with XFree86 ver 4.3.(0 I think) I am using the NV drivers in order to use the flatscreen in portrait mode. I can rotate the image so it is the correct way up when in portrait mode by adding Rotate CCW to my /etc/X11/XF86Config-4 file But the kde desktop does not resize to match the new resolution (change from 1024 * 768 = 768 * 1024). Do I need to change my Xserver provided with Mandrake to the Xkdrive implementation? If you think this is the wrong place to ask, then please help me to work out where to ask. Many thanks in advance. Gareth Deli Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Trouble switching between portrait and landscape mode by modifying the ~/.xserverrc file
Dear all, I have enclosed parts of 3 files which I have set to try and allow me to alter the mode the X server starts in - be it landscape or portrait. Unfortunately, I do not understand the script in startx enough to work out why this isnt working (that file is the default by the way - i havent changed it) The ~/.xserverrc file has permissions 755. Please could you assist me in working out why my x server -layout option is not being picked up. Regards Gareth Deli I enclose below, the ServerLayout part of my XF86Config-4 file # this is the default server layout as is the first one :o) Section ServerLayout Identifier landscape InputDevice Keyboard1 CoreKeyboard InputDevice Mouse1 CorePointer Screen scr_landscape EndSection Section ServerLayout Identifier portrait InputDevice Keyboard1 CoreKeyboard InputDevice Mouse1 CorePointer Screen scr_portrait EndSection I enclose below, the ~/.xserverrc file #! /bin/sh -layout portrait I enclose below, the first part of my /etc/X11R6/bin/startx file userclientrc=$HOME/.xinitrc userserverrc=$HOME/.xserverrc sysclientrc=/etc/X11/xinit/xinitrc sysserverrc=/etc/X11/xinit/xserverrc defaultclientargs= defaultserverargs= clientargs= serverargs= if [ -f $userclientrc ]; then defaultclientargs=$userclientrc elif [ -f $sysclientrc ]; then defaultclientargs=$sysclientrc fi if [ -f $userserverrc ]; then defaultserverargs=$userserverrc elif [ -f $sysserverrc ]; then defaultserverargs=$sysserverrc fi whoseargs=client while [ x$1 != x ]; do case $1 in /''*|\.*) if [ $whoseargs = client ]; then if [ x$clientargs = x ]; then clientargs=$1 else clientargs=$clientargs $1 fi else if [ x$serverargs = x ]; then serverargs=$1 else serverargs=$serverargs $1 fi fi ;; --) whoseargs=server ;; *) if [ $whoseargs = client ]; then if [ x$clientargs = x ]; then clientargs=$defaultclientargs $1 Yahoo! Messenger - Communicate instantly...Ping your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Xkdrive the Rotate CCW option... - last ditch attempt for help.
Does anyone have any experience of using the Rotate option on a linux desktop with an analogue connected flatscreen? I have been using the proprietry NVIDIA drivers with my GeForce 2 card, but have now switched back to the NV drivers in order to use the flatscreen in portrait mode. So far, I can rotate the image so it is the correct way up with the following command (this bit is easy): Rotate CCW however, i have not managed to get the kde desktop to resize to match the new resolution. Is this where changing from the standard Xserver provided with the distribution to the Xkdrive implementation is required??? At the moment (while in landscape mode) the screen is set to use a virtual size of 1280 * 1024... and if I set this to 1280 * 1600, then I get the effect I want (a taller screen which you have to scroll up and down...), however, when I then enable the Rotate option, the X session fails to start. Presumably it cannot find a suitable resolution, or is confused by the fact the virtual resolution could not be displayed if it were an actual resolution. Please help. I have searched the internet over, and have found no reference to this problem or a howto on setting the XF86Config correctly so the kde desktop size matches the rotated screen resolution. Many thanks in advance. Gareth Deli [EMAIL PROTECTED] (my subscription to the mailing list doesnt seem to want to arrive). ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] X Crashing.
Hi. Recently, X has been crashing on my machine whenever I've left it left alone for more than a few hours. Until a week or so ago, this would happen maybe once a week, but now it's doing it every time. I've asked various friends, all of whom are far wiser than me, but they have no idea. I've included below bits of information it seems you would like. But if I have missed things, please let me know what else you want. Thanks, Gareth - From /var/log/gdm/\:0.log : XFree86 Version 3.3.6a / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: xx November 2000 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.4.13 i686 [ELF] Configured drivers: Mach64: accelerated server for ATI Mach64 graphics adaptors (Patchlevel 1) (using VT number 7) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: keycodes: xfree86 (**) XKB: types: default (**) XKB: compat: default (**) XKB: symbols: en_US(pc101)+gb (**) XKB: geometry: pc (**) Mouse: type: IMPS/2, device: /dev/psaux, buttons: 3 (**) Mach64: Graphics device ID: ATI (**) Mach64: Monitor ID: Samsung (--) Mach64: Mode 1024x768 needs vert refresh rate of 86.96 Hz. Deleted. (--) Mach64: Mode 320x240 needs vert refresh rate of 75.14 Hz. Deleted. (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/ (--) Mach64: PCI: Mach64 RagePro rev 92, Aperture @ 0xf500, Registers @ 0xf410, Block I/O @ 0x9000 (--) Mach64: PCI (92) and CONFIG_CHIP_ID (124) don't agree on ChipRev, using PCI value (--) Mach64: Card type: AGP (--) Mach64: Memory type: SDRAM (4) (--) Mach64: Clock type: Internal (--) Mach64: Maximum allowed dot-clock: 230.000 MHz (**) Mach64: Mode 1024x768: mode clock = 78.750 (--) Mach64: Virtual resolution: 1024x768 (--) Mach64: Video RAM: 8192k (--) Mach64: Using hardware cursor (--) Mach64: Using 16 MB aperture @ 0xf500 (--) Mach64: Using 4 KB register aperture @ 0xf410 (--) Mach64: Ramdac is Internal (--) Mach64: Ramdac speed: 230 MHz (--) Mach64: Pixmap cache: 2 256x256 slots, 8 128x128 slots, 32 64x64 slots (--) Mach64: Font cache: 16 fonts SetKbdSettings - type: 2 rate: 30 delay: 500 snumlk: 0 SetKbdSettings - Succeeded Caught signal 11. Server aborting... eip: 0812cf90 eflags: 00013213 eax: 4137a030 ebx: 0019 ecx: edx: 0400 esi: fffd edi: 00414141 ebp: ba2c esp: b994 Stack: 03ff 02ff ba14 ba18 ba1c ba20 001e 0023 ba24 ba28 0005 00d8 0004 0001 08b3009c 0004 400bfae2 40168e48 0023 02ff 03ff 00d8 0400 000bfc00 41079038 001e ffba 003c Call Trace: 0812cb93 0812cbe0 0812c7d0 08098640 08096063 080960eb 08078cff 080777c1 0806eb85 080b9c07 080a4b7d 080a4de8 080a4ad4 0815fcc4 08095fd8 080a49a2 080a49bb 081b8ce0 0806a400 0806a421 080a44e8 081b8ce0 0806a400 Code: 89 38 8d 65 a8 5b 5e 5f c9 c3 8d b6 00 00 00 00 55 89 e5 83 Please forward information about this crash to [EMAIL PROTECTED] including the _full_ output of the X server. To analyse the crash dump, please type gdb /usr/bin/X11/X /var/lib/gdm/core where and include this output in your report. Thanks! - The core thingy: sqook:/hoome/gareth# gdb /usr/bin/X11/X /var/lib/gdm/core GNU gdb 2002-04-01-cvs Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-linux...(no debugging symbols found)... warning: core file may not match specified executable file. Core was generated by `/usr/bin/X11/X :0 -bpp 24 -deferglyphs 16 -nolisten tcp vt7 -auth /var/lib/gdm/'. Program terminated with signal 5, Trace/breakpoint trap. #0 0x08076859 in ?? () --- ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Rotating the desktop
To whom it may concern, I'm not sure if this is the right place to ask, but is this feature planned for the next release (4.44)? Is it being worked on? If so who do I need to talk to in order to best assist in its development? Thanks Gareth.
[XFree86] Using multiple device sections
All, Does anyone have a Flatscreen working, both in Portrait mode and Landscape mode under XFree86 and Linux? If so, I'd really appreciate some help. I have an NVidia graphics card, and can set an option in the XFree86 config file to rotate the screen to portrait mode, but can not work out how to enable the same sort of functionallity as Windoze, where you can just rotate the screen at the click of a button... is there a way of doing this under XFree86 ? I think that it may be possible be setting up multiple screens (and devices), one being in Portrait mode, and one in landscape, then switch between the 2 in some way. Am I on the right lines? Ive read the XFree86 readme file, and searched the web, but cannot find any reference to what I want to achieve. If anyone has any ideas, Id really appreciate them. Many thanks all. Gareth Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Flatscreens - Portrait - Landscape Mode when changing Res...
I'd really appreciate some help trying to get my new Flatscreen to automatically change its mode (Landscape / portrait) when the resolution is one that best suits that mode. i dont mind hardcoding which resolutions jump into portrait mode, in fact, I expect that is the only way I can do it. I scoured the readme that came with the XF86 download, but cant make anything out for definite. I think that it will be possible, using perhaps multiple displays??? or mode lines but nothing is specifically mentioned, and I dont wish to break the monitor - only had it a day! Im not on the mailing list (due to 14.4Kpbs modem - yes I know I should get a better inet connection! :o) ), so would REALLY appreciate it if people could include this email address when posting any replies. Many many thanks in advance!!! Gareth. [EMAIL PROTECTED] Want to chat instantly with your online friends? Get the FREE Yahoo! Messenger http://uk.messenger.yahoo.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] Missing information from the xkb file for logitech cordless desktop pro keyboard
Regarding: Missing information from the xkb file for logitech cordless desktop pro
keyboard
Email: [EMAIL PROTECTED]
XFree86 Version: 4.2.1
OS: SourceMage GNU/Linux
Area: Xkb config files
Server: not server related
Description:
I have found that some of the key symbols are missing from the
file:/usr/X11/lib/X11/xkb/symbols/inet file, in the section for the logitech cordless
desktop keyboard. I've completed the section, and I'm including it below in case you
want to include it in a future X11 release.
partial alphanumeric_keys
xkb_symbols logicordless {
// Describes the extra keys on a Logitech Desktop Pro keyboard.
name[Group1]= CordLess;
key I5F { [ XF86Standby ] };
key I6D{ [ XF86AudioMedia] };
key I20 { [ XF86AudioMute ] };
key I2E { [ XF86AudioLowerVolume ] };
key I30 { [ XF86AudioRaiseVolume ] };
key I22 { [ XF86AudioPlay ] };
key I24 { [ XF86AudioStop ] };
key I10 { [ XF86AudioPrev ] };
key I19 { [ XF86AudioNext ] };
key I32 { [ XF86HomePage ] };
key I6C { [ XF86Mail ] };
key I65 { [ XF86Search] };
key I66 { [ XF86Start ] };
key I11 { [ XF86Community ] };
key I14 { [ XF86Shop ] };
key I66 { [ XF86Favorites ] };
key I69 { [ XF86OpenURL ] };
key I12 { [ XF86WWW ] };
key I6A { [ XF86Back ] };
key I13 { [ XF86VendorHome] };
};
I've used XF86WWW for a button that is actually marked Webcam, XF86VendorHome for a
button marked iTouch and XF86Community for a button marked Messenger/SMS. The
other additions are pretty self explanatory.
I have this keyboard myself and have tested the bindings to make sure they work :)
I hope this helps you,
Gareth
Repeat By:
Well, if you have one of these keyboards, tell X to load the symbols using
Option XkbRules xfree86
Option XkbModel logicordless
in the XF86Config file. Without my additions, you'll find that some of the hotkeys are
unbound. My additions to the /usr/X11/lib/X11/xkb/symbols/inet file fixes this.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
RE: [Dri-devel] Re: GL testing Re: [Xpert]problem with ati and mandrake 8.1
On Sun, 3 Feb 2002, Dr Andrew C Aitchison wrote: On Sun, 3 Feb 2002, Vladimir Dergachev wrote: In fact, I do not even know a good app to test GL functionality, not perfomance (i.e that all calls do as they should and do not crash the machine). I'm fairly sure that there is an OpenGL test suite; although I doubt that it is freely available. Should XFree86 (or another organization) have a licence that can be used to test DRI ? Well, I tried to search for one and asking on DRI list.. I was not able to compile the GL benchmark (viewperf ?) and there was nothing better, so in the end I settled for testing with Quake, Descent and glxgears. Try glean: http://glean.sourceforge.net/ -- Gareth ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]RE: [Dri-devel] Re: [GATOS]Re: Bugfix for br0ken DMA on r128 andpossibly radeonDMA functions
That's too bad because this will imply a _lot_ of hair in the drivers. That's the way it has to be, for the DRM code to remain in the stock kernel distro. Linus has make this crystal clear. The fact is that we have a driver split several ways: 3 portions from XFree tree (2d, 2d and drm), capture (km, GATOS) and kernel framebuffer. The only right way, IMO, is to simply request that all driver versions must match. Maybe it is good idea to change drm to allow driver libraries, where we do not simply request radeon driver but, radeon driver version X.Y.Z The only safe way to ensure this is to distribute the drivers (all parts) as a separate package. There are obviously pros and cons to doing it that way. Now, I'll be the first to agree that for this particular change (memory controller) we can get by with one extra IOCTL or poking in the card's registers or even passing invormation in the lower bits of aperture addresses MS-Windows style. The problem is what the code is going look like.. And the more important question is: what it will look like after another change like that ? This memory controller patch is not the last change that would make DRM incompatible with older drivers. Let me see: * TV out might cause it to happen again (I don't know as this code has not been written yet) * 8500 3d driver might do it too. * whatever ATI might come up with next. Perhaps, if we were able to start from scratch, we could come up with a clean way to avoid these problems. Unfortunately, a lot of the early design decisions were made when, quite frankly, we didn't understand the current -- and future -- hardware well enough. So, it is possible to make this change work, but I do not see this worth it in the end. What you're suggesting boils down to shipping the DRI drivers (incl. the DRM portions) as a separete package. If you can't maintain backwards compatibility, this is the way it will be. End of story. -- Gareth ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]RE: [Dri-devel] Re: [GATOS]Re: Bugfix for br0ken DMA o n r128 andpossibly radeonDMA functions
I can't believe I am hearing this. The major benifit of free software is that if there is a new and better design you can try it out and then everyone can upgrade. It's not as if we are charging them money they way Microsoft does. Are you saying that progress stops with the inclusion of the driver into the kernel tree ? Could it be that you misunderstood Linus and he meant: during stable series ? No, there was no misunderstanding. You can't update the DRM code in the kernel in such a way that it breaks older versions of the 2D and 3D drivers. Simple as that. As for understanding the hardware - you can't possibly understand which has not been released yet. Heck, with the state of things that is now, we often don't know details about the hardware that was just released. That's my point. We didn't know how to program the offsets, hence the current situation. -- Gareth ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RE: [Dri-devel] Re: [GATOS]Re: Bugfix for br0ken DMA on r128 andpossibly radeonDMA functions
The assumption was only made for experimental GATOS drivers. It is a practical one. More people come and ask: I upgraded to GATOS driver and DRI won't work anymore ! Answer: RTFM, upgrade drm driver. It's already been determined that: I just upgraded my kernel, and DRI won't work anymore! RTFM, upgrade your X server I just upgraded my X server, and DRI doesn't work anymore! RTFM, upgrade your kernel just doesn't cut it. You aren't allowed to do anything that requires a response of RTFM, upgrade ... Start thinking of alternatives... -- Gareth ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RE: [Dri-devel] Re: [GATOS]Re: Bugfix for br0ken DMA on r128 andpossibly radeonDMA functions
Gareth, the current driver is broken. If someone wants to use video capture they _need_ both GATOS 2d driver and GATOS drm driver, period. What's so wrong about upgrading ? Guaranteed, someone will get a mismatch -- your changes may go back into the stock kernel, breaking DRI CVS or whatever, who knows. Forcing everyone to upgrade their kernel, 2D and 3D drivers to the right magic revision is a recipe for disaster, one that the kernel people have already kicked our arses over (rightly so). Also, I can make drm driver work nice with older 2d drivers - as soon as someone will show me a way to tell the version of the 2d driver that is accessing the drm driver. Sounds like it'll need a 2D driver upgrade :-) -- Gareth ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RE: [Dri-devel] [PATCH] 4.2.0 DRM fixes to delay loops
Mike A. Harris wrote: The i830 DRM driver contains empty for loops used for short delays. Modern gcc and other compilers, when used with optimization switches will optimize these empty for loops out, leaving no delay. In addition, CPU's such as the Pentium 4, will needlessly overheat when executing empty for loops such as this (assuming they're not optimized out by the compiler) which can cause the chip to kick in it's thermal protection and lower the CPU speed. You've got to be kidding... The P4 docs suggest using a PAUSE insn to reduce the otherwise-huge branch misprediction penalty associated with busy-wait loops like this. It also allows the processor to consume less power, which is handy for mobile platforms. To suggest that a busy-wait loop will cause the processor to overheat (given a functioning -- and attached -- heatsink/fan combo) and kick in the thermal protection is absurd! :-) Instead of using empty for loops for delays, udelay() should be used to provide delays. Either way, this is A Good Thing(TM). -- Gareth ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
