NetStumbler.org Forums

Go Back   NetStumbler.org Forums > Software > Unix/Linux
Reload this Page linux-wlan-ng-0.2.1-pre26 and NL-2511
Register Search Today's Posts Mark Forums Read

Closed Thread
 
LinkBack Thread Tools Display Modes
Old 03-25-2005   #1 (permalink)
kimbell
Registered Member
 
Join Date: Jan 2005
Posts: 38
Post linux-wlan-ng-0.2.1-pre26 and NL-2511
Quote:
Originally Posted by tekn0
kimbell, I think you might want to move your question to a new thread because this is getting a little off topic for this one, you will probly get more help if you started a new one.
What is up with this?
(Auditor HD install and linux-wlan-ng-0.2.1-pre26 DMESG)
prism2_cs: Ignoring new-style parameters in presence of obsolete ones //Why is this being ignored?
prism2cs_init: prism2_cs.o: 0.2.1-pre26 Loaded
prism2cs_init: dev_info is: prism2_cs
prism2_cs: index 0x01: Vcc 3.3, irq 3, io 0x0140-0x017f
PDA Read from 0x007f0000 in NV space.
PDA Read from 0x007f0000 in EXTDS space.
Writing 2590 bytes to ram @0x7e0000 // why is it writing to ram here
Writing 2268 bytes to ram @0x7e0b00
Writing 2 bytes to ram @0x7e17fe
Writing 4096 bytes to ram @0x7e17fe
Writing 4096 bytes to ram @0x7e27fe
Writing 4096 bytes to ram @0x7e37fe
Writing 4096 bytes to ram @0x7e47fe
Writing 4096 bytes to ram @0x7e57fe
Writing 4096 bytes to ram @0x7e67fe
Writing 4096 bytes to ram @0x7e77fe
Writing 4096 bytes to ram @0x7e87fe
Writing 4096 bytes to ram @0x7e97fe
Writing 4096 bytes to ram @0x7ea7fe
Writing 4096 bytes to ram @0x7eb7fe
Writing 4096 bytes to ram @0x7ec7fe
Writing 4096 bytes to ram @0x7ed7fe
Writing 676 bytes to ram @0x7ee7fe
Writing 4096 bytes to ram @0x7f0800
Writing 3282 bytes to ram @0x7fe000
ident: nic h/w: id=0x800c 1.0.0
ident: pri f/w: id=0x15 1.1.4 //Why has this changed
ident: sta f/w: id=0x1f 1.8.3 //This also
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=4/5
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/15
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: 00049231176\x0a //Isn't this the NL-2511 card
prism2_cs.o: 0.2.1-pre26 Unloaded
p80211.o: 0.2.1-pre26 Unloaded
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0820-0x08ff: clean.
cs: IO port probe 0x0800-0x080f: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x220-0x22f 0x250-0x257 0x260-0x267 0x330-0x337
0x378-0x37f 0x388-0x38f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
prism2_cs: Ignoring new-style parameters in presence of obsolete ones
prism2cs_init: prism2_cs.o: 0.2.1-pre26 Loaded
prism2cs_init: dev_info is: prism2_cs
prism2_cs: index 0x01: Vcc 3.3, irq 3, io 0x0140-0x017f
PDA Read from 0x007f0000 in EXTDS space.
PDA Read from 0x007f0000 in EXTDS space.
Writing 2590 bytes to ram @0x7e0000
Writing 2268 bytes to ram @0x7e0b00
Writing 2 bytes to ram @0x7e17fe
Writing 4096 bytes to ram @0x7e17fe
Writing 4096 bytes to ram @0x7e27fe
Writing 4096 bytes to ram @0x7e37fe
Writing 4096 bytes to ram @0x7e47fe
Writing 4096 bytes to ram @0x7e57fe
Writing 4096 bytes to ram @0x7e67fe
Writing 4096 bytes to ram @0x7e77fe
Writing 4096 bytes to ram @0x7e87fe
Writing 4096 bytes to ram @0x7e97fe
Writing 4096 bytes to ram @0x7ea7fe
Writing 4096 bytes to ram @0x7eb7fe
Writing 4096 bytes to ram @0x7ec7fe
Writing 4096 bytes to ram @0x7ed7fe
Writing 676 bytes to ram @0x7ee7fe
Writing 4096 bytes to ram @0x7f0800
Writing 3282 bytes to ram @0x7fe000
ident: nic h/w: id=0x800c 1.0.0
ident: pri f/w: id=0x15 1.1.4
ident: sta f/w: id=0x1f 1.8.3
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=4/5
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/15
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: 00049231176\x0a
linkstatus=ASSOCFAIL (unhandled)
hfa384x_copy_to_bap4: copy_to_bap() failed.
hfa384x_docmd_wait: hfa384x_cmd timeout(1), reg=0xffff.
prism2_cs.o: 0.2.1-pre26 Unloaded
p80211.o: 0.2.1-pre26 Unloaded
prism2_cs: Ignoring new-style parameters in presence of obsolete ones
prism2cs_init: prism2_cs.o: 0.2.1-pre26 Loaded
prism2cs_init: dev_info is: prism2_cs
prism2_cs: index 0x01: Vcc 3.3, irq 3, io 0x0140-0x017f
PDA Read from 0x007f0000 in EXTDS space.
PDA Read from 0x007f0000 in EXTDS space.
Writing 2590 bytes to ram @0x7e0000
Writing 2268 bytes to ram @0x7e0b00
Writing 2 bytes to ram @0x7e17fe
Writing 4096 bytes to ram @0x7e17fe
Writing 4096 bytes to ram @0x7e27fe
Writing 4096 bytes to ram @0x7e37fe
Writing 4096 bytes to ram @0x7e47fe
Writing 4096 bytes to ram @0x7e57fe
Writing 4096 bytes to ram @0x7e67fe
Writing 4096 bytes to ram @0x7e77fe
Writing 4096 bytes to ram @0x7e87fe
Writing 4096 bytes to ram @0x7e97fe
Writing 4096 bytes to ram @0x7ea7fe
Writing 4096 bytes to ram @0x7eb7fe
Writing 4096 bytes to ram @0x7ec7fe
Writing 4096 bytes to ram @0x7ed7fe
Writing 676 bytes to ram @0x7ee7fe
Writing 4096 bytes to ram @0x7f0800
Writing 3282 bytes to ram @0x7fe000
ident: nic h/w: id=0x800c 1.0.0
ident: pri f/w: id=0x15 1.1.4 //here it is agian
ident: sta f/w: id=0x1f 1.8.3
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=4/5
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/15
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: 00049231176\x0a
My 'cardinfo' now reads "I-Gate 11m PC Card " . Why the change in the card name? Also new firmware is loaded.
__________________
(I get this as what is expected when I boot off the CD)
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:00:11.0[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:11.0 [0e11:b121]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:11.0, mfunc 0x01001c72, devctl 0x64
Yenta: ISA IRQ mask 0x0498, PCI irq 11
Socket status: 30000010
ACPI: PCI interrupt 0000:00:11.1[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:11.1 [0e11:b121]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:00:11.1, mfunc 0x01001c72, devctl 0x64
Yenta: ISA IRQ mask 0x0498, PCI irq 11
Socket status: 30000010
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0820-0x08ff: clean.
cs: IO port probe 0x0800-0x080f: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x100-0x107 0x220-0x22f 0x250-0x257 0x260-0x267 0x330-0x337 0x378-0x37f 0x388-0x38f 0x3e8-0x3ff 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0xa0000000-0xa0ffffff: clean.
hostap_crypt: registered algorithm 'NULL'
hostap_cs: 0.2.6 - 2004-12-25 (Jouni Malinen <jkmaline@cc.hut.fi>)
hostap_cs: setting Vcc=33 (constant)
hostap_cs: CS_EVENT_CARD_INSERTION
hostap_cs: setting Vcc=33 (from config)
Checking CFTABLE_ENTRY 0x01 (default 0x01)
IO window settings: cfg->io.nwin=1 dflt.io.nwin=1
io->flags = 0x0046, io.base=0x0000, len=64
hostap_cs: Registered netdevice wifi0
hostap_cs: index 0x01: Vcc 3.3, irq 3, io 0x0140-0x017f
prism2_hw_init: initialized in 239 ms
wifi0: NIC: id=0x800c v1.0.0
wifi0: PRI: id=0x15 v1.1.1
wifi0: STA: id=0x1f v1.7.4
wifi0: registered netdevice wlan0
__________________
kimbell is offline  
Old 03-25-2005   #2 (permalink)
Dutch
Humourless EuroMod.
 
Dutch's Avatar
 
Join Date: Mar 2004
Location: City of Mermaids, Denmark
Posts: 6,813
Try the Auditor support site, and the wlan-ng support site.

This has to do with configuring your system, not anything to do with Netstumbler nor Wireless network auditing.

Dutch
__________________
All your answers are belong to Google. SEARCH DAMMIT!
Warning. Warning.
Low C8H10N4O2 level detected. Operator halted....
Dutch is offline  
Closed Thread

« Trouble with Senao NL-2511CD Plus EXT2 | I cracked my own WEP »

Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Google
 
Web NetStumbler.org

All times are GMT -7. The time now is 10:45 PM.

Contact Us - NetStumbler.org - NetStumbler.com - Online Backup - Archive - Top

Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0 ©2007, Crawlability, Inc.


All messages express the views of the author and are for entertainment purposes only. Netstumbler.org cannot be held responsible for the authenticity of the content or the actions of its members. By using this site and its services, you warrant that you will not post any messages that are discriminating, obscene, hateful, threatening, or otherwise violates any laws and you release Netstumbler.org from any future claims of any kind whatsoever including, but not limited to, addiction and loss of productivity. All forum messages, private messages and any other content are properties of Netstumbler.org. Even if publicly available, personal or copyrighted information are not to be posted without the consent of the owner. Distribution of licensed and copyrighted materials in any way not endorsed by the copyright owner is strictly prohibited. You may not use this site and its resources to spam other sites or individuals or perform any action that violates any law. Items sold or bought in the For Sale forum are sold as is and no warranty or insurance of any kind is provided. Netstumbler.org cannot be held responsible for the outcome of any transactions and no warranty of any kind is provided, either express or implied. Vulgar words are not allowed in the subject lines ; they may be used in the message body in any forum. The Administrator, Super Moderators and Moderators of Netstumbler.org have the right to remove, edit, move or close any thread for any reason and to reveal your identity and other known information in the event of a complaint or legal action arising from any message posted by you.