| 1 |
On Tue, Aug 26, 2008 at 9:04 AM, Duncan <1i5t5.duncan@×××.net> wrote: |
| 2 |
> "Mark Haney" <mhaney@××××××××××××.org> posted |
| 3 |
> 48B4148E.2010703@××××××××××××.org, excerpted below, on Tue, 26 Aug 2008 |
| 4 |
> 10:34:54 -0400: |
| 5 |
> |
| 6 |
>> Yep. That's it. I can't believe I didn't think of that. I haven't |
| 7 |
>> done much with overlays, so it didn't occur to me. Ever had one of |
| 8 |
>> those days you couldn't do diddly right? I'm having one of those today. |
| 9 |
> |
| 10 |
> Yes. =:^( |
| 11 |
> |
| 12 |
> Sometimes, I think it's the hardware. I'll beat my head against a wall |
| 13 |
> trying to fix a bug, only to giveup and shutdown. Low and behold, after |
| 14 |
> a night's rest or when I come back from work, I can flip the machine back |
| 15 |
> on and it works fine. On at least one occasion that was after I had |
| 16 |
> repeatedly rebooted trying to fix it, too, all without success. I'm |
| 17 |
> convinced that one was some capacitor saved setting or something, that |
| 18 |
> wouldn't go away with a simple reboot, only when I let the machine stay |
| 19 |
> off for long enough that the capacitor fully discharged, so when I |
| 20 |
> restarted after letting it set for several hours, the setting was reset |
| 21 |
> to machine normal and everything just "magically" worked. |
| 22 |
> |
| 23 |
|
| 24 |
I see this periodically with audio devices under Linux. Hardware bits |
| 25 |
that get in the wrong state and the Linux drivers cannot sovle the |
| 26 |
problem whereas a reboot will, or a couple of MIDI devices that only |
| 27 |
work correctly if you boot Windows first, then warm boot into Linux. |
| 28 |
|
| 29 |
Life in a world where development folks do their best with little or |
| 30 |
no support from hardware manufacturers. |
| 31 |
|
| 32 |
- Mark |
Archives