Arch Linux

gbcbooks

Member

Registered: 2014-12-03

Posts: 25

do we need to install various of drivers under EFI

why do we need to install various of drivers when we choose EFI instead of legacy.
i read many artical today , they all said EFI provide unifiled hardware interface to Operation System , so OS doesn't need to worry who they need to talk to to order those hardwares except EFI API. and in the end of the artical said  , drivers can be installed on EFI partition.

so why this example "Does my Graphics card are supported by Linux " is stilling happening.

hardware vendor should provide their EFI driver and User will not care if the hardware will be supported under what kind of OS they choose to install on the computer before they make their decisions.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: do we need to install various of drivers under EFI

You really need to post in the Other Languages forum in your native language: your post is impossible to understand.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

katsuki

Member

From: NY, USA

Registered: 2015-01-28

Posts: 26

Re: do we need to install various of drivers under EFI

UEFI is not an interface for utilizing hardware; the operating system still needs to know how to talk to your hardware (such as the video card).

In fact, EFI can complicate things with third party video drivers; I used to have a Gentoo desktop that used the nvidia closed source drivers and I remember having to play with various kernel params to get it to play nice with the EFI frame buffer of the console.

From uefi.org:

Today, UEFI implementation enables the ability for modern, high-level programming principals to be applied to the firmware space. There are many possible implementations of UEFI that encourage code reuse, modularization, flexibility and modernization. UEFI specifications contain interfaces that streamline and aid in firmware innovation by promoting interoperability between devices, software and systems. One typical implementation is done in high-level C programming language, which is fundamentally different than the Legacy BIOS by encouraging the use of modern software practices.