Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 44344 - orinoco card gives "Unknown information frame received (type f202)" with some APs and WEP
Summary: orinoco card gives "Unknown information frame received (type f202)" with some...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Mobile Herd (OBSOLETE)
Depends on:
Blocks: 68964
  Show dependency tree
Reported: 2004-03-11 04:42 UTC by jochen
Modified: 2005-05-21 14:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

extracted patch from above mails (pcmcia-cs-orinoco_cs.patch,563 bytes, patch)
2004-03-11 05:00 UTC, jochen
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description jochen 2004-03-11 04:42:43 UTC
my orinoco gold card gives above error message when I try to use it with an Agere Access point with WEP enabled.

It's a known problem, this thread gives a good summary on it:

The patch proposed on

works for me (and doesn't break operation on other access points... for me)

I'd like to request inclusion of above patch

Reproducible: Always
Steps to Reproduce:
Comment 1 jochen 2004-03-11 05:00:41 UTC
Created attachment 27198 [details, diff]
extracted patch from above mails

this is the patch I'm using in my local ebuild
Comment 2 jochen 2004-09-02 05:12:50 UTC
Comment 3 Henrik Brix Andersen 2004-09-02 05:21:57 UTC
Please check if the stand-alone orinoco driver fixes this (should be fixed in 0.14 according to ChangeLog).

The stand-alone orinoco ebuild can be found on bug #32737.
Comment 4 jochen 2004-09-02 05:41:18 UTC
I will test this this weekend
Comment 5 jochen 2004-09-06 00:43:42 UTC
that ebuild doesn't compile. actually, it doesn't correctly unpack and/or configure as well.

Unluckily I was in a hurry this weekend, so I didn't find the time to dig into the problem....
Comment 6 Henrik Brix Andersen 2004-11-01 04:35:53 UTC
The stand-alone orinoco driver has been added to portage as net-wireless/orinoco. Please re-test.
Comment 7 Henrik Brix Andersen 2004-11-01 05:31:15 UTC
This bug report is awaiting feedback from the reporter.
Comment 8 jochen 2004-11-01 05:41:40 UTC
hey, not so fast! I will test the new ebuild next weekend, when I have access to that netgear ap again
Comment 9 Henrik Brix Andersen 2004-11-01 06:13:39 UTC
Thanks. Please attach your results to this bug report.
Comment 10 jochen 2004-11-02 10:50:35 UTC
I compiled the new orinoco ebuild (with pcmcia use-flag) and tried to test it, however when inserting the card, all I received was an oops (process cardmgr, access to addr 0x32, I don't have the oops in my logs and didn't feel like writing it down myself)

I thought maybe this is because of the pcmcia_cs modules with the same name, so I moved them away. When inserting the card again I got the "foo does not match" error mentioned in the FAQ. The FAQ suggested to set the pcmcia_cs variable correctly... however, since I have the pcmcia useflag i thought the ebuild did that itself.

five oopses and ten reboots later I removed the orinoco ebuild again, put the pcmcia modules back in place, and let you know this :-)
Comment 11 jochen 2004-11-03 04:01:02 UTC
See bug #69929 for the errors I described above

will test as soon as they are fixed
Comment 12 jochen 2004-11-06 05:44:26 UTC
ok, I compiled the module myself and tested it. Due to the nice new AP scan feature, I could verify that the card actually sees the access point, however I could not associate to the access point, i.e. no matter whether i used the /etc/init.d/net.eth1 script or iwconfig ... I could not connect to the access point.

nothing in the syslog either...

with the pcmcia-cs orinoco module (0.13e) I can connect without problems (after applying the patch ofcourse :)
Comment 13 Henrik Brix Andersen 2005-04-25 05:16:50 UTC
Reporter, please check if sys-apps/pcmcia-3.2.8 fixes this issue.
Comment 14 Henrik Brix Andersen 2005-05-21 14:20:07 UTC
Closing due to lack of feedback.