Bios csm just noticed

Forumite Members General Topics Tech PC Talk Bios csm just noticed

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #68011
    keith with the teefkeith with the teef
    Participant
      @thinktank
      Forumite Points: 0

      So a while back I tried to install w10 to pure eufi. But it would not do it. Basically it was because of the limitation of said bios.

      On my new bios CSM is not supported. Strangely enough on bios update w10 just reconfigured its self eufi along with the usual tick box setting windows screens.

      I am reasonably sure the reason why the new bios does not support CSM is because new gfx card functions.

      #68014
      Wheels-Of-FireWheels-Of-Fire
      Participant
        @grahamdearsley
        Forumite Points: 4

        W10 now requires your system to support the UEFI v2.3 framework  or it will only attempt to install in CSM mode.

        I don’t see why your gfx card would affect CSM unless it no longer included the VGA BIOS option rom code and I haven’t seen one that doesn’t yet.

        Maybe your new UEFI has just decided to drop CSM support, after all it is only required for installing a non UEFI aware OS like DOS.

        #68016
        Dave RiceDave Rice
        Participant
          @ricedg
          Forumite Points: 7

          I’ve had a couple of PCs in from that time when we were changing over and compatibility mode was what it was all about. All your bootable software tools still relied on MBR, apps like Rufus didn’t exist yet etc.

          One of them had a Gigabyte motherboard with a dodgy ram slot, but an i5-2400 and HD5570. The other had a Biostar board and a Celeron, a real “value” build but had lasted nearly 8 years doing all it’s owner needed before running out of grunt and viable sectors on the HDD.

          I had a 120GB SSD knocking about, could get ram up to 6GB and one of the 500GB spinners passed all it’s diagnostics so I had enough hardware to do something worthwhile, especially when a check on benchmarks showed the i5 comparable to a Ryzen 3 3200G.

          Nightmare trying work out what the hell I did to make things boot back in the day. In the end I converted all drives to GPT, turned off any CSM and turned on Secure Boot. Sanity restored and W10 installed in what seemed like an age. Of course it wasn’t really that slow but I’ve got used used to NVMe drives and USB3 sticks. W10 didn’t barf at the age of anything and it’s still a very usable “office” machine. The PSU is a Coolermaster 500 watt which must have been bundled with the case as it’s well OTT, so I’m hoping for many more years out of it.

          #68019
          keith with the teefkeith with the teef
          Participant
            @thinktank
            Forumite Points: 0

            So, yeah, the bios function that does not support CSM in the gfx settings is the re size bar. Its a new AMD feature for the mo, NVIDIA will catch on later.

            #68020
            keith with the teefkeith with the teef
            Participant
              @thinktank
              Forumite Points: 0

              Better appraisal here. My new bios 7A38v9C2(Beta version)

              Smart Acces memory
              A recent ability that AMD made available and a trick that is now passing onwards to intel and NVIDIA as well is SAM. Smart Access memory is able to boost your framerates a bit further, sometimes significantly, sometimes a little, sometimes not at all. SAM requires that CSM Support is turned off in the BIOS in order to enable the above 4G Decode, which will allow Resizable Bar Support (SAM) to be enabled. The problem here is that if your Windows installation is configured as non-UEFI, Windows will be unable to boot from your currently installed SSD/HDD. Most PCs will be configured like that. The only solution is to disable CSM and reinstall Windows 10 to get this feature-set supported or perform some really advanced trickery.

               

              #68022
              Wheels-Of-FireWheels-Of-Fire
              Participant
                @grahamdearsley
                Forumite Points: 4

                My system is getting on a bit and it only has UEFI v2.0 framework. W7 installed in UEFI mode just fine but W10 would not. I searched for a reason for days, off and on, and finally found the bit about W10 requiring v2.3

                The main reason for needing v2.3 is W10’s system and device firmware update module, this requires the UEFI firmware query and update functions which didn’t exist before v2.3

              Viewing 6 posts - 1 through 6 (of 6 total)
              • You must be logged in to reply to this topic.