D-Link DWL-650

I'm working on getting a DWL-650 (Revisions A1-J3 according to the D-
Link website) running with Puppy Linux. Sometimes it works great.
Other times, it won't connect. Here's some of /var/log/messages when
it works and when it doesn't work.

Any idea what I can do to make this more reliable?

THANKS!

Harold

GOOD BOOT:
Aug 30 20:48:10 (none) user.info kernel: eth0: New link
statusisconnected (0002)
Aug 30 20:48:10 (none) user.info kernel: eth0: New link status:
Connected (0001)
Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: dhcpcd 3.1.4
starting
Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: hardware
address = 00:05:5d:f1:ca:d5
Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: DUID =
00:01:00:01:0e:67:33:21:00:05:5d:f1:ca:d5
Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: broadcasting
for a lease
Aug 30 20:48:31 (none) user.info kernel: eth0: New link status:
Connected (0001)
Aug 30 20:48:34 (none) local0.info dhcpcd[2029]: eth0: offered
192.168.1.102 from 192.168.1.1
Aug 30 20:48:35 (none) local0.info dhcpcd[2029]: eth0: checking
192.168.1.102 is available on attached networks
Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: leased
192.168.1.102 for 86400 seconds
Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: no renewal time
supplied, assuming 43200 seconds
Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: no rebind time
supplied, assuming 75600 seconds
Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: adding IP
address 192.168.1.102/24
Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: adding default
route via 192.168.1.1 metric 0


BAD BOOT:
Sep 2 12:01:24 (none) user.info kernel: eth0: New link status:
Disconnected (0002)
Sep 2 12:01:24 (none) user.info kernel: eth0: New link status:
Connected (0001)
Sep 2 12:01:34 (none) user.err kernel: hermes @ 00010100: Timeout
waiting for command 0x0002 completion.
Sep 2 12:01:34 (none) user.warn kernel: eth0: Error -110 disabling
MAC port

On Fri, 07 Sep 2007 21:30:05 -0700, (E-Mail Removed) wrote:

> I'm working on getting a DWL-650 (Revisions A1-J3 according to the D-
> Link website) running with Puppy Linux. Sometimes it works great.
> Other times, it won't connect. Here's some of /var/log/messages when
> it works and when it doesn't work.
>
> Any idea what I can do to make this more reliable?
>
> THANKS!
>
> Harold
>
> GOOD BOOT:
> Aug 30 20:48:10 (none) user.info kernel: eth0: New link
> statusisconnected (0002)
> Aug 30 20:48:10 (none) user.info kernel: eth0: New link status:
> Connected (0001)
> Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: dhcpcd 3.1.4
> starting
> Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: hardware
> address = 00:05:5d:f1:ca:d5
> Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: DUID =
> 00:01:00:01:0e:67:33:21:00:05:5d:f1:ca:d5
> Aug 30 20:48:30 (none) local0.info dhcpcd[2029]: eth0: broadcasting
> for a lease
> Aug 30 20:48:31 (none) user.info kernel: eth0: New link status:
> Connected (0001)
> Aug 30 20:48:34 (none) local0.info dhcpcd[2029]: eth0: offered
> 192.168.1.102 from 192.168.1.1
> Aug 30 20:48:35 (none) local0.info dhcpcd[2029]: eth0: checking
> 192.168.1.102 is available on attached networks
> Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: leased
> 192.168.1.102 for 86400 seconds
> Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: no renewal time
> supplied, assuming 43200 seconds
> Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: no rebind time
> supplied, assuming 75600 seconds
> Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: adding IP
> address 192.168.1.102/24
> Aug 30 20:48:36 (none) local0.info dhcpcd[2029]: eth0: adding default
> route via 192.168.1.1 metric 0
>
>
> BAD BOOT:
> Sep 2 12:01:24 (none) user.info kernel: eth0: New link status:
> Disconnected (0002)
> Sep 2 12:01:24 (none) user.info kernel: eth0: New link status:
> Connected (0001)
> Sep 2 12:01:34 (none) user.err kernel: hermes @ 00010100: Timeout
> waiting for command 0x0002 completion.
> Sep 2 12:01:34 (none) user.warn kernel: eth0: Error -110 disabling
> MAC port


harold,

how intermittent is the working vs. non-working? every third boot works?
every tenth? every other?

more information is needed if we are to help you...

1. what chipset does that Revision A1-J3 (?!) contain? The G650 cardbus
adapters received different chipsets at different times. For example,
my G650 is H/W Ver B4 and it contains an Atheros chipset. And, the
device nmemonic for mine is ath0, not eth0.

2. what kernel drivers are loaded for your adapter? Enter: lsmod
to see which driver is loaded for your adapter.

3. when it fails to connect, have you subsequently tried removing the
adapter, and then reinserting it into a cardbus slot again? Have you
tried another card slot? Are your cardslot pins all straight and clean?

4. what version of the linux kernel have you? reason being, the
earlier versions of the 2.6 kernels didn't have the required or working
pieces of kernel wireless extensions, so that might be an issue. Enter:
uname -a

5. what make/model of laptop/desktop are you trying this cardbus adapter
with?



please, gather the requested data and report back here.

jm

On Sep 8, 11:14 pm, john mckenna <pikiw...@hushmail.com> wrote:
THANKS! Responses are below:
> harold,
>
> how intermittent is the working vs. non-working? every third boot works?
> every tenth? every other?

At times, it will work on every boot, but then it might take 10 to get
it to come up. I've got another laptop running ndiswrapper on an
internal wireless interface, and it comes up every time, so I think
the network is ok. It's running 128 bit WEP encryption.

>
> more information is needed if we are to help you...
>
> 1. what chipset does that Revision A1-J3 (?!) contain? The G650 cardbus
> adapters received different chipsets at different times. For example,
> my G650 is H/W Ver B4 and it contains an Atheros chipset. And, the
> device nmemonic for mine is ath0, not eth0.
>

The card is a D-Link DWL-650. According to someone on the Puppy Linux
forum, this card has either the Orinoco or Prism2 chipset. From the D-
Link website:

# The DWL-650 has a rectangular body with the antenna that looks like
a tab or "ear" that is connected to the body. These are revisions A1-
J3.

> 2. what kernel drivers are loaded for your adapter? Enter: lsmod
> to see which driver is loaded for your adapter.

# lsmod
Module Size Used by
usb_storage 86464 0
evdev 10624 1
snd_mixer_oss 17536 0
lp 12744 0
parport_pc 32996 0
parport 35784 2 lp,parport_pc
usblp 14340 0
orinoco_cs 16272 1
orinoco 43036 1 orinoco_cs
hermes 7552 2 orinoco_cs,orinoco
apm 21372 0
yenta_socket 28188 4
rsrc_nonstatic 13580 1 yenta_socket
snd_ymfpci 61376 0
gameport 15368 1 snd_ymfpci
firmware_class 9984 1 snd_ymfpci
snd_ac97_codec 97700 1 snd_ymfpci
ac97_bus 2432 1 snd_ac97_codec
snd_pcm 78992 2 snd_ymfpci,snd_ac97_codec
snd_opl3_lib 10752 1 snd_ymfpci
snd_timer 23432 3 snd_ymfpci,snd_pcm,snd_opl3_lib
snd_hwdep 9348 1 snd_opl3_lib
snd_page_alloc 10248 2 snd_ymfpci,snd_pcm
snd_mpu401_uart 8448 1 snd_ymfpci
snd_rawmidi 23872 1 snd_mpu401_uart
snd_seq_device 8332 2 snd_opl3_lib,snd_rawmidi
snd 52324 10
snd_mixer_oss,snd_ymfpci,snd_ac97_codec,snd_pcm,sn d_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd _rawmidi,snd_seq_device
soundcore 7904 1 snd
i2c_piix4 8980 0
i2c_core 22672 1 i2c_piix4
intel_agp 24860 1
agpgart 36176 1 intel_agp
uhci_hcd 25364 0
usbcore 132252 4 usb_storage,usblp,uhci_hcd
nls_iso8859_1 4352 0
nls_cp437 6016 0
#

>
> 3. when it fails to connect, have you subsequently tried removing the
> adapter, and then reinserting it into a cardbus slot again? Have you
> tried another card slot? Are your cardslot pins all straight and clean?

This is a small machine with only one card slot. Puppy Linux has a
network interface wizard. Sometimes after the card does not come up, I
go to the wizard and tell it to scan for networks. It does not find
any. I unplug the card, put it back in, and scan again. It then finds
networks. Telling it to connect to one, though, is then still pretty
intermittent. I think the card pins are ok.
>

> 4. what version of the linux kernel have you? reason being, the
> earlier versions of the 2.6 kernels didn't have the required or working
> pieces of kernel wireless extensions, so that might be an issue. Enter:
> uname -a


# uname -a
Linux puppypc 2.6.21.5 #1 Sat Jun 23 21:16:21 PUP 2007 i686 unknown
unknown GNU/Linux
#


>
> 5. what make/model of laptop/desktop are you trying this cardbus adapter
> with?

This is a Sony Viao PCG-SR27 notebook.

>
> please, gather the requested data and report back here.
>
> jm

THANKS!

Harold