Debian emmc installer

[db579]

I'm trying to install Debian on the emmc. I've tried building an image from the firmware and partition images here https://deb.debian.org/debian/dists/bull...rd-images/ and here https://d-i.debian.org/daily-images/arm6...rd-images/.

In both cases no network interfaces are detected at all and it appears wifi drivers are missing, meaning I can't complete the install.

Is it expected that those images don't contain the driver? (I thought the netboot spin included non-free?). What is the best way of getting that driver? Is there another image I should be using?

[jsch]

take a look on https://forum.pine64.org/showthread.php?tid=16862, maybe this gives an idea what needs to be done in your case

[db579]

take a look on https://forum.pine64.org/showthread.php?tid=16862, maybe this gives an idea what needs to be done in your case

Thanks. I was hoping to avoid needing to buy a USB eth adapter but looks like it's the easiest (only?) way for now.

[jsch]

You could install the system without the wifi driver, use a usb-stick to copy the necessary packages over once debian is installed on the pinebook. My pinephone came with the dock, hence I chose this approach.

[TRS-80]

Generally speaking, Armbian is going to be far ahead of upstream (vanilla Debian) on any sort of SBC type device (including PBP) because Arm/SBC world is so different from x86.

Having said that, there is currently an issue with installing Armbian to eMMC. Not sure what's up with that, pretty sure it used to work. I hope to have my new PBP in my hands in a few more days, then I can maybe try and see what's happening. In the meantime, it should run well off SD card.

[db579]

Right tried installing with a USB ethernet adapter (worked on the roght USB port only not the left), seema like everything installs fine but at the very end it fails to reboot and doesn't boot thereafter. I'm trying the guided partitioning with encrypted LVM, could that be an issue or is that expected to work fine?

[db579]

Actually looks like it might be unrelated to luks after all, the same thing seems to happen with an unencrypted install