D-Link 802.11 Wireless Lan card on Powerbook

[Bernard mentink]

Hi Neill,

I have managed to get as far as getting the prism2 driver loaded which 
results is a wlan0 device present.
(I found the correct PPC memory settings for config.opts in the 
PCMCIA.HOWTO in the source directory)

Now that I have a device, how do I get it up and running (or is it?) 
ifup doesn't see it as a device, and here is the result from
ifconfig:

wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

According to the above, it is not running (no UP), and no hardware address?

My /var/log/messages when bringing pcmcia up is:

-------------------------------------------------------------
Nov 11 19:05:10 localhost kernel: Linux Kernel Card Services 3.1.22
Nov 11 19:05:10 localhost kernel:   options:  [pci] [cardbus] [pm]
Nov 11 19:05:10 localhost kernel: Intel PCIC probe: not found.
Nov 11 19:05:10 localhost kernel: resource conflict with: 
90000000..9fffffff (1200), name: PCI CardBus #11
Nov 11 19:05:10 localhost kernel: resource conflict with: 
f3000000..f33fffff (200), name: PCI CardBus #11
Nov 11 19:05:10 localhost kernel: resource conflict with: 1000..8fff 
(100), name: PCI CardBus #11
Nov 11 19:05:10 localhost kernel: resource conflict with: 9000..90ff 
(100), name: PCI CardBus #11
Nov 11 19:05:10 localhost kernel: Yenta IRQ list 0000, PCI irq58
Nov 11 19:05:10 localhost kernel: Socket status: 30000810
Nov 11 19:05:10 localhost cardmgr[2065]: watching 1 sockets
Nov 11 19:05:10 localhost cardmgr[2066]: starting, version is 3.2.3
Nov 11 19:05:10 localhost kernel: cs: memory probe 
0x80000000-0x80ffffff: excluding 0x80000000-0x800fffff
Nov 11 19:05:10 localhost cardmgr[2066]: socket 0: D-Link DWL-650 11 
Mbps Wireless LAN card
Nov 11 19:05:11 localhost cardmgr[2066]: executing: 'modprobe prism2_cs '
Nov 11 19:05:11 localhost kernel: init_module: prism2_cs.o: 0.1.16-pre5 
Loaded
Nov 11 19:05:11 localhost kernel: init_module: dev_info is: prism2_cs
Nov 11 19:05:11 localhost kernel: prism2_cs: index 0x01: Vcc 3.3, irq 
58, io 0x0100-0x013f
Nov 11 19:05:11 localhost cardmgr[2066]: executing: './network start wlan0'
Nov 11 19:05:11 localhost modprobe: modprobe: Can't locate module net-pf-4
Nov 11 19:05:11 localhost /etc/hotplug/net.agent: invoke ifup wlan0
Nov 11 19:05:29 localhost kernel: eth0: switching to forced 100bt

What is the module net-pf-4 it can not find, is this my problem?

How do I tell if everything is working (at least as far as having the 
interface working correctly.

Last question: In wireless.opts, what option settings should I use. I am 
confused about this file, as there is a multiple of
devices there, and they are all have sections enabled.

Cheers,
Bernie.


Neill Miller wrote:

>On Sat, 09 Nov 2002 11:35:18 +1300
>Bernard mentink <ebike@paradise.net.nz> wrote:
>
>>Thanks for your config.opts file. I did try it, but unfortunatly got a
>>
>>kernel oops with those settings. One of the memory ranges seems to be 
>>the problem. error message on insertion of card is:
>>
>
>In my experience, if you don't boot with the card in, chances of getting
>the card to work are slim (for x86 too).  I haven't spent any time
>looking into this, as it's not that a big of a deal to me.  There's
>probably a way around that.
>
>I also just realized that I sent you the wrong config.opts file. :-{
>
>My current PPC installation is not actually working on the wireless
>network (nor can I test it since I don't have wireless at home).
>
>>By the way, what config settings did you use for your Orinoco card?
>>
>
>I'm not sure what you mean here.  I usually boot up, login as root; run
>/etc/init.d/pcmcia start; and run dhcpcd eth1; and it just works
>(assuming you have all the kernel support you need).
>
>The only change I recall making to any of the pcmcia config files were
>the memory ranges in the config.opts file.  This was documented
>somewhere (probably the official pages), but I can't recall where.  I'll
>look around for that...
>
>Best regards,
>-Neill.
>