Jump to content
3992 posts in this topic

Recommended Posts

Hi Jalavoui, here are separate logs taken for iwi3945_515 (before launching NS and after) and for the iwi3945.dmg uploaded above (also before launching and after NS). Under the Network Selector I used the same routine, twice the option 1 and then option 2. After each hit I waited for at least 30 seconds to see if something happens, and after that I used the combination Fn+F2 twice with the same pause between. Only after that I used getlogs command.

Any chance you guys could name the packages with the version number.... i.e. iwi3945_515.dmg

 

Just makes it easier to keep a track of what I've downloaded already and what i'm trying...

 

Keep up the good work!

I renaming it by myself just after download due to keep rev's separately.

please post logs

 

 

iwi3945

 

more rfkill hacking

rename the .zip to .dmg and install

 

alright I installed it, luckily that kernal panic didn't show!

 

now when I go to system profiler and I go to airport card it still says no information.

 

However, PCI Ethernet Slot pci8086, 4222 showed up in control panel.

 

About logs, where do I go and what do I type to copy the information you need?

please post logs

iwi3945

got to pack 'em - too much error info dumped.

 

Gundam,

first, use the `networkSelector` utility provided with each package. at present all is need is to use option (1) several times and then quit (5). read jalavoui's posts carefully - he's always ask for what exactly we need to do.

 

second, go to iwidarwin home and get the `getlogs3.command` script which creates three log files on the root of your MacOS volume. post them here.

 

please read the FAQ and other docs from the iwidarwin home page - there's answers for most questions.

3945rev517log.zip

About logs, where do I go and what do I type to copy the information you need?

Oi. :P

 

Jalavoui and all:

I promise I will fix/update the getlogs3.command tonight. Sorry, no good excuse...

It will work really well to create better logs for the devs.

It will be posted to code.iwidarwin tonight with the name getlogs4.command.

 

:POLL:

Where would you guys prefer your logs created?

A. In a logs folder in the root directory ( /logs )

B. In a logs folder on your desktop ( ~/Desktop/logs )

C. Script chooses A or B: Depends on whether full boot or SingleBoot ( boot with -s )

D. Somewhere else?

 

I think C is teh most logical choice.

Let me know.

 

 

;)

:POLL:

Where would you guys prefer your logs created?

A. In a logs folder in the root directory ( /logs )

B. In a logs folder on your desktop ( ~/Desktop/logs )

C. Script chooses A or B: Depends on whether full boot or SingleBoot ( boot with -s )

D. Somewhere else?

 

I think C is teh most logical choice.

Let me know.

;)

D. home (~/logs) - or B. ~/Desktop/logs

You did well by uploading the log files as attachments to your post, but it is totally unnecessary (redundant) to post the contents of the logs in your post.

 

yeah sorry about that, I looked at previous posts and I saw what they posted.. heh anyhow I fixed all that goodness up.

why not /var/log?

That's a great idea but our iwi logs are already in there. And they are all mixed in with the other programs' logs. Our getlog.command filters those logs and puts them in a place that is easy for even the n00best of n00bs to upload here.

 

Thanks for the idea, though :)

Sorry... I just thought it would make sense for a Unix driver/app to keep to Unix conventions. Apple manage it ;)

 

It can't be that hard to explain to n00bs that they need to upload the file /var/log/iwi.log, can it? If it is, why are they using OSX86 to start with?

 

At least make the destination user configurable, so users don't have to clean up logs all over the place if they don't want to!

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