Hello,

I have bought a D-Link DWL-G650 108MBit PCMCIA-Wireless lan card. I have an
Acer Travelmate 524tx. I want to use this card to connect to a wireless lan
at home.

TheCard has an Atheros chipset. So I have installed the madwifi driver.
First I jave tried to connect to the wireless lan over WPA-PSK. I did not
connect. Then I have tried to connect to an open wireless lan. There I was
successful but the I can't send or receive any data.
A ping to the router returns the error message, that there are wrong data
byte.

I have figured out that the used PCMCIA-Card chipset (O2 Micro OZ6933 /
711E1) of the Acer Travelmate 524 TX might be not compatible to the Atheros
chipset (or the used driver etc.).
I tried to use madwifi and ndiswrapper. Both did not work.

Can anyone help me?
Has anyone accompished to get the card on this cardbus chipset running?
Anyone an idea what I can do further?

Best regards Christian

Christian Panten wrote:
> I tried to use madwifi and ndiswrapper. Both did not work.

Care to elaborate a *lot* more on what you mean by "did not work"?

I've never seen a "wrong data byte" error in my experience with wireless
cards, unfortunately.

Hello,

here I give you some more detailed information. I hope, this are enough. If
it is not, tell me what more information you want.


After putting the pcmcia card into the pcmcia slot lspci give me this
information:

======================= lspci ==============================================

0000:00:00.0 Host bridge: ALi Corporation M1621 (rev 05)
0000:00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller (rev 01)
0000:00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
Controller Audio Device (rev 01)
0000:00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin
IV]
0000:00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro
100] (rev 08)
0000:00:10.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
0000:00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
0000:00:13.0 CardBus bridge: O2 Micro, Inc. OZ6933/711E1
CardBus/SmartCardBus Controller (rev 01)
0000:00:13.1 CardBus bridge: O2 Micro, Inc. OZ6933/711E1
CardBus/SmartCardBus Controller (rev 01)
0000:00:14.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility
P/M AGP 2x (rev 64)
0000:02:00.0 Ethernet controller: Atheros Communications, Inc. AR5212
802.11abg NIC (rev 01)

Then I start the wireless card by calling /etc/init.d/net.ath0 start. From
this I get the following informations:

============== net.ath0 start ==============================================

Starting ath0
Loading networking modules for ath0
modules: iwconfig essidnet iptunnel ifconfig dhcpcd apipa
iwconfig provides wireless
ifconfig provides interface
dhcpcd provides dhcp
Configuring wireless network for ath0
Connecting to "mcrhomenet" (WEP Disabled) ... ok
ath0 connected to "mcrhomenet" at 00:11:95:07:7B:AC
in managed mode (WEP disabled)
Configuring ath0 for "mcrhomenet" ... ok
Bringing up ath0
dhcp
Running dhcpcd ... ok
ath0 received address 192.168.123.100


After this both leds on the pcmcia blinks in time with each other.

Now I try to ping the wireless access point (192.168.123.1)

=============== ping 192.168.123.1 =========================================

PING 192.168.123.1 (192.168.123.1) 56(84) bytes of data.
64 bytes from 192.168.123.1: icmp_seq=3 ttl=127 time=0.167 ms
wrong data byte #12 should be 0xc but was 0x0
#8 8 9 a b 0 0 0 0 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22
23 24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 0 0 0 0
64 bytes from 192.168.123.1: icmp_seq=4 ttl=127 time=1.05 ms
wrong data byte #20 should be 0x14 but was 0x0
#8 8 9 a b c d e f 10 11 12 13 0 0 0 0 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23
24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
64 bytes from 192.168.123.1: icmp_seq=7 ttl=127 time=1.01 ms
wrong data byte #20 should be 0x14 but was 0x7f
#8 8 9 a b c d e f 10 11 12 13 7f 1 1 0 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23
24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
64 bytes from 192.168.123.1: icmp_seq=10 ttl=127 time=0.169 ms
wrong data byte #28 should be 0x1c but was 0xc
#8 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b c 0 3 7f 20 21 22 23
24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35 36 37
64 bytes from 192.168.123.1: icmp_seq=14 ttl=127 time=1.01 ms
wrong data byte #52 should be 0x34 but was 0x11
#8 8 9 a b c d e f 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22
23 24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 11 95 7 7b
64 bytes from 192.168.123.1: icmp_seq=15 ttl=127 time=22.0 ms
wrong data byte #12 should be 0xc but was 0x12
#8 8 9 a b 12 24 60 6c 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21
22 23 24 25 26 27
#40 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 11 95 7 7b
64 bytes from 192.168.123.1: icmp_seq=17 ttl=127 time=0.999 ms
[...]
--- 192.168.123.1 ping statistics ---
36 packets transmitted, 18 received, 50% packet loss, time 35011ms
rtt min/avg/max/mdev = 0.153/3.392/23.551/6.887 ms


Here you see the error message: wrong data byte.
I tried to ping www.google.de. But I did not get any message.

At least I give you the information ifconfig and iwconfig give me:

=============== ifconfig ================================================== =
ath0 Protokoll:Ethernet Hardware Adresse 00:0F:3D:AB:77A
inet Adresse:192.168.123.100 Bcast:192.168.123.255
Maske:255.255.255.0
inet6 Adresse: fe80::20f:3dff:feab:77da/64
Gültigkeitsbereich:Verbindung
UP BROADCAST NOTRAILERS RUNNING MULTICAST MTU:1500 Metric:1
RX packets:143 errors:5 dropped:0 overruns:0 frame:5
TX packets:55 errors:0 dropped:0 overruns:0 carrier:0
Kollisionen:0 Sendewarteschlangenlänge:199
RX bytes:35678 (34.8 Kb) TX bytes:7064 (6.8 Kb)
Interrupt:11 Speicher:d8d80000-d8d90000


================ iwconfig ==================================================

ath0 IEEE 802.11g ESSID:"mcrhomenet" Nickname:"mcrhomenet"
Mode:Managed Frequency:2.437 GHz Access Point: 00:11:95:07:7B:AC
Bit Rate:36 Mb/s Tx-Power:50 dBm Sensitivity=0/3
Retryff RTS thrff Fragment thrff
Encryption keyff
Power Managementff
Link Quality=43/94 Signal level=-52 dBm Noise level=-95 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

And this modules are loaded:

================= lsmod ================================================== ==
Module Size Used by
ath_pci 53888 0
ath_rate_onoe 7016 1 ath_pci
wlan 108988 3 ath_pci,ath_rate_onoe
ath_hal 146864 2 ath_pci
pcmcia 19304 4
yenta_socket 20008 3
rsrc_nonstatic 7360 1 yenta_socket
pcmcia_core 41892 3 pcmcia,yenta_socket,rsrc_nonstatic
battery 8164 0
processor 18612 0
ac 3300 0
button 4848 0
e100 32000 0

================================================== ======================
At the very end I give you some paramters of my kernel-configuration:
CONFIG_PCMCIA=m
CONFIG_CARDBUS=y
CONFIG_YENTA=m
CONFIG_NET_WIRELESS=y


I hope these information are enough for you to help me.

Best regards
Christian


Paul Bredbury wrote:

> Christian Panten wrote:
>> I tried to use madwifi and ndiswrapper. Both did not work.
>
> Care to elaborate a *lot* more on what you mean by "did not work"?
>
> I've never seen a "wrong data byte" error in my experience with wireless
> cards, unfortunately.

Christian Panten wrote:
> PING 192.168.123.1 (192.168.123.1) 56(84) bytes of data.
> 64 bytes from 192.168.123.1: icmp_seq=3 ttl=127 time=0.167 ms
> wrong data byte #12 should be 0xc but was 0x0

All the Googling about "wrong data byte" refers to the problem being an
old version of "ping" which timeouts too early.

Try running:
emerge --sync
emerge --pretend --nospinner --verbose --update --newuse --deep world

To see whether your system is up-to-date.

Hi Paul,

Today I have done a update which you told me to do. You were right: iputils
were out of date. But after the update the wireless lan does not work.

So has anyone an idea how I can solve my problem?

Best regards
Christian


Paul Bredbury wrote:

> Christian Panten wrote:
>> PING 192.168.123.1 (192.168.123.1) 56(84) bytes of data.
>> 64 bytes from 192.168.123.1: icmp_seq=3 ttl=127 time=0.167 ms
>> wrong data byte #12 should be 0xc but was 0x0
>
> All the Googling about "wrong data byte" refers to the problem being an
> old version of "ping" which timeouts too early.
>
> Try running:
> emerge --sync
> emerge --pretend --nospinner --verbose --update --newuse --deep world
>
> To see whether your system is up-to-date.

Christian Panten wrote:
> Today I have done a update which you told me to do. You were right: iputils
> were out of date. But after the update the wireless lan does not work.
>
> So has anyone an idea how I can solve my problem?

You will find a wealth of information at your fingertips by using
www.google.com to search on "madwifi" - what specific problem do you
have, that you can't find an answer to?

Hi Paul,

Paul Bredbury wrote:

> Christian Panten wrote:
>> Today I have done a update which you told me to do. You were right:
>> iputils
>> were out of date. But after the update the wireless lan does not work.
>>
>> So has anyone an idea how I can solve my problem?
>
> You will find a wealth of information at your fingertips by using
> www.google.com to search on "madwifi" - what specific problem do you
> have, that you can't find an answer to?

I have searched by google but I did not find an answer to my problem.
Once again, I can connect to the AP, both LED are blinking, ifconfig tells
me the IP-address of the wlan-card. iwconfig tells me I am in my net. I can
find the AP by pinging it. But there are a lot of errors: wrong data byte
and I can't surf in the www. I have no idea to solve the problem.

Best regards
Christian

Christian Panten wrote:
> Once again, I can connect to the AP, both LED are blinking, ifconfig tells
> me the IP-address of the wlan-card. iwconfig tells me I am in my net. I can
> find the AP by pinging it. But there are a lot of errors: wrong data byte
> and I can't surf in the www. I have no idea to solve the problem.

As a wild guess: What's the output of running "route"? If it pauses
for more than 10 seconds before showing all the lines, then that may
indicate that it's a routing problem. Presumably the *default* route
should be through the wireless card.

Paul Bredbury wrote:

> Christian Panten wrote:
>> Once again, I can connect to the AP, both LED are blinking, ifconfig
>> tells me the IP-address of the wlan-card. iwconfig tells me I am in my
>> net. I can find the AP by pinging it. But there are a lot of errors:
>> wrong data byte
>> and I can't surf in the www. I have no idea to solve the problem.
>
> As a wild guess: What's the output of running "route"? If it pauses
> for more than 10 seconds before showing all the lines, then that may
> indicate that it's a routing problem. Presumably the *default* route
> should be through the wireless card.

route -n needs less than 1 sec and results:

Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
192.168.123.0 0.0.0.0 255.255.255.0 U 0 0 0 ath0
127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 0 lo
0.0.0.0 192.168.123.254 0.0.0.0 UG 0 0 0 ath0

Paul Bredbury wrote:

> Christian Panten wrote:
>> Once again, I can connect to the AP, both LED are blinking, ifconfig
>> tells me the IP-address of the wlan-card. iwconfig tells me I am in my
>> net. I can find the AP by pinging it. But there are a lot of errors:
>> wrong data byte
>> and I can't surf in the www. I have no idea to solve the problem.
>
> As a wild guess: What's the output of running "route"? If it pauses
> for more than 10 seconds before showing all the lines, then that may
> indicate that it's a routing problem. Presumably the *default* route
> should be through the wireless card.

Oops... I did the test again but this time with route not with route -n

It took ~10secs and results to:
Kernel IP Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
192.168.123.0 * 255.255.255.0 U 0 0 0 ath0
loopback localhost 255.0.0.0 UG 0 0 0 lo


I hope this helps you.
Thx
Best regards Christian