On 2023-04-02, znoteer@mailbox.org wrote: > On Wed, Mar 15, 2023 at 09:50:23AM -0400, Znoteer wrote: >> On Tue, Mar 14, 2023 at 11:34:42PM +0100, Cyril Brulebois wrote: >> > Znoteer <znoteer@mailbox.org> (2023-03-14): >> > How reliable is your storage? >> > >> > Mar 14 21:26:04 in-target: dpkg-deb (subprocess): decompressing archive '/tmp/firmware-brcm80211_20230117-2_all.deb' (size=5349764) member 'data.tar': lzma error: compressed data is corrupt >> > Mar 14 21:40:09 in-target: dpkg-deb (subprocess): decompressing archive '/tmp/apt-dpkg-install-JqSiZc/097-libllvm15_1%3a15.0.6-4+b1_arm64.deb' (size=20662856) member 'data.tar': lzma error: compressed data is corrupt^M >> >> I'm not sure how to answer that. It's an nvme drive that I bought for this pinebook pro, so was new though I've had the pinebook pro for some time. Some NVME draw a bit too much power with the default power profiles, but can be configured to be a bit more conservative. I picked slower NVME devices partly to avoid having to do this, and still I had one NVME that was reliable, and one that was not out-of-the-box (but worked fine in another computer). You might want to set the NVME power usage (using the "nvme" command from the "nvme-cli" package): https://wiki.pine64.org/index.php/Pinebook_Pro#Post_NVMe_install_power_limiting Main commands that are useful are "nvme id-ctrl" to see the various power profiles, and "nvme get-feature" and "nvme set-feature" to select a different profile. > I've succesfully installed, first try, Armbian to the eMMC of my Pinebook Pro. Install is maybe not as accurate as "copied". ... > I took out the SD card after and rebooted (I chose not to write anything to SPI as I was confident that Tow-boot would do). Since you're using Tow-boot (presumably installed to SPI?), you might be booting in EFI mode, and grub might be using the device-tree that is provided by Tow-boot... which might not be fully compatible with the kernel you are running. You might have to configure grub to use the device-tree consistent with your kernel (which is unfortunately more difficult than it ought to be). Alternately, switch to using u-boot-menu which generates an extlinux.conf boot menu, or flash-kernel boot scripts... both of those will use a device-tree that matches your running kernel. Another option might be to try the sd-card-images: https://ftp.debian.org/debian/dists/bookworm/main/installer-arm64/current/images/netboot/SD-card-images/ Or the same thing from the daily-images: https://d-i.debian.org/daily-images/arm64/daily/ ... which appears to be missing the netboot images today (probably in the middle of the kernel transition) ... Technically, the Tow-boot on your SPI (or eMMC?) will likely take over and not use the u-boot on the microsd, but I *think* it should support those images, which should pass the correct device-tree at least. You might need a USB-ethernet adapter if the wifi firmware is not included in those images... or otherwise do the firmware dance to get the wifi working (I've only ever used the pinebook-pro-rk3399 with USB ethernet/wifi). live well, vagrant
Attachment:
signature.asc
Description: PGP signature