**** BEGIN LOGGING AT Mon Jan 24 02:59:56 2022
Jan 24 04:08:41 <fakuivan> Hello, I'm a noob with respect to the beaglebone boards. A university professor asigned me to look into how to get a beaglebone black running with a linux OS. What linux distros does that board support?
Jan 24 04:10:04 <fakuivan> It'd be great if I could get something familiar to run like ubuntu or debian server
Jan 24 04:24:53 <hnv> The BeagleBone Black (and Green) are shipped with Debian pre-installed
Jan 24 04:33:58 <hnv> (booting from the eMMC). You can also boot from a uSD with another distro (supporting that particular board). I never tried Ubuntu though
Jan 24 07:52:42 <mattb0ne> hnv: I will try that
Jan 24 09:23:44 <Guest21> hi
Jan 24 10:25:39 <zmatt> hnv: though people should be warned that booting from uSD when there's a substantially different distro on eMMC can cause weird problems due to u-boot incompatibility, solvable using the S2 button or by simply wiping eMMC (or at least wiping the bootloader from eMMC)
Jan 24 12:27:34 <hnv> Right
Jan 24 12:37:09 <jfsimon1981> Hi good afternoon
Jan 24 15:14:22 <fakuivan> I'm trying to flash the eMMC on a beaglebone black, the instructions I've found specify that the flashing is done once all LEDs turn off, this board is flashing all LEDs at the same time. Is the flashing process complete?
Jan 24 15:17:40 <rcn-ee> fakuivan, all on and all of; repeat is an error condition.. please plug in a usb-serial adapter into J1 and pastebin your serial log..
Jan 24 15:22:39 <fakuivan> I don't have a serial adapter on hand :c
Jan 24 15:23:14 <fakuivan> I've read about this being caused by a 4GB image trying to flash a 2GB eMMC
Jan 24 15:23:54 <fakuivan> This board has a "3da18 jw896" micron chip as eMMC
Jan 24 15:25:00 <fakuivan> I didn't try a 2GB image since those are not listed on the main section, but the "Older Debian images"
Jan 24 15:25:57 <fakuivan> If that's the case, is there a jumper I can bridge to always boot from the sd card?
Jan 24 15:28:14 <rcn-ee> fakuivan, if it's a 2GB model, there should have been a sticker placed on it saying A6* or A6* but that would have been stuck on the board 10 years ago...
Jan 24 15:28:42 <fakuivan> A5C in fact
Jan 24 15:28:55 <fakuivan> This board looks pretty old
Jan 24 15:29:07 <rcn-ee> Just flash a normal image to a microSD, insert in board... Use your finger hold the boot button, insert power.. then once booted, zero out the eMMC..
Jan 24 15:29:24 <rcn-ee> Sorry missed my coffee.. that first A6* should have been an A5*..
Jan 24 15:31:43 <zmatt> fakuivan: Micron JW896 is indeed 2GB (more precisely, 1832 MB)
Jan 24 15:33:25 <zmatt> fakuivan: I'd generally recommend a console image for those
Jan 24 15:33:56 <zmatt> if you're comfortable using apt to install whatever packages you want/need after flashing
Jan 24 15:35:46 <fakuivan> rcn-ee: how do I zero it out? using dd?
Jan 24 15:35:46 <hnv> what about using a pulldown resistor to bot always from uSD?
Jan 24 15:35:57 <hnv> *boot
Jan 24 15:36:01 <zmatt> fakuivan: blkdiscard /dev/mmcblk1
Jan 24 15:36:19 <zmatt> hnv: possible, but wiping eMMC is more convenient
Jan 24 15:37:00 <zmatt> fakuivan: or rather, sudo blkdiscard /dev/mmcblk1
Jan 24 15:37:12 <fakuivan> I see
Jan 24 15:37:25 <fakuivan> Do I need to mount the emmc?
Jan 24 15:37:39 <zmatt> no, emmc must not be mounted
Jan 24 15:38:02 <fakuivan> got it
Jan 24 15:39:31 <zmatt> of course 2GB is plenty of space for many applications, just not for bloated images that include everything and the kitchen sink ;)
Jan 24 15:39:51 <zmatt> unfortunately the old micron eMMC was also kinda slow
Jan 24 15:40:59 <zmatt> (though sd card may be slower still)
Jan 24 15:41:33 <fakuivan> This board will be used with a touch screen cape
Jan 24 15:41:43 <fakuivan> So I'm guessing a GUI will be mandatory
Jan 24 15:42:02 <zmatt> GUI doesn't necessarily require much space
Jan 24 15:42:13 <zmatt> depends on what kind of gui
Jan 24 15:42:40 <fakuivan> that and a web browser, those are pretty bloated from what I understand
Jan 24 15:43:08 <rcn-ee> fakuivan, "a web browser".... circa 2008, or circa 2022... that alone is bloated...
Jan 24 15:43:09 <zmatt> e.g. a single-window-fullscreen qt5 application running directly on the framebuffer doesn't require much space at all
Jan 24 15:43:22 <zmatt> fakuivan: a web browser? you have my condolences
Jan 24 15:44:02 <fakuivan> It's for an electron app, so sort of a web browser
Jan 24 15:44:11 <rcn-ee> fakuivan, it's going to be slower then crap...
Jan 24 15:55:48 <zmatt> (and possibly run out of memory)
Jan 24 15:56:50 <rcn-ee> 512Mb... electron + xorg.. (and probally web-browser)... yeah your out of memoryu...
Jan 24 16:36:13 <jkridner> 3 months of unread messages.... yeah, not likely to read those. :-)
Jan 24 16:37:48 <Guest76> Hello,
Jan 24 16:37:49 <Guest76> I am a Senior Computer System Engineering student that needs the board as controller for a drone project, but I need to understand some critical points that are not clear. So who can I ask ?
Jan 24 16:42:53 <jkridner> read the topic.... just ask, don't ask to ask.
Jan 24 16:44:18 <jkridner> I've built a few quadcopters. I like BeagleBone Blue and Ardupilot for that. Depends on what you want to get into. There are small, cheap, open-source MCU-based controllers out there.
Jan 24 16:50:09 <Guest76> I am thinking of building the fight controller from scratch. is that possible with beagle blue ?
Jan 24 16:53:02 <rcn-ee> Guest76, https://ardupilot.org/copter/docs/common-beagle-bone-blue.html
Jan 24 16:53:35 <Guest76> or as a second option try to edit and add some other functions on the Arudupiolt program. Is that possible ?
Jan 24 16:54:01 <rcn-ee> Guest76, big write up here: https://github.com/imfatant/test
Jan 24 17:00:48 <zmatt> Guest76: with enough time and dedication you can build anything from scratch
Jan 24 17:02:48 <Guest76> those links are to install aurdopilot on beaglebone , I am thinking about building a flight contoller, but thanks anyway.
Jan 24 17:03:51 <Guest76> yes, i know its possible , but is there any controllers that are better from othe in building flight controller from scratch ?
Jan 24 17:04:03 <Guest76> other**
Jan 24 17:04:09 <rcn-ee> Guest76, so your asking us to help you build it from scratch?
Jan 24 17:04:23 <zmatt> it may be worth using off-the-shelf software to get the hardware side working before trying your hand at custom software, that way you avoid debugging software and hardware at the same time
Jan 24 17:04:43 <zmatt> your question is confusing
Jan 24 17:07:02 <zmatt> if you just want to drop in a custom flight control algorithm, presumably your best bet is customizing ardupilot so you can reuse the code that deals with stuff like hardware interfacing
Jan 24 17:10:57 <zmatt> of course if you want to start entirely from scratch, that's totally an option... if you have the time to spend on that (including the time to acquire the necessary knowledge)
Jan 24 17:11:58 <Guest76> i am sorry is my questions seems confusing, that actually reflects how i am also confused in my thoughs. how much time it may require building it from scratch?
Jan 24 17:12:03 <Guest76> if**
Jan 24 17:13:20 <zmatt> that seems like an impossible thing to answer, given the vagueness of the scope of the project and the fact that it will heavily depend on your abilities
Jan 24 17:13:20 <Guest76> and are you saying that i can add or edit functions on  arudopilot program so it can function the way i want ?
Jan 24 17:13:34 <zmatt> ardupilot is open source, so yes
Jan 24 17:14:19 <Guest76> what language do i need to use for the program ?
Jan 24 17:14:57 <zmatt> if that's not information you're able to find out on your own, I'm worried for your project
Jan 24 18:00:58 <Guest80> Hello
Jan 24 18:01:20 <Guest80> I want to ask about beaglebone blue
Jan 24 18:01:38 <Guest80> Can you help me
Jan 24 18:19:09 <fakuivan> rcn-ee: I might reconsider rebuilding the app for NodeGUI
Jan 24 18:19:38 <fakuivan> It uses Qt in the background, so no chromium
Jan 24 18:20:46 <mattb0ne> mattbone is back with problems
Jan 24 18:25:18 <mattb0ne> i am getting dns server errors
Jan 24 18:25:32 <mattb0ne> i may of blew things up with resolv.conf file
Jan 24 18:25:53 <zmatt> resolv.conf is normally auto-generated and should not be touched
Jan 24 18:28:45 <hnv> fakuivan: I was looking for a lightweight html+css rendering tool...
Jan 24 18:29:51 <fakuivan> Qt supports css, I think NodeGUI is only responsible for translating the html components to the Qt ones
Jan 24 18:32:44 <mattb0ne> what if i did zmatt
Jan 24 18:33:01 <mattb0ne> is there a way to force an auto generation of the file
Jan 24 18:33:13 <mattb0ne> i cannot ping 8.8.8.8 at the moment
Jan 24 18:33:18 <zmatt> mattb0ne: typically it would be regenerated at boot, but it depends a bit on what you did
Jan 24 18:33:34 <zmatt> if you can't ping 8.8.8.8 then your bbb doesn't have internet access
Jan 24 18:33:44 <zmatt> which is not a problem related to resolv.conf
Jan 24 18:42:07 <mattb0ne> hmmmm
Jan 24 18:42:18 <mattb0ne> had this working and like all things beagle it is not cooperating
Jan 24 18:43:01 <mattb0ne> the LCD cape has gone kaputz and I lost internet connection after having this work
Jan 24 18:51:16 <mattb0ne> windows sucks
Jan 24 18:56:04 <mattb0ne> ok I had to disable sharing and reenable
Jan 24 18:56:07 <mattb0ne> now on to the cape
Jan 24 18:56:14 <mattb0ne>  need your expertise zmatt
Jan 24 18:56:35 <mattb0ne> this cape once worked and now I cannot get LED to light up when the board is plugged in
Jan 24 18:56:59 <mattb0ne> I had two of the same LCD cape and the other one power cycles
Jan 24 18:57:16 <mattb0ne> I already did the modidication you suggested by taking out the R1 resistor
Jan 24 19:10:06 <mattb0ne> ok the 2nd LCD cape power cycles and a completely different brand also power cycles
Jan 24 19:10:10 <mattb0ne> I get to see the tux for a bit
Jan 24 19:10:18 <mattb0ne> i will paste the serial output
Jan 24 19:26:15 <fakuivan> I have this cape model https://www.openhacks.com/uploadsproductos/bbb-usr.pdf . Should I expect to plug the bbb in and have it show a terminal on the screen?
Jan 24 19:26:27 <fakuivan> Because it's currently not doing that :P
Jan 24 19:29:56 <zmatt> most capes will be autodetected, unless nobody (including the manufacturer) bothered to contribute support for it in the form of an overlay
Jan 24 19:30:15 <zmatt> never heard of this one
Jan 24 19:30:30 <zmatt> try logging in via ssh and use sudo /opt/scripts/tools/version.sh
Jan 24 19:33:48 <fakuivan> What should I look for on that output?
Jan 24 19:34:04 <zmatt> can you share it via pastebin.com so we can take a look?
Jan 24 19:34:39 <fakuivan> https://gist.github.com/fakuivan/2cfb9e076a3793401509782a5f5c1095
Jan 24 19:35:58 <hnv> The detection and overlay happens at U-Boot stage?
Jan 24 19:35:59 <zmatt> this is not hopeful, it doesn't look like it recognized your cape
Jan 24 19:36:02 <zmatt> yes
Jan 24 19:36:27 <zmatt> I thought it woulld also show the identifiers of detected capes but maybe I'm wrong
Jan 24 19:36:31 <fakuivan> @zmatt: rip. Is there anything obvious I could try?
Jan 24 19:39:07 <zmatt> check which of /sys/bus/i2c/devices/2-005[4-7]/eeprom exists and then   hexdump -C /path/to/eeprom | head   that one
Jan 24 19:41:41 <fakuivan> `ls /sys/bus/i2c/devices/2-005{4..7}/eeprom` throws "cannot access '/sys/bus/i2c/devices/2-0054/eeprom': No such file or directory" for all of them
Jan 24 19:42:07 <zmatt> ehhhhhh
Jan 24 19:42:34 <fakuivan> The cape also came with a DVD drive, I could boot up an old server of mine and see if there's anything useful about the board
Jan 24 19:42:46 <zmatt> well that at least explains why your cape wasn't autodetected
Jan 24 19:42:54 <zmatt> sounds like it doesn't even have an identification eeprom
Jan 24 19:43:20 <fakuivan> @zmatt: https://gist.github.com/fakuivan/50f284a0af207e2459ccad2b8434b9c0
Jan 24 19:44:30 <fakuivan> @zmatt: how bad is not having an identification eeprom_
Jan 24 19:44:33 <fakuivan> ?*
Jan 24 19:44:48 <zmatt> well it precludes auto-detection obviously
Jan 24 19:44:52 <fakuivan> The can bus is detected, so I'm guessing the BBB is attached correctly
Jan 24 19:45:07 <zmatt> no the can bus isn't detected
Jan 24 19:45:16 <zmatt> cape-universal just enables everything and the kitchen sink
Jan 24 19:45:48 <fakuivan> debian@bbb-unam:~$ dmesg | grep CAN
Jan 24 19:45:48 <fakuivan> [    9.172744] CAN device driver interface
Jan 24 19:45:58 <zmatt> yes that means nothing
Jan 24 19:46:02 <fakuivan> Oh
Jan 24 19:46:04 <fakuivan> dang
Jan 24 19:46:19 <zmatt> your cape hasn't been detected (since it's undetectable) hence nothing _on_ your cape is detected either
Jan 24 19:46:48 <fakuivan> I see
Jan 24 19:47:07 <fakuivan> How did people do the cape thing before automatic detection?
Jan 24 19:47:56 <zmatt> I'm pretty sure capes were always supposed to have an identification eeprom
Jan 24 19:48:11 <zmatt> but if you have an overlay for it then you can force-enable it via /boot/uEnv.txt
Jan 24 19:48:35 <zmatt> but it sounds like this cape is so old it predates devicetree, it's from the board file era
Jan 24 19:48:49 <zmatt> based on an old thread I found
Jan 24 19:50:13 <fakuivan> Dang, this thing must have been like 10+ years in a closet
Jan 24 19:50:33 <zmatt> something like that yeah
Jan 24 19:50:44 <zmatt> the thread is from 2012
Jan 24 19:51:30 <zmatt> getting this thing to work may require writing an overlay based on the cape's schematic
Jan 24 19:51:49 <zmatt> (assuming you have the schematic on that DVD)
Jan 24 19:52:17 <fakuivan> oh no
Jan 24 19:52:30 <fakuivan> I'll see what I can find on that DVD
Jan 24 19:52:35 <fakuivan> Thanks for the help so far
Jan 24 19:53:45 <rcn-ee> fakuivan, that one is fun... the i2c eeprom... is on the wrong 2 pins..
Jan 24 19:53:51 <zmatt> lol
Jan 24 19:54:07 <zmatt> fail
Jan 24 19:55:05 <rcn-ee> there are two models, one oem made them for a bunch of downstream re-sellers.. (SVTronics/etc..)
Jan 24 19:55:19 <rcn-ee> i have a custom *.dtb for it: https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v4.14.x-ti/src/arm/am335x-boneblack-bbb-exp-c.dts
Jan 24 19:55:40 <rcn-ee> or v4.19.x: https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/v4.19.x-ti/src/arm/am335x-boneblack-bbb-exp-c.dts
Jan 24 19:55:58 <rcn-ee> and that's as far as i cared for that mess of lcd. ;)
Jan 24 19:56:19 <rcn-ee> so either boot v4.14.x-ti/v4.19.x-ti and dtb=am335x-boneblack-bbb-exp-c.dtb
Jan 24 19:56:23 <zmatt> custom dtb even rather than overlay? o.O
Jan 24 19:56:33 <rcn-ee> or r= dtb=am335x-boneblack-bbb-exp-r.dtb
Jan 24 19:56:56 <rcn-ee> (resistive vs capacitive)
Jan 24 19:59:41 <rcn-ee> the dvd was just a schmatic and a 3.8.x kernel..
Jan 24 20:02:51 <fakuivan> rcn-ee: what do you mean by "the i2c eeprom... is on the wrong 2 pins"
Jan 24 20:03:07 <fakuivan> Could I rewire those and fix automatic detection?
Jan 24 20:03:43 <rcn-ee> fakuivan, when they designed the board, they screwed up.. the i2c bus for eeprom is 2 pins over... then the bus for i2c, is can...
Jan 24 20:04:04 <fakuivan> I see
Jan 24 20:04:32 <rcn-ee> fakuivan, so either use v4.14.x-ti or v4.19.x-ti and set the dtb.. ;)
Jan 24 20:04:58 <zmatt> he's already using v4.19-ti
Jan 24 20:05:03 <fakuivan> this one is running kernel 4.19.94-ti-r42
Jan 24 20:05:10 <rcn-ee> dtb=am335x-boneblack-bbb-exp-c.dtb
Jan 24 20:05:36 <fakuivan> is that for the capacitive board?
Jan 24 20:05:40 <rcn-ee> yeap
Jan 24 20:05:43 <fakuivan> nice
Jan 24 20:06:06 <fakuivan> So do I add that to uEnv.txt?
Jan 24 20:06:24 <rcn-ee> open /boot/uEnv.txt and just add it..
Jan 24 20:06:53 <rcn-ee> echo "dtb=am335x-boneblack-bbb-exp-c.dtb" >> /boot/uEnv.txt
Jan 24 20:07:04 <fakuivan> echo 'dtb=am335x-boneblack-bbb-exp-c.dtb' >> /boot/uEnv.txt then?
Jan 24 20:07:15 <fakuivan> thanks
Jan 24 20:08:11 <fakuivan> is the file included with the kernel or do I need to download it from that github link above?
Jan 24 20:08:20 <rcn-ee> it's pre-built in that version..
Jan 24 20:12:31 <fakuivan> https://gist.github.com/fakuivan/755d46b14de5ef2ce45b3c79fce524ee that's the output from `sudo /opt/scripts/tools/version.sh`
Jan 24 20:13:27 <fakuivan> The screen shows nothing. I'm expecting a blinking cursor or something
Jan 24 20:13:43 <fakuivan> Do I need to do more configuration?
Jan 24 20:14:32 <zmatt> hmm this looks like it ignored the override
Jan 24 20:14:59 <zmatt> which is odd, I thought dtb= took priority over most things
Jan 24 20:15:11 <zmatt> try disabling cape-universal maybe?
Jan 24 20:15:23 <zmatt> (comment out enable_uboot_cape_universal=1)
Jan 24 20:15:32 <rcn-ee> ftop: uboot_overlay_options:[enable_uboot_cape_universal=1]
Jan 24 20:15:52 <rcn-ee> drop: enable_uboot_overlays=1
Jan 24 20:16:21 <zmatt> you can't use overlays in combination with a custom dtb ?
Jan 24 20:16:55 <zmatt> especially selecting the pru overlay would still be useful
Jan 24 20:20:04 <fakuivan> omg
Jan 24 20:20:13 <fakuivan> I think this is the first tux this screen has ever seen
Jan 24 20:20:28 <fakuivan> or showed rather
Jan 24 20:21:22 <rcn-ee> and you need to force 24bit mode..
Jan 24 20:21:45 <zmatt> force 24bit mode?
Jan 24 20:22:45 <rcn-ee> in xorg...
Jan 24 20:23:09 <zmatt> why? isn't that the default?  also, should be autodetected based on the pixelformats lcdc supports?
Jan 24 20:27:48 <fakuivan> can I build kernel modules using the dkms from apt?
Jan 24 20:28:07 <zmatt> why not?
Jan 24 20:28:25 <fakuivan> apt also installs "linux-headers-3.8.13-xenomai-r86"
Jan 24 20:28:30 <zmatt> what
Jan 24 20:28:30 <zmatt> why
Jan 24 20:28:32 <zmatt> no
Jan 24 20:28:36 <fakuivan> I think those are not the correct headers for this kernel xd
Jan 24 20:28:43 <zmatt> that makes no sense
Jan 24 20:29:43 <zmatt> install dkms does not do that for me
Jan 24 20:30:22 <fakuivan> The following NEW packages will be installed:
Jan 24 20:30:23 <fakuivan>   dkms fakeroot libfakeroot linux-headers-3.8.13-xenomai-r86
Jan 24 20:30:48 <fakuivan> that's the output for `sudo apt install dkms`
Jan 24 20:31:31 <rcn-ee> sudo apt install linux-headers-`uname -r`
Jan 24 20:33:19 <fakuivan> I see
Jan 24 20:33:51 <fakuivan> it stills wants to install `linux-headers-3.8.13-xenomai-r86` lol
Jan 24 20:34:50 <fakuivan> does it change anything to have those headers installed along the correct ones?
Jan 24 20:37:58 <zmatt> something must be weird or broken, it shouldn't be attempting to install that
Jan 24 20:38:22 <zmatt> I would not let it install it
Jan 24 20:39:36 <zmatt> hmm, I've set apt to not automatically install "recommended" packages
Jan 24 20:43:34 <fakuivan> `sudo apt install --no-install-recommends dkms` installed only dkms
Jan 24 20:43:43 <fakuivan> I guess that's fine
Jan 24 20:45:29 <fakuivan> https://github.com/Mange/rtl8192eu-linux-driver/blob/realtek-4.4.x/Makefile what CONFIG_PLATFORM_ should I enable for building this on the bb black?
Jan 24 20:45:53 <fakuivan> There's "CONFIG_PLATFORM_ARM_TI_PANDA"
Jan 24 20:46:03 <fakuivan> But like 20 other variations on arm
Jan 24 20:48:04 <zmatt> all of them are wrong... why does it care so specifically about the platform?
Jan 24 20:48:40 <fakuivan> No idea tbh
Jan 24 20:49:43 <fakuivan> I was wondering the same thing
Jan 24 20:51:20 <fakuivan> They add `EXTRA_CFLAGS += -DCONFIG_IOCTL_CFG80211 -DRTW_USE_CFG80211_STA_EVENT` for the raspberry pi
Jan 24 20:51:46 <fakuivan> Should that also work for the SOC on the bb black?
Jan 24 20:52:30 <zmatt> from their name those don't sound SoC-related at all
Jan 24 20:58:58 <rcn-ee> sorry what did i miss? weekly call went long... that driver should be package?
Jan 24 20:59:34 <rcn-ee> no sorry... rtl8723bu and rtl8821
Jan 24 20:59:58 <mattb00ne> ok i got a serial output
Jan 24 20:59:59 <mattb00ne> https://pastebin.com/PAqVWHwc
Jan 24 21:00:16 <rcn-ee> fakuivan, uninstall  linux-headers-3.8.13-xenomai-r86
Jan 24 21:00:23 <mattb00ne> i got tux and the login screen before a cycles
Jan 24 21:01:00 <rcn-ee> mattb00ne, powered by 5Volt rail?
Jan 24 21:02:26 <mattb00ne> I believe so it comes with a plug that goes into the P8 and P9 rails
Jan 24 21:02:36 <mattb00ne> but the board is powered by an adadapter
Jan 24 21:02:47 <mattb00ne> its weird why it can get to the log on before failing
Jan 24 21:03:25 <rcn-ee> looks like a power starve, rebooting cycle to me...
Jan 24 21:04:03 <rcn-ee> What does the power supply show for rating? 5~10Watts..
Jan 24 21:05:52 <mattb00ne> 5V 2Amp adapter
Jan 24 21:06:38 <rcn-ee> should be fine... disable 'quiet' in /boot/uEnv.txt and lets what my have been cuasing the issue..
Jan 24 21:06:47 <mattb00ne> ok
Jan 24 21:13:23 <mattb00ne> so just delete quiet in that one line
Jan 24 21:13:54 <mattb00ne> #cmdline=coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
Jan 24 21:14:17 <mattb00ne> there is one that is un-commented
Jan 24 22:01:06 <fakuivan> What are the recommended desktop environments for debian on the bb black?
Jan 24 22:07:08 <mattb00ne> none
Jan 24 22:07:09 <mattb00ne> cli
Jan 24 22:07:14 <mattb00ne> why waste the space
Jan 24 22:07:27 <mattb00ne> what are you doing with it
Jan 24 22:13:27 <fakuivan> it's not a waste of space if it's the only reason why someone at my uni bought it :P
Jan 24 22:14:23 <fakuivan> idk what they're doing with it, they just want a dekstop environment to run diagnostics software
Jan 24 22:15:42 <fakuivan> it's running from an SD card anyways, I don't think space is a concern
Jan 24 22:18:47 <mattb00ne> depends on the usage but they may big sd cards
Jan 24 22:18:51 <mattb00ne> why not just stick with debian
Jan 24 22:20:20 <mattb00ne> since you are on an sd card anyway
Jan 24 22:20:27 <mattb00ne> and put cinnamon on as a gui
Jan 24 22:20:32 <mattb00ne> i like that one
Jan 24 22:20:37 <mattb00ne> very windows like
Jan 24 22:20:44 <mattb00ne> or gnome
**** ENDING LOGGING AT Tue Jan 25 02:59:56 2022