orinoco_cs does not work
Brought to you by:
dahinds
Menu
▾
▴
#329 orinoco_cs does not work
I insalled kernel 2.4.22 and pcmcia-cs 3.2.5.
I tried to use a WLAN-card from Lancom (AirLancer
MC-11 which is a OEM of Agere Model 0104) which
reports a firmware version 8.42.
At first attempt to access the network (dhclient ist
started) i get a couple 'Watchdog: ... transmit timed
out' and 'orinoco_lock() called with hw_unavailable'
messages.
As result the Network over WLan ist not useable.
I attached an excerpt of my syslog as result of following
procedure:
- start pcmcia
- insert WLan card
- extrct WLan card
- shutdown pcmcia
A cheap standard PCMCIA-network card is working well
in the same slot.
Syslog excerpt
Logged In: YES
user_id=7760
You may want to report to the orinoco maintainer.
It was your intent to configure your wireless card with
essid "public" using DHCP, right?
-- Dave
Logged In: YES
user_id=194627
Ok, i will report to the orinoco maintainer David Gibson (right
?).
The essid and dhcp was intended. If it runs successful it will
be changed.
regards
Petric
Logged In: YES
user_id=7760
Was there any resolution of this?
-- Dave
Logged In: YES
user_id=194627
No change nor fix.
See last mail in conversation with David Gibson:
------------------------ cut ------------------------
On Mon, Oct 13, 2003 at 06:53:51PM +0200, Petric Frank
wrote:
> Hello,
>
> On Monday 13 October 2003 04:03, you wrote:
> > On Fri, Oct 10, 2003 at 07:07:42PM +0200, Petric Frank
wrote:
> > > Hello,
> > >
> > > On Friday 10 October 2003 03:35, you wrote:
> > > > > could you please have a look at this bug report ?
>
> [...]
>
> > We're missing interrupts. This is probably a configuration
problem in
> > the pcmcia-cs layer.
>
> But why a standard (NE2000 compatible) PCMCIA-network
card works well in the
> same slot ?
> This card one does not miss interrupts. So i argue there
must be some special
> in the communication between orinoco and the pcmcia-cs
modules.
>
> Please let me know what i can do to analyze the real
problem point.
It's not at all obvious to me why, but it's certainly a fact
that
we're missing interrupts - the time out shows the card has
generated
an event, but clearly we haven't got an interrupt or we
wouldn't have
timed out. Since the interrupt dispatch is handled by the
pcmcia
layer below, the problem must lie there.
--
David Gibson | For every complex problem
there is a
david@gibson.dropbear.id.au | solution which is simple,
neat and
| wrong.
http://www.ozlabs.org/people/dgibson
------------------------ cut ------------------------
After that i expected that he contact you directly. Putting
me as relay in between does not make things better ...
regards
Petric
Logged In: YES
user_id=7760
Ok, what I would do is:
With the NE2000 card, verify that the same interrupt (irq
11) is used for that card, and that the interrupt increments
correctly (see that /proc/interrupts shows increasing counts
during network activity, and verify that you get no errors
in your system log).
I don't know enough about the orinoco cards to know if David
Gibson's explanation makes sense. Transmit timeouts do not
necessarily indicate interrupt delivery problems; but he
seems to be saying that (based on the register values in the
driver messages?) that the card did indeed try to trigger an
interrupt.
-- Dave
Logged In: YES
user_id=194627
Sorry, but i can't test this any more. The notebook have
been sold.
regards
Petric