SL 6.0 NI-VISA 5.1.1 - libnipalu.so failed to initialize

[Josh Cartwright]

You may alternatively try:

memmap=60G$0x100000000

Which basically says, "hey kernel, just ignore (mask off as reserved) 60G of memory above 0x100000000..." instead of mem=2048M, which says: "hey kernel, you have 2048 megabytes of RAM".

[JCKey]

You may alternatively try:

memmap=60G$0x100000000

Which basically says, "hey kernel, just ignore (mask off as reserved) 60G of memory above 0x100000000..." instead of mem=2048M, which says: "hey kernel, you have 2048 megabytes of RAM".

Ok so I did that and it didn't work after restart UNTIL i re-ran the updateNIDrivers routine and let it reboot. NOW NI-VISA launches, but I kinda knew this would be a problem as well but was taking one problem at a time, it doesn't detect the USB connection with my scope. and through NI-VISA i can't add a static USB device to configure.

I'm using a USB keyboard and mouse so it can recognize USB devices but in the NI-VISA readme it said this

USB ISSUES ON LINUX

-------------------

NI-VISA relies on a Linux kernel feature for its USB support. This feature

is called "usbfs", and on older Linux kernels was referred to as "usbdevfs".

For NI-VISA to support USB devices, this feature must be present and

mounted (like a virtual filesystem). This is supported in most major Linux

distributions such as Red Hat, SUSE, and Mandrake. You may use the "mount"

command to display what filesystems are currently mounted to see if your

system currently supports this feature.

Also, the VISA user must have write access to the file that represents

the USB device, which is typically somewhere in a subdirectory within

"/proc/bus/usb". If this is not the case, the USB device is not

accessible by VISA (it will not be found using viFindRsrc and viOpen will

fail). The default configuration on most systems is that the 'root' user

has write access; however, no other user has this access.

when I run NI-VISA Driver wizard the USB bubble selection is greyed out and un-selectable

when I plug in the usb from my ociloscope this is what gets added (to what's already there) to my proc/bus/usb/devices  file

T:  Bus=02 Lev=02 Prnt=02 Port=01 Cnt=01 Dev#=  7 Spd=480  MxCh= 0

😧  Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1

P:  Vendor=0699 ProdID=0401 Rev= 2.58

S:  Manufacturer=Tektronix

S:  Product=DPO4054

S:  SerialNumber=B010288

C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA

I:* If#= 0 Alt= 0 #EPs= 3 Cls=fe(app. ) Sub=03 Prot=01 Driver=usbtmc

E:  Ad=01(O) Atr=02(Bulk) MxPS= 512 Ivl=125us

E:  Ad=82(I) Atr=02(Bulk) MxPS= 512 Ivl=0ms

E:  Ad=83(I) Atr=03(Int.) MxPS=   2 Ivl=250us

I was looking here

http://www.linux-usb.org/USB-guide/x173.html

and tried this

# mount -t usbdevfs none2 /proc/bus/usb

mount: unknown filesystem type 'usbdevfs'

then tried this

# mount -t usbfs none2 /proc/bus/usb

mount: none2 already mounted or /proc/bus/usb busy

does that mean that from mount

proc on /proc type proc (rw)

everything in subfolders of proc should also be mounted?

this is the contents of etc/fstab

# /etc/fstab

# Created by anaconda on Wed Aug 10 04:23:52 2011

#

# Accessible filesystems, by reference, are maintained under '/dev/disk'

# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info

#

/dev/mapper/vg_vistemp3-lv_root /                       ext4    defaults        1 1

UUID=92ebcc1e-0e17-489f-a7df-e17bf8a8182d /boot                   ext4    defaults        1 2

/dev/mapper/vg_vistemp3-lv_home /home                   ext4    defaults        1 2

/dev/mapper/vg_vistemp3-lv_swap swap                    swap    defaults        0 0

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

this is what appears when i check mount

# mount

/dev/mapper/vg_vistemp3-lv_root on / type ext4 (rw)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

tmpfs on /dev/shm type tmpfs (rw)

/dev/sda1 on /boot type ext4 (rw)

/dev/mapper/vg_vistemp3-lv_home on /home type ext4 (rw)

none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)

sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)

[Josh Cartwright]

I suspect that the errors you are seeing now are related to the kernel's USB TMC class driver attaching to the device, making its interfaces unavailable to NI-VISA.

The quick-and-dirty check would be to unload the 'usbtmc' driver, reloading VISA, and trying again.  You can do this as root by running 'modprobe -r usbtmc'.

Unfortunately, 'usbtmc' on reboot will reattach, so you'll need to either run the command before your application, or add 'usbtmc' to the modules blacklist.

[JCKey]

JoshCartwright wrote:

I suspect that the errors you are seeing now are related to the kernel's USB TMC class driver attaching to the device, making its interfaces unavailable to NI-VISA.

The quick-and-dirty check would be to unload the 'usbtmc' driver, reloading VISA, and trying again.  You can do this as root by running 'modprobe -r usbtmc'.

Unfortunately, 'usbtmc' on reboot will reattach, so you'll need to either run the command before your application, or add 'usbtmc' to the modules blacklist.

This doesn't seem to work, it still does not detect the USB device in NI-VISA Configuration or NI-VISA Driver wizard

[Jorge_Amaral]

Hello to all,

I've a question regarding the value that we should put after memmap=4096M$XXXXXXX.

My Dmesg returns:

BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)

BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)

BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)

BIOS-e820: 0000000000100000 - 00000000629f0000 (usable)

BIOS-e820: 00000000629f0000 - 0000000629f00000 (ACPI)

BIOS-e820: 00000000fffc0000 - 0000000010000000 (reserved)

The explanation says that I should look for the last line with usable memory. So I should add "memmap=4096M$100000".

But If I do this, Centos can't boot anymore.

Can someone give a tip please?

Thanks!

Jorge Amaral

[irwan]

try the 'mem=4096M' by itself, and don't worry about memmap= stuff.. I'm not convinced you need memmap=

Beware though, with this option, you're telling linux: please ignore all memory above 4G. so you'll end up with less memory for your system.

We don't have this arcane limitation on 64-bit linux.