 Dzień dobry. Dzień dobry. Chcieliśmy testować sześć materiałów, z największymi BSD-ami i korbutami, ponieważ korbut nie działa dobrze z niektórymi borą. Są problemy i będziemy chcieliśmy rozmawiać o nich. Dzień dobry. Są ludzie, które myślą, że korbut może działać tylko z Linux systemem, ale jesteśmy trwani z BSD systemem, więc to jest dlaczego musieliśmy to sprawdzić. I ten komputer nie jest mój, nie... Rysujemy z BSD i jest tu coś o tym, Tak jak mówiłem wcześniej, że jesteśmy fanami w FRIEN Open Source Software and Hardware Solution i chcemy integrować to z BSD systemem. A kiedy kupimy nowy device, sprawdzamy, czy to będzie pracować z Colbert. I to jest główny kryteria dla nas. Prawie. Jestem reakcją datacenteru. Gdybym zazwyczaj uruchomił linuczny system, jakaś bsd. I ja pracuję na firmie, które prowadzą supporty IT dla innych firm, a desktop i serwisów. Jestem też mantiencą z 3BS-D-pods. Oby cobód. Dla tych, którzy nie znają, to jest całkowicie otwór, alternatywne dla BIOS lub UE. To może działać na x86, może działać na arm. To było... Jakoś spróbowało, żeby spróbować na połowę. Dla połowach, to może działać bez żadnych bloków. Na przykład na x200. To będzie faster niż BIOS. To inicializuje memę w parallelu. Możemy też spróbować memtest, który zwykle możesz spróbować z USB. Możesz spróbować to do BIOS. BIOS czyb. Więc... To jest bardziej zróbne. Więc... Open source nie jest tak szybko. To może być. Więc jest zawsze coś złego, co może się stać. Coś złego, co może się stać. I jeśli to może się stać, to się stać. Więc jakieś zróbne zróbne z Colbert. To większość temperatury. Colbert nie kontroluje fanów. I te problemy, które były najwyższe, te najwyższe, te rzeczy, które musieliśmy zauważyć. I tak jak mówiłem, przed podróżnieniem systemów, które nie są linuczne, nie jest tak obwitne. Tak. Myślę, że tylko linuczny jest dobrze testowany. Czasem nawet Windows. Ale BSD... To jest ciemno... Marginalne używanie dla Colbert. To może być problem. Mówiłem z jakichś rozwiązań, nie otworzyły nawet żadnego BSD na górę. Więc to jest problem. OK. Trzebaśmy te górki. Myślę, że niektóre są dobrze znane. Niektóre nie mogą być dobrze znane. Trzebaśmy to testować z externalną GPU, ponieważ mam CPU bez żadnej integracji. Więc to było potrzebne. I to nie zawsze było sukcesowe. I wiesz dlaczego. OK. To jest... Czasem BSD nie utworzył kontrolingu fundów. To jest wielka kwestia. Zresztą fundów wystarczają na 100% lub wystarczają na coś, co Colbert zainteresuje. Czasem jest 20% na przykład. Jeśli wystarczają na bardzo wysoką górę, komputer może się zatrzymać. To jest naprawdę wielka problem. Zresztą BSD na górę jest naprawdę wielka. Właśnie wsparcie. To BSD też nie jest źle. To jest trochę lepsze niż BSD, ale też nie jest źle. Cieszymy się, że w 10 latach wytrzymałem do studiów do otworzenia BSD Hardware Sensor Framework do 3BSD. To było nawet skomentowane, ale później to było skomentowane. Jutra kompletowała z PHA. Polsko nie podobał się. I teraz nie jest alternatywna. To też jest problemy z górą TDP. CPU, jeżeli ma więcej temperatury, masz zresztą plusy. To jest pierwsza górę. To jest rzutem. To było mniejszych problemów. To nie ma żadnych problemów, ponieważ górą TDP nie podobał się. To jest skomentowane do otworzenia BSD. To nie ma żadnych problemów z górą TDP. I to jest normalnie tak, że nie ma żadnych problemów zarinowani przez PHA. Właśnie to nie podobał się. Nie podobał się, ponieważ nie podobał się. Nie podobał się. Nie podobał się, że nie podobał się. więc nie musisz skończyć na hardware flash, kiedy zrobiłeś kod butrom i nie skończyłeś. W tym komputerach widać tutaj. To był pierwszy raz, kiedy skończyliśmy hardware, i to działa bardzo dobrze. To nawet działa jak główny PC w domu, kiedy jedna z deskotów została zbrojona. I jedna z tych problemów jest, że nie możemy rozwijać regiony. Więc naprawdę? Tak, nie możemy rozwijać regiony, i to działa, ale to trudno powiedzieć. Jakieś godziny, kiedy rozwijać regiony, to po prostu skończymy. Mogę rozwijać regiony, po prostu znaleźć wiele razy, czy po prostu jedna razy. To nie ma znaczenia. I wtedy, kiedy zrobiłem coś, mogę zrobić wszystko, to po prostu skończymy. Nie mogę to skończyć z botą. Muszę to skończyć. Muszę to skończyć kodem. To zawsze jest problemy z PCK. I to oczywiście z kodem. To jest kodem z SSD. To jest kodem z kodem z SSD. Muszę powiedzieć, że używam wielkiego, nie wiem, powietrza, mocno zaprezentowałem, żeby zrobić małe, małe, piękne powietrza przez 3 volt. Nie używam wielkiego z... Tak, to jest powietrza 88. Tak, to było wielkie. I to... To było jakieś zbierania w górę wielkiego. Tak, w górę wielkiego. Tak. I te zbierania musiały być bardzo krótkie. I te... Tak, te... ...zbyt za długo. Musieliśmy na to zbierania. I zbierali się z żadnej zbierania. I kodem jest pomona. To jest dużo lepiej niż kodem zbierania. Właśnie jeśli jest bardziej spędny. I zbieramy pomona. Powiedzmy wam trochę zbierania. I dużo lepiej. Zbieramy później, jak zbierają się zbierania zbierania. I dlaczego nie są tak dobrze. I jeśli chcesz zobaczyć, jak robisz zbierania, możesz oglądać filmy na YouTube. Te filmy są na Czciświata. I to jest... To jest o zbieraniu zbierania. I myślę, że zbierają się zbierania zbierania. Są trochę fajne momenty. I następny zbieranie. Ok, ten zbieranie jest całkowicie interesujący. Można się doespanансować zbieranie w dimensje z scen buenos robók. Artigę involveṭe тип roofs.架 ul. Dziękuję bardzo za czytanie zbierania zbierania. Popatrz, że mam zbieranie. Powinniśmy coś, ale oczywiście gycielowe. Even that loud, with my case. FreeBSD also works great. It works actually out of the box. I don't have to set up anything, I just install it. NetBSD, well. I can install from the USB, just fine. It works, but when I reboot, and I want to boot from HDD, well, it doesn't work. It loads another payload from the CBS list. For example, memtest or anything else. The next one on the list. So, yes, the installation works, boot's fine, but there are some problems with booting from HDD, I guess. This is our server. Yes, this was actually the most interesting case here. As we said before, the most problematic issue is with the thermal control on the board. And it's a well-known fact, but mostly on the Linux systems. And we noticed that, on theBSD systems, it's even more problematic. And when we installed the call boot, we couldn't use the server at all, because it used to turn off because of overheating. For the overheating, it's about 10 to 12, 20 minutes. And the CPUs were really hot. They were about 90 degrees. In Linux, they were about 50 degrees. So, that's the difference. And we only had some heaters, radiator, not heaters. We didn't have any fans. We had fans in the case only. That was a problem. We had to add fans to the CPUs. After that, the temperatures lowered, they are now okay, about 30, 40 degrees. That's nice. But I use 3BSD on it. Call Boot sets fans to 100%, and it doesn't lower. So, I needed another solution to control the fans, because they are not constant rate. Another issue is that, after I worked out the cooling, when the server started doing anything, some work, it didn't overheat, but it ran unstable. There were no thermal panics, but it just rebooted. So, about 10, 20, 30 minutes, and it reboots. When doing some compilation, anything. When it does nothing, just runs idle, there's no problem. Timothy Pearson from Raptor ported Call Boot to this board, suggested turning off C-States in CMOS. That actually helped. It runs now very stable. I can reach enough time. And it works nice, I guess. It's usable for everyday using. Okay, so, about the fans. There are some recent developments by Raptor and Timothy Pearson. He ported the OpenBMC stack by Facebook. They use it to control the fans, and it's now possible to flash the BMC chip with OpenBMC. That makes a completely open solution for running system. Unfortunately, OpenBMC uses Linux, Anders on the background, but, well, it works. And about other systems, well, OpenBSD runs nice, no problems. I didn't test it after OpenBMC flashing, but it can control the fans just fine. NetBSD, I couldn't test it, because lack of time. So, I actually don't know, but those two work just fine. And this is our cooling. At first, we tried the cat because cats like to go where it's high temperature, but the cat wasn't enough. And radiators, even if they are copper, they weren't enough. So, we tried to use some active cooling from Dynatron. And I was wondering if the aluminum heaters can work as well as copper ones, but they do. Yeah, those are A8 and A13 models. This one is for 1U and this one is for few, because there's an HDD backplane just above the CPU. Okay. That was actually my desktop board that burned and I use this X200 because of it. I flashed Corbot on it. It's quite a nice board, but there are some OpenBSD problems. OpenBSD works fine. No problem at all. Other than the GPU, which was from NVIDIA, so no drivers, well, no issue. About 3BSD, the same problem with cooling. When doing some work, some compilation, I was playing some game online, for example, it just shuts down. The CPU is very hot. Well, that's a problem. Another issue. After booting the system, there are some messages in the console, actually during booting. After some messages about PCI, the screen doesn't update anymore. It just displays the old lines, but the system boots fine. I can use it via Serial. I can also set X11 to load automatically or I can load it via SSH or Serial, and it loads. It works fine. There's desktop, everything, but you can't get to the TTY. There was a similar issue with Intel drivers at 9.1 version and later, when you couldn't get to the TTY after it's 11 started. So that's similar. About NVIDIA. Well, I was told by the NVIDIA developer that NUVU is still quiet unstable, so I guess it can show here. When starting X11 with the DSD7, the system just hangs up, but the console works before starting, after starting it doesn't. With that DSD8 NUVU is enabled by default, so it just hangs. And there's no output at all, Serial or video. This is the next thing part. We tried to flash from the hardware. This is this Chinese chip clip. We tried to save some money and we didn't buy Pumona clip. And then we have some problems, because those clips have very narrow pins. So you have to decide. And then it's not so easy just to clip the gold pins. It's duct tape. It's not the clip. I had to cut them and solder them directly to the chip, to the clip. And the clip itself, it wears out very quickly. So you need to buy fuel, because when you try to clip it right to the chip, maybe a problem because they slip off. The soldering wasn't enough, because we couldn't get the right image from the chip. So then we asked some people on their channel. And it's like that. So the board just fried. And there was smoke and the smell and so on. And then we bricked the laptop with pretty good parameters. So as I said before, after some experiences with the big power supply, I made the small one with gold pins. And it worked pretty well. When we tried to get a proper image, we couldn't get it. And my advice is just make a big loop for 50 or 100 trials. And some guys on the channel suggested using the Lenovo power supply inside. And it was a bad idea. So don't trust the random guys, because they give you advice and then they disappear. The idea was that if you enable wait online in the UFE and connect the PSU without the battery on, the laptop is actually on, even if you turn it off and you can get the DOM image. But it didn't work. It worked with our own PSU. It didn't work with Lenovo PSU. So it's way much safer to make your own PCU and don't trust the guys from the internet. And if you are lucky and your laptop is still on the warranty, you can sell it back to the seller and sell them all. I don't know what's happened. It doesn't work. I don't know why. Please help me. And they replaced the main board. And I have a fresh new ThinkPad. But I am afraid to repeat the actions because I think they wouldn't believe me twice. And some alternatives to codeboot. Because it's not the only one solution. Yes, there are other completely open solutions, mainly open hardware solutions. There are some Novena boards. They make some really nice development boards. They are based on ARM. So I guess it could be ported to FIBSD or other BSDs. There's also to this Omnia, a Czech hardware router with 8 gigabyte flash. So actually any BSD would fit in without any slimming. And actually about H86, there are no more open H86 boards. Intel makes CPUs with management engine enforced. And ARM enforces PSP. So that's a big problem. There's also a board from the guys who ported codeboot to the D16 boards. Talos 2. It works with IBM Power 9 CPUs. There are two, at least two, FIBSD developers buying this board. They want to port FIBSD on it. I can make a really powerful workstation, a server, actually everything. You can see the specs here. The guys sell it right now. And I guess it's actually the only open solution right now. That is modern. It's actually pre-order right now. And it works with Linux. You can port FIBSD on it. Just inhibits from FIBSD and some other developer about those boards. And it's a pretty good example, because it's one of those free and open devices that are not updated. And you can show it to the other people. And they want to rapidly have old computer. And you can use it for scientific purposes, for enterprise purposes, and other stuff that needs just a big power. It's a big powerful workstation. So, any questions? If you have? I was about to flash my X2, 230, mainly because of Intel ME. Right. Do you know if it solves completely the issue of Intel ME? No, it doesn't solve. It can solve it partially. There's an utility, ME cleaner. It can strip down the ME. It leaves the most necessary partitions that are necessary to boot. The others are stripped down. So you can strip it from, I don't know, maybe five megabytes to actually 100 kilobytes. That's quite nice, I guess. And some guys at Librem, they make purism laptops, work on completely reverse engineering the ME. What's the difference between core boot and Libra boot? OK, Libra boot tries to avoid any blobs. Any blobs meaning even microcode updates. For me, that's an issue. I prefer to have microcode updates. I need to have microcode anyway. So if I can get it updated, I do it. So I started with Libra boot, actually. But it's pretty pointless for me because I don't even have hardware virtualization on my laptop. And I can have it if I just update the microcode. That's it. You mean CPU, microcode? Yes. On the D16 server, we showed, there's even vulnerability with some CPUs, if you don't update the microcode. And Libra boot doesn't, so that's a big problem. Please speak like this just to make sure it's actually recorded. So what is your opinion of U-boot in comparison to core boot? Because it's not just an arm. There is a bunch of Intel engineers working on x86 compatibility. U-boot is quite nice, but it doesn't work on x86. Yes, Raspberry Pis, Bigel Bones, they work with U-boot. It's actually nice. So in the most recent version, the one released earlier this month, there is quite a bit of code from Intel for the i5 and i7 modern CPUs as well. It may require special motherboards, but it should support at least the Broadwell and Haswell and all that stuff. OK, U-boot, I guess it may be an alternative to core boot. And it may work. I'm not sure I didn't try it, but I'm pretty sure it still needs management engine, or PSP if you use it on AMD boards. So that's an alternative to core boot, but it doesn't fee. It's not fee anymore than core boot. Just as a data point, I have a Purism Librem laptop, which is with core boot, and it's working quite well on OpenBSD. The only problem is that there is no support for the frequency scaling of the CPU, because the ICPI tables are missing from core boot to give the information to the OpenBSD kernel. So I'm trying to push the Purism people to add this table back to the core boot firmware. I'm not sure if it's going to work, if they're going to listen to me or not, because of course, under Linux, they are using their own Intel PayState drivers to scale the CPU frequency, and they don't need the ICPI tables. But I don't think anyone on OpenBSD is going to implement these kind of drivers. The background for that is that Intel stopped providing the necessary data points for the frequency voltage tables for the CPU quite a long time ago. So core boot would have to, as a reverse engineer, from the existing ROM images, or try to figure them out on their own. So it's quite tricky. Do you know the current state of more modern AMD systems, like the Zen architecture, if there is any issues like on Intel with management firmware, or so? Yes, actually there are issues just like with management engine. There's the mentioned PSP blob, which is, I guess, a platform security processor. And it's just, well, it's another backdoor, just like management, probably a backdoor, not proven, actually, which is like management engine. Actually, the last USB boards are from 2013-2012. With those, this ASUS KGPE D16 is quite nice. You can have 192 gigabytes RAM, 32 cores. So you can buy this one, I guess. So do you have any idea why the power usage is so much, or like the heat dissipation is higher, but why is the power usage so much higher in FreeBSD? Can you speak a little louder? Okay, do you have any idea why the power usage is so much higher if you're running FreeBSD? Can you read anything why that happens? I actually don't know. And it's not FreeBSD. Other BSDs are also down hotter, but they can support controlling fans. So they can make fans go faster. And that works around the problem. With FreeBSD, I'm not sure, that's a problem to solve for developers. I'm not a FreeBSD developer. I'm not sure. If you depend on your operating system for fan control, what happens if you get a kernel panic? Because at least in FreeBSD, if you have a kernel panic, then one CPU goes into a spin loop and it gets quite hot. Yes, but I didn't have any kind of panics. Tram. Well, they were, but when it worked, when I don't do any crazy stuff, it worked. So there are no panics right now. I had the C-states problem, but it just rebooted. There were no panics. I think the idea of Core Boot or BIOS going into system management mode every once in a while, aby się znalazła, aby się konfigurować. To jest dość zbliżone. Na serdebordie, czy masz żadnego różnego? Zobaczysz, że pokazywanie się w górę otwór, czy masz... Czy to też zbyt zbyt, kiedy masz zbyt powodzenia z regulacyjną kulemką, to było w ogóle w hodowaniu. Więc... Nie, to nie jest problem. Jeśli możesz... Jeśli masz jakieś wskazów, bym zainteresował, że są jakieś problemy z netrodrowami Intel i 3BSD. I to jest to, co się wyrzucał. Kiedy są te wskazów, to są...