Jump to content
3992 posts in this topic

Recommended Posts

Jalavoui, each time I test a driver version, after the test I clean up the system by this way:

1. delete the iwi3945.pkg from Library/Receipts (otherwise in Install window appears UPDATE button)

2. delete the entrance in the Library/Preferences/SystemConfiguration/NetworkInterfaces.plist (in order to have a vacancy for en1 ethernet card)

3. remove the active checked entrance PCI 8086x4222 in the Network Port Configuration and apply the changes

4. delete the extensions.kextcache and.mkext

5. delete the iwi3945.kext

6. delete the caches and logs with ONYX in order to have a clean log files

7. restart the system and remove the inactive entrance of PCI8086x4222 entrance from Network Port Configuration and apply the changes.

8. only when all these operations are performed I install a newer version.

 

One very good thing is that the Mac address of the card is the same in all the three operating systems (Vista, Linux, OSX), the one reported in the logs posted above.

I don't know if that's a reliable observation, but in the system.txt there are three lines reporting errors:

 

iwi3945: iwl_rx_handle UNHANDLED - #0x74 UNKNOWN

iwi3945: : Error wrong command queue 37 command id 0x74

iwi3945: : Read index for DMA queue (117) is out of range [0-0) 0 0

 

The UNHANDLED - #0x74 UNKNOWN shouldn't be with the code #0x47 (the native address of a generic HDD where to write RX information). I am so sorry I cannot help any deeper due to my missing knowledge in programming.

iwi3945

well...

i forgot to copy back the iokit code when i rewrite the driver

this can be the cause of bad hardware detection - it's fixed in this release

but this can be a solution for the cards that have the old ff:ff:ff bug in hardware - i really don't know

try networkselector option (1) a few times before post logs

 

you'll need to reinstall the driver as i said before for testing this

if this work you'll see your device in network preferences

iwi3945.dmg

iwi2200 logs. WEP64, automatic authentication type.Selector suggests to enter network key. It doesn't matter whether entered key is valid.Keep your good work!

 

you need to try a simpler wep configuration - the driver isn't ready yet

 

iwi3945

this is an example of a good harware detected driver in ioreg

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

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

| | | +-o pci8086,4227@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>

 

anyone get this for 4222?

 

you all know what to do when you get a kernal panic? hope so

 

from last logs i can see that the rfkill hack does not work

this mean you have to test the driver with the card powered on

this will give kernel panics - so post the pictures

i have no way to figure out how to hack the rfkill

so from now on you need to do the re-boot from windows into mac os with the card on

pay attention to logs - if you get a SW/HW rfkill - this means the driver is doing nothing

Yeah, I just need to tweak boot.plist so I can get timeout to get into -v mode to see the code then I can post the picture of it :)

 

EDIT: this is going to have to wait as my Mac OS X installation crashed trying to fix an HFS Partition Error (its gone for some reason) so I'll reinstall OS X, never know this may help me with my problems with the driver in case remnants from previous installations were still present and interfering with later releases.

Jalavoiu, thank you for your great driver for the 2200! I would like to say that WEP works only with Open authentication, and will connect with 64 or 128 bit. Shared key will not connect at all.

 

In system.log, the error I keep seeing is "iwi2200: E key mismatch" 100 times over.

 

Also, I do "sudo ifconfig en0 inet 192.168.1.108" and it works fine, but "sudo ifconfig en0 netmask 0xFFFFFF00" only generates an "Invalid Argument" error. What should broadcast be set to?

Jalavoiu, thank you for your great driver for the 2200! I would like to say that WEP works only with Open authentication, and will connect with 64 or 128 bit. Shared key will not connect at all.

 

In system.log, the error I keep seeing is "iwi2200: E key mismatch" 100 times over.

 

i don't have a way to test because i don't have the hardware.

if wep 64/128 works in open mode without bugs maybe i can write the code for the shared key (need to learn first)

do you get the key mismatch warning after associated?

Jalavoiu, thanks for the program the driver is working with my 2200 but it's really slow. Sometimes it will take forever to for something load. in addition, i can not log in to my router and it keep saying "No Internet Connection". i was wondering if there's any solution. thanks

 

Chris

i don't have a way to test because i don't have the hardware.

if wep 64/128 works in open mode without bugs maybe i can write the code for the shared key (need to learn first)

do you get the key mismatch warning after associated?

 

Yes. I have tried all 4 keys, along with the actual password itself. Same error after association.

Is there anything I can do to help...like post logs etc. for 2200. I don't really know how...

 

It does take a long time for the comp to detect the driver, connecting to unencrypted network takes a while, it will connect almost randomly though. Like if you keep clicking connect, it will sometimes "be connected" or just take a while and then returns to the SSID list screen.

 

Without Network Selector, the driver would be active for a few minutes. Maybe www.apple.com will open okay, a few pictures won't show up, and then you can go to www.google.com, but by that time, the driver will have stopped functioning.

 

We appreciate your work!

auqs10,

can you change the install script (preinstall) of iwi3945.pkg to match your install steps

i think it would be very usefull for everybody

you can delete the preupgrade - better to always do a fresh install

 

Jalavoui, I would like to make those changes in the package but you or someone else could guide me a bit on How To...

What editor should I use (PlistEdit is OK or should I use Resorcerer) and where are the lines to be changed.

 

About ioreg.txt for me is missing the third line (you mentioned) about identifying the card. I don't know why?

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

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

| | | +-o pci8086,4227@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>

Jalavoui, I would like to make those changes in the package but you or someone else could guide me a bit on How To...

What editor should I use (PlistEdit is OK or should I use Resorcerer) and where are the lines to be changed.

 

you can use textedit to edit the info.plist of iwi3945.kext

but you'll need to find a compatible device and replace the pci8086,xxxx

you don't need to do this if the interface shows up in network preferences

jalavoui,

 

I just removed and installed the latest driver you released. I recived a kernel panic on the second reboot, on the first reboot however I booted into verbose mode and watched as the rkill tried to run hundreds of times ( it was scrolling down my screen almost to fast to read), after third reboot I can log back into OS X and view the "PCI Slot XXXX" in network preferences.

 

Thank you for all the countless hours of work you have put into this project!!

 

A picture of my Kernel panic is is attached...

 

kernel_panic.zip

Jalavoui, the logs (system.txt commented) of latest driver iwi3945.dmg

Only after the third restart system didn't hag-up when associating in Network Preferences.

After that, two times I restarted the system but it hang-up when the interface was loaded.

For good association captures of the info.plist (inside iwi3945.kext) and Network Preferences list are added below.

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