692 logs and pics, got KP bootig with -s

check if you have add the interface to system preferences - this can make different logs
the driver as a bug and it expects en1 to be the card interface

ok...
i'll post one more release to svn
wait

done

iwi3945 rel 693
ready to test

heres some new logs and kp pics.


Click to view attachment
Click to view attachment
Click to view attachment
Click to view attachment


jalavoui, no interface in network prefs.


build faild error: 'ieee80211_sta_start_scan' was not declared in this scope

no network interface here either

I don't have a en1 either...


...and building rev 693 i get the error
ieee80211_sta_start_scan not defined in this scope

anyone know if everytime there is a new build, it is being built into the dmg, or do I have to recompile?

anyone know if everytime there is a new build, it is being built into the dmg, or do I have to recompile?

For those that have no idea how to get the source code and how to compile the kext:
in terminal do this
svn co http://iwidarwin.googlecode.com/svn/trunk/...945_new-osx10.5 /Users/your_user_name/iwi_OSX_folder
after that open, if you have installed the Xcode, iwi3945.xcodeproj from the source folder and run Build.
Download http://iwidarwin.googlecode.com/files/getlogs4.command.zip
unzip-it somewhere ...

To load the kext:
drag and drop iwi3945.kext into /System/Library/Extensions/
(authenticate when prompted)

in terminal:
sudo -s
your password
sudo chmod -R 755 /System/Library/Extensions/iwi3945.kext
sudo chown -R root:wheel /System/Library/Extensions/iwi3945.kext
kextload /System/Library/Extensions/iwi3945.kext
or
kextload -t /System/Library/Extensions/iwi3945.kext

To get logs:
drag and drop getlogs.command from where you unzip-it and hit enter
Now you have the logs in the root of your drive.
Upload the logs here ...

Cheers

iwi3945 rev 693
I'm geting this error when building. 'ieee80211_sta_start_scan' was not declared on the scope

the building failed

same here ... no idea what to do next

iwi3945 rev 693

im not sure i compiled it ok or not but it seems to recognize the card in sys prefs.

heres some logs.
Click to view attachment
Click to view attachment
Click to view attachment

ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fd5c:8d92:fb98:79ee:216:d4ff:fecf:7996 prefixlen 128
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::216:d4ff:fecf:7996%en0 prefixlen 64 scopeid 0x4
inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
ether 00:16:d4:cf:79:96
media: autoselect (100baseTX <full-duplex>) status: active
supported media: 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 100baseTX <half-duplex> 100baseTX <full-duplex> 1000baseT <half-duplex> 1000baseT <full-duplex> autoselect
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 2030
lladdr 00:02:3f:73:93:40:13:a6
media: autoselect <full-duplex> status: inactive
supported media: autoselect <full-duplex>
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether 00:1b:77:10:dd:44
media: autoselect status: inactive
supported media: autoselect

BTW This is the worst way to communicate ever.. is there any other way??? mayb?

i'll fix it and upload to svn

iwi3945 rel 694
check if builds ok
i've add a fix for ieee80211_sta_start_scan
i'll wait for the logs

I'm getting an error building.

error: 'ieee80211_sta_start_scan' was not declared in this scope

i'd like to install mac os x 10.5.2 in my imac g3 to see if it works
i'll need the ppc version and the i386 if possible
if anyone as a ftp link please pm me
torrents are very annoying

about communicating
i've already said this before...
i don't like to use msn, etc to talk about development
because i need to go back and check previous messages/logs
the best place to to it is in this forum
it as the driver history and help other developers to work on the drivers
if i keep the code discussions in one place i can go back and check the code later
in the past i've used code from iwi3945 in iwi2200
i'd like to keep it this way - learn and help other developers
sorry if this is not the best way to communicate

about virtual development
i always thought that it's not possible to share a network connection for someone with a computer with a 3945 card. to test the driver i need to unplug the 3945 computer connections and leave iwi3945 active
but - who am i - if someone as a solution for this please share it
i do feel that if i have the hardware this driver will be ready in a week

logs from 694

compile, tried to load kext and got this:

Last login: Sat Apr 12 15:08:08 on ttys000
damians-mx6920:~ Damian$ sudo -s
Password:
bash-3.2# sudo chmod -R 755 /System/Library/Extensions/iwi3945.kext
bash-3.2# sudo chown -R root:wheel /System/Library/Extensions/iwi3945.kext
bash-3.2# kextload -t /System/Library/Extensions/iwi3945.kext
kernel extension /System/Library/Extensions/iwi3945.kext has problems:
Missing dependencies:
{
"com.apple.iokit.IO80211Family" =
"A valid compatible version of this dependency cannot be found"
}

bash-3.2#


am I missing a kext? if so, and someone post.

can you try a few times to load the driver with kextload?
maybe removing en1 from system preferences helps
your logs show that the driver is not loading

thanks for helping

Tin_man_0,
you os x is probably {censored}ed up
better reinstall it

i haven't figured out why after using
kextload iwi3945.kext
some logs miss the initial debug messages
can this be because of already having en1 added to system preferences?
this doesn't help debugging the driver - initial log lines are very important
can someone figure this out for me?

694
ok.. iv loaded it several times. deleted the en1 from sys pref

heres some logs.

on img_0901 top line say too many chunks- and it repeated at least 28 lines.
Click to view attachment
Click to view attachment
Click to view attachment
Click to view attachment
Click to view attachment

my logs and pictures.
network preferences detected my card as an ethernet conncetion as usual.

after a lot of messing around this is what i came up with
hopefully this helps

heres some more logs..
Click to view attachment
Click to view attachment
Click to view attachment

iwi3945 rel 695
last version for today
thanks for help testing

curious question, at some point will it be possible for the card to be detected as an airport card rather than as ethernet?

"curious question, at some point will it be possible for the card to be detected as an airport card rather than as ethernet? "



yes flynhawaiian that is our goal. im not sure how long it will take but with the way everyone is working at this.. especially jalavoui i would expect it to be pretty soon. correct me if i am wrong....

I don't think the goal is for it to be detected as an Airport. I think the goal is to get it working at all, and have it use the network selector program - as the 2100 already does. As far as I know, the only drawback of the network selector is it doesn't support encryption, but I could be completely wrong about that.

So after, formatting, zeroing out and installing a fresh new iATKOS (i figured out why I wan't able to load the compiled kexts - I had opted to install the 10.4 wifi kexts durring install). I finally got my KPs! I only hope that my logs shed more light.

ok.. heres some 695 logs.

Click to view attachment
Click to view attachment
Click to view attachment

mayb we can do some kind of dump in linux. i know my ubuntu works perfectly...

so, I decide to load the driver using the kextload method this time arround. I saw that there was a new Eathernet interface in my network settings... I also notice that my existing Airport device that was already installed in my system turned into a standard NIC (still labeld airport but the settings options changed). I used the networkSelector to turn on the device... although I couldn't be sure if it was turning on the device or scanning because it gave no feedback when I select option 1 or 2. is this normal? based on the logs it looks like it turned my card on, but you're the gurus. My 'puter musta been on for a good 15min before I got the KP. I'll attache my new logs.

P.S. - jalavoui had mentioned some command or something to produce a more verbose loglevel and I can't seem to find it in the previous posts... anyone remember what it is?

I saw something interesting in lastsoft and tin_man_0's system.txt

"error iwl3945: Failed to get channel info for channel 0 [3]"

Not sure if I'm correct but I don't think there is a channel 0, but I could be wrong.

Just saw something that might be causing problems not sure if it is or not :-)

Yeah, I think you're right. It goes 1-11 doesn't it?

Actually it goes from 1 to 14 with 1 to 13 used in most of the world. Due to regulations only channels 1 to 11 are allowed in the US and Canada.

best logs ever seen s far
you manage to make the driver start scanning correctly
looks like all it takes is a few reboots - i really need to find out why...
note: networkSelector is disabled don't use it
long system.log - use console - reload to see full system.log

i wonder is there a way to make driver write to system.log or some other log in -single user mode?

iwi3945 rel 696
first version for today
if you get errors try a few reboots to check if the driver gets more stable - just see Tin_man_0 system.log as an example

glorybox,
if boot -s you need to wait for mac os finish sh etc/rc to make system.log works
sometimes the driver don't show initial log lines - don't know why
can you try to remove this lines from code?
//hack
ieee80211_sta_start_scan(local->mdev, NULL, 0);
the driver isn't expected to work this way
it should call the __ieee80211_rx() them ieee80211_invoke_rx_handlers(local, local->rx_handlers
if you manage to make this work it will help a lot
i don't know why local->rx_handlers aren't called
if the driver can make this call it will start scanning without hacks
a good way to see if this functions is called is to set the driver to give less debug msgs:
put static int iwl3945_param_debug = 0;//0xffffffff & ~(IWL_DL_IO | IWL_DL_ISR | IWL_DL_POWER | IWL_DL_TEMP | IWL_DL_INFO);

if you have the card and xcode please try to help me on this
i'm wasting to much time here trying to guess it without the card

if anyone as the iwl3945 logs from linux please post it here
i can't find the old 200 pages thread - it as this file

i will surely try later today. today we have the first sunny day, so want to spend sometime outdoors

Logs for 696

(Sorry, got KP while posting attachments )

Click to view attachment

here are my logs:

his this original svn code or have you changed something?

he's my 696 logs...

Question.... does the kext get put into the extentions folder automaticaly after build?

I'm using the command "sudo xcodebuild"

this time arround my computer started KPing right after build and when I booted in -s I saw the iwi3945 in my extientions folder. So i deleted iwi3945.kext and Extentions.mkext rebooted and re-ran kext using the kextload command, is this normal behaviour?

Tin_man_0,

you can change the build script in xcode to put iwi3945.kext in /
the default is system/library/extensions
this doesn't help debugging because it make the kext to autoload after rebooting
better use kextload to do it
can you post your ifconfig?

iwi3945 rel 697
this is getting better
by some unknown reason Tin_man_0 shows the driver working... weird...
it's crucial to see the first driver log lines - i can't see it in the logs you've send me

this line is very important:
en1: DHCP duplicate configured service
are you guys testing iwi3945.kext with other network devices connected
disconnect ALL other devices or this will never work
you can add en1 to system preferences but don't change any parameter
the driver will work without any changes
one good way to do this:
remove iwi3945.kext
reboot
remove en1 device from system preferences - network
reboot
kextload /iwi3945.kext
goto system preferences and add en1 (it should be autodetected)
check system.log

Jalavoui,

Here is the linux driver you requested for the 3945abg
http://prdownloads.sourceforge.net/ipw3945....0.tgz?download

Good Luck!

No, it is the original SVN, i've noticed that i get different results every time i boot with -s, some times i just get a KP right away, other times i get it after what seems to be a scanning process. I've noticed too that my network name appears after the number chain in some of the logs for example here:


FT46099 is my networks name.

i couldn't get the logs every time i booted but so far is the best thing i've gotten. i have some pics of the different KPs, hope u can find them some use for developing.

I also noticed that one time the driver made a complete scan of all 11 channels.

iwi3945 rel 698
made a mistake on last rel
this should fix it

imwithalwood,
this is the source code
what i need is the system.log of the linux driver
the most recent: iwl3945

iwi3945 testing
please red previous system.log
the driver is unstable and you might need to do some reboots to get it work
i can't use logs full of bugs - check them before posting

Hello,

Fresh build of 698. It sees one of my AP's (LukeGX), looks like things are going faster now. Thanks Jalavoui, you rock!

Click to view attachmentClick to view attachmentClick to view attachment

Where can I access these drivers, I see they are not available from your google code site.

jalavoui - where in xcode can I change the build setting because every time I build I immediatly get a kp and have to boot in -s remove the kext and reboot again to do kextload.

P.S. here's my last logs (i think they're build 697) - I had a hard lock this time arround.

jalavoui i can get logs from my ubuntu live??? i know that the i3945 works.
how can i get theme is it the same command???

build 698 I had to try an kextload 3 times for this one to work. attached are my logs and my ifconfig. ( I made sure not to have anything connected this time arround)

i think they're in /var/log folder


all developers should change the script
in xcodein the icons (expand)
Target
them
iwi3945
them you see Run Script
change the linecp -rf build/Debug/iwi3945.kext /System/Library/Extensions
to
cp -rf build/Debug/iwi3945.kext /
this will allow you to use
kextload /iwi3945.kext
after reboot to test the driver

iwi3945 rel 699
fix ieee80211_sta_timer
this can make the driver work much better
but i think you need a few reboots/kextunload to make it give good logs
at this time i suspect
stabssid=00:00:00:00:00:00
is the driver bug

after some reboots this is what i got: