Jump to content
3992 posts in this topic

Recommended Posts

http://code.google.com/p/iwidarwin/

 

iwi2100 rev 372

 

iwi3945 rev 373

 

if this give kernel panic, boot with -s and post the picture

 

if this happens please don't send logs - they're usefull in this situation

 

at this point i think iwi2100 as better chances to work, iwi3945 will take more time

 

another issue when getting panic

 

reboot with -s

 

allways do fsck -fy

 

if this fails to fix bugs you'll have to reinstall mac os - this use to happen to me a lot

 

to fix this i managed to rebuild the mac os x ppc diskwarrior cd and make it work for mac os x86

 

this is a good solution because it allows to fix bugs that fsck can't

 

networkselector

 

i find a bug when showing network list in a place it just one network - it just don't show up

the fix is to use the "wireless button" to connect (without calling networkselector)

this happens only for some networks - can someone confirm this?

 

please post a picture of boot with -s option :)

jalavoui

 

First of all, thank you for taking on this project and for making your work public.

I'm sorry but I need to ask a dumb question. I cannot find a definitive answer in this thread.

I have been to the Google code site, sourceforge, and even the wordpress blog.

 

Which cards need which versions of which kexts/framworks?

[EXAMPLE] 2100BG needs io80211.kext v10.4.7 and apple80211.framework v10.4.5 [EXAMPLE]

[EXAMPLE] 3945ABG needs io80211.kext v10.4.8 and NO framework [EXAMPLE]

 

I have Dell E1505, 3945ABG, 10.4.9 w/semthex(?) 8.9.1 -> netkas 792.18.15~1

I am really good with C but I do not know anything about kexts except plist ;)

I really want to help write/debug code, interpret logs, etc.

 

THANKS!!!

iwi3945 rev 373

no panic no crash......................no address :unsure:

 

for those who get somiliar logs like these:

 

+-o RP03@1C,2 <class IOPCIDevice, registered, matched, active, busy 0, retain count 10>

| | | +-o IOPCI2PCIBridge <class IOPCI2PCIBridge, registered, matched, active, busy 0, retain count 8>

| | | +-o PXS3@0 <class IOPCIDevice, registered, matched, active, busy 0, retain count 10>

| | | +-o darwin_iwi3945 <class darwin_iwi3945, registered, matched, active, busy 0, retain count 7>

| | | +-o IOEthernetInterface <class IOEthernetInterface, registered, matched, active, busy 0, retain count 10>

| | | +-o IONetworkStack <class IONetworkStack, registered, matched, active, busy 0, retain count 9>

| | | +-o IONetworkStackUserClient <class IONetworkStackUserClient, !registered, !matched, active, busy 0, retain count 5>

 

this means that there's no hardware in the computer compatible with iwi driver and it will never load.

this is also the reason of getting the driver try to free message

 

check ioreg for 8086 devices

 

go into windows, linux and find the vendor/card id

 

without this the driver will never load - put the right vendor id in info.plist of iwi3945.kext (check if it exist in ioreg log)

 

looks like some iwi cards are not set as 8086 (intel) devices

 

 

iwi3945 rev 376

 

this fixes last panic log message

 

 

iwi2200

since the driver reaches a stable status, it's time to put it in the insanelymac hardware list - anyone who admin iwidarwin can do this for the team?

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