URGENT HELP ON PCMCIA!
sroy at broadcom.com
Fri Dec 17 16:48:19 EST 2004
Thank you for the additional information. I will dig into it to see what could be wrong in config....any suggestion for the probable causes and areas I need to check?
From: Roar Bjørgum Rotvik [mailto:roarbr at tihlde.org]
Sent: Friday, December 17, 2004 12:20 PM
To: Santanu Roy
Cc: linux-pcmcia at lists.infradead.org
Subject: Re: URGENT HELP ON PCMCIA!
Santanu Roy wrote:
> Here is the output from /var/log/messages:
> Feb 29 08:59:52 173 cardmgr: watching 2 sockets
> Feb 29 08:59:52 173 cardmgr: starting, version is 3.1.34 Feb 29
> 08:59:52 173 cardmgr: unsupported card in socket 1
> Feb 29 08:59:52 173 cardmgr: product info: "Broadcom", "802.11b
> SC 3.3V CF", "4.2"
> Feb 29 08:59:52 173 cardmgr: manfid: 0x02d0, 0x044d function: 6
> Feb 29 09:05:54 173 insmod: Note: /etc/modules.conf is more recent
> than /lib/modules/2.4.20_mvl31-compulab_armcore/modules.dep
> If wl.o is not getting loaded, why would it be a driver issue?
As you have been told, this indicates a configuration problem: "08:59:52 173 cardmgr: unsupported card in socket 1" cardmgr does not recognize this card, i.e. has no config data about this
Cardmgr uses /etc/pcmcia/config to identify PCMCIA/PC Card manfid and
connect this to a driver.
Here you need to tell cardmgr that manfid: 0x02d0, 0x044d (product ID)
is bound to a certain driver "wl.o". See /etc/pcmcia/config for examples
on how to do this (notice that you will probably need to entries to this
file, one in the start to describe the card ("network") and one entry to
bind manfid,prodid to driver "wl.o").
Then cardmgr should be able to automatic load the driver on card
But you also have a problem when manually loading the module, and you
need to solve this problem first..
Roar B. Rotvik
More information about the linux-pcmcia