Sources for linux-dtb-current-sunxi64?

I tried to load the source code for linux-dtb-current-sunxi64, but apt-get is complaining:

gollumm64% sudo apt-get source linux-dtb-current-sunxi64
[sudo] password for heller: 
Reading package lists... Done
Picking 'linux-5.4.43-sunxi64' as source package instead of 'linux-dtb-current-sunxi64'
E: Unable to find a source package for linux-5.4.43-sunxi64
gollumm64% apt-get source linux-dtb-current-sunxi64
Reading package lists... Done
Picking 'linux-5.4.43-sunxi64' as source package instead of 'linux-dtb-current-sunxi64'
E: Unable to find a source package for linux-5.4.43-sunxi64

How do I get the source code for this package? I’d like to modify /boot/dtb-5.4.43-sunxi64/allwinner/sun50i-a64-bananapi-m64.dtb – I think I need to change something in it to enable the eMMC.

… if its just enabling.

Yes, I just need to enable the eMMC. I install the kernel source tree and tied to modify the DTS and did build an alternitive version of the dtb, but that did not help.

Well, nevermind. In the process of following posts to try to get the camera working, I managed to upgrade the kernel (to 5.7.15-sunxi64), and suddenly /dev/mmcblk2 showed up (but not the camera…).

HI Robert, I saw that you found the solution for your problem by upgrading the linux. Refering to your original question, if you would have such apt complains, you could try:

  • make apt update for refresh packages list and try again,
  • check /etc/apt/sources.list for URL of repositiories that are checked,
  • uncomment these one that are refering to sources (you searched for sources),
  • visit the links by a web browser
  • try to find your package (somethimes releases may contain the package you need - be aware of dependencies) The path on server may be changed if your system is old, you need to update it in sources.list.

Armbian presents overlays some general examples as well as specific for chip versions:

Unfortunatelly BPI-M64 has some differences in device tree, so overlays in example folder need to be tuned to be correct for that chip type. If it is a case please read uboot messages on serial console and check /sys/firmware/basic/…

Regards,

Piotr Romaniuk