[Z77A-GD65] How to edit UEFI boot entries?
Hi everyone, just received a Z77A-GD65 as a replacement for a failed Asus P67 board (glad to have got rid!). Working really great as a straight swap, except it hasn't recognised one of my EFI boot devices.
I can boot it from the EFI shell by typing the path of the .EFI file, but I cannot get it to show up as an option in the boot settings (the only UEFI boot entires are the EFI Shell and 'Windows Boot Manager').
I've tried using bcdedit to create another entry, but I can't seem to get it working. Please could someone give me a hand? Thanks in advance
Exactly what is the device?
Similar Messages
-
Z77a-gd65 sound interference using uefi
Good Morning all,
I have today installed windows 8 on my z77a-gd65 board using windows 8 fast boot uefi features in the bios. Everything is great apart from one thing - I have terrible interference on my speakers plugged in to the green port on the back of the motherboard.
I have reinstalled windows 8 without using windows 8 fast boot uefi and the problem dissapears.
I have tried to use spread spectrum and this does not help.
This sound interference is when using the mouse also and when scrolling.
Setup -
z77a-gd65 bios 10.8
intel celeron g540
onboard graphics
samsung ssd 840 120gb
8gb ddr3Did you have this issue with a previous windows installation?
Have you tried uninstalling the drivers while in safe mode then re-installing the most recent from here:
http://www.msi.com/product/mb/Z77A-GD65.html#/?div=Driver&os=Win8%2064 -
How can I edit a calendar entry? I get a message saying it is read only.
Editing an event will only work in a calendar that is created on the iPad or synced directly to the device.
-
Z77A-GD65 + MSI GTX 780Ti = No Boot!
Hello all,
I have a Z77A-GD65 Motherboard, and I've just got my new MSI GTX 780Ti last night.
However when I install the graphics card, the PC won't boot properly. - all I can see is a line ( _ ) at the top left of the screen, and "B2" on the bottom right.
The PC beeps about 3 times if I just leave it, and after the 3rd beep the screen refreshes and the line ( _ ) starts blinking. but that's it.
No boot, no post, nothing.
I have an 850watt powersupply, and I have been running 2x 660s up till now, so i'm sure that it's not a power problem.
Also, I have tested the 780Ti in my friend's PC (G1.Sniper 3) and it works perfectly fine.
Does anyone know what might be wrong?
Thanks,Quote from: jimseeKOR on 21-November-13, 12:20:03
I'm using the same motherboard and just bought GTX780ti last week. I encountered the same issue when i plugged in my new GTX780 ti. I got the B2 error code. So i decided to flash and update my Bios version and IT WORKED !!
To the people having the same issue as i am.,please update your BIOS to the latest one. Make sure the PCI Gen 3 is enabled in the BIOS for full perfomance.
For the BIOS update i need the monitor, and with code 62, you dont get any signal.. -
How to edit one particular entry in custom database table
Hi all,
I want edit one particular entry in custom database table with or without a program.
1. I tried using SE16N and &SAP_EDIT but im unable to get entries to edit.
2. I tried using '/h' and 'code = edit' but it is prompting me to delete an entry but not edit.
3. I tried using modify statement. But in vain.
I tried this statements through programatically,
MODIFY itab FROM wa_itab TRANSPORTING zabc.
MODIFY zsample_02 FROM itab.
please suggest with out writing a program, if possible.Hi ,
Try with FM SE16N_INTERFACE.
1 .Go to SE37
2. Enter FM SE16N_INTERFACE and execute
3. Give table name in Itab,
I_EDIT =
X
I_SAPEDIT =
X
4. Press F8
5. Edit table entries and save.
Thanks -
How to edit GRUB boot options from within Arch.
Hello!
I'm having a problem with scanlines (both in X and tty), and I think that the solution is the vga= boot option. I, however cannot edit the GRUB boot options from within GRUB, because the commands go off my screen (overscan.)
I was wondering if there is a way to edit the default GRUB options from withing Arch. I have GRUB on /dev/sdb0 and chainload with the windows bootloader, it it matters.
Thanks,
wesleyac.Mr.Elendig wrote:http://www.gnu.org/software/grub/manual/grub.html
Thanks.
I cannot seem to figure out how the steps here translate to grub.cfg settings. If you could explain this to me or point me to somewhere that does, I'd appreciate it.
qinohe:
Thanks! I actually ran into a page that mentioned grub.cfg, but at the top of my grub.cfg, there's a big warning saing not to edit it. Should I ignore that? -
MOVED: A75MA-G55 UEFI boot entries disappear
This topic has been moved to Linux/Unix.
https://forum-en.msi.com/index.php?topic=153411.0Quote from: flobelix on 14-April-13, 04:12:52
And boot order is set to boot from SSD?
Yes, but it forces it to boot to EFI Shell. When I press F10 on startup there is no other option to boot from than EFI Shell. I had this mobo working for about month and half with Windows 8 without any problems. Now after I flashed it to v 2.0 (Which is not reverse downgradeable to older 1.xx version) whole system started to act strange, display resolution can not be set properly, sound card stopped working. I wonder if its really final or only unstable beta version of this bios file. -
Z77a gd65 doesn't boot/power off
Hello,
I have a problem with my z77a gd65. It doesn't boot anymore. Each time I need to clear CMOS. Also when I do a shutdown or restart it doesn't respond anymore. (all leds on motherboard are off except the first one of the CPU_PHASE leds). Shutdown or restart have the same effect when i try them in windows or bios, even the buttons on the board have the same results. Only the fans keep spinning. It doesn't power off anymore, I need to unplug the power cord.
It has worked for over 2 months, it just happened yesterday. I haven't installed or changed anything that day.
I haven't overclocked the mainboard.
I tried the latest BIOS version, but this didn't solved the problem
I removed all other hardware (videocard, hdd, dvd,...) but still same problem
Any suggestions
thanksQuote from: juikel on 03-December-12, 20:08:21
I've contacted the store and they replaced the board.
Thanks for your time flobelix!
Does that mean the system is now fixed and working? -
[SOLVED] Need help with rEFInd boot entry for rsync backup
I made a successful backup my arch install to an other internal SSD disk (from my HDD).
But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
This is the fstab for my HDD:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda5
UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
And this is the fstab on my SSD which I edited:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb1
UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
But I'm not sure about the /boot entry, do I need something else here?
Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
ps. I dual boot with Windows.
Last edited by Devenda (2014-08-18 07:58:07)I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
Invalid loader file!
Error: Not Found while loading vmlinuz-linux
Here is some additional info:
refind.conf:
menuentry "SSD Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "ArchSSD"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=/dev/sdb1 ro"
I hope this helps.
blkid
/dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
/dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
/dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
/dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
/dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
/dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
/dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
├─sda3
├─sda4 ntfs Windows 8 38D6E449D6E408C8
├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
├─sda6 ntfs F80680CC06808D76
└─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
sdb
└─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
sr0
boot tree
/boot
├── BOOT
│ └── boot.sdi
├── BOOTSECT.BAK
├── EFI
│ ├── Boot
│ │ ├── bootx64.efi
│ │ ├── LenovoBT.EFI
│ │ ├── License.txt
│ │ └── ReadMe.txt
│ ├── gummiboot
│ │ └── gummibootx64.efi
│ ├── Lenovo
│ │ └── Boot
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ ├── BCD.LOG2
│ │ ├── bg-BG
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── bootmgfw.efi
│ │ ├── bootmgr.efi
│ │ ├── BOOTSTAT.DAT
│ │ ├── boot.stl
│ │ ├── cs-CZ
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── da-DK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── de-DE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── el-GR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── en-GB
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── en-US
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── es-ES
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── et-EE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── fi-FI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Fonts
│ │ │ ├── chs_boot.ttf
│ │ │ ├── cht_boot.ttf
│ │ │ ├── jpn_boot.ttf
│ │ │ ├── kor_boot.ttf
│ │ │ ├── malgun_boot.ttf
│ │ │ ├── malgunn_boot.ttf
│ │ │ ├── meiryo_boot.ttf
│ │ │ ├── meiryon_boot.ttf
│ │ │ ├── msjh_boot.ttf
│ │ │ ├── msjhn_boot.ttf
│ │ │ ├── msyh_boot.ttf
│ │ │ ├── msyhn_boot.ttf
│ │ │ ├── segmono_boot.ttf
│ │ │ ├── segoen_slboot.ttf
│ │ │ ├── segoe_slboot.ttf
│ │ │ └── wgl4_boot.ttf
│ │ ├── fr-FR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── hr-HR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── hu-HU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── it-IT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ja-JP
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ko-KR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── lt-LT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── lv-LV
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── memtest.efi
│ │ ├── nb-NO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── nl-NL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pl-PL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-BR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-PT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── qps-ploc
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Resources
│ │ │ ├── bootres.dll
│ │ │ └── en-US
│ │ │ └── bootres.dll.mui
│ │ ├── ro-RO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── ru-RU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── sk-SK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sl-SI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-CS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sv-SE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── tr-TR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── uk-UA
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── zh-CN
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── zh-HK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── zh-TW
│ │ ├── bootmgfw.efi.mui
│ │ ├── bootmgr.efi.mui
│ │ └── memtest.efi.mui
│ ├── Microsoft
│ │ └── Boot
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ ├── BCD.LOG2
│ │ ├── bg-BG
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── bootmgfw.efi
│ │ ├── bootmgr.efi
│ │ ├── BOOTSTAT.DAT
│ │ ├── boot.stl
│ │ ├── cs-CZ
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── da-DK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── de-DE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── el-GR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── en-GB
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── en-US
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── es-ES
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── et-EE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── fi-FI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Fonts
│ │ │ ├── chs_boot.ttf
│ │ │ ├── cht_boot.ttf
│ │ │ ├── jpn_boot.ttf
│ │ │ ├── kor_boot.ttf
│ │ │ ├── malgun_boot.ttf
│ │ │ ├── malgunn_boot.ttf
│ │ │ ├── meiryo_boot.ttf
│ │ │ ├── meiryon_boot.ttf
│ │ │ ├── msjh_boot.ttf
│ │ │ ├── msjhn_boot.ttf
│ │ │ ├── msyh_boot.ttf
│ │ │ ├── msyhn_boot.ttf
│ │ │ ├── segmono_boot.ttf
│ │ │ ├── segoen_slboot.ttf
│ │ │ ├── segoe_slboot.ttf
│ │ │ └── wgl4_boot.ttf
│ │ ├── fr-FR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── hr-HR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── hu-HU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── it-IT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ja-JP
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ko-KR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── lt-LT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── lv-LV
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── memtest.efi
│ │ ├── nb-NO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── nl-NL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pl-PL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-BR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-PT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── qps-ploc
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Resources
│ │ │ ├── bootres.dll
│ │ │ ├── en-US
│ │ │ │ └── bootres.dll.mui
│ │ │ └── nl-NL
│ │ │ └── bootres.dll.mui
│ │ ├── ro-RO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── ru-RU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── sk-SK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sl-SI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-CS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-RS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sv-SE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── tr-TR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── uk-UA
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── zh-CN
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── zh-HK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── zh-TW
│ │ ├── bootmgfw.efi.mui
│ │ ├── bootmgr.efi.mui
│ │ └── memtest.efi.mui
│ ├── refind
│ │ ├── icons
│ │ │ ├── arrow_left.png
│ │ │ ├── arrow_right.png
│ │ │ ├── boot_linux.png
│ │ │ ├── boot_win.png
│ │ │ ├── func_about.png
│ │ │ ├── func_exit.png
│ │ │ ├── func_firmware.png
│ │ │ ├── func_reset.png
│ │ │ ├── func_shutdown.png
│ │ │ ├── os_altlinux.png
│ │ │ ├── os_arch.png
│ │ │ ├── os_centos.png
│ │ │ ├── os_chrome.png
│ │ │ ├── os_clover.png
│ │ │ ├── os_debian.png
│ │ │ ├── os_ecomstation.png
│ │ │ ├── os_fatdog.png
│ │ │ ├── os_fedora.png
│ │ │ ├── os_freebsd.png
│ │ │ ├── os_freedos.png
│ │ │ ├── os_funtoo.png
│ │ │ ├── os_gentoo.png
│ │ │ ├── os_gummiboot.png
│ │ │ ├── os_haiku.png
│ │ │ ├── os_hwtest.png
│ │ │ ├── os_kubuntu.png
│ │ │ ├── os_legacy.png
│ │ │ ├── os_linuxmint.png
│ │ │ ├── os_linux.png
│ │ │ ├── os_lubuntu.png
│ │ │ ├── os_mac.png
│ │ │ ├── os_mageia.png
│ │ │ ├── os_mandriva.png
│ │ │ ├── os_manjaro.png
│ │ │ ├── os_mythbuntu.png
│ │ │ ├── os_netbsd.png
│ │ │ ├── os_openbsd.png
│ │ │ ├── os_opensuse.png
│ │ │ ├── os_redhat.png
│ │ │ ├── os_refind.png
│ │ │ ├── os_refit.png
│ │ │ ├── os_slackware.png
│ │ │ ├── os_suse.png
│ │ │ ├── os_ubuntu.png
│ │ │ ├── os_unknown.png
│ │ │ ├── os_win.png
│ │ │ ├── tool_apple_rescue.png
│ │ │ ├── tool_memtest.png
│ │ │ ├── tool_mok_tool.png
│ │ │ ├── tool_part.png
│ │ │ ├── tool_shell.png
│ │ │ ├── tool_windows_rescue.png
│ │ │ ├── transparent.png
│ │ │ ├── vol_external.png
│ │ │ ├── vol_internal.png
│ │ │ └── vol_optical.png
│ │ ├── icons-backup
│ │ │ ├── arrow_left.png
│ │ │ ├── arrow_right.png
│ │ │ ├── boot_linux.png
│ │ │ ├── boot_win.png
│ │ │ ├── func_about.png
│ │ │ ├── func_exit.png
│ │ │ ├── func_firmware.png
│ │ │ ├── func_reset.png
│ │ │ ├── func_shutdown.png
│ │ │ ├── os_altlinux.png
│ │ │ ├── os_arch.png
│ │ │ ├── os_centos.png
│ │ │ ├── os_chrome.png
│ │ │ ├── os_clover.png
│ │ │ ├── os_debian.png
│ │ │ ├── os_ecomstation.png
│ │ │ ├── os_fatdog.png
│ │ │ ├── os_fedora.png
│ │ │ ├── os_freebsd.png
│ │ │ ├── os_freedos.png
│ │ │ ├── os_funtoo.png
│ │ │ ├── os_gentoo.png
│ │ │ ├── os_gummiboot.png
│ │ │ ├── os_haiku.png
│ │ │ ├── os_hwtest.png
│ │ │ ├── os_kubuntu.png
│ │ │ ├── os_legacy.png
│ │ │ ├── os_linuxmint.png
│ │ │ ├── os_linux.png
│ │ │ ├── os_lubuntu.png
│ │ │ ├── os_mac.png
│ │ │ ├── os_mageia.png
│ │ │ ├── os_mandriva.png
│ │ │ ├── os_manjaro.png
│ │ │ ├── os_mythbuntu.png
│ │ │ ├── os_netbsd.png
│ │ │ ├── os_openbsd.png
│ │ │ ├── os_opensuse.png
│ │ │ ├── os_redhat.png
│ │ │ ├── os_refind.png
│ │ │ ├── os_refit.png
│ │ │ ├── os_slackware.png
│ │ │ ├── os_suse.png
│ │ │ ├── os_ubuntu.png
│ │ │ ├── os_unknown.png
│ │ │ ├── os_win.png
│ │ │ ├── tool_apple_rescue.png
│ │ │ ├── tool_memtest.png
│ │ │ ├── tool_mok_tool.png
│ │ │ ├── tool_part.png
│ │ │ ├── tool_shell.png
│ │ │ ├── tool_windows_rescue.png
│ │ │ ├── transparent.png
│ │ │ ├── vol_external.png
│ │ │ ├── vol_internal.png
│ │ │ └── vol_optical.png
│ │ ├── keys
│ │ │ ├── altlinux.cer
│ │ │ ├── canonical-uefi-ca.der
│ │ │ ├── fedora-ca.cer
│ │ │ ├── openSUSE-UEFI-CA-Certificate.cer
│ │ │ ├── refind.cer
│ │ │ └── SLES-UEFI-CA-Certificate.cer
│ │ ├── refind.conf
│ │ ├── refind.conf.old
│ │ ├── refind.conf-sample
│ │ └── refind_x64.efi
│ └── tools
├── grub
│ ├── grub.cfg
│ └── grub.cfg.example
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── loader
│ ├── entries
│ │ └── arch.conf
│ └── loader.conf
├── refind_linux.conf
└── vmlinuz-linux
refind_linux.conf
"Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
"Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
"Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee" -
FiOS Quantum Gateway - Edit Port Forwarding Entries
New to FiOS. Installer provided the new Quantum Gateway.
Can't seem to figure out how to edit Port Forward entries on this gateway. Seems I can only add or delete them. But once created, no way to edit them to change. So to change anything, I have to delete the existing entry and recreate it. Pain in the ARSE.
Many other awefull interface usage issues on this gateway. Definately a lot of room for improvement.
...Also couldn't find anywhere to update firmware, so I'm guessing Verizon has no plans to ever release updates for this gateway...
Can't Edit DHCP Address Reservations
Can't Edit Port Foward assignments
Can't Release Address Reservations
Can't Convert DHCP Lease to a Reservation AND change the IP you'd like to assign (can convert to a reservation, but only using the IP dynamically assigned originally)
Can't sort tables
Sorting appears to always be based on MAC address, can't sort by IP or Name.
Am I missing something?toxicman wrote:
New to FiOS. Installer provided the new Quantum Gateway.
Can't seem to figure out how to edit Port Forward entries on this gateway. Seems I can only add or delete them. But once created, no way to edit them to change. So to change anything, I have to delete the existing entry and recreate it. Pain in the ARSE.
Many other awefull interface usage issues on this gateway. Definately a lot of room for improvement.
...Also couldn't find anywhere to update firmware, so I'm guessing Verizon has no plans to ever release updates for this gateway...
Can't Edit DHCP Address Reservations
Can't Edit Port Foward assignments
Can't Release Address Reservations
Can't Convert DHCP Lease to a Reservation AND change the IP you'd like to assign (can convert to a reservation, but only using the IP dynamically assigned originally)
Can't sort tables
Sorting appears to always be based on MAC address, can't sort by IP or Name.
Am I missing something?
You don't mention what router it is you have.
If it's the new Actiontec rev I you are quite correct - there is no apparent way to edit PF rules - totally user unfriendly -
Z77A-GD65 Win7 64bit boot fail followingMSI Live Update 5 Firmware update
Hi,
For some reason I decided to have a go with MSI Live Update 5 auto update today (having not used it previously in the 1.5years I've owned this system.
Running in Win 7 64 bit, it performed an 'update' and then the system completely crashed (as in turned off and on again). On reboot the system only went as far as the BIOS flash screen.
It failed to boot form the SSD boot drive and a message saying "Reboot with Proper Boot Drive".
I booted into BIOS (version 10.11) and the boot drive is still recognised.
I tried a reboot and the same error.
I tried to boot backup within BIOS and saw a message flash that ended with "Failed to initialize MSI-X".
None of the MSI applications work, it doesn't boot into Windows and I'm stuck.
Can anyone suggest how I might be able to get Windows back and running without having to do a full reinstall? I can't seem to get the backup software to work now so I'm a bit stuck. If I try and do a full flash of the drive and start again, will it fix the issue or is the problem with the motherboard/bios setup?
Has anyone else had this problem?
System spec:
MSI Z77A-GD65
Intel i7-3770k 3.5Ghz
Corsair Vengeance LP 8GB RAM
Win7 64BitYES
OK, so I found a few people on Tom's Hardware message board that seem to have the same issue with this latest BIOS update from MSI so at least it's not just me.
I reset CMOS
I set BIOS to default
I downloaded the BIOS ME from an older version 10.8 of BIOS that I knew worked fine (from another computer)
Flashed BIOS with USB
Booted the system with Win7 64 OEM CD
Selected Repair Mode
Let it do its thing
I'm back in business from where I left off.
Won't be touching the BIOS update again unless I can be absolutely sure its going to be stable on my MB.
RE: Legacy and UEFI
After installing 10.11, it defaulted to UEFI only but I changed the setting to Legacy and UEFI. It didn't fix the issue though.
I've rolled back, it works again so I'm happy other than the fact I've lost almost a full day of work over it.
Cheers xmad -
Varying boot times - Z77A-GD65
I have a new build and find that the boot times seem to vary for no apparent reason. Most of the time I will see the MSI splash screen within 15 seconds and then it boots quickly into windows. However, some times it will hang up on codes A2, B4, C3, or CA for up to 45 seconds before the splash screen appears and then it boots fine. I will note that no matter how long the boot takes, the system runs flawlessly and has never crashed or had any odd behavior other than the varying boot times. I see from the manual that A2 and B4 are Onboard Devices Initialize and Detect, but this happens randomly without changing any of the onboard devices. I ran memtest86 on the ram for over 12 hours and 6 passes and got no errors.
Anyone else have this experience or any suggestions on what may be causing it? I'm OK with it if others have the same experience and it is normal. I'm just concerned that it is a sign of some sort of problem.
First post, thanks in advance.
Intel i5-3570K (stock speeds)
MSI Z77A-GD65 board
Seasonic M12II 750 w psu
Corsair Vengeance LP Ram (16 GB)
Samsung Pro 840 128GB SSD drive (boot drive)
WD Caviar Black 500 GB HDD (data drive)
Win 7 Pro
ATI Firepro V5800 graphics
Noctua NH-U12P SE2 heatsink
Corsair Obsidian 550D CaseI tried disabling the PCIE GEN3 and I don't think it helped. I did a few restarts and still got a hang up on CA, whatever that is. Thanks for the codes. The most common ones I get seem to be:
A2 - IDE Detect
B2 - Legacy Option ROM initialization
B4 - USB Hot plug
C3 or C6 - OEM BDS Initialization Code
CA - no idea
The strangest thing is that I would say 7 out of 10 times it starts up perfect. The other 3 it will hang on something, but then it still boots and runs perfect. It just strikes me odd that I can make no changes whatsoever and it can go from perfect to hanging up. If anyone has any other suggestions for any of those codes, please feel free to respond. Thanks. -
How to edit GRUB for boot new compile kernel?
I compile the newest Linux kernel.
I read Archlinux wiki about how to edit GRUB for boot new compile kernel,
but Archlinux wiki do not reference to it.
Who can help me, baby?bangkok_manouel wrote:
how did you build your kernel? traditional way or arch way?
if it's the arch way (TM), here's an example of a custom kernel with -mm patch.
what I have in /boot:
-rw-r--r-- 1 root root 4.3M 2008-12-23 09:52 kernel26mm-fallback.img
-rw-r--r-- 1 root root 668K 2008-12-23 09:52 kernel26mm.img
-rw-r--r-- 1 root root 764K 2008-12-22 18:44 System.map26mm
-rw-r--r-- 1 root root 1.7M 2008-12-22 18:44 vmlinuz26mm
now here's the /boot/grub/menu.lst related entry (you may add the fallback one):
# (2) Arch Linux
title kernel26mm
root (hd0,0)
kernel /vmlinuz26mm root=/dev/sda5 ro vga=773
initrd /kernel26mm.img
Should be traditional way. -
Z77A-GD65 Wont Boot Without Clearing CMOS. Gets Error 32.
Hi!
I just switched GPU from 2x 7950 to 980.
I cleared drivers etc etc and was powering down my pc for the replacement. took out the cards and put in the 980.
When i later was trying to boot, i got debug error 32, which is early cpu initialization. So i checked all the cables and tried again. Same thing.
Took everything out and reinserted it again. Same error. even tried the to take out each ram to see. Still nothing.
I later cleared cmos and the computer booted. but then when i restart i doesnt boot until power everything down and clear cmos again.
Do you guys have any idea?
My specs are
Z77A-GD65
2500k CPU (Now after clearing CMOS at stock speed)
Corsair Vengance 2x4GB RAM
850W Bronze psuQuote from: Nichrome on 30-January-15, 15:01:36
Tryreplacing battery. Also could try to run it with single Ram stick and outside of the case.
I Couldn't wait so i went to town and bought me a battery, didn't change anything.
I've tried running a single RAM in each slot, just to try. no change there. Still error 32.
I've also test it outside the case now and still no difference.
Otherwise i've noticed i can boot if i press the reset button exact when debug code 55 shows. It's really weird. doing this way all bios settings are still there and i can test my pc with OC. I've played Dying Light on it this way with no problem at all. except this annoying code 32 who reappers everytime i restart my computer and hinders it to boot...
EDIT: Also sometimes (very rare), it starts at first boot. -
Boot Loop Issues - MSI Z77A-GD65 - Solved
Picked myself up an MSI Z77A-GD65 as well as some Kingston 2x 4GB RAM sticks with a i5 2500k.
After getting everything installed, it just boot-loops on me showing me no boot menu, with a debug code of 55.
If I take out one of the RAM sticks and just use the #2 slot, it boots fine (but after starting windows, it flashes some blue screen and it boots again. I'm thinking that's only because I haven't installed any drivers and still have the old drivers from my motherboard. Yes/No?).
But as soon as I put the second stick in, it will not boot (swapped sticks and it boots fine with one stick). I've tried 1/3 and 2/4 and the only slot that seems to work is #2 (#4 slot won't boot with one stick in it). Tried each stick in each slot. 1/2 work, but 3/4 will not
I'm guessing this isn't a RAM issue but a MOBO issue? I sense an RMA in my future....Quote from: XFM on 24-December-12, 08:29:56
Can you take a good quality, in focus hi-rez picture of the socket and post it so we can see what you are talking about?
I would if I could. Best way I can describe it is that the pins are all kind of bent at an angle (imagine an L shape, but upside down). Now take the bottom of the L (where it's small and turns) and kind of bend that facing the ceiling. It's kind of like that...
Quote from: Froggy Gremlin on 24-December-12, 08:30:08
Why is this thread in the Intel duo/quad section?
What are the amps on the PSU +12V rail(s)? And how old is it? Suggest to keep just the one RAM stick in the primary DIMM slot and do a fresh OS install with the Mode set to AHCI. BTW, what is the OS? 32 or 64 bit?
Good question. I think I was very tired/annoyed when I made this, and I guess I didn't look properly. If any mods can move it, or need me to take it down, I can.
PSU - http://www.newegg.com/Product/Product.aspx?Item=N82E16817703005
I don't have a problem doing a fresh install, but would like to make sure it's nothing else before hand. If I do a fresh install, and I still have to RMA the board, I would have to do another one to put all my old stuff back in, and I wouldn't really have a PC until the new board came (I mean I could still use it, but would have to re-install stuff and it seems like a bit of a pain if I don't *have to).
64-bit OS
Maybe you are looking for
-
Limiting Discount to customers
Hello, We have four discount condition types in our pricing prodcedures with 2%, 3%, 7% and 4% discount. We want system to limit the total discount to 10% at any time to our customer . How this can be acheived and pls advice on the complete confi
-
Hello! Does anyone know the t-code to create a broadcast setting? I would like to create a broadcast through the SAP GUI back-end rather than running it through the portal. Is there a t-code to do that? Thanks! Andrew
-
Okay, just picked up the E71 and trying to sync it with my Mac. For this I understand I need to download iSync. Problem is, apparently I need OSX 10.4.6 at least and I'm only running 10.3.9. Is there any way of getting iSync for my E71 and if so, how
-
Efax gives error when trying to connect
I'm running Arch 64bit with multilib I have a fax modem that I've checked out @ xmodem.org for compatibility. Modem: GVC F-1156I from lspci: 04:01.0 Communication controller: Agere Systems LT WinModem (rev 02) I was trying to send a test page thro
-
Hello, I have to use a logo in a TIFF format. It is made up of mainly letters and graphics, but somehow, the edges of the whole logo look terrible. Redoing it is not an option. Any way to smooth things out in CS5? I have tried with the Gaussian blur