Announcement

Collapse
No announcement yet.

Fedora 19 Alpha Gets Its First Delay Due To UEFI

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Fedora 19 Alpha Gets Its First Delay Due To UEFI

    Phoronix: Fedora 19 Alpha Gets Its First Delay Due To UEFI

    After a badly-delayed Fedora 18, Fedora 19 has already received its first release set-back...

    http://www.phoronix.com/vr.php?view=MTM0OTg

  • #2
    UEFI sucks

    UEFi is terrible, it should been replaced by coreboot.
    Coreboot is sane, UEFI is not.
    Viva la coreboot!

    Comment


    • #3
      and so it begins...


      f19 is going to be another fail like f18... I bet 20e that the alpha will be delayed again in a weeks time

      Comment


      • #4
        Originally posted by maksml View Post
        UEFi is terrible, it should been replaced by coreboot.
        Actually the more realistic approach is using coreboot for hardware initialization and UEFI on top of it. Google has worked towards this goal. It might be unfortunate but in not so distant future all x86 and ARM (at least AArch64 (64bit ARM)) devices will use UEFI.

        Comment


        • #5
          Originally posted by Pallidus View Post
          and so it begins...


          f19 is going to be another fail like f18... I bet 20e that the alpha will be delayed again in a weeks time
          I hope it won't ;-) Alpha is pretty solid (for Alpha), except the UEFI bug. We even had possible workarounds (at least for the Grub2 one). But as UEFI is more wide spread, the impact could be bigger than before and especially the kernel bug could lead to really very broken system.

          And yes, the main reason why we said No-Go was - we don't want to loose our reputation of slipping!!!

          Comment


          • #6
            Who the hell decided UEFI problems get to block anything?! Currently its of tertiary significance. UEFI systems are in minority and the function can be disabled anyway. Correct me if I'm wrong.

            That's why I desperately need a way to install Gnome Shell 3.8 on Fedora 18! Please drop me a link if you you've stumbled upon a set of complete instructions please drop me a link.

            Comment


            • #7
              Originally posted by Bucic View Post
              Who the hell decided UEFI problems get to block anything?! Currently its of tertiary significance. UEFI systems are in minority and the function can be disabled anyway. Correct me if I'm wrong.

              That's why I desperately need a way to install Gnome Shell 3.8 on Fedora 18! Please drop me a link if you you've stumbled upon a set of complete instructions please drop me a link.
              Bull-freaking-shit.

              Any notebook or desktop motherboard bought after 2008 is loaded with UEFI and not BIOS.

              Comment


              • #8
                Originally posted by Sonadow View Post
                Bull-freaking-shit.

                Any notebook or desktop motherboard bought after 2008 is loaded with UEFI and not BIOS.
                Which one of my claims does this negate?

                Comment


                • #9
                  ;

                  Originally posted by Bucic View Post
                  Which one of my claims does this negate?
                  You can't disable uefi, at best you can enable BIOS emulation on top of it.

                  Comment


                  • #10
                    Originally posted by AJenbo View Post
                    You can't disable uefi, at best you can enable BIOS emulation on top of it.
                    I confused UEFI with the Secure Boot. Does the bug in question affect UEFI as a whole or just the SB?

                    Comment


                    • #11
                      Originally posted by Bucic View Post
                      I confused UEFI with the Secure Boot. Does the bug in question affect UEFI as a whole or just the SB?
                      UEFI as a whole.

                      https://bugzilla.redhat.com/show_bug.cgi?id=949761

                      Comment


                      • #12
                        Originally posted by Bucic View Post
                        Who the hell decided UEFI problems get to block anything?! Currently its of tertiary significance. UEFI systems are in minority and the function can be disabled anyway. Correct me if I'm wrong.

                        That's why I desperately need a way to install Gnome Shell 3.8 on Fedora 18! Please drop me a link if you you've stumbled upon a set of complete instructions please drop me a link.
                        While recent motherboards have a BIOS mode (I'm booting in BIOS mode from a mobo that uses UEFI right now), you can only dual-boot Windows and Linux if they both use the same booting system (e.g. cannot boot UEFI Windows and BIOS Linux). I don't dual-boot, but some people do.

                        Comment


                        • #13
                          Originally posted by directhex View Post
                          Thanks. I wish they would just stick to the schedule and just place such issues in the 'known issues' section of release notes.

                          Comment


                          • #14
                            Originally posted by Sonadow View Post
                            Bull-freaking-shit.

                            Any notebook or desktop motherboard bought after 2008 is loaded with UEFI and not BIOS.
                            That's nice.
                            I have a brand new purchased only a few days ago Gigabyte GA-990FXA-UD3 in my workstation here at work. I'm running a pre-release version of Fedora 19. I told the bios NO FUCKING UEFI CRAP, and passed "noefi" to the installer's kernel. Worked perfect, and no UEFI crap.

                            I think the big problem that exists, is the approach that Fedora seems to take on this UEFI crap. There are actually two bootloaders on the installer disk, one's UEFI and launched by UEFI crap, the other's syslinux, and launched by normal boot process. Even if the bios is in UEFI mode, it would still happily launch the syslinux bootloader on the CD, but only if the UEFI crap... WAS NOT THERE. In other words, stick to syslinux, scan the INSTALL DISK for UEFI crap, and then decide if UEFI should be used. I.e., UEFI should ONLY be used if the user already has UEFI crap on the disk, which implies that they are dual booting with something evil. If there's no UEFI crap on the disk, take over the disk and *do it right*.

                            Comment


                            • #15
                              Originally posted by Calinou View Post
                              While recent motherboards have a BIOS mode (I'm booting in BIOS mode from a mobo that uses UEFI right now), you can only dual-boot Windows and Linux if they both use the same booting system (e.g. cannot boot UEFI Windows and BIOS Linux). I don't dual-boot, but some people do.
                              I can't think of a single reason why anyone would want to do this. If they must have ballmer's donkey for any use, run it (an older version is less evil than a newer version), in a virtual machine under Linux. There is NO EXCUSE for letting the donkey have access to the metal.

                              Comment

                              Working...
                              X