rendered paste bodyDoes it give you any kind of messages when you issue an "ifup wlan0"?
The messages from the initialization and the /proc/ sections look fine
(other than showing that packets have neither been sent nor received).
If you could send the output of "cat /proc/driver/acx_wlan0_diag"
immediately after an "ifup wlan0" attempt and include the section
containing interrupt counts that may help.
Bill
> > -----Original Message-----
> > From: Paul Sokolovsky [mailto:pmiscml@gmail.com]
> > Sent: Thursday, October 19, 2006 9:57 PM
> > To: Jerry Rocha; Reese, William (C&I)
> > Cc: h4100-port@handhelds.org; kernel-discuss@handhelds.org
> > Subject: Re[2]: [H4100-port] ACX100 loading firmware...
> >
> > Hello Jerry,
> >
> > Sunday, October 15, 2006, 11:20:06 PM, you wrote:
> >
>> > > On 15-Oct-06, at 7:59 AM, Paul Sokolovsky wrote:
> >
>> > > Hi Paul,
>>> > >>
>>> > >> Well, firmware in our "slavemem-"intefcaced ACX's is
> > likely differs
>>> > >> from any other model supported by mainline AXC driver. The
> > reliable
>>> > >> way to get the right firmware is to download it from
> > /windows dir of
>>> > >> wince running. Or you cna try already extracted hx4700
> > firmware (it
>>> > >> would be very improbable that it won't work for us; however, if it
>>> > >> won't, we really must try our native as next step).
>>> > >>
>>> > >> http://www.sdgsystems.com/pub/ipaq/hx4700/starterkit/20060615-gpe/
>>> > >>
>>> > >> As file sizes show, it indeed differs from what you've tried.
>>> > >>
> >
>> > > You were right --- The firmware from /windows
> > (ACX100_dl.bin renamed
>> > > to /lib/firmware/WLANGEN.BIN and maxim_radio_dl.bin renamed to
>> > > /lib/firmware/RADIO0d.BIN) loaded right up!
> >
> > Good progress, Jerry! I hoped to find time to play with ACX
> > myself, but still busy with other tasks. So, I'll just cc:
> > this to kernel-discuss as a status report and to Bill Reese
> > who might see if there's something wrong immediately.
> >
> > Otherwise, it may be good idea to read thru hx4700-port
> > archives on ACX100 topic, there was quite large discussion
> > which would be relavant for us too.
> >
>> > > root@h4000:/storage/kernel26/drivers/net/wireless/acx#
> > insmod ./acx.ko
>> > > root@h4000:/storage/kernel26/drivers/net/wireless/acx# insmod ./
>> > > h4000_acx.ko root@h4000:/storage/kernel26/drivers/net/wireless/acx#
>> > > dmesg
>> > > acx: this driver is still EXPERIMENTAL
>> > > acx: reading README file and/or Craig's HOWTO is recommended, visit
>> > > http://acx100.sf.net in case of further questions/discussion
>> > > acx: compiled to use 32bit I/O access. I/O timing issues
> > might occur,
>> > > such as non-working firmware upload. Report them running on a
>> > > little-endian CPU PCI module v0.3.35 initialized, waiting
> > for cards to
>> > > probe...
>> > > h4000_wlan_init: acx-mem platform_device_register h4000_wlan_start
>> > > acx: found ACX100-based wireless network card initial debug
> > setting is
>> > > 0x000A using IRQ 34 ACX radio type 0x0d requesting firmware image
>> > > 'WLANGEN.BIN'
>> > > acx_write_fw (main):0
>> > > acx_validate_fw (main):0
>> > > acx: patching in at 0x98d494de
>> > > requesting firmware image 'RADIO0d.BIN'
>> > > acx_write_fw (radio): 0
>> > > acx_validate_fw (radio): 0
>> > > acx100_s_init_wep: writing WEP options initializing max packet
>> > > templates NVS_vendor_offs:0000 probe_delay:500 eof_memory:65536
>> > > CCAModes:04 Diversity:01 ShortPreOpt:01 PBCC:01 ChanAgil:00 PHY:05
>> > > Temp:01
>> > > AntennaID:01 Len:02 Data:1E 00
>> > > PowerLevelID:0A Len:00 Data:
>> > > DataRatesID:02 Len:05 Data:02 04 11 22 44
>> > > DomainID:03 Len:07 Data:10 20 30 31 32 40 41
>> > > ProductID:04 Len:09 Data:TI ACX100
>> > > ManufacturerID:05 Len:07 Data:TI Tes
>> > > get_mask 0x00004D82, set_mask 0x00000000 got sensitivity
> > value 176 got
>> > > antenna value 0x8D got Energy Detect (ED) threshold 112 got Channel
>> > > Clear Assessment (CCA) value 13 got regulatory domain 0x10 get_mask
>> > > 0x00000000, set_mask 0x00000000 - after update new
> > ratevector: 82 84
>> > > 0B 16 2C setting RXconfig to 2010:0FDD
>> > > acx: form factor 0x03 (Compact Flash), radio type 0x0D
> > (Maxim), EEPROM
>> > > version 0x05, uploaded firmware 'Rev 1.10.5.0' (0x01030505)
> > creating
>> > > /proc entry driver/acx_wlan0 creating /proc entry
>> > > driver/acx_wlan0_diag creating /proc entry driver/acx_wlan0_eeprom
>> > > creating /proc entry driver/acx_wlan0_phy
> >
>> > > Even though it loads successfully, nothing appears to
> > work --- wlan0
>> > > is detected and I can set information in iwconfig and ifconfig, I
>> > > can't really use the radio.
> >
>> > > Here's some random output of commands I've looked at:
> >
>> > > root@h4000:/home/jrocha# iwconfig
>> > > lo no wireless extensions.
> >
>> > > usb0 no wireless extensions.
> >
>> > > Warning: Driver for device wlan0 has been compiled with
> > version 20 of
>> > > Wireless Extension, while this program supports up to version 19.
>> > > Some things may be broken...
> >
>> > > wlan0 IEEE 802.11b+ ESSID:"RCMP" Nickname:"acx v0.3.35"
>> > > Mode:Managed Frequency:2.412 GHz Access Point: Not-
>> > > Associated
>> > > Bit Rate=11 Mb/s Tx-Power=18 dBm Sensitivity=176/255
>> > > Retry min limit:7 RTS thr:off
>> > > Encryption key:
>> > >
> > 3431-3639-3939-3938-3931-3131-3131-3131-3131-3131-3131-3131-31
> > 31-5243-4D
>> > > Security mode:open
>> > > 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
> >
> >
>> > > It never associates with my AP. I'm going to try messing
> > around with
>> > > the settings (no wep, adhoc, etc) but I'm pretty sure that it isn't
>> > > even using the radio... Although that's just a guess at this stage.
> >
>> > > I'll include the output of all the files in /proc/driver
> > at the end
>> > > of this email.
> >
>> > > Paul, when I compiled my kernel I removed PCMCIA support for the
>> > > h4000 --- Maybe that's what's keeping you from loading your
> > firmware?
>> > > I also had to compile it as a module since I didn't want to mess
>> > > around with initrd filesystems to store my /lib/firmware contents.
>> > > You're using a 4150/4150 as well I'm assuming?
> >
>> > > We're close, I think. :)
> >
>> > > Output of various files:
> >
>> > > /proc/driver/acx_wlan0:
> >
>> > > acx driver version: v0.3.35
>> > > Wireless extension version: 20
>> > > chip name: TNETW1100B (0x01030505)
>> > > radio type: 0x0D
>> > > form factor: 0x03
>> > > EEPROM version: 0x05
>> > > firmware version: Rev 1.10.5.0 (0x01100500)
>> > > status: 1 (SCANNING)
> >
> >
>> > > /proc/driver/acx_wlan0_diag
>> > > ** Rx buf **
>> > > 00 (00) empty [tail]
>> > > 01 (00) empty
>> > > 02 (00) empty
>> > > 03 (00) empty
>> > > 04 (00) empty
>> > > 05 (00) empty
>> > > 06 (00) empty
>> > > 07 (00) empty
>> > > 08 (00) empty
>> > > 09 (00) empty
>> > > 10 (00) empty
>> > > 11 (00) empty
>> > > 12 (00) empty
>> > > 13 (00) empty
>> > > 14 (00) empty
>> > > 15 (00) empty
>> > > ** Tx buf (free 16, Linux netqueue STOPPED) **
>> > > ** Tx buf 29 blocks total, 29 available, free list head dd80
>> > > 00 available (82) [head] [tail]
>> > > 01 available (82)
>> > > 02 available (82)
>> > > 03 available (82)
>> > > 04 available (82)
>> > > 05 available (82)
>> > > 06 available (82)
>> > > 07 available (82)
>> > > 08 available (82)
>> > > 09 available (82)
>> > > 10 available (82)
>> > > 11 available (82)
>> > > 12 available (82)
>> > > 13 available (82)
>> > > 14 available (82)
>> > > 15 available (82)
> >
>> > > ** Generic slave data **
>> > > irq_mask d9fc irq_status 0000 irq on acx 0000 txbuf_start c10d0000,
>> > > txbuf_area_size 37536 txdesc_size 48, txdesc_start 0000ba10
>> > > txhostdesc_start c1108800, txhostdesc_area_size 896 txbuf
> > start dd80,
>> > > txbuf size 7424 rxdesc_start 0000bd10 rxhostdesc_start c391dc00,
>> > > rxhostdesc_area_size 448 rxbuf_start c1140000, rxbuf_area_size 38240
> >
>> > > ** network status **
>> > > dev_state_mask 0x0003
>> > > status 1 (SCANNING), mode 2, channel 9, reg_dom_id 0x10,
>> > > reg_dom_chanmask 0x07FF, ESSID "RCMP", essid_active 1, essid_len 4,
>> > > essid_for_assoc "", nick "acx v0.3.35"
>> > > WEP ena 1, restricted 0, idx 0
>> > > dev_addr 00:0E:7F:B5:3D:EB
>> > > bssid 00:00:00:00:00:00
>> > > ap_filter FF:FF:FF:FF:FF:FF
> >
>> > > ** PHY status **
>> > > tx_disabled 0, tx_level_dbm 18
>> > > sensitivity 176, antenna 0x8D, ed_threshold 112, cca 13,
> > preamble_mode
>> > > 2 rts_threshold 2312, frag_threshold 2346, short_retry 7,
> > long_retry 4
>> > > msdu_lifetime 4096, listen_interval 100, beacon_interval 100
> >
>> > > ** Firmware **
>> > > NOTE: version dependent statistics layout, please report if you
>> > > suspect wrong parsing!
> >
>> > > version "Rev 1.10.5.0"
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > Best regards,
> > Paul mailto:pmiscml@gmail.com
> >
> >
_______________________________________________
Kernel-discuss mailing list
Kernel-discuss@handhelds.org
https://handhelds.org/mailman/listinfo/kernel-discuss