Ant
2017-02-18 10:45:37 UTC
Hi!
I have a broken 15" MacBook Pro (early 2008) with its updated Mac OS X
v10.5.8/Mountain Lion. I tried booting up this old MBP with these boot
ups' keys and without connected USB devices (mouse and external hub):
1. normal boot -- never reaches the user account screen. It stays stuck
in Apple logo's loading screen with its spinning wait icon.
2. shift -- never reaches the user account screen. It stays stuck in
Apple logo's loading screen with its spinning wait icon.
3. command+v (verbose) = saw the text mode with technical datas. Then,
it loaded the light blue screen for about a second and then back to text
black screen with a white block on the top left corner. Then back to
light blue screen to the black text screen with the top left white block
in a loop forever.
4. command+s (single-user mode) = got to its text bash prompt, but not
sure what to do here to dig deeper and fix. Need experts' help if I need
to use it. At least, this is usable.
5. command+r (recovery) = It stays stuck in Apple logo's loading screen
with its spinning wait icon. No OS X Utilities like in newer mac OSes. I
don't think Mac OS X v10.5.8 has this feature IIRC.
6. d (diagnostics) = Short test passed after about three minutes. It is
now running a long test which will take about 1.5 hours. Isn't this just
memory tests?
7. option-d (online diagnostics) = It stays stuck in Apple logo's
loading screen with its spinning wait icon. I don't think it has that
feature.
8. Option-Command-P-R (Reset NVRAM) = Heard a beep and saw bright screen
and heard loud volume as resets, but it did not fix the boot up issue.
I am trying to figure out if this is hardware or a software issue. :(
Any other ideas to try? I don't see how Apcupsd-3.14.14 could break it
that badly. Earlier, I downloaded and installed
https://sourceforge.net/projects/apcupsd/files/osx-binaries%20-%20Stable/3.14.14/'s
Apcupsd-3.14.14.dmg file into an old 15" MacBook Pro (2008) with its
updated Leopard v10.5.8 since
http://www.apcupsd.org/manual/manual.html#id37 says apcupsd supports Mac
OS X v10.4.x and higher. However, I was unable to save auto-opened
apcupsd.conf that I was required to edit due to lack of admin access
even though I was using an admin account. So, I tried to edit
/etc/apcupsd/apcupsd.conf in Terminal's with su and sudo commands but
they said something about PAM. I said frak it and rebooted, but it won't
boot up anymore. :(
Thank you in advance. :)
--
"In the early 1940s, as a young teenager, I was utterly appalled by the
racist and jingoist hysteria of the anti-Japanese propaganda. The
Germans were evil, but treated with some respect: They were, after all,
blond Aryan types, just like our imaginary self-image. Japanese were
mere vermin, to be crushed like ants." --Noam Chomsky
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.
I have a broken 15" MacBook Pro (early 2008) with its updated Mac OS X
v10.5.8/Mountain Lion. I tried booting up this old MBP with these boot
ups' keys and without connected USB devices (mouse and external hub):
1. normal boot -- never reaches the user account screen. It stays stuck
in Apple logo's loading screen with its spinning wait icon.
2. shift -- never reaches the user account screen. It stays stuck in
Apple logo's loading screen with its spinning wait icon.
3. command+v (verbose) = saw the text mode with technical datas. Then,
it loaded the light blue screen for about a second and then back to text
black screen with a white block on the top left corner. Then back to
light blue screen to the black text screen with the top left white block
in a loop forever.
4. command+s (single-user mode) = got to its text bash prompt, but not
sure what to do here to dig deeper and fix. Need experts' help if I need
to use it. At least, this is usable.
5. command+r (recovery) = It stays stuck in Apple logo's loading screen
with its spinning wait icon. No OS X Utilities like in newer mac OSes. I
don't think Mac OS X v10.5.8 has this feature IIRC.
6. d (diagnostics) = Short test passed after about three minutes. It is
now running a long test which will take about 1.5 hours. Isn't this just
memory tests?
7. option-d (online diagnostics) = It stays stuck in Apple logo's
loading screen with its spinning wait icon. I don't think it has that
feature.
8. Option-Command-P-R (Reset NVRAM) = Heard a beep and saw bright screen
and heard loud volume as resets, but it did not fix the boot up issue.
I am trying to figure out if this is hardware or a software issue. :(
Any other ideas to try? I don't see how Apcupsd-3.14.14 could break it
that badly. Earlier, I downloaded and installed
https://sourceforge.net/projects/apcupsd/files/osx-binaries%20-%20Stable/3.14.14/'s
Apcupsd-3.14.14.dmg file into an old 15" MacBook Pro (2008) with its
updated Leopard v10.5.8 since
http://www.apcupsd.org/manual/manual.html#id37 says apcupsd supports Mac
OS X v10.4.x and higher. However, I was unable to save auto-opened
apcupsd.conf that I was required to edit due to lack of admin access
even though I was using an admin account. So, I tried to edit
/etc/apcupsd/apcupsd.conf in Terminal's with su and sudo commands but
they said something about PAM. I said frak it and rebooted, but it won't
boot up anymore. :(
Thank you in advance. :)
--
"In the early 1940s, as a young teenager, I was utterly appalled by the
racist and jingoist hysteria of the anti-Japanese propaganda. The
Germans were evil, but treated with some respect: They were, after all,
blond Aryan types, just like our imaginary self-image. Japanese were
mere vermin, to be crushed like ants." --Noam Chomsky
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.