Jump to content
3992 posts in this topic

Recommended Posts

i find out what's happening with the cards that don't get detected in ioreg as pci8086,xxxx

that happens because of shared irqs - this mean that the driver receivs interrupts of other devices!!!

this can cause the driver to fail since i have no code to filter the interrupts from other devices!!

can someone do a search on this subject - the driver will not work properly for those cards until this is fixed

although ther'es some code to filter the interrupts from other drivers iwi3945 will be much slower this way

 

iwi3945

 

I was wondering if this helps:

 

"So what I did was use IOFilterInterruptEventSource to register a primary that always returned

false so that the dummy secondary was never called. So instead of

returning true to accept the interrupt and trigger a secondary, i have

preexisting IOInterruptEventSources registered that i trigger manually. In

my case, i registered multiple IOInterruptEventSources with the workloop

(here you could have two workloops and an IOInterruptEventSource registered

in each with a NULL provider - meaning you will manually trigger this

secondary with a call to interruptOccurred()). This way i could use the

primary to determine the type of interrupt and run a corresponding

secondary by calling interruptOccured()."

 

I found this on the internet (someone else looking for help writing drivers)

iwi3945

add a simple filter for interrupts

add register service with exclusive option

 

if you get that bogus interrupt them this doesn't work

 

anyone online to post logs?

 

 

still not working, heres the logs jalavoui :-

iwi3945

can someone with a 0x42278086 card post logs?

you do know that the card must be tested powered on and the you need to try option 1 of networkselecor a few times before making the log files. - previous logs show that doing this helps skip the interrupts bug

 

the ndiswrapper is nice but i guess it depends to much on the linux kernel to be ported to mac os x

 

 

i've written the same code i'm using for iwi2200 into iwi3945 interrupt call handler

i have no idea why iwi3945 interrupts hangs but if this happens:

just use networkselector option (1) a few times until you see in system.log that the driver is receiving interrupts (check for "alive received")

iwi3945.dmg

Hi Jalavoui, here are logs and captures under single user mode. The lines that appear between last command and Kernel Panic are not recorded in logs. There were 2-3 screens of lines when trying with option 1 in Network Selector to turn on the card (meaning second hit of option 1 in Network Selector in single user mode).

Logs attacehd, and comments included in system.txt with specific indications of the captures shot for different stages.

Still not included the line in ioreg.txt where should appear PCI8086x4222 (before darwin_iwi3945).

iwi3945

can someone with a 0x42278086 card post logs?

you do know that the card must be tested powered on and the you need to try option 1 of networkselecor a few times before making the log files. - previous logs show that doing this helps skip the interrupts bug

 

the ndiswrapper is nice but i guess it depends to much on the linux kernel to be ported to mac os x

 

 

i've written the same code i'm using for iwi2200 into iwi3945 interrupt call handler

i have no idea why iwi3945 interrupts hangs but if this happens:

just use networkselector option (1) a few times until you see in system.log that the driver is receiving interrupts (check for "alive received")

 

ok loaded the latest driver tryed networkselestor but after a few times it crashes, heres my logs :-

Hi there, I have a toshiba laptop with an ipw3945 card in it. I'd like to help out with the development of this project however my only contribution would be to supply logs for troubleshooting. I've been reading this thread and am wondering if there are docs on what is required as far as logs and exactly what is needed other than installing the dmg and network selector. I read some of the posts here and a lot of them say to refer to previous posts for instructions however given that this topic has close to 150 pages that makes figuring out how to help harder than actually helping. I am sure you would get more help from users if the instructions were easier to locate. This project could benefit by those involved the most on this topic having something in their signatures pointing to a howto on posting logs and anything else needed. I see a lot of "boot -s etc as in previous posts" being used by jalavoui. I have honestly searched for previous posts with this information but after reading 10-15 pages looking for the info I pretty much gave up. I am sure I am not the only one this has happened to either. If the information was available I guarantee you'd have more help in troubleshooting for this project.

 

Hopefully all of what I have written is taken as constructive comments and not negative criticism. I, like anyone that is reading this topic, only want a working wifi card and I'm just trying to help out where I can. I'd even write a howto if needed but of course I'd first need to know how to do it.

Hi, can someone please help me by giving some ideas. I think I am almost there, but am missing something. I tried to install the driver (the last version from the forum, but this occurs on all latest versions) on a Intel 2200BG MINIPCI. The driver is loaded, though the card is not visible under Network. The NetworkSelector gives "Could not get ID for kernel control.2". So I guess the card is not connected to the driver (?). I added 0x27028086 to the string under IOPCIMatch in de plist (as mentioned in Windows) in iwi2200.kext/Contents/info.plist and restarted. But still the same problem. I saw the integer under p_disable is set to 1, I tried to set this on 0. I thought maybe it would "enable" PCI-support. No effect.

 

Hope someone can help me. Thanks in advance! p_up.gifp_middot.gifp_report.gif

p_delete.gif

iwi3945

removed cmd validation

to test this:

boot with -s, etc,etc

try networkselector option 1 until you get a kernel panic

take a picture of the screen and post it

 

Geneman,

post your ioreg.log so i can check it

 

howto make logs that really help developing this driver:

see system.log/pictures in this

http://forum.insanelymac.com/index.php?s=&...st&p=485257

if you all do this i can do a much better work

iwi3945.dmg

hi Jalavoui,Sorry, I thought my question was not logs-related else I would have included it immediately. Hereby my files:If you need more info, or testing then please request.Thank you!

my guess is you should reinstall mac os x

you have a 0x42208086 card - same as mine

should work with no problemsi

 

wi3945

fix for last panic picture

iwi3945.dmg

my guess is you should reinstall mac os x

you have a 0x42208086 card - same as mine

should work with no problemsi

 

Thank you for your answer! I reinstalled it already, but I will do it again (10.4.9). But maybe I have to install something extra or actually shouldn't install something? The one at code.google should just work by installing, rebooting?

dmesg.txt

ioreg.txt

system.txt

iwi3945

check if this version doesn't loose the mac address

i figured out why the driver fails receiving interrupts at startup - trying to fix

try a few times networkselector option 1

 

thanks for posting fast logs - maybe i can finish this today

iwi3945.dmg

HI Jalavoui, during the time you have uploaded two more versions I was testing the one from post #3213.

I know it is a kind of redundant, but perhaps some good things appear from the logs and image captures. Same comments are included in system.txt.

Here is already over midnight, so only tommorow I can check the newest version, sorry.

hi jalavoui,

 

I reinstalled MacOS without any extras only the VGA-driver and AGPGart 2.2. Still the same error with network selector. I see in system.txt :

Oct 29 22:01:59 localhost kernel[0]: iwi2200: disable 1 led 0 mode 0

Oct 29 22:01:59 localhost kernel[0]: iwi2200: E darwin_iwi2200 map is zero

Oct 29 22:01:59 localhost kernel[0]: iwi2200: W TODO: Free

Is that right?

dmesg.txt

ioreg.txt

system.txt

heres the logs, ./networkselector wont run from root with -s option even though its there ? weird !!

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