Red Hat Bugzilla – Bug 129457
Adaptec Starfire QuadEthernet Problems
Last modified: 2015-01-04 17:08:36 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Description of problem:
My Adaptec Starfire QuadEthernet does not
work under Fedora Core 2, all kernels up to
If I try to put some traffic to the card,
all I get is
eth2: Something Wicked happened! 0x02018101.
(or similiar error codes, like 02010001 or 02019101)
Under FC1 (kernel 2.4.x, the same card just worked fine)!
Version-Release number of selected component (if applicable):
all FC2 kernels (2.6.x)
Steps to Reproduce:
1. Install FC2
2. ping to something connected by
the Starfire card
Actual Results: An error message "Something Wicked happened"
goes to /var/log/messages. (See above)
tcpdump shows no traffic on any device.
Expected Results: The card should operate as expected.
Using same setup, upgraded from FC1 to FC2
We have 10 starfire's, all of them exhibit the same issue.
Changing hardware does not resolve issues.
Cards generate the same reported issues and messages.
Interesting: when dumping traffic (TCPDUMP) all frames that should be
normal ip traffic are reported as unsupported ethernet type.
Really need the starfires to work, as the replacements (we also use
Intel 10/100/100 quads) do not work in non 3.3v pci slots.
Rein van Koten
I had the same issue with these kind of cards.
I still have this issue with FC3 and couldn't get the card work properly.
I see everything o.k. but I cannot send a single paket to the network.
My solutions is now to use freebsd and the card works there.
Hi, Can anyone tell me whether someone is working on this or if
there's some kind of solution? Maybe I've missed something but as far
as I know there's not yet a solution or even cause found...
Rein van Koten
I don't think anyone is. I contacted the people I could find in the
MAINTAINERS file and on the net and nobody responded. I gave up now
and replaced the card.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.