+- PINE64 (https://forum.pine64.org)
+-- Forum: Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=111)
+--- Forum: Linux on Pinebook Pro (https://forum.pine64.org/forumdisplay.php?fid=114)
+--- Thread: Kernel panic on boot with danielt's Debian installer (/showthread.php?tid=14084)
Pages:
1
2
RE: Kernel panic on boot with danielt's Debian installer - KiteX3 - 07-08-2021
(06-07-2021, 07:49 PM)jbrock Wrote: This is so perplexing to me.
Have you all tried this image? https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images
I think the included kernel is ready / almost fully ready.
I tried this out today and it actually booted with a virtual terminal command line installer. Nice! I wasn't able to install since it didn't seem to include the firmware drivers for the Pinebook Pro (and it seems to be a netinstall image) and I hadn't backed up my current Daniel Thompson's installer image, but it's still nice to be able to run *something* that's mainline Debian on my PBP.
Edit: I got back home and tried to complete the netinstall process, but unfortunately it didn't work; it failed the "Installing Software" stage and then after that the "Making bootable" stage, and after being forced to abort the installation it (naturally) wouldn't boot. I'm still glad the installer at least started, but it certainly wasn't ready to do a complete functional Debian install.
RE: Kernel panic on boot with danielt's Debian installer - moonwalkers - 07-09-2021
(07-08-2021, 11:18 AM)KiteX3 Wrote: I tried this out today and it actually booted with a virtual terminal command line installer. Nice! I wasn't able to install since it didn't seem to include the firmware drivers for the Pinebook Pro (and it seems to be a netinstall image) and I hadn't backed up my current Daniel Thompson's installer image, but it's still nice to be able to run *something* that's mainline Debian on my PBP.
Edit: I got back home and tried to complete the netinstall process, but unfortunately it didn't work; it failed the "Installing Software" stage and then after that the "Making bootable" stage, and after being forced to abort the installation it (naturally) wouldn't boot. I'm still glad the installer at least started, but it certainly wasn't ready to do a complete functional Debian install.
I've followed the official installer through on my original PB, and the issue I found is that by default the way it partitions eMMC doesn't leave any space for u-boot. It also doesn't install u-boot automatically. So if you use that installer you need to:
- make sure you partition manually and the very first usable partition starts at exactly 16MiB mark - this part is a bit hard to do from within the installer itself though as it prefers decimal prefixes instead of binary.
- after installation you may need to either use a trick with yanking the SD card out as soon as u-boot loaded from it--that can result in u-boot loading from SD card but then booting system from eMMC instead of going back into installer--or going through installer until it loads the necessary components to detect eMMC, then switch to another VT (say, VT2), mount eMMC, mount other necessary file systems, chroot into newly installed system, install u-boot-rockchip, and run `u-boot-install-rockchip /dev/mmcblk2` - just make sure you use correct device name for eMMC.