MOVED: A75MA-G55 UEFI boot entries disappear

This topic has been moved to Linux/Unix.
https://forum-en.msi.com/index.php?topic=153411.0

Quote 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.

Similar Messages

MOVED: A75MA-G55 - "Lab Burst Mode"?

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=153182.0

I checked the changelogs for the standard BIOS release series of the A75MA-G55. There are two references to "Lab Burst Mode".
The first appears in the changelog for the E7696AMS.138 [v1.3b8] release:
- Change setup item "Enhanced Spread Spectrum" to "Lab Burst Mode".
The second reference appears in the changelog for the E7696AMS.139 [v1.3b9] release:
- Fixed Lab Burst Mode always enable when OC more than 133Mhz successful then load default.
That tells us three things:
1) The option should be available be available in the E7696AMS.130 final release under the name "Lab Burst Mode" and as "Enhanced Spread Spectrum" in all final releases before that.
2) The "old name" for that option suggests that it has to do with "clock modulation" (because that is what Spread Spectrum generally does).
3) Spread Spectrum probably may need to be enabled first in order to get access to the "Lab Burst Mode"/"Enhanced Spread Spectrum" option.

[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?

MOVED: A75MA-G55 and memory Problem

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=152324.0

1866 is a multiplication of something. Do not set it to 1866!!
I do not know your motherboard, but your processor would probably like something that add up to 1333 MHz.

MOVED: A75MA-G55 Static-y, echo-y audio output from local files

This topic has been moved to Linux/Unix.
https://forum-en.msi.com/index.php?topic=156801.0

fuser -v /dev/snd/* when chrome is playing an mp3
UTENTE PID ACCESSO COMANDO
/dev/snd/controlC0: gigitsu F.... pulseaudio
/dev/snd/controlC1: gigitsu F.... pulseaudio
/dev/snd/controlC2: gigitsu F.... pulseaudio
/dev/snd/pcmC0D0p: gigitsu F...m chrome
/dev/snd/timer: gigitsu f.... chrome
/etc/pulse/default.pa without comments
.nofail
.fail
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore
load-module module-augment-properties
load-module module-switch-on-port-available
.ifexists module-udev-detect.so
load-module module-udev-detect
.else
load-module module-detect
.endif
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif
.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif
load-module module-default-device-restore
load-module module-rescue-streams
load-module module-always-sink
load-module module-intended-roles
load-module module-suspend-on-idle
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif
load-module module-position-event-sounds
load-module module-filter-heuristics
load-module module-filter-apply
And i've not altered /usr/share/alsa/alsa.conf.
libflashsupport-pulse did not work, I've killed and started pulseaudio but nothing. I did not even flashplugin

MOVED: A75MA-G55 oc genie 2

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=152929.0

Geez... You Too?
Plus RAID issues
Plus Crossfire issues
This is my first new build in a while.
MY initial overclocking experience involved a #2 pencil and a 750mhz AMD Duron,
after that it was more like microsurgery with magnified optics, soldering traces.
I haven't done much since AGP got phased out by PCI.
What sounded like, in the initial reviews, to be a Board "Sent by the Gods"
I bit... I bought...
and now I'm finding that there is no documentation anywhere on
initializing any of the features that I bought it for in the 1st place.
Sure, I can Convert(x) 2 .avi movies per DVD in 20 minutes instead of 2 hours...
But I'm walking around feeling like I just PAID to be a BETA Tester.
LiveUpdate5 keeps telling me "Your Drivers are current, You have nothing to update'
When I KNOW there are more current point releases. I've SEEN them.
I make $10 an hour... after taxes and child-support payments, that leaves $195 a week.
Any ideas on How Long you have subsist on Ramen Noodles and multi-vitamins to do this?
I've got about a month's pay sunk into this system
New Coolermaster HAF case w/ 200mm red led fans
It Looks good... It LOOKS like it wants to run
4G of 1600 mhz Corsair VENGEANCE RAM
and another 4G in reserve for Win7 (current XP)
MSI R6670 Graphics Card
a Terabyte of Fresh Barracuda's...Raid 0 would SO pump out those GB/s
Half the frustration was that my 1st 7696 had a bad RAM slot #2
5 hour round-trip to MICROCENTER on public transportation- THREE TIMES
only to find out that it WASN'T the RAM being quirky.
Once I figure this thing out...and I will figure it out
I'll post my findings.
I just don't get it though...
in the reviews... snip, snap, plug, power... bada-bing bada-boom
... HUMMING!!!
and I wonder if I'm too stupid or too smart to solve the problem.
I'll be in touch

MOVED: A75MA G55 default memory frequency

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=152729.0

yes that's true. memory doesnt support jedec at higher level than 666 Mhz. just XPM is 1k MHz
It is not such a big problem to owerlock the memory to get it work on that frequency, but more, what i dont understand is, why i cannot get change the NB frequency to this 993Mhz.
I tried to overlock it also, i have movedl bus speed to higher level, but also max cannot give me this number and of course computer is than very unstable ( problems to start etc. )
I would like to have this overlocked frequency supported also by mobo and CPU and it looks like i'm not able to get it in any way :D or better :(
maybe im missing some point here.

BETA UEFI Releases for the A75MA-G55 [MS-7696 PCB v1.0]

I am uploading the latest BETA Release for the A75MA-G55 [MS-7696 PCB v1.0] mainboard.
Currently, the latest version is E7696AMS.13A [=v1.3b10].
E7696AMS.120 ---> E7696AMS.13A
- Fix ps2 kb/mouse issue when WHQL test.
- Update Llano-AGESAMSI module.
- Update VBIOS to AMD_SUMO_GENERAL_100.
- Update Llano-AGESAMSI module.
--->Fixed DRAM Timing incorrect when DRAM insert DIMM3 or DIMM4.
------> a) When OC Genie Enable and insert 1600Mhz Memory, system will reduce Memory frequency to 1333Mhz, but work timing still use DDR1600. DRAM Timing mode must be set to Manual at this moment.
------> b) When OC Genie Disable, above setting have be set to Auto.
- Add CPU FAN 3/4 PIN ITEM and System FAN1 SMART FAN Support.
- Fixed select RAID mode and SATA decive plug on SATA1 or SATA2, system will hang CP#B2 issue.
- Fixed AMD USB3 yellow mark issue in WHQL test.
- Patch System FAN1 SMART Fan Support.
- Fixed CPU/System1 SMART Fan cannot work on first setting.
- Patch two Memory fail issue.
----> G.Skill F3-1066CL7T-3GBPK
----> G.Skill F3-1066CL7T-6GBPK
- Patch TL-584 and RST.
- Fixed when Enabled TPM support, system will hang CP#4F 40 Sec issue.
- Update TMP patch.
- Update Llano-AGESAMSI module.
- Update SB module to 4.6.4.1_AMD_SB900_017.
- Update AHCI module to 4.6.3_AhciSrc_017.
- Update CSM function.
- Update PEI Ram Boot module to 4.6.3_PEIRamBoot_10.
- Update smiflash module to 4.6.3.6_SMIFLASH_19.
- Update shell module to 4.6.3_SHELL_20100528_01.
- Update fixedbootorder module.
- Update post time tune module to 4.6.4.0_PTT_06.
- Update to 4.6.3.7_AgesaV5_039.Modified AGESAMSI setup menu for OCICC.
- Show cpu ratio in cpuz module.
- Add ukey function.
- Add VGA display rule.
- Adjust Initiate Graphic Adapter default to PEG.
- Fix some time will hang 0Dh by fixbootorder function.
- Fix plug PCI/PCIE lan card can't boot issue when the "Lan Option ROM" item set disabled.
- Fix mflash boot issue.
- Change setup item "Enhanced Spread Spectrum" to "Lab Burst Mode".
- Fix memory-z part string issue for some memory.
- Enable C'n'Q function as default and C1E item.
- Add clear cmos function.
- Adjust VGA display rule.
- Fixed Lab Burst Mode always enable when OC more than 133Mhz successful then load default.
- Fix bev device cannot boot.
Please note that flashing this release occurs entirely at your own risk! >>Use the MSI HQ Forum USB flasher<<, Method II for best results. Do NOT use the BIOS/UEFI integrated M-Flash Routine.

E7696AMS.146 ---> E7696AMS.140
- Add UEFI_Driver module for doing raid and installing UEFI OS.
E7696AMS.140 ---> E7696AMS.150
- Add Agesa MSI Source safe version 4.6.3.7_Llano-AGESAMSI_040-4.
- Modified AGESAMSI Adjust Ratio function incorrect.
- Support CMOS bad flag in AGESA Platform Configuration.
E7696AMS.150 ---> E7696AMS.162
- Fix USB keyboard and mouse would useless after using m-flash boot function.
- Fixed system can't boot up when press 'Del' or 'F11' key with using AMD A4-3300 (AD3300OJZ22GX/HX) sometimes.
E7696AMS.162 ---> E7696AMS.163
- Fixed clear coms or use M-Flash update bios "Windows Boot Manager" will lost.
- Fix windows boot order will be disordered after clear coms or load default.
Please note that flashing this release occurs entirely at your own risk!
>>Use the MSI HQ Forum USB flasher<<, Method II for best results.
Do NOT use the BIOS/UEFI integrated M-Flash Routine.

MOVED: Found issues on A75MA-G55

This topic has been moved to Overclockers & Undervolting & Modding Corner.
https://forum-en.msi.com/index.php?topic=152752.0

Quote from: HU16E on 05-October-11, 01:17:33
No need to clutter up the beta thread with final releases when it is readily available at the MSI Global Website for the mainboard; http://eu.msi.com/product/mb/A75MA-G55.html#/?div=BIOS
Don't use Live Update. For flashing, use the forum's USB Flashing Tool found here, along with instructions how to use it; https://forum-en.msi.com/index.php?topic=108079.0
Like I said earlier, I can't download the 1.3, it says my bios is the latest. And if MSI could be sweet and put a download link instead of pointing to Live Update.

MSI A75MA-G55 won't boot sometimes

Hello,
My system specs:
MSI A75MA-G55
AMD Llano A8-3850
Corsair Vengeance CMZ8GX3M2A1600C83
Corsair Builder CX430 V2
My system sometimes boots and sometimes not.
Memtest has run a whole night without errors.
Al settings on manual won't help.
Having only one RAM module on the board didn't help.
It looks like the mobo and the RAM aren't broken.
Is it not compatible or what?
I can't update the BIOS because it hangs on making a backup.

Quote
I can't update the BIOS because it hangs on making a backup.
See here for solution:
https://forum-en.msi.com/index.php?topic=152524.msg1129109#msg1129109

[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"

A75MA-G55: Lab Burst Mode temp sensor bug

Me and a friend were on a quest to find the best BLK frequency on stock voltage and finally arrived on 153MHz to be the max possible on stock voltage.
We went some benchmarking on 7-zip, GTA4 and wPrime without problems, only we can't measure the cpu core temperature because of that no software can't give us an honest result.
Then our heads came up with an idea, howbout 2hours Prime95 then quick reboot and check temps from Bios.
2 hours later quick reboot, enter bios and there we almost passed out... CPU temperature: 128 degrees Celsius but case temp on 27degrees C.
We left the system off for 3 hours then checked again from a cold boot, 128 degrees C again! then we changed to default settings and there we go 25 degrees C, we switched back to LabBurstMode and temperature showed us again 128 degrees C.
Maybe this was a planned Helloween trick from the MSI team But this have to be looked at.
System:
2x A8-3850 chips
2x 1866MHz Kingston 4GB
2x 1600MHz OCZ Gold 2GB
MSI A75MA-G55
Asrock A75Pro4-M
500GB WD Black
2x 500GB WD Green
Corsair TX650

I checked the changelogs for the standard BIOS release series of the A75MA-G55. There are two references to "Lab Burst Mode".
The first appears in the changelog for the E7696AMS.138 [v1.3b8] release:
- Change setup item "Enhanced Spread Spectrum" to "Lab Burst Mode".
The second reference appears in the changelog for the E7696AMS.139 [v1.3b9] release:
- Fixed Lab Burst Mode always enable when OC more than 133Mhz successful then load default.
That tells us three things:
1) The option should be available be available in the E7696AMS.130 final release under the name "Lab Burst Mode" and as "Enhanced Spread Spectrum" in all final releases before that.
2) The "old name" for that option suggests that it has to do with "clock modulation" (because that is what Spread Spectrum generally does).
3) Spread Spectrum probably may need to be enabled first in order to get access to the "Lab Burst Mode"/"Enhanced Spread Spectrum" option.

Booting hangs at loading vmlinuz-arch.efi (UEFI boot)

Hello,
I have just installed Arch Linux on my desktop machine (UEFI motherboard) which contains drives & partitions as follows:
1. /dev/sda (~ 250 GB) with
1: Win 7 64 bit
2: ntfs partition for data
3: ntfs partition for programs
2. /dev/sdb (1 TB) with
1: ntfs
2: fat32 / vfat as the uefi partition thingy
3: linux fs with swap, root and home
I have followed the Beginners' Guide dow nto the letter.
So I used rEFInd to set up the UEFI boot manager. However, it hangs at using the vmlinuz-arch.efi file/partition (?) on boot.
I have tried booting with a new efibootmgr entry as well, but it still hangs.
At this point, I'd like to know:
How can I get rid of all the rEFInd boot manager entries?
What precisely do I have to do to get it working? I could, of course, read around on here all day, but I somehow won't really learn anything as I can't deduct the right path of action for myself. If the machine weren't my productive system I'd definitely "play" around a lot more, that's for sure.
Any advice is greatly appreciated.

henrik wrote:
Thanks for your reply.
s1ln7m4s7r wrote:
OK, i will post, maybe it can help you!
First you need to boot from the arch installation media in UEFI mode. Mount your system partitions and chroot into it.
If you only have refind and kernel files under /boot/efi/ you can delete all files (clearing the EFI partition).Then run
modprobe efivars
. If you want to remove any efi entry, you can do it with
efibootmgr -b <entry_number> -B
Ok I did that.
sed -i "s/root=PARTUUID=XXXXXXXX rootfstype=XXXX ro/root=UUID=$(blkid -s UUID -o value $(df -k /)) rootfstype=$(blkid -s TYPE -o value $(df -k /)) ro/" "/boot/refind_linux.conf"
You meant here for me as wlel to exchange the X's wit hthe corresponding keys, right? I mean I did it. Would not make sense to me to call the comman with lots of Xs.
The rest was quite easy, I paid a lot of attention and made sure I typed in everthing correctly.
I am now at a blank black screen and there is a white underscore flashing in the upper left corner.
edit Can't boot into Windows anymore. Can't repair the MBR / UEFI boot with the Windows 7 DVD either...
edit2 Did lots of googling and at least Win 7 works fine again.
No. All the code is for you to type exactly as it is. The only statements you need to replace are <drive_with_efi_partition> and <efi_partition_number> with your current setup. What the line you questioned does is to replace the lines with "root=PARTUUID=XXXXXXXX rootfstype=XXXX ro" using the linux "sed" command, in refind_linux.conf with "root=UUID=<autodetected_uuid_of_your_root_partiton> rootfstype=ext4 ro". That will only work with the original refind_linux.conf, so if you edited it, you need to rerun
cp -r /usr/lib/refind/config/refind_linux.conf /boot/
There are 3 main reasons that may caused you to boot into a black screen with nothing written on it.
1. By not writing the code as it is, and editing files by hand instead, you may have done something wrong;
2. Your computer is booting from the wrong uefi entry, intead of the one created earlier;
3. You need to have "nomodeset" in your kernel boot line.
When does the black screen apears? After selecting a refind entry from refind's menu? Right after the pc boots (refind menu does not appear)
Another thing. In order for you to have access to windows, you need to edit refind.conf windows corresponding entry and remove the disabled statement or it wont appear on refind menu
Last edited by s1ln7m4s7r (2013-04-05 17:02:18)

[SOLVED, sort of] Yet another UEFI boot issue

Hello everyone,
Let me start by saying sorry for the long (first) post.
I've ended up with a UEFI boot problem I can't solve. I've searched the forum and internet and I realize I'm not the only one who ran into problems with UEFI. Unfortunately, the problems other have had seem not similar to mine. I've spent almost 2 days now trying to figure this out, and I'm getting nowhere (though I've learnt some more about UEFI, which I guess is good). I was hoping someone here can give me some hints on how to proceed.
So lets start with the background. I recently bought a new computer (Lenovo Thinkpad Edge E530 with Windows 8) and of course I want to run ArchLinux on it (been using ArchLinux for almost 7 years now and no plans on switching). Installation went ok with only a few problems during installation that I managed to solve (or so I thought). I must admit I didn't follow the guide fully. I didn't want to remove the Restore and Windows partitions, so I figured it would be safe to reuse the existing UEFI System Partition, as long as there was enough room, which there was. Anyway, I now have a computer I can boot into ArchLinux and also Windows 8, just the way I want it, almost. There is this one final issue I haven't been able to figure out how to solve.
The problem
Whenever I reset/power on the computer, I must press Enter during the initial screen (showing a Lenovo logo, and a message about pressing Enter to interrupt normal startup). If I don't press Enter before the timeout (a second or so), the screen will go white and that's it. No beep, no message, no nothing but a white screen. A power cycle is the only way to leave this state. Occasionally the screen will be a white bar at the top and random colours below, but I'm guessing this only represents what is in graphics memory at the time (0x00, 0xFF or any other random value).
If i do press Enter however, then I'm presented with a menu where I can select what to boot; rEFInd (which is preselected) along with Windows 8 and some restore and diagnostic entries. Pressing enter will take me to the preselected rEFInd, pressing enter again (or wait for timeout) will boot linux, and I'm in. Nothing weird there. And if I select Windows in rEFInd, then windows boot, just as expected.
There is no difference whether I'm switching from Windows to Linux or Linux to Windows or just reboot the same OS I was using again. The result is the same whatever I choose to boot.
So the question is: Why do I have to select rEFInd manually and go through all these menus? Should I not be able to just power it on and let it boot the preselected rEFInd entry and continue from there, without me helping it?
Trying to solve it
Searching here and on the internet gave me some ideas on what to try, so here is a list of my attempts:
efibootmgr show me there is a rEFInd entry, and that it is the first one in boot order
I copied refindx64.efi to /boot/efi/EFI/Boot/bootx64.efi (replacing an existing entry)
I've updated the EFI firmware (from Lenovo) to the latest and greatest
One other guy had almost the same issue, but with a single boot of Windows. He solved it with Microsoft Boot Manager (there is an Automatic Repair, or something). I even dared trying this, though I must admit I was a bit hesitant about letting some Microsoft program trying to repair my computer. Anyway, it said it couldn't repair my problem, nor did it say I had one, so I am none the wiser.
None of the above gave anything.
So, that's it. I guess I can live with having to press Enter on every power up/reset, but it is very annoying having to do so, and even more so when I forget it because then I'm forced to power cycle it. I hope someone reading this can figure out what's going on, because I am clueless.
Best regards,
Johan
Last edited by 6feet5 (2013-01-08 19:03:50)

WonderWoofy wrote:@srs5694, have you thought about filing a bug report/feature request about the naming scheme here? I would imagine that something coming directly from the upstream developer would be something that they should take into consideration. Also, I imagine that renaming it to refindx64.efi kind of goes against the whole "vanilla packages" thing we tout around here... so it really makes me wonder why it is done in the first place.
I've just done that:
https://bugs.archlinux.org/task/33326
It's not been very important until recently; but I've been putting a lot of effort into the ancillary support scripts (install.sh and mvrefind.sh). They necessarily rely on the files having certain names, so installing them under other names robs users of functionality.
6feet5 wrote:I've decided to try and restore the whole unit, thinking it would take maybe an hour or two. It's been running now for almost 3 hours and only completed 20%.
Good luck with that!
FWIW, it seems that the number of EFI-related bug reports on Linux forums has gone way up recently. No doubt this is because EFI is now pretty much universal on new computers, so problems that used to affect one or two people now affect dozens or hundreds, and some of those post about them.

[SOLVED] UEFI boot configuration using efibootmgr

Hello All,
I've been having a very frustrating time with efibootmgr on my HP Laptop.
I've been searching around for some information regarding the OS Bootmanager in UEFI boot and cannot find anything that works for me.
I'm trying to get efibootmgr to load the boot entries in the order that I specify, but, although it lists exactly what I want in the terminal, when it comes to a reboot, the OS Bootmanager is failing and writing new entries every boot and I cannot fathom why.
Please could someone point me in the direction of a good guide to UEFI boot/OS Bootmanager and it's configuration using efibootmgr? I have read info found in the Archwiki, but was hoping for something focussing on efibootmgr alone as a configuration tool.
Many thanks for your help,
Frazer
Last edited by frazer (2014-03-10 22:21:14)

It's likely that the firmware (or maybe Windows, if you're booting into Windows between boots and haven't mentioned that fact) is changing the boot order. Unfortunately, some EFIs do that, or worse.
I recommend you start by upgrading your firmware. (In some cases, this will wipe out all your boot entries, so be prepared.) If the problem continues, either file a bug report with the manufacturer or return the hardware for a refund and buy something else. The manufacturers have had a long enough time to work out such major problems with their firmware, and returning defective hardware is really the only thing we as consumers can do that will get the manufacturers' attention.
If you must keep the hardware and a firmware update doesn't help, you may just need to find a workaround. If you need advice on doing that, you'll need to provide more details about what your setup is -- in particular, what you want the boot manager's boot list to look like (as in "efibootmgr -v" output once it's configured) and how the firmware is reshaping that when you reboot.

MOVED: A75MA-G55 UEFI boot entries disappear

Similar Messages

Maybe you are looking for