Bug#1009670: installation-reports: Mostly working installation on rockpro64

2022-04-20 Thread Diederik de Haas
On Thursday, 14 April 2022 05:02:26 CEST Vagrant Cascadian wrote:
> On 2022-04-13, Vagrant Cascadian wrote:
> > I will admit I used a tained image that added a couple modules for
> > HDMI output on another platform (rock64); I'll check without the extra
> > modules and report back if they're needed.
> 
> Grahpical installer seems to work out of the box on rockpro64, yay!

Do you know what's the status wrt Bullseye installer and the RockPro64?
Does it work? Does HDMI output work? Or is a serial adapter needed?

signature.asc
Description: This is a digitally signed message part.


Bug#1009670: installation-reports: Mostly working installation on rockpro64

2022-04-13 Thread Vagrant Cascadian
On 2022-04-13, Vagrant Cascadian wrote:
> I will admit I used a tained image that added a couple modules for
> HDMI output on another platform (rock64); I'll check without the extra
> modules and report back if they're needed.

Grahpical installer seems to work out of the box on rockpro64, yay!

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1009670: installation-reports: Mostly working installation on rockpro64

2022-04-13 Thread Vagrant Cascadian
Package: installation-reports
Severity: normal
X-Debbugs-Cc: vagr...@debian.org

Boot method: microSD media
Image version: 
https://d-i.debian.org/daily-images/arm64/20220413-02:17/netboot/gtk/SD-card-images/
Date: 2022-04-13 ~2:00:00 UTC

Machine: Pine64 Rockpro64 RK3399
Partitions:
Filesystem  Type 1K-blocksUsed Available Use% Mounted on
udevdevtmpfs   1925472   0   1925472   0% /dev
tmpfs   tmpfs   395808 944394864   1% /run
/dev/mapper/rkp64a-rewt ext4   4721184 1222728   3237952  28% /
tmpfs   tmpfs  1979032   0   1979032   0% /dev/shm
tmpfs   tmpfs 5120   0  5120   0% /run/lock
/dev/sda5   ext4447306   65659353129  16% /boot
tmpfs   tmpfs   395804   0395804   0% /run/user/1000


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect media:   [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [E]
Install base system:[O]
Install tasks:  [O]
Install boot loader:[O]
Overall install:[O]

Comments/Problems:

This wasn't *too* easy, but not too bad either.

The initial boot failed because I was unable to change the partition
type to be bootable, and there is another OS install on this disk. I
tried unmarking the bootable partition of the other install but upon
selecting it, nothing changed. Same for trying to mark the partition I
wanted it to boot from as bootable.

My guess is this is because with GPT partition tables bootable is not
a flag but a partition type?

I worked around this by manually adjusting the partition table to
change the partition types for the two partitions to use the "EFI
System" partition that u-boot, for better or worse, uses as a flag to
mark the partition as bootable.

The daily images use u-boot 2022.04+dfsg-2, which supports booting
from devices on a PCIe sata card for rockpro64, although not all sata
cards work, apparently. With older versions of u-boot (or if you have
an unlucky pick of sata cards) you would have to put /boot on a
microSD or eMMC device.


I will admit I used a tained image that added a couple modules for
HDMI output on another platform (rock64); I'll check without the extra
modules and report back if they're needed.


live well,
  vagrant


-- Package-specific info:

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/Linux installer"
DISTRIB_RELEASE="12 (bookworm) - installer build 20220413-02:01:57"
X_INSTALLATION_MEDIUM=netboot-gtk

==
Installer hardware-summary:
==
uname -a: Linux rkp64w 5.16.0-6-arm64 #1 SMP Debian 5.16.18-1 (2022-03-29) 
aarch64 GNU/Linux
lspci -knn: 00:00.0 PCI bridge [0604]: Fuzhou Rockchip Electronics Co., Ltd 
RK3399 PCI Express Root Port [1d87:0100]
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 01:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 
Serial ATA Controller [1b21:0612] (rev 02)
lspci -knn: Subsystem: ASMedia Technology Inc. Device [1b21:1060]
lspci -knn: Kernel driver in use: ahci
lspci -knn: Kernel modules: ahci
usb-list: 
usb-list: Bus 01 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.16.0-6-arm64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 02 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.16.0-6-arm64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 03 Device 01: EHCI Host Controller [1d6b:0002]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.16.0-6-arm64 ehci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 04 Device 01: Generic Platform OHCI controller [1d6b:0001]
usb-list:Level 00 Parent 00 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Linux 5.16.0-6-arm64 ohci_hcd
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus 04 Device 02: Generic USB Hub [04fe:0008]
usb-list:Level 01 Parent 01 Port 00  Class 09(hub  ) Subclass 00 Protocol 00
usb-list:Manufacturer: Chicony
usb-list:Interface 00: Class 09(hub  ) Subclass 00 Protocol 00 Driver hub
usb-list: 
usb-list: Bus