Double logo on boot [solved]

i have a strange problem here.. it's not important at all but i ask because i can't explain why it happens.
during the boot process, on the top of the framebuffer i see 2 (TWO) arch logos, one to the top left (normal) and another just to the right of the former. this happens on both my laptops, and started recently (about a couple of months ago i think). maybe somebody knows what's going on or maybe it's just normal, who knows?
also, after i login, if i scroll back the terminal output (shift+pgup) the top part of the screen doesn't change (logos and user/pass prompt), so what should be scrolled there is unreadable.
thanks in advance for any clues about these things.
Last edited by mips (2007-06-17 14:53:14)

mips wrote:
i have a strange problem here.. it's not important at all but i ask because i can't explain why it happens.
during the boot process, on the top of the framebuffer i see 2 (TWO) arch logos, one to the top left (normal) and another just to the right of the former. this happens on both my laptops, and started recently (about a couple of months ago i think). maybe somebody knows what's going on or maybe it's just normal, who knows?
also, after i login, if i scroll back the terminal output (shift+pgup) the top part of the screen doesn't change (logos and user/pass prompt), so what should be scrolled there is unreadable.
thanks in advance for any clues about these things.
I know the answer to your first question. This is by design. One arch logo is displayed per CPU. This is compiled into the standard Arch kernel with kernel config param "CONFIG_LOGO=y".
Raymano

Similar Messages

My 2009 iMac gets stuck on the grey Apple logo when booting up. It boots correctly when in safe mode. I have tried erasing the HD and re-installing from a USB installer. It says the install is complete, but after restarting it gets stuck on the Apple log

My late 2009 27" iMac gets stuck on the grey Apple logo when booting up. It boots correctly when in safe mode. I have tried erasing the HD and re-installing from a USB installer. It says the install is complete, but after restarting it gets stuck on the Apple logo again. This could possibly be an HD failure, but then why does Safe Mode still work and the USB install not work? Any ideas?

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
Don't be put off merely by the seeming complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the behest of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 1000 MB );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[26]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}') printf("%s (UID %s) is using %s '${p[$2]}'",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ N;/:.+:/d;s/ *://;b0'$'\n'' };/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;};$b0'$'\n'' d;:0'$'\n'' x;s/\n\n//;/Apple[ ,]|Intel|SMSC/d;s/\n.*//;/\)$/p;' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/ / { n++;print;} END { if(n<200) print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}') print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR!=2{next}'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' 's/^.{52}(.+) <.+/\1/p' ' /Launch[AD].+\.plist$/ { n++;print;} END { if(n<200) print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' ' /\.(framew|lproj)|\):/d;/plist:|:.+(Mach|scrip)/s/:[^:]+//p ' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/ { n++;print;} END { if(n<1000) print "/System/";} ' '/^\/usr\/lib\/.+dylib$/p' ' /Temp|emac/d;/(etc|Preferences)\//s/^\.\/[^/]+//p;' ' /\/(Contents\/.+\/Contents|Frameworks)\/|\.wdgt\/.+\.([bw]|plu)/d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a) print "CPU: "a;if(b) print "I/O: "b;if(c) print "Net: "c" (KiB/s)";if(d) print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' $1~"lR"&&$2<='${p[25]}';$1~"li"&&$3!~"wpa2";' ' BEGIN { FS=":";} { n=split($3,a,".");sub(/_2[01].+/,"",$3);print $2" "$3" "a[n]" "$1;b=b$1;} END { if(b) print("\n\t* Code injection");} ' ' NR!=4{next} {$NF/=10240} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L) f=f"\n "$0;} END { F=FILENAME;if(!F) exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(AS.+ (En.+ )?text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' /^ +[NP].+ =/h;/^( +D.+[{]|[}])/{ g;s/.+= //p;};' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' / /{$0="'"${p[28]}"'"};1;' '/ en/!s/\.//p' ' NR!=13{next};{sub(/[+-M]$/,"",$NF)};'"`S0 39 40`" ' $10~/$L/&&$9!~"localhost" { sub(/.+:/,"",$9);print $1": "$9;} ' '/^ +r/s/.+"(.+)".+/\1/p' 's/(.+\.wdgt)\/(Contents\/)?Info\.plist$/\1/p' 's/^.+\/(.+)\.wdgt$/\1/p' 's/0/Off/p' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup mdutil sudo\ lsof test );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1|head -1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status " -F '\$Time \$Message' -k Sender kernel -k Message Req 'Beac|caug|dead[^bl]|FAIL|fail|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|tim(ed? ?|ing )o|WARN' -k Message Rne 'Goog|ksadm|SMC:' -o -k Sender fseventsd -k Message Req 'SL' " '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/r*/com.apple.*.{BS,Bas,Es,OSXU,Rem,up}*.bom' '{/,}L*/Lo*/Diag* -type f -regex .\*[cgh] ! -name *ag \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;|sort -t: -k2 |tail -n'${p[38]} '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Ca*/*/Ex,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo,Widg}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto,{cron,fs}tab,hosts,{[lp],sy}*.conf,pam.d,ssh{,d}_config,*.local} {,/usr/local}/etc/periodic/*/* /L*/P*{,/*}/com.a*.{Bo,sec*.ap}*t .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers\ "${p[N5]}" -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l -s\ / '-R -l1 -n1 -o mem -stats command,uid,mem' -i4TCP:0-1023 com.apple.dashboard\ layer-gadgets '-d /L*/Mana*/$USER&&echo On' '-app Safari WebKitDNSPrefetchingEnabled' );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n ' syscall::'${p[33+j]}':return { @out[execname,uid]=sum(arg0) } tick-10sec { trunc(@out,1);exit(0);} '";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP Wi-Fi Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' Spotlight Memory Listeners Widgets Parental\ Controls Prefetching );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear >&-;date '+Start time: %T %D%n';};for i in 0 1;do eval ' A'$((1+i))'() { v=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "$v" ]];};A'$((3+i))'() { v=` while read i;do [[ "$i" ]]&&eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "$v" ]];};A'$((5+i))'() { v=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "$v" ]];};';done;A7(){ v=$((`date +%s`-v[3]));};B2(){ v[$1]="$v";};for i in 0 1;do eval ' B'$i'() { v=;((v['$((i+1))']==0))||{ v=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v=` paste -d: <(printf "${v[$1]}") <(printf "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v=`grep -Fv "${v[$1]}"<<<"$v"`;};C0(){ [[ "$v" ]]&&echo "$v";};C1() { [[ "$v" ]]&&printf "${f[$1]}" "${l[$2]}" "$v";};C2() { v=`echo $v`;[[ "$v" != 0 ]]&&C1 0 $1;};C3() { v=`sed -E "$s"<<<"$v"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;{ A0;A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D23 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 44 54 45;D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A3 14 6 32 0;B4 0 5 11;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A3 14 7 32 6;B4 0 7 11;B3 4 0 22;A3 14 6 32 0;B4 0 8 11;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D13 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D12 34 43 53 44;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;B1&&D23 35 45 55 46;D23 32 31 43 38;D12 36 47 32 48;D13 20 42 32 41;D13 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;D12 26 48 59 49;B3 4 22 57;A1 26 46 56;B7 22;B3 0 0 58;C3 47;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "syntax error," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

My Black Berry Z10 is not starting- Stuck at logo while booting..

My mobile BBZ10 STL-100 is stuk at logo while booting. Its not completing the process to open/on the mobile.
Is there any way to fix this issue?
Can any of you help me, how to resolve this issue.
Thanks in Advance.

You can try loading the OS again, using
Upgrading OS10 devices using Autoloader
You will need to know the exact model STL100-x , found on the white sticker under your battery.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Apple tv freezes at apple logo while booting

My apple tv was working pretty well, then I unplugged it ti connect my iPad via Hdmi and when I back to connect my apple tv it freezes at apple logo while booting it can stay like that for hours

I don't even know if this will work...buy a USB to micro USB cable and connect the AppleTV to your computer and try doing a firmware restore. Here are the instructions from the manual:
If Apple TV still doesn’t respond:
Disconnect the power and HDMI cables from Apple TV.
Connect one end of a micro USB cable (sold separately) to the back of Apple TV, and the other end to your computer.
Open iTunes on your computer, select Apple TV in the Source list, and then click Restore.
The problem is, I don't know if your computer will be able to talk to the AppleTV if it can't even boot. So this procedure may not work. Good luck!

Laptop freezes on HP logo during boot

We have a Pavilion Dv5 running 32-bit Windows 7. Today when my wife went to wake it (it locks and shuts off the screen after half an hour of no use) it instead reboot itself. When it boots, it immediately gets stuck on the screen with the HP logo.
I've tried the various key presses during startup (Esc, F2, F10, etc.). It seems to recognize that I pressed the key, because the little message in the lower left hand corner of the screen will say something appropriate to the key I pressed, but it never actually goes into Bios, or Startup Setup, or whatever. It just stays on the HP logo. It does not shut itself down, either, even after several minutes. It just hangs on the HP logo.
After reading other forum posts I tried several things. I did the HP "hard reset", which had no effect at all. I took out the hard drive and tried booting up that way, with no change at all. I tried removing each of the two memory sticks in turn as well, also with no change. There were not, before or now, any peripherals attached either.
I've run out of things to try. Is there anything else I can attempt or am I just toast? Also, does the fact that nothing changed when I removed the hard drive mean that the hard drive is probably OK (and thus I can still get important files off of it through some other channel)?
Thanks for any assistance or tips!

@MaineScott,
Hello and thank you for posting on the HP support forums. If you have already tried a hard reset and are not able to enter any of the restore menus or access the bios then you will need to contact HP phone support for repair options.
Please try the steps in the following links just in case.
HP Notebook PCs - Performing a Hard Reset or Forced Reset
As well are you getting any beep codes or LED flash codes.
HP Notebook PCs - Troubleshooting LED Blink Codes or Beep Codes During Startup or Boot
If this fails.
Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region.
http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
Thank you again for posting and have a great day.
Please click the "Thumbs Up" on the bottom right of this post to say thank you if you appreciate the support I provide!
Also be sure to mark my post as “Accept as Solution" if you feel my post solved your issue, it will help others who face the same challenge find the same solution.
D5GR
I work on behalf of HP

My Macbook is stuck on Apple logo when booting up!

Hello,
I have a Macbook Core 2 Duo that is stuck on apple logo, And I already tried inserting the mac OS x leopard disc but when I insert the disc and power up the Macbook it shows this picture down below. So if you have any answers that could solve my problem please comment down below Thanks!!!!

OS X- About kernel panics
OS X- How to log a kernel panic
Visit The XLab FAQs and read the FAQ on diagnosing kernel panics.
Note that panics at startup usually signal a hardware failure.
Question (?) Mark, Blinking Folder, or Gray Screen at Startup
These are related but not identical issues. Their causes are outlined in Intel-based Mac- Startup sequence and error codes, symbols. Solutions may be found in:
A flashing question mark appears when you start your Mac
Mac OS X- Gray screen appears during startup
In most cases the problems may be caused by:
Problem with the computer's PRAM - See Resetting your Mac's PRAM and NVRAM.
Boot drive's directory has been corrupted - Repair with Disk Utility.
Critical system files are damaged or deleted - Reinstall OS X.
The disk drive is physically non-functional - Replace the hard drive.
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
The main difference if you are using Lion or Mountain Lion is that you must first boot from the Recovery HD:
Boot From The Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Reinstall Snow Leopard Without Erasing The drive
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install Mac OS X 10.6.8 Update Combo v1.1.
Reinstalling Lion/Mountain Lion Without Erasing The Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

IMac 27" does not show "apple logo" on boot, keeps on restarting.

Hello there is something wrong with my girlfriend's iMac.
She has the iMac 27" 2.8GHz, Quad-Core Intel Core i5, 8GB RAM
She bought it two days ago, it gave her problems last night (after less than a day of usage), when she tried to call the call center, it was closed. We're bringing it down to the nearest service centre tomorrow but in the mean time I want to see if I can get any help here.
What happened was: She was using it and the screen suddenly turned white half way. Nothing else was on the screen, just one entire white patch. Not even the cursor showed up. So she decided to force shut-down. But when she started it up again, she couldn't even get to the screen which showed the apple logo. The iMac just continued restarting itself, giving me the start up sound, the "boonngggg" sound that all Macs give when they boot up.
The situations is similar to holding Command-Option-R-P (resetting PRAM) but this time the iMac doesn't even get to the apple logo, and if it's powered on, the restarting continues on its own.
I have surfed the web quite a bit and haven't found a problem similar to this one (except some which suggest Logic Board failure).
What can I do now?

You can't do anything now, if you purhcased it directly from Apple contact them immediately and advise them of the problem. They will allow her to return for exchange however they will need to run it through diagnostics first. The other avenue with them is to return for refund and then re-order however this is more time consuming because she will not receive a credit until the old machine is returned.
Also she can call AppleCare in the morning and they can also try some diagnostics.
Finally she can run Apple Hardware Test in extended mode to see if there are any hardware problems.
http://support.apple.com/kb/HT1509
Roger

MacBook Pro won't get past Apple logo during boot

Hey, recently while I was using on my MacBook Pro (note: just simply browsing the internet), the battery ran dry and the computer shut down almost immediately. When I plugged it in and turned on the computer again, the familiar Apple logo appeared and looked as though it would start up normally. However, an unfamiliar grey progress bar appeared and the usual grey gear started spinning. The progress bar looks as though it reaches up 10-15% completed but the computer just shuts down after that every time. I know it has nothing to do with the charge in the battery as I tried doing it plugged in and even waiting overnight for the battery to charge fully with the plug plugged in.
So, I tried using Disk Utility on the Snow Leopard Install disc (my original MacBook Pro install discs had Leopard on it so I just used the Snow Leopard discs instead). After using the "Verify Disk" command on the Macintosh HD volume, it stated that 'Invalid node structure' and then stated that the disk could not be verified and needed repair. I then proceeded with using 'Repair Disk' and it did say 'Volume repair complete' but then stated 'Updating boot support partitions for the volume as required.' This was when an error popped up and said "Error: Disk Utility can't repair this disk" and then told me to back up my files and reformat the disk.
I'm hoping that I don't have to reformat the disk as I haven't backed up in a while. I do have a separate partition on the hard drive that has Windows 7 on it that I can boot to. At least that means my hard drive hasn't completely died on me. However, I'm unsure what to do at this point to fix the computer. I tried to Safe Boot but it didn't change the outcome of start up.
Any ideas as to what I can do? I appreciate any help.

Thanks for the replies! Anyway, I gave DiskWarrior a try and it failed to work. The first time I tried it, I put the disc into the drive of my MacBook Pro and booted it from the disc. After going through the rebuild process it told me that due to a hard drive malfunction it couldn't append any changes to the drive. I then tried putting the disk into my iMac and used my MacBook Pro in Target Disk mode. This wouldn't even attempt to rebuild my drive saying that there was a hardware failure.
So, I booted into Windows 7 and saw that Windows was able to access the drive and read the files perfectly. All the files were in tact. I don't understand why disk warrior had a problem with it. Anyway, what I can do is reinstall Mac OS X Snow Leopard onto the hard drive again after moving the data onto an external hard drive using Windows. The only problem is that I would have to reinstall all of my programs while reimporting all of the settings and data that I can from the external hard drive. What I want to know is can I make an image of my hard drive (with SuperDuper?), and append that back onto my Mac's hard drive? Would that work again after reformatting the disk or would it just give me the same problems as before? Would it be better or easier to just start new and reinstall everything? Thanks!

Hangs on white screen with Apple logo while booting

I can not get my Mac Pro Quad Core to boot up. It gets to the plain white screen with the Apple logo and will not go any further. I shut down the computer and unplugged it before a bad thunderstorm. Since then I haven't gotten it to boot up just once.

The Genius Bar said it was a "blip" in the OS. I just love the technical terms Apple uses. They did a repair install of Tiger. All of my software and documents seemed to have remain safely on my computer but none of my hardware was. I had to reinstall all related software for my hardware (Apogee Ensemble and wireless keyboard and mouse).
Hope this helps you Yogafreak. I could have reinstalled the OS myself but I had already carried the heavy mac pro all through the mall so I let the pros handle it. I would have preferred some service through the phone that didn't cost $50 for 30 days.

New Arch Logo - Kernel Boot

Well I made a Arch Kernel Boot Logo using the new logo (in knoppix as netpbm is broken in arch)
It is kinda fuzzy on the edges, I'll try to see if its possible to fix up hopefully this weekend.
Get it here: http://mezoko.net/stuff/arch/logo_arch_clut224.ppm
How to install:
Just download this package (i686), I used the pkgbuild from aur, I just replaced logo_linux_clut224.ppm with mine: http://mezoko.net/stuff/arch/kernel26-2 … pkg.tar.gz
From source:
-Way 1-
1) Run abs
2) cd /var/abs/base/kernel26
3) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
4) Run makepkg
-Way 2-
1) cd /usr/src/linux/drivers/video/logo/
2) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
3) Compile kernel as normal
-Way 3-
1) More official if you have your own kernel source (adds logo to kernel tree)
2) Read: http://gentoo-wiki.com/HOWTO_Linux_Logo … o_it_Right
P.S. if someone could fix the netpbm package, as it lacks
[mezoko@pyther ~]$ pnmtoplainpnm
/usr/bin/pnmtoplainpnm: line 3: pnmtopnm: command not found
Last edited by mezoko (2008-01-17 00:49:45)

mezoko wrote:
Well I made a Arch Kernel Boot Logo using the new logo (in knoppix as netpbm is broken in arch)
It is kinda fuzzy on the edges, I'll try to see if its possible to fix up hopefully this weekend.
Get it here: http://mezoko.net/stuff/arch/logo_arch_clut224.ppm
How to install:
Just download this package (i686), I used the pkgbuild from aur, I just replaced logo_linux_clut224.ppm with mine: http://mezoko.net/stuff/arch/kernel26-2 … pkg.tar.gz
From source:
-Way 1-
1) Run abs
2) cd /var/abs/base/kernel26
3) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
4) Run makepkg
-Way 2-
1) cd /usr/src/linux/drivers/video/logo/
2) Replace logo_linux_clut224.ppm with logo_arch_clut224.ppm
3) Compile kernel as normal
-Way 3-
1) More official if you have your own kernel source (adds logo to kernel tree)
2) Read: http://gentoo-wiki.com/HOWTO_Linux_Logo … o_it_Right
P.S. if someone could fix the netpbm package, as it lacks
[mezoko@pyther ~]$ pnmtoplainpnm
/usr/bin/pnmtoplainpnm: line 3: pnmtopnm: command not found
lool when i first posted the ppm problm on a multimedia topic it was for this purpose

Self-compiled kernel wont boot [solved]

Hey, I compiled a kernel yesterday using the PKGBUILD from http://wiki.archlinux.org/index.php/Ker … n_with_ABS
All went fine, i made a init thing with mkinitcpio -g /boot/mykernel.img -k 2.6.18.1-mykernel and it went fine, i added it to menu.lst (grub) and rebooted,
at first it says it can't parse block device name for '/dev/sda6' (wich is my root partition) then i added rootfstype=ext3/ext2 (I tried both since i know i have one of them but cfdisk shows amoeba =/ )
but i still get the error 'cannot open root device dev(0,0)' (and also 'kinit: init not found') and then a kernel panic.
This is the boot part of menu.lst for the kernel
title [Arch mykernel]
root (hd0,0)
kernel /vmlinuz-2.6.18.1-mykernel root=/dev/sda6 rootfstype=ext3 ro
initrd /mykernel.img
and this is the hook line from mkinitcpio.conf (all other lines where either comments or ="" so i decided to exclude them).
HOOKS="base udev autodetect usb ide scsi sata filesystems"
also, i have some trouble with ata2.01 "qc timeout (cmd 0xa1)" something, is there a way to save the output of a boot?
--SOLVED--
I forgot -ARCH in the mkinitcpio -k argument.

tomk wrote:
firedance wrote:I do feel as you are treating me like i would treat an idiot :?
Perhaps somebody else should help you, in that case.
I answered you original post with the understanding that you had chosen to use mkinitcpio, and were therefore familiar with the way it worked. Your follow-up suggested that this might not be the case, so I clarified my original answer.
firedance wrote:I'm not sure if that's so smart tho if i load a module thats also in the kernel
Given your previous reaction, I won't comment on whether it's smart or not - I will simply say that it won't work.
firedance wrote:when i used the right parameter it started complaining about missing modules.
Which missing modules did it complain about?
As topic states this is solved, it complained about usb-storage (wich i had compiled into the kernel) It didn't complain about ext2 since i had allready been messing around with the kernel and recompiled it with ext2 as a module. It did work to just do make modules and make modules_install for the usb-storage. But then again, maybe i was very lucky and accedently made it a module on the same time as making ext2 a module
I will recompile the kernel tonight so i am sure it is with ext2 and usb-storage only as modules.

No apple logo on boot

Whenever I start up my iMac, instead of getting the apple logo, i get a black background and white text with things the computer is loading, and its the same thing at shutdown. Anyone have any ideas? I just got this thing and already a problem.

If you are still ending-up in the familiar OS X environment when it's done, then what you are seeing is the "verbose mode" startup.
Go in to Terminal (the command line) by going to:
Applications --> Utilities --> Terminal
at the command line, type in the following exactly as it appears:
sudo /usr/sbin/nvram boot-args=""
Then, close terminal, and restart.
Verbose mode is simply a mode that shows you everything that is happening as you start-up. This is useful for figuring out where a system is locking-up during startup, etc.
To see verbose mode, you can also hold down the Command (Apple Key) and the letter "V" while starting up.
Or, you could go into the Terminal again, and type in the following:
sudo /usr/sbin/nvram boot-args="-v"
hope this fixes it for you.
Let me know how it works out.
I hope this helps.

Grey screen (no spinning logo) - does boot as able to operate cd

Hi,
There seems to be a fair bit of information about regarding this but nothing I have tried so far has worked. Basically, over a protrcted period of about 3 months, my imac G5 has occasionally booted up to a grey screen. It has corrected itself on reboot on some occasions and on others taken a few hours to reboot. It now only boots to a grey screen but I am atill able to operate some things by connecting my pod, it syncs with the computer and will download new podcasts and I can play and listen to CDs. I have tried a number of reboot with keys and also with my original disc but to no avail. It is still stuck in the grey mode. There is no spinning or apple logo, just plain grey.
Unfortunately, I have not taken a back up of any of my files so would like to do this if I am unable to boot the syastem back to normality.
Can anyone help with any of this.
Thanks
BC

It sounds as if your drive is going, but try to reset the PRAM and the SMU although it really sounds like your drive. You can try Target Disk Mode to retrieve your data.
Let us know how you make out,

Systemd.timesyncd fails on boot [Solved]

Upgraded systemd to 217-1 and now each boot sees timesyncd fail:
● systemd-timesyncd.service - Network Time Synchronization
Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
Active: failed (Result: start-limit) since Fri 2014-10-31 10:25:59 NZDT; 5min ago
Docs: man:systemd-timesyncd.service(8)
Process: 303 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
Main PID: 303 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Oct 31 10:25:59 Shiv systemd[1]: start request repeated too quickly for systemd-timesyncd.service
Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
Once I log in, I am able to restart the service without any complaint.
Anyone else seeing this?
# edit: perhaps related to this fixed(?) bug: http://lists.freedesktop.org/archives/s … 03199.html

tl;dr answer:
# sed -i 's/ remote-fs.target$//' /usr/lib/systemd/system/systemd-journal-flush.service
Long answer:
In systemd 217 a few changes were made with regard to ordering of early boot units, resulting in certain setups which used to work with systemd 216 to make problems with systemd 217. The fix above was also applied in systemd upstream by this commit:
commit 919699ec301ea507edce4a619141ed22e789ac0d
Author: Lennart Poettering <[email protected]>
Date: Fri Oct 31 16:22:36 2014 +0100
units: don't order journal flushing afte remote-fs.target
Instead, only depend on the actual file systems we need.
This should solve dep loops on setups where remote-fs.target is moved
into late boot.
For example, in my case, connman.service explicitly requests to be ordered before remote-fs.target, leading to all kinds of fun:
systemd[1]: Found ordering cycle on basic.target/start
systemd[1]: Found dependency on sysinit.target/start
systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
systemd[1]: Found dependency on systemd-journal-flush.service/start
systemd[1]: Found dependency on remote-fs.target/start
systemd[1]: Found dependency on connman.service/start
systemd[1]: Found dependency on basic.target/start
systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
systemd-timesyncd[201]: Failed to allocate manager: No such file or directory
systemd[1]: systemd-timesyncd.service: main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start Network Time Synchronization.
systemd[1]: Unit systemd-timesyncd.service entered failed state.
systemd[1]: systemd-timesyncd.service failed.
Explanation:
systemd-journal-flush.service wants to be ordered after remote-fs.target whereas connman.service wants to be ordered before remote-fs.target. Additionally, connman.service requires basic.target. (This is implicit behavior for units which don't declare "DefaultDependencies=no".) This is why basic.target ends up getting pulled in so early in the first place.
Furthermore, systemd-timesyncd.service relies on properly initialized runtime directories in order to work, so it wants to be ordered after systemd-tmpfiles-setup.service.
In order to be able to start basic.target, systemd breaks the ordering cycle by taking systemd-tmpfiles-setup.service out of the transaction, thereby preventing systemd-timesyncd.service from starting up correctly.
Last edited by csn (2014-11-01 22:18:37)

Mirror front G4 stuck on apple logo on boot ?

Hi all, Friends just called to say his G4 won't boot.. it gets to the grey screen with apple logo an goes no further. He's tried re-booting. Unplugged everything .. HD etc.. still no joy. Any ideas? HD failed? logic board?
many thanks.
Simon

I should have said to try using Disk Utility to repair your startup disk (hard drive) as shown in Dr.Smokes repair thread first. Then try those other links.
Do everything in his link once a month and you'll keep your Mac running smooth.
Cheers!
DALE

Double logo on boot [solved]

Similar Messages

Maybe you are looking for