Frequently Asked Questions
Linux (page2)
Q6: The Extreme SCSI tools are core dumping immediately. What's wrong?
A6: The tools were compiled against dynamically loaded libraries to cut down
on installation size. Your shell needs to define an environmental variable
called LD_LIBRARY_PATH so that the programs have access to these functions.
Linux has not shown any problem with this so no configuration should be
neccessary.
A6b: Current versions of software do a tranfer size probe along with the
SCSI bus probe. This means that we attempt to send a SCSI command with a
very large buffer. If it fails we divide the buffer in half and try it
again. This proceedure continues until the command suceeds. This value
should be good for all future SCSI commands.
We've discovered that some systems crash when you attempt to do a larger
transfer size than they're prepared to handle. You can attempt to patch the
OS to the latest revision and download the latest drivers for your host
adapter(s).
Currently size probing is disabled in Linux and the max is set to a static
512k transfer.
Q7: The program is crashing, what can I do?
A7: If the program is crashing and it's not due to the LD_LIBRARY_PATH
export, then we're going to need to see the appropriate debug file. Each
product has a running debug file named Debug_[productname].txt. Viewing
the file may provide insights into why you're having problems. If nothing
is obvious to you, please send it to us at
unix_support@extremeprotocol.com
Q8: Are there any other environmental variables that need to be set?
A8: In order to view text files (logs, scripts, etc), we rely on a standard
environmental variable called EDITOR. This should point to a GUI based text
editing tool of your choice. (ie. setenv EDITOR "gedit")
Q9: When running xdev it complains that it could not allocate colors for a
Pixmap and the xdev launcher bar is black with white squares?
A9: Unfortunately, the default window manager for Linux (sawtooth/gnome?)
seems to allocate all of the shared colorspace. Even reducing the color
requirements down to 24 doesn't accomodate it. You can use another window
manager (mwm) or run xdev with a private colormap by adding the -private
command line option. A side effect of the private colormap is that the
colors will be wrong unless the xdev window has focus (you click into it.)
To change window managers, you can edit the $HOME/.Xclients or
$HOME/.Xclients-defaults file to point to a new manager.
Q10: I get error messages complaining that a file isn't found, or can't be
opened. What's going on?
A10: Some sections of the code may assume that the current working directory
is in your PATH. If you find such an example, please let us know. This
can be fixed on your end though by changing your PATH variable to always
include the current directory (.) in its pathing searches. Another
possible explaination is that the file doesn't have its file permissions set
appropriately to be read/written/executed by your account. This should
rarely happen if you are running as root as recommended.
|
|
|
