[SOLVED]Unknown boot option `radeon.modeset=0'

Hi All. I've just installed newest kernel from testing repo (2.6.31). After that on my MobilityRadeon X1400 the 3D acceleration stopped working (I've used "early start method" from ArchWiki). So i've set /boot/grub/menu.lst a follows:
# (0) Arch Linux
title Arch Linux
root (hd0,1)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/ad5d0eae-969d-4e29-a98e-925480dc4519 radeon.modeset=0 ro quiet vga=838
initrd /boot/kernel26.img
And during the reebot i can see: Unknown boot option `radeon.modeset=0' ignoring
Despite it 3d acceleration works fine after that. Can someone explaint the problem?
Last edited by Nixxx (2009-10-12 23:30:58)

@Zariel: While disabling KMS I've removed "radeon" from MODULES in /etc/mkinitcpio.conf and then I've lunched "mkinitcpio -p kernel26". Shoud I do anything else? As AndyRTR wrote despite this message KMS seems to be disabled bacause the 3D acceleration is working fine - "modinfo radeon" says:
filename: /lib/modules/2.6.31-ARCH/kernel/drivers/gpu/drm/radeon/radeon.ko
license: GPL and additional rights
description: ATI Radeon
author: Gareth Hughes, Keith Whitwell, others.
license: GPL
alias: pci:v00001002d00009714sv*sd*bc*sc*i*
alias: pci:v00001002d00009713sv*sd*bc*sc*i*
alias: pci:v00001002d00009712sv*sd*bc*sc*i*
alias: pci:v00001002d00003150sv*sd*bc*sc*i*
depends: drm,ttm,i2c-core,i2c-algo-bit
vermagic: 2.6.31-ARCH SMP preempt mod_unload 686
parm: no_wb:Disable AGP writeback for scratch registers (int)
parm: modeset:Disable/Enable modesetting (int)
parm: dynclks:Disable/Enable dynamic clocks (int)
parm: r4xx_atom:Enable ATOMBIOS modesetting for R4xx (int)
parm: vramlimit:Restrict VRAM for testing (int)
parm: agpmode:AGP Mode (-1 == PCI) (int)
parm: gartsize:Size of PCIE/IGP gart to setup in megabytes (32,64, etc)
(int)
parm: benchmark:Run benchmark (int)
parm: test:Run tests (int)
parm: connector_table:Force connector table (int)

Similar Messages

[SOLVED]-ish boot/device/radeon issues after recent upgrade

Hi, I am having major issues after last update. Basically it seems it is no longer loading drivers correctly at boot. I have a radeon graphics card, and the screen resolution normally switches during the boot process (presumably when the radeon module loads). This is no longer happening, so X is not starting for me. The network card is also not being picked up.
When i look at the boot log there is no errors i can find, but also there is NO [drm] messages at all (there is normally a fair few as it sorts out the graphics card.
I am still investigating, but if anyone has any ideas I'd be grateful (should i be looking at mkinitcpio? or the kernel itself? or the ati-dri ? what exactly were the changes made to the packages in the last couple of days on this sort of thing?
Last edited by WombleGoneBad (2012-07-15 11:37:00)

Hi i have sorted it. Unfortunately i am not sure exactly *how* i sorted it, I did another pacman -Suy which installed linux-utils (which i cant see affecting much). Unfortunately i had switched to a custom kernel when i first got the issue with the arch one, when i switched back again suddently everthing started working.
I understand the /usr/lib changes look like they have screwed np my custom kernels modules folder. But i still dont know why i got the problem in the first place, as it was with the arch standard kernel and ram disk if first got the issue. Anyway gone now. and the network card is working too.

Unknown kernel option and a freeze, help please!

Hi,
Reopening this thread - I had to re-start at boot three times today. The kernel freezes up on boot, right before I'm supposed to load the console fonts. On boot, my fonts change, so that could be the point where the thing freezes...
Uname -r gives "2.6.36-ARCH", possibly this started after the last update, I dunnow...
What's the next step I take? Except a panic, please, no more panic!!! Please help, thanks.
Thor
Edit : this is what it said :
unknown boot option+0x0/0x19f
Any clues?
Edit - once up and running, the thing keeps going. Udev is 165-1 according to pacman.log...
Edit - This was reported (today?) as a bug ( https://bugs.archlinux.org/task/22343 ) so, all I can say is "go-developers-go!!" and I'll just w8 the ride, I guess...
Last edited by Thor@Flanders (2011-01-19 09:46:38)

Hi,
I too just recently had a Kernel Panic. I think mine was related to video. Yours looks like there are hints to storage problems? Look at these:
dependency: com.apple.iokit.IODVDStorageFamily(1.4)@0x6e4000
dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(1.4.4)@0x52a000
dependency: com.apple.iokit.IOStorageFamily(1.5)@0x4e3000
dependency: com.apple.iokit.IOSCSIBlockCommandsDevice(1.4.4)@0x6eb000
dependency: com.apple.iokit.IOCDStorageFamily(1.4)@0x6da000
com.apple.iokit.IOSCSIArchitectureModelFamily(1.4.4)@0x52a000
Do you have SCSI drives? I don't even really know how to read these as I am really guessing based on reading previous posts and seeing other logs including mine. I never had a kernel panic until I installed 10.4.4 So I suspect there is maybe a bug in 10.4.4, maybe in the video driver or my Graphics card is croaking.
How long have you been having Kernel Panics? Since what version of the OS?
Here is a link I have seen posted on here several times.
http://www.thexlab.com/faqs/kernelpanics.html
Thanks,
RacerX

[SOLVED] Board no longer sees uefi as boot option

Hi,
I installed Arch on an ssd and was using rEFind to boot the system. It was working fine until I unhooked the ssd from the Mobo to install a hard drive with an old version of arch.( I was going to use the hd for extra space) However, when I hooked my ssd back up the bios did not detect the uefi. It shows the ssd but not the option to boot with uefi.
When I run lsblk -f from my old installation I can see that the ssd is not mounted to anything. I can mount the ssd with the old installation and see all my files. I just can't boot to the ssd. Any Ideas?
I have an Asus mobo and a Kingston ssd. Probably not relevant info but thought I would mention it just in-case.
Last edited by Mgrim (2013-03-08 05:42:47)

ls -l /dev/disk/by-partuuid/ output
lrwxrwxrwx 1 root root 10 Mar 4 15:12 0c20bfb2-b03b-467f-9faf-d8f7311027ec -> ../../sdb4
lrwxrwxrwx 1 root root 10 Mar 4 15:12 38362986-f8ad-416d-86eb-659f7e78f8c3 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Mar 4 15:12 628b4764-b385-4f6c-a92c-8c1ccc551e19 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Mar 4 15:12 82e01db0-b264-4555-910d-aa020bccb086 -> ../../sdb2
-not sure how to do this for sda drive
refind.conf
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 20
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner
# label - text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# all - all of the above
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported.
#banner hostname.bmp
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits.
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Use text mode only. When enabled, this option forces rEFInd into text mode.
#textonly
# Set the screen's video resolution. Pass this option two values,
# corresponding to the X and Y resolutions. Note that not all resolutions
# are supported. On UEFI systems, passing an incorrect value results in a
# message being shown on the screen to that effect, along with a list of
# supported modes. On EFI 1.x systems (e.g., Macintoshes), setting an
# incorrect mode silently fails. On both types of systems, setting an
# incorrect resolution results in the default resolution being used.
# A resolution of 1024x768 usually works, but higher values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans. If a specified
# directory doesn't exist, it's ignored (no error condition results).
# The default is to scan no additional directories.
#also_scan_dirs boot,EFI/linux/kernels
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP.
#dont_scan_dirs EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,MokManager.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Most notably, if you
# want to give a kernel a custom icon by placing an icon with the kernel's
# filename but a ".icns" extension in the same directory as the kernel, this
# option will cause the icon file to show up as a non-functional loader tag.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
Last edited by Mgrim (2013-03-05 16:07:44)

A friend bought second hand macbook air mid 2011 with crossed circle on the display, we tried recovery from partition and same thing happened, after internet recovery it stays the same except now it asks for password for boot option, what happened?

A friend bought second hand macbook air mid 2011 with crossed circle on the display and give to me to try to recover the system, I tried recovery from partition and same thing occured, after internet recovery it stays the same-crossed circle after reboot, then we tried to boot from USB with mac os 10.8 on it, it installs something,like it has being finishing installation, rebootes, and now it asks for password for boot option.We have no idea what that password could be.What happened!!!

I forgot to write down my computer specs:
iMac 27 Mid 2011
2.7 GHz Intel Core i5
4 GB 1333 MHz DDR3
AMD Radeon HD 6770M 512 MB
OS X 10.9.2

Boot options duplicated; Boot Camp Assistant newly non-functional

Short version:
1. Up to tonight, my hard drive was encrypted using PGP Whole Disk Encryption -- secure boot and all. Had Boot Camp working fine with it.
2. Attempted to install OS X 10.6.5 despite PGP warnings to decrypt first. Ended up with an unbootable OS X partition. Decrypted drive in Windows, got back into OS X.
3. Disk Utility returned a few errors on OS X partition. Quickly fixed those by booting from Snow Leopard CD and running it.
4. What I'm now noticing is that when I hold down the option key, I'm given duplicate options. Instead of "OS X Partition Name Here" and "Windows 7 Name Here", I've got a duplicate for the former. So my options are "OS X", "OS X", or "Windows".
5. And, when I try to run Boot Camp Assistant out of curiosity, I'm told that I either need one big non-partitioned drive, OR existing partitions created by Boot Camp. I already did that.
Any thoughts on fixing #4 or #5? Resetting PRAM doesn't help. Windows does not show as an option in "Startup Disk" in system preferences. But the Windows partition boots just fine when holding option on restart.

And since I can't edit my original post any longer, here's what fixed the redundant boot option thing:
http://hints.macworld.com/article.php?story=20091111185717745
Worked like a charm. Fixed the duplicate "OS X" option on boot, and both OSes boot normally. Can now click past the first few options in Boot Camp Assistant, so I'm assuming that's working normally now also.
Still no Windows option in Startup Disk, but apparently that's related to my use of NTFS-3g? Thought that was fixed.
sudo fdisk /dev/rdisk0 is now:
Disk: /dev/rdisk0 geometry: 30401/255/63 [488397168 sectors]
Signature: 0xAA55
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
1: EE 1023 254 63 - 1023 254 63 [ 1 - 409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [ 409640 - 423624704] HFS+
*3: 07 1023 254 63 - 1023 254 63 [ 424298496 - 64098304] HPFS/QNX/AUX
4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
Only thing I'm worried about now is whether I might have damaged any files though any of this crap. Don't know if I can check for that, or if I should worry about it.

Pavilion dv7 advanced boot options keyboard not working

1. Print screen key has never worked
2. In Advanced Boot Options screen, arrow keys do not function to select Safe Mode, Esc key does not work to cancel out of screen.

Hi,
Does the arrow and esc key works in Windows?
If it doesnt work in windows also then i can suggest you to try doing a hard reset and check..else could be a hardware issue
How to Perform Hard Reset
Note:
If you have HP Support Assistant installed on the computer(The Blue Question Mark) then open it ==> Complete all pending Updates & Tuneups==> Restart and Check. It may solve your problem
Although I am an HP employee, I am speaking for myself and not for HP.
**Click on “Kudos” Star if you think this reply helped** Or Mark it as "Solved" if issue got fixed.

Windows Server 2008 R2 SP1 - Safe mode not listed in Advanced boot options

HI all,
After a bad driver installation, the server got the blue screen issue.
I tried to access the safe mode and make a restore, but unfortunately the safe mode is not listed in the advanced boot options.
The only options available pressing F8 at boot are :
Repair
Normal mode
Am I missing something ?
Is there a way to launch the safe mode from the console (accessible from repair mode) ?
Is there a way to restore from the console ?
Thanks for your help, for now I am really stucked...
Olivier Tisserand

Hi again
Problem solved, I document the solution for others :
open a console from repair mode
search the real system drive, instead of the X: default of the console
inn my case D:
cd Windows/system32
SystemHardwareProperties
Advanced options
start and recovery
tick the 'show os list' with 30 sec timer
close and reboot
when the system list appears, press F8 on wanted os
Then complete Advanced Boot Options menu appears, including safe mode
That saved my customer's server
Hope that helps...
Olivier Tisserand

G400s bios don't have usb boot option

hi all
my laptop is G400s, i want try install linux but i got to bios but usb boot option missing ,
any option i wrong to choose or any suggetion?
pictur below is my bios setting picture:
Link to picture
Link to picture
Link to picture
Link to picture
Moderator note; picture(s) totalling >50K converted to link(s) Forum Rules
Solved!
Go to Solution.

hi try2ops,
Welcome to Lenovo Community Forums!
The options set under your BIOS are all set,
With that, try this
Plug in your Bootable USB
Power ON your system then right away start hitting F12
It should give you a Boot Menu Including USB as bootable.
Hope this helps
Cheers!
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

HOW TO YOU ADD USB FLASH DRIVE TO BOOT OPTION

i HAVE TWO LAPTOPS SAME MODEL NUMBER ONE CRASHED, hp SUPPORT TALKED ME THROUGH F11 TO RECOVER TO FACTORY CONDITION THE LAPTOP STOP AT 100% WITHN1 MINUTE LEFT TO CMPLETE. HP TOLD ME TO ESCAPE AN DO F2 TO CHECK THE HARD DRIVE. THAT WORK IT SHOWED ALL THE CHECKS PASSED. IT TOOK 2 + HOURS SO WHEN i CALLED BACK DIFFERENT PERSON SAID $350 SEND IT THEY WILL FIX. iT'S NOT IN WARRANY SINCE FEB2014 i ONLY PAID $399 FOR IT, CANNOT AFFORD THAT. SO HP TECH SAID USE SECOND PC TO MAKE A FLASH DRIVE . (I MADE CD'S WHEN I FIRST GOT IT BUT THEY DID NOT WORK). SO GOT A FLASH DRIVE WTH 32GIGS (I THOUGHT SHE SAID I NEEDED AT LEAST 20 GIGS) COPIED THE RECOVERY PROGRAM, NOW THE USB WILL NOT OPEN. FROM AN EARLIER WRITTER HE WAS TOLD TO F10 BIOS, ESC LOOP FOR BOOT OPTIONS TO SEE IF USB FLASH DRIVE IS THERE. MY PROBLEM ITS NOT ON MY PC SO HOW DO I ADD IT SO THE USB WILL OPEN.
RIGHT NOW PC IN A LOOP WHEN POWERED ON HP AND TIME COMES UP, LITTLE WHILW A BLOCK WITH HP/DAT/TIME COMES UP AND A CMD ON BOTTOM OF SCREEN, IT GOES BY TOO FAST T CLICK ON IT AND GOES BACK TO HP LOGO. IF I COULD ADD USB FLASH AS AN OPTION IT MIGHT MAKE IT OPEN ANY HELP APPRECIATED.

The flash drive is not going to show up if it is not bootable. To make a bootable Recovery on flash you have to use Recovery Manager just like you do to create cd/dvd Recovery.
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

RESET THE NO. OF PROCESSORS IN THE BOOT OPTION TO NORMAL

I accidently switched the number of prcessors to '1' in the boot option in my laptop and clicked on apply & my pc is working very slow than before and it suddenly shut down's automatically can anyone please help me with this

HI @orianpax360
I see that you accidentally switched the processor to 1 in the bios and saved the changes. Now your notebook is very sluggish and will do an auto shutdown.
Would you please try this.
Go back to the bios.
Along the bottom you will see an option to restore defaults. Please select that and save your changes.
If that did not resolve the issue here is a link to Restoring the BIOS that may also help.
You can contact HP support at anytime to assist you with this issue. They can remotely log onto your system to help resolve difficulties.
Please call our technical support at 800 474 6836. If you live outside the US/Canada Region, please click the link below to get a support number for your region.
World Wide Phone Support
Good Luck!
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Looing for PXE-Boot option on T430s

Hello
I am in the process of testing a Thinkpad T430s to possibly do a mass purchase for our company. We use SCCM
to manage imaging, patching / updates etc. I am trying to PXE boot but but I am getting an error which may have to do with
SCCM but as an extra measure I am trying to locate PXE Boot option in the BIOS but can't seem to find anything.
ANy suggestions would be appreciated

do you see Wake On Lan and/or Ethernet LAN Option ROM on the Network menu under the Config tab in your BIOS.
apologies if you don't. all i've got to check is my X220 in front of me, at the moment.
regards.
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество
Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
PM requests for individual support are not answered. If a post solves your issue, please mark it so.
X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
I am not a Lenovo employee.

Partition is there, but Windows boot option is gone?

Hey folks, I'm having a small issue with bootcamp.
Not too long ago did I have Windows running just fine on my Mac; everything was up to date, I managed to install 7 and upgrade to 8.1 just fine. Everything was good until one evening I open my Mac up, there is a command line that states "no bootable device." I don't believe I had installed Yosemite because last time I shut the Mac it was in Windows. I found a thread from another user here, and followed LonerT's suggestions and managed to get Windows back as a boot option, but the command line still pops up with "non-system disk."
The bootcamp partition is still on my HD with everything installed, so if there's some way I could get this back to how it was without having to go through the hassle of erasing the partition and starting anew I would be greatly appreciative.
Thanks!

Whoa, LonerT!?
Certainly, here are the results of the commands:
joshuas-mbp:~ joshua$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                  Apple_HFS Macintosh HD            394.4 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:       Microsoft Basic Data MAC TO PC               5.0 GB     disk0s4
   5:       Microsoft Basic Data BOOTCAMP                100.0 GB   disk0s5
joshuas-mbp:~ joshua$
joshuas-mbp:~ joshua$ diskutil cs list
No CoreStorage logical volume groups found
joshuas-mbp:~ joshua$
joshuas-mbp:~ joshua$ sudo gpt -vv -r show /dev/disk0
Password:
gpt show: /dev/disk0: mediasize=500277790720; sectorsize=512; blocks=977105060
gpt show: /dev/disk0: Suspicious MBR at sector 0
gpt show: /dev/disk0: Pri GPT at sector 1
gpt show: /dev/disk0: Sec GPT at sector 977105059
      start       size index contents
          0          1         MBR
          1          1         Pri GPT header
          2         32         Pri GPT table
         34          6
         40     409600      1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
     409640 770347720      2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC
770757360    1269536      3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
772026896       1520
772028416    9762816      4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
781791232       2048
781793280 195311616      5 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
977104896        131
977105027         32         Sec GPT table
977105059          1         Sec GPT header
joshuas-mbp:~ joshua$
joshuas-mbp:~ joshua$ sudo fdisk /dev/disk0
Disk: /dev/disk0 geometry: 60821/255/63 [977105060 sectors]
Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 770347720] HFS+
3: AB 1023 254 63 - 1023 254 63 [ 770757360 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [ 772028416 -    9762816] HPFS/QNX/AUX
joshuas-mbp:~ joshua$
I thought the corestorage command was a bit odd so I looked around the web to find out what it means. It doesn't sound promising.
As for you question on "what modifications were made to get [the drive] bootable again:"
I followed these instructions you gave in that thread listed above...
Here is an example.
sudo fdisk -e /dev/disk0
Password:
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> p
Disk: /dev/disk0 geometry: 121643/255/63 [1954210120 sectors]
Offset: 0 Signature: 0xAA55
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
1: EE 1023 254 63 - 1023 254 63 [         1 -     409639] <Unknown ID>
2: AF 1023 254 63 - 1023 254 63 [    409640 - 1452530904] HFS+
3: AB 1023 254 63 - 1023 254 63 [1452940544 -    1269536] Darwin Boot
*4: 07 1023 254 63 - 1023 254 63 [1454211072 - 499998720] HPFS/QNX/AUX
fdisk: 1> setpid 4
         Starting       Ending
#: id cyl hd sec - cyl hd sec [     start -       size]
*4: 07 1023 254 63 - 1023 254 63 [1454211072 - 499998720] HPFS/QNX/AUX
Partition id ('0' to disable) [0 - FF]: [7] (? for help)
fdisk: 1> flag 4
Partition 4 marked active.
Saying the Windows is bootable may be a bit subjective; the option appeared after this example you gave, but it won't boot into Windows.

Wrong selection of number of processor in advanced boot option. system became dead slow.

hello sir,
i have acer aspire v3-571g laptop with windows 8.1 x64 based OS. Processor is Intel Core i5.
To get a faster booting, i selected 2 processor instead of 1 in advanced boot option (msconfig) by mistake and now my laptop become dead slow on booting and startup.
I am in a big headache now...
Please help a hand to solve this issue...
Thank you..

Nishaf
Cross posted on Microsoft community. Like I told you there go back into msconfig and select one processor. I dont suspect that either change is responsible for the slowness. Did you do anything else?
Wanikiya and Dyami--Team Zigzag

Disabled Secure BOOT option in G580 Bios options

How do I disable this setting in the Bios? Do I have to turn in off in Windows 8 first?
I have the option but I can not arrow to it and turn it off or on. Only way to disable it is by brute force and turn off UEFI boot option and set it as Legacy.
I am obviously missing something.
Solved!
Go to Solution.

You don't have to disable it ........... Just when you are shutting down the device Press (SHIFT + SHUTDOWN from the power menu) .........
This will do it

[SOLVED]Unknown boot option `radeon.modeset=0'

Similar Messages

Maybe you are looking for