Bug 64811
Summary: | Error message on ifup with Orinoco driver | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Matthew Saltzman <mjs> |
Component: | kernel-pcmcia-cs | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | notting |
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-09-22 04:29:51 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
Matthew Saltzman
2002-05-13 04:13:03 UTC
Bill: do you have any idea where this is comming from? It's coming when the wireless tools set the parameters; it's either a driver bug or a tools bug. I am seeing a slightly different problem (but maybe related?) with the Orinoco driver. On a Dell C400 with TrueMobile builtin wireless, I get eth1: Tx error, status 1 (FID=0135) (where the FID varies). These errors only appear occasionally, but once in a while (after a couple of hours of operation) the card even hangs and I have to bring the interface down and up again. In addition, on my desktop machine, which has a Orinoco PCMCIA card via a PCI-to-PCMCIA adapter, I get (in addition to the above error) occassionally a eth2: error -5 reading frame header. Frame dropped. I replaced the orinoco-related modules that came with the kernel rpm for 2.4.18-3 by the newer driver version 0.12a that can be obtained from http://ozlabs.org/people/dgibson/dldwd/orinoco-0.12a.tar.gz (This is the download site of the author of the driver.) This fixed the problems that I saw earlier. NB: The Makefile included in the orinoco tar ball may be used to compile the driver modules without the need to recompile the kernel (the kernel source rpm has to be installed, of course). Also happens with the wavelan_cs driver. I had configured the orinoco driver by hand, but when I ran through the standard setup procedure, it selected the wavelan_cs driver. Using it produces the same message as originally reported with the orinoco driver. I conclude that either the two drivers share the same code or the bug is tool-related rather than driver-related. Same thing happens in latest Phoebe beta. I used orinoco-0.13 and then it works. I got several insmod errors when trying to load orinoco. /Richard In fact, currently in Psyche (and I don't know exactly what changed between my last post and now): [mjs@paladin mjs]$ ifup eth1 Error for wireless request "Set Mode" (8B06) : SET failed on device eth1 ; Invalid argument. Error for wireless request "Set Frequency" (8B04) : SET failed on device eth1 ; Operation not supported. Determining IP information for eth1... done. I get the same problem with RH9. When i try to make orinoco 0.13e i get this error: make -C /lib/modules/2.4.20-8/build SUBDIRS=/root/orinoco-0.13e modules make: *** /lib/modules/2.4.20-8/build: No such file or directory. Stop. make: *** [modules] Error 2 what's the problem? Do you have kernel-source installed? Hi, again, sorry but I am having trouble installing the kernel source. I gunzipped and untarred my kernel source (2.4.2) into /usr/src/linux-2.4.2 and made a symbolic link with linux to linux-2.4.2 but when I run the make for orinco-0.13e i still get the same error. NM, I got it to work after installing 0.13e. It also appears that Psyche does not support wireless encryption? (I had to disable it to get it to work). I had no problem with wireless encryption in Psyche (but I'm up to Shrike on that system now). There are some issues with string keys vs hex keys that appear elsewhere in Bugzilla and have been fixed in the latest redhat-config-network. That's kind of OT for this bug, though. OK, closing as fixed in the current beta snapshots. |