Sponsored Content
Full Discussion: ins mod error on eth0
Top Forums UNIX for Dummies Questions & Answers ins mod error on eth0 Post 7001 by PxT on Monday 17th of September 2001 02:07:02 PM
Old 09-17-2001
cat /proc/interrupts

will show you the interrupts currently in use (if you are running Linux, which it sounds like you are).
 

2 More Discussions You Might Find Interesting

1. AIX

Excessive Page INs

Gurus, What does excessive Page Ins indicate for the memory status on the machine. Or, in another form, Reardless the OS, does excessive Page INs reflects memory shortage ? (6 Replies)
Discussion started by: Negm
6 Replies

2. UNIX for Dummies Questions & Answers

Running Built-ins in current shell

Hi, Can any one please describe why I am not able to run any built-in commands in current shell? Thanks. (5 Replies)
Discussion started by: siba.s.nayak
5 Replies
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)
All times are GMT -4. The time now is 05:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy