Mac boot loader problem
Hi,
I am having a trouble with my Mac Mini. I tried to setup windows in my mac using Bootcamp. I partitioned my hard-disk using bootcamp and give 50GB space for widnows. when i pressed the install button it just restarted my computer and then a blank screen.
Neither i can login in my Mac not my windows is installing. It just a blank black screen. If i remove the external DVD driver it ask me to connect a installtion disk and press enter. I did hold down the menu/option key after restart my mac but it's not working and for that i can't login in the boot option. I am using A4Tech keyboard with my mac mini.
Please help me, how can I get my OS X back to the previous position.
Thanks!
When you "setup windows in my mac using Bootcamp" did you maybe think that was going to install some version of Windows for you? Because it sounds as if you thought it would, but it doesn't. All it does is give you a dedicated partition on your Mac's hard drive onto which you can install Windows. Please read this:
http://support.apple.com/kb/HT1461
And this:
http://manuals.info.apple.com/en_US/boot_camp_install-setup_10.8.pdf
Similar Messages
-
Boot Loader Problem(rEFIt & GRUB/LILO)
Hi,
I'm planning to "triple boot" my iMac with "Mac SL, Win 7, & openSUSE". But installing the "GRUB/LILO" makes my origanel boot loader rEFIt cannot work directly.
I have to select "Win 7/openSUSE" from the rEFIt, and select "WIn 7/openSUSE" again (from GRUB/LILO).
Any suggestion for fixing the problerm so I can boot straight to the OSes?
Thanks.Boot from the solaris dvd in to singe user mode, mount the system under /a and run the instalgrub command in the shell:
/sbin/installgrub -m /boot/grub/stage1 /boot/grub/stage2 /dev/rdsk/c?d?s? (whatever your drive is).
Maybe make a backup copy of /a/boot/grub/menu.lst, I cant remember if it gets over written that way you can copy it back if necessary. -
Latitude E5440 - Truecrypt Boot Loader Problems
I've been using Truecrypt for many years on Latitude D and E Series laptops and never had a problem until we upgraded to E5440's. Now I continually get Truecrypt boot loader errors.
I've tried versions 7.1 and 7.1a and FDE as well as just encrypting the System Partition. What happens is that when the computer is started up, I get a black screen with a white blinking cursor.
The temporary fix is easy. I boot off the Truecrypt Rescue disk and Repair the Truecrypt Boot Loader. This works for several days and then it happens again.
I am lost as to a solution, but I believe it might involve one of the following:
1. Hybrid Hard Drives. These E5440's have a Samsung 500GB hybrid drive in them. I am wondering if some file or component of Truecrypt is being put on the Flash drive component of the HD and it becomes unavailable at boot up.
2. Closing the lid of the laptop instead of shutting it down for transport.
If you've had similar problems or have any insight into this issue, I would love to get your feedback.
Thanks, Greg
Also, these laptops run W7 Pro.I've been using Truecrypt for many years on Latitude D and E Series laptops and never had a problem until we upgraded to E5440's. Now I continually get Truecrypt boot loader errors.
I've tried versions 7.1 and 7.1a and FDE as well as just encrypting the System Partition. What happens is that when the computer is started up, I get a black screen with a white blinking cursor.
The temporary fix is easy. I boot off the Truecrypt Rescue disk and Repair the Truecrypt Boot Loader. This works for several days and then it happens again.
I am lost as to a solution, but I believe it might involve one of the following:
1. Hybrid Hard Drives. These E5440's have a Samsung 500GB hybrid drive in them. I am wondering if some file or component of Truecrypt is being put on the Flash drive component of the HD and it becomes unavailable at boot up.
2. Closing the lid of the laptop instead of shutting it down for transport.
If you've had similar problems or have any insight into this issue, I would love to get your feedback.
Thanks, Greg
Also, these laptops run W7 Pro. -
CPU heat & win XP boot/load problem
I have been experencing 2 big problems with my new set setup.
First one is high temp are being reported for the CPU. I have stock heatsink installed on the CPU. According to speedfan, idle temps around 40 - 45 C and on load temp goes all the up over 60, around 61-63. MSI core cell (ran it seprately) reports about the same, but the high it had was 65-66C. I had arctic cooling HSF installed but took out since it was giving me high temp around 70C on load, so I took it out. Possibly I couldn't apply the thermal paste (the one that it came with) properly, tried 4 times and seems like the arctic Heatsink isn't working right anymore. did run a Prime95 test for 8 hours and it finished with 0 errors/warning. The system seems stable after it loads up.
Second problem is booting up win xp. Frequently window XP goes go the loading window XP screen and after that it crashes. After a couple crashes it does boot into win XP though. Like mentioned, after win XP is loaded it is stable. Also I have noticed if I restart windows XP after sucessful boot, it reboot without crashing. However, if I even turn of the comp for 5-10 mins and boot up, window XP crashes when it trying load again.
Here are specs that i have right now:
Athlon 64 3400 socket 754 newcastle
MSI Neo Platinum with 1.4 verions BIOS
corsair 512 MB ram
120 GB ATA seagate HD (main)
40 GB ATA WD HD (secondary)
Thermaltake 480w PSU
Any help would be appericiated!Corsair is value ram wiht 2.5 CAS, also don't think that got any problem at all. Like said windows is stable after it loads. Also I think I found the problem with booting, I removed a 2nd old HD that I had in there. Now it is booting properly.
Now about that temp, I decided to check it out myself. I let prime95 run for 40 mins and let go max temp. This time speedfan showed only max of 58C, while core center showed 62C. I touched the bottom of the heatsink and it was midly warm to hot. I also checked with the temperature sensor that is on my thermaltake case. The LCD on case showed only 40-42C. So could the core temp actaully be 20C warmer? Also another thing I keep on seening people with "K8N Neo Platinum bios 1.5B5", is that a better version of the bios and does help with themp reading?? -
Cannot mount Windows partition with boot loader on Mac OS 10.8
I took out my hard drive of my Windows 7 PC, which has 3 partitions on it: C drive which contains the OS and the boot loader that the computer boots into, D drive which contains my data, and a third called "System Reserved" a few megabyte in size that I have no idea what so ever what it does besides that I cannot modify or delete it, which probably means that it is important. Now I put the hard drive inside an USB 3.0 enclosure and I am trying to mount this hard drive onto my OS X Lion Macbook air. Something strange is happening, in that the computer takes about 30 seconds or more to detect the drives presence, and then it just freezes after that. On the initial try, the system actually successfully launched DiskUtility, and I can see the drive mounted in the list of detected drives and 3 partitions "SD1, SD2, SD3" under that drive, but after repeating the procedure a few more times, nothing seems to be happening after the system freeze.
Anyone have any idea what's going on? I am trying to access the data partition for my stuff.
I have Tuxera NTFS installed, and I should probably also mention that my Macbook Air is mid 2011 with only USB 2.0 ports.
Thanks in advance.Ok, I figured out the freezing part; apparently, I had to connect to the USB port on the left side next to the power supply or the disk does not have enough power and causes the system to crash. So, now Disk Utility can see the hard drive with no problem.
But now, the partitions are detected as XFAT format and no volumes are mounted to the desktop. Disk Utility displays the disk description as:
Disk Description : INTEL SS DSA2M160G2GC Media Total Capacity : 160.04 GB (160,041,885,696 Bytes)
Connection Bus : USB Write Status : Read/Write
Connection Type : External S.M.A.R.T. Status : Not Supported
USB Serial Number : CVPO049000W0160AGN Partition Map Scheme : Master Boot Record
Why is the status "not supported"? How should I go about mounting the data volume so I can access the files on my Mac? -
SOMEBODY HELP ME PLEASE.
i have a mac os x 10.4.11
and when i turn it on it goes to a black window and it says
localhost mDSResponder-108.6 : starting
launchd: com. apple.niblindd: exited abnormally : bad system call
launchd: com. apple.niblindd:respawning to quickly ! trottlingHi Mac turning on problems, and a warm welcome to the forums!
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Tiger Install disc that came with your computer, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
*Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
3. Click the First Aid tab.
4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
5. Select your Mac OS X volume.
6. Click Repair. Disk Utility checks and repairs the disk."
http://docs.info.apple.com/article.html?artnum=106214
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
The usual reason why updates fail or mess things up, is if Permissions are not fixed before & after every update, with a reboot... you may get a partial update when the installer finds it doesn't have Permissions to change one obscure little part of the OS, leaving you with a mix of OS versions.
Some people get away without Repairing Permissions for years, some for only days.
If Permissions are wrong before applying an update, you could get mixed OS versions, if Directory is the slightest messed up, who knows!
If many Permission are repaired, or any Directory errors are found, you may need to re-apply some the latest/biggest updates.
May even need to do an Archive and Install if you have room on the HD, but saves all your files and gives a new OS...
http://docs.info.apple.com/article.html?artnum=107120
I only use Software Update to see what is needed, then get them for real via...
http://www.apple.com/support/downloads/
That way I can wait a week or so, check the forums for potential problems, and get Permissions & such in order before installing.
If all the above fails, then it appears to be time for a relatively painless Archive & Install, which gives you a new/old OS, but can preserve all your files, pics, music, settings, etc., as long as you have plenty of free disk space and no Disk corruption, and is relatively quick & painless...
http://docs.info.apple.com/article.html?artnum=107120
Just be sure to select Preserve Users & Settings. -
When my Mac boots, a little bar appears below the apple logo. Then, the bar fills up very slowly. I know the bar isn't the progress of my Mac booting, because after the bar fills up and disappears, the spinning wheel goes on for like another 20 seconds. the Mac actually boots, and there is nothing wrong, but because of the little bar that shows up, my Mac takes 15 minutes to boot, and its a waste of battery and time. Please help me get out of this problem. Thanks!
That means the directory of the boot volume is damaged and a repair is being attempted. If it happens repeatedly, you should assume that there's a hardware fault in the drive, the internal cable, or the logic board. Make a "Genius" appointment at an Apple Store to have the machine tested. Back up all data before you go.
-
Problems unlocking the boot loader of xperia z3
Hello,
i'm trying to unlock the boot loader of my xperia z3, i'm following the instructions on sony's site but i'm stuck: i connect the phone to the pc in fastboot mode (blue light on), then i open the command prompt window in the platform-tools folder of android sdk, but when i type fastboot devices nothing happens. If i try to enter my unlock code i get "waiting for device" forever.
Any help?I recommend that you check that you have installed the fastboot driver. You can download it from here: http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
And as uliwooly says, make sure that you have read the information on http://developer.sonymobile.com/unlockbootloader/ and that you are aware of the risks.
- Official Sony Xperia Support Staff
If you're new to our forums make sure that you have read our Discussion guidelines.
If you want to get in touch with the local support team for your country please visit our contact page. -
[SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.
Hello,
The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
Information
efibootmgr 0.6.0-1
refind-efi 0.6.8-1
Linux 3.8.4-1-ARCH
sudo efibootmgr
BootCurrent: 000A
Timeout: 0 seconds
BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Startup Interrupt Menu
Boot0004 ME Configuration Menu
Boot0005 Rescue and Recovery
Boot0006* USB CD
Boot0007* USB FDD
Boot0008* ATAPI CD0
Boot0009* ATA HDD2
Boot000A* ATA HDD0
Boot000B* ATA HDD1
Boot000C* USB HDD
Boot000D* PCI LAN
Boot000E* ATAPI CD1
Boot000F* ATAPI CD2
Boot0010 Other CD
Boot0011* ATA HDD3
Boot0012* ATA HDD4
Boot0013 Other HDD
Boot0014* IDER BOOT CDROM
Boot0015* IDER BOOT Floppy
Boot0016* ATA HDD
Boot0017* ATAPI CD:
Boot0018* PCI LAN
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
boot refind tools
/boot/EFI/boot:
bootx64.efi icons refind.conf
/boot/EFI/boot/icons:
*** Icons
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
*** icons
/boot/EFI/tools:
drivers shells
/boot/EFI/tools/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/tools/shells:
Shell.efi Shell_Full.efi
cat /boot/refind_linux.conf
"Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
"Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
# 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 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option 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
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#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, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# 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,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# 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
#resolution 3
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
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
scan_driver_dirs /boot/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
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 UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# 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, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/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,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.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. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# 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
default_selection "vmlinuz-linux"
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# 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
cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda1
# UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=5447-7409 /boot vfat noatime 0 2
# /dev/sda3
UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
EDIT2: @swordfish Removed /boot/EFI/arch.
Last edited by donniezazen (2013-04-04 06:37:07)I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that I have in /boot/EFI/tools/Shells.
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
drivers refind tools
/boot/EFI/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
### Icons
/boot/EFI/tools:
Shell.efi
# 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 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option 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
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#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, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# 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,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# 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
#resolution 3
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
showtools shell, 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
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
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 UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# 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, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/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,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.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. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# 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
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# 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
Thanks for suggesting to try older ISO.
UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
Last edited by donniezazen (2013-04-04 06:43:16) -
Switch 2960 IOS boot fixing problem
I have a prolem .when I change the IOS from rommon I try to reload the switc but he stopped and not complet it,s boot as show..
I tried the ios latest and old also, even same problem
Loading "flash:c2960-lanbasek9-mz.122-50.SE5.bin"...@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
File "flash:c2960-lanbasek9-mz.122-50.SE5.bin" uncompressed and installed, entry point: 0x3000
executing...
Switch uptime is 13 seconds
cisco WS-C2960-24PC-L (PowerPC405) processor (revision G0) with 65536K bytes of
memory.
Processor board ID FCQ1521Y4UG
Using driver version 1 for media type 1
Base ethernet MAC Address: 20:37:06:8a:e0:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
Initializing Flash...
mifs[2]: 0 files, 1 directories
mifs[2]: Total bytes : 3870720
mifs[2]: Bytes used : 1024
mifs[2]: Bytes available : 3869696
mifs[2]: mifs fsck took 1 seconds.
mifs[3]: 8 files, 3 directories
mifs[3]: Total bytes : 27998208
mifs[3]: Bytes used : 9243136
mifs[3]: Bytes available : 18755072
mifs[3]: mifs fsck took 5 seconds.
...done Initializing Flash.
done.
Loading "c2960-lanbasek9-mz.150-2.SE2.bin"...c2960-lanbasek9-mz.150-2.SE2.bin: n
o such device
Error loading "c2960-lanbasek9-mz.150-2.SE2.bin"
Interrupt within 5 seconds to abort boot process.
Loading "flash:/c2960-lanbasek9-mz.122-50.SE4.bin"...@@@@@@@@@@@@@@@@@@@@@@@@@@@
File "flash:/c2960-lanbasek9-mz.122-50.SE4.bin" uncompressed and installed, entr
y point: 0x3000
executing...
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE4, REL
EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 26-Mar-10 09:14 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01400000
Initializing flashfs...
Using driver version 1 for media type 1
ifs[3]: 0 files, 1 directories
mifs[3]: Total bytes : 3870720
mifs[3]: Bytes used : 1024
mifs[3]: Bytes available : 3869696
mifs[3]: mifs fsck took 0 seconds.
mifs[3]: Initialization complete.
mifs[4]: 8 files, 3 directories
mifs[4]: Total bytes : 27998208
mifs[4]: Bytes used : 9243136
mifs[4]: Bytes available : 18755072
mifs[4]: mifs fsck took 0 seconds.
mifs[4]: Initialization complete.
...done Initializing flashfs.
Checking for Bootloader upgrade.. not needed
POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed
POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed
POST: CPU MIC interface Loopback Tests : Begin
POST: CPU MIC interface Loopback Tests : End, Status Passed
POST: PortASIC RingLoopback Tests : Begin
00:00:08 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 200, PC = 8A26E0
-Traceback= 8A26E0 651700 64A3F8 64B458 64C008 64C4C8 4F32E8 101C2A0 101C338 BCA
4C8 BCA734 1098AE4 108F5B4
Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_5
=== Flushing messages (00:00:11 UTC Mon Mar 1 1993) ===
Buffered messages:
Queued messages:
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE4, REL
EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 26-Mar-10 09:14 by prod_rel_team
Machine Check Exception (0x0200)!
ESR: 0x00000000, BESRA: 0x00000000, BESRB: 0x00000000, BEAR: 0x00000000
CPU Register Context:
Vector = 0x00000200 PC = 0x008A26E0 MSR = 0x00029230 CR = 0x39033033
LR = 0x00651700 CTR = 0x006516F0 XER = 0xC0000010
R0 = 0x00651700 R1 = 0x01FAFDA8 R2 = 0x00000000 R3 = 0x00000000
R4 = 0x7C0000A4 R5 = 0x00000000 R6 = 0x00000000 R7 = 0x00000000
R8 = 0xFFFFFFFF R9 = 0x01D40000 R10 = 0x7C0000A4 R11 = 0x01472004
R12 = 0xE59C0800 R13 = 0x00110000 R14 = 0x01FAFDF8 R15 = 0x00000001
R16 = 0x01FAFDFA R17 = 0x01FAFDF8 R18 = 0x00000001 R19 = 0x00650000
R20 = 0x0144DED8 R21 = 0x00000000 R22 = 0x00000578 R23 = 0x00000001
R24 = 0x019F0000 R25 = 0x00000000 R26 = 0x00000000 R27 = 0x00000000
R28 = 0x00000000 R29 = 0x00000000 R30 = 0x0000000F R31 = 0x00000001
Stack trace:
PC = 0x008A26E0, SP = 0x01FAFDA8
Frame 00: SP = 0x01FAFDB0 PC = 0x008A26D4
Frame 01: SP = 0x01FAFDB8 PC = 0x00651700
Frame 02: SP = 0x01FAFDD0 PC = 0x0064A3F8
Frame 03: SP = 0x01FAFDF0 PC = 0x0064B458
Frame 04: SP = 0x01FAFE90 PC = 0x0064C008
Frame 05: SP = 0x01FAFEC0 PC = 0x0064C4C8
Frame 06: SP = 0x01FAFEE0 PC = 0x004F32E8
Frame 07: SP = 0x01FAFEE8 PC = 0x0101C2A0
Frame 08: SP = 0x01FAFF00 PC = 0x0101C338
Frame 09: SP = 0x01FAFF20 PC = 0x00BCA4C8
Frame 10: SP = 0x01FB0028 PC = 0x00BCA734
Frame 11: SP = 0x01FB0030 PC = 0x01098AE4
Frame 12: SP = 0x00000000 PC = 0x0108F5B4
Switch uptime is 13 seconds
cisco WS-C2960-24PC-L (PowerPC405) processor (revision G0) with 65536K bytes of
memory.
Processor board ID FCQ1521Y4UG
Using driver version 1 for media type 1
Base ethernet MAC Address: 20:37:06:8a:e0:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
Initializing Flash...
mifs[2]: 0 files, 1 directories
mifs[2]: Total bytes : 3870720
mifs[2]: Bytes used : 1024
mifs[2]: Bytes available : 3869696
mifs[2]: mifs fsck took 0 seconds.
mifs[3]: 10 files, 3 directories
mifs[3]: Total bytes : 27998208
mifs[3]: Bytes used : 9521664
mifs[3]: Bytes available : 18476544
mifs[3]: mifs fsck took 5 seconds.
...done Initializing Flash.
done.
Loading "c2960-lanbasek9-mz.150-2.SE2.bin"...c2960-lanbasek9-mz.150-2.SE2.bin: n
o such device
Error loading "c2960-lanbasek9-mz.150-2.SE2.bin"
Interrupt within 5 seconds to abort boot process.
Loading "flash:/c2960-lanbasek9-mz.122-50.SE4.bin"...@@@@@@@@@@@@@@@@@@@@@@@@@@@
File "flash:/c2960-lanbasek9-mz.122-50.SE4.bin" uncompressed and installed, entr
y point: 0x3000
executing...
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE4, REL
EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 26-Mar-10 09:14 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01400000
Initializing flashfs...
Using driver version 1 for media type 1
ifs[3]: 0 files, 1 directories
mifs[3]: Total bytes : 3870720
mifs[3]: Bytes used : 1024
mifs[3]: Bytes available : 3869696
mifs[3]: mifs fsck took 0 seconds.
mifs[3]: Initialization complete.
mifs[4]: 10 files, 3 directories
mifs[4]: Total bytes : 27998208
mifs[4]: Bytes used : 9521664
mifs[4]: Bytes available : 18476544
mifs[4]: mifs fsck took 0 seconds.
mifs[4]: Initialization complete.
...done Initializing flashfs.
Checking for Bootloader upgrade.. not needed
POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed
POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed
POST: CPU MIC interface Loopback Tests : Begin
POST: CPU MIC interface Loopback Tests : End, Status Passed
POST: PortASIC RingLoopback Tests : Begin
00:00:08 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 200, PC = 8A26E0
-Traceback= 8A26E0 651700 64A3F8 64B458 64C008 64C4C8 4F32E8 101C2A0 101C338 BCA
4C8 BCA734 1098AE4 108F5B4
Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_6
=== Flushing messages (00:00:11 UTC Mon Mar 1 1993) ===
Buffered messages:
Queued messages:
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE4, REL
EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 26-Mar-10 09:14 by prod_rel_team
Machine Check Exception (0x0200)!
ESR: 0x00000000, BESRA: 0x00000000, BESRB: 0x00000000, BEAR: 0x00000000
CPU Register Context:
Vector = 0x00000200 PC = 0x008A26E0 MSR = 0x00029230 CR = 0x39033033
LR = 0x00651700 CTR = 0x006516F0 XER = 0xC0000010
R0 = 0x00651700 R1 = 0x01FAFDA8 R2 = 0x00000000 R3 = 0x00000000
R4 = 0x7C0000A4 R5 = 0x00000000 R6 = 0x00000000 R7 = 0x00000000
R8 = 0xFFFFFFFF R9 = 0x01D40000 R10 = 0x7C0000A4 R11 = 0x01472004
R12 = 0xE59C0800 R13 = 0x00110000 R14 = 0x01FAFDF8 R15 = 0x00000001
R16 = 0x01FAFDFA R17 = 0x01FAFDF8 R18 = 0x00000001 R19 = 0x00650000
R20 = 0x0144DED8 R21 = 0x00000000 R22 = 0x00000578 R23 = 0x00000001
R24 = 0x019F0000 R25 = 0x00000000 R26 = 0x00000000 R27 = 0x00000000
R28 = 0x00000000 R29 = 0x00000000 R30 = 0x0000000F R31 = 0x00000001
Stack trace:
PC = 0x008A26E0, SP = 0x01FAFDA8
Frame 00: SP = 0x01FAFDB0 PC = 0x008A26D4
Frame 01: SP = 0x01FAFDB8 PC = 0x00651700
Frame 02: SP = 0x01FAFDD0 PC = 0x0064A3F8
Frame 03: SP = 0x01FAFDF0 PC = 0x0064B458
Frame 04: SP = 0x01FAFE90 PC = 0x0064C008
Frame 05: SP = 0x01FAFEC0 PC = 0x0064C4C8
Frame 06: SP = 0x01FAFEE0 PC = 0x004F32E8
Frame 07: SP = 0x01FAFEE8 PC = 0x0101C2A0
Frame 08: SP = 0x01FAFF00 PC = 0x0101C338
Frame 09: SP = 0x01FAFF20 PC = 0x00BCA4C8
Frame 10: SP = 0x01FB0028 PC = 0x00BCA734
Frame 11: SP = 0x01FB0030 PC = 0x01098AE4
Frame 12: SP = 0x00000000 PC = 0x0108F5B4
Switch uptime is 13 seconds
cisco WS-C2960-24PC-L (PowerPC405) processor (revision G0) with 65536K bytes of
memory.
Processor board ID FCQ1521Y4UG
Using driver version 1 for media type 1
Base ethernet MAC Address: 20:37:06:8a:e0:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
Initializing Flash...
mifs[2]: 0 files, 1 directories
mifs[2]: Total bytes : 3870720
mifs[2]: Bytes used : 1024
mifs[2]: Bytes available : 3869696
mifs[2]: mifs fsck took 0 seconds.
mifs[3]: 12 files, 3 directories
mifs[3]: Total bytes : 27998208
mifs[3]: Bytes used : 9800192
mifs[3]: Bytes available : 18198016
mifs[3]: mifs fsck took 5 seconds.
...done Initializing Flash.
done.
Loading "c2960-lanbasek9-mz.150-2.SE2.bin"...c2960-lanbasek9-mz.150-2.SE2.bin: n
o such device
Error loading "c2960-lanbasek9-mz.150-2.SE2.bin"
Interrupt within 5 seconds to abort boot process.
Loading "flash:/c2960-lanbasek9-mz.122-50.SE4.bin"...@@@@@@@@@@@@@@@@@@@@@@@@@@@
File "flash:/c2960-lanbasek9-mz.122-50.SE4.bin" uncompressed and installed, entr
y point: 0x3000
executing...
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE4, REL
EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 26-Mar-10 09:14 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01400000
Initializing flashfs...
Using driver version 1 for media type 1
ifs[3]: 0 files, 1 directories
mifs[3]: Total bytes : 3870720
mifs[3]: Bytes used : 1024
mifs[3]: Bytes available : 3869696
mifs[3]: mifs fsck took 0 seconds.
mifs[3]: Initialization complete.
mifs[4]: 12 files, 3 directories
mifs[4]: Total bytes : 27998208
mifs[4]: Bytes used : 9800192
mifs[4]: Bytes available : 18198016
mifs[4]: mifs fsck took 0 seconds.
mifs[4]: Initialization complete.
...done Initializing flashfs.
Checking for Bootloader upgrade.. not needed
POST: CPU MIC register Tests : Begin
POST: CPU MIC register Tests : End, Status Passed
POST: PortASIC Memory Tests : Begin
POST: PortASIC Memory Tests : End, Status Passed
POST: CPU MIC interface Loopback Tests : Begin
00:00:07 UTC Mon Mar 1 1993: Unexpected exception to CPUvector 1000, PC = 6DCA7
0
-Traceback= 6DCA70
Writing crashinfo to flash:/crashinfo_ext/crashinfo_ext_7
=== Flushing messages (00:00:09 UTC Mon Mar 1 1993) ===
Buffered messages:
Queued messages:
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 12.2(50)SE4, REL
EASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Fri 26-Mar-10 09:14 by prod_rel_team
Programmable Interval Timer Exception (0x1000)!
SRR0 = 0x006DCA70 SRR1 = 0x00029230 SRR2 = 0x006533DC SRR3 = 0x00021200
ESR = 0x00000000 DEAR = 0x00000000 TSR = 0x8C000000 DBSR = 0x00000000
CPU Register Context:
Vector = 0x00001000 PC = 0x006DCA70 MSR = 0x00029230 CR = 0x39000033
LR = 0x0064B04C CTR = 0x0022E52C XER = 0xE0000010
R0 = 0x0064B04C R1 = 0x01FAFE58 R2 = 0x00000000 R3 = 0x0000002F
R4 = 0x01FC1E3C R5 = 0x00000000 R6 = 0x000001ED R7 = 0x00000000
R8 = 0x00000000 R9 = 0x019F0000 R10 = 0x00029230 R11 = 0x01D40000
R12 = 0x39000033 R13 = 0x00110000 R14 = 0x00BCA6D4 R15 = 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000
R20 = 0x00000000 R21 = 0x00000000 R22 = 0x00000000 R23 = 0x00000000
R24 = 0x00000000 R25 = 0x00000000 R26 = 0x00000578 R27 = 0x00000000
R28 = 0x01D40000 R29 = 0x00000000 R30 = 0x01FAFEC8 R31 = 0x00000001
Stack trace:
PC = 0x006DCA70, SP = 0x01FAFE58
Frame 00: SP = 0x01FAFE80 PC = 0x01CA11B4
Frame 01: SP = 0x01FAFEB0 PC = 0x01DAC898
Frame 02: SP = 0x01FAFEC0 PC = 0x0064C29C
Frame 03: SP = 0x01FAFEE0 PC = 0x004F32A4
Frame 04: SP = 0x01FAFEE8 PC = 0x0101C2A0
Frame 05: SP = 0x01FAFF00 PC = 0x0101C338
Frame 06: SP = 0x01FAFF20 PC = 0x00BCA4C8
Frame 07: SP = 0x01FB0028 PC = 0x00BCA734
Frame 08: SP = 0x01FB0030 PC = 0x01098AE4
Frame 09: SP = 0x00000000 PC = 0x0108F5B4
Switch uptime is 12 seconds
cisco WS-C2960-24PC-L (PowerPC405) processor (revision G0) with 65536K bytes of
memory.
Processor board ID FCQ1521Y4UG
Using driver version 1 for media type 1
Base ethernet MAC Address: 20:37:06:8a:e0:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
Initializing Flash...
mifs[2]: 0 files, 1 directories
mifs[2]: Total bytes : 3870720
mifs[2]: Bytes used : 1024
mifs[2]: Bytes available : 3869696
mifs[2]: mifs fsck took 0 seconds.
mifs[3]: 14 files, 3 directories
mifs[3]: Total bytes : 27998208
mifs[3]: Bytes used : 10084864
mifs[3]: Bytes available : 17913344
mifs[3]: mifs fsck took 5 seconds.
...done Initializing Flash.
done.
Loading "c2960-lanbasek9-mz.150-2.SE2.bin"...c2960-lanbasek9-mz.150-2.SE2.bin: n
o such device
Error loading "c2960-lanbasek9-mz.150-2.SE2.bin"
Interrupt within 5 seconds to abort boot process.
Loading "flash:/c2960-lanbasek9-mz.122-50.SE4.bin"...@@@@@@@@@@@@@@@@@@@@@@@@@@@
Thanks & Regards,
Srinivas. N.To solve this problem, please follow instruction carefully as follows:
1. go to cisco download website: http://software.cisco.com/download/release.html?mdfid=281231709&catid=268438038&rellifecycle=ED&release=12.2.50-SE5&softwareid=280805680&sortparam=
2. Copy the error loading message "c2960-lanbasek9-mz.150-2.SE2.bin" (without quotes). Paste it in the "search tab"
left side middle-corner then click the search zoom icon.
3. Locate your "c2960-lanbasek9-mz.150-2.SE2.bin" file. see below
All Releases
15.0
15.0SE
15.0.2-SE6(ED)
15.0.2-SE5(ED)
15.0.2-SE4(ED)
15.0.2-SE2(ED) <--click it
4. Download the the file
LAN BASE
c2960-lanbasek9-mz.122-55.SE9.bin <-- download this one.
Now you can proceed to the next step.
5. User HyperTerminal in sending files via xmodem
Step 1. Boot your switch into switch ROM mode. This typically involves holding down the STAT button on the front of the switch when plugging in the power.
Once you’ve booted your switch into Switch ROM mode you’ll be see the following dispatch;
Boot Sector Filesystem (bs) installed, fsid: 2
Base ethernet MAC Address: 00:00:00:00:00:00
Xmodem file system is available.
The password-recovery mechanism is enabled.
The system has been interrupted prior to initializing the
flash filesystem. The following commands will initialize
the flash filesystem, and finish loading the operating
system software:
flash_init
boot
switch:
Step 2. Once you’ve booted into Switch ROM mode you’ll need to initialize the flash file system by executing the flash_init command as shown below;
switch: flash_init
Initializing Flash...
flashfs[0]: 1 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 21592931
flashfs[0]: Bytes used: 19474880
flashfs[0]: Bytes available: 4224091
flashfs[0]: flashfs fsck took 8 seconds.
...done Initializing Flash.
switch:
Step 3 – OPTIONAL – If your image is corrupted you can format your flash file system by executing the format flash: command as shown below however this will delete your start-up configuration!!!
Switch: format flash:
Are you sure you want to format "flash:" (all data will be lost) (y/n)?y
flashfs[0]: 0 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 8440441
flashfs[0]: Bytes used: 2024
flashfs[0]: Bytes available: 8540274
flashfs[0]: flashfs fsck took 9 seconds.
Filesystem "flash:" formatted
Switch:
Step 4. To speed up the xModem file transfer speed you’ll need to set the console line BAUD rate to 115200 by executing the set BAUD 115200. If you do this you’ll need to disconnect your console session and change the serial line speed from 9600 to 115200. However if you do not set the BAUD to 115200 your file transfer can take up to 3 hours.
switch: set BAUD 115200
Step 5. Once setting the BAUD rate and reconnecting to the console line of your Cisco switch you’re ready to copy the IOS image via xmodem to the switch’s flash memory by executing the copy xmodem: flash:filename.bin and Then go to Hyper Terminal's menu bar, select Terminal, then send the file.
Select the file c2960-lanbasek9-mz.150-2.SE2.bin to send and select Xmodem as the protocol.
switch: copy xmodem: flash:c2960-lanbasek9-mz.150-2.SE2.bin
Begin the Xmodem or Xmodem-1K transfer now...
CCC
Starting xmodem transfer. Press Ctrl+C to cancel.
Transferring c2960-lanbasek9-mz.150-2.SE2.bin...
100% 12181 KB 6 KB/s 00:31:56 0 Errors
File "xmodem:" successfully copied to "flash:c2960-lanbasek9-mz.150-2.SE2.bin"
switch:
Step 6. Once the IOS image is copied into flash you’ll need to update the BOOT parameter by executing the set BOOT flash:filename.bin command as shown below;
switch: set BOOT flash:c2960-lanbasek9-mz.150-2.SE2.bin
Step 7. Once the boot parameter has been set you can now set the BAUD rate back to the default 9600bps by executing the command unset BAUD. Note that when doing this you’ll need to disconnect your current console connection and change the baud speed on your terminal emulator from 115200 back to 9600.
switch: unset BAUD
Step 8 is the last step which is to boot the switch and verify that the switch successfully boots the IOS image placed into flash from xMODEM. Execute the Boot command to load the IOS image specified in the boot parameter as shown below;
switch: boot
Loading "flash:/c2960-lanbasek9-mz.150-2.SE2.bin"...@@@@@@@@@@@@@@@@@@
WAIT UNTIL YOU SEE THE LAST MESSAGE
Press RETURN to get started!
CONGRATULATION!
DONE! -
Windows 8.1 Installation On Mac - Got a Problem
Windows 8.1 Installation On Mac - Got a Problem
Hi everyone,
I'v researched a lot about installing Win on Mac but I still got a problem when everything seems to be fine.
I got a Macbook Pro Retina, Late 2013 with OSX Mavericks and Bootcamp 5 installed on. And for installing windows, I already got an empty 8GB USB Drive formatted as MS-DOS (FAT32). And I've prepared Windows 8.1 ISO in my Downloads folder.
During my last effort, I opened Bootcamp Assist and then Chose the options: "Create Windows 7 or later version installation disk" and "Download the latest windows support software from Apple". Then I chose my Windows 8.1 ISO location and my destination. When it finished ,I was expecting it to run windows setup. But it closed and nothing happened
When I opened BootCamp again, only the first two options were available as before and "Install or remove Windows 7 or later" wasn't.
Now ,what do I have to do exactly? (NOTE: I'm not a professional. So please answer in a simple way. )
Should I restart the Mac and Hold OPTION while booting to run Windows setup? I was thinking about it but I thought I might screw it up all. So I decided to ask it here to be sure.
Any help will be appreciated by heart!Hi Alcatrax,
I would recommend following the steps in this link in order to help you complete your installation of Boot Camp:
Boot Camp Help: Install Windows on your Mac
https://help.apple.com/bootcamp/mac/5.0/help/#apdecf0e4b6-b472-438d-881e-57c230b 1c250
Prepare your Mac for Windows
Boot Camp Assistant helps prepare your Mac for Windows by creating a new partition for Windows and then starting the Windows installer. Optionally, you can install Windows using an external USB drive that contains a Windows ISO image downloaded from Microsoft and Windows support software.
Important: If you’re using a portable computer, connect the power adapter before continuing.
Insert an external drive into the USB port on your Mac and keep it inserted while you install Windows and Windows support software.
Open Boot Camp Assistant, located in the Other folder in Launchpad.
Select the option to install Windows, select other options you need, then click Continue.
Here are the other options you can choose:
If you want to install Windows from an external USB drive and you have a Windows ISO image, select the option to copy the image to an external USB drive. If this option isn’t available, your Mac doesn’t support installing Windows from an external USB drive.
If you haven’t already downloaded the Windows support software for your Mac, select the option to download it. In a later step, you’ll install the Windows support software on your Windows partition.
Follow the onscreen instructions for the options you selected.
When you’re asked to create a Windows partition, specify a partition size. If you have multiple hard drives in your computer, you can select a different hard drive and create a single partition on that drive, so that the drive is solely used for Windows.
Note: You can’t resize the partition later.
If you need help determining the best size for your Windows partition, refer to your Windows installer documentation. For Windows 8, create a partition that is at least 30 GB.
In a later step, you’ll format the Windows partition.
If you are using an installation disc for the 64-bit version of Windows, insert it into the optical drive in your Mac or the external optical drive. Otherwise, keep the external USB drive with the 64-bit version of Windows inserted.
Click Install.
Boot Camp Assistant creates the Windows partition, restarts your Mac, then opens the Windows installer.
Thanks for being a part of the Apple Support Communities!
Regards,
Braden -
Can I download music from my PC onto my new iPhone and still have my iPhone sync with my Mac without a problem?
I've had an iPod over a year and have not done much with it except download music onto it from my PC. Just recently have purchased the iPhone. When I got my iPod I didn't have a Mac, but now I do. I am really into my iPhone, so now I want to make sure that I don't do anything wrong. So can I connect my iPhone to both my PC and my Mac without it getting mixed signals and stop working. I have no music on my Mac but plan to download music into iTunes on it. So can I download music from both computers without problems onto my iPhone?StoneMountainGirl,
No. You can only music to your iPhone from one computer at a time. If you try to load music onto it from a 2nd computer, it will erase the current content on the iPhone and replace it with whats in the iTunes library you are connected to,
B-rock -
Beige G3 boot from **** problem; open firmware issues; bad motherboard?
Dear all,
I'm having huge boot/startup problems with my beige G3 that had been happily running OSX 10.3.9, but for purposes of this discussion we can (mostly) revert to OS 9. Originally, the machine was a G3 @300; was upgraded more than a year ago to a ZIF G4 @500.
To make a long story short, it won't boot from any hard drives, will not boot from any OS X CD, and will only occasionally boot from a 9.x startup CD (whether Apple or Norton Utilities). I think it's an open firmware issue, possibly caused by a bad motherboard (rev. 2).
All this started happening after I used techtool pro, but I think that's coincidence (even though I acknowledge that, for cops and computer users, there are no coincidences.) Also, as discussed below, I'm having the same problems with an HD that wasn't even in the computer when all these things began.
Here are some of the things I've done.
--repeatedly reset PRAM, both with key combinations and removing battery. The only time it will boot from a 9.x CD is after resetting PRAM.
--removed all add-on PCI cards.
--removed additional VRAM
--removed all memory cards and tried replacing one at a time.
--disconnected both existing hard drives and replaced with an older OS 9.x hard drive (approx 60 mb) that I'd used before. Also tried different ribbon cables.
--unplugged floppy drive
--disconnected PCI ATA disk controller that I'd been using for running a large (1.8 gb) hard drive.
--regarding open firmware: readenv usually shows totally normal default AND installed settings. Using reset-all works fine -- at least it makes the machine reboot, but doesn't solve the problem. reset-nvram does NOT work -- says it's an "unknown word."
--using startup keys like holding down the option key, or shift key, or X key or cmd-option plus two others I can't remember, has no effect. Again, after I've tried any kind of reboot, the ONLY way to get the C-key at startup to boot the CD is by resetting the pram (key combination). Otherwise, the usual result of these experiments is a dark screen on startup -- nothing at all (and the LCD monitor tells me "no input.")
--regarding OSX: sometimes (and I emphasize sometimes) I can get the machine to start booting from an OSX 10.2 CD, but it won't complete the process. Sometimes I get a "prohibited" (as in no-parking, no-smoking) icon; sometimes it will start booting (grey screen, OS X Apple icon), then crash (horizontal grey and white jagged bars); sometimes it will show the OS 9 start icon (the tiny smiling Mac SE), but not boot at all.
--when I get the mac successfully booted with an OS 9.x CD (again, this works sometimes, but not always), the old hard drive with two partitions does show on the desktop and can be accessed. Using either disk repair or Norton Utilities shows the 9.2 system partition on the hard drive to be fine. But if I go to the startup disk control panel, confidently set the 9.2 partition as my startup disk, then reboot, there's no change. It won't boot and I'm back at square one.
--even when I do get successfully booted with 9.x, the machine will still occasionally crash for no reason -- ie when I'm moving a Window.
--the only thing I haven't done is slowed down the processor. It's a ZIF G4 bought more than a year ago from XLR8 your Mac. I'm running at the default 500 mhz, and it's never given me any trouble.
So I think it's a bad motherboard or ROM. Thoughts?
Thanks.The beige Mac is now operating happily again. My original tentative diagnosis remains the same (although still tentative): corrupted PRAM from bad battery, compounded by bad cables that wrote corrupted data to hard drives, and also (possibly) allowing Tech Tool Pro (a utility that I now regard with deep suspicion) to create a "virtual" startup partition.
A few things I've learned along the way that hopefully may be useful:
--remember that the Ex Post Facto utility can be used to help OS X startup, not just installation. This applies to hard drives, emergency CDs, installation CDs, etc. If you can boot into any working hard drive partition (OS 9 or a backup OS 10), then run Ex Post Facto (same program runs on either OS 9 or X -- don't ask me how) and tell it what system you want to start up from. Also, the utility has sometimes told me that the startup extensions on the disc that I wanted to boot up from were bad, and offered to fix them (which works).
--at least on my Mac (beige, v. 2 motherboard), resetting the CUDA button, resetting the PRAM, resetting Open Firmware and "draining" the memory by unplugging the computer and disconnecting the battery for several hours ALL DO DIFFERENT THINGS.
Specifically, if I'm having trouble booting (from a hard drive or a CD), the FIRST thing I do is restart and resetting the PRAM on the fly -- holding down command, option, P and R at startup, and waiting for the chimes (preferably at least 3-4 times).
If I do that and DON'T hear the chimes, that's my cue for my SECOND action -- restarting into open firmware (command, option O and F keys on startup). That should bring up the black text on white background open firmware screen. View other posts or apple support for details, but if you do PRINTENV and see a bunch of weird gibberish after the default/installed lists, you know that it was messed up and you need to clear it through reset nvram and reset all commands. Be aware some of these commands do or do not work depending upon what version of Open Firmware you have.
After I've rebooted with Open Firmware, then on restart I should be able to reset the PRAM on the fly. If that works, then either let the machine run and see what happens, or hold down the C command and see if it will boot from the CD
Usually, if I've fixed everything as above, the machine will boot into whatever version of OS 9 it finds on a hard drive. That's fine with me -- at that point, use Ex Post Facto to reboot into your OS X. (Before I forget: I used the shareware startup CD creator program BootCD to make an emergency boot CD based on OS 10.2.8 (which theoretically will support a beige mac in native fashion) and Disk Warrior, the god of disk repair utilities. Even though the CD should boot just by holding down the C key on startup, it doesn't -- but if I use Ex Post Facto to boot it, no problems (although the process is very slow -- be patient). Then I can fix almost anything using Disk Warrior.)
If none of the above works, then I'll try resetting the CUDA (on my beige minitower, it's a very small black button inconveniently located between a PCI slot and the side of the computer housing). Hold it down for 15 seconds. That should REALLY clear the PRAM. I know this does something different from the previous steps because this is the only action (except the battery disconnect -- next) that clears the date and time from the memory.
If all else fails, I will unplug the computer and disconnect the battery, then push the CUDA button for 15 seconds and let the machine sit overnight.
One final finding -- I thought I'd fixed everything, but both my hard drives suddenly quit working, I discovered that during all this repeated connect/disconnect of things, one of the male pins inside one of the connectors on my Acard ATA PCI card had broken off. Not good. Fortunately, the card had a second connector, which works fine. And I did some extensive shaking of the computer to make sure (I hope) that the broken pin hadn't landed on a circuit board.
All this took more than two weeks, and the advice of this board was much appreciated. Now I'm on to my next adventure -- trying to figure out why a combo Firewire/USB PCI card won't mount an external drive on Firewire, but will on USB. I've tried two cards with same result -- but a Firewire-only card works just fine.)
Regards to all,
Graham -
Bootcamp not showing up in boot loader
Today I needed to resize my Windows Vista Ultimate partition for work, so I used Disk Utility to crate an image from the partition. After that I used Boot Camp Assistant to remove the partition, and then create a larger partition. After this was done I went back into Disk Utility and restored the partition using the image I created earlier.
In OS X I can mount the partition and access the files and it seems everything was restored correctly. When I restart my machine and hold down the Option key to bring up the boot loader, Bootcamp is no longer an option. The only partition I can boot from is HD.
Please help! ThanksDid you actually Install a version of Windows into that Boot Camp Partition? It doesn't sound like you did.
You'll need a copy of Windows 7 or 8, 64bit, and a valid license key code for whatever version you plan on installing.
Ethan_Fidler wrote:
I have sucessfully partitioned my macbook pro (thanks Ds Store!) and now I have another problem, When booting up I hold down option to choose my startup disc all that shows up is macintosh HD and recovery, BOOTCAMP is not showing up, even though it showes up in devices please help me!!
- Ethan -
Strange System Font in Dreamweaver. After I installed Dreamweaver CS4 on my Mac, it loaded this strange font as seen in the photo attached. Anyone know how to fix this? I have uninstalled/reinstalled many times to no avail. There are no other problems with w/ other CS4 programs, they all have the normal system font. I can't figure it out. Thanks!
Funny fonts issue in PI etc.,
http://kb2.adobe.com/cps/405/kb405153.html
Fonts in Dreamweaver panels display incorrectly
http://kb2.adobe.com/cps/138/tn_13862.html
Nadia
Adobe Community Expert : Dreamweaver
Unique CSS Templates | Tutorials | SEO Articles
http://www.DreamweaverResources.com
Web Design & Development
http://www.perrelink.com.au
http://twitter.com/nadiap
Maybe you are looking for
-
My computer died when I was syncing music from iTunes onto my iPad. I can reset it and get it running, but I want to get back my photos and videos. How do I get back photos and videos in recovery mode?
-
Newbie problem please help ...
Hi, how do i get start javascript like run(1);document.form.city.focus(); in Actionscript3 when i click to the button. Thanks in advance for every advice.
-
HT204370 download issues Hd movie on ipad 1
Recently downloaded a HD movie on an ipad 1 and cannot watch it
-
Hi. Whenever I am using safari and clicking to a new page it opens up with a warning saying system may have found unauthorized access on your computer and malicious viruses Rootkit.spyware and Trojan.malware. also I get a warning from http://shopatkm
-
HttpSession Bug in WebLogic 6.0?
I've been having trouble getting sessions restored by jsps in my web applications under WebLogic 6.0. In order to shed some light on the issue, I tried deploying the jsp examples in the examples server. When I run