Login or Register to Ask a Question and Join Our Community


SCO

Problems with network card in SCO

 
Thread Tools Search this Thread
Operating Systems SCO Problems with network card in SCO
Prev   Next
# 1  
Old 12-16-2009
Problems with network card in SCO
hello, i am new to unix and need support</SPAN></SPAN>
</SPAN></SPAN>The problem is:
I have a SCO 5.0.5 server, and has no local network access, I think my problem are the drivers for network card.
my network card is Kingston EtheRx PCI Fast Ethernet Adapter KNE120TX and already installed the drivers, but when I run:
# hwconfig-h the result that describes the network card is:
ktcHT 0xd400-0xd41f - - Kingston Et ....... NOT FOUND [KNE120TX]

reinstall the drivers and the network connection, but does not work
when setting up the network connection, save with default values:
Bus = 0
Device = 0
Function = 0
this can cause any conflict?
if this is wrong, what are the correct values?
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Regarding Network Interface Card

Dear All , While taking backups in one Linux Server , we find one alert came with regard to Network Interface Card. Pl find the below alert. Network Interface Card performance for NIC:eth1 has exceeded Major threshold. Bytes sent and received per second (Average)= 105540.303101... (6 Replies)
Discussion started by: jegaraman
6 Replies

2. Solaris

Network Card Name details

Hi All, Can somebody explain that whats the meaning of different interfaces naming scheme, Like ' hme, qfe, e1000g0, ce, eri, bge' ? This is such a basic question which i always overlooked :( Thanks ! (6 Replies)
Discussion started by: Solarister
6 Replies

3. SCO

network problems with sco

SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that. thanks (8 Replies)
Discussion started by: ajantha
8 Replies

4. Solaris

How to identifying the network card ?

Hi Experts, Can we use some command from unix to find the available network interface? I did tried Its listing following, however how can I decide the which vender card is attached e.g. if its hme , bge or some thing else Thanks (7 Replies)
Discussion started by: kumarmani
7 Replies

5. UNIX for Dummies Questions & Answers

How can I tell which network card is which?

I have three network cards in my unix box. I need to figure out which card corresponds to an assigned IP address. If there some command in unix I can use to make an ethernet interface blink? Any advice would be appreciated. (6 Replies)
Discussion started by: mojoman
6 Replies

6. SCO

3c905b network card problem with SCO 5.0.5

Hi, I was wondering if anyone could help me out with this problem. I have SCO 5.0.5 installed on a system that I am using 3c905b (3 Com) network card. This system is always powered on. After no certain time period this NIC doesn't work. I can't ping to this system from any other machine or vice... (2 Replies)
Discussion started by: AtALoss
2 Replies

7. UNIX for Dummies Questions & Answers

Network card and internet

Hi!. I have problems installing my network card under ther redhat kernel. First i tryed my integrated intel pro set 10/100 then my d-link 530tx Pci but none of them seems to be found. also i huse my network card to connect to the net trough PPPOE where i need to type my username and... (3 Replies)
Discussion started by: Gibbler
3 Replies

8. UNIX for Advanced & Expert Users

Network Card Help

I have been having trouble with my sis900 neytwork card in slacwkare linux. I tried to modprobe the sis900, it didnt give me any errors but it didnt load it. so I put in a realtek 8139 network card and tried it too. These are the errors i get with the two cards when trying to do insmod on either of... (3 Replies)
Discussion started by: The Fridgerator
3 Replies

9. IP Networking

Network Card with SGI

The Octane is driving me nuts . It was sitting on the network doing its job nicely and i had to pull the n/w cable out from the wall to pull it from the inside of the table and connected it again . The logs show this -- link down .... < when i pulled it out > link ok < when i connected > But... (0 Replies)
Discussion started by: DPAI
0 Replies

10. IP Networking

network card

I have a UnixWare 2 server that has an ISA 3Com NIC that has just a BNC connector on it. I want to remove this and install an ISA 3Com NIC that has a BNC/RJ45 connector. What steps do I have to go through to successfully complete this? Thye are almost the exact same cards except for the... (1 Reply)
Discussion started by: cparks
1 Replies
Login or Register to Ask a Question

LEARN ABOUT NETBSD

rump_sp

RUMP_SP(7)					       BSD Miscellaneous Information Manual						RUMP_SP(7)

NAME

     rump_sp -- rump remote system call support

DESCRIPTION

     The rump_sp facility allows clients to attach to a rump kernel server over a socket and perform system calls.  While making a local rump sys-
     tem call is faster than calling the host kernel, a remote system call over a socket is slower.  This facility is therefore meant mostly for
     operations which are not performance critical, such as configuration of a rump kernel server.

   Clients
     The NetBSD base system comes with multiple preinstalled clients which can be used to configure a rump kernel and request diagnostic informa-
     tion.  These clients run as hybrids partially in the host system and partially against the rump kernel.  For example, network-related clients
     will typically avoid making any file system related system calls against the rump kernel, since it is not guaranteed that a rump network
     server has file system support.  Another example is DNS: since a rump server very rarely has a DNS service configured, host networking is
     used to do DNS lookups.

     Some examples of clients include rump.ifconfig which configures interfaces, rump.sysctl which is used to access the sysctl(7) namespace and
     rump.traceroute which is used to display a network trace starting from the rump kernel.

     Also, almost any unmodified dynamically linked application (for example telnet(1) or ls(1)) can be used as a rump kernel client with the help
     of system call hijacking.	See rumphijack(3) for more information.

   Connecting to the server
     A remote rump server is specified using an URL.  Currently two types of URLs are supported: TCP and local domain sockets.	The TCP URL is of
     the format tcp://ip.address:port/ and the local domain URL is unix://path.  The latter can accept relative or absolute paths.  Note that
     absolute paths require three leading slashes.

     To preserve the standard usage of the rump clients' counterparts the environment variable RUMP_SERVER is used to specify the server URL.  To
     keep track of which rump kernel the current shell is using, modifying the shell prompt is recommended -- this is analoguous to the visual
     clue you have when you login from one machine to another.

   Client credentials and access control
     The current scheme gives all connecting clients root credentials.	It is recommended to take precautions which prevent unauthorized access.
     For a unix domain socket it is enough to prevent access to the socket using file system permissions.  For TCP/IP sockets the only available
     means is to prevent network access to the socket with the use of firewalls.  More fine-grained access control based on cryptographic creden-
     tials may be implemented at a future date.

EXAMPLES

     Get a list of file systems supported by a rump kernel server (in case that particular server does not support file systems, an error will be
     returned):

	   $ env RUMP_SERVER=unix://sock rump.sysctl vfs.generic.fstypes

SEE ALSO

     rump_server(1), rump(3), rumpclient(3), rumphijack(3)

HISTORY

     rump_sp first appeared in NetBSD 6.0.

BSD
								 February 7, 2011							       BSD