Login or Register to Ask a Question and Join Our Community


Cybersecurity

network card physical reset error

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Cybersecurity network card physical reset error
# 1  
Old 02-15-2002
network card physical reset error
Hi all

I am facing some problem with network card
i am using solaris8 and on sunultra10 .As it is my firewal machine i have got on backup harddisk for any emergency.

In one hardidsk while installation only hme0 interface was configured and in the backup hard disk qfe0/hme0 both are configured and now due to some problem i am puting the backup hard disk and trying to boot One error is coming like

there is no interface hme0
SW Hme0 phy reset error this message is coming continuously.
for qfe0 interface also the same mesage is coming.
But when i am putting the oringinal harddisk both the interfaces are succesfully configured.


please suggest.as i wan't the back disk to be used for some time.

waiting for ur suggestion.
thanks
PRAFUL
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Ubuntu

Error on network card

Hi Please can you help me to understand what could be wrong based on what I have captured in the logs: I have run cat /var/log/syslog | grep -i warn, and I got the following output NetworkManager: <warn> Activation (eth3) failed. Dec 23 10:58:25 cmoveldb02 NetworkManager: <warn> (eth3): DHCPv4... (2 Replies)
Discussion started by: fretagi
2 Replies

2. 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

3. Solaris

dependency require_all/none svc:/network/physical (maintenance)

I am using telnet instead of ssh because network/physical service is on maintenance mode. I can ping google and other internel machines. I can't ssh to this server because network/physical is dependency of ssh. How can I fix this service. I can use network service but it is maintenance mode.... (8 Replies)
Discussion started by: getrue
8 Replies

4. Solaris

svc:/network/physical:default: Method "/lib/svc/method/net-physical" failed with exit status 96. [ n

After a memory upgrade all network interfaces are misconfigued. How do i resolve this issue. Below are some out puts.thanks. ifconfig: plumb: SIOCLIFADDIF: eg000g0:2: no such interface # ifconfig eg1000g0:2 plumb ifconfig: plumb: SIOCLIFADDIF: eg1000g0:2: no such interface # ifconfig... (2 Replies)
Discussion started by: andersonedouard
2 Replies

5. Solaris

Network interface statistic reset

Hi, all! Can anybody tell me how can I reset network statistic, which could be seen by command 'netstat -i' or 'dladm show-dev -s'? Thank you for advance Christian (2 Replies)
Discussion started by: Inventor
2 Replies

6. 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

7. Solaris

[need help] error after configure network card at v890 sparc

hi experts, i have some problem with my server v890, i had config the network with ce0,ce1 and eri0 but after reboot the server have this error messages display : WARNING: ce0: fault detected external to device; service degraded WARNING: ce0: xcvr addr:0x01 - link down configuring IPv4... (2 Replies)
Discussion started by: bucci
2 Replies

8. Solaris

Testing physical network connection

How do you test the physical network connection of an interface in solaris. I know that if you have an active connection and the cable gets yanked, you can look in the messages file to check for link failure messages. But is there any better way to see if you have good layer 2 connectivity? (1 Reply)
Discussion started by: tjlst15
1 Replies

9. 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

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 REDHAT

axnet_cs

AXNET_CS(4)						     Kernel Interfaces Manual						       AXNET_CS(4)

NAME

       axnet_cs - Asix AX88190 chipset PCMCIA Ethernet Driver

SYNOPSIS

       insmod axnet_cs.o [pc_debug=n] [irq_list=i,j,...]

DESCRIPTION

       Axnet_cs  is  a driver for PCMCIA ethernet cards based on the Asix AX88190 chipset.  These cards are mostly NE2000 compatible but have sev-
       eral bugs that are sufficiently tricky to work around that a separate driver was deemed necessary.  When this driver is bound to a card, it
       allocates  the  next  available	ethernet  device (eth0..eth#).	This device name will be reported in the kernel log file, and passed on to
       cardmgr(8).

PARAMETERS

       pc_debug=n
	      Selects the PCMCIA debugging level.  This parameter is only available if the module is compiled with debugging enabled.  A  non-zero
	      value enables debugging.

       irq_list=i,j,...
	      Specifies the set of interrupts that may be allocated by this driver.

DIAGNOSTICS

       axnet_cs: this is not an AX88190 card!
	      Indicates that this card is probably a normal NE2000 compatible card, which requires the pcnet_cs driver.

       eth#: interrupt(s) dropped!
	      Indicates that the driver did not receive an interrupt notification for some reason.  The driver will poll the card (with a signifi-
	      cant performance penalty) if the problem persists.  The most likely cause is an interrupt conflict and/or host bridge  configuration
	      problem.

AUTHOR

       David Hinds - dahinds@users.sourceforge.net

SEE ALSO

       cardmgr(8), pcmcia(5).

pcmcia-cs							2001/08/17 12:51:58						       AXNET_CS(4)