Jump to content
3992 posts in this topic

Recommended Posts

delete /System/Library/Extensions.kextcache and Extensions.mkext and reboot

 

might have to do this twice

 

boot with -s and try to use kextload

 

if previous versions work with your card this one must work

 

done - but no success.

 

btw: I tried rev228 again and it does work (kext loaded, led is on etc, but not connected to any network).

 

so something happened when you removed Airport stuff...

no... not yet...

i'm still working on taking out all the unnecessary parameters...

perhaps this is why we have the memory leak...

 

are you sure it is a memory leak ? cause i had stable memory usage during upload/download and even after crash.

 

 

just tested!.. still detected as pci ethernet pci8086,4222.

 

no wifi leds on.. fn+f2 no working too.. only bluetooth.

 

im here to test right way!!

 

regards,

 

don't use fn+f2 to activate the card, try and use network selector.

networkSelector.zip

no... not yet...

i'm still working on taking out all the unnecessary parameters...

perhaps this is why we have the memory leak...

 

are you sure it is a memory leak ? cause i had stable memory usage during upload/download and even after crash.

don't use fn+f2 to activate the card, try and use network selector.

 

tested.

 

iDell:~/Desktop root# ./networkSelector

ZeroLink: could not load .o file: /Users/asafalgawi/networkSelector/build/networkSelector.build/Debug/networkSelector.build/Objects-normal/i386/main.ob

Bus error

 

regards,

so something happened when you removed Airport stuff...

 

this is what i get for iwi2100:

 

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: disable 0 mode 0

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: darwin_iwi2100 iomemory length: 0x80000 @ 0xb0080000

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: darwin_iwi2100 virt: 0x201ff000 physical: 0xb0080000

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: darwin_iwi2100 IRQ: 16, Vendor ID: 8086, Product ID: 2592

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: ipw2100_queues_allocate.

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : Detected Intel PRO/Wireless 2100 Network Connection

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: fw version 769 s: 201050 uc s:8128

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: disable 0 mode 0

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: darwin_iwi2100 map is zero

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: TODO: free

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : sw_reset_and_clock failed: -5

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : ipw2100_verify failed: -5

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : : Error initializing Symbol

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : : Error loading microcode: -5

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : : sw_reset_and_clock failed: -5

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: initializing bd queue at virt=0x1b479000, phys=117a4000

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: initializing bd queue at virt=0x1b49e000, phys=1e089000

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: Waiting for f/w initialization to complete...

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: f/w initialization complete: SUCCESS

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: table 1 size: 0

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: table 2 size: 0

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : ordinal 204 neither in table 1 nor in table 2

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: failed querying ordinals at line 2846

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : : Failed to determine HW features.

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: wrong table

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : : Failed to clear ordinal lock.

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: : ordinal 1001 neither in table 1 nor in table 2

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: MAC address read failed

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: darwin_iwi2100 attach failed

Mar 21 19:30:19 Macx86 kernel[0]: iwi2100: TODO: free

 

and i don't have the card...

 

there's something wrong with it

 

anyone else is using iwi2100?

jalavoui, if a function does not recieve parameters, what value whould i put in in the te tx queue functions ?

 

tested.

 

iDell:~/Desktop root# ./networkSelector

ZeroLink: could not load .o file: /Users/asafalgawi/networkSelector/build/networkSelector.build/Debug/networkSelector.build/Objects-normal/i386/main.ob

Bus error

 

regards,

 

oops, didn't know that on debug mode it doesn't do the linking...

here you go... try this version:

networkSelector.zip

are you sure it is a memory leak ? cause i had stable memory usage during upload/download and even after crash.

 

depending os you pc memory. i have 512M

 

if u download a cd image file (700M) mac os freezes at 170M download (1GB mem should crash higher)

 

previous iwi versions cause a kernel panic

 

new versions just freezes mac os - can't open any app

 

and the memory (activity monitor) increases until mac os freeze

 

this can also be because of my os x install. i'm on the 10.4.9

 

this bug as happen for other users (see previous posts)

i know... happned to me too...

maybe it is due to the moving of the "priv" parameter but it is a longshot... really really really longshot...

anyways... once i finish removing all these "priv"s i'll the modified kext here... if it will work, we will add it to svn

 

hmmm...

looks like i forgot something in the app...

a new ipw3945 will be out soon... hopefully this one will work with network selector...

hmmm i don't know... ipw_scan for example...

it gets priv as a parameter, and i'm removing them from the functions parameters list, for all the functions... so what should i put in as a parameter for the queue functions (they recieve function name, and the parameters for the function)

maybe it is due to the moving of the "priv" parameter but it is a longshot... really really really longshot...

 

the "priv" from iwi3945 is not the same as iwi2200

 

iwi3945 uses a different ieee -> mac80211-4.0.4

 

it uses code from iwlwifi-0.0.10 and ipw3945.h to define "priv"

 

this is a mess, but i'm trying to use iwi2200 functions on iwi3945 (instead of write a new driver code)

jalavoui, i was talking about iwi2200...

i'm removing unneccesary stuff from it (un-needed parameters, i think...)

 

iwi3945:

new version, this one should work with network selector (only power up for now, and even that is not sure)

iwi3945.zip

hmmm i don't know... ipw_scan for example...

 

:P

 

ok. i understand

 

yes you can remove all priv from that functions - the declaration isn't used

 

because the priv reference is already inside them - this will fail if defining static functions

 

this will allow to pass other params to qeue_te (or null if no params)

for example for ipw_scan, qeue_te can have the param IW_SCAN_TYPE_ACTIVE or PASSIVE

jalavoui, i was talking about iwi2200...

i'm removing unneccesary stuff from it (un-needed parameters, i think...)

 

iwi3945:

new version, this one should work with network selector (only power up for now, and even that is not sure)

 

worked.. hummm.. dont know

 

iDell:~/Desktop root# ./networkSelector

Wellcome to the insanelyMac SpacePort 0.1

 

1) Activate NIC

2) Network List

3) Close Program

 

Enter Option: 1

 

Wellcome to the insanelyMac SpacePort 0.1

 

1) Activate NIC

2) Network List

3) Close Program

 

Enter Option: 3

 

iDell:~/Desktop root#

 

no wifi leds on, only blue led from bluetooth

no bluetooth kext..

and still detecting pci ethernet.

log attatch.

 

regards,

dmesg.txt

ioreg.txt

system.txt

thats what i thought would happen...

maybe the card is getting powered this way, but there is no way to know, since i has to associate to a network for the leds to lit.

but still, just to know that it don't crash is good thing :P

 

we still need to work on scanning and associating for the 3945 and 2100, then we will know what the hell goes on there...

 

just a sec !!!!!

i think the card is powerd !! it does scanning ! i don't think it did it before...

 

do you think you could upload a dmesg output of 2min after boot without touching network selector.

and then 2min after powering the card with network selector ?

worked.. hummm.. dont know

 

moseschrist

 

the driver is cycling thru enable/disable

 

need to call ipw_rfkill()

 

this should be called every time power state change

 

also need to write code for ipw_down()

 

 

fullOut,

 

all iwi drivers are detected as pcixxx devices - no more airport

 

when you press the (1) the card is powered on/off - open the console and try this.

 

you should see in the log that it calls enable - should not cycle unless you press twice the (1)

 

before pressing (1) check in log if the card is already on. if so, pressing (1) will power off the card!

thats what i thought would happen...

maybe the card is getting powered this way, but there is no way to know, since i has to associate to a network for the leds to lit.

but still, just to know that it don't crash is good thing ;)

 

we still need to work on scanning and associating for the 3945 and 2100, then we will know what the hell goes on there...

 

just a sec !!!!!

i think the card is powerd !! it does scanning ! i don't think it did it before...

 

do you think you could upload a dmesg output of 2min after boot without touching network selector.

and then 2min after powering the card with network selector ?

sure..

here it is..

dmesg_with_netsel.txt

dmesg_after_boot.txt

moseschrist

 

the driver is cycling thru enable/disable

 

need to call ipw_rfkill()

 

this should be called every time power state change

 

also need to write code for ipw_down()

fullOut,

 

all iwi drivers are detected as pcixxx devices - no more airport

 

when you press the (1) the card is powered on/off - open the console and try this.

 

you should see in the log that it calls enable - should not cycle unless you press twice the (1)

 

before pressing (1) check in log if the card is already on. if so, pressing (1) will power off the card!

 

i don't think it will power it off... at least i never managed to power it off here...

i also don't think it powers on, but only makes the driver think it is, because i don't see any "action" in

the ipw_rf_kill() function in 3945. should be a call for restart function. at least this is how it works on 2200...

same as mine, my system is 10.4.9 kernel 8.9.1, I deleted bluetooth kexts and turned wireless on with the button before executing the script.

 

Wellcome to the insanelyMac SpacePort 0.1

 

1) Activate NIC

2) Network List

3) Close Program

 

Enter Option: 1

 

Wellcome to the insanelyMac SpacePort 0.1

 

1) Activate NIC

2) Network List

3) Close Program

 

Enter Option: 2

 

Available Networks:

 

 

Wellcome to the insanelyMac SpacePort 0.1

 

1) Activate NIC

2) Network List

3) Close Program

 

Enter Option:

*****

iwi3945: IPW_INTA_BIT_RF_KILL_DONE

Press wireless button to turn interface on

iwi3945: request scan called when driver not ready.

*****

Guest
This topic is now closed to further replies.
×
×
  • Create New...