1

I'm trying to follow the instruction https://wiki.ubuntu.com/ARM/RaspberryPi to install Ubuntu ARM64 on my Raspberry Pi 3B+.

The ISO file I chose is Ubuntu Server 18.04 ARM64 (not mini), written to a USB stick.

In installation procedure, it says: No network interfaces detected

Any ideas?

Thanks.

Improve this question
1
  • Update: If I choose to install without network, it will failed later: grub cannot be installed. It seems that ARM64 release of ubuntu server 18.04 is not ready for RPi3B+
    – Allen St.Clair
    Jun 1, 2018 at 13:25

5 Answers 5

Reset to default
1

This script will download the generic arm64 server iso and convert it to use the raspi2 kernel - https://1drv.ms/u/s!AvHY_kl4hMB4gQXOBm-XGx8sp457

Once run, copy all the files in the server-raspi2 folder to a usb fat formatted drive. Make sure you copy the hidden '.disk' folder.

The installer has a largish initramfs so there is longer than usual pause at the pi rainbow screen. The installer also pauses for a long time when it searches for the cdrom. If you select the 'erase disk and install' option then the installation should work.

Improve this answer
19
  • Your script should check whether 7z is installed before downloading iso... lol
    – Allen St.Clair
    Jun 22, 2018 at 1:14
  • Something's wrong: No USB keyboard supported in my 3b+ while installing. No way to install...
    – Allen St.Clair
    Jun 22, 2018 at 1:38
  • That's annoying. You'll either have to add the kernel modules to the initramfs, or preseed the locale/keyboard questions via cmdline.txt so that you get to the stage where modules are loaded from the cdrom. If the cdrom fails to detect then you'll definitely have to go the initramfs route.
    – Adam Smith
    Jun 22, 2018 at 8:28
  • 7z is pretty standard. What are you using?
    – Adam Smith
    Jun 22, 2018 at 8:29
  • This standardized USB keyboard is working well with lots of systems. Actually, this is the 1st time I found it cannot work. How to add keyboard support to your installation media?
    – Allen St.Clair
    Jun 22, 2018 at 9:01
1

The generic arm64 kernel in 18.04 doesn't have a dtb file for the 3B+ so I'm not sure what works. I had hoped it would still work with the dtb file built into uboot.

If you can't get it to work then this https://ubuntu-mate.community/t/aarch64-on-raspberry-pi-2-rev-1-2-3b-3b/16853 should work on the 3B+ because it uses the raspi2 kernel.

Improve this answer
8
  • i'm using the one built for 3B. The name of the file for 3B is only including the CPU brand and number, that may confused me.
    – Allen St.Clair
    May 30, 2018 at 15:53
  • BTW, could you explain what's the different between raspi2 kernel and the one in ARM64 official release?
    – Allen St.Clair
    May 30, 2018 at 15:56
  • It should boot without a dtb file. Remove it and see what happens. If you still don't have network then you could try insmod'ing the correct module.
    – Adam Smith
    May 30, 2018 at 18:01
  • 1
    The raspi2 kernel is Ubuntu's version of the 'downstream' kernel from the raspberry pi foundation. You can boot it without grub2. The generic arm64 is the upstream kernel. There are a few differences in the modules used, and the dtb file names.
    – Adam Smith
    May 30, 2018 at 18:05
  • without dtb file, it can boot, but still with lacking of nic.
    – Allen St.Clair
    May 31, 2018 at 5:07
0

I think the 3B+ uses the lan78xx.ko module. Check if you have that module in the debian installer. If you don't then you can extract it from the kernel deb, copy it to the 'cdrom' and insmod it.

Improve this answer
23
  • I don't think that is the problem related to installer. When booting from u-boot, the 1st line displayed is no ethernet found. I also tested copying 3b+ deb file from the RASPBIAN into u-boot partition. The problem is the same.
    – Allen St.Clair
    May 31, 2018 at 7:49
  • I put the lan78xx.ko to usb stick at boot, once. But now no matter I attach this usb or not, the boot process is blocked in lan78xx_eth Waiting for PHY auto negotiation to complete. And nothing changed in SD either.... What's wrong here.
    – Allen St.Clair
    May 31, 2018 at 8:22
  • I still have no way to pass the driver right to installer. I use dd to write iso to usb stick (if only file copy, it wont start up). And the shell of the installer dont let me mount any partition --- Invalid argument
    – Allen St.Clair
    Jun 1, 2018 at 8:15
  • You should be able to mount a partition. I've done it before now. I can't remember doing anything special, but that might be my mind playing tricks! Re: copy vs dd....copying would be beneficial here. Did you copy the hidden ".disk" folder?
    – Adam Smith
    Jun 1, 2018 at 17:56
  • Yes, I did copy all files including all hidden. Nvm, installing process will fail later for grub error. I think I have to install xubuntu and then remove all desktop components.
    – Allen St.Clair
    Jun 2, 2018 at 14:49
0

Argh, sorry about the answer spam. Different computers, different logins apparently and I can't add a comment. You may need the microchip.ko module which is the corresponding PHY driver.

Improve this answer
1
0

Similar problem in 18.04 server armhf, not identical configuration, was resolved by edit of netplan setup to define static eth0 ip defs.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .