Debian 11 (bullseye) Testing Images

So today is Launch Day! :wink:

https://www.debian.org/releases/bullseye/amd64/release-notes/

For the BeagleBoard.org family of Boards, i’ve kinda taken this release to “start-over” on things, for users running Debian 10 (Buster), feel free to upgrade thru apt, but tweak your /etc/apt/sources.list as the debian-security repo changed on this release…

deb http://deb.debian.org/debian/ bullseye main contrib non-free
#deb-src http://deb.debian.org/debian/ bullseye main contrib non-free

deb http://security.debian.org/debian-security bullseye-security main contrib non-free
#deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free

deb http://deb.debian.org/debian bullseye-updates main contrib non-free
#deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free

deb [arch=armhf] http://repos.rcn-ee.com/debian/ bullseye main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ bullseye main

For users looking to start fresh, i have daily images here:

https://rcn-ee.net/rootfs/debian-armhf/

Some of the Major changes, v5.10.x based kernel, Network Manager over Connman, and Systemd has usb-gadget.target support.

usb-gadget.target:
libusbgx Docs: https://github.com/linux-usb-gadgets/libusbgx
gt Docs: https://github.com/linux-usb-gadgets/gt

USB Gadgets are way eaiser to load and modify now:

Frequency Asked Questions:

  • /opt/scripts/tools/version.sh → sudo beagle-version

ToDo: (20210814)

  • usb0/usb1 static routes
  • BeagleBoard.org “Doc” fake Image
  • wl18xx Firmware
  • BB-AI WiFi Firmware
  • bb-code-server out of box examples and wire up to systemd
  • ReWrite eMMC Flasher…

Fixes: (20210816)

  • added pkgs: bb-beagle-config, bb-cape-overlays, overlayroot,

Fixes: (20210818)

  • added bb-beagle-version
  • automatic resize of partition to max size of drive (takes 1 reboot to finalize) (bb-growpart/bb-resizefs)
root@BeagleBone:~# journalctl | grep bb-growpart
Aug 18 00:14:36 BeagleBone bb-growpart[310]: /usr/bin/growpart /dev/mmcblk0 1
Aug 18 00:14:39 BeagleBone bb-growpart[312]: CHANGED: partition=1 start=8192 old: size=7364608 end=7372800 new: size=31108063 end=31116255
root@BeagleBone:~# journalctl | grep bb-resizefs
Aug 18 00:31:15 BeagleBone bb-resizefs[310]: resize2fs /dev/mmcblk0p1
Aug 18 00:31:15 BeagleBone bb-resizefs[322]: resize2fs 1.46.2 (28-Feb-2021)
Aug 18 00:31:21 BeagleBone bb-resizefs[322]: Filesystem at /dev/mmcblk0p1 is mounted on /; on-line resizing required
Aug 18 00:31:21 BeagleBone bb-resizefs[322]: old_desc_blocks = 1, new_desc_blocks = 2
Aug 18 00:31:21 BeagleBone bb-resizefs[322]: The filesystem on /dev/mmcblk0p1 is now 3888507 (4k) blocks long.

Regards,

3 Likes

Hi Robert,
I’m currently using … (as follows below)… for lvlg development with a 4DLCD70T display, HW Ver 1.01 and I get a display prompt on the LCD after booting. with the latest image (info at end of this reply) there is no display prompt.

Do I need a different dtb to get the 4DLCD70T to work?

thanks,
amf

Linux beaglebone 5.4.106-ti-rt-r31 #1 SMP PREEMPT_RT Sun May 30 11:46:31 CDT 20x

during boot: 
debug: process_cape_part_number:[BB-BONE-LCD7-01.]
BeagleBone: cape eeprom: i2c_probe: 0x54: /lib/firmware/BB-BONE-LCD7-01-00A3.dt]

amf@beaglebone:~$ sudo /opt/scripts/tools/version.sh                            
[sudo] password for amf:                                                        
git:/opt/scripts/:[b39ec679648a6be8f25f48bd1c9784c1fc5a0c46]                    
eeprom:[A335BNLT000C1619BBBG0011]                                               
model:[TI_AM335x_BeagleBone_Black]                                              
dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-04-06]                     
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g07d570]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]                     
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]                           
UBOOT: Loaded Overlay:[BB-ADC-00A0]                                             
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0]                                   
UBOOT: Loaded Overlay:[BB-BONE-LCD7-01-00A3]                                    
kernel:[5.4.106-ti-rt-r31]                                                      
nodejs:[v10.24.0]                                                               
/boot/uEnv.txt Settings:                                                        
uboot_overlay_options:[enable_uboot_overlays=1]                                 
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI]
uboot_overlay_options:[enable_uboot_cape_universal=1]                           
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>] 
pkg:[bb-cape-overlays]:[4.14.20210416.0-0~buster+20210416]                      
pkg:[bb-wl18xx-firmware]:[1.20210520.0-0~buster+20210520]                       
pkg:[kmod]:[26-1]                                                               
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]                   
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/]
dmesg | grep remote                                                             
[    1.964791] remoteproc remoteproc0: wkup_m3 is available                     
[    2.141
588] remoteproc remoteproc1: 4a334000.pru is available                
[    2.143965] remoteproc remoteproc2: 4a338000.pru is available                
[    2.149765] remoteproc remoteproc0: powering up wkup_m3                      
[    2.149927] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf,8
[    2.153268] remoteproc remoteproc0: remote processor wkup_m3 is now up       
dmesg | grep pru                                                                
[    2.141588] remoteproc remoteproc1: 4a334000.pru is available                
[    2.141812] pru-rproc 4a334000.pru: PRU rproc node /ocp/interconnect@4a00000y
[    2.143965] remoteproc remoteproc2: 4a338000.pru is available                
[    2.144167] pru-rproc 4a338000.pru: PRU rproc node /ocp/interconnect@4a00000y
dmesg | grep pinctrl-single                                                     
[    1.420200] pinctrl-single 44e10800.pinmux: 142 pins, size 568               
dmesg | grep gpio-of-helper                                                     
[    1.440321] gpio-of-helper ocp:cape-universal: ready                         
lsusb                                                                           
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub                  
END  

new 8/2021 image
during boot: BeagleBone Cape EEPROM: 0x54: BB-BONE-LCD7-01-00A3.dtbo [0xfc93c8f]

no:

/opt/scripts/tools/version.sh

uname:
Linux BeagleBone 5.10.41-ti-r12 #1bullseye SMP PREEMPT Tue Aug 10 10:32:45 UTC 2021 armv7l GNU/Linux

sudo apt update
sudo apt install bb-cape-overlays
sudo reboot

There will be two built-in tools that will replace that…

sudo beagle-version
sudo beagle-config

Regards,

Thanks, this fixed the display issue.
sudo apt install bb-cape-overlays

FYI,
debian@BeagleBone:~$ sudo beagle-version
[sudo] password for debian:
sudo: beagle-version: command not found
debian@BeagleBone:~$ sudo beagle-config
sudo: beagle-config: command not found

sudo apt update
sudo apt install bb-beagle-config

I haven’t pushed it out yet…

Regards,

This is now fixed:

sudo apt update
sudo apt install bb-beagle-version
debian@BeagleBone:~$ sudo beagle-version
eeprom:[A335BNLT00C02516BBBK2626]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Bullseye IoT Image 2021-08-17]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot SPL 2019.04-g964dadb (Aug 12 2021 - 17:52:32 +0000)]:[location: dd MBR]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-g964dadb]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2019.04-g964dadb (Aug 12 2021 - 17:52:32 +0000)]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2019.04-g964dadb]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot-univ.dts]
UBOOT: Loaded Overlay:[BB-ADC-00A0.kernel]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.kernel]
UBOOT: Loaded Overlay:[BB-HDMI-TDA998x-00A0.kernel]
UBOOT: Loaded Overlay:[BBORG_RELAY-00A2.kernel]
kernel:[5.10.41-ti-r13]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]
pkg:[bb-cape-overlays]:[4.14.20210809.0-0~bullseye+20210816]
WARNING:pkg:[bb-customizations]:[NOT_INSTALLED]
pkg:[bb-usb-gadgets]:[1.20210816.0-0~bullseye+20210816]
WARNING:pkg:[bb-wl18xx-firmware]:[NOT_INSTALLED]
pkg:[kmod]:[28-1]
WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]
pkg:[firmware-ti-connectivity]:[20210315-3]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input bluetooth netdev admin tisdk weston-launch cloud9ide gpio]
cmdline:[console=ttyS0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BBORG_RELAY, coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   11.112099] remoteproc remoteproc0: wkup_m3 is available
[   41.013425] remoteproc remoteproc0: powering up wkup_m3
[   41.013466] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[   41.013779] remoteproc remoteproc0: remote processor wkup_m3 is now up
[   54.769206] remoteproc remoteproc1: 4a334000.pru is available
[   54.777452] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pru
[   54.769206] remoteproc remoteproc1: 4a334000.pru is available
[   54.777452] remoteproc remoteproc2: 4a338000.pru is available
dmesg | grep pinctrl-single
[   10.697235] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
[   10.699177] gpio-of-helper ocp:cape-universal: Failed to get gpio property of 'P8_03'
[   10.699211] gpio-of-helper ocp:cape-universal: Failed to create gpio entry
[   11.310465] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0 name='P8_03'
[   11.310697] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1 name='P8_04'
[   11.310904] gpio-of-helper ocp:cape-universal: Allocated GPIO id=2 name='P8_05'
[   11.311100] gpio-of-helper ocp:cape-universal: Allocated GPIO id=3 name='P8_06'
[   11.311616] gpio-of-helper ocp:cape-universal: Allocated GPIO id=4 name='P8_07'
[   11.311847] gpio-of-helper ocp:cape-universal: Allocated GPIO id=5 name='P8_08'
[   11.312075] gpio-of-helper ocp:cape-universal: Allocated GPIO id=6 name='P8_09'
[   11.312281] gpio-of-helper ocp:cape-universal: Allocated GPIO id=7 name='P8_10'
[   11.312479] gpio-of-helper ocp:cape-universal: Allocated GPIO id=8 name='P8_11'
[   11.312667] gpio-of-helper ocp:cape-universal: Allocated GPIO id=9 name='P8_12'
[   11.313118] gpio-of-helper ocp:cape-universal: Allocated GPIO id=10 name='P8_13'
[   11.313343] gpio-of-helper ocp:cape-universal: Allocated GPIO id=11 name='P8_14'
[   11.313547] gpio-of-helper ocp:cape-universal: Allocated GPIO id=12 name='P8_15'
[   11.313747] gpio-of-helper ocp:cape-universal: Allocated GPIO id=13 name='P8_16'
[   11.313933] gpio-of-helper ocp:cape-universal: Allocated GPIO id=14 name='P8_17'
[   11.314155] gpio-of-helper ocp:cape-universal: Allocated GPIO id=15 name='P8_18'
[   11.314355] gpio-of-helper ocp:cape-universal: Allocated GPIO id=16 name='P8_19'
[   11.314556] gpio-of-helper ocp:cape-universal: Allocated GPIO id=17 name='P8_20'
[   11.314750] gpio-of-helper ocp:cape-universal: Allocated GPIO id=18 name='P8_21'
[   11.314936] gpio-of-helper ocp:cape-universal: Allocated GPIO id=19 name='P8_22'
[   11.315128] gpio-of-helper ocp:cape-universal: Allocated GPIO id=20 name='P8_23'
[   11.315324] gpio-of-helper ocp:cape-universal: Allocated GPIO id=21 name='P8_24'
[   11.315512] gpio-of-helper ocp:cape-universal: Allocated GPIO id=22 name='P8_25'
[   11.315704] gpio-of-helper ocp:cape-universal: Allocated GPIO id=23 name='P8_26'
[   11.315887] gpio-of-helper ocp:cape-universal: Allocated GPIO id=24 name='P8_27'
[   11.316089] gpio-of-helper ocp:cape-universal: Allocated GPIO id=25 name='P8_28'
[   11.316280] gpio-of-helper ocp:cape-universal: Allocated GPIO id=26 name='P8_29'
[   11.316476] gpio-of-helper ocp:cape-universal: Allocated GPIO id=27 name='P8_30'
[   11.316674] gpio-of-helper ocp:cape-universal: Allocated GPIO id=28 name='P8_31'
[   11.316876] gpio-of-helper ocp:cape-universal: Allocated GPIO id=29 name='P8_32'
[   11.317174] gpio-of-helper ocp:cape-universal: Allocated GPIO id=30 name='P8_33'
[   11.317385] gpio-of-helper ocp:cape-universal: Allocated GPIO id=31 name='P8_34'
[   11.317576] gpio-of-helper ocp:cape-universal: Allocated GPIO id=32 name='P8_35'
[   11.317773] gpio-of-helper ocp:cape-universal: Allocated GPIO id=33 name='P8_36'
[   11.317967] gpio-of-helper ocp:cape-universal: Allocated GPIO id=34 name='P8_37'
[   11.318164] gpio-of-helper ocp:cape-universal: Allocated GPIO id=35 name='P8_38'
[   11.318356] gpio-of-helper ocp:cape-universal: Allocated GPIO id=36 name='P8_39'
[   11.318567] gpio-of-helper ocp:cape-universal: Allocated GPIO id=37 name='P8_40'
[   11.318775] gpio-of-helper ocp:cape-universal: Allocated GPIO id=38 name='P8_41'
[   11.318961] gpio-of-helper ocp:cape-universal: Allocated GPIO id=39 name='P8_42'
[   11.319155] gpio-of-helper ocp:cape-universal: Allocated GPIO id=40 name='P8_43'
[   11.319348] gpio-of-helper ocp:cape-universal: Allocated GPIO id=41 name='P8_44'
[   11.319531] gpio-of-helper ocp:cape-universal: Allocated GPIO id=42 name='P8_45'
[   11.319738] gpio-of-helper ocp:cape-universal: Allocated GPIO id=43 name='P8_46'
[   11.319949] gpio-of-helper ocp:cape-universal: Allocated GPIO id=44 name='P9_11'
[   11.320151] gpio-of-helper ocp:cape-universal: Allocated GPIO id=45 name='P9_12'
[   11.320346] gpio-of-helper ocp:cape-universal: Allocated GPIO id=46 name='P9_13'
[   11.320531] gpio-of-helper ocp:cape-universal: Allocated GPIO id=47 name='P9_14'
[   11.320726] gpio-of-helper ocp:cape-universal: Allocated GPIO id=48 name='P9_15'
[   11.320924] gpio-of-helper ocp:cape-universal: Allocated GPIO id=49 name='P9_16'
[   11.321221] gpio-of-helper ocp:cape-universal: Allocated GPIO id=50 name='P9_17'
[   11.321435] gpio-of-helper ocp:cape-universal: Allocated GPIO id=51 name='P9_18'
[   11.321628] gpio-of-helper ocp:cape-universal: Allocated GPIO id=52 name='P9_19'
[   11.321848] gpio-of-helper ocp:cape-universal: Allocated GPIO id=53 name='P9_20'
[   11.322048] gpio-of-helper ocp:cape-universal: Allocated GPIO id=54 name='P9_21'
[   11.322232] gpio-of-helper ocp:cape-universal: Allocated GPIO id=55 name='P9_22'
[   11.322434] gpio-of-helper ocp:cape-universal: Allocated GPIO id=56 name='P9_23'
[   11.322624] gpio-of-helper ocp:cape-universal: Allocated GPIO id=57 name='P9_24'
[   11.322842] gpio-of-helper ocp:cape-universal: Allocated GPIO id=58 name='P9_25'
[   11.323053] gpio-of-helper ocp:cape-universal: Allocated GPIO id=59 name='P9_26'
[   11.323246] gpio-of-helper ocp:cape-universal: Allocated GPIO id=60 name='P9_27'
[   11.323456] gpio-of-helper ocp:cape-universal: Allocated GPIO id=61 name='P9_28'
[   11.323666] gpio-of-helper ocp:cape-universal: Allocated GPIO id=62 name='P9_29'
[   11.323899] gpio-of-helper ocp:cape-universal: Allocated GPIO id=63 name='P9_30'
[   11.324107] gpio-of-helper ocp:cape-universal: Allocated GPIO id=64 name='P9_31'
[   11.324299] gpio-of-helper ocp:cape-universal: Allocated GPIO id=65 name='P9_41'
[   11.324509] gpio-of-helper ocp:cape-universal: Allocated GPIO id=66 name='P9_91'
[   11.324706] gpio-of-helper ocp:cape-universal: Allocated GPIO id=67 name='P9_42'
[   11.324898] gpio-of-helper ocp:cape-universal: Allocated GPIO id=68 name='P9_92'
[   11.324910] gpio-of-helper ocp:cape-universal: ready
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

Thanks,

A post was split to a new topic: BBB-Wireless Upgrade to Bullseye

Silly question, I’m updating a fleet of PocketBeagles which started out running Debian Stretch-based images.

The last OS update to Buster was achieved by adjusting /etc/apt/sources.list and doing an apt-get update && apt-get dist-upgrade -y, and that seemed to go fine.

I did the same trick yesterday on one of the nodes, and had the update fall flat on its face. I should hook up a serial console to see where it’s failing, but effectively it bricked the OS.

For now I just took a back-up of that failed update, then flashed the latest console image and I’m trying an apt-get dist-upgrade to Bullseye on that now. Update: Having done this, the PocketBeagle boots, but it appears the USB gadget support is broken by this sort of update, making the device inaccessible unless serial console is connected.

Looking in Index of /rootfs/debian-armhf/2021-12-12 I don’t see the console image listed. Are there plans to release such an image? In the application I’m using these for, we’re not using the Cloud9 and NodeRED features that are part of the IoT image, so keeping to a plain and minimal image is desirable.

Hi @sjlongland

I’l need to write some more directions on moving from stretch/buster to bullseye…

I’ve dropped conman for systemd-networkd, this allows us to use simple udev rules to enable a lot of things we did in stretch/buster (some of which is not backwards portable to stretch/buster due to new systemd features…)

the opt scripts directory is gone, everything has a debian package now…

yeah, i think we are ready for console/iot images for Bullseye, i’ve got most things works now days on Bullseye…

Regards,

1 Like

Hi Beagleboard community, Hi @RobertCNelson ,

In 2019 I finally finished my BBB-based NAS (with laser-cut housing). If you’re interested, read about it here.

Since 2018 it didn’t really get any proper software update, and other than the security issues (it’s not internet accessible right now), I’m also very limited by the packages still available.

I’m currently running on Ubuntu 14.04.6 LTS (GNU/Linux 4.4.21-ti-r45 armv7l).

With Debian 11, I could upgrade to the v5 kernel and get kernel support for exFAT so that our removable storage works on all OSses (windows + mac + linux).

Long story short: I’ve not been very active with embedded software in recent years and could use some advice on which image is stable to do a fresh install on the BBB. My goal is to have another rock-solid system that can last for years.

Features I’ve been using

  • EXT4 filesystem on eMMC (set up to auto-fix when power goes off unexpectedly)
  • EXT4 filesystem on SSD + HD (I’m spinning the drive down automatically when not used)
  • Solid kernel (the first one I had wasn’t stable)

Want to add

  • Set up a solid rsync backup
  • exFAT to backup external drives

Nothing too crazy, it just needs to be solid and low maintenance for years to come :slight_smile:

Thanks for all of your work!

Hi @phalox , so our 5.4.x-ti, 5.10.x-ti and 5.15.x-bone branches have exfat built-in. For the am335x you really don’t see an advantage between ti the branch and mainline anymore. As 99% of everything is mainline…

Most of my current testing is on v5.10.x and v5.15.x… I’m just finally starting to EOL v4.19.x in my test farm this week… (how many years of testing is that; Nov 2018… so 3 years…)

For the am335x i’d say start with v5.15.x and let me know if you have issues. Right now I’ve got 4 boards in my automatic tester running v5.15x, with more being transited later in the next few weeks…

Starting the 1st of the year, i will have Monthy Bullseye images, you can see a sneak peak with:

https://rcn-ee.net/rootfs/bb.org/testing/2021-12-28/bullseye-iot/

Regards,

Almost 2 months later! It’s about time I get started on this. But before I break my production system running off of the EMMC, I wanted to double check some things.

I see the latest testing image is am335x-debian-11.2-iot-armhf-2022-02-03-4gb.img.xz
Use balenaEtcher - Flash OS images to SD cards & USB drives to put it on an SD card
Plug it into the bbb, power it and it will boot from the SD card instead?

That’s great for testing!

How would I then proceed to flash it to emmc?

For reference, (as this thread) has a few old ones, latest can be found here…

@phalox, once you booted the first time (on microSD)… Just run:

sudo enable-beagle-flasher
sudo reboot

and it’ll set the bits needed to make it into an eMMC flasher image…

Regards,

Hi I have upgraded Buster to Bullseye. Most things go well. Anyway I would like to clear below problems which are seen during boot

debug: [bootz 0x82000000 0x88080000:6911b0 88000000] …

Flattened Device Tree blob at 88000000

Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8f96e000, end 8ffff1b0 … OK
Loading Device Tree to 8f8e2000, end 8f96dfff … OK

Starting kernel …

[ 0.002172] timer_probe: no matching timers found
[ 0.196984] l4_wkup_cm:clk:0010:0: failed to disable
[ 1.439860] omap_voltage_late_init: Voltage driver support not added
rootfs: clean, 132204/1888768 files, 977845/7790720 blocks
[ 8.833523] cgroup: cgroup2: unknown option “memory_recursiveprot”

Debian GNU/Linux 10 beaglebone ttyS0

BeagleBoard.org Debian Buster IoT Image 2020-04-06

Could you please guide me how I can proceed with that?

Hi @Michal_Poterek i see lots of ‘warnings’ but no real problems…

Please pin point which line you are woried about… PS your kernel might be too old, so please add the value of uname -r so we can help…

Regards,

Hi Robert, I’m running the new image now. On my legacy setup, I forced FSCK to auto fix any issues that might occur on the root file system (usually after power was dropped). I was now trying to reimplement this on the new image, but I’m not sure how to pass the ‘fsck -y’ to the systemd. Any advice?

Also, any clue why my root file system is absolutely full? Did the image size itself grow significantly or did I fill it up for some reason?

sudo du -h --max-depth=1
1.4M    ./root
4.0K    ./srv
11M     ./bin
4.0K    ./media
48K     ./tmp
7.2M    ./sbin
1.9G    ./usr <--------------
16K     ./lost+found
2.2M    ./run
714M    ./opt <--------------
0       ./proc
296M    ./lib
196K    ./home
16K     ./mnt
0       ./sys
467M    ./var <----------------
22M     ./etc
0       ./dev
34M     ./boot
3.4G    .

Is /usr/lib/arm-linux-gnueabihf (913M) installed by default? Or did I somehow put a compiler on this system? It’s so full right now that I cannot even do anything anymore :slight_smile: So I’m trying to figure out what to delete.

1 Like

sudo beaglecfg is the command to bring a SD Card to the full memory widths.

Seth

P.S. There is an option in that entry field for SD Card. If you have a higher GB SD Card, that command can work.

Just reboot…

The resize script auto runs on first boot, but it doesn’t finish till the 2nd…

Regards,