[Acx100-devel] [ acx100-Support Requests-861132 ] Access point 00:00:00:00:00:00

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Support Requests item #861132, was opened at 2003-12-16 17:56
Message generated for change (Comment added) made by jrcolvin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=543746&aid=861132&group_id=75380

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Richard Colvin (jrcolvin)
Assigned to: Nobody/Anonymous (nobody)
Summary: Access point 00:00:00:00:00:00

Initial Comment:
Hello,

Would simple like to commend your progress with these
drivers, well done so far.

I am running SuSE 8.2 on a Dell laptop and running your
ACX100 driver pre 6 with MS Window 98 Firmware provided
by D-Link.  I happen to be using KWiFi Manager 1.0.1 as
a graphic interface and a DWL-650+ AirPlus PCcard.

I have been using your drivers since pre 3 and have
been struggling to resolve an Access Point
00:00:00:00:00:00 issue.

Whenever rebooting or starting up the chances of
getting a 00:00:00:00:00:00 access point is highly
likely, about 9 out of  10 starts.

By pulling out and re-inserting the PCcard the problem
seems to be resolved (After the 3rd attempt that is).

What is interesting is that the KWiFi Manager tells me
that I am connected at 22M dispite having the Access
Point as 00:00:00:00:00:00.

Please would you provide me with some pointers as to
how I can over come this Access Point 00:00:00:00:00:00
problem?

----------------------------------------------------------------------

>Comment By: Richard Colvin (jrcolvin)
Date: 2003-12-24 14:30

Message:
Logged In: YES 
user_id=889609

Hello Admin, sorry for not replying sooner:

I've attached my boot.msg log as it seems to have some errors.

Here is some of my system log:

Dec 23 11:37:04 linux kernel: acx100: It looks like you were
coaxed into buying a wireless network card
Dec 23 11:37:04 linux kernel: acx100: that uses the
mysterious ACX100 chip from Texas Instruments.
Dec 23 11:37:04 linux kernel: acx100: You should better have
bought e.g. a PRISM(R) chipset based card,
Dec 23 11:37:04 linux kernel: acx100: since that would mean
REAL vendor Linux support.
Dec 23 11:37:04 linux kernel: acx100: Given this info, it's
plain evident that this driver is EXPERIMENTAL,
Dec 23 11:37:04 linux kernel: acx100: thus your mileage may
vary. Visit http://acx100.sf.net for support.
Dec 23 11:37:04 linux kernel: acx100_init_module: TI
acx100_pci.o: Ver 0.2.0pre6 Loaded
Dec 23 11:37:04 linux kernel: PCI: Setting latency timer of
device 06:00.0 to 64
Dec 23 11:37:04 linux kernel: Found ACX100-based wireless
network card, phymem1:0x11000000, phymem2:0x11010000,
irq:11, mem1:0xd10f3000, mem2:0xd10f5000
Dec 23 11:37:04 linux kernel: Allocating 6592, 19C0h bytes
for wlandevice_t
Dec 23 11:37:04 linux kernel: Allocated 33708 bytes for
firmware module loading.
Dec 23 11:37:05 linux kernel: Allocated 964 bytes for
firmware module loading.
Dec 23 11:37:05 linux kernel: acx100: form factor 0x00
(standard?), radio type 0x11 (RFMD), EEPROM version 0x0004.
Uploaded firmware 'Rev 1.9.3.e' (0x01020505).
Dec 23 11:37:05 linux insmod: Using
/lib/modules/2.4.20-4GB/kernel/drivers/net/acx100_pci.o
Dec 23 11:37:05 linux insmod: Symbol version prefix ''
Dec 23 11:37:06 linux /etc/hotplug/pci.agent[830]: writing
pcmcia-1 to /var/run/hotplug/net
Dec 23 11:37:06 linux /etc/hotplug/net.agent[924]: Using HW
description eth-pcmcia-1
Dec 23 11:37:07 linux kernel: changing radio power level to
20 dBm (0x3f)
Dec 23 11:37:07 linux kernel: acx100_process_probe_response:
found and registered station 0: ESSID "colvin1" on channel
6, BSSID 00 05 5D 7F 30 74 (Access Point, 22Mbps), SIR 136,
SNR 0.
Dec 23 11:37:08 linux kernel: PCI: Found IRQ 5 for device
00:08.0
Dec 23 11:37:08 linux kernel: PCI: Sharing IRQ 5 with 00:07.2
Dec 23 11:37:08 linux kernel: es1968: clocking to 48000
Dec 23 11:37:08 linux kernel: d11CompleteScan: matching
station FOUND (idx 0), JOINING (00 05 5D 7F 30 74).
Dec 23 11:37:08 linux kernel: Sending authentication1
request, awaiting response!
Dec 23 11:37:08 linux kernel: Tx error occurred (error
0x10)!! (maybe distance too high?)
Dec 23 11:37:08 linux kernel: <sta_list_add> sta =
00:05:5D:7F:30:74
Dec 23 11:37:08 linux kernel: Sending association request,
awaiting response! NOT ASSOCIATED YET.
Dec 23 11:37:08 linux kernel: Tx error occurred (error
0x10)!! (maybe distance too high?)
Dec 23 11:37:08 linux kernel: ASSOCIATED!
Dec 23 11:37:11 linux kernel: Tx error occurred (error
0x10)!! (maybe distance too high?)
Dec 23 11:37:11 linux kernel: Tx error occurred (error
0x10)!! (maybe distance too high?)
Dec 23 11:37:12 linux modify_resolvconf: Service dhcpcd
modified /etc/resolv.conf. See info block in this file
Dec 23 11:37:15 linux kernel: IPv6 v0.8 for NET4.0
Dec 23 11:37:15 linux kernel: IPv6 over IPv4 tunneling driver
Dec 23 11:37:15 linux kernel: Tx error occurred (error
0x10)!! (maybe distance too high?)
Dec 23 11:37:15 linux sshd[1218]: Server listening on ::
port 22.
Dec 23 11:37:15 linux kernel: eth0: duplicate address detected!
Dec 23 11:37:20 linux /usr/sbin/cron[1434]: (CRON) STARTUP
(fork ok)
Dec 23 11:37:23 linux kernel: isapnp: Scanning for PnP cards...

As for some more info, this is when the card is up and running:

linux:/home/colvin # iwconfig
lo        no wireless extensions.

sit0      no wireless extensions.

eth0      IEEE 802.11b  ESSID:"colvin1"  Nickname:"Inspiron7500"
          Mode:Managed  Channel:6  Access Point:
00:05:5D:7F:30:74
          Bit Rate=22Mb/s   Tx-Power:20 dBm
          Retry min limit:5
          Encryption key:off
          Link Quality:100  Signal level:50  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid
frag:0
          Tx excessive retries:0  Invalid misc:0   Missed
beacon:0

linux:/home/colvin # ifconfig
eth0      Link encap:Ethernet  HWaddr 00:80:C8:AD:9B:D9
          inet addr:192.168.0.2  Bcast:192.255.255.255 
Mask:255.0.0.0
          inet6 addr: fe80::280:c8ff:fead:9bd9/64 Scope:Link
          UP BROADCAST NOTRAILERS RUNNING MULTICAST 
MTU:1500  Metric:1
          RX packets:1747 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1947 errors:3 dropped:0 overruns:0
carrier:0
          collisions:0 txqueuelen:100
          RX bytes:1199683 (1.1 Mb)  TX bytes:249711 (243.8 Kb)
          Interrupt:11 Base address:0x4800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:94 errors:0 dropped:0 overruns:0 frame:0
          TX packets:94 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:6412 (6.2 Kb)  TX bytes:6412 (6.2 Kb)

Could this issue be cause by YAST as it reads the card as
detected but not configured?

Hope I have provided the information which you are after?
Regards,

----------------------------------------------------------------------

Comment By: Andreas Mohr (andim2)
Date: 2003-12-22 18:41

Message:
Logged In: YES 
user_id=132674

Please provide proper logs showing the problem.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=543746&aid=861132&group_id=75380