Jump to content
3411 posts in this topic

Recommended Posts

wait...

that panic is because i've disabled some conditions to make the driver allways run

this can't be done because sometimes the radio if off, ucode fails to load, etc

i'll fix this and commit to svn

 

iwi3945 rel 735

this time the driver will fail if get initial errors during startup

need to be tested in extensions folder

 

i'll change the build script to place the kext in extensions folder

the en1 must be recognized by os x to work

ok this is in rel 737

after you build in xcode reboot, goto sys prefs and it's ready to test

you don't need svnx to grab the source

use terminal to get it

i have rapidsvn to work on svn - mybe it works for you

 

can someone else help with logs

mlazy is the only one working here

 

iwi2200

nsgui would looke nice if it as a way to store prefered networks

it should also store hidden essid and wep passwords

anyone with mac os x cocoa skills around?

 

read some posts back and you'll find out all there's to know to build with xcode

you don't need svnx to grab the source

use terminal to get it

i have rapidsvn to work on svn - mybe it works for you

 

can someone else help with logs

mlazy is the only one working here

 

 

Could you elaborate on how to do that? I'm getting really confused with the build stuff..

Or can someone attach a build of 737?

735 logs: (up and running with it loaded right now!) Can't connect to anythng, but did see new enet interface.

 

735syslog.txt

 

735 kext for testing:

 

iwi3945v735.kext.zip

 

screenshot showing new enet with real mac address:

 

post-104181-1208371898_thumb.png

 

 

Ignore this... building 737 now.

can someone else help with logs

mlazy is the only one working here

 

I guess he's not so lazy! ;)

 

 

Anyway, I'd love to get some logs, but so far my system hangs everytime, just as I'm trying to do so. (Trying with the iwi3945 drivers)

 

The last revision I checked out and installed was 735 I think, it booted up fine, and then freeze after a few seconds, before I can get any useful info.

en1 isn't comming up

waht do you have in ifconfig?

try this:

remove iwi3945.kext

reboot

remove en1 from system preferences -> network

reboot

install iwi3945.kext in extensions

load it

goto sys prefs -> network

click apply if you get a new en1 device

see system.log

 

good kp ;) - boot with -s and check last log lines before kp

NEW SYMPTOM:

 

Load kext, no problem, see logs above. Go into network prefs to apply new interface, immediate lock up on pressing apply. got a picture of the syslog in the bg, kinda grainy, can you see it? It's definately starting a scan, but it panics before the log is even written to file. I got lucky and it showed in my tail -f in the background.

 

 

post-104181-1208373817_thumb.jpg

best kp i ever seen - shows driver scanning

you should all test the driver with boot -s

if the driver as reached here it will be very easy to make it work

first working version will only be able to associate to unsecure networks

but i guess you all be happy with it

 

where's the .dmg?

i'd like to see this working on other iwi3945 cards - might work better

 

maybe you'd like to open console -> system.log before clicking "apply" in sys prefs

 

one old advice:

the driver fails if radio is off

one way to fix this is go to windows - turn the card on

tehm reboot to mac os x

en1 isn't comming up

waht do you have in ifconfig?

try this:

remove iwi3945.kext

reboot

remove en1 from system preferences -> network

reboot

install iwi3945.kext in extensions

load it

goto sys prefs -> network

click apply if you get a new en1 device

see system.log

 

good kp ;) - boot with -s and check last log lines before kp

 

I'll try this now.

this is not a show

why is everybody online without posting logs?

 

SuperInsanity,

this ocurs when the driver gets errors on initial load

i have no way to fix this for now

best thing to do is try a few reboots to check if you can load it without errors

this is why i need other logs - iwi3945 are not all the same, some work better tham others

 

iwi4965

if you have xcode you can use iwi3945 code to start hacking - just need to change a few things

this will be the best iwidarwin driver when it's ready ;)

this is not a show

why is everybody online without posting logs?

 

 

Sorry about watching this jalavoui, without helping atm. Im keeping me informed about this because I have the 4965agn. And Im trying to understand everything so i can help when the development of that driver is starting.

 

 

allready installed xcode, and have little c++ knowledge, but do i need to look at the 3945 files or those 4965 files?

this is not a show

why is everybody online without posting logs?

 

SuperInsanity,

this ocurs when the driver gets errors on initial load

i have no way to fix this for now

best thing to do is try a few reboots to check if you can load it without errors

 

 

Okay, I'll try that...I'm running out of free time for that right now...I'll post results later.

 

Oh, and what's the best way to get logs if the system keeps hanging before I can do anything useful. Still a little new to all the Mac ins and outs but pretty familiar with BSD so it's not completely foreign.

 

I can read the logs from my Windows system using HFSExplorer too, which helps since I can't access the Inet (the wired lan is a broadcom that doesn't work in Os X either. ;) ) from my Hackint0sh, so the constant rebooting to get to each system becomes time-consuming. However, the system layout is a little different than what I'm use to, so I'm not sure to find all the relavent info. I've been looking in /private/var/log, is this correct? Any other places I should look?

althought there are other ways to check a kernel panic

you can help by taking a screen picture of it

todo so:

press F8 before boot

type -s

...

 

the driver can work in mac os x 10.4 with small changes

if you have xcode i can help

i'm using mac os x 10.4 to write the code <_<

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