[opensuse] X segfaults when we open Firefox or Chromium
I've just helped a friend set up his system on openSUSE12.3. The hardware is i7-3770, NVIDIA GTX 670, MSI GD65 motherboard, 16GB RAM. Software is a complete default 12.3 install with KDE4 and updates. We added packman, Mozilla, Libreoffice, and nvidia repos, and updated again. Next we installed Chromium and Pepper Flash. Post updates, we verified that the NVIDIA drivers (319.32) were installed and working. Then, with no other desktop setting changes or applications installed, we opened Firefox, and X crashed immediately. Logged back in and tried Chomium... which also crashed X after opening a website (specifically the Skype website). Troubleshooting included deleting the /home/$USER/.mozilla and /home/$USER/.local/chromium directories. Found this in the Xorg log file: ----------------- [ 2103.489] (EE) Backtrace: [ 2103.489] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58f906] [ 2103.489] (EE) 1: /usr/bin/X (0x400000+0x193769) [0x593769] [ 2103.489] (EE) 2: /lib64/libpthread.so.0 (0x7f8ef65e8000+0xf1f0) [0x7f8ef65f71f0] [ 2103.489] (EE) 3: /usr/lib64/xorg/modules/updates/extensions/libglx.so (0x7f8ef3e24000+0xb5f5a9) [0x7f8ef49835a9] ---------------- Which is similar to this discussion here: http://forums.opensuse.org/english/get-technical-help-here/applications/4787... Booting in safe mode, everything works OK. We reinstalled the NVIDIA drivers, and the problem persists. Konqueror is the only browser that works reliably without killing X. So... anyone have any clue what's going on here? C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/03/2013 03:08 PM, C wrote:
I've just helped a friend set up his system on openSUSE12.3. The hardware is i7-3770, NVIDIA GTX 670, MSI GD65 motherboard, 16GB RAM. Software is a complete default 12.3 install with KDE4 and updates. We added packman, Mozilla, Libreoffice, and nvidia repos, and updated again. Next we installed Chromium and Pepper Flash.
Post updates, we verified that the NVIDIA drivers (319.32) were installed and working. Then, with no other desktop setting changes or applications installed, we opened Firefox, and X crashed immediately.
Logged back in and tried Chomium... which also crashed X after opening a website (specifically the Skype website).
Troubleshooting included deleting the /home/$USER/.mozilla and /home/$USER/.local/chromium directories.
Found this in the Xorg log file:
----------------- [ 2103.489] (EE) Backtrace: [ 2103.489] (EE) 0: /usr/bin/X (xorg_backtrace+0x36) [0x58f906] [ 2103.489] (EE) 1: /usr/bin/X (0x400000+0x193769) [0x593769] [ 2103.489] (EE) 2: /lib64/libpthread.so.0 (0x7f8ef65e8000+0xf1f0) [0x7f8ef65f71f0] [ 2103.489] (EE) 3: /usr/lib64/xorg/modules/updates/extensions/libglx.so (0x7f8ef3e24000+0xb5f5a9) [0x7f8ef49835a9] ----------------
Which is similar to this discussion here: http://forums.opensuse.org/english/get-technical-help-here/applications/4787...
Booting in safe mode, everything works OK. We reinstalled the NVIDIA drivers, and the problem persists.
Konqueror is the only browser that works reliably without killing X.
So... anyone have any clue what's going on here?
C.
Well it seems to be crashing in X itself. Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems. If you do add it, I recommend you first apply any pending upgrades, then attach that repository and allow vendor changes (because otherwise even though that package has later versions, they won't get applied unless you allow the vendor change). After updating Xorg from that repository, you will then want to turn off vendor changes. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Oct 4, 2013 at 12:17 AM, John Andersen wrote:
On 10/03/2013 03:08 PM, C wrote:
Post updates, we verified that the NVIDIA drivers (319.32) were installed and working. Then, with no other desktop setting changes or applications installed, we opened Firefox, and X crashed immediately.
Logged back in and tried Chomium... which also crashed X after opening a website (specifically the Skype website).
Snip
Well it seems to be crashing in X itself.
Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems. If you do add it, I recommend you first apply any pending upgrades, then attach that repository and allow vendor changes (because otherwise even though that package has later versions, they won't get applied unless you allow the vendor change).
After updating Xorg from that repository, you will then want to turn off vendor changes.
We gave up at 01:00 last night - by the time we quit, KDE wouldn't even start after running the post-install online updates. This was on a new clean install without adding any repositories, only install with defaults, run updates and splat, X would segfault on login. We couldn't get it to the point of adding the Xorg repo post updates. We are going to give it a go again later today. We will (assuming we can get it to start up on 12.3) try to add the Xorg repo as the first major step post install, set its priority higher, and "switch system packages". Then update.. maybe this way it'll work. The hardware seems to be OK. It was running Windows fine, and another Linux distro installed fine, and was running up until we started this journey into openSUSE. Another thought... could it be the UEFI? It's in full UEFI mode right now (with secure boot turned off). I haven't tried booting/installing in BIOS Legacy mode.... C -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Try openSUSE 13.1 Beta 1 http://software.opensuse.org/developer/en or
if this doesn't work try at the same page with network install media.
The above mentioned 13.1 is not yet 100% stable but it should fix your
issues since it has the new X anyway.
2013/10/4 C
On Fri, Oct 4, 2013 at 12:17 AM, John Andersen wrote:
On 10/03/2013 03:08 PM, C wrote:
Post updates, we verified that the NVIDIA drivers (319.32) were installed and working. Then, with no other desktop setting changes or applications installed, we opened Firefox, and X crashed immediately.
Logged back in and tried Chomium... which also crashed X after opening a website (specifically the Skype website).
Snip
Well it seems to be crashing in X itself.
Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems. If you do add it, I recommend you first apply any pending upgrades, then attach that repository and allow vendor changes (because otherwise even though that package has later versions, they won't get applied unless you allow the vendor change).
After updating Xorg from that repository, you will then want to turn off vendor changes.
We gave up at 01:00 last night - by the time we quit, KDE wouldn't even start after running the post-install online updates. This was on a new clean install without adding any repositories, only install with defaults, run updates and splat, X would segfault on login. We couldn't get it to the point of adding the Xorg repo post updates.
We are going to give it a go again later today. We will (assuming we can get it to start up on 12.3) try to add the Xorg repo as the first major step post install, set its priority higher, and "switch system packages". Then update.. maybe this way it'll work.
The hardware seems to be OK. It was running Windows fine, and another Linux distro installed fine, and was running up until we started this journey into openSUSE.
Another thought... could it be the UEFI? It's in full UEFI mode right now (with secure boot turned off). I haven't tried booting/installing in BIOS Legacy mode....
C -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Oct 4, 2013 at 9:02 AM, Damian Ivanov wrote:
Try openSUSE 13.1 Beta 1 http://software.opensuse.org/developer/en or if this doesn't work try at the same page with network install media.
The above mentioned 13.1 is not yet 100% stable but it should fix your issues since it has the new X anyway.
I considered the 13.1 Beta... for me it'd be no issue (I'm already running 13.1B1 on my laptop), but... this is for a new user (remote to me) who wants to get up an running no later than today (if possible). With things like a mandatory upgrade path through the RCs and Final.., and the lack of the Nvidia proprietary driver in the repos... this option is pretty much a no-go until the final release of 13.1. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
C
On Fri, Oct 4, 2013 at 9:02 AM, Damian Ivanov wrote:
Try openSUSE 13.1 Beta 1 http://software.opensuse.org/developer/en or if this doesn't work try at the same page with network install media.
The above mentioned 13.1 is not yet 100% stable but it should fix your issues since it has the new X anyway.
I considered the 13.1 Beta... for me it'd be no issue (I'm already running 13.1B1 on my laptop), but... this is for a new user (remote to me) who wants to get up an running no later than today (if possible). With things like a mandatory upgrade path through the RCs and Final..,
Fyi:the 13.1 repository already exists and is populated. It is not frozen so the upgrade path is more automatic this time if you set the repo for auto refresh. But I agree, not a good choice for a newbie. 13.1 beta still has big outstanding bugs. Ie. The kde bluetooth stack is only marginally working.
and the lack of the Nvidia proprietary driver in the repos... this option is pretty much a no-go until the final release of 13.1.
That too. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Oct 4, 2013 at 7:27 AM, C wrote:
On Fri, Oct 4, 2013 at 12:17 AM, John Andersen wrote:
Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems.
This seems to have solved it. We wiped the drives and started fresh again this evening. Full openSUSE 12.3/KDE4 install using defaults. Added all the community repos except NVIDIA. Updated. Added the X11 repo with a prio of 50 and switched system packages. Then added the NVIDIA repo and installed the drivers. Works perfectly now. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 05 Oct 2013, C wrote:
On Fri, Oct 4, 2013 at 7:27 AM, C wrote:
On Fri, Oct 4, 2013 at 12:17 AM, John Andersen wrote:
Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems.
This seems to have solved it. We wiped the drives and started fresh again this evening. Full openSUSE 12.3/KDE4 install using defaults. Added all the community repos except NVIDIA. Updated. Added the X11 repo with a prio of 50 and switched system packages. Then added the NVIDIA repo and installed the drivers. Works perfectly now.
*HAH!* I had your OP marked to answer later[0] and wanted you to do a # ls -l /usr/lib64/xorg/modules/updates/extensions/libglx.so and # rpm -qf /usr/lib64/xorg/modules/updates/extensions/libglx.so ... But at least I may be able to shed some light on what I suspect happend. In your OP, the fault originated in /usr/lib64/xorg/modules/updates/extensions/libglx.so which got me suspecting that that file might be from Mesa while you were using the nvidia driver. That combination (nvidia-driver + Mesa libglx.so (and IIRC libGL too[1])) is sure to fail. Your solution fits that suspicion. With your "reinstall" you did it the right way around: first Mesa (via the default or Xorg repo) and then overwrite the Mesa libglx.so (and the symlinks to the Mesa libGL*.so*) with the files/links to the nvidia libglx.so/libGL* via the install from the nvidia repo. Oh, you got to keep that on the radar! Anytime there is a Mesa update (e.g. as a dependency, which may be more often that you'd guess) you need to reinstall the nvidia-driver afterwards! BTW: where's 'switch2nv/switch2nvidia'? I got some backups in backups of /root/bin/, but the scripts show e.g.[2]. Just remember: touching Mesa means reinstalling the (X/Xorg/GL part of the) nvidia driver. Using the (saved) RPM or (untested!) ./nvidia-installer -af --no-kernel-module --no-x-check should work (the .run file calls nvidia-installer with the same options, so '....run -af --no-kernel-module --no-x-check' should work too). And no, you can't just leave out Mesa. Too many packages need it for other purposes (e.g. tons of -devel packages and wine needs the 32-bit versions). So, if you don't need any -devel packages, you may get away without Mesa (64bit) if you're willing to break the 'lsb' package and xorg-x11-server-extra (or don't have those installed). $ rpm -q --whatrequires Mesa libcogl5-1.8.2-2.1.3.x86_64 lsb-4.0-15.1.1.x86_64 Mesa-devel-7.11-11.4.2.x86_64 xorg-x11-server-extra-7.6_1.10.4-36.9.2.x86_64 Here, Mesa gets pulled in, so I need to overwrite with the nvidia stuff as stated above ... JFTR & HTH, -dnh [0] did not feel well all day, then was too tired, by now I feel ok again and am ok for this "wrap-up", no actual do this then that, with an uptime of, uh, ~30 hrs (and a beer or three) ;) [1] not sure if just replacing nvidia's libGL with Mesa's will fail in such way, but with libglx.so it's a sure thing [2] ==== #!/bin/sh # Copyright (c) 2001 SuSE GmbH Nuernberg, Germany. All rights reserved. # # Author: Stefan Dirsch, 2001 ==== and no, they won't work today anymore, too much hardcoded versions in there (e.g. [..] ln -sf libglx.so.100.* libglx.so [..] ln -sf libGL.so.100.* libGL.so.1) ;) -- The nice thing about Windows is - It does not just crash, it displays a dialog box and lets you press 'OK' first. (Arno Schaefer's .sig) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Oct 5, 2013 at 7:42 AM, David Haller wrote:
On Sat, 05 Oct 2013, C wrote:
On Fri, Oct 4, 2013 at 7:27 AM, C wrote:
On Fri, Oct 4, 2013 at 12:17 AM, John Andersen wrote:
Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems.
This seems to have solved it. We wiped the drives and started fresh again this evening. Full openSUSE 12.3/KDE4 install using defaults. Added all the community repos except NVIDIA. Updated. Added the X11 repo with a prio of 50 and switched system packages. Then added the NVIDIA repo and installed the drivers. Works perfectly now.
snip
In your OP, the fault originated in
/usr/lib64/xorg/modules/updates/extensions/libglx.so
which got me suspecting that that file might be from Mesa while you were using the nvidia driver. That combination (nvidia-driver + Mesa libglx.so (and IIRC libGL too[1])) is sure to fail.
Yes, I can see that. I guess what really threw me on this is that I've installed openSUSE 12.3 on a dozen or so machines, most with NVIDIA and have never ran into this segfaulting X thing. We followed the exact same steps (minus the extra X11 repo) and they always "just worked"... you know.. default install, add community repos (Packman, nvidia, Mozilla etc), switch system repos to Packman, run updates (which pulls in Flash, nvidia drivers etc). With my friend's machine it was insta-SPLAT. I did the exact same install on my machine last night (similar but not identical hardware) and it worked.. never had to add the X11 repo to have a stable X. The main thing is... now with the Xorg repo in there, and a higher priority everything seems to be lined up right now and my friend is having a good time discovering how configurable KDE4 can be. :-)
Oh, you got to keep that on the radar! Anytime there is a Mesa update (e.g. as a dependency, which may be more often that you'd guess) you need to reinstall the nvidia-driver afterwards!
I've never had to do this in all the time I've used openSUSE/NVIDIA.. which is pretty much forever.
And no, you can't just leave out Mesa.
It is pretty core a significant portion of the apps out there. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello, On Sat, 05 Oct 2013, C wrote:
On Sat, Oct 5, 2013 at 7:42 AM, David Haller wrote: [..]
Oh, you got to keep that on the radar! Anytime there is a Mesa update (e.g. as a dependency, which may be more often that you'd guess) you need to reinstall the nvidia-driver afterwards!
I've never had to do this in all the time I've used openSUSE/NVIDIA.. which is pretty much forever.
Had to do in a few times. Depending on what you use, just reinstall the rpm (forcefully) or re-run the installer ;0 -dnh -- I'm going to a meeting...? I'd bore myself to death -- if I weren't already dead. -- Georgia 'George' L. Lass, Dead Like Me -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/4/2013 10:42 PM, David Haller wrote:
Your solution fits that suspicion. With your "reinstall" you did it the right way around: first Mesa (via the default or Xorg repo) and then overwrite the Mesa libglx.so (and the symlinks to the Mesa libGL*.so*) with the files/links to the nvidia libglx.so/libGL* via the install from the nvidia repo.
This is a fundamentally broken way of doing things if you ask me. If Nvidia needs a to overwrite a system package with their own, you are in a situation where your system is at risk with any update, or security patch. At a very least Nvidia needs to be a couple release numbers ahead of the system package they are replacing, or change things such that the system package name is not used. Its a ticking time bomb. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Oct 5, 2013 at 7:52 PM, John Andersen wrote:
On 10/4/2013 10:42 PM, David Haller wrote:
Your solution fits that suspicion. With your "reinstall" you did it the right way around: first Mesa (via the default or Xorg repo) and then overwrite the Mesa libglx.so (and the symlinks to the Mesa libGL*.so*) with the files/links to the nvidia libglx.so/libGL* via the install from the nvidia repo.
This is a fundamentally broken way of doing things if you ask me.
If Nvidia needs a to overwrite a system package with their own, you are in a situation where your system is at risk with any update, or security patch.
At a very least Nvidia needs to be a couple release numbers ahead of the system package they are replacing, or change things such that the system package name is not used.
Its a ticking time bomb.
Agreed... and like I said in an earlier reply.. out of a dozen or so separate installs on systems with NVidia... this is the ONLY one that's behaving this way. I've never had to futz about with Mesa and doing any "forced" reinstalls of NVidia drivers because of odd library mismatches or library file overwrites. I even wiped my own machine and did a parallel install with my friend's machine.. mine worked perfect, his failed with X segfaults. It has all the usual bugs we know and love in 12.3... like the initial broken state of the Network Manager... plus this new and exciting segfaulting X. This isn't on a single install either.. we've reinstalled from scratch several times and got the same behaviour. I'm open to doing odd fixes with this particular case... but I don't yet see why this one machine is behaving so differently than any other 12.3 install I've done. I'll poke the log files when we have a chance again this weekend.. maybe the Xorg log file has a new clue? C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/10/13 05:12, C wrote:
On 10/4/2013 10:42 PM, David Haller wrote:
Your solution fits that suspicion. With your "reinstall" you did it the right way around: first Mesa (via the default or Xorg repo) and then overwrite the Mesa libglx.so (and the symlinks to the Mesa libGL*.so*) with the files/links to the nvidia libglx.so/libGL* via the install from the nvidia repo. This is a fundamentally broken way of doing things if you ask me.
If Nvidia needs a to overwrite a system package with their own, you are in a situation where your system is at risk with any update, or security patch.
At a very least Nvidia needs to be a couple release numbers ahead of the system package they are replacing, or change things such that the system package name is not used.
Its a ticking time bomb. Agreed... and like I said in an earlier reply.. out of a dozen or so separate installs on systems with NVidia... this is the ONLY one
On Sat, Oct 5, 2013 at 7:52 PM, John Andersen wrote: that's behaving this way. I've never had to futz about with Mesa and doing any "forced" reinstalls of NVidia drivers because of odd library mismatches or library file overwrites.
I even wiped my own machine and did a parallel install with my friend's machine.. mine worked perfect, his failed with X segfaults. It has all the usual bugs we know and love in 12.3... like the initial broken state of the Network Manager... plus this new and exciting segfaulting X. This isn't on a single install either.. we've reinstalled from scratch several times and got the same behaviour.
I'm open to doing odd fixes with this particular case... but I don't yet see why this one machine is behaving so differently than any other 12.3 install I've done. I'll poke the log files when we have a chance again this weekend.. maybe the Xorg log file has a new clue?
C.
I guess that this computer has an onboard video chip as well as the nVidia pciE 670 card and that the onboard video chip has been disabled so that only the pciE card is active? BC -- Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.3-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Oct 6, 2013 at 8:43 AM, Basil Chupin wrote:
I even wiped my own machine and did a parallel install with my friend's machine.. mine worked perfect, his failed with X segfaults. It has all the usual bugs we know and love in 12.3... like the initial broken state of the Network Manager... plus this new and exciting segfaulting X. This isn't on a single install either.. we've reinstalled from scratch several times and got the same behaviour.
I'm open to doing odd fixes with this particular case... but I don't yet see why this one machine is behaving so differently than any other 12.3 install I've done. I'll poke the log files when we have a chance again this weekend.. maybe the Xorg log file has a new clue?
I guess that this computer has an onboard video chip as well as the nVidia pciE 670 card and that the onboard video chip has been disabled so that only the pciE card is active?
Interesting... I forwarded this to my friend, and he poked around in MSI's UEFI (I'd swear they put extra effort into over-complicating and obscuring things in there) until he found the spot to switch off integrated graphics. Now, KInfoCenter doesn't segfault X... and so far, there have been no more crashes. More testing needed of course, but this is an improvement. Thanks for that suggestion... :-) It never even crossed my mind to try this. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/10/13 21:25, C wrote:
On Sun, Oct 6, 2013 at 8:43 AM, Basil Chupin wrote:
I even wiped my own machine and did a parallel install with my friend's machine.. mine worked perfect, his failed with X segfaults. It has all the usual bugs we know and love in 12.3... like the initial broken state of the Network Manager... plus this new and exciting segfaulting X. This isn't on a single install either.. we've reinstalled from scratch several times and got the same behaviour.
I'm open to doing odd fixes with this particular case... but I don't yet see why this one machine is behaving so differently than any other 12.3 install I've done. I'll poke the log files when we have a chance again this weekend.. maybe the Xorg log file has a new clue?
I guess that this computer has an onboard video chip as well as the nVidia pciE 670 card and that the onboard video chip has been disabled so that only the pciE card is active?
Interesting... I forwarded this to my friend, and he poked around in MSI's UEFI (I'd swear they put extra effort into over-complicating and obscuring things in there) until he found the spot to switch off integrated graphics.
Now, KInfoCenter doesn't segfault X... and so far, there have been no more crashes. More testing needed of course, but this is an improvement.
Thanks for that suggestion... :-) It never even crossed my mind to try this.
C.
Glad to have been of help :-) . But re MSI mobo: I recall reading a while back reviews and comments by tech people in our local IT mags re MSI mobos following which I promised myself never to buy this brand of mobo and always buy Gigabyte. But the techs were probably obviously biased..... BC -- Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.3-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/10/13 23:22, Basil Chupin wrote:
On 06/10/13 21:25, C wrote:
On Sun, Oct 6, 2013 at 8:43 AM, Basil Chupin wrote:
I even wiped my own machine and did a parallel install with my friend's machine.. mine worked perfect, his failed with X segfaults. It has all the usual bugs we know and love in 12.3... like the initial broken state of the Network Manager... plus this new and exciting segfaulting X. This isn't on a single install either.. we've reinstalled from scratch several times and got the same behaviour.
I'm open to doing odd fixes with this particular case... but I don't yet see why this one machine is behaving so differently than any other 12.3 install I've done. I'll poke the log files when we have a chance again this weekend.. maybe the Xorg log file has a new clue?
I guess that this computer has an onboard video chip as well as the nVidia pciE 670 card and that the onboard video chip has been disabled so that only the pciE card is active?
Interesting... I forwarded this to my friend, and he poked around in MSI's UEFI (I'd swear they put extra effort into over-complicating and obscuring things in there) until he found the spot to switch off integrated graphics.
Now, KInfoCenter doesn't segfault X... and so far, there have been no more crashes. More testing needed of course, but this is an improvement.
Thanks for that suggestion... :-) It never even crossed my mind to try this.
C.
Glad to have been of help :-) .
But re MSI mobo: I recall reading a while back reviews and comments by tech people in our local IT mags re MSI mobos following which I promised myself never to buy this brand of mobo and always buy Gigabyte. But the techs were probably obviously biased.....
BC
Oh, I forgot to mention that what applies to the video card/chip also should also apply to the sound card/chip. BC -- Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.3-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, Oct 6, 2013 at 4:58 PM, Basil Chupin wrote:
On 06/10/13 23:22, Basil Chupin wrote:
On 06/10/13 21:25, C wrote:
On Sun, Oct 6, 2013 at 8:43 AM, Basil Chupin wrote: But re MSI mobo: I recall reading a while back reviews and comments by tech people in our local IT mags re MSI mobos following which I promised myself never to buy this brand of mobo and always buy Gigabyte. But the techs were probably obviously biased.....
Oh, I forgot to mention that what applies to the video card/chip also should also apply to the sound card/chip.
Oddly enough, now, in addition to the graphical issues, we are also now running into sound problems... I have to admire the persistence of my friend. He really wants to run Linux :-) I'm still trying to work through the issues. It is quite slow since I'm trying to do it all remotely. Everyone's advice is appreciated. We are making progress. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/10/13 11:05, C wrote:
Oddly enough, now, in addition to the graphical issues, we are also now running into sound problems... I have to admire the persistence of my friend. He really wants to run Linux :-) I'm still trying to work through the issues. It is quite slow since I'm trying to do it all remotely.
What audio hardware is he trying to set up? FWIW I have a new Intel mobo here (i7 4770 CPU @ 3.40GHz) with embedded video which I had to disable before I could get my PCIe nVidia GeForce GTX 670 to work using the proprietary drivers. I also have a Creative X-Fi Titanium sound card, the S/PDIF digital output of which would not work satisfactorily until the HDMI audio control integral to the GTX 670 was disabled in software (YAST sound module). RK -- Robin K Wellington "Harbour City" New Zealand -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 08/10/13 09:05, C wrote:
On Sun, Oct 6, 2013 at 4:58 PM, Basil Chupin wrote:
On 06/10/13 23:22, Basil Chupin wrote:
On 06/10/13 21:25, C wrote:
On Sun, Oct 6, 2013 at 8:43 AM, Basil Chupin wrote: But re MSI mobo: I recall reading a while back reviews and comments by tech people in our local IT mags re MSI mobos following which I promised myself never to buy this brand of mobo and always buy Gigabyte. But the techs were probably obviously biased.....
Oh, I forgot to mention that what applies to the video card/chip also should also apply to the sound card/chip. Oddly enough, now, in addition to the graphical issues, we are also now running into sound problems... I have to admire the persistence of my friend. He really wants to run Linux :-) I'm still trying to work through the issues. It is quite slow since I'm trying to do it all remotely.
Everyone's advice is appreciated. We are making progress.
I've had to do it many times - the "remote solve" gambit :-( . I know your pain :-( . But at least you have someone at the other end who is not totally brain-dead and who at least knows how to get to the BIOS :-) . BC -- "If you read the books that everyone else is reading, you can only think what everyone else is thinking." - Haruki Murakami -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Oddly enough, now, in addition to the graphical issues, we are also now running into sound problems... I have to admire the persistence of my friend. He really wants to run Linux :-) I'm still trying to work through the issues. It is quite slow since I'm trying to do it all remotely.
Everyone's advice is appreciated. We are making progress.
And.... it's done. My friend gave it a go for almost a week to try and get a stable Linux on his system. He tried ElementaryOS (a disaster from the start), Ubuntu 13.10 (couldn't even get the installer to find his drives because of GPT), and then openSUSE 12.3. openSUSE was the closest to actually working, but... with the constant segfaulting X, unreliable sound, and a host of other bizarre issues, he finally gave up and installed Windows. He has tried many times over the past 8 years. I have to give him credit for trying... and trying again :-P He says he might try again after openSUSE 13.1 is out. But... yah... that didn't go so well.... again. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/9/2013 11:33 AM, C wrote:
He says he might try again after openSUSE 13.1 is out.
Noooooo, don't go there. Every other one works. ;-) So wait for 13.2. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, Oct 9, 2013 at 9:07 PM, John Andersen wrote:
On 10/9/2013 11:33 AM, C wrote:
He says he might try again after openSUSE 13.1 is out.
Noooooo, don't go there.
Every other one works. ;-)
So wait for 13.2.
HAHA Actually, I'm running the Beta of 13.1 on my laptop/tablet, and other than Bluetooth being totally busted (known issue discussed on the Factory ML), it's working pretty well. No significant (unknown by the dev team) issues at all. Basically, at this point, 13.1 seems to be really solid, especially for a Beta. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/10/13 05:33, C wrote:
Oddly enough, now, in addition to the graphical issues, we are also now running into sound problems... I have to admire the persistence of my friend. He really wants to run Linux :-) I'm still trying to work through the issues. It is quite slow since I'm trying to do it all remotely.
Everyone's advice is appreciated. We are making progress. And.... it's done. My friend gave it a go for almost a week to try and get a stable Linux on his system. He tried ElementaryOS (a disaster from the start), Ubuntu 13.10 (couldn't even get the installer to find his drives because of GPT), and then openSUSE 12.3. openSUSE was the closest to actually working, but... with the constant segfaulting X, unreliable sound, and a host of other bizarre issues, he finally gave up and installed Windows.
He has tried many times over the past 8 years. I have to give him credit for trying... and trying again :-P He says he might try again after openSUSE 13.1 is out.
But... yah... that didn't go so well.... again.
C.
I wonder....... When I first started in Linux I had a few hassles caused by the use of "/" and "\". Windows uses "\" and Linux "/" and using the former for a Windows user is automatic. It wasn't until one person cottoned on to what I was typing when reporting a problem that the whole thing was resolved :-) . I learnt the hard way to use "/" :-) . BC -- Using openSUSE 13.1, KDE 4.11.2 & kernel 3.11.6-3 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 OC 2GB DDR5 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, Oct 5, 2013 at 1:20 AM, C wrote:
On Fri, Oct 4, 2013 at 7:27 AM, C wrote:
On Fri, Oct 4, 2013 at 12:17 AM, John Andersen wrote:
Have you tried adding this repository: http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ This is an updated Xorg which fixes tons of problems.
This seems to have solved it. We wiped the drives and started fresh again this evening. Full openSUSE 12.3/KDE4 install using defaults. Added all the community repos except NVIDIA. Updated. Added the X11 repo with a prio of 50 and switched system packages. Then added the NVIDIA repo and installed the drivers. Works perfectly now.
OK, something is STILL not right on my friend's computer. I was on a VoIP call with him answering his questions about openSUSE. He wanted to see info about his hardware, so I directed him to KInfoCenter. He clicked Graphical Information > OpenGL, and splat.. X segfaulted. This is on an i7-3770, Nvidia GTX670, using the Nvidia 319.32 drivers (in case that info was forgotten). This is 100% repeatable... every time he clicks the OpenGL entry in KInfoCenter, he's kicked out to the login screen. Next step I guess is David's steps of poking around at libglx.so - I'll compare with my system. Maybe we can nail this down... I hope. C. -- openSUSE 12.3 x86_64, KDE 4.11 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 06 Oct 2013, C wrote:
....
OK, something is STILL not right on my friend's computer. I was on a VoIP call with him answering his questions about openSUSE. He wanted to see info about his hardware, so I directed him to KInfoCenter. He clicked Graphical Information > OpenGL, and splat.. X segfaulted.
This is on an i7-3770, Nvidia GTX670, using the Nvidia 319.32 drivers (in case that info was forgotten).
This is 100% repeatable... every time he clicks the OpenGL entry in KInfoCenter, he's kicked out to the login screen.
Next step I guess is David's steps of poking around at libglx.so - I'll compare with my system. Maybe we can nail this down... I hope.
C. -- openSUSE 12.3 x86_64, KDE 4.11
Hardware issue? I had some instabilities a while back when I failed to check the motherboard settings - turned out I had some kind of MB performance/power optimiser switch set and when I ran a particular app it crossed the limits of stability. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Basil Chupin -
C -
Damian Ivanov -
David Haller -
Greg Freemyer -
John Andersen -
Michael Hamilton -
Robin Klitscher