[Who can share their valid /etc/apt/sources.list for an armhf SBC?]

Does not matter now. I've upgraded to Noble, but it was not straightforward.  Had some post-install fixing-up do do.

[Who can share their valid /etc/apt/sources.list for an armhf SBC?]

No.  It's a BananaPi Pro, but the question, in general, covers all SBCs that use the armhf processor and the Ubuntu operating system.

 

This is what happens when I try and perform an apt update:

 

Hit:1 http://ports.ubuntu.com/ubuntu-ports jammy InRelease
Hit:2 http://archive.canonical.com/ubuntu focal InRelease
Hit:4 https://download.docker.com/linux/ubuntu jammy InRelease
Hit:5 http://ppa.launchpad.net/eivnaes/network-manager-sstp/ubuntu focal InRelease
Get:6 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Get:7 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [128 kB]
Hit:3 http://netcup.armbian.com/apt jammy InRelease
Hit:8 https://github.armbian.com/configurator stable InRelease
E: Repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' changed its 'Origin' value from 'Armbian' to 'Ubuntu'
E: Repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' changed its 'Label' value from 'Armbian' to 'Ubuntu'
N: Repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' changed its 'Version' value from '' to '22.04'
N: Repository 'http://security.ubuntu.com/ubuntu jammy-security InRelease' changed its 'Suite' value from 'jammy' to 'jammy-security'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
E: Repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' changed its 'Origin' value from 'Armbian' to 'Ubuntu'
E: Repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' changed its 'Label' value from 'Armbian' to 'Ubuntu'
N: Repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' changed its 'Version' value from '' to '22.04'
N: Repository 'http://archive.ubuntu.com/ubuntu jammy-updates InRelease' changed its 'Suite' value from 'jammy' to 'jammy-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
Do you want to accept these changes and continue updating from this repository? [y/N] y
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf Packages
Get:10 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf DEP-11 Metadata [158 B]
Get:11 http://archive.ubuntu.com/ubuntu jammy-updates/restricted DEP-11 48x48 Icons [29 B]
Get:12 http://archive.ubuntu.com/ubuntu jammy-updates/restricted DEP-11 64x64 Icons [29 B]
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf Packages
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf DEP-11 Metadata [489 kB]
Get:15 http://archive.ubuntu.com/ubuntu jammy-updates/universe DEP-11 48x48 Icons [247 kB]
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/universe DEP-11 64x64 Icons [398 kB]
Ign:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf Packages
Get:18 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf DEP-11 Metadata [159 B]
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse DEP-11 48x48 Icons [1,867 B]
Get:20 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse DEP-11 64x64 Icons [2,497 B]
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf Packages
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf Packages
Ign:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf Packages
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf Packages
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf Packages
Ign:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf Packages
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf Packages
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf Packages
Ign:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf Packages
Ign:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf Packages
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf Packages
Ign:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf Packages
Err:9 http://archive.ubuntu.com/ubuntu jammy-updates/restricted armhf Packages
  404  Not Found [IP: 2620:2d:4000:1::103 80]
Ign:13 http://archive.ubuntu.com/ubuntu jammy-updates/universe armhf Packages
Ign:17 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse armhf Packages
Fetched 1,396 kB in 27s (50.9 kB/s)
Reading package lists... Done
N: Ignoring file 'azlux.zip' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension
E: Failed to fetch http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease
E: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/jammy-updates/restricted/binary-armhf/Packages  404  Not Found [IP: 2620:2d:4000:1::103 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

 

I'm aware of the issue relating to `azlux.zip`.  I've just not yet moved that zip file out of sources.list.d.

[Who can share their valid /etc/apt/sources.list for an armhf SBC?]

Who can share their valid /etc/apt/sources.list for an armhf SBC?

 

Some past update has messed mine up a bit.

 

Mine is:

 

# deb http://gb.archive.ubuntu.com/ubuntu/ jammy main universe restricted multiverse
deb [arch=armhf] http://ports.ubuntu.com/ubuntu-ports/ jammy main universe restricted multiverse

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
# deb http://archive.ubuntu.com/ubuntu/ jammy main restricted
# deb-src http://archive.ubuntu.com/ubuntu/ jammy main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb [arch=armhf] http://archive.ubuntu.com/ubuntu/ jammy-updates restricted
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
# deb http://archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://archive.ubuntu.com/ubuntu/ jammy universe
deb [arch=armhf] http://archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
# deb http://archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ jammy multiverse
deb [arch=armhf] http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse

deb [arch=armhf] http://security.ubuntu.com/ubuntu/ jammy-security restricted
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security main restricted
deb [arch=armhf] http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security universe
deb [arch=armhf] http://security.ubuntu.com/ubuntu/ jammy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security multiverse

deb [arch=armhf] http://archive.canonical.com/ubuntu focal partner

 

[Build Armbian in Distro box?]

Hello @Werner, so is the recommendation not to do a do-release-upgrade just yet?

[Apart from the usual `backup before upgrading`. Should I invoke a do-release-upgrade to update to Ubuntu 24.04.1 LTS?]

Does anyone know how a do-release-upgrade affect an Armbian 24.8.3 installation?  Had anyone upgraded to the 24.04.1 LTS release of Ubuntu?

Any gotyas when upgrading?  Things to do and things to avoid?  What changes to allow and which to deny?

 

I've done a release upgrade once, it took a long time and questions were asked and options presented suring the release upgrade process.

 

Obviously I'll take an image of the MicroSD card before I even dream of attempting to use the do-release-upgrade.

[Frequent `rcu: INFO: rcu_sched detected stalls on CPUs/tasks` events logged.]

So...  Taken the latest Armbian system update and on kernel version  6.6.31 no more CPU stalls.  🙂

Whoever fixed this, thank-you.

[Frequent `rcu: INFO: rcu_sched detected stalls on CPUs/tasks` events logged.]

This started happening since accepting the kernel when I used apt to upgrade the BananaPi Pro sbc I've got.

 

armbianmonitor report:

https://paste.armbian.com/izuboducul

 

@teknoid are you aware of this?

[USB problem on armbian]

Provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[fake chinese X96Q the 1/8 gb with the H313]

You mentioned that it's a fake.  Possibly because it is a copy it may have not be a perfect copy and that may be why you can't find firmware that will work with it. Also, the only place to find official Armbian images.

 

Have you tried building your own image using the Armbian build tools?  That way you can customise the image you're building to your requirements.

 

Read the Armbian documentation:  https://docs.armbian.com/

 

 

[OrangePi H3 does not start, only network leds are on]

Have you gone through the basic troubleshooting steps?

See: https://docs.armbian.com/User-Guide_Basic-Troubleshooting/

[A normal update has resulted in "No end-user support: untested automated build"]

Maybe there has been a glitch in the update release process?  I performed a sudo apt update && sudo apt upgrade and this has pulled down an automated build.  Should it had pulled down a supported build instead?

[help with ufw :(]

@NepT1 I think ufw and iptables-restore are not compatible with each other.  Several articles on the Internet I've seen seem to mention to turn off UFW if using iptables-restore. Something I've not looked at for myself so I need to do some of my own research.

To signpost you, I guess a good place to start is a Google search like, or similar to:  https://www.google.com/search?q=linux+"iptables-restore"+"ufw"

[Reset password root]

https://docs.armbian.com/User-Guide_Recovery/

[Booting into Cinnamon desktop after installation from armbian-config]

@Esteve Have a look at this article: https://www.cyberciti.biz/faq/switch-boot-target-to-text-gui-in-systemd-linux/

What is the result of the command ...

systemctl get-default

... ?

[FireFly station P2 on Armbian 22.11 Bullseye XFCE does not work on a 4K monitor.]

Yup. That's an oops on my part.  If you've got one, use a USB to Serial card to connect a computer to the serial debug port on the SBC and you'll be able to login to the system that way and then try diagnose the issue that way.

See: https://wiki.t-firefly.com/en/ROC-RK3568-PC/debug.html

 

When I started with my Banana Pi Pro I could not get any video to display on the HDMI port right from the beginning.  When I got a USN-to-Serial bridge I completed the initial setup using that method and, mysteriously, the HDMI port started to work and still works to this day.

[FireFly station P2 on Armbian 22.11 Bullseye XFCE does not work on a 4K monitor.]

Provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[Auto mount USB]

Try this: https://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs

Found it using a search on Google using: linux automount usb drive

[polybar don't start]

Moved from the Beginners forum.

[Orange pi 5 with latest debian and RemoteDesktop (XRDP) hangs on reboot via ssh]

Provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  I don't know why this is happening buy it may help others determine what the issue is.

[Rock Pi 4B+ UART/UART4 no data]

Can you please provide diagnostic logs for the Rock Pi 4B+ with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[Green screen when i take a picture with pygame on jetson nano]

Please provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[Board Becomes Unresponsive to Remote Connections After a Time]

Please provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[Can't update the armbian on banana pi m5]

@RES ... except when I look at the diagnostic log there is no mmc0 device.  There is an mmcblk0.  Is this the one you're referring to?

[Can't update the armbian on banana pi m5]

@cryk_ Have you run a file system check and repair on the root file system?  There are conditions where if the file system is not clean then the root file system is always mounted as read-only.

Also check the /etc/fstab file and make sure there are no errors and/or inconsistencies in there.

 

Also see:  https://www.thegeekstuff.com/2016/03/forcefsck-on-reboot/. Should work on an Armbian built system. I believe it is safe to invoke e2fsck on a read-only root file system as nothing is getting written. It's dangerous to use e2fsck on a read-write root file system and I don't believe e2fsck will allow you to perform repair operations on a read-write enabled file system.

[Can't update the armbian on banana pi m5]

@cryk_ Provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

 

The diagnostic logs might reveal why your file system is read-only and not read-write.