Intel Wireless driver

[jalavoui]

3. Rename iwi3945.dmg to iwi3945_rev235.dmg

if i do this i'll have to delete old releases from svn

if i keep the name "iwi3945.dmg" i can check any release using svn commands

i'll just keep posting here the release version

 

iwi3945

check system preferences - network

you might need to remove old iwi3945 interfaces - this is caused by the mac address 00:00:00:00:00 - it's a bug

 

Do you think if it could help when I reinstall the computer completely?

Does someone else have an acer wlan switcher?

Does it work for you in mac os?

you should reinstall windows. might fix your problem

i have the travelmate 4100 with the switcher - works fine in windows, mac os and linux

[pkmgarf]

Sorry, I didn't take the time to read through all 133 pages, but I scanned the first fifteen or so. Can someone bring me up to speed on how this is going? Working? Not?

 

Also, I have a Tosh laptop that I'll be dual booting Vista Ulti (or XP Pro...haven't decided) along with OSX, so it would be really, really cool to have a driver that I can use the Intel 4965 with....

[Evil_Cartman]

iwi3945

check system preferences - network

you might need to remove old iwi3945 interfaces - this is caused by the mac address 00:00:00:00:00 - it's a bug

Before installing rev 491 I have no other iwi3945 interfaces on my system.

Anyway, deletion of an existing "PCI Ethernet Slot pci8086,4222" didn't solve the problem with mac address.

[spu]

Hi Jalavoui,

 

I've reinstalled the windows xp, in which the card and the switcher worked well. The wlan card was installed, but cannot be used, because windows said that it has no electricity power. Unfortunately the switcher still doesn't work in windows or mac os. The card can be powered on in mac os by nsGUI, but not by the switcher.

 

Is there another way without using the switcher to change the "radio on/off" values?

 

Thanks a lot.

spu

[jhnez]

I tried osx again today, and the 3945abg drivers, but they did not work hope they will soon, if you needd me to test stuff let me know

[moseschrist]

jalavoui, i don't know if we should let users download the dmg from the svn,

this way we can't upload unstable and test versions of already working drivers.

 

for example, now i'm working on the whole wep encryption and if i want to upload a WIP i can't because then the users will download a WIP

and that won't be nice for them since it crashes a lot !!!

so i believe that for the iwi2200 driver we should put a "stable" version link and a WIP [unstable, SVN] version link.

for the others since they arn't working at the moment there should be only an SVN link.

 

anyways... i'm kinda stuck on this whole thing...

i'm having a problem finding the public key inside the packet, this is since there should be a call for (mbuf_pullup() ) before the decryption, but i have no what values should i send so i'm pretty much guessing and for now i think i managed to reach 2/3 of the public key [hurray for me !] which may sound great but it's basicly 2 chars out of 3... while the rest should be inserted by the user.

 

the good news are that i believe i found a way to insert the key, but first we need to make sure crypt/decrypt works.

 

as usual, ideas,thoughts, sexual offers, they are all wellcome

[JustJoe]

jalavoui, i don't know if we should let users download the dmg from the svn,

this way we can't upload unstable and test versions of already working drivers.

 

for example, now i'm working on the whole wep encryption and if i want to upload a WIP i can't because then the users will download a WIP

and that won't be nice for them since it crashes a lot !!!

so i believe that for the iwi2200 driver we should put a "stable" version link and a WIP [unstable, SVN] version link.

We're on the same page, Moses. Last week I set up the iwidarwin home page to do exactly that. The unstable(testing) versions link to the SVN tree while the stable(working) versions link to the download section where we keep the good ones.

 

I just changed the wording on the homepage to be more clear.

 

Nice job with the WEP porting. I know it isn't done, but that's awesome. Hopefully we can use your foundations for the other drivers when the time comes.

[moseschrist]

the following is a part of my log:

 

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: public + private key: ~]?00000‘I^C

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 0, icv match

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 1, icv match

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 2, icv match

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: k: 3, icv match

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: E this packet dont have MBUF_PKTHDR

 

do you know what it means ?

it means that finally the decryption worked !

this whole wep thing is the most annoying encryption ever invented but hey ! it worked !

now i have to fix this little annoying error you see at the end a pray...

so guys keep the faith, soon we WILL have encryption ! [even if it is the simplest one, but it's a start !]

[jalavoui]

Aug 27 19:43:10 asaf-algawis-computer kernel[0]: iwi2200: E this packet dont have MBUF_PKTHDR

if you're getting/sending packets without header, as see in the log, you'll have to find a way to decrypt/encrypt them - this can be hard to do.

i remebered me and xkazu having some troubles in the past with these

 

i just remebered 2 things for nsgui:

1) add a warning on the menu if you connect to a "invalid" network (see picture - i'm unable to upload it to the forum but it says " ip address 169.254.xxx.xxx - no internet connection").

2) add a best networks list. this will allow the user to autoconnect to a network if it is already on the list - just like in windows.

 

About the stable/unstable versions in svn

- i thing we can keep as it is because it allows all revisions of the driver to be in the same folder - this allows to download any release using the right svn commands.

- when we have a stable release we just upload it to the download session of iwidarwin.

 

Is there another way without using the switcher to change the "radio on/off" values?

i believe that if you can get a log withradio on 0x50000 = 0x50000 you'll have you problem solved

i'd love to manage a way to do this - i hope i find the solution one day - you'll have to wait

in the future the 0x40001/0x50001 hacked values will have to go away.

 

iwi3945 rev 494

this is my frist atempt to hack the radio on/off for this card

use networkselector option (1) to turn the card on/off - check the log messages for the rfkill value

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

 

justjoe,

can you fix the links in iwidarwin - maybe put the revision number aways?

i just remebered that we can use a folder of svn (branches or tags) for stable versions of the driver. do you want to give it a try? it can be .../branches/iwi2200/iwi2200_1.0.476.dmg - it will be nice to include the source code on it too in a .tar.gz or .zip file. xkazu always told me to read the svn rules

 

iwi2100, and iwi4965

can someone post the logs/pictures of last version - i'd like to upload a new one but i need to know the logs of the last one.

[moseschrist]

about encryption:

the error doesn't show if i don't decrypt the packet. only after.

so what i'm doing is just writing the correct flag on the mbuf and it works [i think]

 

anyways my problem now is with encrypt [i think] i have some more work to do on the encryption while decryption is almost done [i think]

 

about nsGUI:

i wanted to do a perferred network list for a long time...

if no one implements this until i finish the WEP thingy i'll get it done...

and for the invalid network, i didn't quite understood what you meant...

 

also i will implement a way to send the key from nsGUI to the driver.

what we will do is to send a new data structure,

it will have two values: 1. network. 2. WEP data structure [can easily be extended to other encryptions when they are done]. this will have a new "number" in nsGUI kext control functions.

[rdougan]

Ive a dell 6400 with a wireless 3945 card or something, i've got a ethernet adaptor displaying in network preferences and have tried displaying a list of networks with the utility but nothing is coming up.playing a little more and now i can see the mac address in the networks preferences with the new version. old version i couldnt.when i type 2 to show network list it says hello world: show network list.

 

 

When i switch it on, the wireless light on my keyboard doesnt switch on so it must not actually be going on. led doesnt work either (says its on but isnt, and cant switch it off)

[JustJoe]

About the stable/unstable versions in svn

- i thing we can keep as it is because it allows all revisions of the driver to be in the same folder - this allows to download any release using the right svn commands.

- when we have a stable release we just upload it to the download session of iwidarwin.

 

justjoe,

can you fix the links in iwidarwin - maybe put the revision number aways?

i just remebered that we can use a folder of svn (branches or tags) for stable versions of the driver. do you want to give it a try? it can be .../branches/iwi2200/iwi2200_1.0.476.dmg - it will be nice to include the source code on it too in a .tar.gz or .zip file. xkazu always told me to read the svn rules

I was thinking about svn tags before but I thought it wouldn't work. I forgot that the tag points to a specific revision. This will be good for stable versions.

 

I think people should know which version of unstable driver they are downloading. This will help devs too. The svn at iwidarwin site only shows the latest revision of the entire project. Right now it says 495 for everything, even though iwi2200 is at 476. Technically, they are all at 495, but that doesn't help matters. I will think of something.

 

I will fix the site then tackle tags and source tarballs tonight.

 

I emailed all the devs a couple months ago to stress the importance of reading the svn rulebook. Merges especially can be a pain (I see this coming with the WEP) but not too bad if we take the time to do it right. Maybe we should all refresh our understanding.

 

I'll try to post some radio on/off logs tonight too. Nice job!

 

And speaking of WEP, nice job to moses too!

[Evil_Cartman]

iwi3945 rev 494

this is my frist atempt to hack the radio on/off for this card

use networkselector option (1) to turn the card on/off - check the log messages for the rfkill value

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

Now `networkSelector` doesn't stuck on turning card on (1) and there's also I've found working option (4) "Switch mode" - it gives me three additional commands. Still no networks list (2) but `ifconfig` shows me correct mac for wifi card instead of previous rev.

 

And one more important thing. Previous revs of iwi3945 caused my computer to hang up during boot (no kernel panic, just stop loading and responding), not every time but very often. It was definitely iwi3945 driver because removing it from the system makes computer boot successfully in 100% cases and also, as other way, I've found `-v` switch helps to boot without problems.

 

But now, rev 494 starts to hangs up my system in a few minutes after successful boot, also without kernel panic. Don't know what to do with it and I'll be glad to help with locating this problem.

 

Cannot upload new logs - is there problem with the forum? PM me or reply here to ask logs direct to your inbox.

 

Update: Here comes my logs.

dmesg.txt

ioreg.txt

system.txt

[JustJoe]

I think people should know which version of unstable driver they are downloading. This will help devs too. The svn at iwidarwin site only shows the latest revision of the entire project. Right now it says 495 for everything, even though iwi2200 is at 476. Technically, they are all at 495, but that doesn't help matters. I will think of something.

 

I will fix the site then tackle tags and source tarballs tonight.

Important:

• rev476 was incorrectly named. It is actually rev475. Sorry for the confusion.
  
• With the way Google operates the code site, it is not possible to see the current revision for each driver. It is only possible to see the current revision of the entire project. I made a request that they change the way in which each directory is labeled, but who knows if they will do it. So for now, you will have to rely on us to tell you which version is the current one for each driver.
  
• iwidarwin was captured at rev 475 and placed in the tags directory. It will always be easily and readily available, even if iwi2200 is updated, by browsing the SVN tags. It is not possible to capture only one driver directory, so in the future the tag will be named iwidarwin_rev###.
  
• Source code tarballs are also be available and will be placed in the downloads section. as well as the featured section on the code site homepage. When a new version is uploaded, the old version will be deprecated(archived), but it will always be available.
  

If you have any questions about how this works or why it works this way, please consult the svn rulebook before asking questions here.

Suggestions are welcome.

 

Phew.

[sonotone]

THX for details...

[Bense]

subscribing

[forge]

so where are we at with the 3945 driver?

 

Is the current one working at al? could I log on to my Uni network with it?

 

thanks

[atlee]

forge stop being so blody lazy and read or are you blind....if you can load a page, you can read it...just regarding the latest driver, i can install it and use networkselector without crashes, also the card has a mac address...the network selector program just works like hello world thingy, cant do anything at this stage, i will wait till further development, regarding iwi3945

[forge]

oooh touchy

 

actually I spent a good hour trawling through all this this afternoon - it can be easy to miss things when you've read so much and I didnt see anything conclusive

 

1 post is like a needle in a haystack

[tendycq]

how is the progress of iwi3945?is any one working on it now?

[Evil_Cartman]

forge, tendycq, are you local Project Managers or what?

Why are you thinking you can just come here and start yelling without reading back for a few messages?

 

I've subscribed to this thread to help our developers, not to receive your useless pronouncements.

 

So please read all messages about progress here:

http://forum.insanelymac.com/index.php?showtopic=14169

There are all answers you need.

 

Thank you.

[forge]

wow I really didnt realise people find it that irritating to ask a simple question

 

being one who is myself learning programming at Uni I know too well the perils of long hours in front of a computer

 

might I suggest a nice walk and some fresh air?

 

seriously dudes, it's totally harmless - we end up here after often many HOURS of googling etc and these 100+ page threads are not straightforward to slot into

 

sincerest apologies if my presence offends so much, but really, do you need to reply if you're that concerned?

 

someone who isnt so irritated may actually feel like replyingI didnt just post without searching first, it just really isnt easy to slot in and figure out where you're at

 

might i suggest if the 3945 is such a popular quest, why not a sticky with the progress?

 

or something I dont know

 

BTW - I did d/l the latest from the site and it didnt seem any different at all to the last one

 

so if I know what I am supposed to expect then maybe I can help too?just a thoughtand

 

BTBTW - there was no "yelling" on my part - that was the bit that made be think you need one of those health and saftey prescribed 15 minute breaks at hourly intervals - if you thought I was yelling that is

and turn off the coffee filter!

[moseschrist]

i'm stuck on iwi2200 wep.

i think i finished with rx functions with wep encryption.

now the tx/xmit is left.

 

i uploaded a driver source to the download page,

i can't up to SVN for some reason... [it doesn't like my password]

 

just a heads up there is no interface for entering a password yet,

so you have to do it by hand in the file ieee80211_crypt_wep.c

the last function there (init wep) allows you the enter the key.

 

now this is important !

when creating a wep key you put in a phrase from which the key will be created you have to use

5 char length phrase to create a 64bit key.

i used for my network 00000 as the key, but you can try your own.

also, i use this site to create the key: http://www.andrewscompanies.com/tools/wep.asp

and last but not least when you enter your "key" in the driver code you don't put in the created key, but the original phrase from which the key was created.

 

 

and finally:

this is not for all the users, you can' connect to wep protected networks yet,

it can only decode recieved packets but not send coded packets so it's useless for you unless you wish to develop the code further.

 

as i said in the beginning, you need to implement in tx a call for encrypt functions. see ieee80211_rx(), you can see there how it works on recieved packets.

[jalavoui]

iwi3945 rev 497

 

please post logs

 

 

moses,

i'll look at it and try to help

[moseschrist]

i understood that i the encryption functions are in ieee80211_xmit()

now there is a value called encrypt there which tells the function whether to try and encrypt or not.

if the driver doesn't try to encrypt it automaticly goes to ieee80211_net_hard_start_xmit()

which tries to send packets.

if the driver tries to encrypt it first goes through all those tests and such to encrypt the packet and

only then goes to net_hard_start_xmit().

 

the weird thing is that it crashes when we try to encrypt with the "excuse" of not being connected to a network [or at least that is the last line i see on the log].

but i don't see this error when i don't try to encrypt the packet. and it doesn't even crash.

 

now, why is that weird you ask ?

because in both times were not associated !!! so why it crashes is beyond me