Re: difficulty w/ dwl-500/650


From: jason (rohwedde_at_codegrinder.com)
Date: 2002-04-01 03:05:43 UTC



well i had just build pcmcia-cs and the kernel together.. so i don't see where that message would be coming from..

all the modules and the utils have the same time.. at least that i can find..

hrm.. this is what i get if i try to use my lucent card

Mar 31 17:04:08 bucky cardmgr[450]: socket 0: Lucent Technologies WaveLAN/IEEE Adapter
Mar 31 17:04:08 bucky cardmgr[450]: executing: 'modprobe hermes' Mar 31 17:04:08 bucky kernel: hermes.c: 3 Oct 2001 David Gibson <hermes_at_gibson.dropbear.id.au>
Mar 31 17:04:08 bucky cardmgr[450]: executing: 'modprobe orinoco' Mar 31 17:04:08 bucky kernel: orinoco.c 0.08a (David Gibson <hermes_at_gibson.dropbear.id.au> and others) Mar 31 17:04:08 bucky cardmgr[450]: executing: 'modprobe orinoco_cs' Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: unresolved symbol orinoco_setup Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: unresolved symbol orinoco_shutdown Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: unresolved symbol orinoco_reset Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: unresolved symbol orinoco_proc_dev_cleanup
Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: unresolved symbol orinoco_interrupt Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: unresolved symbol orinoco_proc_dev_init
Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: insmod /lib/modules/2.4.17/pcmcia/orinoco_cs.o failed Mar 31 17:04:08 bucky cardmgr[450]: +
/lib/modules/2.4.17/pcmcia/orinoco_cs.o: insmod orinoco_cs failed Mar 31 17:04:08 bucky cardmgr[450]: modprobe exited with status 255

it seems to me like the bridge doesn't have a resource set properly.. but i could be wrong

-jason
----- Original Message -----
From: "Eric Johanson" <ericj_at_cubesearch.com> To: "jason" <rohwedde_at_codegrinder.com>
Cc: <hostap_at_lists.ssh.com>
Sent: Sunday, March 31, 2002 8:55 PM
Subject: Re: difficulty w/ dwl-500/650

> The only part of the dmesg output that looks fishy:
>
> > Mar 31 16:50:56 bucky kernel: prism2: CardServices release does not
> match!
>
> That makes me think you should rebuild pcmcia-cs & the kernel, or maybe
> the related utils (Don't recall the name; I've never seen this issue)
>
> hth.
> -Eric
>
>
> On Sun, 31 Mar 2002, jason wrote:
>
> > I saw something similar in the archives to this list .. but I'm having
> > problems getting the 650 to work through the 500 pci bridge.. i've tried
> > this in most every configuration i can think of but here's the current
one..
> >
> > any assistance would be appreciated
> >
> > -j
> >
> > 2.4.17 kernel
> > using pcmcia-cs-3.1.33 for pcmcia
> >
> > this is all on top of debian unstable w/o the pcmcia deb installed
> >
> > PCIC_OPTS="irq_mode=0"
> >
> > my wireless.opts
> >
> > include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff
> > include memory 0xc0000-0xfffff
> > include memory 0xfb000000-0xfbffffff, memory 0x60000000-0x60ffffff
> > # Extra port range for IBM Token Ring
> > include port 0xa00-0xaff
> > # Resources we should not use, even if they appear to be available
> > # First built-in serial port
> > exclude irq 4
> > # Second built-in serial port
> > #exclude irq 3
> > # First built-in parallel port
> > exclude irq 7
> >
> > the odd memory bit was required to get it to find the pci bridge
properly
> >
> > ### Error Message ####
> >
> > Starting PCMCIA services: modules cardmgr.
> > cardmgr[375]: watching 1 sockets
> > bucky:/var/log# Mar 31 16:50:55 bucky kernel: Linux PCMCIA Card Services
> > 3.1.33
> > Mar 31 16:50:55 bucky kernel: kernel build: 2.4.17 #3 SMP Sun Mar 31
> > 15:34:59 CST 2002
> > Mar 31 16:50:55 bucky kernel: options: [pci] [cardbus]
> > Mar 31 16:50:55 bucky kernel: Intel ISA/PCI/CardBus PCIC probe:
> > Mar 31 16:50:55 bucky kernel: PCI: Found IRQ 10 for device 00:0d.0
> > Mar 31 16:50:55 bucky kernel: Ricoh RL5C475 rev 80 PCI-to-CardBus at
slot
> > 00:0d, mem 0x10000000
> > Mar 31 16:50:55 bucky kernel: host opts [0]: [pci only] [io 3/6/1]
[mem
> > 3/6/1] [pci irq 10] [lat 32/176] [bus 3/6]
> > Mar 31 16:50:55 bucky kernel: PCI card interrupts, PCI status
changes
> > Mar 31 16:50:55 bucky cardmgr[375]: watching 1 sockets
> > Mar 31 16:50:55 bucky cardmgr[376]: starting, version is 3.1.33
> > Mar 31 16:50:56 bucky kernel: cs: memory probe 0xfb000000-0xfbffffff:
clean.
> > Mar 31 16:50:56 bucky cardmgr[376]: socket 0: D-Link DWL-650 11Mbps WLAN
> > Card
> > Mar 31 16:50:56 bucky cardmgr[376]: executing: 'modprobe prism2'
> > Mar 31 16:50:56 bucky kernel: prism2: prism2.c 0.0.0 2002-03-27 (SSH
> > Communications Security Corp, Jouni Malinen)
> > Mar 31 16:50:56 bucky kernel: prism2: (c) SSH Communications Security
Corp
> > <jkm_at_ssh.com>
> > Mar 31 16:50:56 bucky kernel: prism2: CardServices release does not
> match!
> > Mar 31 16:50:56 bucky cardmgr[376]: +
/lib/modules/2.4.17/pcmcia/prism2.o:
> > init_module: Operation not permitted
> > Mar 31 16:50:56 bucky cardmgr[376]: +
/lib/modules/2.4.17/pcmcia/prism2.o:
> > insmod /lib/modules/2.4.17/pcmcia/prism2.o failed
> > Mar 31 16:50:56 bucky cardmgr[376]: +
/lib/modules/2.4.17/pcmcia/prism2.o:
> > insmod prism2 failed
> > Mar 31 16:50:56 bucky cardmgr[376]: + Hint: insmod errors can be caused
by
> > incorrect module parameters, including invalid IO or IRQ parameters
> > Mar 31 16:50:56 bucky cardmgr[376]: modprobe exited with status 255
> > Mar 31 16:50:56 bucky cardmgr[376]: executing: 'insmod
> > /lib/modules/2.4.17/pcmcia/prism2.o'
> > Mar 31 16:50:56 bucky kernel: prism2: prism2.c 0.0.0 2002-03-27 (SSH
> > Communications Security Corp, Jouni Malinen)
> > Mar 31 16:50:56 bucky kernel: prism2: (c) SSH Communications Security
Corp
> > <jkm_at_ssh.com>
> > Mar 31 16:50:56 bucky kernel: prism2: CardServices release does not
match!
> > Mar 31 16:50:56 bucky cardmgr[376]: +
/lib/modules/2.4.17/pcmcia/prism2.o:
> > init_module: Operation not permitted
> > Mar 31 16:50:56 bucky cardmgr[376]: + Hint: insmod errors can be caused
by
> > incorrect module parameters, including invalid IO or IRQ parameters
> > Mar 31 16:50:56 bucky cardmgr[376]: insmod exited with status 1
> > Mar 31 16:50:57 bucky cardmgr[376]: get dev info on socket 0 failed:
> > Resource temporarily unavailable
> > Mar 31 16:50:57 bucky cardmgr[376]: wrong module 'prism2' for device
> > 'prism2'?
> >
> >
> >
> >
> >
> >
> >
> >
>
>



This archive was generated by hypermail 2.1.4.