D-Link dwl-650 (J3) and Suse

Hey folks

I have been trying to work through a problem for a couple of days now and
have hit the wall. Can some one please point me in the right direction.

I am trying to get a D-Link dwl-650 (J3) working on my laptop (Compaq R3140)
but when I insert the card it gets recognized as memory. Anyway I have
tried shutting down PCMCIA support, loading the prism2_cs drivers,
restarting PCMCIA however can't seem to get access to the card. The card
does light up and is recognized under windows so I know it works just not
with Linux. Anyone that can help it will be most appreciated.

Dave

On Wed, 13 Apr 2005 11:34:59 -0400, Dave Waddling wrote:

> I have been trying to work through a problem for a couple of days now and
> have hit the wall. Can some one please point me in the right direction.
>
> I am trying to get a D-Link dwl-650 (J3) working on my laptop (Compaq R3140)
> but when I insert the card it gets recognized as memory. Anyway I have
> tried shutting down PCMCIA support, loading the prism2_cs drivers,
> restarting PCMCIA however can't seem to get access to the card. The card
> does light up and is recognized under windows so I know it works just not
> with Linux. Anyone that can help it will be most appreciated.

A "cardctl ident" will give some important information about your card...
The most important part is "manfid"

"grep -r <?x???, ?x???> /etc/pcmcia" will tell if another driver claims
ownership. Delete, (or comment out), this entry.

At the buttom of /etc/pcmcia/wlan-ng.conf; make an entry for your card's
manfid.

--
Regards/Med vennlig hilsen
Joachim Mæland
If everything seems under control, you're just not going fast enough.
-Mario Andretti

Joachim Mæland wrote:

> On Wed, 13 Apr 2005 11:34:59 -0400, Dave Waddling wrote:
>
>> I have been trying to work through a problem for a couple of days now and
>> have hit the wall. Can some one please point me in the right direction.
>>
>> I am trying to get a D-Link dwl-650 (J3) working on my laptop (Compaq
>> R3140) but when I insert the card it gets recognized as memory. Anyway I
>> have tried shutting down PCMCIA support, loading the prism2_cs drivers,
>> restarting PCMCIA however can't seem to get access to the card. The card
>> does light up and is recognized under windows so I know it works just not
>> with Linux. Anyone that can help it will be most appreciated.
>
> A "cardctl ident" will give some important information about your card...
> The most important part is "manfid"
>
> "grep -r <?x???, ?x???> /etc/pcmcia" will tell if another driver claims
> ownership. Delete, (or comment out), this entry.
>
> At the buttom of /etc/pcmcia/wlan-ng.conf; make an entry for your card's
> manfid.
>

It seems that that PCMCIA is recognizing the card as an "Anonymous Memory"
and is loading memory_cs instead of using the correct:

card "D-Link DWL-650"
version "D", "Link DWL-650 11Mbps WLAN Card"
bind "orinoco_cs"

or "prism2_cs" I would suspect.

Oddly enough is seems to skip write over the correct one in favour of the
wrong config. BTW cardctl ident comes up with "no product info available"
as it is not able to load in the memory_cs correctly either (as it is not a
memory card)

Next questions are of course if I put in a manfid will that cause it to be
detected correctly? Also I have googled the hell out of Dlink DWL-650 (mine
is hardware version "J3" ) and I can't find a manfid specific to the J3 is
there a way of having the card tell me?

The only one I have found seems to be "manfid 0x0156, 0x0002" and will try
it out and see but if there is a better way than trial and error please let
me know.

Dave

On Wed, 13 Apr 2005 19:09:15 -0400, Dave Waddling wrote:

> It seems that that PCMCIA is recognizing the card as an "Anonymous
> Memory" and is loading memory_cs instead of using the correct:
>
> card "D-Link DWL-650"
> version "D", "Link DWL-650 11Mbps WLAN Card" bind "orinoco_cs"
>
> or "prism2_cs" I would suspect.

Both should work, but you can only load one of them at any given time...

> Oddly enough is seems to skip write over the correct one in favour of
> the wrong config. BTW cardctl ident comes up with "no product info
> available" as it is not able to load in the memory_cs correctly either
> (as it is not a memory card)

This is strange, but it explains why it loads the memory_cs module..

> Next questions are of course if I put in a manfid will that cause it to
> be detected correctly? Also I have googled the hell out of Dlink DWL-650
> (mine is hardware version "J3" ) and I can't find a manfid specific to
> the J3 is there a way of having the card tell me?
>
> The only one I have found seems to be "manfid 0x0156, 0x0002" and will
> try it out and see but if there is a better way than trial and error
> please let me know.

Off the top of my head...:

Make backup copies of /etc/pcmcia/config and /etc/pcmcia/wlan-ng.conf. I
suspect you'll end up making some serious changes...

Comment out this section from /etc/pcmcia/config:
card "Anonymous Memory"
anonymous
bind "memory_cs"

Create an entry in /etc/pcmcia/wlan-ng.conf:
card "Anonymous Memory"
anonymous
bind "prism2_cs"

BTW: What's the output of?:

cardctl status
cardctl info

Have you checked /var/log/messages for additional information about your
card?

--
Regards/Med vennlig hilsen
Joachim Mæland
If everything seems under control, you're just not going fast enough.
-Mario Andretti

Joachim Mæland wrote:

> On Wed, 13 Apr 2005 19:09:15 -0400, Dave Waddling wrote:
>
>> It seems that that PCMCIA is recognizing the card as an "Anonymous
>> Memory" and is loading memory_cs instead of using the correct:
>>
>> card "D-Link DWL-650"
>> version "D", "Link DWL-650 11Mbps WLAN Card" bind "orinoco_cs"
>>
>> or "prism2_cs" I would suspect.
>
> Both should work, but you can only load one of them at any given time...
>
>> Oddly enough is seems to skip write over the correct one in favour of
>> the wrong config. BTW cardctl ident comes up with "no product info
>> available" as it is not able to load in the memory_cs correctly either
>> (as it is not a memory card)
>
> This is strange, but it explains why it loads the memory_cs module..
>
>> Next questions are of course if I put in a manfid will that cause it to
>> be detected correctly? Also I have googled the hell out of Dlink DWL-650
>> (mine is hardware version "J3" ) and I can't find a manfid specific to
>> the J3 is there a way of having the card tell me?
>>
>> The only one I have found seems to be "manfid 0x0156, 0x0002" and will
>> try it out and see but if there is a better way than trial and error
>> please let me know.
>
> Off the top of my head...:
>
> Make backup copies of /etc/pcmcia/config and /etc/pcmcia/wlan-ng.conf. I
> suspect you'll end up making some serious changes...
>
> Comment out this section from /etc/pcmcia/config:
> card "Anonymous Memory"
> anonymous
> bind "memory_cs"
>
> Create an entry in /etc/pcmcia/wlan-ng.conf:
> card "Anonymous Memory"
> anonymous
> bind "prism2_cs"
>
> BTW: What's the output of?:
>
> cardctl status
> cardctl info
>
> Have you checked /var/log/messages for additional information about your
> card?
>


Last things first

linux:/home/dave # cardctl ident && cardctl status && cardctl info
Socket 0:
no product info available
Socket 1:
no product info available
Socket 0:
3.3V 16-bit PC Card
function 0: [ready], [bat low]
Socket 1:
no card
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255

strang eh?

of course when I change the driver for Anonymous Memory it still tries to
probe it but with the wrong driver.

DAve

Joachim Mæland wrote:

> On Wed, 13 Apr 2005 19:09:15 -0400, Dave Waddling wrote:
>
>> It seems that that PCMCIA is recognizing the card as an "Anonymous
>> Memory" and is loading memory_cs instead of using the correct:
>>
>> card "D-Link DWL-650"
>> version "D", "Link DWL-650 11Mbps WLAN Card" bind "orinoco_cs"
>>
>> or "prism2_cs" I would suspect.
>
> Both should work, but you can only load one of them at any given time...
>
>> Oddly enough is seems to skip write over the correct one in favour of
>> the wrong config. BTW cardctl ident comes up with "no product info
>> available" as it is not able to load in the memory_cs correctly either
>> (as it is not a memory card)
>
> This is strange, but it explains why it loads the memory_cs module..
>
>> Next questions are of course if I put in a manfid will that cause it to
>> be detected correctly? Also I have googled the hell out of Dlink DWL-650
>> (mine is hardware version "J3" ) and I can't find a manfid specific to
>> the J3 is there a way of having the card tell me?
>>
>> The only one I have found seems to be "manfid 0x0156, 0x0002" and will
>> try it out and see but if there is a better way than trial and error
>> please let me know.
>
> Off the top of my head...:
>
> Make backup copies of /etc/pcmcia/config and /etc/pcmcia/wlan-ng.conf. I
> suspect you'll end up making some serious changes...
>
> Comment out this section from /etc/pcmcia/config:
> card "Anonymous Memory"
> anonymous
> bind "memory_cs"
>
> Create an entry in /etc/pcmcia/wlan-ng.conf:
> card "Anonymous Memory"
> anonymous
> bind "prism2_cs"
>
> BTW: What's the output of?:
>
> cardctl status
> cardctl info
>
> Have you checked /var/log/messages for additional information about your
> card?
>


Last tings first:

linux:/etc/pcmcia # cardctl ident && cardctl status && cardctl info
Socket 0:
no product info available
Socket 1:
no product info available
Socket 0:
3.3V 16-bit PC Card
function 0: [ready], [bat low]
Socket 1:
no card
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255


This is before and after making the changes you suggested above. Odd thing
too is that when I do a rcpcmcia restart it tells me it failed and that the
ds module is in use but the light on the card goes off. I can then start it
just fine but the care info remains blank..

Dave

BTW thanks again for all of your time and effort

On Wed, 13 Apr 2005 20:53:12 -0400, Dave Waddling wrote:

> strang eh?

Well, it's bits and bytes, they're allways logical.. :-)

This is new to me, but I love a challenge, and an opportunity to learn
something new... I've found several references to DWL-650 and memory_cs,
none stating a fix.

First something related, a quick shot in the dark:
Do you have a orinoco_cs or prism2_cs entry in /etc/modprobe.conf? Remove
it/them!

Then the more methodical approach:
After a clean reboot, please post /var/log/messages when inserting
your card.

What parameters does your /etc/pcmcia/config.opts have for "include
memory", "include port" and "exclude irq"?

What's the output of "cat /proc/interrupts"?

BTW: You'll get your card working...

--
Regards/Med vennlig hilsen
Joachim Mæland
If everything seems under control, you're just not going fast enough.
-Mario Andretti

Joachim

Regarding /etc/modprobe.conf, no I don't usually put stuff in there unless I
know it works.
--------------------------------------
Regarding /var/log/messages...

Apr 14 21:26:26 linux cardmgr[3987]: socket 0: Anonymous Memory
Apr 14 21:26:26 linux kernel: cs: memory probe 0xa0000000-0xa0ffffff:
excluding 0xa0000000-0xa0ffffff
Apr 14 21:26:26 linux kernel: cs: memory probe 0x60000000-0x60ffffff:
excluding 0x60000000-0x60ffffff
Apr 14 21:26:26 linux kernel: cs: warning: no high memory space available!
Apr 14 21:26:26 linux kernel: cs: memory probe 0x0d0000-0x0dffff: excluding
0xd0000-0xdffff
Apr 14 21:26:26 linux kernel: cs: memory probe 0x0e0000-0x0effff: excluding
0xe0000-0xeffff
Apr 14 21:26:26 linux kernel: cs: memory probe 0x0c0000-0x0cffff: excluding
0xc0000-0xcffff
Apr 14 21:26:26 linux kernel: cs: memory probe 0x0f0000-0x0fffff: excluding
0xf0000-0xfffff
Apr 14 21:26:26 linux kernel: cs: unable to map card memory!
Apr 14 21:26:26 linux last message repeated 5 times
Apr 14 21:26:26 linux cardmgr[3987]: executing: 'modprobe memory_cs 2>&1'
Apr 14 21:26:26 linux cardmgr[3987]: + FATAL: Module memory_cs not found.
Apr 14 21:26:26 linux cardmgr[3987]: modprobe exited with status 1
Apr 14 21:26:26 linux cardmgr[3987]:
module /lib/modules/2.6.8-24-default/pcmcia/memory_cs.o not available
Apr 14 21:26:26 linux cardmgr[3987]: bind 'memory_cs' to socket 0 failed:
Invalid argument
-----------------------------------
Regarding /etc/pcmcia/config.opts

include port 0x100-0x3af, port 0x3e0-0x4ff, port 0x800-0x80f, port
0x820-0x8ff, port 0xc00-0xcff
include memory 0xc0000-0xfffff
include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff
include port 0xa00-0xaff

exclude irq 4
exclude irq 7
-----------------------------------
Regarding cat...

linux:/etc/pcmcia # cat /proc/interrupts
CPU0
0: 476792 XT-PIC timer
1: 1233 XT-PIC i8042
2: 0 XT-PIC cascade
9: 400 XT-PIC acpi
10: 8798 XT-PIC ehci_hcd, ohci_hcd, ndiswrapper
11: 28173 XT-PIC ohci_hcd, yenta, yenta, eth0, NVidia
nForce3, nvidia
12: 115 XT-PIC i8042
14: 8042 XT-PIC ide0
15: 2696 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0

Thanks for the help I haven't worked on PCMCIA before and it took me some
time just to find what was going on with it and Yast and Hotplug.

Dave


Joachim Mæland wrote:

> On Wed, 13 Apr 2005 20:53:12 -0400, Dave Waddling wrote:
>
>> strang eh?
>
> Well, it's bits and bytes, they're allways logical.. :-)
>
> This is new to me, but I love a challenge, and an opportunity to learn
> something new... I've found several references to DWL-650 and memory_cs,
> none stating a fix.
>
> First something related, a quick shot in the dark:
> Do you have a orinoco_cs or prism2_cs entry in /etc/modprobe.conf? Remove
> it/them!
>
> Then the more methodical approach:
> After a clean reboot, please post /var/log/messages when inserting
> your card.
>
> What parameters does your /etc/pcmcia/config.opts have for "include
> memory", "include port" and "exclude irq"?
>
> What's the output of "cat /proc/interrupts"?
>
> BTW: You'll get your card working...
>