Boot up hangs at motherboard screen
Last night I was using my comp no problem, today I turned it on and it hangs at the "Platinum" screen... My D-bracket LEDs are all green except the lower left one is red. What is the problem related to this LED pattern?
sigh, I fixed it. Read about this problem a little more and switched my hard drive's jumper to cable select instead of Master, then reset CMOS and its fine.
My only question is why did this happen randomly? Who knows...
Similar Messages
-
Boot camp hangs at blank screen
I have an early 2011 MBP 15 with Lion and all the latest updates install. I removed the super drive and installed an OCZ 120 GB SSD. My current configuration is 120 GB SDD installed in place of the 750GB HDD and the super drive is replaced with an optibay that holds the 750 GB HDD. I have Lion install on the SSD and want top install Windows 7 using boot camp. I ran the Boot Camp Assistant, created a 100 GB partition on the 750 GB HDD and a Windows partition with a full Windows 7 installation disc inserted in an external USB super drive. I click install (or begin, I forget) and my MBP rebooted as it should. I saw the gray screen and the activity light flashing on my external USB super drive, but the screen went blank and simply hang with a flashing cursor. At this point the Windows installer should begin, but it does not. I tried a partition on the SSD with the same results. I checked the Windows 7 installation disk on a PC to insure that it works and is bootable (It worked fine on the PC).
I've been working on this for several days and googled dozens of web sites with no solution that worked. Any help worked be greatly appreciated. TIA!I've been thinking,
since you have two harddrives,
1. restore the windows7.iso onto the hdd,
2. bootcamp and partition the windows part. on your ssd
3. connect your hdd, and fire up your mbp with your hdd holding option key
4. install windows to your windows partition
5. finalise it
6. delete your windows7.iso
BAM you have your ssd+hdd dual system.
this is just my thought, not sure if it'll work or not since i still haven't recieved my optibay yet -
I've tried what I could of the suggestions for this problem. I've used Disk Utility repair and repaired disk permissions and used Techtool pro which said it repaired. I can only get to the login screen by connecting to a clone in the external hard drive by firewire. I reset PRAM but could not get the reset of power manager. I'm confused about what system I'm working in when I boot from a clone.
Also, I've always thought I had a Dual USB ibook G3, but when checking one of the help pages I see that it's supposed to have a reset button. Mine does not. It is an ibook G3 with 2 USB ports which was purchased in 2002.
Please give me any suggestion you can to get this ibook well.
AnnAnn, the ones that came out in 2001 had a reset button. Later ones do not.
Check out this section of the PMU article:
http://support.apple.com/kb/HT1431#faq6
And see if resetting the PMU helps.
Good luck. -
Hanging on blue screen during boot (but Safe Mode OK)
Strange stuff with my iMac G5 -- machine boots normally, gets through Apple icon and spinning spiral, then hangs on blue screen and stays there. Mouse cursor moves but that's it.
Safe boot works normally, all safe-mode functions good. But need network, other services back.
History: Spent most of past week downloading huge, multi-gig file. It eventually downloaded successfully, but during process my wife put computer to sleep a couple of nights without halting download.
Didn't have adverse effect first time, but it froze Finder second and third times, necessitating reboots. Also killed wireless connections for all PCs in network those two times iMac needed reboot, had to reboot gateway as well.
Morning after download finished (Friday), iMac failed to wake up from sleep, wouldn't boot normally, had to go into Safe mode.
Additional RAM was recently installed, but has worked well. Safe mode shows full two gigs in use.
Solutions I've tried, without success:
-- Trashing network preferences in both user and system
-- Re-installing Finder and NetworkInterface apps using Pacifist
-- Removing recently installed extensions in System (extensions put back after that failed to resolve issue)
-- Removing recently installed Startup items (again, put back after that failed to resolve issue)
Clearly it's got something to do with the network interface, but I've tried everything I know how to do. Any ideas? I'm out of them.
Thanks in advance.The Airport card is not removable in this model -- 2nd rev G5 iMac, with automatic light sensor.
But -- I think I've found what's wrong. Unfortunately there's no easy fix ...
It's most likely the bad-capacitor issue that plagued the 1st rev of G5 iMacs. (This particular machine was a refurb bought direct from Apple in the fall of 2005, so it's possible bad caps were put on during the refurbishing.)
I first heard about the problem a couple of days ago but figured a hardware diagnostic test would catch it. More online research reveals that the hardware test doesn't.
When I popped the case this morning to yank the new RAM, there were definitely a few capacitors that had domed tops. Nothing spilling out anywhere, which was what I was looking for, but I've since found out that even contained bulging is a sign of failure. The capacitors should be instead perfectly flat-topped.
So ... I'm gonna call Apple tomorrow morning and see how much it would cost to replace the mobo. There have been reports in forums that Apple sometimes offers to do it for free, even in cases occurring within the few months.
See this link for examples of Apple picking up the tab for complete mobo replacement: http://www.macosxhints.com/article.php?story=20090314071508354
If that offer isn't made, I will look into having the capacitors replaced. This is at the edge of my own technical abilities so I will first ask my techie friends if they can do it for $100 or so, plus parts ... and if not I'm gonna try to do it myself.
This guy shows you how and sells inexpensive parts to do it with: http://jimwarholic.com/2008/07/how-to-repair-apple-imac-g5.php
There is also a guy out in Missouri who replaces bad capacitors on motherboards for a living: http://www.badcaps.net/ Looks as if he'll charge between $80-120 including shipping and parts. So I may go that route.
In any case it turns out Apple did know about this issue back in 2005 and even instituted a program to fix iMacs that had problems stemming from it for free. (Dell Optiplex machines also had the same problem, which was traced back to a few Taiwanese manufacturers.)
Unfortunately there was no recall (Apple would never have lived that down) nor was the issue highly publicized. You had to wait until your own machine acted up, and then the free-repair program expired at the end of 2008.
I myself never knew about it until a few days ago, and I usually keep up on this stuff -- which is something I will make very clear when I'm on the phone with Apple tomorrow. -
Z77a-gd65 hangs on bios screen and also doesn't boot
i7 3770k
MSI GTX 670
2x8GB 1300 memory.
I cannot get into the bios. If I hook the monitor to the gtx 670, I can get it to display the msi bios screen "temperature, boot device priority" but that's it. There's no data, no temperature, just like it put the bios image up and then hung.
Right after hitting the cmos button, I get the following:
E7751 IMS v10.5 4/27/2012
i7 3770k 3.5ghz
16gb ddr 1333 dual channel
It doesn't seem to let me hit "f1 to setup" or "f2 to continue" with a ps2 keyboard.
If I boot from the cd to try and install winki, there's some info that flashes too fast to see but its to the choice of install, and then whatever option I choose, it will display a clear screen with the logo and eventually the screen goes black with a blinking cursor.
If I boot from a usb linux drive I have, it again goes through the boot choices, and then the screen goes black a few seconds in. Doing this I think I got the mainboard leds to display "ff" otherwise they display either "00" or "ad" or "ae".
The monitor is apple monitor through an adc to dvi adapter. I've used this for years on an ati radeon on a p4 windows setup so it shouldn't be a problem but... if I hook the monitor directly to the mainboard onboard video, the bios screen graphics stop hanging open, the screen just immediately goes black.
I've tried clearing the bios with the button, switching the multibios, and jumpering the cmos with the power off.
I have not tried flashing the bios, I was thinking about doing that through winki but it won't load.
Thanks.I tried just one stick of ram in a different slot but no difference.
And as in my first post I tried the onboard a bit but it was about the same. Actually I forgot what I tried, I just now tried the apple cinema display to the onboard video card and unpowered the gtx 670 without taking it off the board and the display doesn't come on at all.
I think that was what it was last time I tried the onboard, that I thought it might be something about the adc-dvi converter. But it works besides.
Why would it be able to get to the boot choice screen but not the bios though? The PSU has a 7 year warranty, its probably decent, manual says 62.4a +12v .8a -12v
One other thing, if this matters. The first two blue lights are always on on the motherboard, the voltage indicators or whatever, but when it tries to load winki, the other blue lights blink. And right now, with the monitor on the onboard, all the lights are on. But the monitor isn't.
Also, do you need a mouse plugged in, that probably wouldn't make a difference, I think I've tried that as well. -
HELP! iMac G5 hangs at blue screen, but boots in Safe Mode
Please can anyone guide me to recover my iMac G5 PowerMac 8,2 running OS X 10.4.11.
Problem; Mac hangs on start-up at blue screen after grey Apple screen. Mouse pointer eventually appears but that is all.
Actions taken so far without success:
1. Disconnected the printer and rebooted - no success.
2. Booted in Safe Mode - first time the screen was completely scrambled but with safe mode log on screen showing through.
2.1 Rebooted in Safe Mode OK This has not occurred again and I have entered Safe Mode twice more without problems. But worrying!
2.2 In Safe Mode I ran disk Utility and verified and repaired Permissions, mostly old EpsonPrinter files.
2.3 I also verified the Disk, which was reported OK.
2.4 I was able to save critical documents to USB............ Phew!
2.5 Reboot in Normal Mode - no success
3. Reset PRAM
3.1 Reboot in Normal Mode - no success
4. Reboot in Safe mode - works fine. NOTE: time and date appear to be correct and dont need resetting.
4.1 Run Disk Utility again and Verify Permissions - OK. Nothing needed fixing.
4.2 Run Disk Verify - Passed OK
4.3 Reboot in Normal Mode - no success. Hangs at blue screen with mouse pointer visible and working. Then pointer vanishes.
I would be most grateful for your help in moving this forwardGot to figure out which which of the things dropped when you boot in safe mode is causing the problem.
see this link:
http://support.apple.com/kb/HT1564?viewlocale=en_US -
Will not boot up to log in screen
will not boot up to log in screen when powered up, all I get is a grey screen with apple logo in middle and spinning timer
I have tried resetting SMC
I have tried starting up in Safe Mode (it won't do that either)
I have gotten into disk utility to repair disk
I have tried resetting PRAM
nothing... we are on a network in a school district so my next step is to re-image it but wondering if there is something else I should try first
if not then how do I backup files that are needed before I re-image
thanks, CindyTake each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider. -
Blackberry Torch 9860 hangs on home screen
I was using whatsapp and suddenly the phone freezed. When I re-inserted the battery, it froze again at the home screen where we have to enter the device password. It freezes in safe mode too. This is the first time I'm experiencing this problem. Earlier, it used to hang on logo screen but I got my phone replaced as it was in warranty. now it is out of warranty. Please suggest me some solution for this. I tried to wipe all the data by connecting it with my pc. But it doesn't get connected to the pc. Please help. Early response will be appriciated. Thanks on advance.
Have you tried Safe Mode? Remove the battery. While holding down the back key insert the battery. Continue to hold the back key for another 20 seconds while the device begins to boot. If that doesn't work proceed to this step:
Download JL_Cmder and see if you can wipe the device with that. You may need to remove the battery and reboot it and then plug it in right away to see if you can get connected to it. It may take a few tries at various stages of boot to get it to connect. If you can get the wipe to take and give you a 507 error you can easily reload the OS.
1. Please thank those who help you by clicking the "Like" button at the bottom of the post that helped you.
2. If your issue has been solved, please resolve it by marking the post "Solution?" which solved it for you! -
[Solved] Boot process hangs for installed Arch and installation usb
Hi. I've been using Arch Linux for around 6 months now and I'm in love with it. It is now my primary OS. However, I might have done something or performed some update, and I can no longer boot into Arch. The boot process hangs right before it should show the login screen (I'm using Gnome 3.6 with GDM). I see the following messages on the screen:
Loading Linux core repo kernel ...
Loading initial ramdisk ...
/dev/sda3: recovering journal
/dev/sda3: clean, 330610/1749664 files, 5585671/6996827 blocks
And then it hangs right there. I have to hard-reboot after this.
I then tried to boot using the Arch Linux Installation USB (archlinux-2012.12.01-dual.img), which also hangs at a particular point, before it should show me the prompt. I took a picture of the screen where it hangs: Screen Capture. This is an issue with just my laptop, because the USB boots just fine on another laptop I tried.
I also have Windows 7 and Ubuntu 12.10 installed on my system, and I'm able to boot into both of them.
I have 2 hard drives: /dev/sda is a 120GB SSD, and /dev/sdb is a 500GB hard disk. My partitions are as follows:
sda1 - Windows 7 100MB System Reserved Partition (boot flag enabled)
sda2 - Windows 7 OS
sda3 - ArchLinux (boot flag enabled)
sdb1 - Ubuntu 12.10 (boot flag enabled)
sdb2 - Just data
I ran bootinfoscript and below is the output:
Boot Info Script 0.61 [1 April 2012]
============================= Boot Info Summary: ===============================
=> Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
=> Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
in partition 99 for .
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows 7
Boot files: /Windows/System32/winload.exe
sda3: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Mounting failed: mount: /dev/sda3 already mounted or sda3 busy
sdb1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 12.10
Boot files: /boot/grub/grub.cfg /etc/fstab
sdb2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders, total 234441648 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 206,847 204,800 7 NTFS / exFAT / HPFS
/dev/sda2 206,848 178,466,084 178,259,237 7 NTFS / exFAT / HPFS
/dev/sda3 * 178,466,085 234,440,703 55,974,619 83 Linux
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 63 20,948,759 20,948,697 83 Linux
/dev/sdb2 20,964,824 976,771,071 955,806,248 7 NTFS / exFAT / HPFS
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/mmcblk0p1 6665-3162 vfat
/dev/sda1 CA6A20CC6A20B75B ntfs System Reserved
/dev/sda2 1EE242D5E242B137 ntfs
/dev/sda3 65db0c59-9f04-46f1-975d-8a4c28132137 ext4
/dev/sdb1 bb9818db-ce7c-43a4-8ad5-8d3702001aed ext4
/dev/sdb2 3C2E3A4E2E3A0206 ntfs
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/mmcblk0p1 /media/dhaval/6665-3162 vfat (rw,nosuid,nodev,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush,uhelper=udisks2)
/dev/sdb1 / ext4 (rw,errors=remount-ro)
=========================== sdb1/boot/grub/grub.cfg: ===========================
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
if background_color 13,37,73; then
clear
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=7
else
set vt_handoff=
fi
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
if [ "${linux_gfx_mode}" != "text" ]; then load_video; fi
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
initrd /boot/initrd.img-3.5.0-21-generic
submenu 'Advanced options for Ubuntu' $menuentry_id_option 'gnulinux-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
menuentry 'Ubuntu, with Linux 3.5.0-21-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.5.0-21-generic ...'
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-21-generic
menuentry 'Ubuntu, with Linux 3.5.0-21-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.5.0-21-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.5.0-21-generic ...'
linux /boot/vmlinuz-3.5.0-21-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.5.0-21-generic
menuentry 'Ubuntu, with Linux 3.2.0-29-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-advanced-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
gfxmode $linux_gfx_mode
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro quiet splash acpi_osi=Linux acpi_backlight=vendor $vt_handoff
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-generic
menuentry 'Ubuntu, with Linux 3.2.0-29-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.2.0-29-generic-recovery-bb9818db-ce7c-43a4-8ad5-8d3702001aed' {
recordfail
insmod gzio
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
echo 'Loading Linux 3.2.0-29-generic ...'
linux /boot/vmlinuz-3.2.0-29-generic root=UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed ro recovery nomodeset
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-3.2.0-29-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux16 /boot/memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1 bb9818db-ce7c-43a4-8ad5-8d3702001aed
else
search --no-floppy --fs-uuid --set=root bb9818db-ce7c-43a4-8ad5-8d3702001aed
fi
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda1)' --class windows --class os $menuentry_id_option 'osprober-chain-CA6A20CC6A20B75B' {
insmod part_msdos
insmod ntfs
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 CA6A20CC6A20B75B
else
search --no-floppy --fs-uuid --set=root CA6A20CC6A20B75B
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
=============================== sdb1/etc/fstab: ================================
# /etc/fstab: static file system information.
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb1 during installation
UUID=bb9818db-ce7c-43a4-8ad5-8d3702001aed / ext4 errors=remount-ro 0 1
=================== sdb1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
4.564525127 = 4.901121536 boot/grub/grub.cfg 1
5.130507946 = 5.508840960 boot/initrd.img-3.2.0-29-generic 2
5.851592541 = 6.283099648 boot/initrd.img-3.5.0-21-generic 2
6.317649364 = 6.783524352 boot/vmlinuz-3.2.0-29-generic 1
4.965751171 = 5.331934720 boot/vmlinuz-3.5.0-21-generic 2
5.851592541 = 6.283099648 initrd.img 2
5.851592541 = 6.283099648 initrd.img.old 2
4.965751171 = 5.331934720 vmlinuz 2
4.965751171 = 5.331934720 vmlinuz.old 2
I tried adding nomodeset and acpi=off to the boot parameters, but the boot process still hangs. Please let me know if I should provide any other information.
Last edited by dhavalparmar (2012-12-30 11:45:25)Ok.. So my Arch Linux randomly decided to work. I'm sure I didn't do anything between my last "not working" state and my current "working" state. Below are a few things I tried:
I thought of trying an earlier build of ArchLinux, and downloaded archlinux-2012.11.01-dual.iso and made a bootable USB out of it. It still hung.
I was getting error messages during Arch boot that the last access time for the disks was at a future date. I found out that Ubuntu was using localtime instead of UTC and screwing up my hardware clock. I fixed it, and thought maybe the time issues were causing the boot problem. But fixing time didn't solve my problem.
I chrooted into Arch from my Ubuntu install, ran 'sudo pacman -Syyu' and updated my Arch install.
I thought maybe GDM isn't starting up. I re-enabled the service using 'systemctl enable gdm.service'.
I removed OpenNTPd and installed NTPd. Enabled the daemon using 'systemctl enable ntpd'
None of the above solved the problem, and rebooting to Arch still hung the system. So I stopped fiddling with it yesterday. Today, as usual, I just tried logging into Arch.. And it just worked out of the blue. The solution to me is as mysterious as the problem.
I told this to my friend who introduced me to Arch, and this is what he said:
Damn it computers, you were supposed to be deterministic! -
My 2007 MacBook pro won't boot up beyond a White screen any ideas what to do?
My 2007 MacBook pro won't boot up beyond a White screen any ideas what to do?
Odd how this hasn't been archived yet.
I'm getting the same thing with my Macbook, but can't boot past the white screen. An Apple store in KS suggested I needed a new hard drive, but I've already put two in there and it's still doing the same thing. I really don't want to buy another motherboard like I had to a couple of years ago.
My choices are either buy a cheap drive to boot from and remove the current one to put into an external case, or save the money by not buying a new motherboard and putting it as a down payment toward a Mac mini. -
Windows Server 2012r2 WDS capture image hangs at black screen
Ok so i upgraded my server to 2012r2 and i am using the boot.wim from windows8.1 pro iso. I create a deploy image and it boots up on my fujitsu stylistic machine. It also boots on my lenovo thinkpad yoga.
I go and create a capture image and at first fails so i added the usb3.0 lenovo dongle driver. It then shows me the windows logo and just hangs at black screen. I have downloaded the entire sccm driver package off lenovo site and nothing has
helped. It also does not load on the fujitsu machine either.
I have been going nuts any help is much appreciated
thanks
DaveHello,
Where did you get the original image? If you download it from MSDN or technet, can you provide the link?
And is update 1 integrated with the original image or you install it manually after installation?
In order to address the issue, we need collect some more informaiton.
Thank you. -
Dual G4 MDD - Boot problem - stopped at blue screen
Good day,
I am trying to revive a machine that was reported dead due to video card issue.
Replaced AGP graphics card with PCI - display OK.
Now I am experiencing further difficulty with the computer.
Computer boots to Apple logo and spinning wheel, then proceeds to blue background screen but no pointer and no further boot progression.
Here is the troubleshooting I have done thus far:
Verbose boot - option-V on boot, no hang-ups seen, but scrolls by rather quickly. Proceeds to blue background screen after verbose boot - same result.
Choose boot device - hold down option at boot - computer recognizes HDD boot volume and CD-ROM boot volume. Try booting to 10.3, 10.5 install CDs / DVDs, TechTool CD from AppleCare - same result.
2 HDDs installed; both cable-select. Remove secondary drive, set primary drive to master, then cable-select - same result.
2x 512K RAM installed; booted with only one, switched out DIMMs, switched RAM slots, installed known good 256K DIMM - same result.
Reset PMU via logic board switch - unplugged machine, pressed switch for 1 second, let sit for 2 minutes unplugged, plugged back in - same result.
Reset PRAM via keyboard - command-option-P-R on boot, wait for second chime, release - same result.
Reset PRAM via OpenFirmware - command-option-O-F on bootup, reset-nvram set-defaults reset-all - same result.
Set computer to target disk mode and installed fresh OS X 10.3 on primary HDD - same result
Boot to Apple Hardware Test CD - looped > 48 hours - reports no errors.
As you can tell, I think I have run out of troubleshooting options. My gut tells me it's a bad CPU, but I wanted to post here before running up the eBay / PayPal tree too far.
Let me know what you think. Thanks!I have had this problem twice, with 2 different fixes. It seems as if yours might be a little bit more serious. First question, how long do you let the computer sit there and try to get past the blue screen? When I got a PC --> Mac flashed Nvidia GeForce 7800 GS the "AppleHWSensor.Kext" was causing a blue screen for about 2 minutes before it would load the login screen. Removing that extension fixed it.
Second time I ran into this problem was when my system profiler was reporting "unable to report Firewire Devies" in red text. I still dont know for sure but i think my firewire port(s) have gone bad on my logic board. One or both of them. I fixed this by removing all of the .Kext files that had anything to do with firewire from my extensions folders.
These extension include :
IOFireWireFamily.kext
IOFireWireAVC.kext
IOFireWireIP.kext
IOFireWireSBP2.kext
IOFireWireSerialBusProtocolTransport.kext
In conclusion, I would say that there is some kind of hardware failure thats causing the boot to hang. The hard part is figuring out what. Goodluck! -
Unable to boot Z10, stuck on loading screen at 99% after a few hours.
Hi, I am unable to boot Z10, stuck on loading screen at 99% after a few hours. I did not try to update, nor load any other OS versions. Running a Bell Canada 10.1. Tried to pull battery, leave phone boot for 5 hours, still stuck on 99%. I tried plugging it in BB Link and computer will not recognize it.
dazedandconfused wrote:
Every option Im seeing is telling me Im going to lose my data... is this true? I know with other phones ppl are able to mount the device as if it were a hard drive and pull content from it... is this not possible with the Z10? Thanks...
I understand you are frustrated and seeking solutions, but please don't double and triple post your inquiry.
I've answered your thread already, here:
Re: Z10 stuck on loading logo on starting up
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 -
Unmountable Boot Volume on XP and screen goes blank before repair begins
The XP Windows partition was seemingly working fine until I turned on the laptop this afternoon. Took a minute or so longer to boot than usual and I was prompted when it did load to update Acrobat, which I did and it rebooted. Took longer to boot, perhaps two or three minutes and I received an Unmountable Boot Volume error. I rebooted a few more times, same result. I tried system restore to three previous dates over past ten days and was told after attempted reloading that it had failed and I should try another day. Worried about my data, I went to safe mode to back up C: drive.
The general advice from MS is to use the Windows installation CD to repair the boot sector. With the CD in, Windows will boot and show my normal desktop and files, though will on perhaps the third item to load to memory, the screen goes blank and the loading seems to continue, as I hear sounds though not sure if it is the programs or the repair.
There does seem to be an ability for it to boot, just not maintain it through full load. Any suggestions short of reinstalling windows would be welcomed. Thank you.I was unistalling some usless programs when my laptop died & when I turned it on I had unmountable boot volume 0x000000ED (the blue screen)
If I hit repair windows it goes to a black screen with the mouse (nothing else)
Now I tried f8 & then did command prompt but after it had gone to the loading files screen it had gone back to the blue screens with unmountable boot volume 0x000000E
I DL windows 7 repair but how do I get it to install when I cant get past the blue screen?
so i decide to repair it my self and then i found this great solution what helps me -
My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you think it is? It won't recognize any hard drive I put in the machine, so might it be the sata cable?
Boot the Recvoery USB, use Disk Utility to select the internal drive makers namea and size on the left.
Now select erase and select the midde option and click erase, it will take a bit to complete but it's best for the drive.
Now select Partiton tab, click the big box and Options: GUID and then Format: OS X Extended journaled and click apply.
Quit and you should be able to install OS X now with your Apple ID and password.
see
http://osxdaily.com/2011/08/08/lion-recovery-disk-assistant-tool-makes-external- lion-boot-recovery-drives/
Maybe you are looking for
-
Creative Cloud updates fail due to error U43M1D212
Problem: Creative Cloud desktop is installed. Login to Creative Cloud works. Applications can be installed BUT applications CANNOT be updated. Error message: "Unable to reach Adobe servers" System: Windows 7 Ultimate, 64-bit What I've tried so far: 1
-
How to export user defined properties in seperate file
Hello, i want to export user definied properties in a seperate file using OMB+ commands. The documentation of this topic doesn't work. The OMB Code I use is the following: OMBEXPORT TO MDL_FILE '${Pfad}/006_${Project}.mdl' \ FROM PROJECT '${Project}'
-
I can create apple ID in mozilla firefox. But I can't sign in on itune. After I fill up all with without using credit card, it appears this sentence "please contact itune support to complete this transaction." I use both mac book pro & sony vaio. Lik
-
Currently my display card is a NVIDIA Quadro FX 500/600 PCI. One of the reasons I chose this card is it supprted dual montors. Now that I have upgraded to CS4 Extended I need to upgrade my display card. When I went to Adobe's List of tested graphics
-
How can I transfer my MAC itunes library to a PC?