NIVXI on RHEL 5

Similar Questions

• NIDAQmxBase Linux RHEL 6 x86_x64 USB...

  Trying to get NIDAQmxBase 3.6 w / USB support for installed on LINUX RHEL 6.3 x86_x64 WS

  USB 6501 OEM,

  USB-6009 OEM

  running as root:

  [root@NIX1 /] # mount

  usbfs seems to be mounted... etc/fstab to mount it as indicated

  / dev/map/vg_nix1-lv_root on / type ext4 (rw)
  proc on/proc type proc (rw)
  Sysfs on/sys type sysfs (rw)
  type devpts on/dev/pts devpts (rw, gid = 5, mode = 620)
  tmpfs on/dev/shm type tmpfs (rw, rootcontext = "" system_ubject_r:tmpfs_t:s0 "")
  usbfs/proc/bus/USB type usbfs (rw, devmode = 0666)
  / dev/sdb1 on / boot type ext4 (rw)
  / dev/map/vg_nix1-lv_home market/House 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)
  / dev/sr0 on/media/NIDAQmxBase360 type iso9660 (ro, nosuid, nodev, uhelper = udisks, uid = 500, gid = 500, iocharset = utf8, mode = 0400, dmode = 0500)

  lsdaq runs and complains about the firmware:

  [root@NIX1 /] # / usr/local/natinst/nidaqmxbase/bin/lsdaq
  --------------------------------
  Detect of National Instruments DAQ devices
  Find the following materials:

  Device error: incompatible firmware.  Serial number: 01646C 23

  Run /bin/FWUpdate update.

  green light on USB 6501 flashes constantly

  running FWUpdate compains as follows:

  --------------------------------
  [root@NIX1 /] # / usr/local/natinst/nidaqmxbase/bin/FWUpdate
  Could not load library /usr/local/lib/liblvrt.so.12.0
  libXinerama.so.1: cannot open shared object file: no such file or directory
  To download the engine Runtime of LabVIEW, go to http://www.ni.com/rteFinder?dest=lvrte&version=12.0&platform=Linux&lang=en

  location of /usr/local/lib/liblvrt.sa.12.0 reports:

  [root@NIX1 /] # locate liblvrt.so.12.0
  /usr/local/lib/liblvrt.so.12.0
  /usr/local/lib/LabVIEW-2012/liblvrt.so.12.0.0

  STAT to file reports:

  [root@NIX1 /] # stat /usr/local/lib/liblvrt.so.12.0
  File: ' / usr/local/lib/liblvrt.so.12.0'-> 'LabVIEW-2012/liblvrt.so.12.0.0 '.
  Size: 30 blocks: 0 IO block: 4096 symlink
  Feature: fd00h / 64768d Inode: 131699 links: 1
  Access: (0777/lrwxrwxrwx) Uid: (0 / root) Gid: (0 / root)
  Access: 2012-10-22 14:27:59.858557301-0400
  Change: 2012-10-22 14:27:59.813443661-0400
  Change: 2012-10-22 14:27:59.813443661-0400

  NIDAQmxBase 3.6 installs VISA and 'C' interface via. \INSTALL, reports success, seems normal.

  cannot run lsdaq, FWUpdate or anything like that on the Menu of Applications National Instruments (NI-VISA submenu, OR Trace of IO.)

  My guess is that the permissions are always watered.

  Solved and was able to update the firmware.

  Well explained here...  http://digital.NI.com/public.nsf/allkb/93C92D41B25341B286257A4D007BACB8

  and here's how-useful.  http://h10025.www1.HP.com/ewfrf/wc/document?CC=CA&DLC=en&docName=c01769573&LC=en

• Install Redhat RHEL 6 on IdeaPad Z565 suspended

  I have Redhat Linux RHEL 6, it blocks during the installation on the IdeaPad Z565, which I was surprised, others seen elsewhere?

  Ubuntu works very well I have it on my z565.

• Checking if NEITHER-6509 works on my RHEL WS 4.6

  I installed NIDAQmx 8.0 on my Red Hat Enterprise WS 4.6 machine.  Installing the driver seemed successful.

  Using the nilsdev command, the following text is displayed:

  OR PCI-6509: "Dev1".
  Serial number: 0x13E94F3
  Bus type: PCI
  PCI bus: 0 x 4
  PCI device: 0x2
  IRQ level: 0xC9
  The memory range: 0xDFAFD000-0xDFAFDFFF
  The memory range: 0xDFAFE000-0xDFAFFFFF

  How can I make sure that the PCI-6509 Board work properly with my RHEL WS 4.6?

  Thank you

  Wayne

  Hi Wayne,

  Welcome to the forums EITHER!  The best way to check that your device is working properly is to use a Test Panel.  Following knowledge base has received instructions to know how to open a Test Linux Panel: panels of Test for DAQmx in Linux

  Since the test Panel, you will be able to read / write the 6509 digital lines to make sure that the device is functioning properly.  Thanks for posting and have a great day!

  -John

• Announcement: update the Configuration guide for RHEL v6/v7 with storage Dell PS Series available

  Red Hat Enterprise Linux Configuration Guide for Dell storage bays Series PS

  This configuration guide provides information on the integration of the RHEL 6 and 7 operating environments with the PS Series Dell storage arrays using iSCSI technology. The guide includes tips for working with volumes, using MPIO and some performance tips.

  The PDF file is available here:

  Kind regards

  Don

  Hello

  With Linux, as any OS, iSCSI is not different from the SAS/SATA or Fibre Channel.  No matter how you are connected to a "disk", it looks like a SCSI to the OS disk.

  So yes, you use the mount points.   That's how Linux as most UNIX operating systems do it.  But use any method supported for other iSCSI disks.   In Windows, you can use drive letters or mount points.

  Kind regards

  Don

• Error thrown when activating disk checking on RHEL 5. 6

  The /home/bb/bbc1.9i-btf/tmp file system is FULL

  Any ideas what might be causing this error as soon as the client has been started? There is no shortage of disk or quotas.

  Just had to come back to this problem today. It turns out that my original solution was not quite accurate. A combination of add DFSORT = ""-k4n ' to bbsys.local and removing the + signs of lines 60 and 75 of bb - disk.sh fixed the problem. " It seems that RHEL was analysis commands differently from previous versions of * Nix.

• EMC Ex3 - 40f, Qlogic ISP 2432 and RHEL 4 x86_64

  I have a blade of 1855 w / daughter CF card. The OS is RHEL AS 4 update 5 x86_64. I recently installed this OS and have it connected to an EMC3 40f, which presents this host w / 100GB RAID5 LUN. First of all, I did this: (orders in "BOLD", released in BLUE)

  1. register with RHN

  2 up2date rpm-build redhat-config-RPM

  3. up2date - get-source kernel

  4. rpm-ivh /var/spool/up2date/kernel*.src.rpm

  5. cd/usr/src/redhat/SPECS

  6 rpmbuild - bp - target = x86_64 kernel - 2.6.spec

  7. cp-a /usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9/usr/src

  8. ln-s /usr/src/linux-2.6.9 usr

  The steps above were made so that these steps should compile without any problem

  9 tar - xvf qla2xxx - v8.01.00 - 3dkms.tar.gz

  10. rpm-ivh dkms - 2.0.5 - 1.noarch.rpm

  11 rpm - ivh qla2xxx - v8.01.00 - 3dkms.noarch.rpm

  Step 11 will produce the following:

  Preparing...                ########################################### [100%]
  1:qla2xxx                ########################################### [100%]

  Create a symbolic link /var/lib/dkms/qla2xxx/v8.01.00/source->
  /usr/src/qla2xxx-V8.01.00

  DKMS: Add Completed.

  Construction of module to the kernel running has been ignored since the
  for this kernel kernel sources does not appear to be installed.

  Hmm... I thought that I just added the CBC core following steps 1 through 8. These steps are listed here: http://kbase.redhat.com/faq/FAQ_85_5109.shtm

  I also installed the EMCPower. Linux - 5.0.0 - 157.rhel.x86_64.rpm under the default location. It has now SANsurferCLI and SANsurfer (gui).

  When I rebooted the machine, I see dmesg:

  HBA QLogic Fibre Channel adapter driver
  ACPI: PCI Interrupt 0000:02:00.0 -> GSI 16 (level, low)-> IRQ 169
  qla2400 0000:02:00.0: found an ISP2432, irq 169, the iobase 0xffffff0000014000
  qla2400 0000:02:00.0: PCI configuration space...
  PCI: The timer setting of latency of the device 0000:02:00.0 to 64
  qla2400 0000:02:00.0: NVRAM configuration settings...
  qla2400 0000:02:00.0: audit loaded RISC code...
  qla2400 0000:02:00.0: allocated (1061 KB) to dump the firmware...
  qla2400 0000:02:00.0: waiting for LIP finish...
  qla2400 0000:02:00.0: LIP reset occurred (f7f7).
  qla2400 0000:02:00.0: LOOP UP detected (2 Gbps).
  qla2400 0000:02:00.0: topology - (F_Port), loop 0 host address 0 x
  SCSI1: qla2xxx
  qla2400 0000:02:00.0:
  Adapter HBA QLogic Fibre Channel driver: 8.01.04 - d8
  QLogic QME2462 - Dell B S PCI-Express to 4Gb FC Dual Channel
  ISP2432: PCIe (2.5 Gb/s x 4) @ 0000:02:00.0 hdma + host # 1, fw = 4.00.23 =
  Seller: DGC model: LUNZ Rev: 0324
  Type: Access Direct ANSI SCSI Revision: 04
  qla2400 0000:02:00.0: scsi(1:0:0:0): activated tagged depth of queue lines, 32.
  SDB: READ CAPACITY failed.
  SDB: State = 1, message = 00, host = 0, driver = 08
  Current SD: sense key illegal request
  Additional detection: logical unit not supported
  SDB: asking cached data failed
  SDB: assuming drive cache: write through
  SDB: READ CAPACITY failed.
  SDB: State = 1, message = 00, host = 0, driver = 08
  Current SD: sense key illegal request
  Additional detection: logical unit not supported
  SDB: asking cached data failed
  SDB: assuming drive cache: write through
  SDB:end_request: i/o error, dev sdb, sector 0
  Buffer I/O error on device sdb, logical block 0
  end_request: i/o error, dev sdb, sector 0
  Buffer I/O error on device sdb, logical block 0
  end_request: i/o error, dev sdb, sector 0
  Buffer I/O error on device sdb, logical block 0
  Failed to read the partition table
  Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0
  Attached scsi generic sg2 at scsi1, channel 0, id 0, lun 0, type 0
  Seller: DGC model: LUNZ Rev: 0324
  Type: Access Direct ANSI SCSI Revision: 04
  qla2400 0000:02:00.0: scsi(1:0:1:0): activated tagged depth of queue lines, 32.
  SDC: READ CAPACITY failed.
  SDC: State = 1, message = 00, host = 0, driver = 08
  Current SD: sense key illegal request
  Additional detection: logical unit not supported
  SDC: asking cached data failed
  SDC: assuming drive cache: write through
  SDC: READ CAPACITY failed.
  SDC: State = 1, message = 00, host = 0, driver = 08
  Current SD: sense key illegal request
  Additional detection: logical unit not supported
  SDC: asking cached data failed
  SDC: assuming drive cache: write through
  SDC:end_request: error e/s, dev SDC, sector 0
  Buffer I/O error on device DSC, logical block 0
  end_request: error e/s, dev SDC, sector 0
  Buffer I/O error on device DSC, logical block 0
  end_request: error e/s, dev SDC, sector 0
  Buffer I/O error on device DSC, logical block 0
  Failed to read the partition table
  Attached scsi disk SDC at scsi1, channel 0, id 1, lun 0
  Attached scsi generic sg3 at scsi1, id 1, channel 0, lun 0, type 0
  ACPI: PCI Interrupt 0000:02:00.1 -> 17 of GSI (low)-> IRQ 193
  qla2400 0000:02:00.1: found an ISP2432, irq 193, the iobase 0xffffff0000016000
  qla2400 0000:02:00.1: PCI configuration space...
  PCI: The timer setting of latency of the device 0000:02:00.1 to 64
  qla2400 0000:02:00.1: NVRAM configuration settings...
  qla2400 0000:02:00.1: audit loaded RISC code...
  qla2400 0000:02:00.1: allocated (1061 KB) to dump the firmware...
  qla2400 0000:02:00.1: waiting for LIP finish...
  qla2400 0000:02:00.1: cable is disconnected...
  SCSI2: qla2xxx
  qla2400 0000:02:00.1:
  Adapter HBA QLogic Fibre Channel driver: 8.01.04 - d8
  QLogic QME2462 - Dell B S PCI-Express to 4Gb FC Dual Channel
  ISP2432: PCIe (2.5 Gb/s x 4) @ 0000:02:00.1 hdma + host # 2, fw = 4.00.23 =
  Insert the floppy driver for 2.6.9 - 55.ELsmp
  Floppy drive (s): fd0 is 1.44 M
  floppy0: not found floppy disk controller

  However, when I run the SANsurferCLI, it shows no. HBA connected. I cannot fdisk the LUN. I get:

  [root@xxx ~] # fdisk/dev/sdb

  Unable to read/dev/sdb

  [root@xxx ~] # mkfs - v-j/dev/sdb
  mke2fs 1.35 (February 28, 2004)
  / dev/sdb whole device, is not just a partition.
  Still? (y, n) y
  WARNING: could not delete sector 2: try to write the file system blocks resulted in brief writing
  Filesystem label =.
  OS type: Linux
  Block size = 4096 (log = 2)
  Fragment size = 4096 (log = 2)
  131072 inodes, 262144 blocks
  13107 blocks (5.00%) reserved for the super user
  First data block = 0
  Maximum filesystem blocks = 268435456
  8 groups of block
  32768 blocks per group, 32768 fragments per group
  16384 inodes per group
  Superblock backups stored on blocks:
  32768, 98304, 163840 229376

  WARNING: could not read block 0: try to read the file system block resulted in short read
  WARNING: could not delete sector 0: try to write the file system blocks resulted in brief writing
  Writing inode tables: fact
  Creating the journal (8192 blocks): fact
  Writing Superblocks and filesystem accounting information:
  Attention, was struggling to write to superblocks.done

  This file system will be automatically checked all 38 media or
  180 days, whichever comes first.  Use tune2fs - c or-i to substitute.

  I expect that to happen. Included here for clues:

  [root@xxx ~] # mount/dev/sdb/san/01 /
  / dev/sdb: input/output error
  Mount: / dev/sdb: cannot read the superblock

  The output of/proc/scsci/qla2xxx/1:

  [root@xxx qla2xxx] # 1
  QLogic PCI with Fibre Channel for QME2462 host adapter:
  4.00.23 firmware version , Driver version 8.01.04 - d8
  INTERNET SERVICE PROVIDER: ISP2432
  Ask the queue = 0 x 215580000, queue response = 0x215d10000
  Ask account queue = 4096, the response queue = 512 count
  Total number of active orders = 0
  Total number of interruptions = 12855
  Device queue depth = 0 x 20
  Number of entries free request = 3592
  Number of time-outs of the mailbox = 0
  Number of ISP abandons = 0
  Number of the loop = 0 Resync
  Number of retries for empty slots = 0
  Number of requests in pending_q = 0, retry_q = 0, done_q = 0, scsi_retry_q = 0
  Adapter: loop State host = , flags is 0x1e03
  DPC flags = 0 x 4000000
  Flags MBX = 0 x 0
  Link down Timeout = 045
  Port down retry = 045
  Number of connection attempts = 045
  Dropped orders retried with image (s) = 0
  Product ID = 0000 0000 0000 0000

  The SCSI device information:
  SCSI-qla0-adapter-node = 200000e08b9b8968;
  SCSI-qla0-adapter-port = 210000e08b9b8968;
  Qla0-SCSI-target - 0 = 5006016941e07929;
  Qla0-SCSI-target - 1 = 5006016041e07929;

  FC Port information:
  SCSI-qla0-port-0 = 50060160c1e07929:5006016941e07929:c302ef:81;
  SCSI-qla0-port-1 = 50060160c1e07929:5006016041e07929:c303ef:82;

  Information about the SCSI LUN:
  (Id: Lun) *-indicates the logical unit number is not registered with the operating system.
  (0: 0): total reqs 12595 pending reqs 0, flags 0x0, 0:0:81 00
  (1: 0): flags of reqs total 130, in anticipation of reqs 0, 0 x 0, 0:0:82 00

  So can someone indicate on WHAT I'm doing wrong? I am open to reinstall the operating system for the same version (LIKE 4u5 x86_64).

  Thank you.

  
  

• HIT for RHEL 7

  When support for RHEL based 7 facilities? We prepare for you present to a RHEL 7 from datacenter and we can't seem to find a HIT for Equallogic

  So, ONCE in 2015, is basically what you're saying.

  Wow this is a very tight timetable for a company of $60 US per year.

  Its been over a year since the last version of Linux has HIT (April 2014) and in terms of support of RHEL7:

  «Red Hat Enterprise Linux 7 (Maipo) is based on Fedora 19, upstream Linux kernel 3.10, systemd 208 and GNOME 3.8.» The first beta was announced December 11, 2013, and a release candidate first aired April 15, 2014. On June 10, 2014 Red Hat Enterprise Linux 7 was officially released. »

  Rhel7 has been officially available for more than a year, none supported yet of Dell.  I hope that Dell realizes that is telling its Linux customers to shop elsewhere.

• Impossible to install RHEL 6

  Hi all
  I have a Dell Inspiron 14z 5423 Ultrabook. I have Windows 7 installed in it. I try to install RHEL 6 alongside windows.
  I've installed RHEL on most older PCs, but this one is new technology with 32 GB SSD + 500 GB HARD drive with the hybrid technology. I couldn't install RedHat.

  The SATA in the BIOS is set to Intel Smart Response Technology (aka RAID). I have about 80 GB unallocated space (as in the picture below: MB free, 82694) and when I try to create partitions (/ boot, / home, /...), then it displays the error message saying "not enough space" and the partition could not be created.

  

  

  Previously he also asked to reset the drive, but I clicked on ignore all because I have not saved anything.

  Please help me about the installation.

  Hi TusharKhatiwada,

  Linux does not support configuring mSATA. You will need to disable acceleration of the application of Smart Response technology since the office. Change the SATA operation setting in the BIOS to AHCI and install RHEL 6 on the 500 GB HARD drive.

  Please let me know if you need further information.

• When support for RHEL based 7 facilities? I see in the post of March/April... Now its may?

  When support for RHEL/ORACLE 7/7.1 based installations? We prepare for you present to a RHEL 7 from datacenter and we can't seem to find a HIT for Equallogic

  not so long ago, the message was 'start-2015'. now "somewhere" later this year

  It seems that we should not expect too much from the reliability of this information, most of the time they are simply not true.

• Installation of RHEL 6.5 kit HIT

  I "m trying to do an installation of the kit Linux HIT (1.2.0) on a server of RHEL6 fully updated (patch level 6.5). While the HIT kit installed, I "m having problems with the demon ehcmd crash on startup, due to a non supported ' iscsiadm - version ' revision.

  The following lines of /var/log/equallogic/ehcmd.log show the error:

  -------

  3 December 13 10:44:40 | EHCMD | 13484. 13484. INFO | Iscsiadm | 307. Analysis of chain vesion "6.2.0 - 873.10.el6"
  3 December 13 10:44:40 | EHCMD | 13484. 13484. ERROR | run | 703. UNHANDLED EXCEPTION *.
  3 December 13 10:44:40 | EHCMD | 13484. 13484. INFO | Iscsiadm | 336. EXCEPTION: version output iscsiadm not recognized (not 2.0): no such file or directory

  ---------

  The iscsiadm installed version is 6.2.0.873.10.el6, the package RPM RHEL6 iscsi-initiator-utils - 6.2.0.873 - 10.el6.x86_64. Running ' iscsiadm - version ' returns ' iscsiadm version 6.2.0 - 873.10.el6.

  Returning the iscsi-initiator-utils RPM package
  iSCSI-initiator-utils - 6.2.0.872 - 16.el6.x86_64 seems to 'solve' the problem and one ' iscsiadm - version ' returns ' iscsiadm version 2.0 - 872.41.el6 "and ehcmd starts as expected.

  So, I "m, a little worried here that the HIT kit does not support the latest fully connected RHEL6 (RHEL 6.5). fix?

  Hello

  The next version of HIT, v1.3.0 will support v6.5 and RHEL v6.4.    The download page for HIT v1.2.0 lists the specific versions that it supports.

  Kind regards

• OMSA on CentOS/RHEL 7

  Hi all!

  I want to get the work of the OMSA on my old PowerEdge 2950 server. OMSA 7 works well with CentOS 6, it will be available on CentOS 7 too?

  Thank you.

  I know me:

  www.dell.com/.../DriversDetails

  It seems that the version 7.4.1 supports 12g (or earlier?) material and RHEL 7 dated November 21.

  Best,
  Martin

• VSOM MSP RHEL Server runtime error

  Hello

  I encountered the problem in VSOM in MSP RHEL Server loading. Login page displays no value. Error loading /media1 during the startup process of RHEL. It says "editing local files system error" and "mount: structure needs to be cleaned. After reviewing the status of service cisco, VSOM is down and in the end "/ media1 is not mounted.

  Anyone has idea or has encountered such a problem, please advise. Thank you.

  Hey Ritchie,

  I think that the option we're trying to do repair is not help us here,

  Run the command again to repair, also follow them above below the foregoing steps above mount the partition.

  ++ Run xfs_repair for /media1

  #-L/dev/sdc1 xfs_repair-l/dev/sdc2

  Represent-L Force newspaper zero setting, let me know if no query.

  Thank you

  Maëlle

• DR SETUP IN RAC on RHEL 6.6 11.2.0.3

  Hello Experts

  We decided to apply to the DR SETUP in RAC environment

  DB version: 11.2.0.3 on RHEL 6.6

  I got enough hands with stand-alone database, but NOT with several Instance.

  Experts please tell me one dataguard used in autonomous would be also identical for the cars or would it be different to implement?

  Please find tell me proper requirement for all this. What to do all this.

  My boss my plate, I have to work, so I'll do some research and development on all this.

  I'm now the pressure.

  Experts please tell me one dataguard used in autonomous would be also identical for the cars or would it be different to implement?

  The process followed to build a house waiting for identical CARS that the stand-alone version one, but in the end, you add instances of sleep which does not happen in a stand-alone creation.

  I guess your standby nodes are all loans with the Oracle binary and set up the IM. If Yes, then you can continue on the creation of Eve.

  I have my notes on creating a physical standby database in a RAC configuration for a primary database of the CARS.

  FCAC Eve physical database to the primary database of the CARS. Shivananda Rao

  HTH

  -Jonathan Rolland

• Oracle 12 c on RHEL 7.2

  I want to install Oracle 12 c on Red hat Linux 7.2. Is Oracle 12 c certified and supported on RHEL 7.2?

  Help, please.

  Thank you

  Aerts

  Oracle Linux or RHEL version updates, such as 7.1, 7.2, 7.3, etc., are all based on the same major version of OS. An update does not break backward compatibility with the same version and introduced fixed bugs, security patches, and may introduce additional features. It is possible that a product requires a minimum version and the version of publication of update, however, if a product is certified for Oracle Linux or RHEL 7.0, there is also picked up and certified on updates later release. Of course, this does not apply to upgrades of major version, such as 6.x or 7.x, for which there is no upgrade path taken in charge anyway.