DKA790GX Bios and ACC settings

I am running on the 9950BE 140W chip on this board and was wondering if anyone knows what ACC settings mean or leaving it at auto gives the most headroom for an OC.
I'm running on the v1.2 bios and also realize that even though the system runs stably (prime95 runs fine for over 8hrs) at 3.1Ghz (230 x 13.5), the system fails to post from a cold boot sometimes. Another perculiarity I've noticed with this board is that for memory overclocking, you have to leave it at a lower speed and overclock the FSB 1st before even tweaking any memory settings for the system to POST. Adjusting the memory voltage does not help.
Anyone with the same experience?

I just slapped a 125 watt 9950 in my DKA790GX Platinum a couple of days ago.  I also was getting blue screens at start-up like a memory issue.  I found ACC being on was the actual cause of the problem.  When I turned ACC off, everything worked fine.  I was running a beta bios MSI gave me for another issue with my old 9600 cpu so it may or may not apply in your case.  I did flash the new 1.30 bios that was very recently posted and I was then able to use ACC with no more problems at start-up.  Once I got ACC running on auto, I found that with the 9950 I was able to lower the cpu voltage to 1.26v completely stable where it needed 1.30v with ACC off.  I haven't attempted to overclock yet as I am temporarily using the stock cooler, but being able to lower the voltage that much with it on should help a lot with heat issues in overclocking this chip.  The one document I saw from AMD on ACC stated to use the all four cores setting with +12 for the best overclocking results, but at least with the 9600 I seemed to get better results using auto.

Similar Messages

  • MOVED: DKA790GX Bios and ACC settings

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

    I just slapped a 125 watt 9950 in my DKA790GX Platinum a couple of days ago.  I also was getting blue screens at start-up like a memory issue.  I found ACC being on was the actual cause of the problem.  When I turned ACC off, everything worked fine.  I was running a beta bios MSI gave me for another issue with my old 9600 cpu so it may or may not apply in your case.  I did flash the new 1.30 bios that was very recently posted and I was then able to use ACC with no more problems at start-up.  Once I got ACC running on auto, I found that with the 9950 I was able to lower the cpu voltage to 1.26v completely stable where it needed 1.30v with ACC off.  I haven't attempted to overclock yet as I am temporarily using the stock cooler, but being able to lower the voltage that much with it on should help a lot with heat issues in overclocking this chip.  The one document I saw from AMD on ACC stated to use the all four cores setting with +12 for the best overclocking results, but at least with the 9600 I seemed to get better results using auto.

  • Upgrade BIOS and drivers have possibly corrupted drive. OS will not boot.

    Model: Toshiba P505-8980
    Part Number: P6PG0U-005002
    OS:  Windows 7 Professional 64-bit (upgraded from Home Premium)
    6 gig RAM, 500gig HD
    Actions:
    I haven't started up my computer in a while.  First I installed the critical and optional updates (3 total) from windows update, rebooted, and Toshiba Service Center popped up and said that there was the BIOS 3.10 update and the HDD/SSD Alert update.  Through the Service Center I downloaded and installed the BIOS update, at the end it seemed as if there was an error.  I rebooted the computer and everything seemed ok, so I downloaded the HDD/SSD update through the Service Center.  Upon rebooting the drive would not boot.  (Screen remained blank with a blinking cursor and HDD light was not on.)  There are no accessories/USB devices/drives attached.  After a reboot I checked the BIOS and it recognizes the Hard drive, I restored all settings in BIOS to default and rebooted.  The computer started receiving stop errors (blue screen) and stuck in a reboot loop.  I entered the BIOS, restored default settings again and rebooted, I could get to safe mode and it would receive stop errors trying to load disk.sys file.  I also tried last known good configuration and that wouldn't work either.  After a while the laptop was able for me to select to try and repair the disk using the repair utility.  It reported that there may be partition errors (on the last step of recovery) and I selected to repartition the drive to factory default with the Toshiba repair tools.  It got to about 98-99% and received errors at the end.  I tried using a Windows disk to reinstall the OS, but it reported it couldn't install on any of the drive partitions because of an error in the boot configurations.  After trying to repair again it doesn't report any disks or partitions.  Currently after booting it reports now that there is an error that occurred while attempting to read boot configuration.  File: \Boot\BCD|Status: 0xc000000f.  Guessing that the boot sector got corrupted.  After reading that BIOS isn't recommended to be installed while in windows, I'm wondering if using the service center messed something up.
    Question 1:  Any recommended actions to take now?  No recovery disk available
    Question 2:  Is there a way to configure the service center to download a BIOS update and be able to save it instead of only being able to install it within windows and the service center?
    Thanks in Advance!

    I was able to get into system recovery.  This system recovery was different then the first one I came across.  Underneath the Command Prompt option there was a selection for a Toshiba based restore.  That is the one I tried that failed at 98-99%  This system recovery just has the standard options.  At first it showed me the original OS of Home Premium (recovered).  I tried to repair the Home Premium and it still wouldn't work.  "Startup could not repair the problem".  On the many tries the probelms were either "Failed Installation" or "Partition Table".  Then when I tried loading the OS it would blue screen and reboot repeatedly.  So I loaded up Windows 7 Professional from a different CD to at least get the OS working.  I tried Repairing but that didn't work with the same errors, and it also reported that there was no system image on the disk.  I did a Custom (fresh) install and had all items copied to Windows.Old folder.  So now I have an OS, BUT I can't activate it now even with the keys that I have from the old version because it said the key was only used for upgrade, not clean installs.  So now I'm left with trying to find a way to get the original Home Premium image so I can load that and then upgrade since I have the keys I need.  I tried doing repairs again, this time it showed me two Windows 7 Professional and one Windows 7 Home Premium.  Again I tried repairing the Home Premium but it came back with the same errors.  Now all that remains is just the fresh install of Windows 7 Professional that I installed but can't activate with the key.  Anyway I can get/download a factory image from Toshiba?  I only just bought the laptop shortly before Christmas.

  • [865PE/G Neo2 Series] Memory timings and power settings anyone?

    I'm not very good with computers, so I've just played around with the timings on my memory, but have not found one stable setting as of yet.
    The memory is brand new and I've tested it for errors on my brothers computer and there's nothing wrong there.
    Intensive harddrive usage, dvd playing and intense downloading while listening to music are sure ways to crash my system. "..........Not less or equal" is the most common error message, but there are
    many many more.
    Oh, maybe I should point out that overheating's not an issue, cause I've good fans and run my computer without sidepanels.
    I also like to say that I have the first generation of p4 with ht and 533fsb.
    I'm sure there's something I forgot to mention but here below I'll paste the system summary that Sandra gave me.
    Would be forever grateful if someone could help me out with the memory timings and power settings for my board. Setting it to "auto by spd" gives me a very unstable system, so no avail there.
    I'm running the mem at 2.70 and sometimes at 2.65, since these two settings seem to be the ones with least crashes.
    The Memory installed are 4*512mb ,kingston 512 kvr333x64c25 pc2700
    The PSU is a Tagan "TG480-u01" 480w
    Many many thanks in advance guys. 
    SiSoftware Sandra
    Processor
    Model : Intel(R) Pentium(R) 4 CPU 3.06GHz
    Speed : 3.10GHz
    Performance Rating : PR4118 (estimated)
    Cores per Processor : 1 Unit(s)
    Threads per Core : 2 Unit(s)
    Internal Data Cache : 8kB Synchronous, Write-Thru, 4-way set, 64 byte line size
    L2 On-board Cache : 512kB ECC Synchronous, ATC, 8-way set, 64 byte line size, 2 lines per sector
    Mainboard
    Bus(es) : ISA AGP PCI IMB USB FireWire/1394 i2c/SMBus
    MP Support : 1 Processor(s)
    MP APIC : Yes
    System BIOS : American Megatrends Inc. V2.5
    System : MICRO-STAR INC. MS-6728
    Mainboard : MICRO-STAR INC. MS-6728
    Total Memory : 2GB DDR-SDRAM
    Chipset 1
    Model : Micro-Star International Co Ltd (MSI) 82865G/PE/P, 82848P DRAM Controller / Host-Hub Interface
    Front Side Bus Speed : 4x 135MHz (540MHz data rate)
    Total Memory : 2GB DDR-SDRAM
    Memory Bus Speed : 2x 168MHz (336MHz data rate)
    Video System
    Monitor/Panel : Iiyama A201HT VisionMaster Pro 510
    Adapter : RADEON X800 Series   
    Adapter : RADEON X800 Series Secondary
    Imaging Device : CanoScan FB630U/FB636U #2
    Imaging Device : Video Blaster WebCam 3/WebCam Plus (WDM) #2
    Physical Storage Devices
    Removable Drive : Diskettenhet
    Hard Disk : ST3160023AS (149GB)
    Hard Disk : WDC WD1000BB-00CAA0 (93GB)
    Hard Disk : WDC WD1200JB-00CRA1 (112GB)
    Hard Disk : FUJITSU MPG3409AT  E SCSI Disk Device (38GB)
    CD-ROM/DVD : PHILIPS DVDR1640P (CD 63X Rd, 63X Wr) (DVD 8X Rd, 8X Wr)
    CD-ROM/DVD : PLEXTOR CD-R   PX-W4824A (CD 40X Rd, 48X Wr)
    CD-ROM/DVD : AXV CD/DVD-ROM SCSI CdRom Device (CD 32X Rd) (DVD 4X Rd)
    CD-ROM/DVD : AXV CD/DVD-ROM SCSI CdRom Device (CD 32X Rd) (DVD 4X Rd)
    CD-ROM/DVD : AXV CD/DVD-ROM SCSI CdRom Device (CD 32X Rd) (DVD 4X Rd)
    CD-ROM/DVD : AXV CD/DVD-ROM SCSI CdRom Device (CD 32X Rd) (DVD 4X Rd)
    CD-ROM/DVD : AXV CD/DVD-ROM SCSI CdRom Device (CD 32X Rd) (DVD 4X Rd)
    Logical Storage Devices
    1.44MB 3.5" (A:) : N/A
    Hard Disk (C:) : 149GB (101GB, 67% Free Space) (NTFS)
    Xp (D:) : 112GB (2.1GB, 2% Free Space) (NTFS)
    Big (E:) : 93GB (9GB, 10% Free Space) (NTFS)
    Jimjimjim (F:) : 38GB (2.1GB, 5% Free Space) (NTFS)
    Bologna_2 (G:) : 3.9GB (UDF)
    CD-ROM/DVD (H:) : N/A
    Bfv_3 (I:) : 486MB (CDFS)
    Doom 3 roe (J:) : 650MB (CDFS)
    Sims2ep1_1 (K:) : 650MB (CDFS)
    Bf2 dvd (L:) : 1.9GB (UDF)
    CD-ROM/DVD (M:) : N/A
    Peripherals
    Serial/Parallel Port(s) : 1 COM / 0 LPT
    USB Controller/Hub : Intel(R) 82801EB USB Universal Host Controller - 24D2
    USB Controller/Hub : Intel(R) 82801EB USB Universal Host Controller - 24D4
    USB Controller/Hub : Intel(R) 82801EB USB Universal Host Controller - 24D7
    USB Controller/Hub : Intel(R) 82801EB USB2 Enhanced Host Controller - 24DD
    USB Controller/Hub : Intel(R) 82801EB USB Universal Host Controller - 24DE
    USB Controller/Hub : USB-rotnav (hub)
    USB Controller/Hub : USB-rotnav (hub)
    USB Controller/Hub : USB-rotnav (hub)
    USB Controller/Hub : USB-rotnav (hub)
    USB Controller/Hub : USB-rotnav (hub)
    USB Controller/Hub : USB-enhet (sammansatt)
    USB Controller/Hub : Stöd för USB-skrivarport
    FireWire/1394 Controller/Hub : OHCI-kompatibel IEEE 1394-värdstyrenhet
    Keyboard : Logitech HID-Compliant Keyboard
    Keyboard : HID-tangentbordsenhet
    Mouse : HID-compliant MX310 Optical Mouse
    Mouse : HID-kompatibel mus
    Mouse : HID-kompatibel mus
    Human Interface : Logitech WingMan Force 3D USB (HID)
    Human Interface : HID-kompatible konsumentkontrollenhet
    Human Interface : HID-kompatibel enhet
    Human Interface : Logitech Virtual Hid Device
    Human Interface : Logitech Virtual Hid Device
    Human Interface : Logitech USB MX310 Optical Mouse
    Human Interface : Logitech WingMan Force 3D USB
    Human Interface : USB HID (Human Interface Device)
    Human Interface : Internet Keys USB
    MultiMedia Device(s)
    Device : Audigy X YouP-PAX A4 v1.00 Audio Driver(WDM)
    Device : Creative Game Port
    Device : Pinnacle PCTV Stereo PAL Capture Device
    Printers and Faxes
    Model : Microsoft Office Document Image Writer
    Model : Canon PIXMA iP4000
    Model : Adobe PDF
    Power Management
    AC Line Status : On-Line
    Operating System(s)
    Windows System : Microsoft Windows XP/2002 Professional (Win32 x86) 5.01.2600 (Service Pack 2)
    Network Services
    Adapter : Intel(R) PRO/1000 MT Desktop Adapter #2

    Thanks for your answers.
    Danny: 1. Yes, I've put my memory in my brothers computer, and ran memtest there, and it came out ok, but on mine it crashes almost instantly.
              2. Yea, I have 2 fans blowing into the case and one out, so airflow is good, cpu is also cool and seems to be happy ;-)
    Geps:  I can't say I understand all these numbers but there are som specs here as an example, Tagan TG480-U01 480W ATX
    I can't imagine that this psu ain't enough, and if so.....I've been had by the dealer. 

  • T540p battery drain in S4 state after Bios and Intel Wifi driver update

    Hey Guys,
    on my T540p, I configured the rapid start technology according to 
    http://download.intel.com/support/motherboards/desktop/sb/rapid_start_technology_user_guide.pdf
    Since I have performed a BIOS update to 2.14  and an update of the Intel Wifi driver to 17.0.5, I experience the problem of battery drain when the computer is in S4 sleep state, at a rate of approximately 0.125% per hour (on the 56Wh battery).
    This was not the case before these updates. There was no noticable power drain in S4 sleep state, even not over multiple days.
    I'm using Win7, I set all the WoL capabilities both in BIOS and in the Intel driver to disabled, according to 
    https://forums.lenovo.com/t5/IdeaPad-Y-U-V-Z-and-P-series/Battery-drain-when-powered-down-Y410P/td-p...
    External device USB charge settings are also fully disabled in BIOS and Power Manager. The problem does not occur when the system is fully shut down, but in S4 Sleep state, which should be a zero-power state too, as it was before the updates. In the details of the BIOS update it is stated " Fixed an issue where the computer might fail to enter sleep state". Could the power drain be a side effect of this fix? Or is it an issue with the (new) Wifi driver, as it was the case for the Y410P?
    How could this battery drain be avoided? Has anybody experienced the same issue?
    Best,
    Martin
    Solved!
    Go to Solution.

    mka1284,
    you could check out devices that might resume laptop from the sleep modes and disable them. Type in the following command in the cmd line window:
    powercfg -devicequery wake_armed
    Also the following command will show you report about power management. Open cmd window with administrative rights and type in:
    powercfg -energy.
    x220 | i5-2520m | Intel ssd 320 series | Gobi 2000 3G GPS | WiFi
    x220 | i5-2520m | hdd 320 | Intel msata ssd 310 series | 3G GPS | WiFi
    Do it well, worse becomes itself
    Русскоязычное Сообщество   English Community   Deutsche Community   Comunidad en Español

  • Error: 0271: Real Time Clock Error - Check Date and Time settings.

    Hello all,
    I have lenovo T430s laptop that is configured with Bitlocker encruptions and TPM PIN entry. I don't think that has anything to do with the error msg I am getting but here it is. Error: 0271: Real Time Clock Error - Check Date and Time settings.
    Press Esc to continue or F1 to enter setup. I am unable to get into BIOS or even the login screen for Windows 7.
    Any advice would be appreciated.

    Thanks to everyone for the help.  Just want to close this out.  I had a IBM/Lenovo technician here today and he replaced the CMOS battery.  Upon the change, the computer is fine being reconnected to the dock (the three times I tried it).  So it has been resolved with the battery.  Surprised by the incompatibility claim because I am not having issues now.  Wondering if it's just a USB 2.0 vs. 3.0 thing (and Lenovo trying to sell more peripherals, of course).
    Thanks!

  • Confusion about UEFI/BIOS and GPT/MBR compatibility issues

    So a user said in another post that they were NOT able to boot in UEFI mode and install Fedora even though it is UEFI compatible.  But this person was able to useLegacy mode and install Fedora, and furthermore, was able to "keep the Windows partition."  I'm guessing that means that Win 8 that came with it, which would be installed in UEFI/GPT mode, correct?  I'm specificly referring to the Y510P but from what I understand *every* laptop that comes preinstalled with Win 8 must be UEFI/GPT.
    So the way I understand it is that the installed Fedora is in "BIOS"/GPT mode rather than "BIOS"/MBR mode because you can't have both GPT and MBR on the same disc.
    I have just started learning about this UEFI/BIOS and MBR/GPT nonsense, and it's going to drive me crazy until I finally understand it. So I guess what I'm asking is:
    1) When I get my y510p I assume it will be in UEFI/GPT mode. Can I install non-UEFI distros alongside it as I take it was done with Fedora?
    2) If I install a linux distro alongside Win 8, do I have to worry about compatibility issues with a drive that is in GPT format? Or does the MBR/GPT issue have nothing to do with it, so I don't have to worry about ever changing my drive to MBR?  
    For example, I read that Win 7 must be installed either as BIOS/MBR or UEFI/GPT.  This can not be mixed and matched.  This means that if I could not get the Windows 7 installer to boot in UEFI I would have to install as MBR.  This also means I would have to format the drive and reinstall Win 8 on the MBR.  
    So my question is do other OS's like Linux have these restrictions?  (For example, if a particular distro will not boot in UEFI and therefor MUST install on MBR)
    3) I have a pendrive with YUMI installed with a ton of distros/tools/Win installs/etc. (It is a USB boot tool like unetbootin that allow you to add multiple bootable images.) When I tried it recently on my dad's laptop.  I have used it many, many times with my older computers, none of which were UEFI.  It works great.  Now that I've had a recent encounter with my dad's ASUS Windows 8 computer (not with the y510p yet) I found out that UEFI seems to be complicating the crap out of things (for me, at least.)
    So when I used this computer, I noticed that when I boot (with legacy mode enabled) and enter the "boot selection screen" in order to boot with USB, I have two options a) UEFI:"name of usb" and b) "name of USB". The UEFI option would NOT boot, but it would boot without the UEFI: option.
    So does this mean that I am booting in non-UEFI mode and once I have booted this way and choose a distro to install that it CANNOT install in UEFI mode?  I recently saw a tool called Rufus that I have yet to try that has an option to set the bootable USB to UEFI, so that would possibly work if I wanted to install a UEFI compatible distro (Arch linux is what I'm wanting.)
    4)  If installing a UEFI compatible distro (such as Arch) requires that the USB device be able to boot in UEFI mode has anyone been able to do this?  Has anyone even been able to boot a device in UEFI mode to do *anything* such as run a live linux?  
    I'm 99% sure I would be able to boot in legacy mode and run a live linux (because I did so on my dad's computer) but the problems arise when I consider how to INSTALL.
    I would really like to know the answers to these questions (as scattered as they are.) Any help would be appreciated!
    Unnecessary info:
    (I started learning about BIOS/UEFI and MBR/GPT the hard way a few days ago by trying for hours to install Windows 7 on my dad's Windows 8 laptop because I could NOT get Win 7 installation to work...it kept asking for drivers before I could install until I finally used the Windows USB install tool, put the stick in a different USB, AND formatted the drive as MBR because Windows 7 would NOT install on the existing GPT drive until I used diskpart.exe -clean. And I have read that Win 7 64 bit will work fine on a UEFI/GPT setup. I used the Windows 7 USB boot tool which did NOT give me a UEFI: and regular option. It showed up simply as "name of usb" without a UEFI in front. Since I read that Windows 7 must either be in BIOS/MBR mode or UEFI/GPT mode that this drive would not boot in UEFI mode, and I don't know why...Although I believe I read that Win 7 cannot be installed from a USB in UEFI/GPT mode, only BIOS/MBR.  UEFI/GPT mode requires a DVD install but I did not have a drive to test this.)

    I have a Y510p which is running dual boot Windows 8.1 and Arch Linux.   I think that it is strongly advised to do plenty of reading ahead of any install if you will be using UEFI and Linux so that you understand all the issued before making critical changes to the existing system.
    Yes, if the machine comes with Windows 8 (as mine did) then the disk will be formatted with a GPT partition table (instead of the old MBR partitioning scheme), and will boot using UEFI. If you are going to try to keep the existing Windows 8 system and add Linux then you will need to keep the disk with its GPT partition table and partition structure, but you can shrink the Windows 8 C: drive to make space for the Linux partitions that are needed ( a root partition and at least a /home and/or /opt partition and possibly a linux swap partition also ).  If you want to boot the Linux install via UEFI then you can simply add the required boot directory to the EFI System Partition (ESP).
    However it is very important that before trying to do any linux install that you switch off Fastboot from within WIndows 8 (or 8.1). Also most Linux distributions are in some difficulty booting using Secure Boot, though a few such a Ubuntu and Fedora are supposed to be able to do so. Hence it is much easier to work with Linux if Secure Boot is first switched off from the BIOS settings menu.
    The order of operations that I used was;
    1) Switch off Secure Boot from the BIOS - and boot back into the Windows 8 system to check that it boots OK.
    2) With Windows 8 running go into the settings and switch off Fastboot (which does a hybrid suspend when it shuts down instead of a full normal shutdown - if you don't do this then the memory gets overwritten when booting Linux in the future which means booting back into Windows will fail). 
    3) Reboot back into WIndows and check all is well, and if so then use the disk management facility within Windows 8 to shrink the C: drive to make room for the Linux partitions.
    4) Reboot to check Windows 8 still boots OK.  
    5) If you are going to update to Windows 8.1 then do so, and then update everything once it is booted (it is a huge update and takes ages!). Once done then you will likely have to update drivers for the graphics cards, the clickpad and possibly the wireless chip and ethernet chip. I found that I needed to get drivers that were newer than were available on the Lenovo website, by going to the relevant hardware manufacturer website (eg for synaptics for the clickpad). Then spent a week or so in the evenings getting Windows 8.1 configured the way I like it.
    6) Then I did a lot of reading about the various options for the boot manager that would suit a UEFI boot for a dual boot system for Windows 8.1 and Arch Linux and there was a choice of Grub, Gummiboot, rEFInd, and others - and after reading the details I decided on rEFInd as my boot manager which can boot not only any new Arch Linux install but automatically finds the Windows UEFI boot files and presents the options in a nice graphical window once the system gets past POST at bootup.
    7) It was important to check which partition was the ESP and to know what partitions I needed to create for the Arch Linux system.  Then I went ahead and booted from a usbkey to a uefi install system, and very carefully proceeded with a standard Arch Linux install, being particularly careful to know where to put the rEFInd boot manager files and the kernel and initrd files. Also I used efibootmgr to write the appropriate NVRAM boot entry in the motherboard memory so that the uefi boot system knows where to find the rEFInd uefi boot files in the ESP.
    8) Once complete the system boots to Arch Linux as the default, with a nice Windows icon which you can select with the arrow keys within the boot timeout period (default 20 seconds).
    I noted also that it is possible to create boot stanzas in the rEFInd boot manager config files which allow rEFInd to chain load other Linux systems or even other bootloaders if you wish - so it is very flexible. So if you want to you could install a grub standalone set of diretories/files so that if the normal linux boot fails then you can select the grub icon from rEFInd and chainload grub to boot either the same Archlinux install, or point to a third linux distribution if you have more partitions containing that third install which might be Ubuntu or Mint or ....
    Either way although getting to understand how uefi boot works is a learning curve it is actually generally simpler than the old legacy BIOS boot. With uefi you no longer need an MBR on the drive, and only a suitable EFI System Partition which has to be VFAT formatted. However if you want to have one of the linux distributions booting from legacy MBR then you need to create an MBR at the start of the drive - so you would need to move the start of the first partition and create a suitable sized Master Boot Record otherwise MBR boot can't work. If you do that then of course you have to be careful if the Windows partition is the one being re-sized that it doesn't mess up the Windows boot! However since using uefi to boot rEFInd allows a chainload to grub/gummiboot or other bootloaders then there should be no need to mess with MBR booting if you go down that route.
    If you are interested in rEFInd then the author Rod Smith has a good set of documentation that describe the details at http://www.rodsbooks.com/refind/
    He is also the author of a really excellent disk partitioner for GPT disks - http://www.rodsbooks.com/gdisk/
    Clearly it is necessary to read up on the boot facilities available for any linux distribution that you plan to put on the system.
    One nice thing is that uefi boot with an efistub supported kernel build is really fast on the Y510p. My system boots Arch linux in about 7 seconds to the KDE login prompt once the POST is complete and that only takes a couple of seconds.  Of course Windows is much slower once it is selected at the rEFInd screen and takes somewherearound 40 seconds or so to boot, but at least Linux is super fast!
    Anyway I hope that this helps.

  • How to enter BIOS and boot menu on Satellite C50-A-1GZ?

    Hi,
    that is, how can I start the BIOS and the boot menu of my Toshiba C50-A-1GZ?
    Thank you

    Hi
    At first you must perform complete shutdown. How to do this you can read on http://aps2.toshiba-tro.de/kb0/TSB2B03EY0002R01.htm
    Restart your notebook and press F12. There you should find setup options for BIOS settings.

  • DKA790GX Platinum and Gigabyte ATI Radeon 4870X2 2GB

    Hi all, was wondering if anyone has had issues with this Gigabyte card in the DKA790GX Platinum. About to purchase but thought I would check here first.
    Thank you in advace.
    Mark
    -MB DKA790GX Platinum
    -Bios version 1.6
    -Cpu - AMD Phenom2 940
    -RAM - Kingstons 2x2G-UDIMM 1066mhz
    -Video - Gigabyte ATI Radeon 4870X2 2GB
    -Power - Antec Signature 650 +5V 0A 24.0A ±3％ 50 50
    +12V1 0A 22.0A ±3％ 120 120
    +12V2 0A 22.0A ±3％ 120 120
    +12V3 0A 25.0A ±3％ 120 120
    -12V 0A 0.5A ±7％ 120 120
    +5VSB 0A 3.0A ±3％ 50 50
    +3.3V 0A 24.0A ±3％ 50 50
    +3.3V, +5V max. load: 140W +12V1, 12V2, 12V3 max. load: 43A
    +5V, +12V1, +12V2, +12V3 & +3.3V
    -Hard Drives: Western Digital 320gb SATA Raid 0
    -Windows XP Pro 64bit SP2.

    I have a gigabyte hd 4870x2 in my dka790gx platinum and it works, just having other problems with getting the board to work with 4gb or more

  • [Solved] Unbootable USB with both BIOS and UEFI setup

    I'm installing Arch to a USB flash drive to be bootable across a wide-range of computers (like the Arch ISO for USB) - both with legacy BIOS and with UEFI support (32bit instead of 64bit for greatest compatibility). I've installed Arch successfully and everything with it works fine.
    To get the flash drive to bootup on legacy BIOS systems, I've installed Grub. This went without a hitch and this boots up on every legacy BIOS machine I've tried.
    However, I cannot for the life of me get UEFI working. I only have one UEFI-enabled machine to test on. I've tied settings up both Gummiboot and Grub for UEFI support and they both seem to get to the same place. I get their boot entries to show up in the UEFI's boot up menu, but it boots the UEFI installation already present on the system (another Arch installation). If I remove the UEFI entry for the Arch installation on the machine, it lists the flash drive in the boot-up menu but clicking on it tells me that there were no bootable mediums found. So I'm guessing there is a configuration error somewhere.
    The Arch ISO disk boots up successfully over UEFI on the machine without a hitch. SafeBoot is disabled on the UEFI machine machine. The UEFI machine has a working UEFI Arch installation by Grub2 which works fine - I setup the flash drive pretty much the same was as detailed below but it doesn't work.
    Here is my setup:
    Disk /dev/sda: 57.9 GiB, 62176362496 bytes, 121438208 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 7AF2949B-01DA-4A5D-96B5-C716601BF56B
    Device        Start       End   Sectors  Size Type
    /dev/sda1      2048  10487807  10485760    5G EFI System
    /dev/sda2  10487808  10489855      2048    1M BIOS boot
    /dev/sda3  10489856 121438174 110948319 52.9G Linux filesystem
    It is a GPT formatted flash drive, with an EFI partition, a BIOS Boot partition (for Grub) and finally a LUKS encrypted file system. (I have also tried the system without LUKS and I still get the same results as above).
    ESP partition with Gummiboot (/boot): (ls -LR /boot)
    EFI  grub  initramfs-linux-fallback.img  initramfs-linux.img  intel-ucode.img  loader  vmlinuz-linux
    ./EFI:
    Boot  gummiboot
    ./EFI/Boot:
    BOOTIA32.EFI BOOTX64.efi
    ./EFI/gummiboot:
    gummibootia32.efi
    ./loader:
    entries  loader.conf
    ./loader/entries:
    arch.conf
    (with BOOTIA32.EFI copied to BOOTX64.EFI so UEFI would recognize the flash drive.)
    ESP partition with Grub (/boot): (ls -LR /boot)
    EFI  grub  initramfs-linux-fallback.img  initramfs-linux.img  intel-ucode.img  loader  vmlinuz-linux
    ./EFI:
    Boot  gummiboot
    ./EFI/boot:
    bootx64.efi
    ./EFI/grub:
    grubia32.efi
    grub.efi
    I've tried copying both grub.efi to bootx64.efi and grubia32.efi to bootx64.efi. Both seem to be the same file.
    BLKID
    /dev/sda1: UUID="E3BA-7D68" TYPE="vfat" PARTLABEL="EFI System" PARTUUID="d3619522-56c7-4a18-9997-3a9649809506"
    /dev/sda2: PARTLABEL="BIOS boot partition" PARTUUID="40132eb6-2994-44b8-a6c4-8380fbd45a98"
    /dev/sda3: UUID="a7392099-0853-4b03-a1e9-82e298eaab95" TYPE="crypto_LUKS" PARTLABEL="Linux filesystem" PARTUUID="300f4171-f1b5-4407-beee-060ae8fb8dee"
    /dev/mapper/Root: LABEL="Root" UUID="679ba330-de69-4805-ba12-59d479ea12fc" TYPE="ext4"
    fstab (using default mount options from fstab generator)
    # /etc/fstab: static file system information
    # <file system>    <dir>    <type>    <options>    <dump>    <pass>
    # /dev/mapper/Root LABEL=Root
    UUID=679ba330-de69-4805-ba12-59d479ea12fc    /             ext4          defaults,relatime    0 1
    # /dev/sda1
    UUID=E3BA-7D68          /boot         vfat          rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro    0 2
    Grub for legacy BIOS was setup with the commands:
    grub-install --target=i386-pc --recheck --debug /dev/sda
    grub-mkconfig -o /boot/grub/grub.cfg
    Grub configuration from /boot/grub/grub.cfg
    GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=UUID=a7392099-0853-4b03-a1e9-82e298eaab95:Root"
    I've tried both Gummiboot and Grub2 (not at the same time) alongside Grub for the legacy BIOS bootup. BIOS bootup works fine.
    UEFI configuration with Gummiboot:
    gummiboot --path=/boot install
    /boot/loader/loader.conf
    default  arch
    timeout  4
    /boot/loader/entries/arch.conf
    title    Arch Linux
    linux    /vmlinuz-linux
    initrd    /initramfs-linux.img
    options cryptdevice=PARTUUID=300f4171-f1b5-4407-beee-060ae8fb8dee:Root root=UUID=679ba330-de69-4805-ba12-59d479ea12fc ro
    UEFI Configuration with GRUB2:
    grub-install --target=i386-efi --efi-directory=/boot --bootloader-id=grub --recheck
    grub-mkconfig -o /boot/grub/grub.cfg
    mkdir /boot/EFI/boot
    cp /boot/EFI/grub/grubia32.efi  /boot/EFI/boot/bootx64.efi
    I have to copy grubia32.efi to bootx64.efi so my UEFI system detects the flash drive.
    I have done all of these steps on a BIOS machine, and a UEFI machine, both with the same results. The machine recognizes the flash drive in the bootup menu and lists it as an option to boot from, but it tells me no bootable device was found. I don't care which method I need to use to get the flash drive to bootup over UEFI, gummiboot or Grub, I'm just trying to get it to work.
    Last edited by awbs (2015-05-17 18:25:19)

    It sounds like you are on the right track.  I got it to work using a similar method.  Here is my setup: 16GB USB 2.0 Corsair Voyager.
    gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 1.0.0
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sdb: 31950720 sectors, 15.2 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): 0C83EC1E-9109-4E1E-9EB8-01373E2339D4
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 31950686
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2014 sectors (1007.0 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 206847 100.0 MiB EF02 BIOS boot partition
    2 206848 616447 200.0 MiB EF00 EFI System
    3 616448 31950686 14.9 GiB 8300 Linux filesystem
    As you can see, I made 3 partitions on a GPT labeled USB stick.  You need to format the EF00 and 8300 partitions:
    mkfs.vfat -F32 /dev/sdb2
    mke2fs -t ext4 -L isofiles /dev/sdb3
    "isofiles" is the label I used for the ext4 partition.  You can change this.  Now install Grub for EFI on the ESP partition:
    mount /dev/sdb2 /mnt
    mkdir -p /mnt/boot
    grub-install --target x86_64-efi --efi-directory /mnt --boot-directory /mnt/boot --removable
    Place your grub.cfg file in /mnt/EFI/BOOT.
    Install GRUB for legacy BIOS on the bios_boot partition:
    umount /mnt
    mount /dev/sdb3 /mnt
    mkdir -p /mnt/boot
    grub-install --no-floppy --target i386-pc --boot-directory /mnt/boot /dev/sdb
    Place your grub.cfg file in /mnt/boot/grub.  On some systems, it is /mnt/boot/grub2.
    Copy all of your ISO files, e.g., arch, gparted, clonzilla, etc, to the ext4 partition.  you will need the UUID of the ext4 partition:
    blkid /dev/sdb3
    This is because we are using a UUID search method to find the ISO's before loop mounting them. You can obtain the grub menu entries for various distros here.  I used the following grub.cfg to boot arch and gparted in EFI mode:
    set default="0"
    function load_video {
    insmod efi_gop
    insmod efi_uga
    insmod video_bochs
    insmod video_fb
    insmod video_cirrus
    insmod all_video
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_gpt
    insmod ext2
    set timeout=10
    submenu 'GParted -->' {
    set default="1"
    set isofile='/gparted-live-0.22.0-1-amd64.iso'
    menuentry 'GParted -- default settings' --class gparted --class gnu-linux --class os {
    search --no-floppy --fs-uuid --set=root THIS_IS_YOUR_UUID
    loopback loop $isofile
    set root=loop
    linuxefi /live/vmlinuz boot=live username=user config components quiet noswap noeject ip= nosplash findiso=$isofile
    initrdefi /live/initrd.img
    submenu 'Arch Linux -->' {
    menuentry 'Install Arch Linux' --class arch --class gnu-linux --class os {
    set isofile='/archlinux-2015.04.01-dual.iso'
    search --no-floppy --fs-uuid --set=root YOUR_UUID
    loopback loop $isofile
    set root=loop
    linuxefi /arch/boot/x86_64/vmlinuz archisolabel=ARCH_201504 img_label=isofiles img_loop=$isofile earlymodules=loop
    initrdefi /arch/boot/x86_64/archiso.img
    The legacy grub.cfg file is identical to the above, except that you use "linux" and "initrd" instead of "linuxefi" and "intrdefi".   Note that unfortunately you have to use two grub.cfg file, one for UEFI and the other for legacy placed in the locations described above.  However, they are very similar.
    When you boot the machine, if it is an ASUS board, let's assume, press F8 during POST.  You should see "Corsair - UEFI" and "Corsair".  They should both work.  Good Luck.

  • Updated Bios and hibernation

    Hi, I have a  K8T Neo that was working just fine for me until I Live Updated the Bios.  Basically, the case I have has a big honking obnoxious case light that hooks up using a HD power connector.  So the thing never turns off unless the power supply is off, and this isn't conducive to sleeping.  Putting the system in stand by has never been an option because the lights stay on.  But I used to be able to put it into hibernation and everything would be great.
    Verizon finally comes along and hooks up my DSL so I decide to update my bios so that to see if a bios update will make my expensive CAS 2 memory actually run at CAS 2 without windows crashing.  Well, the good news is the update worked in that respect.  But my computer will no longer hibernate.  When i try to put it into hibernation it seems to go in to the old standby mode.  Meaning the fans keep running, the lights stay on, and I don't sleep....  However, to top things off, there is now no way to wake the computer up from standby or hibernation.  It will not respond to the keyboard, USB mouse, or the power button.
    I've tried fiddling with every power management bios setting I could think of.  I just can't make it work.
    Has anyone else experience the same problem?

    The symptoms / problems probably change when BIOS updates happen
    since the BIOS update causes all BIOS / CMOS / NVRAM settings  to pretty much
    reset to the new BIOS's default values, and these may differ from what you had
    selected before.
    I've just updated to 1.92B BIOS for my MS-6702-020 / K8T NEO FSR and that
    plus the AMD CPU Driver makes Cool & Quiet work, but "S3/STR" standby mode
    always crashes W2K SP4 when the Wake-Up is  initiated.
    I know that having add in cards that have drivers and hardware that support
    being put to sleep and being woken up are critical for success in general, but
    in my case I have only one add in card, and it's a pretty new design AGP 3.0
    PCI 2.3 ATI RADEON 9800 PRO with new drivers, so I'd assume it can properly
    support sleep / wake up.
    I'd suggest you go to
    http://windowsupdate.microsoft.com/
    and apply all available updates, reboot, go back there, check to see if there
    are any new upapplied ones, and keep doing that until it shows you're totally
    up to date.   If you run XP, be sure you have SP2 installed and all the other
    updates too.
    Go to the OEM home page of all your add in card vendors like your  video card,
    sound card,  whatever you have and get / install the latest compatible driver for
    your OS -- that may help your suspend mode and long term stability.
    I'll update my posts if I discover any other helpful information or diagnostic clues.
    EDITED -- I just discovered that one has to set the
    "Allow this device to wake the system from standby" check box for the
    mouse & keyboard and other devices e.g. USB ones or maybe others in
    W2K Control Panel -> Device Manager -> select the particular keyboard/mouse/etc
    device -> then the "Power Management" tab, then check the
    "Allow this device to wake up the system" optiion.
    One ALSO has to set the "WAKE UP EVENTS" and "WAKE ON USB" settiings
    in the Power Management  BIOS configuration screen.
    Once I did that USB keyboard / mouse wake up from  S1/POS standby or
    S3/STR standby worked for me where it did not work before.
    (though S3/STR still crashes upon the wake up for me).
    Maybe that'll help the original poster also since s/he mentioned a similar
    failure to generate a standby wake-up.
    Re: "hijacking" -- not at all, I'm trying to provide answers or feedback
    relating specifically to the "standby / suspend / wake up" and
    "when I upgraded my BIOS things changed" issues  the original poster mentioned.
    As for hibernate vs. suspend, I have no idea why THAT changed for the original
    poster, and I can't comment on getting hibernate mode working for them, so
    I confined my reply to the other issues that I do have experience with
    (suspend / wake up / bios options clearing when you upgrade BIOS).
    I understand they prefer to hibernate vs. suspend, but the fact is the
    majority of problems they mentioned ARE suspend/standby/wake up ones!

  • [P67-GD65 B3] Safe way to flash 4.2 official bios and why.

    Hi all!
    I am still trying to remedy my problem with too high (~1.43V) voltage while 4.5GHz OC (turbo or not) with "vdroop low" enabled. Now I am on 4.39 and it`s ok on (non turbo/manual x42) 4.2GHz and auto voltage (it`s ~1.288V while Prime, etc). I know that 4.20 official bios gives % vdroop settings. I want to try it to avoid my problem but I can not find 4.20 package ready to go with MSIHQ flasher. Actually all 4.xx MSIHQ versions go from 4.3x.
    I am wondering if it is possible just to compress "valcheck.com" with 4.20 official bios file and throw it via Mode 1 to MSIHQ(?)
    BTW: Maybe it (flashing 4.20) does not make any sense because "%" vdroop on 4.20 will not give me anything higher then "Auto" voltage settings. I think I need ~1,38V to get stable 4.5GHz. Any other ideas?
    I could try manual voltage for CPU but I want to stay with energy saving c-states. I am using C1E with my non turbo OC.
    I know You can find my problem a bit boring  but maybe forum's Gurus could give me a green or red light(?)

    Just to report!
    Yesterday I finally tried to down-flash from 4.39 to 4.20 with MSIHQ. Risk taken  Happily it was success!
    But boy ... I should read carefully comments about 4.20 bios (grammar lost). I did not know that on this bios 100% vdroop is not ... How to say it? It is not 100% of "vdroop low" but rather 100% of "vdroop auto". So it not helped me with my main problem. I am now back to 4.39 beta bios.
    BTW1: After some tests, I found that while on CPU voltage on "Auto" my CPU max voltage is ~1,29V (never more, it stabilize more or less from x40 multi CPU) while stress testing. Switching to "Low vdroop" I get above 1.4V just from x40 multi. Something is not right. It goes up with higher multi.
    I tried to workaround this by Control Center. Switched to lower multi in bios, switched vdroop to "low" (voltage was OK and below the 1,4V line while stress testing) and then bump up multi in CC. Guess what ... Voltage was also bumped to the same (too high) values.
    BTW2: I started to think that above problem may be my fault. From start with my P67-GD65 I experimented with OC Genie and maybe I switched some values or even reseted CMOS while using OC Genie (I know that was warning about it). I don't know, but maybe it damaged something and my motherboard behaves like this for good :/
    I think that it is the end of my experiments. Bios 4.20 (% vdroop) was my last resort, but it failed.
    Big thanks for all that tried to help me . It started 07-April-12:
    https://forum-en.msi.com/index.php?topic=158139.msg1161554#msg1161554
    I have to stay on x42 with ~1.288 voltage or go above x45 with more than 1.43V.

  • Errors in ThinkPad Bios and Thinkvantage Software

    I have been using my ThinkPad T61 model 7664-A24 for almost 6 months now and have noticed quite a few errors in the bios and Thinkvantage software.
    1. Bios:
    Security>Passwords>Passphrase is grayed out and has no functionality.
    2. Bios:
    Security>Passwords>Password Reset Service: The instructions in the description window to the right tell us to go to 'Create Recovery Media' in Windows>ThinkVantage and set up password reset service to recover power-on or hard disk password in case of loss. However there is no such thing in Thinkvantage>Create Recovery Media.
    3. Predesktop Rescue and Recovery workspace:
    The documentation when you click 'Configuration Overview'  relating to setting up a password to protect the Rescue and Recovery predesktop environment is wrong - Method 1 and Method 3 of creating this password in Client Security Solution and Rescue and Recovery respectively do not exist.
    While these errors do not impede the functionality the ThinkPad, I wish Lenovo would tighten up the screws. I can't understand how such a big company could be so sloppy. The bios should not have any dependency on external software but here some bios functions are dependent on RnR in Windows? I've tried removing the RnR and CSS program but the bios 'Password Reset Service' option remains. I hope Lenovo issues updates to fix these errors.
    I will mention more errors in the lenovo software in this thread as I find them.
    Message Edited by zachareth on 05-05-2009 12:24 AM

    Hi Naresh,
    Please double check if your Network Connection settings in Eclipse Preferences are correct. See SAP HANA Cloud Platform for more detailed info.
    HTH!
    --Vlado

  • MSI 850E Max2 aka MS-6592 and Vcore Settings

    Can anybody in here please tell me, what Vcore settings are possible with this mainboard. (manual said nothing)
    but i'm just interested in vcore settings below default - > menas 1.5V and lower.
    So, if it's possible to undervolt the CPU, then please tell my how low you can get and how you did you do that. (BIOS and/or FuzzyLogic)
    thanks in advance

    you can buy one at this site
    http://www.isaacsystems.com/products/components/view2.asp?offset=10&type=Motherboards&code=Socket%20478%20(Pentium%20IV)
    in usa too

  • GT60-one mod bios and EC

    Hi Svet,
    I have just donated and would like the the following:
    System BIOS Version: E16F3IMS.51X (Unlock)
    EC Version: E16F3EMS1 VerT.19
    or whatever you think is best....
    I have a GT60-one (ivy bridge and gtx 680m).
    Current bios and EC is
    Bios: E16F3IMS.50X
    EC  16F3EMS1 ver 5.05
    I am planning on doing the vid card upgrade described here...
    http://forum.notebookreview.com/threads/the-official-msi-gt60-70-970m-980m-upgrade-thread.765058/
    Same thing that Superguy mentioned in his post to you a few weeks ago:
    https://forum-en.msi.com/index.php?topic=252575.0
    thx,
    Paul

    well done
    Quote
    Last question.... is there a recommended windows overclocking too that can let me set some of the critical things within windows instead of going through the 2000 settings in bios?
    don't know, XTU perhaps

Maybe you are looking for