Re: nouveau driver freeze -- can anyone else reproduce this?
Give credit to uncle Ben https://admin.fedoraproject.org/updates/libdrm-2.4.61-3.fc22 https://kojipkgs.fedoraproject.org/packages/libdrm/2.4.61/3.fc22/x86_64/ -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On 06.05.2015 21:05, poma wrote:
On 28.04.2015 20:03, poma wrote:
On 27.04.2015 11:51, Joerg Lechner wrote:
Hi,
the reason why I ask again, if really the nouveau driver is active, when
using Geeqie, is a look into /var/log/Xorg.0.log,
where in my case (hybrid grafics intel/nvidia) I don't find the nouveau
driver, which would explain, why I don't have
the error described in this thread.
see part of /var/log/Xorg.0.log:
148.883]Module class: X.Org Video Driver
[ 148.883]ABI class: X.Org Video Driver, version 19.0
[ 148.883] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35,
Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[ 148.884] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200,
6200, P6300
Therefore my question in case of Matthews Lenovo, is it really the nouveau
driver or another video driver,
which causes the Geeqie error?
Kind Regards
-Ursprüngliche Mitteilung-
Von: Matthew Miller mat...@fedoraproject.org
An: For testing and quality assurance of Fedora releases
test@lists.fedoraproject.org
Verschickt: So, 26 Apr 2015 9:25 pm
Betreff: Re: nouveau driver freeze -- can anyone else reproduce this?
On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote:
What kind of menu
is that? How big is it (height / width in pixels) ?
It's the right-click
context menu you get when clicking on a filename
in geeqie. It's nothing
special -- 14 items in three groups, with View
in new window being the
longest item. 150x300 pixels, maybe?
OK so nothing special about it ...
odd.
Yeah. I did get what seemed like the same behavior with a context menu
in
Gimp *once*, but can't reproduce there. However, geeqie seems to
very reliably
trigger it. And it seems to be only _that_ right-click
menu, in the filelist,
not others in the app. I guess I can go around
right-clicking in other programs
to see if it happens.
One thing that occurs to me is that the placement of this
menu means
that when it comes up, it almost always comes up on top of a
scrollbar
and into another panel. *Maybe* that interaction causes some
rendering
need which triggers the bug? Seems like a longshot, and I really
don't
know what I'm talking about here. :)
If I understood Ilia,
https://bugs.freedesktop.org/show_bug.cgi?id=89842#c5
the problem is somewhere in between:
libdrm-2.4.60
http://cgit.freedesktop.org/mesa/drm/commit/?id=5f7b672
libdrm-2.4.59
http://cgit.freedesktop.org/mesa/drm/commit/?id=d2e0f55
i.e.
74 commitas
What are you waiting for? :)
man 1 git-bisect
https://bugs.freedesktop.org/show_bug.cgi?id=89842#c10
Thus you can quickly test whether Skeggs's commit really works:
$ cd ~/rpmbuild/SOURCES/
$ git clone git://pkgs.fedoraproject.org/libdrm.git .
$ sed -i 's/#define gitdate 20130117/%define gitdate 20150506/' libdrm.spec
$ sed -i 's/: 1/: 100/' libdrm.spec
$ sed -i 's/%patch5/#%patch5/' libdrm.spec
$ sed -i
'/dr[im]stat\|get[csv]\|name_from_fd\|openclose\|setversion\|updatedraw\|bindir}\/exynos/d'
libdrm.spec
$ sed -i '/kmstest/ a\%{_bindir}/proptest' libdrm.spec
$ ./make-git-snapshot.sh
$ pkexec yum-builddep libdrm
$ rpmbuild -ba libdrm.spec
--
test mailing list
test@lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On 28.04.2015 20:03, poma wrote: On 27.04.2015 11:51, Joerg Lechner wrote: Hi, the reason why I ask again, if really the nouveau driver is active, when using Geeqie, is a look into /var/log/Xorg.0.log, where in my case (hybrid grafics intel/nvidia) I don't find the nouveau driver, which would explain, why I don't have the error described in this thread. see part of /var/log/Xorg.0.log: 148.883]Module class: X.Org Video Driver [ 148.883]ABI class: X.Org Video Driver, version 19.0 [ 148.883] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 148.884] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 Therefore my question in case of Matthews Lenovo, is it really the nouveau driver or another video driver, which causes the Geeqie error? Kind Regards -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: So, 26 Apr 2015 9:25 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote: What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. Yeah. I did get what seemed like the same behavior with a context menu in Gimp *once*, but can't reproduce there. However, geeqie seems to very reliably trigger it. And it seems to be only _that_ right-click menu, in the filelist, not others in the app. I guess I can go around right-clicking in other programs to see if it happens. One thing that occurs to me is that the placement of this menu means that when it comes up, it almost always comes up on top of a scrollbar and into another panel. *Maybe* that interaction causes some rendering need which triggers the bug? Seems like a longshot, and I really don't know what I'm talking about here. :) If I understood Ilia, https://bugs.freedesktop.org/show_bug.cgi?id=89842#c5 the problem is somewhere in between: libdrm-2.4.60 http://cgit.freedesktop.org/mesa/drm/commit/?id=5f7b672 libdrm-2.4.59 http://cgit.freedesktop.org/mesa/drm/commit/?id=d2e0f55 i.e. 74 commitas What are you waiting for? :) man 1 git-bisect https://bugs.freedesktop.org/show_bug.cgi?id=89842#c10 -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Sat, Apr 25, 2015 at 09:45:41AM -0400, Matthew Miller wrote: https://bugzilla.redhat.com/show_bug.cgi?id=1215329 I'm not sure exactly *why* this _particular_ context menu triggers destruction, but: 1. run geeqie in a directory with a number of jpg files 2. right click on one of those files in the list 3. boom From upstream, this appears to be a regression in libdrm; going to libdrm-2.4.59 makes the problem disappear (and apparently also a bunch of other freezes). -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On 27.04.2015 19:58, Joerg Lechner wrote: Hi, would like to try, but vgaswitcheroo seems to be ubuntu, can not find this in F22 directory in /.../debug If possible I would like to switch to Nvidia chip without using an second external screen but using the Nouveau driver, to test this Geeqie problem. Is there a similar tool in F22 as switcheroo in Ubuntu? Kind Regards -Ursprüngliche Mitteilung- Von: AV volov...@ziggo.nl An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: Mo, 27 Apr 2015 6:21 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On 04/27/2015 02:17 PM, Matthew Miller wrote: On Mon, Apr 27, 2015 at 04:48:37AM -0400, Joerg Lechner wrote: If it's an optimus, is in case of Geeqie the Nvidia Driver activen or another driver ? It is indeed Optimus. Out of the box, Fedora doesn't support switching as Windows does. There are some experimental support for this http://bumblebee-project.org/, but it's not very active. So, failing that, you can switch in the BIOS setup screen. In my case, since I'm using an external monitor, I needed to set it to Nvidia, because the Intel GPU is only attached to the laptop's built-in screen. My experience is that since the inclusion of PRIME gpu offloading the nouveau driver seems to handle power management and switching adequately by itself, at least on older Nvidia Optimus chips. And you can get relevant info on the state through: # cat /sys/kernel/debug/vgaswitcheroo/switch And turn on/off the gpu driving the output by # echo ON/OFF /sys/kernel/debug/vgaswitcheroo/switch Connect the graphics connectors with: # echo IGD/DIS /sys/kernel/debug/vgaswitcheroo/switch AV http://nouveau.freedesktop.org/wiki/Optimus/ What I remember I played successfully with DRI setups a few months back. But this machine isn't currently here. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On 27.04.2015 11:51, Joerg Lechner wrote: Hi, the reason why I ask again, if really the nouveau driver is active, when using Geeqie, is a look into /var/log/Xorg.0.log, where in my case (hybrid grafics intel/nvidia) I don't find the nouveau driver, which would explain, why I don't have the error described in this thread. see part of /var/log/Xorg.0.log: 148.883]Module class: X.Org Video Driver [ 148.883]ABI class: X.Org Video Driver, version 19.0 [ 148.883] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 148.884] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 Therefore my question in case of Matthews Lenovo, is it really the nouveau driver or another video driver, which causes the Geeqie error? Kind Regards -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: So, 26 Apr 2015 9:25 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote: What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. Yeah. I did get what seemed like the same behavior with a context menu in Gimp *once*, but can't reproduce there. However, geeqie seems to very reliably trigger it. And it seems to be only _that_ right-click menu, in the filelist, not others in the app. I guess I can go around right-clicking in other programs to see if it happens. One thing that occurs to me is that the placement of this menu means that when it comes up, it almost always comes up on top of a scrollbar and into another panel. *Maybe* that interaction causes some rendering need which triggers the bug? Seems like a longshot, and I really don't know what I'm talking about here. :) If I understood Ilia, https://bugs.freedesktop.org/show_bug.cgi?id=89842#c5 the problem is somewhere in between: libdrm-2.4.60 http://cgit.freedesktop.org/mesa/drm/commit/?id=5f7b672 libdrm-2.4.59 http://cgit.freedesktop.org/mesa/drm/commit/?id=d2e0f55 i.e. 74 commitas What are you waiting for? :) man 1 git-bisect -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On 26.04.2015 12:51, Joerg Lechner wrote: Hi, is it possible that this effect is a hardware dependency? As I mentioned I have tested this procedure as Matthew has said, I didn't find this error. My hardware is an Acer Aspire E 15 with hybrid grafics (Intel/Nvidia), but Nvidia does not work with Fedora because of the not working Nvidia driver, therefore in Linux the Intel grafics chip is the only active (Nouveau driver). What!? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
Hi, the reason why I ask again, if really the nouveau driver is active, when using Geeqie, is a look into /var/log/Xorg.0.log, where in my case (hybrid grafics intel/nvidia) I don't find the nouveau driver, which would explain, why I don't have the error described in this thread. see part of /var/log/Xorg.0.log: 148.883]Module class: X.Org Video Driver [ 148.883]ABI class: X.Org Video Driver, version 19.0 [ 148.883] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 [ 148.884] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000 [ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100 [ 148.884] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300 Therefore my question in case of Matthews Lenovo, is it really the nouveau driver or another video driver, which causes the Geeqie error? Kind Regards -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: So, 26 Apr 2015 9:25 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote: What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. Yeah. I did get what seemed like the same behavior with a context menu in Gimp *once*, but can't reproduce there. However, geeqie seems to very reliably trigger it. And it seems to be only _that_ right-click menu, in the filelist, not others in the app. I guess I can go around right-clicking in other programs to see if it happens. One thing that occurs to me is that the placement of this menu means that when it comes up, it almost always comes up on top of a scrollbar and into another panel. *Maybe* that interaction causes some rendering need which triggers the bug? Seems like a longshot, and I really don't know what I'm talking about here. :) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
Hi To this video driver problem I want to ask: As I said I can not reproduce this Geeqie behaviour. In my laptop I have hybrid grafic, something from Intel and a NVIDIA Geforce 840M. I found 2 video drivers installed: Xorg-x11-drv-intel-2.99.917-6.20150.x86_64 and Xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64 As it seems to be in MS Windows 8.1 normal use in grafics is the Intel Chip and only with high grafic load the Nvidia chip is added. Testing now this Geeqie problem how can I test which driver is used Intel or Nouveau. Is in F22 always Nouveau and the Nvidia chip is used, or is it similar to MS Windows? Kind Regards -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: So, 26 Apr 2015 9:25 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote: What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. Yeah. I did get what seemed like the same behavior with a context menu in Gimp *once*, but can't reproduce there. However, geeqie seems to very reliably trigger it. And it seems to be only _that_ right-click menu, in the filelist, not others in the app. I guess I can go around right-clicking in other programs to see if it happens. One thing that occurs to me is that the placement of this menu means that when it comes up, it almost always comes up on top of a scrollbar and into another panel. *Maybe* that interaction causes some rendering need which triggers the bug? Seems like a longshot, and I really don't know what I'm talking about here. :) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
Can it be that Your ThinkPad W530 is an Optimus with Hybrid Grafics like mine Acer? OpenGL (Open Graphics Library) A note out of the Thinkpad W530 homepage: ThinkPad W530 Up to 1GB of dedicated video memory enables graphic-intensive applications. Up to NVIDIA® Quadro® K2000M. If it's an optimus, is in case of Geeqie the Nvidia Driver activen or another driver ? -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: So, 26 Apr 2015 9:25 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote: What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. Yeah. I did get what seemed like the same behavior with a context menu in Gimp *once*, but can't reproduce there. However, geeqie seems to very reliably trigger it. And it seems to be only _that_ right-click menu, in the filelist, not others in the app. I guess I can go around right-clicking in other programs to see if it happens. One thing that occurs to me is that the placement of this menu means that when it comes up, it almost always comes up on top of a scrollbar and into another panel. *Maybe* that interaction causes some rendering need which triggers the bug? Seems like a longshot, and I really don't know what I'm talking about here. :) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Mon, Apr 27, 2015 at 04:48:37AM -0400, Joerg Lechner wrote: If it's an optimus, is in case of Geeqie the Nvidia Driver activen or another driver ? It is indeed Optimus. Out of the box, Fedora doesn't support switching as Windows does. There are some experimental support for this http://bumblebee-project.org/, but it's not very active. So, failing that, you can switch in the BIOS setup screen. In my case, since I'm using an external monitor, I needed to set it to Nvidia, because the Intel GPU is only attached to the laptop's built-in screen. -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On 04/27/2015 02:17 PM, Matthew Miller wrote: On Mon, Apr 27, 2015 at 04:48:37AM -0400, Joerg Lechner wrote: If it's an optimus, is in case of Geeqie the Nvidia Driver activen or another driver ? It is indeed Optimus. Out of the box, Fedora doesn't support switching as Windows does. There are some experimental support for this http://bumblebee-project.org/, but it's not very active. So, failing that, you can switch in the BIOS setup screen. In my case, since I'm using an external monitor, I needed to set it to Nvidia, because the Intel GPU is only attached to the laptop's built-in screen. My experience is that since the inclusion of PRIME gpu offloading the nouveau driver seems to handle power management and switching adequately by itself, at least on older Nvidia Optimus chips. And you can get relevant info on the state through: # cat /sys/kernel/debug/vgaswitcheroo/switch And turn on/off the gpu driving the output by # echo ON/OFF /sys/kernel/debug/vgaswitcheroo/switch Connect the graphics connectors with: # echo IGD/DIS /sys/kernel/debug/vgaswitcheroo/switch AV -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
Hi, would like to try, but vgaswitcheroo seems to be ubuntu, can not find this in F22 directory in /.../debug If possible I would like to switch to Nvidia chip without using an second external screen but using the Nouveau driver, to test this Geeqie problem. Is there a similar tool in F22 as switcheroo in Ubuntu? Kind Regards -Ursprüngliche Mitteilung- Von: AV volov...@ziggo.nl An: For testing and quality assurance of Fedora releases test@lists.fedoraproject.org Verschickt: Mo, 27 Apr 2015 6:21 pm Betreff: Re: nouveau driver freeze -- can anyone else reproduce this? On 04/27/2015 02:17 PM, Matthew Miller wrote: On Mon, Apr 27, 2015 at 04:48:37AM -0400, Joerg Lechner wrote: If it's an optimus, is in case of Geeqie the Nvidia Driver activen or another driver ? It is indeed Optimus. Out of the box, Fedora doesn't support switching as Windows does. There are some experimental support for this http://bumblebee-project.org/, but it's not very active. So, failing that, you can switch in the BIOS setup screen. In my case, since I'm using an external monitor, I needed to set it to Nvidia, because the Intel GPU is only attached to the laptop's built-in screen. My experience is that since the inclusion of PRIME gpu offloading the nouveau driver seems to handle power management and switching adequately by itself, at least on older Nvidia Optimus chips. And you can get relevant info on the state through: # cat /sys/kernel/debug/vgaswitcheroo/switch And turn on/off the gpu driving the output by # echo ON/OFF /sys/kernel/debug/vgaswitcheroo/switch Connect the graphics connectors with: # echo IGD/DIS /sys/kernel/debug/vgaswitcheroo/switch AV -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
Hi, is it possible that this effect is a hardware dependency? As I mentioned I have tested this procedure as Matthew has said, I didn't find this error. My hardware is an Acer Aspire E 15 with hybrid grafics (Intel/Nvidia), but Nvidia does not work with Fedora because of the not working Nvidia driver, therefore in Linux the Intel grafics chip is the only active (Nouveau driver). Kind Regards -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: test test@lists.fedoraproject.org Verschickt: Sa, 25 Apr 2015 3:45 pm Betreff: nouveau driver freeze -- can anyone else reproduce this? https://bugzilla.redhat.com/show_bug.cgi?id=1215329 I'm not sure exactly *why* this _particular_ context menu triggers destruction, but: 1. run geeqie in a directory with a number of jpg files 2. right click on one of those files in the list 3. boom Can anyone else reproduce? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Sun, Apr 26, 2015 at 06:51:56AM -0400, Joerg Lechner wrote: is it possible that this effect is a hardware dependency? As I mentioned I have tested this procedure as Matthew has said, I didn't find this error. My hardware is an Acer Aspire E 15 with hybrid grafics (Intel/Nvidia), but Nvidia does not work with Fedora because of the not working Nvidia driver, therefore in Linux the Intel grafics chip is the only active (Nouveau driver). It definitely might be model specific. I should also add that I'm in Gnome — it might be something with the way the menus are rendered there. But, note that if you're using the Nouveau driver, that's actually the Nvidia chip. If it were using the Intel part, you'd see the Intel driver. (I'd just use the Intel driver as a workaround, but I'm using and external monitor, and unfortunately that only works with the Nvidia side.) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Sun, Apr 26, 2015 at 07:45:11PM +0200, drago01 wrote: It definitely might be model specific. I should also add that I'm in Gnome — it might be something with the way the menus are rendered there. What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Sun, Apr 26, 2015 at 8:03 PM, Matthew Miller mat...@fedoraproject.org wrote: On Sun, Apr 26, 2015 at 07:45:11PM +0200, drago01 wrote: It definitely might be model specific. I should also add that I'm in Gnome — it might be something with the way the menus are rendered there. What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Sun, Apr 26, 2015 at 7:38 PM, Matthew Miller mat...@fedoraproject.org wrote: On Sun, Apr 26, 2015 at 06:51:56AM -0400, Joerg Lechner wrote: is it possible that this effect is a hardware dependency? As I mentioned I have tested this procedure as Matthew has said, I didn't find this error. My hardware is an Acer Aspire E 15 with hybrid grafics (Intel/Nvidia), but Nvidia does not work with Fedora because of the not working Nvidia driver, therefore in Linux the Intel grafics chip is the only active (Nouveau driver). It definitely might be model specific. I should also add that I'm in Gnome — it might be something with the way the menus are rendered there. What kind of menu is that? How big is it (height / width in pixels) ? -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
On Sun, Apr 26, 2015 at 08:54:48PM +0200, drago01 wrote: What kind of menu is that? How big is it (height / width in pixels) ? It's the right-click context menu you get when clicking on a filename in geeqie. It's nothing special -- 14 items in three groups, with View in new window being the longest item. 150x300 pixels, maybe? OK so nothing special about it ... odd. Yeah. I did get what seemed like the same behavior with a context menu in Gimp *once*, but can't reproduce there. However, geeqie seems to very reliably trigger it. And it seems to be only _that_ right-click menu, in the filelist, not others in the app. I guess I can go around right-clicking in other programs to see if it happens. One thing that occurs to me is that the placement of this menu means that when it comes up, it almost always comes up on top of a scrollbar and into another panel. *Maybe* that interaction causes some rendering need which triggers the bug? Seems like a longshot, and I really don't know what I'm talking about here. :) -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: nouveau driver freeze -- can anyone else reproduce this?
Hi, sofar I can not reproduce. See screenshot, is this the procedure You wanted? F22 Beta 3. nouveau 1.0.11-2.fc22 x86_64 geeqie 1.2-0.1.20141130 x86_64 Kind Regards -Ursprüngliche Mitteilung- Von: Matthew Miller mat...@fedoraproject.org An: test test@lists.fedoraproject.org Verschickt: Sa, 25 Apr 2015 3:45 pm Betreff: nouveau driver freeze -- can anyone else reproduce this? https://bugzilla.redhat.com/show_bug.cgi?id=1215329 I'm not sure exactly *why* this _particular_ context menu triggers destruction, but: 1. run geeqie in a directory with a number of jpg files 2. right click on one of those files in the list 3. boom Can anyone else reproduce? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
nouveau driver freeze -- can anyone else reproduce this?
https://bugzilla.redhat.com/show_bug.cgi?id=1215329 I'm not sure exactly *why* this _particular_ context menu triggers destruction, but: 1. run geeqie in a directory with a number of jpg files 2. right click on one of those files in the list 3. boom Can anyone else reproduce? -- Matthew Miller mat...@fedoraproject.org Fedora Project Leader -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
