If those want to enter the lines afterwards, so everyone as far as possible to the middle, please
Thank you. And right side as well, please get to the middle.
Thank you. Thanks a lot.
Testing.
Okay, we'll be starting as soon as there's enough leeway for the sound in the room, so.
Hello. So, yeah, as was introduced, my name is Leo Roe. I'm here to talk about my projects
Lieberboots. I assume most of you here know what it is, but it's a free corporate distribution
by a slash UEFI firm on replacement. I will also have somewhat of a detour in this talk and
talk about one of my other projects, canoe boots. So, yeah, first of all, who am I, so I've been,
I started the Lieberboot project in December 2013. I started another project called canoe boots
in 2023. I will also be talking about that at some point in this talk. I've been using free software
the next since 2005. I've been an avid supporter of it ever since. I'm also involved quite heavily
in politics. I've been advised by our friends that it's probably not good to be part of a talk.
So, let's just say I'm a digital slash human rights activist. How that translates into free
software. Well, you know, the thing to realize about free software is it's not just for computer
geeks. When you think about it, the way society works, we live in a computer age. We use computers
for everything nowadays. Everyone needs an internet connection. Everyone's got, everyone's got in
their pockets nowadays. What would have been regarded as a supercomputer 50 years ago. So,
everything that you do into in civil society depends on access to computing, access to information,
and how you're computing functions should be, the whole idea with free software is,
you have the freedom to run the software however you want, you can modify it however you want,
you can study it, you can share it. In the context of politics and society in general,
that translates essentially into democracy. If all of the services that you use in everyday life
are proprietary, meaning you don't have control over your technology, then it can be argued
that you don't necessarily have a full, fully democratic society. So, free software is not,
as I say, it's not just for, you know, nerds, it's for everyone. Now, the thing to realize
about software freedom is, it's all well and good. If you know how to install Linux, you
have some idea of what you're doing, but everyone needs to have free software because
if only a small group of people know how to use it, then that's obviously no good. You need,
you need everyone else to work on all of their services that you use. So, they need software
freedom as well. If you've got an entire industry that's all, you know, Windows, Mac or wherever else,
that's no good. So, I'm going to go first into the structure of this talk. So, in previous
talks that I've done, I've been much more sort of theoretical, you know, I've gone on for, you know,
an hour talking about my projects and detail. The first 20 to 25 minutes of service talk is going
to be, you know, going through the history, the technical aspects of the project, but it's not going to be,
it's not going to be overly technical, it's going to be more ideological, and we're going to talk
about the goals of the project, but the focus of this talk is going to be on the second half.
So, I'm going to try to get through the talk itself in about 20 to 25 minutes, and then the second
half of this talk, I'm going to give a live demonstration showing the book itself. So, I'm going to go
through the build system, I'm going to go through, I'm basically just, the first thing I'm going
to start with is I'm going to show, you know, if you're, if you're just a user, you want to use
the book, I'm going to show all of the typical ways that you'd use it, I'm going to show, maybe
go into some of the development aspects, show how certain things it maintains, things like that.
And during that second half, it will also be a question, a Q&A. So, if you have any questions,
like, if I'm doing the demo, if I'm doing the demo and, you know, something that doesn't seem
right, you know, put your hand up, interrupts me, I'll explain, I'll stop and explain, and if you want,
yeah. So, that's assuming, of course, that I stick to this schedule, we don't know how long
this talk's going to go on for. So, what is LibreBoot? As I briefly mentioned in the intro to this
talk, it's a free, or open-source, spios, or UFI firmware replacement. What does it mean?
The bios, or UFI, as some people, as a lot of people refer to it, is the thing that starts
your computer. So, it starts the CPU, initializes memory controller, peripherals, then it comes up with a
nice little interface, you start your boot load, a big reporting system, right? So, you know, Linux,
BSD, whatever it is. LibreBoot is also what's known as a core boot district. So, in the past,
some people have, have wrongly assumed that LibreBoot is a fork of core boot. That's not the case.
You know how, you know how you have, say, Debian, Ubuntu, Arch Linux, I suppose, those are Linux distributions.
So, if you want to use Linux, you don't have to download the Linux kernel. You don't have to download,
you know, GNU Core Utils, or X11, Waylands, and all of the variant, you don't have to do everything yourself.
You have these wonderful projects that package everything for you and make it really, really easy,
and they provide user documentation support. LibreBoot is essentially that, but for core boot.
So, it packages core boot and all of the various programs there. So, why, use LibreBoot? Well,
LibreBoot is a free software project. So, I assume most people in this audience know what free
software is, but free software, I'll just briefly explain again in case any one person doesn't know.
Free software means you have the right to study the program, see, I have worked here,
you can run it on as many computers as you like, share it with your friends, you can do whatever you want with it.
This is an important thing to have from an ideological perspective. It's a matter of civil liberties,
as I explained earlier on in this talk. It democratizes computing essentially.
So, this is really the main aspect of LibreBoot. The main point of LibreBoot is to be a free firmware
distribution, but there are other reasons you might want to use it as well. So, it has quite a lot of
nice encryption features in Grab, for example, if you want to boot Linux and you want to
encrypt everything, you can use full disk encryption on standard proprietary firmware, but
LibreBoot, for example, comes with Grab as one of the boot loader options when you start.
It can read luck's partitions directly. So, you can have an encrypt. So, if you have the
slash boot director, we've got with your Linux kernel, you can decrypt that directly so that nothing
on your disks is in secure. And as other security features as well, I've got into some of
this later on in the talk. No DRM, no anti-features. So, for example, this ThinkPad that I've got,
this is a ThinkPad T580. It was added to LibreBoot last month, actually. On ThinkPad's, for example,
if you want to use your own wireless card, that's upgraded to something better. The Nova usually has
a whitelist in their firmware that means you can't use anything but what they provide.
LibreBoot doesn't have features like that. Another advantage to LibreBoot is, because it's a
free software project, because the community has control over it, because you can study it,
change it and completely understand every aspect of it, you get continued for
LibreBoot also tries to provide security features. You really can't get most of the
firmware projects. And, well, it should go with that saying, if we want free software
on everywhere, if we want everyone to use free software, then that logically must mean that
every computer has to have free firmware, whether it be a LibreBoot or something else.
Our brieflet's explain what a core boot payload is. Now, core boots, as I explained,
is the projects that LibreBoot uses for hybrid initialization. But core boots only does
hybrid initialization. It doesn't provide, you know how when you boot your machine and it
comes up with a nice little, like many, you can select your, I don't know, your SSD or a
flaster over or net those or something like that. Core boot doesn't do any of that. It just
starts your hardware and then jumps to what's called a payload. This payload is typically
what provides your bootloader. So, you can use grab Linux, you can use EDK2, EDK2 is the
Intel's reference implementation for UFI. It is a free software project, it's on the GitHub.
You can, LibreBoot provides, LibreBoot doesn't provide every payload. You can modify it and
add whatever you want, but we provide grab C-bass in Uboots on various boards, and I'll go into that
later on in the software as well. You can use other payloads, and this will be in the demo.
You can actually modify each board to use core boots. So, we have our own
logic in the LibreBoot build system for adding payloads to boards, but you can override that and use
core boots. Logic instead, and core boot has more options. Again, I'll go through this in the demo
in the second half of the talk. So, you can find, if you want to know more about core boot in general,
but there is one of LibreBoot's upstream projects, you can go to core boot.org.
Now, so, I explained earlier on in the talk that LibreBoot is a core boot distribution. Well,
let's compare this to say Debian. If you've got Debian, there's a bootstrap script that makes
the install roomage, and then you've got a package manager. Same with any other Linux distribution.
Naturally, LibreBoot has what, I'll go into this in brief history about the LibreBoot project.
So, I started the projects in December 2013. It wasn't initially a project as such.
I was running, and I'm still running actually, a company on the internet called Mini-Free.
Mini-Free.org. It wasn't called Mini-Free.org back then. It was a different domain name, but
saying same thing. A friend that I was talking to at the time was very excited about what I was doing.
I didn't really have any plans in the early days of the projects. I just had my company,
you know, and I provided corporate images, I provided source code on my company website. There wasn't
really a project when they saw first started. It was just commercial, right? But a friend saw the
potential before I did, actually. Here's previously, I'm not going to actually say his name,
but he contacted the F&F and needless to say the F&F was ecstatic. They're licensing and compliance
manager Joshua Gay. That's his name. I see Nick was Jay Gay at the time. He emailed me personally,
to say that the Free Suffolk Foundation is really happy with what you're doing, and they wanted to
promote my work. So, I initially just went through the certification process. So, the F&F,
they have a process, a certification process, it's called, respects your freedom. It's for hardware,
hardware suppliers, and the idea is that they want to verify that each company selling whether
it be a computer, a 3D printer, I don't know, every 3 player, mobile phone, whatever it is. It has to
be all free software that they can't have any spyware, can't have anything malicious, fully free
in spirit, and actually free. So, I went through the process for that. In the early days of
the projects, I ended up, I actually didn't take this as seriously back then. I mean, I was kind
of aware of it, but you may or may not be aware. Corbyn is nominally a free software project,
but it doesn't always, sometimes in Corbyn, you do need certain binary blobs for certain
boards, and I'll go through that later on, but the original purpose of leapboots, as part of
this certification process, was to provide a fully free, deep blobs, Corbyn distribution, fully
free, few months in 2016, after applying in 2015, LibraBoot was actually referred to as
Gennew LibraBoot, and we did actually did three releases of that then. My rationale for having
LibraBoot joined the Gennew Projects back then was, I didn't possibly see how it could hurt,
I only saw ways that it could be improved simply by virtue of the prestige of the Gennew
infrastructure itself. LibraBoot was, and is a free software project started with the same goals,
we want free software everywhere. So, ideologically, we were compatible. There were some technical
disagreements during this time that were not foreseen during the application process,
so standards relating to documentation, coding styles, also the governance of the projects.
I was very critical at the time, because basically I felt like LibraBoot was LibraBoot's
and the points of the FSF was just to promote it. But long story short, there was a very
ugly breakup from the Gennew Projects in 2016. I regret what happened. Not really going to go into
much detail in this talk. There's actually an article on LibraBoot.org. If you can go to
LibraBoot.org, forward slash news, forward slash 10, date to melt 10, as in 100, date to melt.
But the next few years, LibraBoot then was its own projects. During this time, I actually
stepped down. I'm going into this history of the projects now. So, I actually stepped down
from the LibraBoot projects for a number of years, from 2017 to 2021. I was going through some
of my own things at the time, so I left other people in charge that were in the projects then.
We created a committee that everyone could vote on decisions. It was decided then that the
whole projects would be rewritten. One of the design flaws of the original LibraBoot
build system was, it wasn't really very flexible. It worked, but you type one commands, build one
board, and it wasn't really a concept of configurability back then. So, the purpose of the
rewrite was going to go into some details about what they are. So, I started our split with a
very strict and clear policy that basically says, and this is what I'm going into now, if a
blob can be avoided, avoid it, if it can't include it. Try to minimise the harm that certain
blobs can do. So, for example, on a lot of new Intel systems, if you need, if you have the
Intel management engine, LibraBoot by default will use the ME cleaner utility, and there are some
other examples as well. You can actually read that if you, that's the basic summary. If you want to
read the read it in detail, there's this link on the slide, LibraBoot.org, forward slash
news, forward slash policy, that's to now. Now, I should clarify that this was originally on the
OSBoot website, and I'm going to go into some details later on. I did not use the rewritten design
for the LibraBoot build system, then I took my work from 2016, when I essentially steps down
from the projects and modernised it. So, made it possible to use new machines, added lots of
well, but I did, but I basically said, look, new people have not done releases in five years,
and I've got this built system over here in LibraBoot that works, it's got a ton of new boards
and people are using it, people are happy. So, I decided then, why don't I also do this in LibraBoot?
So, that's exactly what I did. Took, throughout five years of bad code and just to cover.
So, obviously, though, from the perspective, then LibraBoot had been essentially dead for a
number of years. So, getting people involved was very difficult. Yeah, it was a bit. I mean,
we got there in the end, but so, but the problem, as I've explained with LibraBoot, was if you have
this policy of only having fully free software, no blobs, no nothing, you can only support boards
from 10, 15, even, sometimes 20 years ago. So, my thought then was, well, why don't I just merge
the two projects together, just have, we've already got LibraBoot, which has been established for years.
So, with a Canadian developer that I was working with at the time, I'm not, I apologise,
Keleb if I'm risk-pronounceing you know, at Keleb, at Grung, someone maybe someone can
correct my pronunciation. Anyway, he did a lot of work with me on OSBoot in 2022. So,
he was amazing, and you can go on to the LibraBoot.org, at LibraBoot.org forward slash
contribbed by HTML, it's got all of the contributions that people have made, he's on there,
and yeah, so we worked together on that, and so he worked on the build system. He worked on
the documentation, I worked on the build system, and we merged at OSBoot.org was completely removed
and redirected to LibraBoot. There was a release shortly after that post merge, and you can
probably tell what's going to happen next. The FSF being the FSF decided, well, we are not very
happy with this. So, at the LibraBoot Planet 2023 conference, one of their people decided why don't
we make another LibraBoot project, LibraBoot.org. Now, I would be a hypocrite, if I said that I
objects to a thought, I don't. I want people to thought my work, if you want to do your own thing,
and you want to go your own way, that's fine. But they tried to use the LibraBoot name, and
they made it very clear that they wanted me to stop using the LibraBoot name. So, what exactly
was I supposed to do? So, I basically just said, well, okay, so I was aware that this was going to
happen, because one of the people that I work with in LibraBoot was contacted by one of their developers
at the time saying, hey, do you want to work on this new LibraBoot thought with us? And he told me
about it. So, I saw that the FSF was doing a talk from Dennis. He's one of the founders of the
LibraBoot project. He had a talk. He didn't say that there was going to be a LibraBoot
thought. It was called something like, seizing the means of free software, production,
or something like that. Anyway, I anticipated that he was going to,
correctly, that he was going to announce a fork during that talk. So, I did a LibraBoot
thought the same day, hours before his talk. It passed amounts of work much more than we did before
in the same period. We did like three leases in a month. After a month, a drew
defaults, the owner of source hats, they were using source hats to host the website,
the repositories, they're mailing this, everything. As some people may know, drew
defaults is not a fan of the FSF, and I basically went through them and said, look,
can we do something about this? So, long story short, the project was deleted from
source hats and after that they didn't want to. I can probably surmise that they wanted it to
look a bit more grass roots rather than hosting it on GNU.org, and calling it GNU LibraBoot,
which obviously wouldn't fly. They wanted to make it look a bit more sort of independent.
But the FSFs tried again, and they created a new project called GNU Boots.
A bit more respectful this time, they weren't trying to use the LibraBoot name,
but they still had the same rotten attitude. They were going around telling people that
LibraBoot is a proprietary software project. So, I decided, well look, they were also using
LibraBoot from July, 2022. This was a bit 2023 at that point. They were using a version of LibraBoot
that was a year out of date. And I looked at the repository and they didn't really seem to be going
anywhere, so I thought, you know what? Why don't I make a project that does exactly what you want?
So in October, 2023, I launched a new project called GNU Boots. GNU Boots is essentially the
old LibraBoot, the old policy, fully free FSF compliant, all of that.
There's a lot of this talk, there's a purpose of this talk is not to talk about GNU, but obviously
no LibraBoot talk is complete without mentions of the FSF, and this is part of the history of
LibraBoot projects. So, that long story short, a few years later, things come down,
full, well and good now. Anyway, I don't want to keep talking about the FSF.
So, there's been loads and loads of new work over the last few years. So, for example, this
thinkpad that I'm running is a T5, I thinkpad T580. The T480 was added, well, it was also the
Deluxeplex 3050 micro. Yeah, a developer that I work with, Marta Kookley, I hope I'm pronouncing
the name correctly this fun. He works on a utility called D-guards, which, besides, there's a feature
on Intel systems called the Intel Boot Guard, and what that does is, if the manufacturer
enables it, your firmware is cryptographic signs. So, if you change anything in the firmware,
it doesn't boot anymore. So, this makes orbit impossible. On 8th generation, I say 8th generation,
anything that has Intel Management Engine version 11. Any, there are any 11.x.
He wrote a utility called D-guards, which used an existing vulnerability in ME version 11,
who decides to completely, the vulnerability in question on the ME, basically allows you to run
on-time code. So, he used that to disable the, to figure out how to disable the Intel boot guard
and from that, we can now support a lot of newer machines, because a lot of newer new machines
are used, but good. Yeah. So, I'm going to go briefly through the future roadmap of the projects.
So, at the moment, there's a lot of work needed on the documentation of the boot. A lot of people
that got back to me and saying, it's all over the place. If I want to figure out how to flash
one machine, I've got to read this page, then that page, and it's all one of the things that we
really need to do in the projects that the moment is, is audit the documentation and make it a bit
more fluent for the, for non-technical people. One of the things I also want to do with
Libre boot is Ad Tiana Core. There is a Tiana Core, or if you're okay to, on lots of modern
desktop systems now, you need to have URIFIRE, because if you're in particular, alongside
the core boot, allows you to have a feature called real okay-table bar, or base address register.
If you want, if your graphics card needs to use a lot more memory, as a lot of them do now,
as you need to have this feature, and we currently don't have this feature, but with a long
side, you need to pay two. If you have like an Intel arc or modern video and the work wherever
it is, a lot of graphics cards just simply don't work anymore. You need URIFIRE, so we're looking
into that. I'm currently working on integrating a bunch of other projects, so there's another
project called Mr Chromebox, which supports a lot of Intel-based Chromebooks. I've been working
with, well, not working with, but the developer of that project has provided me with some advice,
and I'm currently working on integrating those in Libre boot. Libre boot also became part of
a nonprofit organization called Software in the Public Interest last year. They essentially
provide fiscal sponsorships of projects, so if you want to make a donations paid or something
like that, then they can also provide a lot of legal related services. They provide support for
a lot of big projects like Debian, Arch, I think. Yeah, Arch Linux is a member.
If you want to, I said in Ireland, in this talk, I'm not going through the technical aspects of
Libre boot in detail, and I'm not going through it. If I wanted to talk about every
contributor that has ever done anything for the project, it'll be like a hundred slides. If you
want to go on to, if you go on to Libre boot.org forward slash a contract that HTML, you can find
a list of people who have contributed to the project. I am wrapping up the talk part now, and
I'm going to do the demo a little bit. If you want to help Libre boot, some generic advice
is, use it. Tell people about it, tell your friends, tell going line, log about it. If you're
technically inclined, you can work on corporates itself, you can add your main boards, you can
as explained before you can also work on improving use of documentation, also provide use of
this bottom LC. This is obviously obligatory of this part, I've used some images from other
projects. Thank you, and as I explained before, the next part of this talk will be a demo,
and a Q&A. So, yep, thank you.
Now, I am mindful of the facts that I'm currently holding this microphone, but I
need to be able to type to do the demo. So, would it be possible for me to wear the thingy, yeah,
thank you.
Okay, so I'm going to sort of improvise.
So, I'm going to go in. Okay, so if I go now into the, let me put that terminal on the other screen.
Oh, yeah, if anyone wants to ask questions, so as I said before, I'm going to do a demo now on Libre
boot itself on the build system, how it works, but if you want to ask anything,
this is the Q&A session now. So, if you have any questions, I'm sure someone wants to
pass around the mic or ask any questions you have, it can be about the demo itself, or
I can't see up. Okay, hopefully you can see this. So, I see what, I've got an idea. Can you
stand with me and hold the mic to my mouth so I can speak and use both hands? This is me improvising.
So, thank you, thank you very much. Yeah, yeah. Really difficult to do anything on this screen.
Yeah, if anyone has any questions, if I pass around the mic and you can ask what if you want
about Libre roots, yeah, if you have any questions I want to. I can't see my mouth on the second
screen, so it's kind of difficult to. I was wondering, how safest Libre boots to use on my
laptop that I use every day and that I don't want to crash and keep booting?
Relatively safe, so we have a testing process, so we do testing releases first and then we do
stable releases. If you want to have some assurance that you won't break your machine, I recommend
sticking to stable releases of Libre boots. Generally, that will not pose an issue. If you do have
problems, you can report them immediately and we will try. Okay, I can't see what I'm doing.
So, should I then first check all the hardware if it's all supported or...
Sorry, so I'll say again. Should I then first check if all my hardware is supported by Libre
Oh yeah, so if you go to Libre boot.org forward slash dot forward slash in store, there is a compatibility
list there. Okay, thank you. Hello, could everyone see the screen clearly before? Like when it was
black and white? We'll try to ask somebody from this half,
um, well, it's right, I'm trying to just, I can't literally see what happened.
If there's any questions, feel free to ask.
Hello, so from what I understood by scheming the website aside from Chromebooks,
basically every other machine requires you to open it in order to connect an external flash at
to install it. Is there like any plans to deal with it? Because like, well, I probably can do that,
but if we are targeting basically the entire world, it's more complicated for them.
Yeah, really, I think it just, it really just depends on the machine that you're flashing.
So, some are easier than others. Some you can just run software to install Libre boot. Some you
do need to take apart. Unfortunately, it's just one of those things that's currently unavoidable.
Okay, I have a light mode and I wouldn't mind someone on now. Okay, can people see that terminal
better now? Okay, much better, right. So we've got, I don't know if we've got left.
Any other question, maybe? Okay, we've got about 10 minutes. Okay, 10 minutes should be enough time.
So I'm just going to briefly go through, I'm going to, and I know, how do I actually enable mirror mode?
Yeah, just keep asking questions. If you have any questions, I'll be happy to ask them.
I don't need normally doing mirror mode in front of us.
Okay, I'll just, I'll just do it this way. Okay, so if you want to use Libre boot,
I'm going to give you a brief tech demo. So let's say what you have, sorry, what is the single
the most powerful device currently compatible with Libre boot? It really depends on what you want to do.
So if you want a laptop, for example, the most powerful laptop you want to use right now is probably
I think pad T48 or T580. If you want a desktop machine, it really depends on what you're doing.
If you're mostly concerned with multi threading, for example, there's an older boards that we
supports, the ASUS KGB D16 is really old now, but you can use large 16, that's who 16
course, if you're using, if you don't, that's a compiling building, then it's kernels.
Anything that needs a lot of thread. If you're building a modern desktop for workstation use,
you might use one of the has-well systems that we support. We are looking to add more
modern older desktop boards at some points in the near future. There's really no concrete answer
to your question, the most powerful or viable system to use really depends on your use case scenario.
That sounds like a great question, okay, thank you.
Okay, so yeah, brief tech demo, so there's really not much to it. So let's say you want to
feel, again, feel free to interrupt me anytime. If you want to use another question here.
Okay, so I'm just going to briefly go through, so if let's say you just want to use
a little bit, right? Let's say I want to install a little bit on a think-pad T580.
So if I do this command, m, s, m, s, m, k, b, co-book list, or less, you can get a list of boards,
and you can search T580, and actually we'll do know what's in the output here, but let's say now I want
to build for the device that you can do, like, like, blah, okay, it's very difficult to see what I'm doing here, so, okay, go ahead, ask your question.
One of the question is, like, how easy is it to, like, make it possible for, like, a new device?
If I have, let's say, a modern think-pad, and I want to try adding support for that, how long do you
think it would take? Is it, like, a lot of reverse engineering and things, or just go look at
documentation, specs, and just write? Yeah, so if it's not already supported in the corporate
projects, then there are going to be certain questions you have to ask. So it's the chipset already supported,
like, what, what, what Intel Gen is, is the platform, like, is everything supported properly?
Generally speaking, on laptops, there's also an extra chip called the EC, the embedded controller,
which is very different per machine, and you usually have to do a bit of reverse engineering there.
Corby tries to generalize as much as possible for each platform, such that each mainboard
has its own quirks to find in code, but then you have universal code that's you reused on
that hundreds of different mainboards. Go to the corporate projects first, work with then,
add, add the boards. When you add a board to the labor boots, it's essentially, by virtual
configuration, the labor boots supports what the corporate already has, and it provides
the pre-configures, things that you can use. Yeah, there's no real set answered to your question,
yeah, that I would advise that you contact the corporate projects about this. Okay, so I'm going to go through
so I just built one of the the main things you have to realize about every talk is there is going
always going to be an error when you do a commands that works perfectly, that morning,
you're always going to have something. Okay, so I'll ask another question if you want five.
Oh, yeah, for the recent inclusion of the top ten router, is that indicative that there might be
more, sorry, again, what router? Oh, the top ten one. Oh, yeah, yeah, sorry. Oh, sorry,
just to finish, sorry, get you off. Is that indicative that there might be more support for
like older lake twin lake products down the line? Yes, and this is something that we're actively pursuing.
You're asking if we're looking at more, more boards, more from that same generation, right? Yes.
Great presentation. I have a question here. You mentioned that you are supporting
a generation of core i5 i7 CPUs from Intel, such as the ThinkBat T480 and T480s,
what about T490 and 90s, which are using the same generation of Intel CPUs?
Ah, yes. I believe you said the ThinkPad T490, the T490 uses Intel management engine version 12,
for which hack to disable the Intel boot guard has not yet been found. So that's currently not feasible
in reboot. Thank you, great talk. So if I want to use a TPM and ideally something like
measured boot through reboot, can I do that? How is it? Is it?
Libreboots has no facility for use of a TPM. There are other projects that use it. You can look at
a project called heads, for example, which uses TPM and has what it calls measured boot.
It uses the Linux kernel as a payload and it uses K exec for its own interface to boot your
system. It's very similar to using something like, say, grub or something like that. And yeah,
it has that feature. Libreboot currently does not facilitate this in any way. That's not
to say it can't, just that it currently doesn't. You could probably modify whatever you want to
do that. TPM is enabled on some boards, but we don't really use it for anything at the moment.
Okay, so the tech demo is a bit of a nightmare actually because I can't see what I'm doing
because I'm looking at the screen. Anyway, I can't really show it running because we've
run a few minutes left. So let's say you're a user. You want to do Libreboot. Let's say you're
in deviant, right? You got like that NK dependencies, deviant. That will run all your, that will
install all the build dependencies. And then if you want to build for your board, you do.
But this is Doc, you can, you can go on to Libreboot.org forward slash docs forward slash build.
There's also documentation about the build system itself on forward slash docs forward slash main
team. But if you want to, so go ahead and ask more questions if you want, I'll be
up side if you want to crowd around me afterwards as well. So you do that in KB,
call it this, it shows you that a bunch of boards and then you do. And then you just, you can just
call those, you know, build every board. We can add target nine here. I can't, I don't know.
Hello, maybe if we. We have time for one last question. Yep.
I question, I have a Libreboot on X 200 laptop, which I'm really happy about that, about
two, that five seconds. But I have a problem, maybe it's not a feature already implemented with
a QMU and instruction to have hardware acceleration. So, of course, we have the machine
really slow. So when you say hardware acceleration, what you're referring to? I'm talking about
the WXM. Yeah. Well, it's a fairly out the, the most efficient answer is it's a very old machine.
If you want modern hardware acceleration features and what not, you need to upgrade your hardware.
I hope, I know that's not probably not what most people want to hear, but think Pad X 200 is
18 years old. So, yeah, but if I use it, the normal wheels, I have acceleration,
be my virtual machine. Oh, sorry, I misunderstood. Are you referring to virtualization?
Exactly. Oh, okay. Yeah, that is something that we can look into. So, what's, if you have a bug
relating to that, you can send it to the bug tracker on code bug, code bug, dot or forward slash
reboot, forward slash, I'll be in K and you can information about that. Thank you for your talk.
Okay. Yeah, I do apologize. Anyway, yeah. So, basically, if you want to, I briefly alluded
to it in this somewhat Ubisoft successful tech demo, but as you saw from some of these commands,
if you want to build Libre boot and install it on the machine, it's usually just like one or two
commands. If you were going to build your own firmware from scratch, you'd need to download
core boot and tackle the, of the commands you'd need to know which cross compilers to, to build.
You'd need to download grab, you need to download this, download that, and it'd be hundreds of
commands you'd have to go through 50 different configuration files of 50s probably hyperbole, but you get
the point. One commands and it just does everything. That would have been what I was going to,
that I would have demonstrated that, but as I've, as I'm informed, run out of time. Again,
thank you for coming to my presentation. If you have any more questions, we have all day. So,
feel free to crown around me in the corridors outside or ambush me at your leisure during the
rest of the frosttime conference. Thank you again for coming to my talk.