hello people,
I have this trusty iBook G4 since 2005, it's the 15" 1,42 GHz model. I think it's the very last iBook they've done before going intel. I have the last lion osx installed and I've doubled the RAM like a year ago.
For the last month I've started being a bit worried because the power supply of my iBook didn't work well. sometimes the battery would be used even if the power is plugged. I've had this kinds of problems but I knew how to deal with it.
Today I was browsing with it unplugged (on battery) and everything was normal. Then, I plugged the power supply while the computer is still on (read: not sleeping). At the moment I've plugged the power, everything went black.
Since then, I've tried all the keys+power button combinations I've found... but it never turns on.
I am honestly pretty scared that it's just... y'know... dead ?!
does this kind of issue is known ?? what should I do ??
thanks everyone for your help,
rb
PS. I know there's another "iBook won't turn on" thread, but didn't want to hijack it since the problem is obviously not the same...
I have this trusty iBook G4 since 2005, it's the 15" 1,42 GHz model. I think it's the very last iBook they've done before going intel. I have the last lion osx installed and I've doubled the RAM like a year ago.
For the last month I've started being a bit worried because the power supply of my iBook didn't work well. sometimes the battery would be used even if the power is plugged. I've had this kinds of problems but I knew how to deal with it.
Today I was browsing with it unplugged (on battery) and everything was normal. Then, I plugged the power supply while the computer is still on (read: not sleeping). At the moment I've plugged the power, everything went black.
Since then, I've tried all the keys+power button combinations I've found... but it never turns on.
I am honestly pretty scared that it's just... y'know... dead ?!
does this kind of issue is known ?? what should I do ??
thanks everyone for your help,
rb
PS. I know there's another "iBook won't turn on" thread, but didn't want to hijack it since the problem is obviously not the same...