Kudos to Tom. Sorry I made it sound more difficult than it turned out to
be (patching the driver).
BTW, if you use NetworkManager to manage the connections it might be
easier to handle things like unplugging. It works better in 5.3, however,
than in 5.2.
Jerry
Chris Richmond wrote:
Well done...well done indeed. I am in your debt...
I installed it, rebooted, inserted the card. The eth1 hardware was there in
network admin, created a device and bound it to that and away it went
getting a second DHCP ip address on the network. Now to figure out how to
explicitly target "eth1" with software like ping or even a browser for
testing.
Thanks very much for your very expert insight and help with this problem. I
wish there was something I could give back to this community. At the very
least would it be ok for me to post your information/responses and a summary
of what was done in some other groups where I know some people had similar
problems?
Thanks,
Chris
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Tom Sightler
Sent: Thursday, March 05, 2009 11:49 AM
To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list
Subject: RE: [rhelv5-list] PCMCIA ethernet card on RHEL 5.2
On Thu, 2009-03-05 at 10:57 -1000, Chris Richmond wrote:
I inquired about using ndiswrapper and was told to avoid it if
possible..native if at all possible.
When you say a "customer driver" what do you mean?
That should have been "custom driver" as in, a slightly patched version
of the Redhat driver. Based on your other comments it sounds like this
is OK.
So, I've placed a very slightly patched version of the 8139too driver
from the latest RHEL5 kernel source package (2.6.18-128.1.1) at the
following URL:
http://www.tuxyturvy.com/files/8139too-pio.tar.gz
The only changes from the Redhat source was to add the
CONFIG_8139TOO_PIO to make the code compile with PIO support rather than
MMIO support. I've included the patch below.
To try this simply download the patch and extract it to a folder, make
sure you have the kernel-devel package installed that matches your
running kernel, switch to the extracted folder (should be called
8139too-pio) and type "make" and, assuming a successful build "make
install", then reboot and see if the driver will actually load and
recognize the hardware.
If you have problems building or installing the module feel free to
contact me offlist.
8139too.c.orig 2009-03-05 16:31:44.000000000 -0500
+++ 8139too.c 2009-03-05 16:38:56.000000000 -0500
@@ -121,6 +121,9 @@
/* enable PIO instead of MMIO, if CONFIG_8139TOO_PIO is selected */
+/* Force PIO MODE */
+#define CONFIG_8139TOO_PIO 1
+
#ifdef CONFIG_8139TOO_PIO
#define USE_IO_OPS 1
#endif
Later,
Tom
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
