Hotplugging

 
Thread Tools Search this Thread
Operating Systems Linux SuSE Hotplugging
# 1  
Old 01-29-2004
Hotplugging

Hi there,

Im having a problem with Linux setting up my Wireless USB card. When i start up in details that the it successfully detected my card but then a few lines later it says something like "eth0" failed to initialize and this somehow is connected with how the USB operates.

My laptop already has known problems with power management and i don't know if that is connected with the USB problem. the Board is ACPI.

By the way im running SusE 9.0 Linuw Professional.
My laptop is an Averatec 3150P.

Any help with how to get the USB working would be appreciated.
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
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)