Bug 21802
Summary: | Problems with Xircom adapter | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Sammy <umar> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | CC: | david.crim, oolong, twaugh |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-10 18:49:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sammy
2000-12-06 14:52:52 UTC
The card is Xircom CBE2-100 I have been playing around with a Xircom CBEM56G under RedHat 7.2. This laptop used to work great under RedHat 6.2. It has always had problems with newer releases unless I rebuilt the kernel with an old PCMCIA driver set from the 6.2 days. Recently I am having some success with a 2.4.9-21 kernel if I do the following: 1) shut down networking (service network stop) 2) remove the xircom_cb module (modprobe -r xircom_cb) 3) add the xircom_tulip_cb module (modprobe xircom_tulip_cb) 4) restart networking (service network start) I have a script in /etc/init.d which does just this. Using netperf perfomance went form < 20 Mbits/sec to > 75 Mbits/sec. My question is, how is this selection supposed to be made without resorting to a seperate init.d script? I have tried changing the /etc/pcmcia/config file with no luck. I also saw references to hotplug. I saw that xircom_tulip_cb was in /etc/hotplug/blacklist. I removed it and inserted xircom_cb in it's place. This got me no xircom module loaded at all until I did it manually. OK, I saw another xircom thread that mentioned using an "alias eth0 xircom_tulib_cb" entry in /etc/modules.conf. This has eliminated the need to run an init.d script. xircom_tulip_cb now handles this not quite tulip hw fine |