paraview run time error on Linux x86_64 (hard coded path)

296 views
Skip to first unread message

Prakashan Korambath

unread,
Jul 8, 2010, 9:06:44 PM7/8/10
to VSCSE Petascale Programming 2010
For some reason the path /home/kitware is hard coded in the binary
executable. We could create the same path if necessary, but I would
think there may be some environment variables to override that.

Prakashan


-rw-rw-r-- 1 ppk ppk 190307058 Jul 7 18:34 ParaView-3.8.0-Linux-
x86_64.tar.gz

[ppk@localhost petascale]$ cd ParaView-3.8.0-Linux-x86_64
[ppk@localhost ParaView-3.8.0-Linux-x86_64]$ ls
bin lib
[ppk@localhost ParaView-3.8.0-Linux-x86_64]$ cd bin
[ppk@localhost bin]$ ls
lproj paraview pvbatch pvdataserver pvpython pvrenderserver
pvserver smTestDriver
[ppk@localhost bin]$ ./paraview
ERROR: In /home/kitware/Dashboard/MyTests/ParaView-3-8/ParaView-3.8/
ParaView/VTK/Rendering/vtkXOpenGLRenderWindow.cxx, line 631
vtkXOpenGLRenderWindow (0x2f63340): Cannot create GLX context.
Aborting.


Aborted

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:09:44 PM7/8/10
to vscse-petascale-...@googlegroups.com

Can you do a glxinfo and paste the output please?


Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 9:14:04 PM7/8/10
to vscse-petascale-...@googlegroups.com
It is a long output, but I would think you only want to see the header perhaps display.

Prakashan


[ppk@localhost ~]$ glxinfo
name of display: :0.0
Error: glXCreateContext failed

64 GLX Visuals
   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:17:30 PM7/8/10
to vscse-petascale-...@googlegroups.com

No the header is not terribly useful. I want to see if you have the glx extension. The error suggests that vtk failed to create one: 
"Cannot create GLX context.
Aborting."

glxinfo will let us know if you have glx working or not. Can you place it in a text file and attach it to the email please? Also, can you run glxgears and let me know what if you see 3 spinning gears.



Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 9:22:59 PM7/8/10
to vscse-petascale-...@googlegroups.com
My laptop is FC 13 with latest updates.  I never had problem with glxgears before.  May be something FC 13 folks messed up.  It could be a FC 13 specific problem.  

Prakashan


[ppk@localhost ~]$ glxgears
Error: glXCreateContext failed

Prakashan Korambath

unread,
Jul 8, 2010, 9:25:33 PM7/8/10
to vscse-petascale-...@googlegroups.com
I have attached a glxinfo.fc13 file.

Prakashan
glxinfo.fc13

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:30:01 PM7/8/10
to vscse-petascale-...@googlegroups.com


nvidia or ati graphics card? Fedora or vendor drivers?

Your X session does not have a working glx extension. This can be for many reasons: wrong/inactive/misconfigured driver or wrong xorg.conf file .Sadly to be able to sort this out you will need to provide the /var/log/Xorg.0.log file, the /etc/X11/xorg.conf file and the output of lsmod .

3D support on linux is... interesting.

Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 9:33:53 PM7/8/10
to vscse-petascale-...@googlegroups.com
It is  nvidia card.  Google says to add   ModulePath line in xorg.conf, but they don't say which section to add.  Do you know?

Prakashan


These lines were missing:

~ ModulePath "/usr/lib64/xorg/modules/extensions/nvidia"
~ ModulePath "/usr/lib64/xorg/modules/extensions"
~ ModulePath "/usr/lib64/xorg/modules"

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:34:49 PM7/8/10
to vscse-petascale-...@googlegroups.com

Which drivers are you using? Do you have the nvidia drivers installed? Did you disable nouveau?

Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 9:39:24 PM7/8/10
to vscse-petascale-...@googlegroups.com
I also have nouveau.modeset=0.  I don't remember why, but it fixed some problem at that time.  Let me remove that and reboot the machine. 

Prakashan


[root@localhost nvidia]# cat version
NVRM version: NVIDIA UNIX x86_64 Kernel Module  195.36.24  Thu Apr 22 19:10:14 PDT 2010
GCC version:  gcc version 4.4.4 20100503 (Red Hat 4.4.4-2) (GCC) 


kernel /vmlinuz-2.6.33.5-124.fc13.x86_64.debug ro root=UUID=8b5cc333-edbe-4cce-ae1a-ad2f49274222  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet nouveau.modeset=0 vga=31B

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:41:11 PM7/8/10
to vscse-petascale-...@googlegroups.com


Please do the lsmod and provide the output. That's how we can figure out which driver is actually being used. 

Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 9:46:03 PM7/8/10
to vscse-petascale-...@googlegroups.com
Here it is

[root@localhost ~]# lsmod
Module                  Size  Used by
aes_x86_64              7654  2 
aes_generic            27012  1 aes_x86_64
fuse                   54749  2 
sunrpc                192013  1 
cpufreq_ondemand        8420  2 
powernow_k8            14521  0 
freq_table              3851  2 cpufreq_ondemand,powernow_k8
ip6t_REJECT             4055  2 
nf_conntrack_ipv6      17513  2 
ip6table_filter         2743  1 
ip6_tables             16558  1 ip6table_filter
ipv6                  267033  36 ip6t_REJECT,nf_conntrack_ipv6
uinput                  7230  0 
nvidia              10822390  24 
snd_hda_codec_nvhdmi     3962  1 
snd_hda_codec_conexant    34904  1 
snd_hda_intel          24200  2 
snd_hda_codec          73671  3 snd_hda_codec_nvhdmi,snd_hda_codec_conexant,snd_hda_intel
snd_hwdep               6222  1 snd_hda_codec
snd_seq                50941  0 
snd_seq_device          5895  1 snd_seq
arc4                    1377  2 
snd_pcm                76131  2 snd_hda_intel,snd_hda_codec
ecb                     1967  2 
snd_timer              19234  2 snd_seq,snd_pcm
snd                    60573  12 snd_hda_codec_conexant,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_seq,snd_seq_device,snd_pcm,snd_timer
shpchp                 28784  0 
hp_wmi                  5025  0 
soundcore               6198  1 snd
snd_page_alloc          7221  2 snd_hda_intel,snd_pcm
serio_raw               4539  0 
ath5k                 143413  0 
mac80211              196929  1 ath5k
forcedeth              46972  0 
microcode              17930  0 
wmi                     6600  1 hp_wmi
ath                     9190  1 ath5k
edac_core              37487  0 
joydev                  9439  0 
cfg80211              117099  3 ath5k,mac80211,ath
rfkill                 16402  3 hp_wmi,cfg80211
i2c_nforce2             6566  0 
edac_mce_amd            7767  0 
k10temp                 3223  0 
pata_acpi               3251  0 
ata_generic             3323  0 
usb_storage            44408  0 
pata_amd               10842  0 
nouveau               381715  0 
ttm                    53215  1 nouveau
drm_kms_helper         23936  1 nouveau
drm                   169073  3 nouveau,ttm,drm_kms_helper
i2c_algo_bit            4781  1 nouveau
video                  20741  1 nouveau
output                  2117  1 video
i2c_core               24507  6 nvidia,i2c_nforce2,nouveau,drm_kms_helper,drm,i2c_algo_bit
[root@localhost ~]# 

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:50:43 PM7/8/10
to vscse-petascale-...@googlegroups.com
You seem to have both nouveau and nvidia drivers loaded. That might be causing this. This is what I recommend.

Go to:

and follow the instructions there. You already have the nvidia drivers installed, so you can skip that step. Also you might want to remove the nouveau.modeset from your kernel line (edit the /etc/grub.conf to do that). 

Also keep this in mind: the surefire way to get rid of the nouveau driver is to remove it with rpm (not yum) as that will erase it without removing X and then to re-run dracut for safe measure. I also add an entry for nouveau in the /etc/modules.d/blacklist file just to make sure it cannot be loaded in the future. It is overkill but the nouveau driver deserves it: it lies at the heart of many bugs in F12 and F13.

Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 9:54:15 PM7/8/10
to vscse-petascale-...@googlegroups.com
Sure.  Thanks. 

Prakashan

Yaakoub El Khamra

unread,
Jul 8, 2010, 9:57:44 PM7/8/10
to vscse-petascale-...@googlegroups.com

Best of luck Prakashan. Also, if you have time, go to the nvnews forums and check out the instructions they have there. They are not for beginners but they will get you going.

Regards
Yaakoub El Khamra

Prakashan Korambath

unread,
Jul 8, 2010, 10:37:02 PM7/8/10
to vscse-petascale-...@googlegroups.com
Hi Yaakoub,

Thanks to your help I fixed the problem.  I also upgraded my nvidia drivers at the same time.  I added "rdblacklist=nouveau nomodeset" at the end of my kernel line in /etc/grub.conf and recompiled the new nvidia driver.  Now I see glxgears rotating and also paraview coming up ok.   I didn't quit rpm-e nouveau because it is asking me to remove some dependent file as well.  I didn't want to force it since I don't know what I am doing right now :-)  I just want to keep it the way it is now till tomorrow at least.  Thanks again.

kernel /vmlinuz-2.6.33.6-147.fc13.x86_64 ro root=UUID=8b5cc333-edbe-4cce-ae1a-ad2f49274222  LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet rdblacklist=nouveau nomodeset

Prakashan

Yaakoub El Khamra

unread,
Jul 8, 2010, 10:38:30 PM7/8/10
to vscse-petascale-...@googlegroups.com

Glad it worked out :)

Reply all
Reply to author
Forward
0 new messages