Sponsored Content
Operating Systems HP-UX HPUX 10.20 SCSI Hardware Drivers Post 303042686 by KeithM on Friday 3rd of January 2020 11:14:08 AM
Old 01-03-2020
HPUX 10.20 SCSI Hardware Drivers

I own a 1999 vintage HP Logic Analyzer that runs HPUX 10.20. It is a 9000/775/rock system similar to a Visualize C132L/160L system.


I'm attempting, mostly for the fun of it, to upgrade the existing slow 5MB/s-only SCSI system, with a new-er PCI card. Of course drivers is my major concern. I'd like to assemble as many hardware drivers for as many different SCSI cards as possible for that OS. I'm going to attempt to buy from ebay an older card, and then get it running.


I have so many questions:
  • Where are drivers stored within the OS?
  • How do you install a new driver?
  • So far, the best I can determine is that you create a new kernel using SAM and change the "OUT" to "IN" for the particular line, once that driver is installed.
  • Are there any official CDROM sources that would have a ton of drivers?
  • The drivers I obtain are going to become my shopping list --- whatever I have support for, I'll have to find a matching card...

My current system only has C720 installed. This is an NCR/LSI/Symbios 53C720 driver. I *may* be able to find a compatible card, but I think it might be tough.
This User Gave Thanks to KeithM For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Hardware and drivers

Dear All Can somebody help me how H/W and H/W drivers will affect the application? When I port my application from HP-UX to Solaris should I take care this area? What are the application touch point in H/W or H/W drivers on these two O.S.? (1 Reply)
Discussion started by: charlcy
1 Replies

2. HP-UX

HPUX Hardware commands.

HI ALL, I am new tp HPUX and i am looking for command that will retive me the following information on HPUX: Chassis Name & Serial Number: Monitor Name BIOS Name EthernetPort Name IPEndpoint Name PointingDevice Name Keyboard NetworkPrinter Name LocalPrinter (5 Replies)
Discussion started by: Veenak15
5 Replies

3. UNIX for Dummies Questions & Answers

drivers unix 5.01 is compatible with drivers epson fx-2190

Please, I'm From Argentina, And I Need To Know If The Drivers Of Program Unix, Version 5.01 Is Compatible Whit Drivers Of The Printer Epson Fx-2190 Thanks, And I Hope Yuor Answer. (0 Replies)
Discussion started by: juan alberghina
0 Replies

4. Shell Programming and Scripting

Need Script to Use CPUs on a HPUX server to simulate Workload Manager on HPUX.

I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies

5. HP-UX

minimum hardware requirement for HPUX 11i V3

I am new for HPUX OS and want to pursue my career in HPUX Administration. I could not able to get following information from HP.com site, that why I need an assistance to know that - can I install HPUX 11i V3 OS on old HP B2000 & B1000 workstations (these workstation are 4 to 5 year old) or not,... (5 Replies)
Discussion started by: girish.batra
5 Replies

6. Solaris

Which company's hardware is more stable, in case of IBM (AIX), HP (HPUX) & Sun (Solaris)

Hi guru I want to know which company's hardware is more stable means in term of H/W faults or replacement, in case of IBM (AIX), HP (HPUX) & SUN MICROSYSTEM (Solaris) & which order also, if we go through more stable to less stable system. Regards (1 Reply)
Discussion started by: girish.batra
1 Replies

7. HP-UX

pwage-hpux-T for Trusted HPUX servers

I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email. original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies

8. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies

9. HP-UX

Status of hardware in HpUx

We would like to know a HP Utility or any Unix command that can give the exact status of PCI Gigabit Ethernet cable (lan cable) We had tried to execute lanscan ioscan -fnC lan The status appears to be the same when the cable is plugged & unplugged and also when the lan is disabled &... (5 Replies)
Discussion started by: siva3492
5 Replies

10. HP-UX

HPUX 11.11 Sept.2003 cannot see PCI-X scsi adapter

I am trying to reload a RP4440 with 2x300gb disks and dual Port Network card, with HPUX 11.11 Sept 2003. When the os boots and and gets to the main menu to install HPUX or run recovery, it cannot find the disks or NIC. At the OS prompt (after loading files), ioscan shows the Class ba, and shows... (0 Replies)
Discussion started by: mrmurdock
0 Replies
PCSCD(8)							    User Manual 							  PCSCD(8)

NAME
pcscd - PC/SC Smartcard Daemon SYNOPSIS
pcscd [options] OPTIONS
-a, --apdu log APDUs and SW using the debug method (see -d) -c, --config file Specifies the file file as an alternate location for reader.conf -d, --debug OUTPUT display debug messages. OUTPUT may be: stdout (imply -f), stderr (imply -f), or syslog -f, --foreground Runs pcscd in the foreground (no daemon) -h, --help Displays information about the pcscd command line -v, --version Displays the program version number DESCRIPTION
pcscd is the daemon program for pcsc-lite and musclecard framework. It is a resource manager that coordinates communications with smart- card readers and smart cards and cryptographic tokens that are connected to the system. pcscd is normally started at boot time from /System/Library/StartupItems/SmartCardServices. It allows applications to access smart cards and readers without knowing details of the card or reader. pcscd coordinates the loading of drivers for card readers and plug-ins for different card types. The purpose of pcsc-lite is to provide both a cross compatible API for migrating Windows based PCSC applications to Unix and to provide a pluggable architecture for supporting smartcards and cryptographic tokens through high level API's. At startup, pcscd loads the smart card reader drivers specified in the /etc/reader.conf file (or specified using -c file). When a smart card is inserted into a reader, pcscd uses the ATR string from the card to identify this card. The /usr/libexec/SmartCardSer- vices/services directory contains plug-ins for the card. These plug-ins are searched. If the ATR string matches, the client library loads that plug-in for that token. USB SMART CARD READER DRIVERS
USB Smart card reader drivers are placed in the /usr/libexec/SmartCardServices/drivers directory. Each driver is simply a bundle. The bun- dle contains an XML file Info.plist which is parsed by pcscd. This file contains the vendor and product id of the device. This informa- tion allows pcscd to automatically determine when a reader is inserted or removed. SERIAL SMART CARD READER DRIVERS
Serial Smart card reader drivers are placed in the /usr/libexec/SmartCardServices/drivers directory. Each driver is simply a shared object file. The pcscd locates serial drivers with the /etc/reader.conf file. The file has the following format: # comment FRIENDLYNAME <Descriptive name> DEVICENAME <Short name> LIBPATH <Location of the driver library> CHANNELID <Hexadecimal channel identificator> FRIENDLYNAME is a user-friendly name of the reader that is served by this driver. This name is displayed to the user when necessary. DEVICENAME is a driver specific value. If you do not know this value, GEN_SMART_RDR is a good choice. LIBPATH is the full path to the shared library. CHANNELID is the channel ID for serial-port, smart-card readers. This could vary depending on the driver in which you are using - check the driver README for more information. Some use the following: /dev/ttyS0 (COM1) -> 0x0103F8 or 1 /dev/ttyS1 (COM2) -> 0x0102F8 or 2 /dev/ttyS2 (COM3) -> 0x0103E8 or 3 /dev/ttyS3 (COM4) -> 0x0102E8 or 4 Example: # Configuration file for pcsc-lite FRIENDLYNAME "My Smartcard Reader" DEVICENAME GEN_SMART_RDR LIBPATH /usr/libexec/SmartCardServices/drivers/my_reader.so CHANNELID 0x0103F8 # End of file Multiple drivers can be listed in /etc/reader.conf. Drivers are available at http://www.musclecard.com/drivers.html. SMART CARD PLUG-INS pcsc-lite uses plug-ins to handle different types of smart cards. There is a plug-in for each smart-card type. Plug-ins are installed in the /usr/libexec/SmartCardServices/services directory. Plug-ins for cards/tokens are available from the MUSCLE web site http://www.muscle- card.com. FILES
/etc/reader.conf : Reader configuration file /System/Library/StartupItems/SmartCardServices : pcscd startup script /var/run/pcscd.pid : process id of the running pcscd /usr/libexec/SmartCardServices/drivers/ : directory containing bundles for USB drivers" BUGS
None known. SEE ALSO
pcsctool(1), AUTHORS
David Corcoran <corcoran@identityalliance.com> and Ludovic Rousseau <ludovic.rousseau@free.fr> Linux March 2002 PCSCD(8)
All times are GMT -4. The time now is 05:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy