Baslinux mailing list

[sindi keesan <keesan AT sdf.lonestar.org>]

Joel, I am sending you a copy of this in case you have left the BL list, 
because it pertains to your puzzling problem with WPC11 and orinoco_cs for 
wireless.  What model laptop did you try this in?  The card worked for me 
in one computer but not in another (where it had unresolved symbols).

On Sun, 17 Dec 2006, sindi keesan wrote:

> I have a 100Mhz and a 266MHz Toshiba laptop.   The latter will not insert
> 2.4.31 wireless modules for at least airo and orinoco cards (unresolved
> symbols).

The 2.4.31 orinoco modules work in the 100MHz Toshiba.  (2.2.26 insert but 
then segfault).

>  How do I compile mwavelan_cs.o (an improved wavelan2_cs.o which should
> work with iwconfig and iwspy) from the pcmcia source code (used to
> compile all the pcmcia modules)?  Do I unpackage it in the pcmcia
> directory, and if so, do I make all again or can I make just one module?

A search on orinoco_cs.o and unresolved symbol and WPC11 got two hits, one 
for BL3 with Steven's answer.  (There were 220 hits for orinoco_cs.o and 
unresolved symbol, many for Lucent Orinoco Gold).

This pertains to an older BL3, with kernel 2.2.16, but has similar 
problems to my 2.4.31 modules. 2.2.26 does insert the modules but then 
segfaults.  I have not yet tried 2.2.16 with orinoco.


> From BL3 archives:

   Joel Adria [4]AspenDr at telus.net
   Sat Oct 30 15:40:25 EDT 2004


Here's what I have now. I downloaded some pre-compiled drivers (orinoco.o,
orinoco_cs.o, hermes.o) and then edit "conf" in the /etc/pcmcia directory to
point to those drivers. I copied the instructions from a site,
[11]http://linux.oldcrank.com/tips/wpc11/ and went from there. When I run
"start" it gets everything going. It runs the three .o files, makes a high
pitched sound, then pauses for second, and says the last line. The readout
is here:

Oct 30 13:28:19 cardmgr[35]: socket 1: Network Card
Oct 30 13:28:19 cardmgr[35]: executing: 'insmod /lib/modules/2.2.16
/pcmcia/hermes.o'
Oct 30 13:28:19 cardmgr[35]: + Using /lib/modules/2.2.16/pcmcia/hermes.o
Oct 30 13:28:19 cardmgr[35]: executing: 'insmod /lib/modules/2.2.16
/pcmcia/orinoco.o'
Oct 30 13:28:20 cardmgr[35]: + Using /lib/modules/2.2.16/pcmcia/orinoco.o
Oct 30 13:28:20 cardmgr[35]: + insmod: unresolved symbol alloc_etherdev
Oct 30 13:28:20 cardmgr[35]: + insmod: unresolved symbol cpu_raise_softirq
Oct 30 13:28:20 cardmgr[35]: + insmod: unresolved symbol __out_of_line_bug
Oct 30 13:28:20 cardmgr[35]: + insmod: unresolved symbol schedule_task

[I got only ONE unresolved symbol with kernel 2.4.31, and no unresolved 
symbols with 2.2.26 but it then segfaulted]

[deleted lots of this - orinoco_cs tried but would not insert either 
because it needs orinoco.o, so lots more unresolved symbols].

Oct 30 13:28:20 cardmgr[35]: modprobe exited with status 127
Oct 30 13:28:21 cardmgr[35]: get dev info on socket 1 failed: Try again

Alot of crap, I know, but anybody can interpret it, that would be great.

-Joel

   1. https://lists.ibiblio.org/sympa/arc/baslinux/2004-October/index.html
   2. https://lists.ibiblio.org/sympa/arc/baslinux/2004-October/005560.html


Steven's answer:

Joel Adria wrote:
> Here's what I have now. I downloaded some pre-compliled
> drivers (orinoco.o, orinoco_cs.o, hermes.o)

Were they compiled for the 2.2.16 kernel?

[They must have been, because when I used the wrong version modules I got 
a spectacular crash, not the above messages.]

> and then edit "conf" in the /etc/pcmcia directory to
> point to those drivers. I copied the instructions from
> a site, [11]http://linux.oldcrank.com/tips/wpc11/ and went
> from there. When I run "start" it gets everything going.
>
> cardmgr[35]: socket 1: Network Card

It has successfully identified the card.

> cardmgr[35]: executing: 'insmod /lib/modules/2.2.16/pcmcia/hermes.o'
> cardmgr[35]: + Using /lib/modules/2.2.16/pcmcia/hermes.o

The hermes.o module installed.

> cardmgr[35]: executing: 'insmod /lib/modules/2.2.16/pcmcia/orinoco.o'
> cardmgr[35]: + Using /lib/modules/2.2.16/pcmcia/orinoco.o

The orinoco.o module installed

[To me it looks like it tried but failed to install it, but got unresolved 
symbols instead.  lsmod listed only hermes when I tried with 2.4.31]

> cardmgr[35]: + insmod: unresolved symbol alloc_etherdev
> cardmgr[35]: + insmod: unresolved symbol cpu_raise_softirq
> cardmgr[35]: + insmod: unresolved symbol __out_of_line_bug
> cardmgr[35]: + insmod: unresolved symbol schedule_task

That module is unhappy.  Three possibilities come to mind:
(1) it is dependent on another module which is not present;

[orinoco_cs.o won't install because orinoco.o won't install]

(2) it was compiled for a different kernel; or
[Not in my case]

(3) you're trying to install a wireless module on BL3 kernel

[I had the same problems with 2.4.31 on ONE of TWO Toshiba laptops.  The 
same setup worked perfectly on the other laptop.  The difference is 
hardware.  The modules all installed with 2.2.26 but then segfaulted.  I 
have not tried 2.2.16.]

> cardmgr[35]: executing: 'insmod /lib/modules/2.2.16/pcmcia/orinoco_cs.o'
> cardmgr[35]: + Using /lib/modules/2.2.16/pcmcia/orinoco_cs.o

The orinoco_cs.o module installed.
It too is unhappy.

[I think it TRIED to install but did not.  In my case it was not listed by 
lsmod either, since it needed orinoco.o which also did not install.]

> cardmgr[35]: + insmod: unresolved symbol __netdev_watchdog_up
> cardmgr[35]: + insmod: unresolved symbol cpu_raise_softirq

Kernel issues.

> cardmgr[35]: + insmod: unresolved symbol alloc_orinocodev
> cardmgr[35]: + insmod: unresolved symbol orinoco_reinit_firmware
> cardmgr[35]: + insmod: unresolved symbol orinoco_interrupt
> cardmgr[35]: + insmod: unresolved symbol __orinoco_down
> cardmgr[35]: + insmod: unresolved symbol __orinoco_up
> cardmgr[35]: + insmod: unresolved symbol softnet_data

Those look like issues related to the failure of the
previous orinoco module.  I think they might disappear
after the orinoco.o module goes in without error.

You are about halfway.  The card is identified and cardmgr
is trying to install the modules you specified.  Unfortunately
there is something wrong with those modules.  Wrong modules,
wrong kernel, whatever.  Once you get the modules right,
the installation should complete and you will hear the
second beep from cardmgr.

[In my case the something wrong appears to be hardware-related.  What 
worked perfectly on one computer with kernel 2.4.31 had unresolved symbols 
on the other.  Maybe he has the same laptop?]

Cheers,
Steven


References
   7. https://lists.ibiblio.org/sympa/arc/baslinux/2004-October/date.html#5563
   8. 
https://lists.ibiblio.org/sympa/arc/baslinux/2004-October/thread.html#5563