prism2_config() failed... (Consulted FAQ's and Mailing archive but still could not resolve)

Fawad Nazir fawad.nazir
Thu May 18 01:41:57 PDT 2006


On 5/17/06, Bryan Kadzban <bryan at kadzban.is-a-geek.net> wrote:
> Fawad Nazir wrote:
> > On 5/17/06, Bryan Kadzban <bryan at kadzban.is-a-geek.net> wrote:
> >
> >> blacklist orinoco_cs
> >> blacklist orinoco
> >
> >
> > Thanks, i have done that. Now i dont get these warning, but still the
> > problems with my hostap_cs driver are there as i mentioned in my
> > previous email.
> > Any idea, what could cause the problem?
>
> If orinoco_cs and orinoco are not loading anymore, then no, I don't have
> any ideas (I've done very little with wpa_supplicant on Linux).  :-(

Actually I think you are right orinoco_cs and orinoco driver do get
loaded. /etc/modprobe.h/blacklist file does not help when ever we use
hotplug. For hotplug i think Ubuntu has /etc/hotplug/blacklist, this
also does not work.

Finally after trying everything, not to load orinoco_cs and orinoco
driver. I finally gave up and deleted these files.

Now i think the thing are working for me, but i still now sure.

Please have a look at the dmesg message after i plug in my PCMCIA card:

fawad at nicta123:~$ dmesg
[4320001.754000] pccard: PCMCIA card inserted into slot 0
[4320001.754000] pcmcia: registering new device pcmcia0.0
[4320001.756000] hostap_cs: setting Vcc=33 (constant)
[4320001.756000] hostap_cs: setting Vcc=50 (from config)
[4320001.756000] Checking CFTABLE_ENTRY 0x01 (default 0x01)
[4320001.756000] IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
[4320001.756000] io->flags = 0x0046, io.base=0x0000, len=64
[4320001.758000] hostap_cs: Registered netdevice wifi0
[4320001.758000] wifi0: Interrupt, but dev not OK
[4320001.798000] hostap_cs: index 0x01: Vcc 5.0, irq 3, io 0xe100-0xe13f
[4320001.998000] prism2_hw_init: initialized in 200 ms
[4320001.999000] wifi0: NIC: id=0x800c v1.0.0
[4320001.999000] wifi0: PRI: id=0x15 v1.1.0
[4320001.999000] wifi0: STA: id=0x1f v1.4.9
[4320002.001000] wifi0: defaulting to bogus WDS frame as a workaround
for firmware bug in Host AP mode WDS
[4320002.007000] wifi0: registered netdevice wlan0


Does this shows everything is ok. There are few messages about which i
am a bit confused.
like:
[4320001.758000] wifi0: Interrupt, but dev not OK
and
[4320002.001000] wifi0: defaulting to bogus WDS frame as a workaround
for firmware bug in Host AP mode WDS

Please have a look, and let me know how can i fix these errors.


Thanks.
Fawad.
>
>


-- 
Fawad Nazir




More information about the Hostap mailing list