Red Hat Bugzilla – Bug 36339
Can't establish ethernet connection with 2.2.19 kernel
Last modified: 2007-04-18 12:32:41 EDT
I've been using kernel-2.2.17-14 and have had no problems to set up
Ethernet connections with my Xircom CBEM56G PCMCIA card on a Dell Inspiron
Upgraded to kernel-2.2.19-7.0.1 this morning. The Xircom card is properly
configured, two happy beeps. The Ethernet connection is
being set up with identical ifconfig and routing tables as before. My
machine becomes pingable from the outside, but I can't get any connection
to anything from the inside. I can ping localhost, but that's it. The
gateway is not pingable.
My machine is 100% up-to-date with respect to the RedHat 7.0 upgrades.
Luckily, even though I have upgraded to all the new modules in the 2.2.19
kernel upgrade, when I run 2.2.17 instead, I do get a proper
Hm. Do you have any other pcmcia cards to test with?
(not a problem if you don't though)
2.2.19 is only critical if you have "hostile" local users. I'll investigate this
to see if we can fix this, but Xircom cards are very hard to get working ;)
No, I don't have any other pcmcia cards. No, I don't have any local users but
myself, so I'll just keep on using 2.2.17. I had no problem to configure my
system to use the Xircom card a year ago. And It has been performing just fine
through a couple of kernel upgrades, an upgrade to RedHat-7.0, and on the
2.2.17. You are not saying that I will have problems when I switch over to 7.1
For 7.1 (or the 2.4 kernel rather) I wrote a whole new Xircom driver which so
far works very well for everybody....
Thanks a lot!!!! I can't wait until I get my hands on 7.1 ... :^)
If you haven't got 7.1 yet: we put out a new 2.2.19 with the old xircom driver
in it yesterday.
I switched over to 7.1 the minute it came out.
However, as you know from my bug 37454, I'm still having problems with having to
do a cardctl eject followed by a cardctl insert each time I have done a ifdown
on the Ethernet card slot. Further, see my new comments for that bug.
So even if I'm gone from 2.2.19, your fix will work. Bug can be closed.