📄 sk98lin.txt
字号:
and port B as eth1. Both ports can be used independend with distinct IP addresses. The preferred port setting is not used. Rlmt is turned off. NOTE: The modes CheckLocalPort and CheckSeg are meant to operate in configurations where a network path between the ports on one adapter exists. Especially, they are not designed to work where adapters are connected back-to-back.***(6) LARGE FRAME SUPPORT=======================Large frames (also called jumbo frames) are now supported by thedriver. This can result in a greatly improved throughput iftransfering large amounts of data.To enable large frames, set the MTU (maximum transfer unit)of the interface to the value you wish (up to 9000). The commandfor this is: ifconfig eth0 mtu 9000This will only work if you have two adapters connected back-to-backor if you use a switch that supports large frames. When using aswitch, it should be configured to allow large frames, withoutautonegotiating for them.The setting must be done on all adapters that can be reached bythe large frames. If one adapter is not set to receive large frames,it will simply drop them.You can switch back to the standard ethernet frame size with: ifconfig eth0 mtu 1500To make this setting persitent, add a script with the 'ifconfig'line to the system startup sequence (named something like "S99sk98lin"in /etc/rc.d/rc2.d).***(7) TROUBLESHOOTING===================If you run into problems during installation, check those items:Problem: The SK-98xx adapter can not be found by the driver.Reason: Look in /proc/pci for the following entry: 'Ethernet controller: SysKonnect SK-98xx ...' If this entry exists, then the SK-98xx adapter has been found by the system and should be able to be used. If this entry does not exist or if the file '/proc/pci' is not there, then you may have a hardware problem or PCI support may not be enabled in your kernel. The adapter can be checked using the diagnostic program which is available from the SysKonnect web site: www.syskonnect.de Some COMPAQ machines have a problem with PCI under Linux. This is described in the 'PCI howto' document (included in some distributions or available from the www, e.g. at 'www.linux.org'). This might be fixed in the 2.2.x kernel series (I've not tested it).Problem: Programs such as 'ifconfig' or 'route' can not be found or you get an error message 'Operation not permitted'.Reason: You are not logged in as user 'root'. Logout and login as root or change to root via 'su'.Problem: Using the command 'ping <address>', you get a message "ping: sendto: Network is unreachable".Reason: Your route is not set up correct. If you are using RedHat, you probably forgot to set up the route in 'network configuration'. Check the existing routes with the 'route' command and check if there is an entry for 'eth0' and if it is correct.Problem: The driver can be started, the adapter is connected to the network, but you can not receive or transmit any packet; e.g. 'ping' does not work.Reason: You have an incorrect route in your routing table. Check the routing table with the command 'route' and read the manual pages about route ('man route').NOTE: Although the 2.2.x kernel versions generate the routing entry automatically, you may have problems of this kind here, too. We found a case where the driver started correct at system boot, but after removing and reloading the driver, the route of the adapter's network pointed to the 'dummy0' device and had to be corrected manually. Problem: You want to use your computer as a router between multiple IP subnetworks (using multiple adapters), but you can not reach computers in other subnetworks.Reason: Either the router's kernel is not configured for IP forwarding or there is a problem with the routing table and gateway configuration in at least one of the computers.Problem: At the start of the driver, you get an error message: "eth0: -- ERROR -- Class: internal Software error Nr: 0xcc Msg: SkGeInitPort() cannot init running ports"Reason: You are using a driver compiled for single processor machines on an multiprocessor machine with SMP (Symetric MultiProcessor) kernel. Configure your kernel appropriate and recompile the kernel or the modules.If your problem is not listed here, please contact SysKonnect's technicalsupport for help (linux@syskonnect.de).When contacting our technical support, please ensure that thefollowing information is available:- System Manufacturer and Model- Boards in your system- Distribution- Kernel version***(8) HISTORY===========VERSION 4.02 (In-Kernel version)New Features:- Add Kernel 2.4 changesKnown limitations:- NoneVERSION 4.01 (In-Kernel version)Problems fixed:- Full statistics support for DualNet modeKnown limitations:- NoneVERSION 4.00 (In-Kernel version)Problems fixed:- Memory leak found New Features:- Proc filesystem integration- DualNet functionality integrated- Rlmt networks addedKnown limitations:- statistics partially incorrect in DualNet modeVERSION 3.04 (In-Kernel version)Problems fixed:- Driver start failed on UltraSPARC- Rx checksum calculation for big endian machines did not work- Jumbo frames were counted as input-errors in netstatVERSION 3.03 (Standalone version)Problems fixed:- Compilation did not find script "printver.sh" if "." not in PATHKnown limitations:- NoneVERSION 3.02 (In-Kernel version)Problems fixed:- NoneNew Features:- Integration in Linux kernel source (2.2.14 and 2.3.29) Known limitations:- NoneVERSION 3.01Problems fixed:- NoneNew Features:- Full source releaseKnown limitations:- NoneVERSION 3.00Problems fixed:- NoneNew Features:- Support for 1000Base-T adapters (SK-9821 and SK-9822)Known limitations:- NoneVERSION 1.07Problems fixed:- RlmtMode parameter value strings were wrong (#10437)- Driver sent too many RLMT frames (#10439)- Driver did not recognize network segmentation (#10440)- RLMT switched too often on segmented network (#10441)Known limitations:- NoneVERSION 1.06Problems fixed:- System panic'ed after some time when running with RlmtMode=CheckOtherLink or RlmtMode=CheckSeg (#10421) Panic message: "Kernel panic: skput: over ... dev: eth0"- Driver did not switch back to default port when connected back-to-back (#10422).Changes:- RlmtMode parameter names have changedNew features:- There is now a version for ALPHA processorsKnown limitations:- NoneVERSION 1.05Problems fixed:- Driver failed to load on kernels with version information for module symbols enabledKnown limitations:- NoneVERSION 1.04Problems fixed:- Large frame support does work now (no autonegotiation support for large frames, just manually selectable)New Features:- Receive checksumming in hardware- Performance optimizations Some numbers (on two PII-400 machines, back-to-back): netpipe: 300 MBit/sec, with large frames: 470 MBit/sec ttcp: 38 MByte/sec, with large frames: 60 MByte/sec ttcp (UDP send): 66 MByte/sec, with large frames: 106 MByte/secKnown limitations:- NoneVERSION 1.03Problems fixed:- Unloading with "rmmod" caused segmentation fault (#10415)- The link LED flickered from time to time, if no link was established (#10402)- Installation problems with RedHat 6.0 (#10409)New Features:- Connection state ouput at "network connection up"Known limitations:- NoneVERSION 1.02Problems fixed:- Failed with multiple adapters- Failed with Single Port adapters- Startup string was only displayed if adapter found- No link could be established on certain switches when the switches were rebooted. (#10377)Known limitations:- Segmentation fault at "rmmod" with kernel 2.2.3 on some machinesVERSION 1.01Problems fixed:- Sensor status was not set back to 'ok' after 'warning/error'. (#10386)Changes:- improved parallelism in driverVERSION 1.00Known limitations:- not tested with all kernel versions (I don't have that much time :-)- only x86 version available (if you need others, ask for it)- source code not completely available***End of Readme File***
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -