Jump to content

Intel Wireless driver

jalavoui

By jalavoui,
in LAN and Wireless

 Share
3992 posts in this topic

Recommended Posts

PeterGriff
PeterGriff
Posted
Posted
iwi3945

includes networkselector for turning card on/off - test it a few times before post logs

 

When using this to turn on the card (by pressing 1) I got the "You need to restart your Computer" message. I attach logs from the above release.

system.txt

ioreg.txt

dmesg.txt

jalavoui
jalavoui
Posted
  • Author
Posted

iwi3945

linux logs for sharing with developers

 

looks like there's a problem in the forum with atachments - they seem to be removed after 1/2 days

i hope this doesn't happen because we need to share files with users/developers

can someone check this and report to insanelymac?

klog.log.gz

lawrence alan
lawrence alan
Posted
Posted

logs from iwi3945 on 8.9.1 / 10.4.10

 

i also see the device listed in ifconfig, and networkSelector actually runs, but locks if i try to enable and get a network list.

 

thanks for your efforts, much appreciated!

dmesg.txt

ioreg.txt

ifconfig.txt

networkSelector.html

zeclubbeur
zeclubbeur
Posted
Posted

Hello

 

I have installed the lastest svn version of the 3945 driver.

In network selector, I've got the same thing like laurence alan.

In adition, when I go to system preferences > network, a new wifi interface is detected as each boot and the mac adress is always different. I saw that when I boot under linux, my wifi card is detected and configured successfully and is plainly useable. So, I would like to see the mac adress... And, it wasn't the same as on mac...

 

On another side, Do you think that using the 3945 ucode way is the best whereas we know that on linux distro, this way was abandoned for the new iw3945 driver that doesn's need ucode.

It's just a suggestion. I know you have done a lot of work but, I see that this driver is still in development since many month and I think it will remain in this state for a long time

Almamida
Almamida
Posted
Posted

I'm sure you will find the way to do this in the good thread.

Here we are searching solutions for intel wireless drivers, not Realtek :)

 

@Jalaoui : When I try to install iwi3945.dmg, I've got an error telling me that this action is not permited. Don't you know why ?

Thanks for your work :P

qkslvr221
qkslvr221
Posted
Posted

Using the latest 2200 driver, it will see, connect to, and acquire an IP from my WEP secured router. Only problem is, the IP is some wacky number, and I have no internet connectivity.

 

Here is the information from iwconfig

 

en0: flags-8863<UP, BROADCAST, SMART, RUNNING, SIMPLEX, MULTICAST> mtu 1500

inet: 169.254.243.55 netmask 0xffff0000 broadcast 169.254.255.255

 

This IP should be 192.168.1.1xx, as it is the only range my router will assign. I have no idea what broadcast nor netmask should be, but it is worth mentioning that I set the gateway address to 192.168.1.1 on my Windows machines.

lawrence alan
lawrence alan
Posted
Posted
en0: flags-8863<UP, BROADCAST, SMART, RUNNING, SIMPLEX, MULTICAST> mtu 1500

inet: 169.254.243.55 netmask 0xffff0000 broadcast 169.254.255.255

 

This IP should be 192.168.1.1xx, as it is the only range my router will assign. I have no idea what broadcast nor netmask should be, but it is worth mentioning that I set the gateway address to 192.168.1.1 on my Windows machines.

 

 

Looks as though your card is working, minus DHCP... try setting the network parameters manually:

netmask will be 255.255.255.0

 

169.254.etc.etc = default ip address generated by the system when DHCP is selected, but unavailable.

qkslvr221
qkslvr221
Posted
Posted
Looks as though your card is working, minus DHCP... try setting the network parameters manually:

netmask will be 255.255.255.0

 

169.254.etc.etc = default ip address generated by the system when DHCP is selected, but unavailable.

 

I thought so too, I am able to set the IP to a valid one, but the netmask will not change. Perhaps it has to be in hexadecimal?

jalavoui
jalavoui
Posted
  • Author
Posted

iwi2200

wep support is being develop - need logs/coments to proceed

 

iwi3945

looks like it starts to work - i'll fix a few bugs and post a nre version

if you speed up sending logs i can do a better job

kernel panics are important - if you get one post the picture

the svn tree as a recent version of iwi3945 source code - use it if you have xcode and try to find bugs

 

in this release:

- the driver firmware bugs that keep anoying me from months are gone. this mean that the driver can and will work in mac os x :blink:

- the startup routines need minor fixes (doing in this release)

- need to test scan results (don't know how this work)

- write missing code for rx/tx (it will take some time)

 

i need to know how the driver works in 2 situations:

1) boot into mac os with the card turned off - this will allow to check the rfkill hack

2) boot with the card turned on - allows driver to work

 

if you could coment the system.log while testing this it will be much easier for me to understand

 

if you can't see the driver in network preferences try to fix it - my guess is it will work better if detected there

as anyone tryed to change info.plist?

 

i'm uploading latest source code - svn try is not up to date

iwi3945.dmg

iwi3945_source.tar.gz

auqs10
auqs10
Posted
Posted
friends please help me with my Realtek RTL8169/8110 Network card!! Please see to this page: http://forum.insanelymac.com/index.php?sho...mp;#entry480110

 

Hey igarocus, don't be so desperate, this is not the place to find help on your problem. But, try these

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

or this one

http://www.necnet.de/krass.man/Installers/...0Installer.html

PeterGriff
PeterGriff
Posted
Posted
iwi3945

looks like it starts to work - i'll fix a few bugs and post a nre version

if you speed up sending logs i can do a better job

kernel panics are important - if you get one post the picture

the svn tree as a recent version of iwi3945 source code - use it if you have xcode and try to find bugs

 

in this release:

- the driver firmware bugs that keep anoying me from months are gone. this mean that the driver can and will work in mac os x ;)

- the startup routines need minor fixes (doing in this release)

- need to test scan results (don't know how this work)

- write missing code for rx/tx (it will take some time)

 

i need to know how the driver works in 2 situations:

1) boot into mac os with the card turned off - this will allow to check the rfkill hack

2) boot with the card turned on - allows driver to work

 

if you could coment the system.log while testing this it will be much easier for me to understand

 

if you can't see the driver in network preferences try to fix it - my guess is it will work better if detected there

as anyone tryed to change info.plist?

 

i'm uploading latest source code - svn try is not up to date

 

Glad to hear your getting nearer to a final working driver :D I looked into changing info.plist and compared to my Device IDs but there was no difference (i think) it was the Device ID of my soundcard that prevented that from being registered by OS X so I bet thats my problem here. I attach logs from the latest release, for system.txt I added both what happened when I booted with the card on and when the card was off (these are labelled so you can see which is which easily)

system.txt

ioreg.txt

dmesg.txt

jalavoui
jalavoui
Posted
  • Author
Posted

iwi3945

if you get this in logs:

 

WARNING: Requesting MAC access during RFKILL wakes up NIC

 

them the card is off - try to reboot with the card powered on

the driver can't work while rfkill is on

maybe this also hapen if the card isn't registered in network preferences

auqs10
auqs10
Posted
Posted

Hi Jalavoui, the logs of your latest uploaded driver are here (comments inside system.txt). Also, a capture that shows the Mac address associated by Network Selector is different from the one mentioned in the logs. Another difference is the associated IP in Network Connections and the one reported by Network Selector.

jalavoui
jalavoui
Posted
  • Author
Posted

auqs10,

you need to reinstall the driver

try this:

- remove the .kext

- reboot

- goto net prefs and delete any pci8086 interface in there

- reboot

- install iwi3945.pkg

- reboot

- goto net prefs and add the interface (should be detected automatically)

- reboot and the driver will be ready for testing

 

networkselector currently only as option 1 - turn card on/off

 

maybe others should also do this to make a clean driver install

 

does anyone have a ioreg.log with a registered pci8086,xxxx device? - maybe i'm missing something

PeterGriff
PeterGriff
Posted
Posted
iwi3945

if you get this in logs:

 

WARNING: Requesting MAC access during RFKILL wakes up NIC

 

them the card is off - try to reboot with the card powered on

the driver can't work while rfkill is on

maybe this also hapen if the card isn't registered in network preferences

 

When I type ifconfig into terminal i get the following from the Network Interface thats the 3945:

 

en0: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500

 

ether 00:1b:77:32:74:8b

 

media: autoselect (<unknown type>) status: inactive

 

supported media: none autoselect

 

Not too sure if that means anything or what it is supposed to say if the card functions correctly. Can anyone help?

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