Am 24.12.2012 23:44, schrieb Sid Boyce:
> "cat /proc/driver/nvidia/version" will identify the driver in use.

~$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.43  Sun Aug 19 
20:14:03 PDT 2012
GCC version:  gcc-Version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1)

and here: 
http://www.nvidia.de/object/linux-display-amd64-304.43-driver-de.html
my card is listened as supported.

So maybe that is not the reason?

Martin



>
> On 24/12/12 20:01, Arnt Karlsen wrote:
>> On Mon, 24 Dec 2012 18:18:41 +0200, Bayram wrote in message
>> <canwntgfsocswgqvxy4obbybubexeh00ark96xyoyujqtqcn...@mail.gmail.com>:
>>
>>> Just to make sure if all your programs are dynamically linked to your
>>> graphics card's driver.
>>> But it seems ok.
>> ..5 year old graphics card running "nvidia-current" (whatever that
>> means)???  The "new" drivers may have "your old card" do software
>> rendering on the cpu because the new driver does not know your old
>> end-lifed graphics card cannot do some new kinda hardware rendering.
>>
>> ..2 possible solutions: the nouveau driver, if that fails to beat
>> your "nvidia-current" driver, try "nvidia-legacy", some distros
>> have several legacy versions to cover 3, 5, 7 etc year old cards.
>>
>>> May be you need to try to run fgfs in verbose mode to see what happens
>>> internally
>>> nvidia-current
>>>
>>> On Mon, Dec 24, 2012 at 6:02 PM, Kleiner Drache
>>> <kleinerdra...@gmx.at>wrote:
>>>
>>>> Am 24.12.2012 16:24, schrieb Bayram Tamer Gunes:
>>>>> Can you run these on a terminal on bash
>>>>>
>>>>> ldd $(which glxinfo) |grep GL
>>>>> ldd $(which fgfs) |grep GL
>>>>>
>>>>> and tell if the results are same?
>>>> the results are the following:
>>>>
>>>> martin@martin-desktop:~$ ldd $(which glxinfo) |grep GL
>>>>           libGL.so.1 => /usr/lib/nvidia-current/libGL.so.1
>>>> (0x00007f125fc7c000)
>>>> martin@martin-desktop:~$ ldd $(which fgfs) |grep GL
>>>>           libGL.so.1 => /usr/lib/nvidia-current/libGL.so.1
>>>> (0x00007fd5c9d61000)
>>>>
>>>> What does this tell me?
>>>>
>>>> Thanks,
>>>> Martin
>>>>
>>>>
>>>>> On Mon, Dec 24, 2012 at 3:57 PM, Kleiner Drache
>>>>> <kleinerdra...@gmx.at <mailto:kleinerdra...@gmx.at>> wrote:
>>>>>
>>>>>       Am 24.12.2012 14:24, schrieb Miko:
>>>>>       > Hi Kleiner Drache,
>>>>>       >
>>>>>       > you have to enable Multithreading on the command line with
>>>>>       > -- SNIP --
>>>>>       >   --prop:/sim/rendering/multithreading-mode=AutomaticSelection
>>>>>       > -- SNAP --
>>>>>       >
>>>>>       > But I don't think this will solve your Problem.
>>>>>
>>>>>       You are right, thats now better for cpu, but it doesn't solve
>>>>> my problem, but what does?
>>>>>
>>>>>       Martin
>>>>>
>>>>>
>>
>
>

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to