On Sep 27, 10:46 pm, "Wallace Adrian D'Alessio"
wrote:
> Coming in late here but I/O problems always lead me to check hardware
> connections first. Dirty connectors are very common. And this is in keeping
> with the "kiss" principle.
Adrian,
That's very sound advice, but (fortunately) that wasn'
On Mon, Sep 27, 2010 at 7:54 PM, Ashgrove wrote:
> Hi Matevž,
>
> I solved the problem by popping in another HDD with Leopard already
> installed. The other drive is already erased, and I got rid of the
> incompatible RAM, so I guess I'll never know what happened. Too bad,
> because I'm still cur
On Sep 27, 2010, at 3:54 PM, Ashgrove wrote:
I solved the problem by popping in another HDD with Leopard already
installed. The other drive is already erased, and I got rid of the
incompatible RAM, so I guess I'll never know what happened. Too bad,
because I'm still curious as to what exactly h
Hi Matevž,
I solved the problem by popping in another HDD with Leopard already
installed. The other drive is already erased, and I got rid of the
incompatible RAM, so I guess I'll never know what happened. Too bad,
because I'm still curious as to what exactly happened. It was a first
for me.
Goog
Hy!
Have you since solved your problem with bad
extensions?
If not, try recreating the mkext, or play with kernel extensions (perhaps
they are not even loaded ... ?)
"sudo kextload/kextunload"
If it would not help, then I would just reinstall the system.
Yours,
Matevž Markovič
-
On Sep 25, 4:51 pm, Bill Connelly wrote:
> I knew you said different hard drive, but didn't that imply a
> different copy of the OS X? i.e., non-perturbed USB extensions and such?
Well yeah, a hard drive from a different computer wouldn't have its
USB extensions screwed up. Maybe they were work
On Sep 24, 2010, at 5:48 PM, Ashgrove wrote:
On Sep 24, 2:59 pm, Bill Connelly wrote:
Like someone said earlier, sounds like the system USB apps got messed
up with the bad RAM. Wonder if a Combo update to the old system would
replenish the apps. Don't know here, just guessing ...
Not exactl
On Sep 25, 2010, at 11:47 AM, Ashgrove wrote:
> On Sep 25, 12:59 pm, John Markowitz wrote:
>> I've had HHD's do strange things. it would be interesting to know if
>> DiskWarrior could fix your problem?
>
> Good that you mention that, John. I tried DiskWarrior, but it didn't
> do a thing. I sol
On Sep 25, 2010, at 11:47 AM, Ashgrove wrote:
> On Sep 25, 12:59 pm, John Markowitz wrote:
>> I've had HHD's do strange things. it would be interesting to know if
>> DiskWarrior could fix your problem?
>
> Good that you mention that, John. I tried DiskWarrior, but it didn't
> do a thing. I sol
On Sep 25, 12:59 pm, John Markowitz wrote:
> I've had HHD's do strange things. it would be interesting to know if
> DiskWarrior could fix your problem?
Good that you mention that, John. I tried DiskWarrior, but it didn't
do a thing. I solved the problem switching to another HDD, but now I
wonder
>
> Not exactly, because the mouse worked perfectly in all USB ports,
> including the keyboard's.It is back to normal now with a different
> hard drive, though. It's just bizarre...
I've had HHD's do strange things. it would be interesting to know if
DiskWarrior could fix your problem?
John
On Sep 24, 2:59 pm, Bill Connelly wrote:
> Like someone said earlier, sounds like the system USB apps got messed
> up with the bad RAM. Wonder if a Combo update to the old system would
> replenish the apps. Don't know here, just guessing ...
Not exactly, because the mouse worked perfectly in
On Sep 24, 2010, at 2:07 PM, Ashgrove wrote:
Tried all of the above. No cigar. Then I switched the HDD for another
HDD with Leopard also installed (remnants of a dying MDD that I'm
parting out) and everything works as it should.
Like someone said earlier, sounds like the system USB apps got
Hi Matevž,
Thanks for the good advice! The keyboard actually worked for all
purposes like selecting the startup drive, getting into firmware,
booting into safe mode, and so forth. It's when the OS is loaded that
I would lose all keyboard input.
Tried all of the above. No cigar. Then I switched th
Hello!
I would recomend to look at the open-firmware(reset nvram, reset-all). But
since you have no option of inputing text into the console (perhaps it would
work with a bluetooth keyboard), try resseting the PMU the hard way (via
battery on the logic board).
The reason why I think that firmware
Hi all,
I have a dual 800Mhz Quicksilver with 640Mb of RAM running Leopard. It
was working flawlessly until I tried a stick of RAM that didn't work --
meaning it was ignored by the system. From that point on, I lost all
keyboard input. I took the RAM out, but still don't have keyboard
input. I tri
16 matches
Mail list logo
