Management of disconnected Monitors
Hi, i want to know how awesome manages Monitors when they are disconnected and connect. My scenario is the following. I have three LCD Monitors on my workstation. I use a AMD/ATI Radeon 5770 with 5 mini Displayports to which 3 HP ZR24W are connected via DP. I also use the proprietary driver fglrx so i can use the eyefinity feature (although some say it's also working with the opensource driver). With this feature i don't need xinerama or a second GPU to use all 3 LCDs. When i start awesome i have 3 different workspaces on each screen. So when i open a application in fullscreen it will just fill one screen. When i switch between the workspace numbers that only affects one screen. So they are all seperated from each other although i can move windows from screen to screen. I guess that's the default behaviour for awesome with Multi-Head. So now it comes to the question. When i turn off one of the screens, or all, and i turn it/them back on, everything is still on the screen/place it had before the turning off/on. I also recognized that when i turn my right screen off i can still move my mouse there and grab the window without seeing it and move it to the middle or left screen. When i use i3 (my second WindowManager), the behaviour is different. As soon as i turn one screen off, all the windows and workspaces move to one of the screens that are still turned on. What does awesome to prevent the issue i have with i3? Awesome acts exactly how i need it. I turn off all my 3 LCDs when i leave my place and when i return i turn them on and want everything on the places and screens they had before i left. But how does awesome manage this? Does awesome ignore turning off/on? Or is there a nice handling for active and inactive Displays? I hope i could make my issue clear enough :) Greetings, Andi -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
hello, I suppose (but probably Uli, Julien or anxrc will be able to clarify it) that awesome takes info about monitors straight from RandR. You can check that even after the monitor is switched off, 'xrandr -q' still reports it as connected. I don't know how i3 handles that. As for the driver - for me the opensource one works better, and I have very similar hardware config (5750 with 3 monitors). Here is the link to my post with config and screenshot in case you would like to try it: https://bbs.archlinux.org/viewtopic.php?pid=984396#p984396 greetings, Paweł 2011/11/15 andreas herza...@gmail.com: Hi, i want to know how awesome manages Monitors when they are disconnected and connect. My scenario is the following. I have three LCD Monitors on my workstation. I use a AMD/ATI Radeon 5770 with 5 mini Displayports to which 3 HP ZR24W are connected via DP. I also use the proprietary driver fglrx so i can use the eyefinity feature (although some say it's also working with the opensource driver). With this feature i don't need xinerama or a second GPU to use all 3 LCDs. When i start awesome i have 3 different workspaces on each screen. So when i open a application in fullscreen it will just fill one screen. When i switch between the workspace numbers that only affects one screen. So they are all seperated from each other although i can move windows from screen to screen. I guess that's the default behaviour for awesome with Multi-Head. So now it comes to the question. When i turn off one of the screens, or all, and i turn it/them back on, everything is still on the screen/place it had before the turning off/on. I also recognized that when i turn my right screen off i can still move my mouse there and grab the window without seeing it and move it to the middle or left screen. When i use i3 (my second WindowManager), the behaviour is different. As soon as i turn one screen off, all the windows and workspaces move to one of the screens that are still turned on. What does awesome to prevent the issue i have with i3? Awesome acts exactly how i need it. I turn off all my 3 LCDs when i leave my place and when i return i turn them on and want everything on the places and screens they had before i left. But how does awesome manage this? Does awesome ignore turning off/on? Or is there a nice handling for active and inactive Displays? I hope i could make my issue clear enough :) Greetings, Andi -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org. -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
On Tue, Nov 15 2011, andreas wrote: What does awesome to prevent the issue i have with i3? Awesome acts exactly how i need it. I turn off all my 3 LCDs when i leave my place and when i return i turn them on and want everything on the places and screens they had before i left. But how does awesome manage this? Does awesome ignore turning off/on? Or is there a nice handling for active and inactive Displays? Well, awesome does nothing actually. The screens are managed via xrandr, but AFAICT, turning one off does not set the screen configuration provided by RandR, so awesome does nothing. :) You can probably check that via the xrandr command. -- Julien Danjou pgpXaUGrN9ujE.pgp Description: PGP signature
Re: Management of disconnected Monitors
2011/11/15 andreas herza...@gmail.com: On 11/15/2011 01:00 PM, Paweł Rumian wrote: I suppose (but probably Uli, Julien or anxrc will be able to clarify it) that awesome takes info about monitors straight from RandR. You can check that even after the monitor is switched off, 'xrandr -q' still reports it as connected. I don't know how i3 handles that. Hmm i just used ssh and i get Can't open display but i will test it when i'm back at my workstation at home. Yes, you need to do this locally. As for the driver - for me the opensource one works better, and I have very similar hardware config (5750 with 3 monitors). Here is the link to my post with config and screenshot in case you would like to try it: https://bbs.archlinux.org/viewtopic.php?pid=984396#p984396 In what way does the OS driver work better? The problem is i also want to use the 3d acceleration for some games. But i guess i should give the OS drivers a try. I switched to OS drivers some time ago so I'm not sure about current state of fglrx, but the binary drivers used to crash sometimes (which never happened with OS ones) and I had troubles when using hibernation. I remember there was also a problem using xrandr, but from what you wrote it seems it is no more an issue. In the open drivers I also have the ablility to tune them to low clocks manually - there is an issue with power consumption on ATI cards with more then one screen attached. Here is a quick first link from google - it is about Windows, but the problem is the same: http://forums.anandtech.com/showthread.php?t=2066336 Anyway, if you are using 3d games I think you have a very limited choice (I don't care about 3d, thats why I had no troubles in switching to open drivers, but AFAIK they don't support 3d acceleration yet), but of course you still can try :) greetings, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
On 11/15/2011 01:38 PM, Uli Schlachter wrote: BTW: You *are* using Xinerama. That's how multi-head works in X11 (as long as you want to be able to move windows between screens, without that feature you can disable Xinerama and use protocol screens). Xinerama would result in lower performance and the Xinerama Option in amdcccle ist turned off. I used Xinerama in the past when there was no other possibility but with eyefinity support in fglrx i completely disabled xinerama. I can activate it within the AMD Control Center but it's definitely turned off there. But this may be a special AMD fglrx feature to work without xinerama. Andi -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
On 15.11.2011 13:43, andreas wrote: On 11/15/2011 01:38 PM, Uli Schlachter wrote: BTW: You *are* using Xinerama. That's how multi-head works in X11 (as long as you want to be able to move windows between screens, without that feature you can disable Xinerama and use protocol screens). Xinerama would result in lower performance and the Xinerama Option in amdcccle ist turned off. I used Xinerama in the past when there was no other possibility but with eyefinity support in fglrx i completely disabled xinerama. I can activate it within the AMD Control Center but it's definitely turned off there. But this may be a special AMD fglrx feature to work without xinerama. In that case you would only get a single, big screen stretched across all monitors from awesome. Xinerama is how awesome figures out which monitors you have and where their viewport is on the root window. I bet that the following command will confirm that Xinerama is enabled: $ xdpyinfo -ext XINERAMA | tail -n 10 Uli P.S.: For your original problem, I guess you would be better off asking on an i3 mailing list instead of awesome's. -- For saving the Earth.. and eating cheesecake! -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
On 11/15/2011 04:20 PM, Uli Schlachter wrote: I bet that the following command will confirm that Xinerama is enabled: $ xdpyinfo -ext XINERAMA | tail -n 10 I use gentoo with -xinerama useflag :) So xdpyinfo says XINERAMA extension not supported by xdpyinfo. But i will recompile it with +xinerama to see if there is any information about xinerama. P.S.: For your original problem, I guess you would be better off asking on an i3 mailing list instead of awesome's. This is why i asked here, because i wanted to know how awesome manages the screens, so i can help the i3 dev to get this working with i3 :) -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
I use gentoo with -xinerama useflag :) So xdpyinfo says XINERAMA extension not supported by xdpyinfo. Strange, because on my gentoo box with USE='-xinerama' I have: $ xdpyinfo -ext XINERAMA | tail -n 5 XINERAMA version 1.1 opcode: 150 head #0: 1280x1024 @ 2960,0 head #1: 1280x1024 @ 0,0 head #2: 1680x1050 @ 1280,0 I guess your output may be because of the closed drivers, but Uli is right - you may not have Xinerama enabled explicitely, but it must be used somewhere under the hood. greetings, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
On 11/15/2011 04:53 PM, Paweł Rumian wrote: I use gentoo with -xinerama useflag :) So xdpyinfo says XINERAMA extension not supported by xdpyinfo. Strange, because on my gentoo box with USE='-xinerama' I have: $ xdpyinfo -ext XINERAMA | tail -n 5 I ran it and i get this: http://paste.geekosphere.org/ep0o And to the xrandr -q output: 1. All 3 turned on: http://paste.geekosphere.org/4a8p 2. One turned off: http://paste.geekosphere.org/l18t As you can see DFP3 is marked disconnected but i can still move my mouse there etc. And i checked the Xinerama setting in amdcccle. It says You currently have only one desktop enabled. Configuring more than one desktop in the Display Manager will allow you to configure Xinerama. But i have Multi-Display active on the Display-Manager section :) It's called Multi-display Desktop with display(s) X,Y there. Maybe you can help me with further informations about awesome working with this setup. Thanks so far for your help! Andi -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: Management of disconnected Monitors
I'm afraid I cannot help you further, because my experience is limited to system running open drivers, which seems to behave totally different - especially it still reports the monitor as connected even if it is switched off and has more clear reports on Xinerama (in your list of extensions it is listed twice, which I personally do not understand). Maybe someone else with deeper knowledge will be able to clarify these things. greetings, Paweł -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: amixer hangs
Le lundi 14 novembre 2011 à 23:53 -0200, Daniel Hilst a écrit : On 11/14/2011 04:28 PM, Adrian C. wrote: On Mon, 14 Nov 2011, Daniel Hilst Selli wrote: Thanks Adrian, I'm installing awesome from git But from 3.4 branch, if you want stable. Yes, I do thanks! I have already installed it, but now I'm facing problems with my rc.lua. Like widget() and awful.widget:set_color_gradient() are nil, is there any docs for new api? []'s You can found the luadoc on your system. For me it's located here : file:///usr/share/doc/awesome/luadoc/index.html By the way, if you need a simple way to control pulseaudio sink volume, you can use my little command tool pamixer [1]. Clément Démoulins [1] https://github.com/cdemoulins/pamixer -- Clef GPG : 0xDD51E028 signature.asc Description: This is a digitally signed message part
Re: amixer hangs
On 11/15/11 17:23, Clément Démoulins wrote: Le lundi 14 novembre 2011 à 23:53 -0200, Daniel Hilst a écrit : On 11/14/2011 04:28 PM, Adrian C. wrote: On Mon, 14 Nov 2011, Daniel Hilst Selli wrote: Thanks Adrian, I'm installing awesome from git But from 3.4 branch, if you want stable. Yes, I do thanks! I have already installed it, but now I'm facing problems with my rc.lua. Like widget() and awful.widget:set_color_gradient() are nil, is there any docs for new api? []'s You can found the luadoc on your system. For me it's located here : file:///usr/share/doc/awesome/luadoc/index.html Thanks ! By the way, if you need a simple way to control pulseaudio sink volume, you can use my little command tool pamixer [1]. Clément Démoulins [1] https://github.com/cdemoulins/pamixer -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
Re: amixer hangs
Cool that kind of example, I was searching for! 2011/11/15 Clément Démoulins clem...@archivel.fr: Le lundi 14 novembre 2011 à 23:53 -0200, Daniel Hilst a écrit : On 11/14/2011 04:28 PM, Adrian C. wrote: On Mon, 14 Nov 2011, Daniel Hilst Selli wrote: Thanks Adrian, I'm installing awesome from git But from 3.4 branch, if you want stable. Yes, I do thanks! I have already installed it, but now I'm facing problems with my rc.lua. Like widget() and awful.widget:set_color_gradient() are nil, is there any docs for new api? []'s You can found the luadoc on your system. For me it's located here : file:///usr/share/doc/awesome/luadoc/index.html By the way, if you need a simple way to control pulseaudio sink volume, you can use my little command tool pamixer [1]. Clément Démoulins [1] https://github.com/cdemoulins/pamixer -- Clef GPG : 0xDD51E028 -- Gruß Jörg -- To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.
[awesome bugs] #762 - mozplugger freezes desktop (works in wmii)
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY. The following task has a new comment added: FS#762 - mozplugger freezes desktop (works in wmii) User who did this - Thomas Koch (thkoch2001) -- This bug is also reported for Debian[1] and mozplugger[2]. And I just got hit by it. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609215 [2] https://www.mozdev.org/bugs/show_bug.cgi?id=23600 -- More information can be found at the following URL: https://awesome.naquadah.org/bugs/index.php?do=detailstask_id=762#comment2771 You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above. -- To unsubscribe, send mail to awesome-devel-unsubscr...@naquadah.org.
