Hi:-
I am trying to install a device driver for Intel NIC card on TurboLinux, but getting following errors,
cc -O -Wall -o eepro100-diag eepro100-diag.c
eepro100-diag.c:72: unistd.h: No such file or directory
eepro100-diag.c:73: stdio.h: No such file or directory
eepro100-diag.c:74:... (1 Reply)
Hi - Basic question from newbie
I need to find out how to verify hardware installed on HPUX server. Mid-range server - as in i need to prove to customer that a specific cpu is installed, so much memory is installed, etc.
PLEASE HELP.
TA (1 Reply)
Hi - Basic question from newbie
I need to find out how to verify hardware installed on HPUX server. Mid-range server - as in i need to prove to customer that a specific cpu is installed, so much memory is installed, etc.
PLEASE HELP.
TA (16 Replies)
Hi
I need to know how a driver for a network interface card works, I want to learn the basic principles since I know that every driver has its specific implementation.
For example when we speak about the scheduler, we can read an operating system book and learn general design concepts e.g.... (0 Replies)
i want to write shell script that exit by displaying error if sqlplus is not installed.
The platform is oracle10g on solaris sparc.
I tried the which sqlplus command, but it returns errorcode 0 even sqlplus is not installed.
Kindly help? (3 Replies)
I couldn't install my nic in solaris 10. I compiled and added
the driver but failed to attach the driver and ifconfig output
shows only loopback dev. Please see the following output and tell
me whether my nic has been detected and why the driver failed to
attach?
My nic is detected in linux... (0 Replies)
Hi guys
My friend needs nfo driver for his Solaris box. I installed that driver for myself from scratch and he needs that driver in SVR4 format. I downloaded source code and run make and this is the point I don't how to proceed.
How can I recognize which needs go to the package ?
Does make... (0 Replies)
In Solaris 10 it was easy, a simple grep through modinfo output and you'd have the version of any loaded module, including your NIC drivers. In my career I've seen many people relying on this information in their scripts. Now I'm on Solaris 11, and where have the version numbers gone? The... (0 Replies)
Can you please let me know how can i verify /check inside the script if the below to package installation commands are successful or if they failed for any reasons?
1. pkgadd -a $INSTP/install/dadmin -d $INSTP/install/apachesrv.pkg
2. pkgadd -a $INSTP/install/dadmin -d... (6 Replies)
Hello Forum,
I'm issuing a one line bash command to look for the version of an installed application and saving the result to a variable like so:
APP=application --version
But if the application is not installed I want to return to my variable that the Application is not installed. So I'm... (2 Replies)
Discussion started by: greavette
2 Replies
LEARN ABOUT NETBSD
eshconfig
ESHCONFIG(8) BSD System Manager's Manual ESHCONFIG(8)NAME
eshconfig -- configure Essential Communications' HIPPI network interface
SYNOPSIS
eshconfig [-estx] [-b bytes] [-c bytes] [-d filename] [-i usecs] [-m bytes] [-r bytes] [-u filename] [-w bytes] [interface]
DESCRIPTION
eshconfig is used to configure device-specific parameters and download new firmware to the Essential Communications RoadRunner-based HIPPI
network interface. The interface is very sensitive to the DMA performance characteristics of the host, and so requires careful tuning to
achieve reasonable performance. In addition, firmware is likely to change frequently, which necessitates a reasonably easy way to update
that firmware.
Available operands for eshconfig:
-b bytes
Adjust the burst size for read (by NIC of host memory) DMA.
-c bytes
Adjust the burst size for write (by NIC of host memory) DMA.
-d filename
Filename for file to download into NIC firmware. This must be a file in the standard Essential format, with :04 preceding every
line, and a tag line at the end indicating the characteristics of the firmware file.
-e Write data to EEPROM. Normally, setting tuning parameters will only persist until the system is rebooted. Setting this parameter
ensures that the changes will be written to EEPROM.
-i usecs
Interrupt delay in microseconds.
-m bytes
Minimum number of bytes to DMA in one direction (read or write) before allowing a DMA in the other direction. Tuning this prevents
one direction from dominating the flow of bytes, and artificially throttling the NIC.
-r bytes
Bytes before DMA starts for read (from host to NIC). This controls how soon the DMA is triggered; until this many bytes are
requested, the DMA will not begin.
-s Show statistics for the HIPPI NIC. Repeat the option to suppress non-zero statistics.
-t Show current tuning parameters on the host.
-u filename
Name of file to which the NIC firmware should be uploaded. Not currently supported.
-w bytes
Number of bytes required before write (from NIC to host) DMA is started. Until this many bytes are ready to be written, the DMA will
not start.
-x Reset the NIC. This is necessary for the HIPPI-FP support, as ifconfig(8) will no longer physically reset the NIC when the inter-
faces goes up and down.
Only the super-user may modify the configuration of a network interface.
DIAGNOSTICS
Messages indicating the specified interface does not exist or the user is not privileged and tried to alter an interface's configuration.
SEE ALSO esh(4), ifconfig(8)HISTORY
The eshconfig command first appeared in NetBSD 1.4.
BSD June 17, 2005 BSD