Jump to content
3411 posts in this topic

Recommended Posts

sorry to ask this question i know you guys work hard and that's amazing . but what do you guys mean when you say the test worked or it was good . does it mean that your getting connection? or it just means that the driver is being installed good ?

 

also i use linux ubuntu gustygibbon . and on their forume there is a standard easy install file that makes the 3945 work . is it possible to look at how the file is built? i think it's different i'm not sure about these things . just trying. thank you for your hard work guys and hopefully soon it runs right.

Hi Jalavoui, I have changed my Intel 3945 a/b/g wireless card with a Dell 1500 draft N (NJ449, rev A01).

So, I have a spare wireless card and I wish to donate it to the group working for driver development.

Please mail to me and I will send it to the one interested.

Wish you success.

sorry to ask this question i know you guys work hard and that's amazing . but what do you guys mean when you say the test worked or it was good . does it mean that your getting connection? or it just means that the driver is being installed good ?

 

also i use linux ubuntu gustygibbon . and on their forume there is a standard easy install file that makes the 3945 work . is it possible to look at how the file is built? i think it's different i'm not sure about these things . just trying. thank you for your hard work guys and hopefully soon it runs right.

 

It just means that it's "installing" or initializing properly. It does get some beacons, but a lot of code to negotiate a connection is left.

Hello all,

 

I tired making logs as per: http://forum.insanelymac.com/index.php?showtopic=71779

 

But when I did -s at bootloader and got to the screen, I was unable to do the next command "sh /etc/rc"

 

And when I decided to try the command printer for kicks, it said I didnt have permission to write.

 

I checked my os x partition and I couldn't find folders /etc/ in the root either...

 

Am i missing something?

 

Thanks!

I think you're doing what I was at first. If you're testing using the latest from tnw (the folder "START TEST") then you don't test the same way as the previous one (or I don't think you do). Run the command in the folder and answer yes through all questions in the terminal. Once it is done you can simply run the get logs command without running in single user mode.

 

Correct me if I'm wrong guys?

I think you're doing what I was at first. If you're testing using the latest from tnw (the folder "START TEST") then you don't test the same way as the previous one (or I don't think you do). Run the command in the folder and answer yes through all questions in the terminal. Once it is done you can simply run the get logs command without running in single user mode.

 

Correct me if I'm wrong guys?

 

Thanks for your reply!

 

But sorry, I am not able to follow what your instructions are. What is the folder "start test"? Where should I run the command or when? When the OS is booted up and running or in single user mode? I am a little lost. Could you rephrase/clarify?

 

Thank you!

Thanks for your reply!

 

But sorry, I am not able to follow what your instructions are. What is the folder "start test"? Where should I run the command or when? When the OS is booted up and running or in single user mode? I am a little lost. Could you rephrase/clarify?

 

Thank you!

 

He means that you need to download the file of TNW on page 16. To download the file click on this link: Download here

In there is a .command file wich you can run when your leopard machine is turned on normally, that loads the driver.

Then you can do "sudo dmesg" to get te log. Copy the lines out of the terminal in a text document and post them.

jalavoui:

 

Do you have access to a 4965 card? If not, I have an Intel 4965AGN Wireless card here that i'm not using (HP Part# 441086-001), and would gladly donate it to the project if it could be of use.

i'd like to thanks people offering iwi cards to the project

i only have a imac g3 to work - can't use this cards on it

i'm planning to get a laptop with a pci-express port but this will take some time and depends on the donations get so far.

 

i'll keep this project alive no matter what - so don't worry i'm here to stay :D

 

maybe TNW, Symuc can use those cards?

Hello guys,

 

First Time i thank you for your work and all the time you give for OSX86.

 

I have an Intel WIFI 4965 in my Lapto and i am giving up to search for an Driver to get this card working.

Now i want to buy an external Wireless adapter. Can i use every Adapter wich is compatible for MAC OS X,

or do i need a special Adapter for iATKOS v1.0i ?

 

Thank you

Hello guys,

 

First Time i thank you for your work and all the time you give for OSX86.

 

I have an Intel WIFI 4965 in my Lapto and i am giving up to search for an Driver to get this card working.

Now i want to buy an external Wireless adapter. Can i use every Adapter wich is compatible for MAC OS X,

or do i need a special Adapter for iATKOS v1.0i ?

 

Thank you

 

You can use any adapter that's compatible with mac os x, the most common are zydas based ones.

 

By the way, you'll have to wait some time to get a fully working driver for your wireless card.

 

See ya!

just a question.is there some projects to port the ipw3945 to others OS's like linux, solaris ,bsd systems, so is there a open source project based on the soralis support in the page:http://www.opensolaris.org/os/community/laptop/wireless/wpi/why is more easy to port the linux one, and no this one? ins't mac os x based on BSD too?they says:"The wpi driver which is based on mac-wifi plugin and net80211 module has been integrated into snv_64. So if you run snv_64+, you don't need the driver provided here."mac-wifi is not a part of mac os?sorry, iam not good!i know code on c++ but i think my skills are not suficient to development a driver, in this moment. however i want to know if i can help to the comunity, maybe coding some easy parts of the driver, or debuggin on my lappy mac os x86 10.5.1thanks:D oh i forgot that i mailed to a intel guy From: reinette.chatre@intel.com Subject: RE: [ilw] mac users Date: March 5, 2008 5:05:21 PM GMT-06:00 To: revolt_team@mac.com, ilw@linux.intel.comOn Tuesday, March 04, 2008 4:32 PM, Daniel Leon wrote:is there any way to development a driver for mac os x86 project ?thanks ... _______________________________________________The header files in the source code are dual licensed (BSD/GPL) - thisenables other OSs to develop drivers if they do not use GPL code. Somework is in progress for OpenSolaris (seehttp://www.opensourcewireless.org/ ). You should be able to use thatdriver as a reference as it will be BSD licensed.Reinettesorry for my bad inglish :)

just a question.is there some projects to port the ipw3945 to others OS's like linux, solaris ,bsd systems, so is there a open source project based on the soralis support in the page:http://www.opensolaris.org/os/community/laptop/wireless/wpi/why is more easy to port the linux one, and no this one? ins't mac os x based on BSD too?they says:"The wpi driver which is based on mac-wifi plugin and net80211 module has been integrated into snv_64. So if you run snv_64+, you don't need the driver provided here."mac-wifi is not a part of mac os?sorry, iam not good!i know code on c++ but i think my skills are not suficient to development a driver, in this moment. however i want to know if i can help to the comunity, maybe coding some easy parts of the driver, or debuggin on my lappy mac os x86 10.5.1thanks:D oh i forgot that i mailed to a intel guy From: reinette.chatre@intel.com Subject: RE: [ilw] mac users Date: March 5, 2008 5:05:21 PM GMT-06:00 To: revolt_team@mac.com, ilw@linux.intel.comOn Tuesday, March 04, 2008 4:32 PM, Daniel Leon wrote:is there any way to development a driver for mac os x86 project ?thanks ... _______________________________________________The header files in the source code are dual licensed (BSD/GPL) - thisenables other OSs to develop drivers if they do not use GPL code. Somework is in progress for OpenSolaris (seehttp://www.opensourcewireless.org/ ). You should be able to use thatdriver as a reference as it will be BSD licensed.Reinettesorry for my bad inglish :(

did intel just tell you to make your own driver? :hysterical:

 

keep up the good work guys! I can't wait for the day when my 4965 outshines my zydas chip! :P

Hi

 

I would like to know why the mac adress isn't found on my card ? As you know, I've got a intel3945abg card on a HP dv5245ea. Thanks.

 

Please, I have no quarry with you, but do some research. The driver is not functional yet. Please hold on and pay respect to those who put time and effort in giving you the oppertunity to have wireless on your precious laptop.

loo

 

Please dont let this forum turn into bitching against those who ask the "wrong" questions :( , and laugh at other peoples lack of skill. Think we all respect those who work with the driver :D, well those who dont just buy a working card :(

 

rab

loo

 

Please dont let this forum turn into bitching against those who ask the "wrong" questions :( , and laugh at other peoples lack of skill. Think we all respect those who work with the driver :( , well those who dont just buy a working card :)

 

rab

 

I answered his question. and merely pointed out that it is appreciated to first look up some information before you ask it. Allso I did not laugh about his lack of skill. If you feel like I did, pleace point out where. Anyhow lets not spam this forum any further. I awnsered a question and informed him that looking up something doesn't hurt anyone.

iwi3945

i don't know if i understand the apple80211Request() it is suposed to:

- receive driver setup commands.

- receive external commands (maybe from airport menu?)

- call get/set apple80211 commands. this means to write code inside this functions that call iwi3945 commands?

TNW, can you explain how this works in driver load/aiport menu commands ?

 

about the rx

we can change iwi3945 code to use old iwi2200 ieee80211 code. this is not a good idea because iwi3945 uses mac80211 code wich is much better than ieee80211 code.

 

i'll try to help on porting the mac80211 code. i think we can use some of ieee80211 code - maybe...

 

it will be a good idea to put the iwi3945.dmg in the svn tree. this will allow users to post logs for each new release and help understanding the driver progress. i can't help without seeing driver logs.

 

the iwl3945_bg_rf_kill() need to be enabled. if the radio is off the driver must not call. does this work when the wireless switcher is pressed?

 

the driver Rx/tx packet code is the hardest part to do. maybe it's better use IOEthernetController instead of IO80211Controller - this will help in writting the code.

once this is done we can go back and use IO80211Controller code.

 

the ieee80211_tasklet_handler, and other functions need the station code - you need to go back and enable all station code. i think it starts at ieee80211_alloc_hw()

 

does ieee80211_invoke_rx_handlers() uses other functions to work? looks like some code is missing.

 

does the outputRaw80211Packet() works? need to have outputPacket() working in order to call ieee_tx functions. or is this iwl3945_mac_tx()?

 

in run_add_interface(). i think conf.if_id should be the interface number (en1, en2, ...) . can you check this? try fNetif->getNamePrefix(), fNetif->getUnitNumber()

 

the skb_dequeue() and similar functions seems to use some sort of list_head structure - this can be important to handle rx packets.

 

i'll keep following svn code and try to help

hope this helps.

 

about logs

some logs are very incomplete and doesn't help to understand what the driver is doing.

before post system.log open it and check if it as all lines starting from driver load

iwi3945

i don't know if i understand the apple80211Request() it is suposed to:

- receive driver setup commands.

- receive external commands (maybe from airport menu?)

- call get/set apple80211 commands. this means to write code inside this functions that call iwi3945 commands?

TNW, can you explain how this works in driver load/aiport menu commands ?

 

about the rx

we can change iwi3945 code to use old iwi2200 ieee80211 code. this is not a good idea because iwi3945 uses mac80211 code wich is much better than ieee80211 code.

 

i'll try to help on porting the mac80211 code. i think we can use some of ieee80211 code - maybe...

 

it will be a good idea to put the iwi3945.dmg in the svn tree. this will allow users to post logs for each new release and help understanding the driver progress. i can't help without seeing driver logs.

 

the iwl3945_bg_rf_kill() need to be enabled. if the radio is off the driver must not call. does this work when the wireless switcher is pressed?

 

the driver Rx/tx packet code is the hardest part to do. maybe it's better use IOEthernetController instead of IO80211Controller - this will help in writting the code.

once this is done we can go back and use IO80211Controller code.

 

the ieee80211_tasklet_handler, and other functions need the station code - you need to go back and enable all station code. i think it starts at ieee80211_alloc_hw()

 

does ieee80211_invoke_rx_handlers() uses other functions to work? looks like some code is missing.

 

does the outputRaw80211Packet() works? need to have outputPacket() working in order to call ieee_tx functions. or is this iwl3945_mac_tx()?

 

in run_add_interface(). i think conf.if_id should be the interface number (en1, en2, ...) . can you check this? try fNetif->getNamePrefix(), fNetif->getUnitNumber()

 

the skb_dequeue() and similar functions seems to use some sort of list_head structure - this can be important to handle rx packets.

 

i'll keep following svn code and try to help

hope this helps.

 

about logs

some logs are very incomplete and doesn't help to understand what the driver is doing.

before post system.log open it and check if it as all lines starting from driver load

 

Hi , Nice to see you,

 

For IO80211 maybe we'll see that after :P

 

It's fine that you help me for the Rx & Tx because , it's too hard for me !

 

For the test , I can make lot of test it's not a problem for me!Maybe We'll make a DMG when the driver can receive and send data.

 

I disabled iwl3945_bg_rf_kill as you say but it did not work , I will enable it again tomorow .

 

I just commited the IOEthernetController version of the driver , It have a problem with the MAC addresse , I'll change it tomorow too.

 

ieee80211_invoke_rx_handlers is empty at this moment.

 

outputRaw80211Packet is for the IO80211 interface , we'll see that after :P

 

I commited a version with the fifnet , but I did not implement that in run_add_interface

 

For log , I said that the driver is , sometimes , very long to load ( It restarts a lot when it's not properly init)

 

Thank's

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