Jump to content
3992 posts in this topic

Recommended Posts

can anybody help me please ... i installed drivers for my wireless from the iw4965 pkg (in leopard) file and now i can run only system in safe mode (-x) ... :blink: if i try to run it normally i get kernel panic :) how can i uninstall those drivers ? i have important things on my drive :( help please !!

1. open Terminal

 

% sudo -s

% rm -rf /System/Library/Extensions/iwiXXXX.kext (replace XXXX with your specific driver)

% rm -rf /Library/Receipts/iwiXXXX.pkg

% rm /System/Library/Extensions.*

% kextcache -k /System/Library/Extensions

 

2. Driver is now uninstalled

iwi3945/iwi4965

firmware fixes

about source code - i'll not move to mac os x 10.5. i'm using 10.4.8 kernel sources

 

iwi3945 as a bug in the snd_cmd(). when this is fixed we can jump to iwi2100 status

iwi4965 needs to have more code to work

iwi2100 is scanning, need to write code for rx/tx packets - iwi2200 source as all the code for this

iwi2200 need secure nets suport and fix the slowdown bug. i might build a new kernel to fix this since this bug also exists in macintosh computers

 

any developer help is welcome

 

Well, if you won't move to leopard, then maybe others will with the help of the code from "iwi3945". I, myself would do this, but seeing as I do not have the knowledge on how to code a driver for wireless this seems out of the question. Now i can help with testing this if anyone is willing to try it on Leopard seeing as the current dev is not willing to continue work onto 10.5

Major Bummer that 3945 is not being supported for OSX 10.5 - I would like to also help with support for this, Unfortunately my coding skills fall back to machine code on the 6502 (commodore 64) - so I think C or C# is a bit out of the question - or I have some rapid learning to do ;-), Who else would like to see development for 3945 on OSX 10.5 (it maybe worthwhile to do a poll and find out where 3945 development is really required!?) - just a suggestion.

 

I appreciate all the work you guys have been putting in especially jalavoui and also the testers!

 

Many Thanks

 

Keep up the good work.

Lets focus on getting these drivers working for Tiger before we get itching for Leo. I have a iMac Core Duo and a buddy has the new iMac core2Duo with leo on both, On a mac OEM its not stable and full of bugs. Mac needs a patch for leo as it is.

 

I am more than happy to stay with 10.4.8 until at least Leo 10.5.1 or 2 is out.

 

Waiting for the iwi3945 drivers to work with patience. Keep up the good work, PLEASE dont let the negative comments turn you off development.

 

Thanks

 

(I know that you get offers to test 1000 times, but ANYTHING a non-coder "leatch" like me can do, just say the word)

I don't get this eagerness to forget Tiger and move on to Leo, before getting things done on Tiger.

Tiger is good, stable... Leo is not. It's almost a beta OS.

Can you wait a little longer untill we have a little bit more Tiger done and an older Leo? Maybe Leo x.2?

 

Be cool

 

Well, if you won't move to leopard, then maybe others will with the help of the code from "iwi3945". I, myself would do this, but seeing as I do not have the knowledge on how to code a driver for wireless this seems out of the question. Now i can help with testing this if anyone is willing to try it on Leopard seeing as the current dev is not willing to continue work onto 10.5
I don't get this eagerness to forget Tiger and move on to Leo, before getting things done on Tiger.

Tiger is good, stable... Leo is not. It's almost a beta OS.

Can you wait a little longer untill we have a little bit more Tiger done and an older Leo? Maybe Leo x.2?

 

Be cool

 

I would not call it eagerness as much as I call it needed for my situation. Not everyone can run tiger, I have not had any luck with Tiger on my Vostro 1500, I never get to the point where I can even install Tiger, KP's abound, but I managed to get Leo on it, with everything but the NV 8600 GT and 3945 Wireless working, so although more development is needed for Tiger, I would not stop development on Leo. But then again I am biased

Bonjour ^^

Sorry for my bad english :rolleyes:

My wifi card is a intel 2200bg, i download the latest driver and install...everything is ok...

 

wifi2cu8.th.png

 

Tested with WAP2, WAP :

 

wifiqk8.th.png

 

The connexion is active...but no internet :(

 

With WEP :

 

wifi3vm1.th.png

 

 

I don't understand ? all is good ? i know network with wep or wap doesn't work, but the connexion is ok so i hope ^^

 

Do you have any solution or for the moment the project is off for 2200bg drivers ?

 

Thanks a lot ;)

To be hoist with everyone there nothing wrong with tiger, as other people are saying there are less issues with tiger and more support, I myself havn't had many issues with tiger and seems very stable so i dont think im gonna bother moving over to leo as everything i use seems to work great. The morrel of this story is "why fix it if its not broke".

 

keep up the good work jalavoui, you have my suppot for development of the iwi3945 driver on tiger.

I would not call it eagerness as much as I call it needed for my situation. Not everyone can run tiger, I have not had any luck with Tiger on my Vostro 1500, I never get to the point where I can even install Tiger, KP's abound, but I managed to get Leo on it, with everything but the NV 8600 GT and 3945 Wireless working, so although more development is needed for Tiger, I would not stop development on Leo. But then again I am biased

 

I understand your reasons. I truly do, but the thing is jalavoui is working on a Tiger based project and on this stage of development it would be a waste of resources and time to start another project from scratch.

 

No matter what Jalavoui's option is we should support him. After all, it's his project and his work. Not ours.

iwi3945/4965

tx queue fix

 

for developers

you might fix the bug in iwi3945/4965 doing this:

define

static struct iwl_priv priv0;

check iwi2200 code to see where it is used

to make this work you'll need to apply some fixes - easy if you have any of this cards

 

iwi2200

the driver only works for wep networks

if you get 169.254.xxx.xxx them it doesn't work - try to change it in networkpreferences

i haven't write code for hexadecimal wep keys - use simple passwords for now

only open mode is allowed - no shared key association enabled

iwi3945.dmg

iwi4965.dmg

ok now Im trying to send the log files of the latest 2100 driver (thanks to the people who helped me), but I dunno why safari and firefox give an error when I try to attach them, saying no file selected, oops :) I presume I only cause trouble, but Im willing to get this files here, I'll figure out soon..

 

Edit:OK here they are, I'll check the thread and post the new logs as fast as possible. thnks

ioreg.txt

ioreg.txt

system.txt.zip

uk_rules_ok,

the driver seems to stop getting firmware errrors after a few on/off retries

i'll put a module parameter in next build to test this

if your card as a wireless switcher, does it work? check if you get any log message when pressing it

 

jajajaja,

can you post a ngui picture scanning networks?

 

sfxc13,

does your card have a wireless switcher?

iwi3945

 

add param_timer - this is the code:

while (priv->status & STATUS_HCMD_ACTIVE)

{

rc++;

IODelay(HOST_COMPLETE_TIMEOUT);

if (rc==param_timer) break;

}

if param_timer=1000 them this will be done 1000 times

 

check in the iwi3945.kext for the info.plist file

after changing this value

delete /System/Library/Extensions.kextcache and Extensions.mkext (this is important if you miss this mac os will ignore your changes in the info.plist)

reboot

open console and look at system.log

press option 1 of networkselector a few times

 

if you don't get errors while sending commands - you find a good timer value - let me know what is it

otherwise try other values for param_timer

 

iwi2100

this version as much less debug msg

this way i can understand what the driver is doing

changed is_rx function

i don't know if networkselector works - i hope nsgui is working since it's much better for testing

if you get a kernel panic - boot with -s and use networkselector

 

eddie - where are you? you should be writting this code

 

iwi4965

add less debug msgs

i still don't understand where the driver is failing

iwi2100.dmg

iwi3945.dmg

iwi4965.dmg

To get logs run the attached file after testing.

To test:

Install

Restart

Run Network Selector

press 1

press 1

press 1

press 5

run getlogs.command

check logs to see whether card is on or off

if the card is off then run network selector and press 1 to turn card on, press 5

then open network in system preferences.

add any relevant comments when you post the logs

 

for a good example see aquas10 post:

http://forum.insanelymac.com/index.php?sho...mp;#entry500995

logs from #3547

4965

 

jalavoui: I have a switch on the outside of my laptop. Is there something specifically I should be doing with it?

 

Used it to get a restart on this test.

 

logs attached

 

dmesg is blank from last attempt to getlogs

ioreg.txt

system.txt

OK here are the log files for the latest build of 2100 driver, the dmg posted yesterday.

 

The network selector window does not crash with this one (the previous version crashed right after it found the wireless network).

 

But still, when I click connect, it just returns to the network selector and continues scanning, so it does not connect.

 

Also the SS of the ngui, hope this is what you asked. ;)

dmesg.txt

ioreg.txt

system.txt.zip

4.tiff

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