[SOLVED] HP Envy 14 Installation Media Won't Boot Beyond Grub

I just got an HP Envy 14. I've heard of some minor Linux issues with it, but all well past the installation phase.
As for me, I can't get the installation CD/USB to load beyond GRUB. I select the first option - to run the OS live from the USB/CD - and I see the first few lines of the correct output (decompressing kernel, etc.). After that, it hits a blank (black) screen and hangs. Five or ten minutes later - nothing, still black screen.
Has anybody else had this issue - with the Envy or any other computer? I've installed Arch on a few other computers before and never run into this problem.
Last edited by chimeracoder (2011-08-28 18:03:49)

This may be set a record for the fastest/most mundane solution ever! It turns out that the screen turns off after GRUB loads Arch (this isn't just an Arch issue - I tried it with a Xubuntu live CD I had lying around as well). Anyway, if anybody else has this problem as well, just turn the brightness back on once you're past GRUB and you should be good to go.

Similar Messages

MacBook Pro Won't Boot Beyond Grey Apple Screen - Mystery Partition Found

My MacBook Pro, which suffers from appalling overheating (94 degrees C in each core last week) won't boot beyond the grey apple splash screen. I booted from a Developer's disk and ran Repair Disk/Disk Permissions. Both verified AND said the repairs failed. The drive (as opposed to the volumes) said it had no valid files and thus couldn't be repaired even though it verified. I target-disked it to one of my G4s and took off a bunch of apps and lightened its load, waited a while and tried again--it's been grey screen gear turning for 20 minutes now. I have Remote Desktop but it won't respond to that. Of course, Windows XP boots up perfectly normally on its Boot Camp-created partition, dumbly unaware of the general chaos on the other side.
While I had the Disk Utility from the boot disk on, I noticed my partition scheme had changed somehow. The big partition with the system was now in position #2, set between #3 (Windows--formerly #2 of 2) and a new one of only 200MB called #1 which is formatted OS X Journaled. I didn't make that partition and it couldn't be erased. I think the cpmputer is looking in the #1 spot for a system and can't find it because some renegade partition with no brain has pushed its way to the front. How do I annihilate that thing and get on with it? How did it get there?
Has anyone tried that alter the Apple Blower/Fan hack said to turn the fans on permanently?
For the record, I'm in L.A. and the ground has been rocking and rolling for the past 3 minutes on and off.
MacBook Pro 2.0/2GB/100GB Mac OS X (10.4.8) TiBookG4 1.0/512K/60; PowerMacG4 Quicksilver 933/1G/160; PowerMacG4 450/512K/30

I called Apple's Tech Support and they had me do perform sevral procedures I had done already, none of which worked. They suggested that the mystery partition (which has since ceased to reappear in the Disk Utility's view of the partition scheme) was an anomaly caused by the still-Beta Boot Camp--nothing was said about Windows XP booting, but I think you're right because whenever installing Windows, it always reserves a small "free space" on the PC's drive for its own purposes. Anyway, I'mre-installing now but very unhappy to hear I have suspected all along--the overheating is killing the computer. I know this from experience because Ihad a Powerbook G4 with a at-that-time-not-yet-recalled battery that overheated to such an extent that it fried the logic board and the harddrive. After a year of arguing with Apple, they replaced the computer with this MacBookPro--and overheating laptop that also had its battery recalled, has already been sent back to Texas for over heating (they replaced the superdrive which of course had no effect on the heat issue) and now has hard drive problems. I have two old PowerMac G4s sitting here plugging along--maybe I'm over laptops. Thanks
MacBook Pro 2.0/2GB/100GB Mac OS X (10.4.8) TiBookG4 1.0/512K/60; PowerMacG4 Quicksilver 933/1G/160; PowerMacG4 450/1GB/100

[SOLVED] Switch to systemd - Now system won't boot

I saw that todays update upgrade included the installation of systemd. I looked the wiki and did the necessary changes (I already had made the /etc/hostname etc. files). So I added the
init=/bin/systemd
line to grub and now my system won't boot. I get an error saying something about syslog service not enabled and then a black screen. I can boot my machine fine without the "init=/bin/systemd" line but I want to run a pure systemd system since Arch is moving to it anyway. In the wiki it mentions to install systemd-sysvcompat but it conflicts with initscripts it says. What am I doing wrong or missing?
Last edited by fettouhi (2013-12-08 14:42:04)

fettouhi wrote:
Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

After windows 10 installation, pc won't boot

I tried to update my OS to windows 10, but something happened during the instalation that it can't boot anymore. It tries to recover the OS, but then a blue window is diplayed saying something wrong happened and then it reboots. This goes forever. I tried to create an installation media for Windows 10 and isntall again and boot using the usb drive, but same problem. Then, I tried to create an installation media for Windows 8.1 and still can't go forward. Is there a way to recover the system or at least format and reinstall any OS?

Hi there , Thank you for visiting the HP Support Forums and Welcome! This is a great site to get answers and ask questions. I have looked into the issue you had mentioned in your post on the HP Support Forums. I understand that you are receiving a Blue Screen and cannot boot into an Operating System. Here is a document I found called Computer Does Not Start (Windows 10). Have you tried performing a hard reset?Have you tried to do a Hardware Test?What error messages are you receiving? Can you repeat the exact error for me for more specific results? Here is another document called Error Messages Display on a Blue Screen during Startup or Boot (Windows 10, 8, 7). This specific document is used if the computer stops responding and displays a blue screen or continually restarts. Please follow these provided troubleshooting steps, re-post and let me know the results and the answers to the questions above. Thank you! Have a great day!

Snow leopard installation disc won't boot. Can I reset computer to boot from internal hard drive at startup?

I recently installed snow leopard on my macbook (mid 2006). I used system preferences to set the snow leopard boot disc as the install disc, and now my computer won't boot. It stalls at the apple icon with the grey screen. Is there any way I can set my computer to reboot from my internal hard drive at startup without having access to system prefernces (a keyboard code or something)?

Thank you so much for responding. I actually just pushed the trackpad button at startup. It ejected the install disc and automatically booted from the internal. I am sure your method would have worked as well. Thanks again!

Apple won't boot beyond chimes

My Imac 24 inch does not boot beyond the chimes. When I reformatted, it worked but I could not install my Adobe CS3 and on restarting again after 2hrs it did the same thing stopped booting after the chimes. Please I need help to solve this

Hi
When you boot up, you should get a single chime (equiv chord of G apparently). Multiple chimes on startup can signify possible hardware problems. Have you checked your RAM to see if it is correctly seated (may be loose)?
Steve
Oops, didn't see last post, sorry. Please mark your thread as Answered so people know problem is solved. This helps other people with same problem find answers to their problem when using the filters.

Laptop won't boot beyond the screen showing "Tobshiba leading innovation"

I installed an antivirus recently and in its scan some viruses were found. Those viruses were deleted and now my laptop wont boot into windows. It just stays where "toshiba" logo is displayed. My laptop is running on windows 8.1. I have a recovery DVD, but the laptop won't boot from the DVD either. Is there a way to get my laptop to boot windows without doing a factory reset. Please help!!

Try the Troubleshooting Assistant or the suggestions in this article.
What can I do if my Windows 8 laptop won't start?
- Peter

[Solved]USB Flash Installation Media fails on booting kernel

I've been trying to install Arch on my desktop however the live USB keeps failing to load. The process of loading modules freezes at random points. I've tried acpi=off and mem=2048M, as well as enabled various debugging flags. It doesn't freeze at the same spot on different tries. I tried loading from RAM and dd'ing the drive, I'm sure the drive works because my laptop can boot off of it. I've ran out of options, can anyone help?
http://i60.tinypic.com/2rca6bp.jpg
http://i62.tinypic.com/6z9fsl.jpg
EDIT: Nevermind nomodeset worked....
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code [jwr] --
Last edited by Pentlander (2014-03-28 01:52:25)

@DSpider: Please stop FUD about archisolabel and related message. I suggest to learn how boot things really works.
Reaching such message is because some of these things fails:
1) User does not setup a filesystem label when copy ISO contents to booteable media (usb drives). In that case, if users insist in not using label, there is a boot option archisodevice=...
2) Broken/incompatible/unsupported hardware/firmware on Linux and sometimes with udev built-ins (cdrom_id, ...). -> Needed modules not loaded or loaded but not working for boot medium.
Again, archboot work in a really different way than archiso. It just work on initramfs (rootfs), so there is no need to detect and mount boot media then switch_root.
So please finish with these false alarms. I already read several of your messages in different places on this forum, repeating the same thing over and over again.
PS1: Archiso will continue using the great label-system.
PS2: memdisk is the most discourage method to boot especially in x86_32.

[SOLVED] Fresh Install, won't boot past grub

I did a fresh install of Arch (GPT partitioning table) with a 8 GB root directory, 138 GB home directory, 4 GB swap, and a 1007 KB bios boot partition. Everything went well, I got through the installation with no problems, but when I rebooted the computer. It showed this after the grub menu: https://lh6.googleusercontent.com/-UM-3 … 2014-06-22
So now my question is, was I supposed to do anything extra during the installation process? Or is this a hardware problem? Linux Mint, Ubuntu, Lubuntu, and Zorin OS works fine so I'm assuming I need to do something extra during installation...
Last edited by ryukiri (2014-07-03 21:44:44)

Trilby wrote:
ryukiri wrote:That only tells me how to make it a boot option...I assume I need to be chrooted from the install CD to do this.
You can do it one of two ways: boot the install cd/usb, mount all the partitions as in the original installation process, then chroot. From there you can just use pacman to install packages as it it were a normal system: `pacman -S linux-lts`.
There is, however, no need for the chroot. The alternative, and somewhat simpler, approach would be to boot the install media and mount the partitions as above, then use the pacstrap tool just like you did when installing the 'base' group: `pacstrap -i /mnt linux-lts`.
I think it is safer to arch-chroot because you still need to be chrooted to generate your grub.cfg "grub-mkconfig -o /boot/grub/grub.cfg"
Last edited by ugjka (2014-07-03 08:24:30)

[SOLVED] Installed Win 7, now Arch won't boot

Edit: To save anyone reading this all the way, the problem turned out to be a badly edited fstab. Sigh.
PROBLEM:
Grub loads, then loads the kernel, but the boot hangs a few seconds later with no real error messages.
BACKGROUND:
1) I needed to boot a native Windows 7 partition on my 128GB laptop SSD.
2) So, I used gparted in an Ubuntu Live USB to resize my existing Arch partition and create an NTFS partition for Win 7:
sda > sda1=Arch > sda2=ntfs > sda3=linux swap
Arch still booted fine after this (sda1).
3) I then installed windows 7 (BIOS install) onto the second partition (sda2). I don't know where or if it puts some system reserved partition - but I can't see anything in gparted.
4) chrooted from an Arch Live USB, reinstalled GRUB, including mkconfig step
5) *If* I recall, Arch then booted OK.
6) Booted into Windows and applied all updates, set windows to use UTC clock and updated my laptops BIOS. Reboot.
7) Win 7 boots fine from the grub menu from (hd0,2)
8) Arch starts booting, loads the kernel, then hangs after the kernel has loaded, but before gdm appears. With the following on screen:
[2.104597] INFO @wl_cfg80211_attach : Registered CFG80211 phy
I have tried chrooting and reinstalling linux and linux-headers and grub. But so far to no avail.
[SOLVED with face palm]
I installed syslinux using chroot, as it displays more startup messages. The boot was hanging at [a disk task is starting] or words to that effect. It was my USB stick, which I'd foolishly added to fstab with the "auto" option. Editing that out of fstab - and it's all good.
I'll leave this here in case anyone else does something this dumb.
Last edited by sultanoswing (2013-10-30 08:09:03)

fettouhi wrote:
Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

Failed XP installation, now won't boot OS X

Hi, I just got my Mac Pro and am experiencing problems after trying to set up a second partition with Windows XP. On top of the 500GB HD, I installed a Western Digital Caviar Green 1TB internal drive, which I had planned to install Windows on. After a failed attempt to format & partition the drive with Windows XP (I kept getting a black screen with "The following file is missing or corrupt: \system32\hal.dll"), I gave up on XP's problems, restarted in OS X and deleted the Windows partition through Boot Camp Manager.
Now when I boot up my computer, I'm greeted with a black screen and a blinking cursor. That is unless I hold down Option and select "Mac OS X". However, that is going to get old after a while. I'm guessing it's still trying to boot up Windows even though it was supposedly deleted. Any help would be greatly appreciated!

MDew1:
Please try the following:
1. Boot into Leopard as you do with holding down the Option Key.
2. In Leopard go to *System Preferences*
3. Under System select *Startup Disk*
4. Highlight *Mac HD* and Restart
See if the above works for you and that you no longer have to hold down the Option key during the subsequent startups.
Axel F.

Won't boot beyond grey screen. Gear just spins.

I have a MacBook Pro. I recently updated to OS X 10.8.2. Once this update was completed I updated my iPhone 4S to OS 6 followed by my iPad. This was done over successive days. My problem started one morning sending an email reply via Mail. I was also checking some Internet news sights. Suddenly I lost my connection and noticed the email had not been sent. I closed Safari and re- opened it only to see the message that I was not connected to the Internet. The other laptop in the household could connect but not mine. I choose to restart it but it never would get beyond the grey screen. Sometimes the gear freezes or just keeps spinning. I have tried everything, rebooting holding down command S to do an fsck -y check, holding down the shift key, and holding down the option key to select the recovery disk. Still nothing. I tried using a FireWire connection to my desk top. I used Disk Utilities to perform First Aid on the volume. I backed up the volume also this way. I then tried booting from the last OS X disk I had (Snow Leopard). I can hear the disk working but then the laptop freezes and the error message tells me that I must shut down and reboot. It restarts but it continues to reboot on its own over and over until I shut it down. I was hoping that I could do a clean install and start over but I can't get the laptop to boot from a disk I have in my possession.
What can I do?

This link is for troubleshooting the 'Gray Screen' problem....
http://support.apple.com/kb/TS2570
Hopefully it won't take a clean install

New Install Won't boot after GRUB

I have been using ArchBang for the past year and a half so I finally thought that I knew enough about Linux to try installing a true Arch Linux system.
I followed the beginner instructions carefully and was able to successfully install my system (or at least I thought) and GRUB. I am currently running my system on a Dell inspiron with two separate hard drives. The primary drive is the one I am trying to install Arch on while I have Windows 7 installed on the second drive.
The drive I installed Arch on is /dev/sde. I think that I successfully installed GRUB given that when I boot my computer it goes into GRUB and shows both my Arch Linux install and my Windows 7 system and when I select Windows 7 in GRUB it successfully boots.
But when I selected my Arch install in GRUB the system does not boot. It just shows:
/dev/sda1: clean, 31087/3751936 files, 478966/15000685 blocks
and then I am left with a blinking cursor and after a few minutes I get:
Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode.
Give root password for maintance:
Anyone one how I fix this? Do I need to reinstall? As I said before I didn't receive any errors during the install and GRUB seems to be working correctly. Please remember that I am a newbie but please help!

Trilby wrote:
No you don't need to reinstall, you do need to fix your grub configuration though. It sounds like it is not properly pointing to the root partition.
Post your grub config and your partitioning scheme.
Partition Scheme from lsblk output:
Name MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931G 0 disk
sda1 8:1 0 57G 0 disk /
sda2 8:2 0 7G 0 disk
sda3 8:3 0 866G 0 disk
sdb 8:16 0 111G 0 disk
sdb 1 8:17 0 111G 0 disk
sr0 11:0 1 1024M 0 disk
I don't now if this output of the partition table is what you want given that the lsblk is the only command I am familiar with. The sdb disk is where the windows install is.
Here is the /boot/grub/grub.cfg file:
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
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}"
saved_env saved_entry
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='hd4,msdos1'
if [x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 9fd0e01-89b1-494c-908f-e89db34d80e0
else
search --no-floppy --fs-uuid --set=root 9fd0e01-89b1-494c-908f-e89db34d80e0
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_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-9fd0e01-89b1-494c-908f-e89db34d80e0' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd4,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 9fd0e01-89b1-494c-908f-e89db34d80e0
else
search --no-floppy --fs-uuid --set=root 9fd0e01-89b1-494c-908f-e89db34d80e0
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinux-linux root=UUID=9fd0e01-89b1-494c-908f-e89db34d80e0 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### 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_memtext86+ ###
### END /etc/grub.d/20_memtext86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sdf1)' --class windows --class os $menuentry_id_option 'osprober-chain-44F084A6F0849FB2' {
insmod part_msdos
insmod ntfs
set root="hd5,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd4,msdos1 --hint-efi=hd4,msdos1 --hint-baremetal=ahci4, msdos1 44F084A6F0849FB2
else
search --no-floppy --fs-uuid --set=root 44F084A6F0849FB2
fi
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This files 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 ###
Last edited by johnnymike (2012-10-15 01:52:09)

G5 tower won't boot beyond chime, fan is possessed?

Hi, have been having problems with my Dual 2.5 GHz PowerPC G5. Fan has been running loud and fast, and on last restart, whirred like crazy w/no reboot. Shut off by pressing power button on front of unit and waited a few minutes. Now when I try to turn on, I get a chime and brief noise as if trying to start but then nothing but blank screen (if I leave on, the fan gets loud after a few minutes). Also tried unplugging power cord for a few minutes then restarting, but that hasnt worked. Cannot find my OS X disks (augh!), so what now? Would appreciate any help.. thanks .
P.S. Just bought a new super-de-dupery mac pro and was getting ready to backup my G5 before transferring files. How does it know...?

Bob Ayre wrote:
I had the same trouble 2 years ago.... Turned out to be a bad RAM chip. I had enough RAM to pull two bad chips. I have been running on 3GB since then. The computer ran fine until this AM. I cant start it but the fan doesnt wind up. Good luck.
Bad RAM may sometimes cause the power LED to flash in a particular pattern on power up, though this usually happens when you don't get the boot tone (or as we like to call it, the chime). Something to note when you attempt to power up.
See http://support.apple.com/kb/HT1547 for some information, some of which applies to G5s.

System won't boot to USB Recovery Media

I have a Satellite P55-A5312 with pre-installed Windows 8 (upgraded to 8.1), Intel i5 processor and 6GB Ram. I created a set of DVD recovery media and a USB Flash (Toshiba brand 32GB) recovery drive. I set the boot order in BIOS to USB, then DVD, then HDD. Secure Boot is enabled.
Question I have is, how can I verify that the reovery media will boot if needed? If I power on the laptop, neither the DVD nor USB will boot and it goes directly to Windows, which kind of makes sense. If I then restart, the DVD recovery media will in fact boot, but the USB recovery media won't boot. Even if I restart with F12 and choose USB as the boot device, the USB media will not boot. The only way I can get the USB recovery media to boot is if I disable Secure Boot.
I find it hard to believe that USB recovery media will only work if Secure Boot is disabled. What am I doing wrong?
Ken
Solved!
Go to Solution.

Sure would be nice to know what the recovery media boot behavior is suppose to be with Secure Boot enabled...
With a little luck, Peter will stop by and let us know.
-Jerry

[SOLVED] HP Envy 14 Installation Media Won't Boot Beyond Grub

Similar Messages

Maybe you are looking for