WEBVTT 00:00:00.240 --> 00:00:06.319 Co-pilot, you need to opt out. Windows 00:00:03.840 --> 00:00:09.319 update. You will own nothing and be happy. 00:00:09.840 --> 00:00:17.359 Oh, thank goodness. It was just a dream. For a second there, I thought Windows 00:00:14.559 --> 00:00:20.800 really was getting worse. It wasn't a dream. I'm 00:00:18.720 --> 00:00:22.880 >> sorry. I was just scared for my privacy. I didn't want to sleep in my own bed 00:00:22.080 --> 00:00:27.359 anymore. >> What are you doing here? I heard that 00:00:25.199 --> 00:00:34.160 Lionus was going to save us. >> Linux. Elijah, not Lionus. 00:00:31.679 --> 00:00:38.559 He does have a valid concern though with Microsoft adding more and more bloat 00:00:36.880 --> 00:00:43.440 that negatively impacts the user experience and user privacy on Windows. 00:00:41.680 --> 00:00:47.600 More people than ever are asking themselves, "What can I do?" Well, 00:00:46.000 --> 00:00:51.280 there's those Windows debloating scripts, but uh those aren't quite the 00:00:49.920 --> 00:00:57.120 silver bullet that they're made out to be. And there is Mac, but that's not a 00:00:54.640 --> 00:01:01.760 great solution for gamers. That is where Linux comes in. As the rest of the world 00:00:59.199 --> 00:01:06.720 inifies, thanks to the incredible open- source community and corporate sponsors 00:01:03.760 --> 00:01:12.720 like Valve, Linux just keeps getting better. And I think it's high time that 00:01:09.280 --> 00:01:15.119 I try once again to make the switch. And 00:01:12.720 --> 00:01:17.439 he's joining me. Hey, ELIJAH, WAKE UP. LET'S GO. 00:01:15.760 --> 00:01:22.080 >> WHAT? BUT TONS of games I play don't work on Linux. >> Sure, but there's thousands of titles 00:01:20.000 --> 00:01:27.200 that do work. And besides, it's only a month. That is unless you discover that 00:01:25.040 --> 00:01:32.400 you love it so much you don't even want to play Fortnite anymore. Maybe the only 00:01:28.799 --> 00:01:35.439 '9s you'll want to crank are these 90° 00:01:32.400 --> 00:01:37.759 segways to our sponsor, Meter. They 00:01:35.439 --> 00:01:42.320 build enterprise levels from the ground up and design and manufacture their own 00:01:40.640 --> 00:01:46.640 hardware to boot. If you're looking for a reliable, scalable networking across a 00:01:44.640 --> 00:01:50.479 multi-sight enterprise environment, Meter might be a great fit for you. 00:01:48.799 --> 00:01:53.759 Click our link in the video description to learn more today. 00:02:01.600 --> 00:02:07.680 The first and possibly biggest hurdle when it comes to embracing that 00:02:05.360 --> 00:02:12.560 open-source life is the overwhelming number of options. Now, for some folks, 00:02:09.920 --> 00:02:17.520 the idea of having so many choices, each catering to a specific user or use case, 00:02:15.040 --> 00:02:22.959 is amazing, and it is, especially if you love to tinker. But for everyone else, 00:02:20.319 --> 00:02:27.760 choice paralysis is a real thing. And with literally dozens of viable options 00:02:25.680 --> 00:02:31.680 for Linux distros, not to mention the social pressure that comes from picking 00:02:29.680 --> 00:02:37.599 the wrong one, it can be a major turnoff. Last time we did this over 4 00:02:34.720 --> 00:02:41.840 years ago, I called out how terrible these listical sites are, and so did 00:02:40.239 --> 00:02:46.879 many others in the Linux community. >> And right out of the gate, 00:02:44.000 --> 00:02:49.280 >> these are just terrible, terrible options. I don't expect much from this 00:02:48.879 --> 00:02:54.480 article. >> Let's have a look and see if they've improved. Oh, XDA's article was from 00:02:52.959 --> 00:02:58.640 less than a month ago, though. And of course, the very first one is one I 00:02:56.319 --> 00:03:04.800 haven't even heard of. No, Linux built on Fedora, quality of life tweaks, 00:03:02.480 --> 00:03:12.000 controller support out of the box, Pop OS, Fedora's on here, Open Zusa, 00:03:08.959 --> 00:03:15.120 Tumbleweed, Catchy OS, this I've heard 00:03:12.000 --> 00:03:17.280 of, Endeavor OS, Ubuntu. Good lord, 00:03:15.120 --> 00:03:22.239 you've hardly narrowed it down, bud. Fedora KDE, straight up, that's it. No 00:03:20.400 --> 00:03:26.400 pros and cons of anything else. Just go for it. Unless you're going handheld, 00:03:23.920 --> 00:03:30.159 then Bazite. I'd really like a DRO I can use across all my devices, though. So, 00:03:28.000 --> 00:03:33.920 that's AMD, NVIDIA, handheld, and desktop. We'll see if that happens. Pop 00:03:32.080 --> 00:03:37.599 OS is the easiest. There's shockingly little overlap on these. I'm on my 00:03:35.599 --> 00:03:41.920 fourth article now, and three of the six options are ones that I haven't seen 00:03:39.120 --> 00:03:47.200 yet. Hollow ISO, Garuda Linux, and Mangaro. Of course, googling the answer 00:03:44.480 --> 00:03:51.760 is basically boomer behavior. Now, if I wanted to do my thing and I want to 00:03:49.440 --> 00:03:56.720 roleplay as a typical techin interested gamer who's looking to make the switch, 00:03:54.000 --> 00:04:01.200 I got to fire up chat GPT and see what open AI has to say on the subject. 00:03:59.519 --> 00:04:05.040 >> Giving it an essay there. >> Well, I'm giving it as much information 00:04:02.879 --> 00:04:09.200 as I feel it needs to give me a good recommendation. I like I want to make 00:04:07.120 --> 00:04:13.519 the switch to Linux. I have a variety of PCs, each with different needs, and 00:04:11.200 --> 00:04:20.880 ideally I could find a DRO that works for all of them. Recommendation number 00:04:15.680 --> 00:04:22.960 one, Pop OS, Buntu LTS with game mode. 00:04:20.880 --> 00:04:26.960 Maybe not the greatest recommendation if it doesn't know what hardware I'm using. 00:04:24.880 --> 00:04:31.520 Right. Right there. Cons. You have to manually install drivers sometimes. 00:04:28.880 --> 00:04:37.199 Menaro comes up again. Fedora starts giving me a whole like how-to for some 00:04:34.880 --> 00:04:41.520 of the systems. Tips for smooth multi-achine use. Use a single desktop 00:04:39.680 --> 00:04:47.600 environment and the same one across different machines. Bottom line. Pop OS. 00:04:45.520 --> 00:04:51.440 H. I don't know if I'm sure about that. Kind of got burned by them last time. My 00:04:49.759 --> 00:04:55.120 approach was to go to Reddit and I wanted to find someone that fit a 00:04:52.880 --> 00:04:59.120 similar profile as me. And I just basically searched for what got the most 00:04:56.639 --> 00:05:02.880 upd. But when I narrowed it down to gaming dros, there was really only a 00:05:01.280 --> 00:05:08.320 handful that were commonly recommended to me these days. Mangaro, Chimera OS, 00:05:05.759 --> 00:05:12.880 Cashio OS, Bazite, and Pop exclamation mark OS. If your preferred flavor wasn't 00:05:11.039 --> 00:05:16.320 on that list, I promise it doesn't mean that it's bad. It just means that I 00:05:14.720 --> 00:05:21.520 didn't come across many recommendations for it. So, let's talk about the pros 00:05:18.800 --> 00:05:26.160 and the cons of those five. Camar OS is cool, but seems to prioritize being more 00:05:23.919 --> 00:05:30.720 of a console-like experience, which is not really what I'm going for. And the 00:05:28.400 --> 00:05:34.479 same goes for Steam OS. I mean, it's still the one that I think is most 00:05:32.240 --> 00:05:38.080 likely to usher in the year of the Linux desktop, and Valve has promised to 00:05:36.320 --> 00:05:42.479 continue chipping away at the desktop experience, but it's still very much big 00:05:40.560 --> 00:05:46.400 picture first. Not to mention that the limited hardware support is going to be 00:05:43.919 --> 00:05:51.120 a challenge for oh, I don't know, 90% of desktop users, including my downstairs 00:05:48.720 --> 00:05:56.560 PC, which I'm also migrating this time to ensure that my immersion is complete. 00:05:54.240 --> 00:05:59.680 for Mangaro and Casios, both based on Arch, by the way. Mangaro has been 00:05:58.080 --> 00:06:03.440 around for several years at this point, meaning there's tons of documentation 00:06:01.120 --> 00:06:06.960 online or other independent YouTubers have made videos and guides. It would 00:06:05.440 --> 00:06:11.120 make hopefully getting things working nice and easy. Cashios is relatively 00:06:09.199 --> 00:06:14.720 new, but because it's new, it kind of has the same thing. Tons of people are 00:06:12.960 --> 00:06:18.000 covering it and making guides online about using it. Both of those could be a 00:06:16.400 --> 00:06:21.759 bonus for helping me get through this month. Like I mentioned before, Pop OS 00:06:19.919 --> 00:06:26.639 screwed me over pretty good last time. Though, from my understanding, that was 00:06:24.160 --> 00:06:30.560 an insane bug that was present for less than 24 hours, and I just happened to 00:06:28.720 --> 00:06:35.039 run up against. In general, it's known to provide a very friendly experience 00:06:32.400 --> 00:06:39.280 for new users, and it uses Ubuntu as a base, which can make it a little easier 00:06:36.800 --> 00:06:44.560 to find guides and other resources. Last but not least, there's Basite, which is 00:06:41.680 --> 00:06:48.479 explicitly gaming first and has gained serious momentum over its short 00:06:46.400 --> 00:06:52.720 three-year history thanks to the bakedin support for HDR and variable refresh 00:06:50.560 --> 00:06:56.880 rate, easy integration with non- Steam launchers, and emulationfriendly 00:06:54.880 --> 00:07:01.039 features. It's based on Fedora, which doesn't quite have the same normie 00:06:58.720 --> 00:07:05.759 install base as Ubuntu, but it is still a major distro, meaning hopefully it 00:07:04.000 --> 00:07:10.160 shouldn't be too hard to find support. Again, on the subject of support, 00:07:07.840 --> 00:07:13.280 there's no real reason that Elijah and I would have to figure any of this out on 00:07:11.680 --> 00:07:17.360 our own. We could easily use our industry contacts to get help with 00:07:14.720 --> 00:07:22.000 everything from choosing a DRO to even getting a bug fix implemented in real 00:07:19.120 --> 00:07:25.280 time. But to me, that kind of ruins the spirit of the challenge. I mean, it's 00:07:23.840 --> 00:07:30.560 not like the average person would be able to contact Linux Torvt for help 00:07:27.840 --> 00:07:35.360 recompiling the kernel, you know? With all of that in mind, I'm going with 00:07:32.639 --> 00:07:39.360 Basite, specifically the KDE desktop environment. One, it's the cool new kit 00:07:37.599 --> 00:07:44.160 on the block. Two, Basite's documentation seemed slightly easier to 00:07:41.680 --> 00:07:48.000 parse through, which for me is a huge W. And three, while it might be a little 00:07:46.000 --> 00:07:51.680 bit more limiting than Cache OS, which several people warned me about, those 00:07:49.599 --> 00:07:55.039 same people did tell me that it was a little bit easier for a first- timer. I 00:07:53.680 --> 00:08:00.560 think I'm going to take that trade-off. Now, some of you may remember from my AMD upgrade 2 years ago, I actually 00:07:58.479 --> 00:08:05.520 installed Pop OS at the end. Uh, spoiler alert, I haven't been using it. I had an 00:08:02.560 --> 00:08:09.039 issue with my Go XLR, and I spent way too long trying to figure it out that I 00:08:07.039 --> 00:08:12.879 ended up defaulting back to Windows 11. It's also worth mentioning that I'm only 00:08:11.039 --> 00:08:16.639 going to be swapping over my gaming PC to Linux, not my streaming PC. I can't 00:08:15.039 --> 00:08:21.440 afford to have any issues with that. And right now, it just works. And besides, 00:08:19.039 --> 00:08:25.919 all I hit is go live anyways. But who knows, if this goes well, maybe I'll be 00:08:23.759 --> 00:08:30.240 considering swapping that one over. I, on the other hand, will be converting 00:08:27.680 --> 00:08:35.120 all of my PCs, which means that I need something that's compatible with both 00:08:31.840 --> 00:08:38.240 GeForce and Radeon GPUs. I will be 00:08:35.120 --> 00:08:39.919 converting all of my PCs to Yeah, that's 00:08:38.240 --> 00:08:45.040 where the script ends. I have to actually decide now. I'm going with Pop 00:08:42.560 --> 00:08:49.279 OS. Just because it blew up on me once doesn't mean it'll blow up on me again. 00:08:47.279 --> 00:08:52.560 I'm going to follow ChatGpt's recommendation here. I'm going to start 00:08:50.480 --> 00:08:55.279 with one machine, get everything going the way that I want it, and then 00:08:53.760 --> 00:09:00.399 assuming that that goes well, I'm going to stick with Pop OS. Okay, so who 00:08:57.440 --> 00:09:04.880 nailed this? Chat GPC got the way I was already leaning. Pop OS was the first 00:09:02.560 --> 00:09:14.279 recommendation from Intererver, whatever this is. NVIDIA drivers handled cleanly. 00:09:07.760 --> 00:09:14.279 Okay, Pop OS, drive me, daddy. 00:09:15.120 --> 00:09:22.240 >> What? You guys started without me. Uh, my side of this challenge probably won't 00:09:19.760 --> 00:09:27.200 be quite as bad as Linus' since I've been using Arch on my laptop for a while 00:09:24.399 --> 00:09:30.800 now, by the way, and I've gotten pretty comfortable with it. That being said, my 00:09:28.640 --> 00:09:35.440 use case on my laptop is is fairly limited. So, this is an expansion 00:09:32.480 --> 00:09:39.279 forward. I'm in and I'm going with Cashy OS. The whole reason why I've been 00:09:36.959 --> 00:09:44.399 running Arch on my laptop was to try to demystify and and defang the the scary 00:09:42.480 --> 00:09:47.279 experience of Linux for some people cuz I wanted to show like look I'm going to 00:09:45.760 --> 00:09:52.399 put very little effort into this to be completely honest and I expect it's mostly going to go okay but the reason 00:09:50.320 --> 00:09:58.000 for that was because my experience was limited mostly to a browser. So I kind 00:09:54.560 --> 00:09:59.600 of want to continue the Arch experiments 00:09:58.000 --> 00:10:03.600 but in a way that the community is mostly flagging right now as better for 00:10:01.519 --> 00:10:07.279 gaming which is going the cashy direction. I still love Linux Mint. 00:10:05.360 --> 00:10:11.600 Still use it in a couple spots here or there just because I find it so like 00:10:09.839 --> 00:10:14.720 easy to get set up and going. And I know there was some comments under last 00:10:12.959 --> 00:10:19.200 challenge about my choice of Linux Mint and like, "Oh, it's not as updated as 00:10:16.480 --> 00:10:21.839 other things or cuz the Linux community loves to just scream about stuff all the 00:10:20.640 --> 00:10:26.640 time." I wouldn't dissuade you from choosing it. I'm just kind of doing a experiment thing with Arch and enjoying 00:10:25.200 --> 00:10:30.480 it right now. So, I'm going to continue on to Cashachi OS and hopefully it goes 00:10:29.200 --> 00:10:35.519 fine. It is 8:03 and I am just about to start 00:10:33.279 --> 00:10:39.279 my basite installation. Here we go. Insert. Oh, wait. Crap. I got to put the 00:10:37.440 --> 00:10:42.880 SSD in. But I got Hey, you guys like my new server rack? A, it's pretty cool. 00:10:41.200 --> 00:10:45.920 And Lionus made fun of me saying I'd never see it again in the server rack 00:10:44.560 --> 00:10:50.480 case. Now, some of you might actually ask why I'm ripping out both of my 00:10:48.079 --> 00:10:54.000 drives in my computer when Windows is probably only installed on one. Well, 00:10:52.000 --> 00:10:58.399 one thing I won't miss about Windows is there's this really weird bug. Sometimes 00:10:56.000 --> 00:11:02.079 when you rip out one drive after you've installed it with two in it, it will 00:11:00.000 --> 00:11:06.560 show up in the boot option in the BIOS, but it will just fail to boot. I don't 00:11:03.920 --> 00:11:10.160 know how that is still a bug on Windows 11, but hey, I won't have to deal with 00:11:08.240 --> 00:11:15.279 that with Basite. Hopefully, >> I have Cachios on this flash drive ready 00:11:12.959 --> 00:11:20.959 to go. But I ran into a problem. My motherboard has an M.2 slot here, an M.2 00:11:18.800 --> 00:11:24.800 slot here, here, and here. But I didn't build my system. I don't know where my 00:11:22.720 --> 00:11:28.560 current drive is installed. It should be installed here, but it was built by 00:11:26.240 --> 00:11:33.839 Linus' kid, so I have no idea. And my problem is that's my system. This is the 00:11:31.519 --> 00:11:38.079 Bulbasaur PC, right? Getting to the M.2s behind this GPU is going to be insane. I 00:11:36.560 --> 00:11:42.880 like doing that without completely destroying my computer is not really possible. So hopefully I can remove this 00:11:41.200 --> 00:11:47.360 one little strip and there's no drive there and everything will be fine. But if there is a drive there, I'm screwed. 00:11:45.920 --> 00:11:52.160 >> For no reason other than that I'm a sucker for punishment, I've decided to 00:11:48.959 --> 00:11:54.399 do my upgrade to Pop OS here at Whale 00:11:52.160 --> 00:11:58.079 Land. I just got to unplug my boot drive. I treated myself to an Optane 00:11:56.560 --> 00:12:03.360 drive a little while back. Now I just got to disable secure boot and then hopefully this is going to be completely 00:12:01.120 --> 00:12:08.240 painless and I'll be gaming in like 15 minutes. 00:12:06.160 --> 00:12:11.760 And we're off to a great start. Select your drive. Can't see it. Well, I put it 00:12:10.079 --> 00:12:14.880 in a known good slot. Turns out the drive is bad. Why are these challenges 00:12:13.920 --> 00:12:19.920 always cursed? >> Downside of a multimonitor setup. This is my primary monitor. So, we're trying 00:12:18.399 --> 00:12:25.040 to boot into the BIOS right now. So, we're going to go into Fedora. Verifying 00:12:22.399 --> 00:12:29.440 shim sbate date failed. Something has gone seriously wrong. I've done nothing. 00:12:27.600 --> 00:12:35.279 Okay, I think I saw something related to secure boot. It is enabled. I'm going to 00:12:31.680 --> 00:12:37.360 try disabling it. This OS version 00:12:35.279 --> 00:12:42.079 workstation. It's past its end of life date. What? I downloaded fresh from 00:12:39.440 --> 00:12:46.079 Basite's website today. That's a scary warning. So, I did take 00:12:44.399 --> 00:12:50.320 this drive from the office. I wonder if that's why it's showing up as LTT. Maybe 00:12:48.320 --> 00:12:54.880 I did happen to grab a drive from work that had Fedora. I won't mark that 00:12:52.800 --> 00:12:59.839 against Basite then. That was 100% on me. Okay, we're booting up again. Hey, 00:12:57.040 --> 00:13:03.120 there we go. Okay, Basite. Yes, we want to go into live ISO just so I can do the 00:13:01.600 --> 00:13:08.000 install. Hey, there you go. Little Basite logo. Oh, this monitor lit up. 00:13:05.839 --> 00:13:12.639 Hey, there we go. Welcome to the live ISO for Basite. How would you like to 00:13:10.320 --> 00:13:17.440 install? Oh, yeah. So, the drive I did grab had Fedora on it. I wonder if this 00:13:14.800 --> 00:13:21.600 was the drive I used in the Linux Torvt video. Erase data and install. I will 00:13:20.160 --> 00:13:25.279 say I think the default background is really pretty. I might actually keep that. Kind of matches the keyboard 00:13:24.079 --> 00:13:32.079 colors. You know, while I'm waiting for an install, I might as well do a merch plug. ltstore.com. Oh god, I punched my 00:13:29.519 --> 00:13:38.240 other camera. ltstore.com. All right. No drive under there. You can see an empty 00:13:34.399 --> 00:13:41.120 slot. They didn't decorate over the 00:13:38.240 --> 00:13:48.399 screws. Was Kids >> Gamer time. Welcome to Cashios. 00:13:45.360 --> 00:13:50.720 I used Roffus to uh flash my drive. I 00:13:48.399 --> 00:13:54.320 got the M.2 installed and now we're here. So far, the hardest part was 00:13:52.560 --> 00:13:59.040 getting it to boot to the flash drive. I've been super interested in trying 00:13:56.240 --> 00:14:04.560 Hyperland, but I think I'm going to keep that for maybe something on my laptop or 00:14:02.320 --> 00:14:07.440 something that I'm I'm I'm more happy to just play with. I'm going try to keep 00:14:05.920 --> 00:14:11.600 pretty much everything the same as what I'm used to except for Cashios and just 00:14:09.839 --> 00:14:17.600 see how it goes. You know what? Calling an Audible. Let's give it a shot. 00:14:14.240 --> 00:14:20.240 Lemonade or how I first read it with my 00:14:17.600 --> 00:14:24.800 broken brain is lime line. Sounds cool. Looks cool. Going to go with Grub. I'm 00:14:22.639 --> 00:14:29.440 just used to it. Right, we're in. Everything seems okay so far. Uh, I 00:14:27.680 --> 00:14:34.320 wonder how many times Lionus has bricked his install. >> All right, now that I have a working 00:14:32.240 --> 00:14:39.199 drive, this is great. Prompted to set up encryption right out of the gate. You 00:14:36.800 --> 00:14:44.399 love to see it. Pretty painless setup so far. Don't need this. 00:14:41.839 --> 00:14:50.160 This looks fine. Oo, we're in. Now I got to play a game. 00:14:47.440 --> 00:14:54.959 >> Oh, hey, there you go. Secure boot key added. Okay, well, let's do a reboot. I 00:14:52.320 --> 00:14:58.399 assume I just leave it on Fedora. What the 00:14:56.560 --> 00:15:03.279 frackle is this? Do I have to do the secure boot thing? Let's try this again. 00:15:00.880 --> 00:15:07.120 Error. You need to load the kernel first. Okay, maybe I should read the 00:15:05.279 --> 00:15:10.480 documentation. That's the error I was getting. So, we're going to use method 00:15:08.480 --> 00:15:14.560 B. Disable secure boot in the BIOS before proceeding and then reenable it 00:15:12.160 --> 00:15:18.320 after enrolling the key. I have to enter a command in the host terminal. Did I 00:15:16.800 --> 00:15:23.680 mess this up? You know what? I'm gonna try reinstalling it with secure boot 00:15:20.480 --> 00:15:25.920 enabled this time. And oh maybe I don't 00:15:23.680 --> 00:15:30.800 I don't want to do that. That takes so long. Okay. Well, let's let's try 00:15:28.560 --> 00:15:34.639 reinstalling Bazite from the beginning with secure boot on this time and we'll 00:15:32.959 --> 00:15:40.399 see if something's different. All right. I've reinstalled it. Documentation says 00:15:36.800 --> 00:15:43.199 to reboot, enroll the keys. Yes, it's 00:15:40.399 --> 00:15:47.360 just universal blue. I think I enabled it. Hey, there you go. I feel like I 00:15:45.680 --> 00:15:52.560 just went in a circle, but we'll let it cook. Hey, we're in. Okay, it did detect 00:15:50.320 --> 00:15:57.519 all three. I kind of have a weird one that's off to the side here, so I can 00:15:54.399 --> 00:16:00.320 like monitor chat when I do other stuff. 00:15:57.519 --> 00:16:02.959 Oh, okay. Not right now, Steam. That's kind of cool. I got Steam pre-installed. 00:16:01.680 --> 00:16:08.399 That'll be nice. Maybe I'll get a game up and running like real quick. All right, here comes the point where we 00:16:05.759 --> 00:16:12.959 tripped up last time. Well, that was painless. I'm almost there, but before I 00:16:10.800 --> 00:16:17.519 can game with this man, I'm going to need voice chat. So, we're getting 00:16:15.440 --> 00:16:22.079 Discord going. I already got Left 4 Dead 2 installed already. There's some 00:16:19.519 --> 00:16:26.560 slightly icky things. I have Discord working, which is super cool. What? 00:16:24.720 --> 00:16:32.320 Really? All right, I'm ready to launch the game. 00:16:29.360 --> 00:16:35.680 What is this? What is this? The Linux curse might be coming for me. Wait, it 00:16:34.240 --> 00:16:40.240 magically healed itself. Magically healed itself. Well, this is messed up. 00:16:37.360 --> 00:16:45.519 I've got my Discord volume at 200%. I've got Luke's individual user volume at 00:16:42.720 --> 00:16:51.199 170%. And I've got my system volume at 150%. And I can barely hear anybody. No, 00:16:48.320 --> 00:16:55.680 it's not you guys. It's me. I'm just experiencing Linux things. But hey, it 00:16:53.519 --> 00:16:59.199 could be worse. I could be that guy at Alan who's not running his game in full 00:16:57.680 --> 00:17:05.520 screen. Sup, Rob. All right, just rebooted and no game volume whatsoever. 00:17:02.720 --> 00:17:09.280 What about like a YouTube video? Okay. Okay, that's loud. That's loud. That's a 00:17:07.600 --> 00:17:12.160 good sign. That is so bizarre. Okay, let's see if Discord is solved. If 00:17:10.640 --> 00:17:15.760 Discord solved, we're good. And then Discord maybe just magically healed 00:17:14.160 --> 00:17:18.160 itself. What's up, gamers? Oh, we're good. >> So, did your audio just require a 00:17:17.679 --> 00:17:23.600 restart? >> It's complicated. My system was set to like spitif out. So, obviously that was 00:17:21.839 --> 00:17:26.720 why I was getting no audio in game, but that doesn't explain why I was getting 00:17:24.959 --> 00:17:30.640 extremely low audio in Discord. >> Yeah, that's strange. It's It's that 00:17:29.039 --> 00:17:34.559 problem of like why isn't this working and then why is this working? It's like 00:17:33.039 --> 00:17:38.400 >> Yeah. I'd rather have why isn't it working than why is it working? 00:17:36.720 --> 00:17:41.840 >> Oh, whoa, whoa, whoa. Why did that change it? Do you Whoa. Do you see that? 00:17:40.000 --> 00:17:45.679 Since I have a dual PC setup in my server rack, this is my streaming PC 00:17:43.919 --> 00:17:51.200 that records. I was actually getting ready to record and it's not quite 00:17:49.280 --> 00:17:55.280 scaled correct. Like you can see I'm missing like half my taskbar. That was 00:17:53.360 --> 00:17:59.360 not a scaling thing. This monitor is not 4K. So, I'm a little confused on why 00:17:57.280 --> 00:18:03.200 it's showing 4K as an option. I do normally set to 120 Hz, though. Oh, it 00:18:01.440 --> 00:18:06.880 made everything Oh, whoa, whoa, whoa. Why did that change it? Do you Whoa. Do 00:18:04.799 --> 00:18:12.080 you see that? It's scaled properly, but you know what scaled it properly is 00:18:09.039 --> 00:18:14.640 adjusting the frame rate. If I go to 140 00:18:12.080 --> 00:18:21.760 on my OBS capture, it's not scaled right. But if I change it to 120 and 00:18:18.480 --> 00:18:23.280 apply it, now it's scaled appropriately. 00:18:21.760 --> 00:18:26.720 Like my scaling is the same. My resolution's the same. Now that I got 00:18:24.799 --> 00:18:30.160 these displays configured, Steam looked like it was already installing. So, 00:18:28.559 --> 00:18:35.520 let's double check that. Dude, are we going to get a game going like that? I 00:18:33.520 --> 00:18:40.480 know it's not compatible. I'm still going to download it because I want to 00:18:37.520 --> 00:18:44.240 try it. I won't blame any Bite or Linux for it not working, but it's one of my 00:18:42.160 --> 00:18:48.799 go-to games right now. I need to test if PUBG is going to work. Do I need to 00:18:46.160 --> 00:18:52.080 enable the Proton compatibility later? Hey, it's enabled right away. Oh, yeah. 00:18:50.480 --> 00:18:55.280 Look, it like installed it right here. I guess while that's installing, maybe I 00:18:53.600 --> 00:19:00.240 can get some other apps going here. Discord. Hey, there it is. Oh, Discord 00:18:57.280 --> 00:19:04.640 is high risk. This app uses legacy X11 windowing system, which allows it to 00:19:02.240 --> 00:19:08.960 record all keystrokes captures. It also has access to the internet, meaning it 00:19:06.240 --> 00:19:13.200 could send your data to outside parties. Ooh, this is very timely. Well, I need 00:19:11.120 --> 00:19:17.280 Discord, so I'm installing it. that warning. As scary as it probably seems 00:19:14.960 --> 00:19:21.840 to a lot of people, I think it is kind of a cool thing that they're letting you 00:19:19.120 --> 00:19:25.760 know that it might be risky. So, if you're a non-experienced user going to 00:19:23.919 --> 00:19:29.520 download something, it could give you a heads up like, "Whoa, whoa, whoa." Just 00:19:27.360 --> 00:19:33.280 so you're aware for Discord, we already know they're stealing all our data 00:19:30.720 --> 00:19:38.960 anyways. I don't know. Wo, you can download Edge. Holy cow, you got to be a 00:19:35.440 --> 00:19:40.080 psychopath. High risk. 00:19:38.960 --> 00:19:46.640 Let's go through audio while everything's installing really quick. It's showing up is is huge. I hear the 00:19:44.480 --> 00:19:50.960 mic is going directly to the Roadcaster and the Roadcaster should just pass out. 00:19:48.640 --> 00:19:55.280 Hey, it's being detected. Wow, that was really fast. Really? I'm going to call 00:19:52.799 --> 00:19:58.080 my wife really quick. Hello. Hello. >> Yes, I can hear you. 00:19:56.240 --> 00:20:01.520 >> I didn't have to configure anything. That's a lot easier than I thought it 00:19:59.919 --> 00:20:05.280 was going to be. But hey, the fact that I didn't have to troubleshoot it makes 00:20:03.600 --> 00:20:11.360 me very happy. >> Just installed it. Instantly installed 00:20:07.360 --> 00:20:12.720 OBS. I had to restart my Roadcaster, but 00:20:11.360 --> 00:20:16.320 then it worked immediately. We'll see if the audio is fine. Seems like the audio 00:20:14.480 --> 00:20:20.400 was fine. Off to bigger and better things. So, I'm gonna uh get Teams 00:20:18.799 --> 00:20:25.039 installed here because I need to do a work call. Well, the Teams call went 00:20:22.320 --> 00:20:30.080 fine. Sort of. Teams is still a very annoying experience on Linux regardless 00:20:26.960 --> 00:20:32.640 of what Linux flavor you go with. 00:20:30.080 --> 00:20:38.799 There's no official app. Uh I was using the Teams for Linux open source 00:20:34.720 --> 00:20:40.880 community thing. It's like fine. There's 00:20:38.799 --> 00:20:44.000 some cludginess here and there. It seems like most of the community agrees that 00:20:42.400 --> 00:20:49.760 the best way to do it these days is to just run it through the browser entirely, which I really don't prefer, 00:20:48.240 --> 00:20:55.039 but I'm going to keep fighting with Teams for Linux and see if I can get it working in a state that I would like. I 00:20:53.280 --> 00:21:01.200 would say with the like install it real quick, sign in and it works perfectly. 00:20:58.480 --> 00:21:05.360 No, not quite. But at least they're doing it. Not like Microsoft's 00:21:02.960 --> 00:21:09.520 supporting it. So, I appreciate the effort. Another thing that I'd say is 00:21:06.799 --> 00:21:16.000 that gaming has been perfectly fine so far. Ha. Say this wire is working is 00:21:13.520 --> 00:21:21.600 working. No problem. Gaming so far going okay. No major hiccups with anything as 00:21:19.679 --> 00:21:26.480 of right now, but I'll let you know if things change. 00:21:24.320 --> 00:21:32.799 >> Well, uh, control altdelete doesn't do anything. Alt tab allows me to switch to 00:21:29.760 --> 00:21:36.400 things, but my mouse is not there. Like 00:21:32.799 --> 00:21:38.240 I'm hearing like re like in my ears. 00:21:36.400 --> 00:21:42.880 This is so awesome. I managed to play a game for 20 seconds. I must just be 00:21:40.480 --> 00:21:46.400 cursed. Like I just I have to be cursed at this point. Okay, I managed to find 00:21:44.640 --> 00:21:51.679 this. I'm going to try to end the process. Halflife 2, I think. Is this 00:21:49.760 --> 00:21:57.120 Hello, Delette. Is that not going to work? That's not going to do anything. 00:21:55.360 --> 00:22:01.760 >> Yeah, I have seven people waiting for me because I'm a special Linux snowflake 00:21:58.880 --> 00:22:08.080 right now. I I don't understand why trying to do the most basicst of things, 00:22:04.080 --> 00:22:10.080 launch a Valve game on a fresh install 00:22:08.080 --> 00:22:13.840 manages to be like this. I'm even on AMD, guys. I'm on AMD. I'm going back to 00:22:12.480 --> 00:22:19.840 Windows for now because this is just it's not acceptable. I have to be able to play the game right now. Okay, the 00:22:17.760 --> 00:22:24.880 last thing now. I think I'm just going to game. Ooh, it's got a borked rating. 00:22:22.640 --> 00:22:30.159 As of 2 weeks ago, someone said it's borked. So, 00:22:27.120 --> 00:22:32.080 yikes. I won't blame any Basite or Linux 00:22:30.159 --> 00:22:38.159 for it not working, judging by how long it's taking. That's not a good sign. Uh, 00:22:35.039 --> 00:22:41.039 a month without PUBG. Oh, okay. Well, 00:22:38.159 --> 00:22:44.159 let's launch Batro. Hey, there we go. >> All right, we finished the round. It's 00:22:42.480 --> 00:22:47.120 the next day and I'm going to see if I can figure out what the heck was going 00:22:45.840 --> 00:22:51.200 on there. >> Off to a great start. >> Closing the gap. 00:22:50.000 --> 00:22:54.480 >> All right, I'm just playing single player now. Let's see how this goes. All 00:22:53.039 --> 00:22:59.679 right, this is how far I made it last time. You good? 00:22:56.480 --> 00:23:00.400 >> Now you are playing with power. 00:22:59.679 --> 00:23:05.120 >> I just got to >> try running it in Vulcan. >> Unfortunately, there's no in-game 00:23:03.760 --> 00:23:10.799 setting for it, but apparently this will do the trick. >> Like you had to break through this wall. 00:23:08.480 --> 00:23:14.080 >> And there it is. That was the fix. Not complicated, but definitely frustrating 00:23:12.640 --> 00:23:18.559 when you consider that this is a first party Valve title and the buggginess is 00:23:16.880 --> 00:23:23.200 so immediately apparent when you try to play the game. And has also apparently 00:23:20.880 --> 00:23:26.240 been an issue since at least July of last year. 00:23:24.640 --> 00:23:29.600 To be clear, none of this is meant to discount the experiences that other 00:23:28.000 --> 00:23:34.159 people have. It's just to also acknowledge that not everybody has such 00:23:31.840 --> 00:23:36.880 a seamless experience. With Left 4 Dead Solved, our next challenge is going to 00:23:35.360 --> 00:23:40.799 be Hell Divers 2. We're going to be playing with the VIPs. I've never played 00:23:38.559 --> 00:23:44.640 before, so I'm finding so much weird stuff, dude. 00:23:43.039 --> 00:23:49.760 It like turned into two black Windows that then turned into this. Oh, wo, 00:23:46.960 --> 00:23:53.120 check this out. Why am I cursed like this? Opening cinematic played okay. 00:23:51.760 --> 00:23:58.400 Okay. And this looks promising other than the weird white line that I have at 00:23:55.280 --> 00:24:00.400 the left and top for some reason. Is the 00:23:58.400 --> 00:24:03.840 mouse supposed to do anything. >> Supposed to do something. 00:24:01.679 --> 00:24:08.880 >> Hold on. Here's an idea. Okay. So, look up. We can rebind that. Let's go. Left 00:24:06.320 --> 00:24:13.440 click. Okay. Hey, controller works. I guess I'm 00:24:11.520 --> 00:24:17.760 gaming on a controller, boys. So, I'm going to install Dolphin. Oh, wait. 00:24:15.679 --> 00:24:22.559 Dolphin's the name of their like the file manager, right? Oh, speaking of 00:24:20.000 --> 00:24:28.000 files, I should try to mount my network share. So, network shared folders. SMB. 00:24:25.360 --> 00:24:34.080 Oh, dude. Is it going to find it for me? Woah, it found it for me. Hell yeah. 00:24:31.520 --> 00:24:38.799 Add. Can I pin them to the side? Oh, I can. Oh, that's kind of nice. That was 00:24:36.480 --> 00:24:44.200 really easy to mount my network share. And these are SMB. Set as default app. 00:24:44.640 --> 00:24:52.080 Hey, there you go. Hey, I set VC as a default app. I'm feeling pretty decent 00:24:49.679 --> 00:24:57.520 right now. I have my audio working. I have a game running. I have my SMB share 00:24:54.559 --> 00:25:01.120 mounted. The most painful roadblock was by far like getting it to this point. A 00:24:59.919 --> 00:25:04.880 quick recap on what happened with the secure boot thing was I turned secure 00:25:02.960 --> 00:25:09.039 boot off because I thought that's what it needed when the fedora drive that I 00:25:07.279 --> 00:25:13.440 accidentally grabbed from work was asking for it. Then when I installed 00:25:10.640 --> 00:25:17.039 basite, it was, "Hey, turn secure boot on. I don't have it on. I have your 00:25:14.799 --> 00:25:21.600 key." But after I installed it, I think I might have gotten a little bit 00:25:18.320 --> 00:25:23.600 confused or chose the wrong thing when 00:25:21.600 --> 00:25:27.919 it asks me to enroll it. I needed to make sure that secure boot was on first. 00:25:26.240 --> 00:25:31.840 And now that it was on when I installed it, it was pretty painless. I do think 00:25:30.240 --> 00:25:37.279 it's a little weird that they still wanted me to type universal blue when I 00:25:34.880 --> 00:25:41.520 was enabling the keys. I'm not really sure why. I do wonder how much it'll 00:25:39.760 --> 00:25:46.000 help me in the future if there's a software or a game that requires secure 00:25:43.679 --> 00:25:51.039 boot. I I wonder if Lionus is going to have as smooth of a time or if his is 00:25:48.640 --> 00:25:55.120 going to be a little bit worse. >> Well, this is remarkable. I'm up to 00:25:52.720 --> 00:25:58.559 three steam Windows now. Nope. Can't type. After I figured out the control 00:25:56.880 --> 00:26:01.840 issues, we did manage to get through the entire Hell Divers mission with no 00:26:00.320 --> 00:26:06.240 further complications. So, while I wouldn't call today a success, it also 00:26:04.559 --> 00:26:10.159 wasn't a complete failure. And I think I'm ready to do a little bit more 00:26:08.080 --> 00:26:13.679 Googling, learn a bit more, figure out what the heck is going on with my Steam 00:26:11.760 --> 00:26:17.279 interface here. Now, it is worth noting that while I am obviously showing a lot 00:26:15.520 --> 00:26:20.480 of the problems I'm having today, I'm not trying to make Linux look bad or 00:26:18.720 --> 00:26:25.919 anything, and there were aspects of the experience that were much better. For 00:26:22.720 --> 00:26:27.760 instance, setting up Hop OS involved 00:26:25.919 --> 00:26:30.880 none of my data being given away. And maybe more importantly, if you don't 00:26:29.120 --> 00:26:35.039 like futing about with things, is I had to do nothing to get all of my various 00:26:33.120 --> 00:26:38.880 devices working. No going to the manufacturer's website, downloading 00:26:36.480 --> 00:26:42.080 drivers, none of that nonsense. the convenience of the Cosmic Store and it 00:26:40.640 --> 00:26:46.000 being something I might actually want to use, unlike the Windows Store. Pretty 00:26:44.240 --> 00:26:50.320 nice. And so far, I've got to give it credit for being pretty darn intuitive, 00:26:47.679 --> 00:26:56.320 other than maybe the pressing the power button to reach my settings that has 00:26:52.960 --> 00:26:58.240 like Windows 95 her you press start to 00:26:56.320 --> 00:27:00.960 shut down kind of energy. With all that said, I'm excited about the next month 00:26:59.679 --> 00:27:06.960 and I hope you guys are excited to come along with us and excited to hear about our sponsor, 00:27:04.480 --> 00:27:10.559 Meter. As your company grows and branches out around the world, you'll 00:27:08.720 --> 00:27:15.520 need a network that can scale with your operations. Juggling different ISPs, 00:27:13.200 --> 00:27:19.760 vendors, and all the necessary tools you need can be a massive time sync. Well, 00:27:18.000 --> 00:27:24.159 Meter can help you build enterprise levels from the ground up that work with 00:27:21.840 --> 00:27:28.480 wired and wireless networks as well as cellular all in one platform with 00:27:26.400 --> 00:27:32.880 predictable and transparent pricing. They even design, deploy, and manage the 00:27:30.880 --> 00:27:37.279 entire network end to end. Whether that's across multiple warehouses or on 00:27:35.279 --> 00:27:44.600 something like a large campus. To learn more, go to meter.com/LTT 00:27:39.679 --> 00:27:44.600 to book a demo today. That's me.com/LTT 00:27:44.880 --> 00:27:51.440 to book a demo. If you guys enjoyed this video, why not check out the first 00:27:48.799 --> 00:27:55.600 episode of the last Linux challenge. Some stuff is kind of the same in that I 00:27:53.840 --> 00:27:58.960 seem to be cursed, but other stuff is different. I did get Pop OS installed 00:27:57.760 --> 00:28:02.640 this time. >> Uh, how refraining is it? It looks 00:28:01.120 --> 00:28:05.440 >> It doesn't look straight. I mean, there's That's probably the straightest 00:28:04.159 --> 00:28:09.360 thing about what's going on right now, though. 00:28:07.360 --> 00:28:13.840 >> Are you going to eat in a box? What are you doing? Panini, 00:28:11.760 --> 00:28:18.240 were you in the shot the whole time? Panini, 00:28:14.960 --> 00:28:21.039 >> the Honkers Railway. Oh, it's that 00:28:18.240 --> 00:28:21.039 Honkai star rail.