nilsdev does not find my PCI-DIO-32HS cards

[djm]

I've installed nidaqmx 8.0 on Red Hat Linux WS 3 Update 8 (kernel 2.4.21-47.ELsmp) and nilsdev does not find my two PCI-DIO-32HS (PCI-6533) cards on a Dell Precision 390 (has no ouput in standard or verbose mode). I have previously successfully installed this software configuration on a Dell Precision 380 (Pentium 4 3GHz /smp kernel /1GB RAM /SATA disks / two DIO-32HS / developing in g++) and am now unsuccessfully installing the same configuration in a Dell Precision 390 (Core 2 Duo/smp kernel/2GB RAM / two DIO-32HS / SATA disks).  niSystemReport finds the cards on my 390 and reports almost the exact same information regarding them as on my 380 (both output files attached). I have run "updateNIDrivers" and rebooted with the same results.  I have tried installing NI-KAL 1.5 prior to nidaqmx with the same results (again running updateNIDrivers).  I have tried disabling the second processor core in bios with the same results.  I have tried using nidaqmxconfig to export the configuration on the 380 and import it on the 390 but receive an error "-2147220712" (the bus and device numbers match in the system report - only the serial numbers are different although I don't know how to query the new serial numbers in software). I have tried booting with the kernel option "mem=4096M" with the same results.  Any help getting nilsdev and nidaqmx to work on my 390 would be greatly appreciated.
***@honeywell-tsi.com


Dell380SystemReport.txt:
http://forums.ni.com/attachments/ni/70/6959/1/Dell380SystemReport.txt


Dell390SystemReport.txt:
http://forums.ni.com/attachments/ni/70/6959/2/Dell390SystemReport.txt

[Matt A]

Hello David,

You could place the PCI-6533 devices from the Dell Precision 380 system
into the Dell Precision 390 system. Then, you would know that the
configuration file created by nidaqmxconfig had the correct serial
numbers. This might be worth your time, just to see if the working cards
from the working system can work in the Precision 390.

I also noticed another post <a href="http://forums.ni.com/ni/board/message?board.id=170&amp;message.id=164549&amp;requireLogin=False" target="_blank">here</a> with a similar error message. In this
case it was a conflict with firewall software. You may want to look
into that to see if you could be experiencing the same problem.