SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Well, probably I did not state my question clearly. The title of this thread is "Slackware on UEFI," and I imagine things have changed at least a little since the thread was first started, so my question is similar to the initial post: how compatible are Slackware 14.1, UEFI and Win 8 on the latest hardware?
On the Slackware side few things if any have changed. What matters is the specific UEFI firmware of your machine I think, as the implementation of the UEFI standard vary upon machines.
Well that's interesting: a standard that is not standardized. And people wonder why some of us can't stand Microsoft.
At least there is a specification for UEFI, so the situation is better than with BIOSes.
Also,
The writers of the specification can't bear the responsibility of the way it is interpreted by firmware designers.
The writers of the specification are not responsible of the exact version to which each firmware is compliant (or even worse a mix of versions, as seems to be the case for some implementations by Apple).
The specification has to leave some freedom for some implementation's details. What freedom is left can be inferred in reading the specification, and sometimes is clearly stated in it.
Microsoft alone can't bear responsibility for the specification of which it is not the sole writer, and the parts that have a Microsoft legacy (e.g. the format of the PE/COFF images) themselves benefit of a written specification.
PS Sorry to be a bit pedantic but a specification is not exactly a standard, as the latter should be released by some normative body, as e.g. ISO.
Last edited by Didier Spaier; 10-10-2014 at 08:55 AM.
Reason: Wording changed.
Well, probably I did not state my question clearly. The title of this thread is "Slackware on UEFI," and I imagine things have changed at least a little since the thread was first started, so my question is similar to the initial post: how compatible are Slackware 14.1, UEFI and Win 8 on the latest hardware?
I do like to suggest the following links for user that have issues when composing posts;
Quote:
FYI: Netiquette is a set of social conventions that facilitate interaction over networks, ranging from Usenet and mailing lists to blogs and forums.
FYI: I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem or query.
Two memorable quotes;
Quote:
"Knowledge is of two kinds. We Know a subject ourselves, or we know where we can find information upon it."- Samuel Johnson
"It is one of the most beautiful compensations in life…that no man can sincerely try to help another without helping himself." - Ralph Waldo Emerson
At least there is a specification for UEFI, so the situation is better than with BIOSes.
Also,
The writers of the specification can't bear the responsibility of the way it is interpreted by firmware designers.
The writers of the specification are not responsible of the exact version to which each firmware is compliant (or even worse a mix of versions, as seems to be the case for some implementations by Apple).
The specification has to leave some freedom for some implementation's details. What freedom is left can be inferred in reading the standard, and sometimes is clearly stated in it.
Microsoft alone can't bear responsibility for the specification of which it is not the sole writer, and the parts that have a Microsoft legacy (e.g. the format of the PE/COFF images) themselves benefit of a written standard.
PS Sorry to be a bit pedantic but a specification is not exactly a standard, as the latter should be released by some normative body, as e.g. ISO.
(pronounced as an initialism U-E-F-I or like "unify" without the n)[a] is a specification that defines a software interface between an operating system and platform firmware. UEFI is meant to replace the Basic Input/Output System (BIOS) firmware interface, originally present in all IBM PC-compatiblepersonal computers.[2][3] In practice, most UEFI firmware images provide legacy support for BIOS services. UEFI can support remote diagnostics and repair of computers, even without another operating system.[4] The original EFI (Extensible Firmware Interface) specification was developed by Intel. Some of its practices and data formats mirror ones from Windows.[5][6] In 2005, UEFI deprecated EFI 1.10 (final release of EFI). The UEFI specification is managed by the Unified EFI Forum
Intel did originate 'EFI' along with other members, not just Microsoft.
2.4. Where to find more information ... Ubuntu uses the Intel AML compiler. ... are expecting that most OEM machines will ship with a firmware that complies with version 2.3.1 of the UEFIstandard. 9.1. Legacy BIOS compatibility
The above pertains to Ubuntu but does provide good references within that can provide some insight. Be sure to look at the References table links;
You can look at: UEFI documents for additional information. Documentation for 'UEFI & BIOS' can be provided by Motherboard vendors, you can do a site search on vendor web site.
Well, probably I did not state my question clearly. The title of this thread is "Slackware on UEFI," and I imagine things have changed at least a little since the thread was first started, so my question is similar to the initial post: how compatible are Slackware 14.1, UEFI and Win 8 on the latest hardware?
Thanks dugan, I read the thread you linked, and some of the other stuff linked there. You seem to think it was easy to set up by following the Slackware UEFI readme, but a lot of other people seem to have had trouble with it, which still makes me hesitant. I'll have to do some more reading and pondering before I'm ready to commit money to new hardware.
As much as UEFI is standardized, mobo manufacturers still differ in their implementation much like BIOSes. In general it will work just fine. Some implementations are easier to work with, others harder.
As for stories about "bad" motherboard firmware, the worst problem I've heard of is that the boot menu would be built properly, but the default would stay at Windows, forcing you to press F-something to get into Linux on each boot. I personally wouldn't consider that a dealbreaker.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.