Issues creating dietpi image for banana m4

Creating a bug report/issue

Details:

  • Date | 2025-12-09 00:26:48
  • Program name | DietPi-Installer
  • Command | apt-get -y --allow-change-held-packages install initramfs-to ols linux-image-pine64 u-boot-tools
  • Exit code | 100
  • DietPi version | v9.19.2 (MichaIng/master)
  • Distro version | bookworm (ID=7,RASPBIAN=0)
  • Kernel version | Linux bpi-iot-ros-ai 4.9.119-BPI-M4-Kernel #1 SMP PREEMPT Mo n May 18 10:41:36 HKT 2020 aarch64 GNU/Linux
  • Architecture | arm64
  • Hardware model | (ID=22)
  • Power supply | (EG: RAVPower 5V 1A)
  • SD card | (EG: SanDisk Ultra 16 GB)

Steps to reproduce:

  1. begin from

2020-05-18-ubuntu-18.04-mate-desktop-bpi-m4-aarch64-sd-emmc.img.zip

  1. remove xorg packages, upgrade to bookworm by this guide

  2. bash -c “$(curl -sSfL ‘ttps://raw.githubusercontent.com/MichaIng/DietPi/master/.build/images/dietpi-installer’)”
    (i removed “h” because of limitations for number of urls, it is from official guide and i can’t make it not url otherwise)

  3. I choose Trixie

Expected behaviour:

  • dietpi installation

Actual behaviour:

  • linux-image-pine64 does not install

Extra details:

  • …

Additional logs:

Reading package lists...                                                        
Building dependency tree...                                                     
Reading state information...                                                    
Package linux-image-pine64 is not available, but is referred to by another packa
ge.                                                                             
This may mean that the package is missing, has been obsoleted, or               
is only available from another source                                           
                                                                                
E: Package 'linux-image-pine64' has no installation candidate

How do you upgrade an Ubuntu system to Debian Bookworm?

DietPi is based on Debian. You can’t use Ubuntu base image

it just… worked for me. apt did not complain about debian repositories. I have issues downloading stretch image for bpi-m4, so i started from ubuntu mate. Can that influence the outcome of apt not finding linux-image-pine64 in trixie repos that dietpi script put into my sources.list?

root@bpi-iot-ros-ai:/tmp/DietPi-Installer# cat /etc/apt/sources.list            
deb https://deb.debian.org/debian/ trixie main contrib non-free non-free-firmwar
e                                                                               
deb https://deb.debian.org/debian/ trixie-updates main contrib non-free non-free
-firmware                                                                       
deb https://deb.debian.org/debian-security trixie-security main contrib non-free
 non-free-firmware                                                              
deb https://deb.debian.org/debian/ trixie-backports main contrib non-free non-fr
ee-firmware 

linux-image-pine64 is not a debian package at all:
https://packages.debian.org/search?lang=en&suite=trixie&searchon=names&keywords=linux-image-pine64
What do you mean with linux-image-pine64?

edit:

This package does not exist in the apt repo at all.
But the BananaPi M4 uses a RK3399, so it should be linux-image-arm64 maybe? But why is it detected as Pine64?
@Katie do you have more of the log before the error occured?

For my understanding of the script, it should’ve picked

	# G_HW_MODEL 24 Generic Rockchip RK3399

But it got

	# G_HW_MODEL 40 PINE A64

@MichaIng what do you think?

I choose “print report” in the error window and in the topic is what it outputted me

i have opened shell for that error. how can i obtain more logs?

You can have a look into /var/tmp/dietpi/logs.
Ubuntu loggs into the journal, but since a lot gets removed, idk if you will find anything useful about the dietpi isntallation there, but you can have a look

journalctl

Folks, please don’t keep messing around with Ubuntu images. This will only cause more problems later on and is not supported by us.

Your are always so reasonable :smiley:
But yes, you are also right: No more support for this problem.

It’s not that we don’t want to help. But even if it works for now, who’s to say there won’t be problems in the future? And then no one will remember that it was once an Ubuntu system. Who knows? There’s a reason why we don’t support Ubuntu as a source. There is a difference between it and Debian after all.

linux-image-pine64 got autodetected by our installer as kernel package to keep. But it looks like that package is not installed anymore, just its config files which keeps it in the database.

Anyway, yes it the base image was Ubuntu, ot won’t work anyway.