[00:00.000 --> 00:15.360]  Alright, so I'm Derek, and I originally hail from New London, Connecticut, where, you know, my love for technology first took root back in the mid-90s when I was a youngster.
[00:15.740 --> 00:21.160]  And back then I was always kind of hacking, tinkering with computers and phone systems.
[00:21.760 --> 00:29.280]  When I was about 16, I was fortunate to meet a couple of mentors that I'd met at a local Linux user group meeting.
[00:30.200 --> 00:31.580]  One of them is here right now.
[00:31.800 --> 00:32.320]  His name is Roy.
[00:32.960 --> 00:35.020]  And the other one, his name is Brian.
[00:35.240 --> 00:41.920]  And unfortunately, he left us a few weeks ago.
[00:42.160 --> 00:42.900]  So fairly recent.
[00:43.160 --> 00:50.040]  So anyway, they taught me about electronics and, you know, introduced me to programming.
[00:51.180 --> 00:56.040]  And so then after, whoops, sorry about that.
[00:56.520 --> 00:57.680]  Getting used to the controls here.
[00:58.580 --> 01:00.620]  Okay, let me dial this in here.
[01:02.160 --> 01:09.200]  So yeah, after high school, I served six years in the Army National Guard as an electronics technician.
[01:10.320 --> 01:13.620]  That experience helped me kind of further hone my skills and technology.
[01:14.900 --> 01:22.780]  And eventually I transitioned into the IT field and beginning in what I finally call my soul-sucking help desk career.
[01:24.420 --> 01:27.080]  So, you know, I was at a telecom company.
[01:27.400 --> 01:28.860]  So that was fun.
[01:30.300 --> 01:35.880]  Now I work as a security analyst for a small company out in Wisconsin.
[01:37.380 --> 01:40.280]  So with, I'm out there with my wife and three kids.
[01:41.940 --> 01:45.540]  And I just love instilling a love of technology in them.
[01:46.140 --> 01:49.440]  So we do all kinds of little fun projects.
[01:49.540 --> 01:50.380]  I try to get them involved.
[01:50.920 --> 01:54.420]  Getting introduced to scratch programming.
[01:55.240 --> 01:57.880]  A little bit of Arduino tinkering and things like that.
[01:58.420 --> 01:59.820]  Just mostly basic stuff.
[01:59.820 --> 02:01.840]  Let's get like LEDs to work and things like that.
[02:02.820 --> 02:11.420]  One of my favorite memories fairly recently was I took my kids to Hack for Kids out at the CypherCon conference in Milwaukee.
[02:11.920 --> 02:22.020]  And my oldest daughter at the time, she went to lock picking and she learned how to rake a four pin lock.
[02:22.180 --> 02:26.980]  And she was working on the fifth pin lock before we had to get kicked out.
[02:27.420 --> 02:29.620]  So I'm real proud of her for that.
[02:29.620 --> 02:30.300]  That was pretty awesome.
[02:34.530 --> 02:36.050]  I'm all over with this mouse here.
[02:37.470 --> 02:37.870]  Whoops.
[02:38.870 --> 02:39.510]  Oh boy.
[02:39.790 --> 02:39.990]  Okay.
[02:45.070 --> 02:49.910]  So my other two kids, my middle daughter, she's fairly inquisitive.
[02:50.150 --> 02:55.370]  And then my five-year-old, he's going to grow up and be an engineer, I think.
[02:56.530 --> 03:00.550]  In the middle here, that's a picture of him with his Lego motherboard he made.
[03:01.050 --> 03:02.790]  And I don't know where he picked that up.
[03:02.790 --> 03:05.210]  I wasn't like sitting there showing him motherboards or anything.
[03:05.490 --> 03:07.030]  So he just like showed me that.
[03:07.130 --> 03:09.350]  And I'm like, he's got bus lines and everything.
[03:09.450 --> 03:10.170]  I'm like, this is crazy.
[03:13.530 --> 03:14.090]  All right.
[03:16.030 --> 03:18.370]  So why do this?
[03:18.630 --> 03:22.890]  Well, so Chromebooks weren't even originally on my radar.
[03:23.390 --> 03:30.530]  The spark for this happened when my wife was on a hunt for affordable options for our kids.
[03:31.810 --> 03:37.270]  Because they get Chromebooks from their school, but we wanted them to have something they could actually use.
[03:38.230 --> 03:44.590]  And, you know, something to learn and play on, right?
[03:44.790 --> 03:56.450]  And so my wife found some used Chromebooks and at a great price because used Chromebooks are ridiculously cheap, which is kind of an awesome price point.
[03:56.910 --> 04:03.230]  And so upon receiving them, we found out that the version of Chrome OS that they had was end of support.
[04:04.330 --> 04:10.490]  So knowing my penchant for Linux, putting Linux on things, as it were, my wife suggested that I do that.
[04:10.690 --> 04:16.490]  So then that's kind of when I started my adventure into this.
[04:18.570 --> 04:21.890]  I discovered real quickly how limited these devices were.
[04:24.290 --> 04:29.270]  And with the exception of one, which I have here with me that I'll kind of demo in a little bit.
[04:30.790 --> 04:33.070]  It's got a removal M.2 drive.
[04:33.250 --> 04:36.450]  Everything else was surface mount soldered to the motherboard on these things.
[04:37.090 --> 04:38.590]  Limited to like four gigs.
[04:38.990 --> 04:40.950]  I don't even remember what the hard drive size was.
[04:41.570 --> 04:43.090]  It's like just really tiny.
[04:43.230 --> 04:45.170]  I think it was like 64 gigs or something.
[04:45.290 --> 04:45.930]  I don't even know.
[04:47.770 --> 04:49.330]  So really, really tiny.
[04:49.590 --> 04:52.210]  So, but I couldn't resist a challenge.
[04:52.770 --> 05:00.210]  I wanted to see what I could do with these seemingly underwhelming devices, see if I could turn them into something, you know, cool and hopefully useful.
[05:04.490 --> 05:14.530]  So for this project, yeah, I used an Acer, well, two Acer models that were C731 and C740 models.
[05:14.530 --> 05:19.550]  And then this I have here is an Lenovo N23.
[05:19.910 --> 05:23.930]  So this one's like the slightly better version out of those three older model.
[05:25.610 --> 05:30.950]  I also explored a newer Acer C433T model.
[05:32.010 --> 05:41.410]  And early on, I realized that Google had designed these things with just significant restrictions, making it necessary to remove these before proceeding with anything else.
[05:41.410 --> 05:43.730]  So a little quick disclaimer here.
[05:44.350 --> 05:50.790]  Don't do this on devices you don't own, because you will avoid warranties and possibly break things.
[05:54.750 --> 06:02.110]  Ideally, older Chromebooks are, I found, best for this project, at least when you're kind of figuring things out with them.
[06:03.150 --> 06:16.010]  I'm going to share my journey kind of figuring this out and remove these restrictions and kind of go over what's needed to replace Chrome OS with Linux to make these things more like traditional computers.
[06:18.270 --> 06:22.690]  So while Google's efforts, you know, to...
[06:24.490 --> 06:26.810]  Recently, they've had pushback, right?
[06:26.970 --> 06:28.850]  You know, it's like, oh, into support, right?
[06:29.010 --> 06:31.550]  And it's like these things basically become e-waste.
[06:31.750 --> 06:33.450]  Well, nobody likes that.
[06:34.830 --> 06:37.850]  So, you know, they've extended support on the newer models.
[06:39.010 --> 06:43.530]  You know, they've even improved the hardware and enabled running Android apps.
[06:45.630 --> 06:49.670]  But I'm not really a fan of the Google ecosystem.
[06:50.230 --> 06:54.730]  You know, kind of the control, the tracking they do, it's kind of creepy.
[06:57.070 --> 07:04.350]  And to kind of underscore the importance of this project, I'm going to kind of cite an article here from The Verge.
[07:05.250 --> 07:15.210]  It discusses the challenges faced by school districts using Chromebooks, such as repairability issues, auto-update expiration dates, and e-waste concerns.
[07:15.550 --> 07:17.330]  So the U.S.
[07:17.610 --> 07:24.210]  Public Interest Research Group Education Funds report Chromebook churn.
[07:24.690 --> 07:32.530]  And it highlights the financial and environmental impacts of Chromebooks reaching end-of-life prematurely.
[07:32.530 --> 07:40.490]  So it emphasizes the difficulties in obtaining replacement parts and the high costs of repairs.
[07:41.490 --> 07:49.850]  The report also raises concerns about the short auto-update expiration dates leading to the e-waste and increased costs for schools.
[07:50.710 --> 08:06.530]  PERG suggests eliminating the automatic update expiration system, increasing the availability of replacement parts, and promoting the use of alternative operating systems like Linux to extend the lifespan of the Chromebooks.
[08:08.870 --> 08:22.290]  And so Google has responded by emphasizing its efforts to extend years of guaranteed support for Chromebooks and its commitment to sustainability through regular software updates and eco-friendly manufacturing practices.
[08:24.230 --> 08:25.830]  I'm sorry if I sound like a robot.
[08:30.620 --> 08:36.080]  Okay, so I kind of wanted to dive into a little bit of the history here, kind of like how we got here, right?
[08:37.320 --> 08:40.140]  So how did these Chromebooks get so prevalent, right?
[08:40.940 --> 08:42.760]  Namely in academia, right?
[08:43.000 --> 08:45.640]  That's where we're seeing these things popping up all over the place.
[08:47.320 --> 08:52.840]  So on May 2011, or excuse me, May 11th, 2011, at the Google I.O.
[08:52.960 --> 08:56.560]  conference in San Francisco, a new kind of laptop was introduced.
[08:56.560 --> 08:57.720]  The Chromebook, right?
[08:57.840 --> 08:59.200]  Developed by Samsung and Acer.
[09:00.000 --> 09:05.820]  These devices were built around Chrome OS, an operating system essentially centered on the Chrome web browser.
[09:06.220 --> 09:09.660]  Initially, there was a lot of skepticism about their potential.
[09:10.960 --> 09:16.680]  Initial reactions, you know, early on were doubtful.
[09:17.660 --> 09:25.840]  So Dan Ackerman, a tech journalist, recalled seeing Chromebooks as a step back from netbooks.
[09:26.940 --> 09:29.800]  They were priced between $349 and $499.
[09:29.800 --> 09:38.980]  These early Chromebooks seemed like limited web browsers, unable to run traditional software, leading many to question their usefulness.
[09:41.300 --> 09:44.420]  So the first steps were budget-friendly but basic.
[09:44.960 --> 09:52.560]  The first Chromebooks faced the challenges that, you know, they were praised for being free of bloatware, common on Windows laptops.
[09:53.400 --> 09:56.260]  But their limited functionality led to frustration.
[09:56.600 --> 10:01.180]  Simple tasks like opening zip files were problematic due to unsupported formats.
[10:01.680 --> 10:07.880]  Early reviews were lukewarm, often comparing them unfavorably to netbooks and tablets at the time.
[10:08.600 --> 10:13.800]  Turning the corner, adaptation and innovation, you know, over the years, Chromebook evolved.
[10:13.800 --> 10:21.200]  And by 2017, Samsung Chromebook Pro marked a significant breakthrough.
[10:21.460 --> 10:22.660]  It was priced at $550.
[10:22.940 --> 10:26.920]  It featured a sleek design, high-resolution touch screen, and a built-in stylus.
[10:27.760 --> 10:36.560]  Crucially, it introduced access to the Google Play Store, allowing users to run Android apps, addressing one of the biggest early criticisms.
[10:37.860 --> 10:40.960]  Which I'm going to kind of poke fun at some of that stuff here in a little bit.
[10:44.100 --> 10:46.660]  And then cue the pandemic, right?
[10:46.820 --> 10:48.580]  So it was a catalyst for change.
[10:48.700 --> 10:52.840]  In 2020, COVID-19 changed everything.
[10:53.100 --> 10:54.980]  You know, we're all basically sent home.
[10:55.140 --> 10:59.700]  And so with schools and offices closing, millions shifted to remote work and learning.
[11:00.480 --> 11:06.480]  Suddenly, you know, the affordable web-based Chromebooks became indispensable to families.
[11:06.840 --> 11:11.940]  You know, they needed multiple laptops and Chromebooks were cost-effective.
[11:12.720 --> 11:17.640]  So it was perfect for essential online tasks required for remote work and education.
[11:20.140 --> 11:28.340]  So kind of today, by 2021, Chromebooks had firmly established themselves as vital tools for students, workers, and everyday users.
[11:28.340 --> 11:33.480]  They offered a blend of affordability, simplicity, and functionality, right?
[11:33.640 --> 11:39.600]  So Dan Ackerman noted that what was once seen as a secondary device had become a primary tool for many.
[11:41.080 --> 11:54.960]  The addition of Android app support turned Chromebooks into versatile machines capable of much more than just browsing the web, right?
[11:54.960 --> 11:55.040]  All right.
[11:57.180 --> 11:59.280]  So why hack your Chromebook with Linux?
[12:00.440 --> 12:07.800]  You know, for those of us that are, you know, tech enthusiasts and developers, there's even more potential.
[12:07.960 --> 12:16.340]  Hacking your Chromebook with Linux opens up, you know, a lot more possibilities, allowing you to run a broader range of software and development tools.
[12:16.340 --> 12:23.980]  This transforms the Chromebooks from simple, you know, browser-in-a-box and future e-waste into versatile and customizable devices.
[12:25.520 --> 12:32.040]  So, you know, Google did try to add value by allowing Android apps and Debian-based virtual machines.
[12:32.180 --> 12:35.300]  The limitations within Google's ecosystem remain.
[12:35.940 --> 12:41.660]  So by installing Linux, you can break free from these constraints and fully harness your Chromebooks capabilities.
[12:43.580 --> 12:54.800]  So embracing the full potential from humble beginnings to essential pandemic tools, Chromebooks have come a long way.
[12:56.080 --> 13:00.480]  Their journey is a testament of how technology can evolve, adapt, and meet changing needs.
[13:00.900 --> 13:06.120]  As Dan Ackerman highlights, the Chromebook story is one of those of resilience and innovation.
[13:06.900 --> 13:14.380]  For those looking to maximize their capabilities, installing Linux can offer great flexibility and functionality.
[13:15.480 --> 13:20.620]  Transforming these devices into versatile tools for various tasks.
[13:24.140 --> 13:29.080]  So, with that, I'm going to... we're going to dive into the steps and kind of how to make this happen.
[13:29.320 --> 13:33.960]  At least from the four Chromebook models that I've had experience with.
[13:37.840 --> 13:43.600]  Before we do that, though, I want to take a little satirical dig here.
[13:46.960 --> 13:51.040]  So, you know, I say it works on low-cost computers, right?
[13:51.360 --> 13:53.080]  And this is a defense of Chrome OS, right?
[13:53.520 --> 13:55.680]  So, tongue-in-cheek here, we're going to...
[13:55.680 --> 14:01.200]  Sure, you know, as long as you don't mind your computer struggling with anything more demanding than an open web browser.
[14:01.680 --> 14:04.240]  It's like multitasking, forget about it, you know.
[14:04.480 --> 14:06.180]  Good security with automatic updates.
[14:06.340 --> 14:10.140]  Yeah, because nothing says secure like having Google in control of your updates.
[14:11.160 --> 14:16.440]  You know, trusting Google with your data and updates is like trusting Dr. Evil with your world domination plans.
[14:16.860 --> 14:17.800]  What could go wrong?
[14:19.980 --> 14:23.120]  And then the running the Android apps.
[14:23.120 --> 14:26.860]  Oh, yes, because who doesn't love running phone apps on their laptops?
[14:27.240 --> 14:28.320]  It's a delightful experience.
[14:28.700 --> 14:34.940]  If you enjoy apps not optimized for a bigger screen and limited functionality, fast boot up.
[14:35.460 --> 14:40.240]  True, Chrome OS boots up fast just in time to remind you that it's still a glorified web browser.
[14:42.680 --> 14:44.960]  And then tight integration with Google services.
[14:45.560 --> 14:46.660]  Google knows best, right?
[14:47.500 --> 14:52.440]  Especially when it comes to tracking your every move and ensuring you're perpetually logged into their ecosystem.
[14:52.660 --> 14:53.540]  Privacy, what's that?
[14:55.980 --> 14:58.220]  So, real quick before moving on from this.
[14:58.420 --> 15:03.040]  You know, I do want to acknowledge that some people earnestly want to run Android apps on their Chromebook, right?
[15:03.120 --> 15:06.620]  That was one of the main pushback that people had when Chromebooks came out.
[15:07.800 --> 15:13.080]  While this is still possible, there are still limitations, right?
[15:13.440 --> 15:16.080]  Certain apps just aren't optimized to run on the desktop.
[15:16.820 --> 15:23.660]  That being said, there is a similar option available in Linux with the andbox snap package.
[15:24.760 --> 15:42.240]  So, I will have links and things like this available that I'm going to try to make a way to get on like a wiki or something somewhere to share with everybody that's interested in looking at these additional resources because I'm not going to go any deeper on the andbox project here.
[15:42.340 --> 15:46.680]  But I will have links available here.
[15:50.010 --> 15:56.450]  So, kind of as I mentioned earlier, you know, my biggest issue with Chrome OS and Google is just the unsettling level of tracking they employ.
[15:56.730 --> 15:59.570]  I mean, we already have to deal with this on our Android phones, right?
[15:59.570 --> 16:04.850]  I mean, it's... I don't need another device that does additional, you know, stuff.
[16:07.010 --> 16:07.910]  Where am I at on time?
[16:08.110 --> 16:08.230]  Whoa.
[16:13.290 --> 16:13.930]  All right.
[16:31.080 --> 16:35.320]  So, this is a couple of the limitations of Chrome OS I'm just going to kind of highlight here.
[16:35.320 --> 16:38.640]  You know, it's a lack of customization is one of the things.
[16:39.240 --> 16:46.820]  Users face severe limitations in customizing their desktop environment, system configuration, which can be frustrating for power users.
[16:47.260 --> 16:54.180]  App compatibility and consistent performance on Android apps on Chrome OS can lead to less than an ideal experience.
[16:55.100 --> 16:59.980]  The presence of two separate app stores, you have the Google Play Store and the Chrome Web Store.
[16:59.980 --> 17:02.060]  That can be confusing for users.
[17:03.940 --> 17:04.900]  Software compatibility.
[17:05.160 --> 17:08.540]  Chrome OS may not support demanding programs like Photoshop or video editing.
[17:08.700 --> 17:11.460]  I think that's really more of a limitation on the hardware.
[17:13.000 --> 17:23.760]  You know, obviously the Chrome OS may not as well, but the hardware on a lot of these devices, especially the older ones, are not up for those tasks.
[17:25.960 --> 17:26.740]  Cloud storage.
[17:26.920 --> 17:29.740]  So, you have limited onboard storage, so you heavily rely on the cloud.
[17:29.740 --> 17:35.060]  Such as Google Drive and may run out quickly for users.
[17:35.300 --> 17:38.180]  So you have limited local file system access.
[17:38.680 --> 17:47.360]  Chrome OS has restrictions, restricted access to the local file system, which can be a drawback for users needing .
[17:50.780 --> 17:54.160]  I can't guarantee that what I'm proposing will fix all these problems.
[17:54.600 --> 17:57.540]  I just think our chances will be better with a different approach.
[18:02.160 --> 18:09.560]  So, now that we've kind of covered the why and the limitations of Chrome OS, take a high-level look at the steps that I'm going to go over here.
[18:10.180 --> 18:26.780]  I've kind of broke it down like we have gathered Chromebook specifications, remove the hardware, software read-write protections, enter developer mode, flash to firmware for boot sequence control, enable boot from USB, create the boot bootable USB, install Linux, and then troubleshoot the inevitable problems.
[18:33.220 --> 18:40.740]  So, when hacking a Chromebook to run Linux, understanding your device's specifications is crucial for several interconnected reasons.
[18:40.740 --> 18:54.520]  During my journey, I spent countless hours scouring sites like MrChromebox.tech, Chromebook, and Reddit to ensure that, you know, my hardware choices would support the Linux distributions I was considering, and even then it wasn't perfect.
[18:55.500 --> 19:04.020]  So, first and foremost, knowing your Chromebook specifications ensures that, you know, you've chosen a compatible distribution.
[19:05.920 --> 19:11.620]  Different models have varying hardware configurations, and this information helps in selecting the right distribution.
[19:13.040 --> 19:22.240]  Verifying your Chromebook meets the specific hardware requirements of Linux distribution is vital to prevent installation or performance issues.
[19:22.440 --> 19:27.700]  I found that these Chromebook, the hardware on these things is like all over the place, you know.
[19:27.840 --> 19:34.800]  So, anything we can do to try to like mitigate that, you know, all the better.
[19:34.800 --> 19:43.900]  So, some Linux distributions require, you know, specific firmware versions for BIOS or UEFI updates.
[19:44.900 --> 19:49.820]  So, you know, understanding this helps determine the compatibility.
[19:50.300 --> 19:52.740]  I just want to ensure a smooth transition.
[19:53.720 --> 19:57.440]  Identifying any proprietary hardware components is essential for driver support.
[19:57.980 --> 20:02.700]  I'm still dealing with some driver issues with one of the Chromebooks.
[20:03.800 --> 20:05.580]  Well, the newer Chromebook, anyway.
[20:06.840 --> 20:10.420]  And so, obviously, you know, understand this helps optimize it.
[20:11.080 --> 20:11.840]  Excuse me.
[20:12.460 --> 20:15.340]  Selecting a distribution optimized for the configuration.
[20:18.160 --> 20:18.720]  So...
[20:20.320 --> 20:28.300]  This is a Chromebook read-write protection kind of like timeline, if you will, for the... based on kind of the generations of Chromebooks.
[20:28.300 --> 20:35.620]  So, the early models, 2012 to 2013, had like physical jumpers and switches on the motherboard.
[20:36.260 --> 20:41.160]  And then you have 2014 through 2017, they had screws.
[20:42.660 --> 20:58.940]  And then you had the 2017-plus CR50 models that basically have like either a battery sense line or you have to kind of use like a SUSE-Q cable type configuration to deal with that.
[20:59.020 --> 21:02.400]  There was actually somebody here at the con that was just dealing with that.
[21:02.400 --> 21:07.100]  They did do the SUSE-Q method to go over that.
[21:07.540 --> 21:07.900]  So, let me see.
[21:08.120 --> 21:09.440]  Now, that kind of went off.
[21:09.580 --> 21:11.000]  Let me just find where I'm at here.
[21:12.760 --> 21:20.240]  So, most of the models that I used for this project fall in that kind of middle category, the pre-CR50 one.
[21:21.620 --> 21:26.120]  There's one newer one that was kind of that 2017 model.
[21:26.140 --> 21:29.020]  And I was able to just remove the battery from it.
[21:29.020 --> 21:32.820]  And that was enough to allow me to flash it.
[21:33.220 --> 21:36.360]  So, let's see.
[21:47.150 --> 21:47.690]  Okay.
[21:47.850 --> 21:50.710]  So, removing the read-write protections.
[21:51.990 --> 21:55.130]  So, again, the models I have, we have a screw.
[21:55.130 --> 21:59.170]  So, this is my daughter pointing out where the screw was on this one.
[22:02.770 --> 22:13.070]  So, disabling it requires, you know, bypassing the physical mechanisms like, you know, screws or jumpers, disconnecting the battery, or using the SUSE-Q cable that I mentioned.
[22:14.030 --> 22:15.690]  This can be disabled through...
[22:15.690 --> 22:25.050]  And then the software-write protection can be disabled through the firmware commands, allowing it to modifications for... to read-only regions.
[22:26.130 --> 22:28.510]  So, the importance...
[22:28.510 --> 22:42.310]  Custom firmware disabling write protection is necessary for flashing the custom firmware or modifying the Google, or excuse me, the boot behavior Google binary block.
[22:42.310 --> 22:45.790]  I spelled that out because there's a little bit of a mouthful.
[22:48.390 --> 22:56.850]  So, what GBB flags do are shorten the developer mode, boot screen timeout from 30 seconds to 1 second, and remove the beep.
[22:57.670 --> 23:02.970]  Prevents accidental disablement of developer mode via space bar.
[23:03.930 --> 23:09.830]  Force enablement of legacy boot mode, regardless of cross-system flag value.
[23:09.830 --> 23:17.570]  So, set legacy boot mode as the default boot path negates the need to use Control-L.
[23:18.530 --> 23:28.190]  And then troubleshooting, enabling modifications, and it facilitates troubleshooting and recovery process in case of firmware-related issues.
[23:29.210 --> 23:42.170]  Disabling write protection typically involves steps like entering developer mode, manipulating hardware, and using specialized tool like the case-closed debugging feature on the CR50 models devices.
[23:42.650 --> 23:49.530]  So, the CR50 firmware runs on the Google security chip and supporting closed-case debugging.
[23:54.660 --> 23:56.840]  So, personal experience here.
[23:56.980 --> 23:58.660]  I got my daughter, Elena, involved.
[23:59.120 --> 24:05.360]  So, identifying and locating the jumper screw was straightforward for the three older model of Chromebooks that we had.
[24:06.100 --> 24:13.880]  Typically, the screw could be identified by its distinctive contact or a larger head, sometimes marked by silk screen, but this wasn't always reliable.
[24:15.240 --> 24:22.280]  On the first Chromebook, I found a picture online pointing out the screw, but for the other models, I had to rely on visual inspection.
[24:24.260 --> 24:30.680]  The newer 2022 model had a read-write protection tied to the battery sense line.
[24:30.840 --> 24:32.100]  I think I mentioned that earlier.
[24:32.300 --> 24:34.040]  So, I removed the battery.
[24:34.960 --> 24:42.360]  And, you know, the process was a lot more engaging when I had Elena search for the screw with me, so that, you know...
[24:42.360 --> 24:46.060]  And then I had her carefully remove it, and I wanted to get her kind of hands-on.
[24:46.060 --> 24:53.800]  So, you know, this was a nice experience, a bit of an introduction for a little bit of hardware hacking for her.
[24:55.460 --> 25:06.800]  And I'm briefly going to touch on the CZQ method because, like, I didn't use it, but I do want to point out that, you know, it's a valuable technique for devices that require it.
[25:06.800 --> 25:16.580]  So, the fine folks at crulturebook.com provide a comprehensive guide on this method for unbricking and flashing firmware.
[25:17.600 --> 25:22.880]  So, real quick, you know, the abstract on crulturebook.com is, you know, that...
[25:22.880 --> 25:34.180]  The article on crulturebook.com details, you know, these requirements and steps for the CZQ cable to flash a Chrome OS device with CCD enabled.
[25:34.180 --> 25:43.440]  So, this includes necessary hardware like the USB-C debug cable and a secondary device running Linux-based OS.
[25:44.140 --> 25:58.260]  This process involves disconnecting the external power, removing the Chromebook's bottom cover, disconnecting the battery, and setting up a Linux environment to install and use the flash ROM utility.
[25:58.260 --> 26:08.080]  So, after connecting the CZQ cable, the guide explains how to verify the connection, open the CCD state, and choose the appropriate firmware file to flash.
[26:08.500 --> 26:16.960]  It also covers, you know, preserving the device's vital product data and the steps to safely flash the firmware.
[26:16.960 --> 26:25.020]  This guide is an excellent resource, along with MrChromebox.tech, for, you know, anyone looking to kind of hack Chromebooks.
[26:25.660 --> 26:28.860]  Offering detailed instructions and support for various Chromebook models.
[26:29.940 --> 26:35.960]  Again, I'm going to have kind of just links to all these resources you can read, dive into it a little bit more.
[26:39.470 --> 26:43.170]  So, next we kind of engage the developer mode.
[26:44.450 --> 26:58.650]  So, developer mode grants users elevated privileges, enabling them to modify system settings or install custom software, crucial for disabling software firmware protection.
[26:58.650 --> 27:09.790]  So, the activation process, you enter recovery mode by pressing and holding the escape, refresh, and pressing power.
[27:10.490 --> 27:13.650]  And then pressing control D to enter developer mode.
[27:13.650 --> 27:21.570]  And then confirming, you know, when prompted, it's going to essentially do like a bit of like a factory reset.
[27:21.570 --> 27:30.090]  So, upon the first boot, the system securely wipes all user data, ensuring a clean transition to the developer mode.
[27:30.690 --> 27:38.230]  So, access to advanced features, developer mode unlocks additional functionality and customization options not available in standard mode.
[27:39.350 --> 27:45.750]  Users gain greater control over their devices, allowing for experimentation customization according to their needs.
[27:45.750 --> 27:53.650]  Entering developer mode entails certain risks, such as potential data loss during the transition process.
[27:53.970 --> 27:57.410]  Users should ensure they understand the applications before proceeding.
[28:00.340 --> 28:02.120]  So, then we flash the firmware.
[28:03.280 --> 28:12.840]  So, flashing firmware on Chrome OS devices can unlock, you know, various capabilities such as dual booting, which I had somebody ask me about that actually.
[28:12.840 --> 28:17.480]  I personally haven't felt the need that I want to try to dual boot these things.
[28:20.120 --> 28:29.320]  But this is a great script here that allows you to do just that, as well as the full ROM wipe, which is kind of what I did.
[28:29.580 --> 28:33.300]  So, I'm going to find where I'm at on my slide here.
[28:33.300 --> 28:38.840]  But, yeah, I was kind of going through all these options here.
[28:38.860 --> 28:46.380]  But essentially, for the sake of time here, I'm going to not go over all that.
[28:46.660 --> 28:53.480]  So, essentially, what I did, the full ROM version, and that allowed me to, you know, replace the OS completely.
[28:55.840 --> 29:11.380]  So, my personal experience with the full ROM firmware, the flashing involved using the full ROM version completely to replace the stock firmware on the 2022 ACES C433 T Chromebook.
[29:11.500 --> 29:13.000]  That's, you know, the newer one.
[29:13.860 --> 29:21.360]  Initially, I encountered difficulties because I was trying to figure out how to use the cross shell, because that's what I did on the older ones.
[29:21.980 --> 29:24.680]  And instead, it required the VT2 terminal.
[29:24.900 --> 29:28.060]  So, this mistake led to, you know, several failed attempts.
[29:31.220 --> 29:41.340]  So, flashing firmware on the older models, like the ACER C731, 740, and this Lenovo, was considerably easier due to the simpler read-write protection methods.
[29:41.340 --> 29:45.600]  You know, these devices used screws or jumpers to disable the hardware.
[29:46.000 --> 29:51.800]  Write-Protect, making the process more straightforward compared to the newer models, requires more advanced techniques.
[29:56.210 --> 30:04.170]  So, you know, kind of always ensure that you're in the correct terminal environment based on the model that you're working with.
[30:04.170 --> 30:08.130]  So, you know, before attempting to run the firmware utility script.
[30:08.510 --> 30:16.390]  So, just make sure you back up your stock firmware before flashing the full ROM to safeguard against any potential issues, in case you need to kind of revert back.
[30:18.810 --> 30:27.610]  Enabling USB support on Chrome OS devices, you know, crucial for, you know, being able to boot it and load the OS.
[30:27.610 --> 30:33.390]  Now, I've noticed that some of these devices actually don't have a USB drive at all.
[30:33.450 --> 30:37.210]  So, that's another challenge to overcome in and of itself.
[30:37.410 --> 30:40.870]  But for my purpose, with the Chromebooks I had, they all had USB.
[30:41.390 --> 30:47.630]  So, you know, again, I kind of touched on, you know, it's like the cross method.
[30:47.630 --> 31:02.410]  So, that's essentially, you access that by doing like Ctrl-Alt-T, and then, you know, you type shell, and then you get your root privileges by typing sudo su, right?
[31:02.650 --> 31:16.070]  And then you execute this command, slash user, slash lab excc, slash debug d, slash helpers, slash dev, underscore features, underscore USB, underscore boot, right?
[31:16.070 --> 31:17.810]  So, that's why, like, I wrote all this stuff down.
[31:17.870 --> 31:19.970]  Because, I mean, I'm not remembering all that off the top of my head.
[31:22.790 --> 31:25.770]  But, you know, so that's the method for the older models.
[31:25.990 --> 31:36.550]  Now, the VT2 method I was babbling about earlier, to kind of get into there, you have to do the Ctrl-Alt, refresh, or the right arrow key, and then log in as Kronos.
[31:36.550 --> 31:39.770]  And then use sudo dash I to get your root prompt.
[31:40.250 --> 31:53.270]  And then you need to set the dev underscore boot underscore USB flag to one, using this cross system, dev underscore boot underscore USB equals one command.
[31:54.450 --> 31:58.030]  So, that's going to be more suitable for the newer models.
[32:00.630 --> 32:05.170]  And then, you know, yeah, I've got a bunch more.
[32:05.890 --> 32:08.510]  Yeah, I would just say document the steps as you go.
[32:08.770 --> 32:12.270]  That was one of the things I wasn't always the best at.
[32:12.410 --> 32:15.130]  I kind of just jumped in and got myself into trouble a lot.
[32:15.310 --> 32:18.690]  Because, you know, I should have documented a little better as I went.
[32:18.930 --> 32:21.050]  So, lessons learned, so to speak.
[32:21.810 --> 32:24.590]  All right, so I'm going to move on.
[32:24.810 --> 32:25.990]  So, sorry.
[32:28.070 --> 32:28.950]  Vocal fillers.
[32:30.790 --> 32:35.550]  So, yeah, the first attempt to create the bootable USB, they could be relatively straightforward.
[32:35.930 --> 32:38.630]  I tried using, I don't know, Rufus or whatever.
[32:38.810 --> 32:40.530]  And that failed multiple times.
[32:40.630 --> 32:42.770]  I was like, I couldn't figure out why that wasn't working for me.
[32:42.850 --> 32:44.730]  Anyway, so then I grabbed Balena Etcher.
[32:45.330 --> 32:48.290]  And I was able to just boom, boom, boom, three-step process.
[32:48.390 --> 32:49.630]  And that worked.
[32:52.950 --> 32:54.210]  So, just real quick.
[32:54.370 --> 32:57.470]  I'm just going to kind of highlight the distros that I used for this project.
[32:57.750 --> 33:06.010]  I used the Ubuntu 2204 LTS, which I found out later was end of development.
[33:06.050 --> 33:08.630]  So, I'll talk about that in a minute, too, if I have time.
[33:09.510 --> 33:16.630]  And then, Ubuntu 2204 LTS, which is, you know, lightweight distro.
[33:20.450 --> 33:24.830]  So, when I first attempted to install Ubuntu on my Chromebook, I was filled with excitement.
[33:24.830 --> 33:29.250]  Only to be quickly deflated by hardware limitations that made the installation fail.
[33:30.550 --> 33:34.590]  Determined to find a solution, I turned to Gallium OS, known for its Chromebook compatibility.
[33:35.450 --> 33:39.190]  However, my first attempt at installing Gallium OS also ended in failure.
[33:39.930 --> 33:48.090]  I faced a range of frustrating audio issues with Ubuntu, and sometimes I'd get annoying horn noise or no sound at all.
[33:49.490 --> 33:56.230]  But after some persistent troubleshooting, I managed to resolve the sound issues on a couple of the older Chromebook models.
[33:56.230 --> 34:02.230]  And finally, I tried installing Gallium OS, and this time it worked flawlessly.
[34:02.870 --> 34:06.850]  No audio, no issues, no lag, and no broken apps.
[34:07.050 --> 34:08.170]  Everything just worked perfectly.
[34:08.650 --> 34:11.030]  So, I think persistence pays off.
[34:14.780 --> 34:24.780]  So again, my first attempt with Ubuntu, I don't know why I was trying to cram a full version on such limited hardware, but that's kind of where I started.
[34:24.780 --> 34:26.920]  It was just kind of just being dumb, I guess.
[34:29.080 --> 34:35.120]  So while the full version wasn't great for the older units with the hardware limitation, the minimal install worked okay.
[34:36.240 --> 34:46.640]  Though I found it was kind of marginally better than Chrome OS, minus the privacy issues.
[34:52.680 --> 34:53.620]  Gallium OS.
[34:54.140 --> 34:58.620]  So yeah, here lies a tribute to a short-lived triumph, right?
[34:58.620 --> 35:04.360]  So it was a Linux distribution that specifically optimized for Chromebooks.
[35:04.620 --> 35:07.180]  You know, it offered unparalleled performance and compatibility.
[35:07.620 --> 35:09.560]  Like I said, I had a great experience with it.
[35:13.400 --> 35:16.200]  This Lenovo I brought here has Gallium loaded on it.
[35:16.220 --> 35:19.400]  So I want to try to get to demo on that here in a second.
[35:19.820 --> 35:21.040]  So I thought it was really cool.
[35:22.200 --> 35:27.340]  Essentially what I had to do to kind of overcome the challenge getting that working, I had to toggle the Wi-Fi off.
[35:28.720 --> 35:34.200]  It's probably due to the out of development issues that I was having with it or whatever.
[35:35.280 --> 35:41.060]  And then once it just worked really well.
[35:42.620 --> 35:47.800]  So I was going to really just like wax eloquent on Gallium OS because I was kind of enamored.
[35:48.600 --> 35:53.280]  But again, for the sake of time, I'm going to kind of skip over that.
[35:53.280 --> 35:57.800]  We can do like an after thing if anybody has questions about that or whatever.
[35:58.080 --> 36:02.860]  But so I'm going to kind of skip over to the...
[36:03.820 --> 36:08.120]  Yeah, I wanted to show that like that project is it's it was a really cool project.
[36:08.400 --> 36:11.720]  I don't know how it ended up, you know, dying or whatever.
[36:12.000 --> 36:15.740]  But this was a really awesome like lookup page here.
[36:15.740 --> 36:21.280]  Like so you could just find your device on this list and find out if it was supported or not.
[36:21.860 --> 36:28.420]  And it gave you all kinds of awesome specifications and, you know, tips and things to kind of get things working.
[36:28.740 --> 36:38.840]  And then you'd go on their site and find the, you know, model of or version of Gallium OS that was, you know, tailored specifically to your hardware.
[36:40.480 --> 36:42.000]  That's one of the things I loved about it.
[36:42.180 --> 36:43.080]  I just thought it was awesome.
[36:45.520 --> 36:49.400]  And again, you know, despite its success, Gallium OS development ceased.
[36:49.920 --> 36:51.340]  So I'm sad panda.
[36:53.360 --> 36:54.440]  Marking the end of an era.
[36:54.640 --> 36:57.480]  Users are now transitioning to other, you know, Linux distros.
[36:57.840 --> 37:01.380]  But I think Gallium OS's legacy continues to inspire the community.
[37:02.080 --> 37:09.760]  Although it's no longer under development, the lessons and successes I had with Gallium and continue to inform, you know, my work with the alternative distributions.
[37:14.540 --> 37:17.260]  And this one here is, you know, about Lubuntu.
[37:17.560 --> 37:22.180]  It works on multiple devices, PCs, laptops, Raspberry Pis, and Chromebooks.
[37:22.780 --> 37:28.160]  So I was going to share that, you know, my daughter, Elena, installed this on her Chromebook herself.
[37:29.640 --> 37:31.640]  So, yeah, it was pretty awesome.
[37:31.640 --> 37:34.460]  It was a really easy installer, straightforward.
[37:37.540 --> 37:38.980]  And kind of the after action.
[37:39.140 --> 37:44.600]  I really thought the LXQT desktop was quite pleasing, you know.
[37:44.740 --> 37:47.240]  And no surprise, though, we were plagued by the sound issue again.
[37:47.840 --> 37:55.940]  But fortunately, I was able to find a command on Reddit that, you know, run this options.
[37:56.480 --> 38:06.000]  I'm not going to read the whole thing, but basically edit the also dot base config file, restart, and then it works.
[38:13.420 --> 38:14.540]  Where am I at on time?
[38:15.400 --> 38:15.540]  Three?
[38:17.160 --> 38:17.940]  Ten minutes?
[38:18.280 --> 38:18.380]  Okay.
[38:21.000 --> 38:26.840]  So I was going to share a really cool troubleshooting story that I came across on...
[38:29.620 --> 38:36.140]  on a YouTuber's channel where she was doing a Chromebook project herself.
[38:36.920 --> 38:38.240]  It's Veronica Explains.
[38:42.060 --> 38:46.360]  So I kind of had this done up in like a story format.
[38:46.360 --> 38:48.420]  So it's just a little snippet from one of her videos.
[38:49.240 --> 39:00.340]  So imagine you've got this Lenovo ThinkPad C13 Yoga, and you're excited to transform it into a Linux powerhouse.
[39:00.780 --> 39:06.400]  You know, the journey starts smoothly with the installation of core boot firmware.
[39:07.130 --> 39:11.360]  You eagerly proceed to install Debian 12, anticipating a seamless transition.
[39:11.360 --> 39:13.400]  However, things take an unexpected turn.
[39:13.740 --> 39:19.140]  After booting from Debian 12 ISO, you're met with an endless loop of frustration.
[39:19.620 --> 39:23.680]  Every attempt to select an option in Grub results in the system restarting.
[39:24.760 --> 39:31.160]  It's a perplexing dilemma because other distributions installed perfectly without a hitch, yet Debian 12 refuses to cooperate.
[39:31.920 --> 39:35.360]  Determined to get to the bottom of this, you embark on a troubleshooting adventure.
[39:36.160 --> 39:40.660]  First, you experiment with different ISOs, Debian 12 ISO stubbornly loops.
[39:40.880 --> 39:46.020]  But a glimmer of hope appears when a Debian nightly testing ISO installs successfully and boots up perfectly.
[39:46.900 --> 39:55.160]  However, this success is short-lived as the boot loop returns post-installation, courtesy of Grub 2.06 version reverting back.
[39:55.460 --> 39:58.860]  You realize that Grub version is the key to this puzzle.
[39:59.340 --> 40:03.520]  The Debian testing ISO used Grub 2.12.
[40:04.600 --> 40:06.640]  Which seems to bypass the issue.
[40:06.920 --> 40:17.620]  Armed with this knowledge, you decide to manually modify the boot targets in the ISOs Grub command line to point directly to your installed Debian system.
[40:17.860 --> 40:26.280]  Booting your system successfully using the ISOs Grub 2.12, you then install the newer Grub version from the Debian's SID branch.
[40:26.480 --> 40:30.620]  And then it goes into kind of all the commands that you do and you reboot.
[40:30.900 --> 40:31.160]  Success.
[40:31.960 --> 40:35.340]  So, now your system boots flawlessly liberated from the boot loop nightmare.
[40:36.360 --> 40:41.460]  You know, this experience uses a valuable lesson about the intricacies of firmware and boot loaders.
[40:42.740 --> 40:48.580]  And I didn't personally run into this, so I just, I thought it was really great to kind of, you know, just share that a little bit of...
[40:48.580 --> 40:53.220]  From people doing similar projects that ran into this kind of weird bizarreness.
[40:55.520 --> 40:59.500]  And it highlights the value of community resources like culture book forums.
[41:00.260 --> 41:04.580]  You know, that provide critical support and insights during challenging times.
[41:07.520 --> 41:15.580]  And so through a bit of, you know, technical wizardry and perseverance, you transform a frustrating obstacle into a triumphant success.
[41:17.760 --> 41:23.100]  Again, so, you know, this is based on experiences shared by Veronica Explains on her YouTube channel.
[41:23.300 --> 41:25.960]  You can find more awesome content there.
[41:27.860 --> 41:31.540]  And then I kind of want to move on to one other thing.
[41:34.320 --> 41:35.620]  If I can get this to work right.
[41:38.120 --> 41:41.800]  You know, I'm not even going to pull up this other slide.
[41:41.800 --> 41:43.260]  I'm just going to jump right into that.
[41:49.520 --> 41:51.680]  So, this is running Gallium OS.
[41:53.160 --> 41:55.840]  And I wanted to know if this thing would play Doom.
[42:22.200 --> 42:22.940]  There we go.
[42:23.840 --> 42:25.980]  I had to figure out where my controls were again.
[42:37.080 --> 42:38.860]  This is the Lenovo N23.
[42:49.320 --> 42:51.480]  Alright, let me quit that.
[42:55.160 --> 42:56.040]  So, yeah.
[42:56.280 --> 42:59.500]  So, that's running the chocolate Doom port.
[43:00.140 --> 43:01.640]  In case anybody was curious about that.
[43:01.820 --> 43:04.000]  But, yeah.
[43:04.120 --> 43:06.260]  I actually have the specifications wrote down.
[43:06.440 --> 43:07.180]  I'd have to like look.
[43:07.340 --> 43:08.200]  I don't have it memorized.
[43:08.220 --> 43:13.160]  So, to answer those questions about the processor and all that stuff, we can talk about that after.
[43:13.300 --> 43:14.820]  I want to be judicious of time.
[43:16.140 --> 43:17.000]  So, yeah.
[43:17.380 --> 43:19.620]  I thought this was a fun little demo.
[43:19.620 --> 43:24.040]  And you can come up after outside if you want to take a look at this thing.
[43:26.880 --> 43:29.680]  This is the one that belongs to my son, Caleb, actually.
[43:32.260 --> 43:33.280]  And so, yeah.
[43:33.380 --> 43:35.740]  I think that it was a pretty good success.
[43:36.200 --> 43:41.960]  And that's partly why I'm disappointed that, you know, Gallium is end of development too.
[43:42.100 --> 43:45.800]  Because, I mean, it's obviously working on this thing really well.
[43:47.360 --> 43:49.200]  And, unfortunately, I can't get updates now.
[43:49.200 --> 43:52.740]  So, I'm going to have to maybe switch this one over to Lubuntu or something.
[43:54.460 --> 43:58.060]  But, with that, were there any other questions or anything?
[43:58.480 --> 44:00.360]  Have you ever done anything for dual booting?
[44:00.560 --> 44:01.980]  Just in case you want to keep that drum on?
[44:02.400 --> 44:02.800]  Yeah.
[44:02.940 --> 44:03.100]  No.
[44:03.240 --> 44:04.440]  So, that's kind of...
[44:04.440 --> 44:07.160]  I briefly kind of alluded to it at the beginning.
[44:07.360 --> 44:09.820]  Somebody else was talking about they wanted to do dual booting.
[44:09.820 --> 44:12.640]  I personally haven't done any dual booting yet.
[44:13.440 --> 44:16.640]  I'm concerned about the hardware limitations of these.
[44:17.060 --> 44:19.000]  Not really allowing for that.
[44:19.620 --> 44:22.320]  Now, this one does have the removable M.2 drive.
[44:22.480 --> 44:27.400]  So, in theory, I could update the drive and I may actually try to experiment with that.
[44:28.020 --> 44:31.500]  Because I think the main limiting factor there's going to be the hard drive space, right?
[44:31.500 --> 44:35.620]  I mean, you know, I got to be able to load like a couple of OS's on the thing.
[44:35.800 --> 44:40.460]  So, that may be, you know, like a VDOT next type of project.
[44:40.900 --> 44:42.420]  Is that a pre-CR50?
[44:42.860 --> 44:43.820]  This is, yes.
[44:45.520 --> 44:49.220]  The other like post-CR50 model actually doesn't belong to me.
[44:50.220 --> 44:52.260]  It belongs to my brother-in-law and he's a mechanic.
[44:52.480 --> 44:57.380]  And so, he actually wanted me to load an automotive software on there.
[44:57.620 --> 45:00.020]  So, I had to go a different direction with that one.
[45:00.020 --> 45:02.700]  But, you know, here we are.
[45:03.020 --> 45:04.740]  So, yes.
[45:05.200 --> 45:11.420]  You mentioned running the Android S in the Bluetooth through a special...
[45:11.420 --> 45:12.080]  And box.
[45:12.360 --> 45:12.920]  Yep.
[45:13.420 --> 45:18.740]  Is that costing like performance degradation over the Chrome OS?
[45:19.140 --> 45:19.580]  Yeah.
[45:19.740 --> 45:23.340]  So, right before coming out here, I had actually just discovered that.
[45:23.620 --> 45:25.960]  So, I really didn't get a chance to dive into it, unfortunately.
[45:26.900 --> 45:34.360]  But, again, I'm going to try to get this stuff loaded up on some sort of like where I can share the slides with folks.
[45:35.680 --> 45:36.560]  Because I...
[45:36.560 --> 45:37.360]  Thank you.
[45:37.680 --> 45:44.660]  I do want to dive into that a little bit more and kind of explore that myself a little bit and kind of see what that was all about.
[45:46.040 --> 45:55.580]  Based on the reviews I read though, basically, you have the same limitations as far as the optimization of Android apps.
[45:55.580 --> 46:03.720]  It works basically, from what I understand, just as well on the inbox thing versus like the Chrome OS, you know, options.
[46:03.720 --> 46:11.060]  Just because the developers of those specific apps, you know, don't necessarily have all the optimizations, right?
[46:11.240 --> 46:14.820]  So, it's going to be what's been optimized.
[46:15.720 --> 46:16.120]  So...
[46:16.120 --> 46:17.280]  Yeah, I was really...
[46:17.280 --> 46:19.520]  Like, you find Gallagher that much better than Ubuntu?
[46:19.720 --> 46:21.620]  Like, it's like a significant bit, but...
[46:22.500 --> 46:22.900]  Um...
[46:22.900 --> 46:23.460]  I don't know.
[46:23.500 --> 46:24.620]  I just kind of became a fanboy.
[46:25.540 --> 46:25.940]  Like...
[46:25.940 --> 46:30.380]  There's no grumblings of like forks of people like working it or anything like that?
[46:31.220 --> 46:34.640]  I think there was some grumblings of it on Reddit a little bit.
[46:34.640 --> 46:39.580]  I think some people were maybe going to try to pick up the project or something, but I don't really know.
[46:39.960 --> 46:45.220]  I know it's like a bit out of my scope right now for me to try to jump in there and do things with it.
[46:45.360 --> 46:49.080]  Because, you know, full-time job, wife, three kids, all that kind of stuff.
[46:49.120 --> 46:51.640]  I just don't have the, you know, the bandwidth.
[46:51.920 --> 46:52.960]  But, I mean...
[46:54.160 --> 46:54.520]  I...
[46:54.520 --> 46:55.640]  So, again, like...
[46:57.340 --> 46:58.220]  Lubuntu is awesome.
[46:58.560 --> 47:00.960]  Like, it worked really good on the other Chromebooks.
[47:00.960 --> 47:02.680]  But, unlike...
[47:03.540 --> 47:08.240]  When I put Gallium on this one, I didn't have any of the issues that I really...
[47:08.240 --> 47:11.940]  So, when I put Lubuntu on the other one, I still had audio issues that I had to resolve, right?
[47:12.020 --> 47:13.240]  I had to troubleshoot some things.
[47:13.720 --> 47:15.000]  This one, it loaded up.
[47:15.100 --> 47:16.020]  Like, everything worked.
[47:16.120 --> 47:17.060]  I mean, the touchpad worked.
[47:17.320 --> 47:18.200]  The screen works.
[47:18.360 --> 47:19.500]  Like, the touch screen works.
[47:19.640 --> 47:20.640]  Like, you know, sound works.
[47:20.740 --> 47:21.700]  I didn't have any issues.
[47:21.820 --> 47:22.680]  It just...
[47:22.680 --> 47:26.920]  So, you know, that kind of sold me, at least on this one.
[47:27.660 --> 47:28.020]  Yes.
[47:29.600 --> 47:32.800]  Do you know why the development of Gallium OS was...
[47:32.800 --> 47:34.180]  I actually don't.
[47:34.360 --> 47:38.160]  So, right before coming out here, I kind of stalked the...
[47:38.160 --> 47:40.740]  One of the main developers on LinkedIn, messaged him.
[47:41.560 --> 47:43.600]  And I didn't get a response back.
[47:44.520 --> 47:45.040]  So...
[47:46.780 --> 47:47.300]  Yeah.
[47:48.020 --> 47:51.320]  I was just saying, I've done this with an Asus.
[47:51.480 --> 47:51.740]  Yeah.
[47:52.220 --> 47:52.740]  Yeah.
[47:52.740 --> 47:52.840]  Yeah.
[47:53.260 --> 47:57.960]  And the big issue, which I know you didn't really go into, but the firmware change.
[47:59.340 --> 48:00.800]  And I know it's a flip.
[48:01.060 --> 48:04.600]  Like, basically, when I did the firmware, I basically lost all the audio on it.
[48:05.020 --> 48:05.240]  Yeah.
[48:05.320 --> 48:08.740]  There's no support without the Chrome OS.
[48:09.240 --> 48:09.480]  Right.
[48:09.760 --> 48:10.560]  And I...
[48:10.560 --> 48:10.840]  Exactly.
[48:11.240 --> 48:13.060]  It would have been...
[48:13.060 --> 48:14.300]  Well, and I've done dual boot on it.
[48:14.460 --> 48:14.840]  So...
[48:15.000 --> 48:17.200]  I kind of wish I just stayed dual boot.
[48:17.660 --> 48:19.520]  There's a case for dual boot right there.
[48:19.520 --> 48:19.740]  Yeah.
[48:19.880 --> 48:21.980]  Because I have a newer one that I'm...
[48:21.980 --> 48:22.440]  Okay.
[48:22.520 --> 48:23.360]  I got two minutes left.
[48:24.620 --> 48:25.020]  Yeah.
[48:25.220 --> 48:27.120]  I ran into the same thing with the newer one.
[48:27.260 --> 48:28.700]  I'm still dealing with sound issues.
[48:28.840 --> 48:32.000]  I'm still troubleshooting and trying to figure out some solution for it.
[48:32.960 --> 48:35.260]  Just personal experience, I'd recommend dual boot.
[48:35.940 --> 48:37.100]  If you want audio.
[48:37.220 --> 48:38.460]  If you didn't need audio, it's fine.
[48:38.780 --> 48:39.040]  No.
[48:39.280 --> 48:39.680]  Exactly.
[48:40.160 --> 48:40.300]  Yeah.
[48:40.680 --> 48:42.000]  And that's it right there.
[48:42.140 --> 48:42.220]  Yeah.
[48:42.220 --> 48:42.520]  Yeah.
[48:42.520 --> 48:43.440]  To my art...
[48:43.440 --> 48:45.200]  Like you said, hardware...
[48:45.200 --> 48:46.220]  Other systems is not...
[48:47.440 --> 48:47.800]  Right.
[48:48.240 --> 48:49.560]  There's a whole firmware wrap...
[48:49.560 --> 48:50.400]  Well, it's literally...
[48:50.400 --> 48:51.600]  4OS is a wrap.
[48:51.820 --> 48:52.180]  So...
[48:52.180 --> 48:52.420]  Yeah.
[48:52.520 --> 48:57.220]  And I noticed I had like flip screen issues too with one of the flip models I had that I was playing with.
[48:57.380 --> 48:57.600]  It...
[48:57.600 --> 48:59.440]  It was like all sideways for a minute.
[48:59.560 --> 49:00.020]  It was weird.
[49:01.680 --> 49:02.040]  Um...
[49:02.040 --> 49:02.180]  Okay.
[49:03.380 --> 49:03.740]  Um...
[49:03.740 --> 49:04.780]  I think I'm pretty much at time.
[49:04.880 --> 49:05.660]  I'm gonna call it right here.
[49:06.160 --> 49:06.400]  Um...
[49:06.400 --> 49:06.640]  Thank you.
[49:07.040 --> 49:07.400]  Thank you.