Re: [PATCH] Re: [Acx100-devel] D-Link DWL-G630 with an ACX111

[Denis V. <vd...@po...>]

> I've put up another log at
> http://stop.crashing.org:16080/~trini/dwl-g630_acx111_take2.txt
>
> This has the 32-bit i/o patch from above, and I tried using both FwRad16
> and FwRad17, but nothing changed.  It's not in the log, but I did try to
> bring the i/f up, but it didn't work (and iwconfig still showed no
> signal, which I don't think was a surprise based on the messages).

Same here. I disabled eth+usb which share irq11 with acx111.
This is what I did:

modprobe acx_pci "firmware_dir=$firmware_dir" debug=0xffff
ip l set dev wlan0 up
iwconfig wlan0 essid zeon
iwconfig wlan0 mode managed

dmesg parts are attached, in the files named
NNNNNNNNN.command
^^^^^^^^^ ^^^^^^^
timestamp corresponding command

Apparently I can't associate with the AP.
It worked in Windows, so hw must be in working condition.

# cat /proc/interrupts | grep wlan0
11:         16          XT-PIC  wlan0

# iwconfig wlan0
wlan0     IEEE 802.11g+  ESSID:"zeon"  Nickname:"acx100 v0.2.0pre8"
          Mode:Managed  Channel:1  Access Point: 00:00:00:00:00:00
          Bit Rate=11Mb/s   Tx-Power:18 dBm
          Retry min limit:7   RTS thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  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

# ip -s -s l l dev wlan0
4: wlan0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:e0:98:ba:20:c3 brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast
    0          0        0       0       0       0
    RX errors: length  crc     frame   fifo    missed
               0        0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    0          0        0       0       0       0
    TX errors: aborted fifo    window  heartbeat
               0        0       0       0

Ok, what can be wrong? In up log:
FIXME: unknown/unsupported radio type, cannot modify Tx power level yet!
Updating antenna value: 0x4A
Configure Command 0x100B not supported under acx111 (yet)
Updating Energy Detect (ED) threshold: 112
Configure Command 0x100F not supported under acx111 (yet)
Updating Channel Clear Assessment (CCA) value: 0x0D
Configure Command 0x100E not supported under acx111 (yet)

in essid and mode_managed log:
acx100_issue_cmd failed: Invalid parameter [46400 uSec] Cmd: 8h, Result: Eh

I guess we shall dig deeper around those.
--
vda