r165 does not recognize nVidia core at /dev/nvidiactl

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Pull r165 from svn.
2. Build and install the pyrit & cpyrit_cuda modules.
3. Run: pyrit list_cores and pyrit benchmark

What is the expected output? What do you see instead?
Expect to see pyrit identify my GTX-260 card, but it does not. Instead, it 
displays both AMD cores of the CPU and error message about /dev/nvidiactl:

Pyrit 0.2.4-dev (svn r165) (C) 2008, 2009 Lukas Lueg 
http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3

The ESSID-blobspace seems to be empty; you should create an ESSID...


NVIDIA: could not open the device file /dev/nvidiactl (No such file or 
directory).


Running benchmark for about 1 seconds... /

Computed 481.71 PMKs/s total.

#1: 'CPU-Core (SSE2)': 247.8 PMKs/s (Occ. 94.6%; RTT 3.0)

#2: 'CPU-Core (SSE2)': 247.4 PMKs/s (Occ. 99.9%; RTT 2.9)


What version of the product are you using? On what operating system?
BT4Pre-Final
r165 from svn

Please provide any additional information below.

This had been working in r159.

And it is true that there is no /dev/nvidiactl entry in my /dev directory. 
Don't know what's going on here. Can you help?

Thanks in advance.

Original issue reported on code.google.com by cpmitc...@gmail.com on 14 Aug 2009 at 7:14

[GoogleCodeExporter]

Just noticed that this exact error is addressed in the Troubleshooting 
directory...

Let me give it a shot...

Original comment by cpmitc...@gmail.com on 14 Aug 2009 at 7:27

[GoogleCodeExporter]

Troubleshooting guide says:

NVIDIA: could not open the device file /dev/nvidiactl (No such file or 
directory). 
Ensure that the 'nvidia' module has been successfully loaded. Taking a look at 
the 
kernel ringbuffer may give more help: 
 modprobe nvidia 
 dmesg | tail

On my system, the modprobe nvidia command comes back with no error and no other 
output other than the system prompt.

The next command dmesg | tail  shows the last event to be related to the DHCP 
address pulled:

EXT3 FS on hda1, internal journal
ip_tables: (C) 2000-2006 Netfilter Core Team
powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ processors 
(2 
cpu cores) (version 2.20.00)
[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a 
way 
that Linux understands. Please report this to the Linux ACPI maintainers and 
complain to your BIOS vendor.
[Firmware Bug]: powernow-k8: Your BIOS does not provide ACPI _PSS objects in a 
way 
that Linux understands. Please report this to the Linux ACPI maintainers and 
complain to your BIOS vendor.
eth1: no link during initialization.
eth1: link up.



And that's it.

Suggestions?

Original comment by cpmitc...@gmail.com on 14 Aug 2009 at 7:38

[GoogleCodeExporter]

Filter nvidia-related messages with "dmesg | grep nvidia" and post the results.

Original comment by lukas.l...@gmail.com on 14 Aug 2009 at 7:50

[GoogleCodeExporter]

Lukas,

Got it working. It may be related to non-root user doing the modprobe command. 
Switched to root user, performed modprobe nvidia, dmesg | grep nvidia shows 
related 
output, and the card was recognizable once again. Thanks for your support! 
Please 
close the ticket.

Original comment by cpmitc...@gmail.com on 14 Aug 2009 at 8:00

[GoogleCodeExporter]

closed

Original comment by lukas.l...@gmail.com on 14 Aug 2009 at 8:11

• Changed state: Invalid