[kismac] Re: [kismac]

  • From: "John Warren" <xaive1@xxxxxxxxx>
  • To: kismac@xxxxxxxxxxxxx
  • Date: Fri, 8 Dec 2006 08:57:10 -0800

Thank you.  I'll give that a try.

On 12/7/06, James Lancaster <james.lancaster@xxxxxxxxx> wrote:
My guess is that the motherboard is failing (or your new drive could also be
bad).  Try TechTool Pro from Micromat.  It has a bootable CD with a lot of
diagnostics tailored specifically for the Apple platform.  You can buy it
=85 , but you can "get" it from other sources as well.

-----Original Message-----
From: kismac-bounce@xxxxxxxxxxxxx [mailto:kismac-bounce@xxxxxxxxxxxxx] On
Behalf Of John Warren
Sent: Thursday, December 07, 2006 9:05 AM
To: kismac@xxxxxxxxxxxxx
Subject: [kismac] Re: [kismac]

Since this was started with a dying powerbook comment.... I've been
searching around for what might cause a problem with my powerbook.
Apparently no one I talk to has ever heard of this happening.  I know
this is necessarily the right place to ask, so if you guys know a good
forum to go to for this, I would be much appreciated.  Thanks.  John

Here's the story - go below for straight out details.

My wife was using it and it just stopped working right in the middle
of her working on a word document.  She tried to turn it off by
holding the power button, but it wouldn't turn off.  When I got home,
it had put itself to sleep, I hit a button... nothing.  I closed the
lid and re-opened it.  It awoke, but I could do nothing.

I started thinking "hard-drive has gone bad" so I replaced it.  Still
nothing.  This hardrive already had OSX on it, but I got the balck
multi language screen saying to restart the computer, i think it's
called the kernel panic screen.

Straight out details.
1) I checked both the new and old harddrives in external enclosures.
The new one fully works.  The old one can be seen, but not formated or
written to.

2) With the new drive in the powerbook, starting in firewire target
mode, the new drive can be seen, but not formated.

3) Starting the powerbook from the OSX install disc gives a kernel
panic, but the black box never displays the text.  It's more of a gray

4) Starting the powerbook with "option" pressed shows nothing to boot
from, unless the OSX disc is in and then see #3.

5) The pram has been reset and all that good stuff.  No change.

Has anybody ever seen this or know what would actually cause it.

On 12/7/06, globo <globo@xxxxxxxxxx> wrote:
> Hi everyone,
> my Powerbook died and i wanted to wait for the 2ng gen macbooks. Now
> I've got one and tried how kismac would work with it. Signal reception
> is way better than the powerbook but i guess that was always the case,
> even with the ibooks.
> I compiled 217 and at first glance everything works fine. A few
> glitches here and there.
> Kismac dumps a lot of GPS-device data into the log. I have it up on the
> desktop with geektool. Kinda hard to catch the "important" messages
> when there's a new line every second or so.
> "2006-12-06 10:50:25.316 KisMAC[390] nmesgs 3, tmsg 3, satsinview 11,
> sat1 prn 4 signal 240582687, sat2 prn -1341002320 signal 6603632, sat3
> prn -1839244802 signal 5332992, sat4 prn 8 signal 6703536"
> I had a few crashes. Not sure why though.
> "KisMAC(601,0x1876400) malloc: *** error for object 0x6f0670: double
> free
> KisMAC(601,0x1876400) malloc: *** set a breakpoint in szone_error to
> debug"
> I also had problems with my DWL-122 A1. The loved spinning ball of
> death....
> "2006-12-07 09:27:31.131 KisMAC[189] USBIntersilJack: Detected a Prism2
> card
> 2006-12-07 09:27:31.189 KisMAC[189] USBIntersilJack: Firmware vendor
> 31, variant 1, version 1.7
> 2006-12-07 09:27:31.191 KisMAC[189] USBIntersilJack: MAC 0x0 0xf 0x3d
> 0xe9 0xb4 0xda
> 2006-12-07 09:33:36.001 KisMAC[189] Timeout error.
> 2006-12-07 09:33:41.001 KisMAC[189] Timeout error.
> 2006-12-07 09:33:46.001 KisMAC[189] Timeout error.
> 2006-12-07 09:33:51.001 KisMAC[189] Timeout error.
> 2006-12-07 09:33:56.001 KisMAC[189] Timeout error.
> 2006-12-07 09:34:01.001 KisMAC[189] Timeout error.
> 2006-12-07 09:34:01.001 KisMAC[189] USBIntersilJack::unable to execute
> commmand (00000002)
> 2006-12-07 09:34:01.001 KisMAC[189] USBIntersilJack::_disable:
> _doCommand(wlcDisable) failed
> 2006-12-07 09:34:01.001 KisMAC[189] USBIntersilJack::setChannel:
> Couldn't disable card
> 2006-12-07 09:34:01.005 KisMAC[189] USBIntersilJack::Data overrun,
> attempting to clear the pipe stall
> ...
> "
> I can't tell for sure but it seemed that after waking up kismac would
> run fine but wouldn't pick up new APs. After a restart it worked again.
> Since I was gone so long I didn't want to post a new ticket.
> It's great to see that Kismac is alive and kicking.
> globo

Other related posts: