Hi all, I am trying to compile syncekonnector-0.2.1 on a suse 9.3 amd64 platform. It depends on synce and synce-devel packages with are both (to my knowledge 32bit packages. configure complains about de synce libraries not being compatible in config.log. So, I instructed configure to use 32bit compile (-m32). Now, it complains it can't find libXext, but I know it's there (devel packages are both in 64bit and 32bit present). I'm not a devel guy, who to get out of this mess?
Fred van Zwieten wrote:
Hi all,
I am trying to compile syncekonnector-0.2.1 on a suse 9.3 amd64 platform. It depends on synce and synce-devel packages with are both (to my knowledge 32bit packages. configure complains about de synce libraries not being compatible in config.log. So, I instructed configure to use 32bit compile (-m32). Now, it complains it can't find libXext, but I know it's there (devel packages are both in 64bit and 32bit present).
I'm not a devel guy, who to get out of this mess?
Try giving --x-libraries=/usr/X11R6/lib to configure, see if that helps. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Doesn't help, Sid. I found this in config.log: configure:26988: gcc -m32 -o conftest -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-a rith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2 -Wformat- security -Wmissing-format-attribute -L/usr/X11R6/lib conftest.c -lXext -lX11 >&5 /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-linux/bin/ld: cannot fin d -lXext Can you make any sense of it? On Monday 06 June 2005 15:23, Sid Boyce wrote:
Fred van Zwieten wrote:
Hi all,
I am trying to compile syncekonnector-0.2.1 on a suse 9.3 amd64 platform. It depends on synce and synce-devel packages with are both (to my knowledge 32bit packages. configure complains about de synce libraries not being compatible in config.log. So, I instructed configure to use 32bit compile (-m32). Now, it complains it can't find libXext, but I know it's there (devel packages are both in 64bit and 32bit present).
I'm not a devel guy, who to get out of this mess?
Try giving --x-libraries=/usr/X11R6/lib to configure, see if that helps. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Fred van Zwieten wrote:
Doesn't help, Sid. I found this in config.log:
configure:26988: gcc -m32 -o conftest -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-a rith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2 -Wformat- security -Wmissing-format-attribute -L/usr/X11R6/lib conftest.c -lXext -lX11 >&5 /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-linux/bin/ld: cannot fin d -lXext
Can you make any sense of it?
-rw-r--r-- 1 root root 76022 2005-03-22 17:28 /usr/X11R6/lib/libXext.a lrwxrwxrwx 1 root root 14 2005-04-19 16:26 /usr/X11R6/lib/libXext.so -> libXext.so.6.4* lrwxrwxrwx 1 root root 14 2005-04-19 14:05 /usr/X11R6/lib/libXext.so.6 -> libXext.so.6.4* -rwxr-xr-x 1 root root 57064 2005-03-22 17:33 /usr/X11R6/lib/libXext.so.6.4* I've seen this problem where the link for libXext.so was missing, but that should be installed as standard and I've checked.... # file /usr/X11R6/lib/libXext.so.6.4 /usr/X11R6/lib/libXext.so.6.4: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped Run "ldconfig -v|less" and check for that library. I can't see why it's not finding it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
lothlorien:/home/fred # ls -l /usr/X11R6/lib/libXext* lrwxrwxrwx 1 root root 14 2005-05-19 16:20 /usr/X11R6/lib/libXext.so.6 -> libXext.so.6.4 -rwxr-xr-x 1 root root 57064 2005-03-22 18:33 /usr/X11R6/lib/libXext.so.6.4 lothlorien:/home/fred # ls -l /usr/X11R6/lib64/libXext* -rw-r--r-- 1 root root 115314 2005-03-22 18:25 /usr/X11R6/lib64/libXext.a lrwxrwxrwx 1 root root 14 2005-05-19 16:28 /usr/X11R6/lib64/libXext.so -> libXext.so.6.4 lrwxrwxrwx 1 root root 14 2005-05-19 16:18 /usr/X11R6/lib64/libXext.so.6 -> libXext.so.6.4 -rwxr-xr-x 1 root root 71112 2005-03-22 18:30 /usr/X11R6/lib64/libXext.so.6.4 Libraries are in both 32 and 64 X11 lib paths. Links seems ok ldconfig -v | less shows LD sees both 32 and 64 bit libs. I use: CC="gcc -m32" ./configure --x-libraries=/usr/X11R6/lib I Get: checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for IceConnectionNumber in -lICE... no checking for libXext... no configure: error: We need a working libXext to proceed. Since configure can't find it itself, we stop here assuming that make wouldn't find them either. Regards, Fred On Monday 06 June 2005 21:37, Sid Boyce wrote:
Fred van Zwieten wrote:
Doesn't help, Sid. I found this in config.log:
configure:26988: gcc -m32 -o conftest -ansi -W -Wall -Wchar-subscripts -Wshadow -Wpointer-a rith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -O2 -Wformat- security -Wmissing-format-attribute -L/usr/X11R6/lib conftest.c -lXext -lX11 >&5 /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.5/../../../../x86_64-suse-linux/ bin/ld: cannot fin d -lXext
Can you make any sense of it?
-rw-r--r-- 1 root root 76022 2005-03-22 17:28 /usr/X11R6/lib/libXext.a lrwxrwxrwx 1 root root 14 2005-04-19 16:26 /usr/X11R6/lib/libXext.so -> libXext.so.6.4* lrwxrwxrwx 1 root root 14 2005-04-19 14:05 /usr/X11R6/lib/libXext.so.6 -> libXext.so.6.4* -rwxr-xr-x 1 root root 57064 2005-03-22 17:33 /usr/X11R6/lib/libXext.so.6.4* I've seen this problem where the link for libXext.so was missing, but that should be installed as standard and I've checked.... # file /usr/X11R6/lib/libXext.so.6.4 /usr/X11R6/lib/libXext.so.6.4: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped Run "ldconfig -v|less" and check for that library. I can't see why it's not finding it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
Hi all, SuSE 9.3_64 shows on a AMD64 3200 machine with MSI K8T Neo FIS2R board with 512 MB RAM and GeForce5900XT (nvidia 7664 driver) after upgrading RAM with another 512 MB a weird behavior. After a differently while (between 5 and 20 minutes), keyboard completely and mouse bottons are freeze. Mouse pointer is working, also the rest of the system. Tested with ssh or a X connection from a remote computer. Also memtest is running without a error message. Because other OS (Win2k Pro, Solaris 10), installed besides on the same AMD64 machine, are working solid like a rock with the additional RAM, I think, this is not a hardware problem. It seems, that SuSE 9.3_64 makes the trouble. What can I do? Kindly Regards Uwe -- (Open)PGP Key auf Anfrage, (Open)PGP-Key on request
On Friday 15 July 2005 12:44 pm, Uwe Pannecke wrote:
Hi all,
SuSE 9.3_64 shows on a AMD64 3200 machine with MSI K8T Neo FIS2R board with 512 MB RAM and GeForce5900XT (nvidia 7664 driver) after upgrading RAM with another 512 MB a weird behavior. After a differently while (between 5 and 20 minutes), keyboard completely and mouse bottons are freeze. Mouse pointer is working, also the rest of the system. Tested with ssh or a X connection from a remote computer. Also memtest is running without a error message. Because other OS (Win2k Pro, Solaris 10), installed besides on the same AMD64 machine, are working solid like a rock with the additional RAM, I think, this is not a hardware problem. It seems, that SuSE 9.3_64 makes the trouble. What can I do?
Run memtest86 on it. You may need to rachet back the speed of the memory to get stability. Memtest86 should show you if any issues are apparent. http://www.memtest86.com/ Scott -- POPFile, the OpenSource EMail Classifier http://popfile.sourceforge.net/ Linux 2.6.11.4-21.7-default x86_64 SuSE Linux 9.3 (x86-64)
Hi Scott and all,
SuSE 9.3_64 shows on a AMD64 3200 machine with MSI K8T Neo FIS2R board with 512 MB RAM and GeForce5900XT (nvidia 7664 driver) after upgrading RAM with another 512 MB a weird behavior. After a differently while (between 5 and 20 minutes), keyboard completely and mouse bottons are freeze. Mouse pointer is working, also the rest of the system. Tested with ssh or a X connection from a remote computer. Also memtest is running without a error message. Because other OS (Win2k Pro, Solaris 10), installed besides on the same AMD64 machine, are working solid like a rock with the additional RAM, I think, this is not a hardware problem. It seems, that SuSE 9.3_64 makes the trouble. What can I do? Run memtest86 on it.
as I wrote, memtest (memtest86 v3.2) gives 0 Err as result. Tested today again with a run over 5 hours. No Error at all.
You may need to rachet back the speed of the memory to get stability.
Setting in Bios the CAS latency to 3.0 makes no difference. Win2k Pro and Solaris 10 are running very well, SuSE 9.3_64 on the same machine make trouble. But if a remote computer is connected to that SuSE box, I can work on this SuSE 9.3_64 over ssh or a X session from the remote machine for hours and hours. What is wrong? Kindly regards Uwe -- (Open)PGP Key auf Anfrage, (Open)PGP-Key on request
Hi all Suselinux fans We have a web site about suse whose name's www.suse-tr.com All we want is just to enter rhe site and give a feedback about site.Also we are very hppy if you support us.It opened only one week ago and we need a good number of document. Please you can send us any document about suse.İt will be very useful for all Turkish suse users.We have a forum about suse in english.If you share your ideas about suse,we will be very happy.I want to say again:WE NEED SUPPORT.Pleasesupport us.If support us,it will be good beginnig for Suse in Turkey. Please write us about your ideas Regards Tora Toraman Site Admin www.suse-tr.com __________________________________________________ Yahoo! kullanıyor musunuz? İstenmeyen postadan bıktınız mı? Yahoo! Posta'da piyasanın en iyi istenmeyen posta korunması var http://tr.mail.yahoo.com ___________________________________________________________________ Yahoo! kullaniyor musunuz? http://tr.mail.yahoo.com Istenmeyen postadan biktiniz mi? Istenmeyen postadan en iyi korunma Yahoo! Posta’da
Your problem sure sounds like it is the NVidia driver - there is a well-known and long-standing problem with the exact symptoms you describe - frozen X but working mouse, can still login remotely. Unfortunately, I've never seen a definitive fix - different things work for different hardware. The only sure fix is to stop using the NVidia binary driver entirely, and use "nv" instead, but no 3D then :(. You could experiment with "slowing down" all video-related (and perhaps memory-related) BIOS settings, but I doubt you will be able to get rid of the problem completely as long as you use the NVidia driver. One other note - this has NOTHING to do with AMD64 - I know because I was having the problem with an Athlon board two years (and many driver versions) ago. You could Google around for thinks like "linux nvidia lockup", and check the NVidia discussion boards (http://www.nvnews.net/) to see if anyone has more recent fixes... Good luck, John Jegla On Sunday 17 July 2005 3:51 am, Uwe Pannecke wrote:
Hi Scott and all,
SuSE 9.3_64 shows on a AMD64 3200 machine with MSI K8T Neo FIS2R board with 512 MB RAM and GeForce5900XT (nvidia 7664 driver) after upgrading RAM with another 512 MB a weird behavior. After a differently while (between 5 and 20 minutes), keyboard completely and mouse bottons are freeze. Mouse pointer is working, also the rest of the system. Tested with ssh or a X connection from a remote computer. Also memtest is running without a error message. Because other OS (Win2k Pro, Solaris 10), installed besides on the same AMD64 machine, are working solid like a rock with the additional RAM, I think, this is not a hardware problem. It seems, that SuSE 9.3_64 makes the trouble. What can I do?
Run memtest86 on it.
as I wrote, memtest (memtest86 v3.2) gives 0 Err as result. Tested today again with a run over 5 hours. No Error at all.
You may need to rachet back the speed of the memory to get stability.
Setting in Bios the CAS latency to 3.0 makes no difference. Win2k Pro and Solaris 10 are running very well, SuSE 9.3_64 on the same machine make trouble. But if a remote computer is connected to that SuSE box, I can work on this SuSE 9.3_64 over ssh or a X session from the remote machine for hours and hours. What is wrong?
Kindly regards
Uwe -- (Open)PGP Key auf Anfrage, (Open)PGP-Key on request
Hi John and all,
SuSE 9.3_64 shows on a AMD64 3200 machine with MSI K8T Neo FIS2R board with 512 MB RAM and GeForce5900XT (nvidia 7664 driver) after upgrading RAM with another 512 MB a weird behavior. After a differently while (between 5 and 20 minutes), keyboard completely and mouse bottons are freeze. Mouse pointer is working, also the rest of the system. Tested with ssh or a X connection from a remote computer. Also memtest is running without a error message. Because other OS (Win2k Pro, Solaris 10), installed besides on the same AMD64 machine, are working solid like a rock with the additional RAM, I think, this is not a hardware problem. It seems, that SuSE 9.3_64 makes the trouble. What can I do? Run memtest86 on it. as I wrote, memtest (memtest86 v3.2) gives 0 Err as result. Tested today again with a run over 5 hours. No Error at all. You may need to rachet back the speed of the memory to get stability. Setting in Bios the CAS latency to 3.0 makes no difference. Win2k Pro and Solaris 10 are running very well, SuSE 9.3_64 on the same machine make trouble. But if a remote computer is connected to that SuSE box, I can work on this SuSE 9.3_64 over ssh or a X session from the remote machine for hours and hours. What is wrong? Your problem sure sounds like it is the NVidia driver - there is a well-known and long-standing problem with the exact symptoms you describe - frozen X but working mouse, can still login remotely. Unfortunately, I've never seen a definitive fix - different things work for different hardware. The only sure fix is to stop using the NVidia binary driver entirely, and use "nv" instead, but no 3D then :(.
yes, with "nv" instead of "nvidia", the freezes has gone. But as you wrote, also 3D acceleration. And in the meantime another weird thing has shown: With the additional 512 MB RAM VMware has read errors on CD/DVDs and CD/DVD images. Its a mess. And I give up. :( After removing the additional 512 MB, the "nvidia" driver works again, and so the read errors under vmware are gone. The question stays, why Win2k Pro and Solaris 10 can handle the two 512 MB module, but Linux cant... BTW, thanks for all antwort replying and hints, Kindly regards Uwe -- (Open)PGP Key auf Anfrage, (Open)PGP-Key on request
Uwe Pannecke
But if a remote computer is connected to that SuSE box, I can work on this SuSE 9.3_64 over ssh or a X session from the remote machine for hours and hours. What is wrong?
Run the box with the VESA X server for a while and check if the problem then occurs as well. This sounds like an Nvidia driver problem. -- A lack of leadership is no substitute for inaction.
participants (7)
-
Fred van Zwieten -
Harald Milz -
John D. Jegla -
Scott Leighton -
Sid Boyce -
Tora TORAMAN -
Uwe Pannecke