More fascinating facts about my Airport problems

It seems to happen more when I’m holding the laptop or moving it around, which would lead me to think that it could be flexing and dislodging something lose. It happened once today while I was at work and it was on my desk, but my home office is so cold I wouldn’t rule out thermal flexing. It failed tonight while I was standing there holding it in the Apple Store waiting for it to finish booting, it failed again while I was carrying it to the dinner table, and it failed just now when I picked up my computer from the floor.

It happened when I was logged on as Guest, which was something the Apple Store Genius suggested I try.

Whenever I reboot it because of this, Spotlight is busy indexing and can’t be used for a few minutes after it comes up. This is slightly annoying, because I use Spotlight more than the Dock to start up programs. But more than annoying, it’s worrisome because I don’t remember that happening before.

Tomorrow I’m going to try booting it from the install disk and seeing if it fails while it’s running off the DVD.

Sitting in the Apple Store…

I’m sitting at the Genius Bar waiting for the Genius to come back from the back room where he was probably googling my symptoms.

And now he’s back with some strange theories about a magic keyboard shortcut that disabled my Airport. And now he’s installing some third party software called OnyX. He keeps saying “well it’s still connected” and I keep reminding him that yesterday it failed three times in 5 hours (ie about once every 1.66 hours) and we’ve only been looking at it for half and hour, so that’s no indication of anything.

Oh well, next stop I’ll have to try something more drastic like ‘archive and reinstall’.

Update: After OnyX ran, the computer rebooted. I had to go to my chiropractor appointment, so I was walking out the store as it rebooted, and then while I was still in the store, the damn Airport turned off. I showed it to the Genius, and he said “Oh, that’s what you meant – oh, that’s definitely software”. I don’t understand why he didn’t understand what I meant at that point – when I described it the first time, the other guy behind the Genius Bar said “oh, you mean the pie wedge goes completely white”, and I confirmed that was exactly what I meant. I also don’t understand his conclusion. We’ll see.

Oh, I don’t like that at all

Three times in the last three or four days, my computer has shown the Airport (wifi) as being off, and nothing I could do would turn it back on again short of rebooting. At the advice of a friend, I tried rebooting it with command-option-p-r, but it’s happened again since, so that didn’t fix it.

I see a trip to the Apple Store in the near future.

Climb, Conserve, Confess

(Climb, Conserve, Confess is the mantra for pilots who are lost – climb up in case there are obstacles around, lean the engine and fly conservatively in case you’re far off course, and contact local ATC or Flight Service to “confess” and see what help they might offer you, like radar vectors or a “DF Steer”.)

Yesterday I went flying with a club member who is a CFII (an instrument instructor) who wanted a safety pilot. What I hadn’t known ahead of time is that because he’s an instructor he wanted me to sit in the left seat and fly some of the time. Not only that, but because he was an instrument instructor, I could log the approaches towards my IFR currency.

As I was doing the pre-start checklist, he said that he would work the radios while I flew, and then I would work the radios while he flew. I’ve never done that before, and it was confusing. The first confusion was that because he said he was going to work the radios, I expected him to turn off the avionics master when I went to start the engine. He didn’t, and I didn’t, and the noise through the intercom while the starter motor was cranking was horrendous. I should probably note at this time that while doing the pre-start checklist, I noticed the autopilot flashing strangely, and neither of us knew what it meant. After the engine turned twice and didn’t catch, the battery died and so I think we discovered what it meant. We jump started the airplane with the cart, and it ran fine, and the autopilot wasn’t flashing any more. I vaguely recall that the autopilot flashes when there was a low voltage condition.

I did the first approach, the ILS to 28. Jim surprised very mild surprise that I loaded up the real ILS approach on the GPS instead of a GPS approach. But hey, to me an ILS is a real approach and everything else is a pale substitute, even an LNAV+VNAV. It wasn’t the greatest ILS ever, and Jim kept telling me to correct this way and that, mostly stuff I would have done even without him. It seemed like I was doing the infamous “s-turns down the localizer”, then I remembered where to see the ground track on the GPS and used that to get settled down.

Then it was Jim’s turn, and in spite of the fact that he is a CFII, and he’s much more current than I, he too ended up doing s-turns down the localizer. We discussed it, and considering that both of us had the same trouble, plus how bumpy it was, we figured there were some shifting winds at different altitudes and that was throwing us both off.

Then it was my turn again, and since we’d just taken off from runway 22 and were requesting the ILS for runway 28, we ended up getting vectored to the south of the airport. The air was much smoother there. My second approach went amazingly well. I got a nice gentle turn to the localizer well outside the marker, in contrast to the nearly 90 degree turns we had gotten less than a mile outside the marker on the first two approaches, and the air was smooth, and plus I was using the ground track indication, so I did almost ATP quality approach, with both needles one dot and maybe occasionally two dots off all the way down.

But as we continued off runway 28 and asked for the ILS 28 again for Jim’s turn, they turned us right to the north of the airport, and once again it was getting very bumpy. And when you combine early in the year, bumps, and flying under the hood, for me that means airsick. So I reluctantly told Jim that we’d have to make this the last one. I don’t know whether it’s because we intercepted it from the bumpy north instead of the smooth south, or because I was felling sick and so felt the bumps more or because I wasn’t flying, but it seemed like it was much worse than when I’d done it, both in terms of the bumps and Jim seemed to be having much more trouble keeping the needles centered than I did. But then again, he adamantly refused to use the GPS ground track – he said it was “cheating”. I’ve heard it said for air combat, and I apply it for IFR flying, if you aint cheating, you aint trying hard enough. The plan was to do the ILS 28, do a touch and go, and join the pattern for 25, and I told the approach controller that, although more likely I should have waited to talk to the tower controller.

Now comes the confession part. I mentioned before I wasn’t used to this “pilot non-flying works the radios”. A few times previously I’d either gone to say something on the radio when Jim was working the radios, or waited for Jim to say something before I realized I was supposed to do it. Also, both radios had “flip-flop” alternate frequencies. Jim used the first radio for the tower frequency and the second for the approach frequency. But the approach frequency was also the alternate frequency on radio one. So when we took off from 28, I’d used the flip-flop to switch to the approach. And I didn’t think anything of it, until taking off from our touch and go on 28 that I realized we were still on the approach frequency. A terrible feeling in the pit of my stomach joined the already building air-sickness. I don’t know if I missed a radio call, but I just let us do a touch and go without a clearance, without even talking to the tower. The neither the approach controller nor the tower controller mentioned it, although instead of just directly joining the pattern for 25, we got a bit of a vector to the south and then back in again.

So here is my confession: I didn’t switch frequencies, I didn’t talk to the tower, and let us land without a clearance when it was my job to do all that. Time to fill out a NASA ASRS form.

Does anybody know anything about Mailman?

I upgraded my server to Debian Lenny the other day, and everything seemed ok until this morning. I evidently spammed myself with the couple of hundred VERPed bounce messsages that normally Mailman is supposed to silently handle. Instead, they seemed to have all ended up in my inbox, and there is no indication in /var/log/mailman/bounce.1 that Mailman even saw them.

I’ve checked that postfix still has the mail delimiter set to +, and if I send out a message to a VERP style address on my box it does get delivered. It even appears that the bounces got delivered to “/var/lib/mailman/mail/mailman bounces mailman”. I just can’t understand why they then got delivered to me – normally Mailman does whatever it does and doesn’t bother me about them.