Bug#971606: installation-reports cubieboard 5

[Валериан Пережигин]

Bug#971606: installation-reports cubieboard 5

[Geert Stappers]

On Sun, Oct 04, 2020 at 01:03:00AM +0300, Валериан Пережигин wrote:
> 03.10.2020, 22:53, Geert Stappers
> > Please rerun the installer, find a shell, do `lsblk`
> > and pretty please report back.
> 
> BusyBox v1.30.1 (Debian 1:1.30.1-4) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> ~ # lsblk
> /bin/sh: lsblk: not found
> ~ # ls
> ls lsmod lspci lsscsi
> ~ # blk
> blkdiscard blkid

Ah, yes that command


> ~ # blkid
> /dev/sda1: LABEL="cb5-boot" UUID="a3d6a5a1-9796-4605-a317-8bdc94af219e" 
> TYPE="ext2" PARTUUID="fdb06b7f-01"
> /dev/sda2: UUID="87c9e46c-1293-474e-801d-3a0f5ee3569d" TYPE="swap" 
> PARTUUID="fdb06b7f-02"
> /dev/sda3: LABEL="cb5" UUID="adb31049-edbb-4d50-b4a2-0aca6a82159b" 
> TYPE="ext4" PARTUUID="fdb06b7f-03"
> /dev/sda4: LABEL="cb5-home" UUID="29c228f9-6541-4ff7-bf5c-44ebb8eebe6d" 
> TYPE="ext4" PARTUUID="fdb06b7f-04"
> /dev/sdb1: LABEL_FATBOOT="BLACK16G" LABEL="BLACK16G" UUID="6088-862B" 
> TYPE="vfat" PARTUUID="b7bb8d8a-01"
> /dev/sdb2: LABEL="DebTry" UUID="e95a4f9e-e1fb-4679-9d1d-63a516e76a8a" 
> TYPE="ext4" PARTUUID="b7bb8d8a-02"
> /dev/sdb3: UUID="3ee578b5-a253-459e-810d-34885848b8b5" TYPE="swap" 
> PARTUUID="b7bb8d8a-03"
> /dev/sdb4: LABEL="DebTry-home" UUID="221e7afe-a030-40e5-8bdf-79bea0e0fcaa" 
> TYPE="ext4" PARTUUID="b7bb8d8a-04"
> /dev/loop0: UUID="2020-09-26-15-00-29-00" LABEL="Debian 10.6.0 armhf 1" 
> TYPE="iso9660" PTTYPE="dos"
> ~ #

/dev/sda, /dev/sdb  and /dev/loop0.

No /dev/mmcblk

 

> That's all. Usb storage device new, because old one already reused.

I'm not sure about that. I don't know what is attached to the
cubieboard. But /dev/sdb1, labelled BLACK16G, is something I would
inspect closer.

> The installer worked ok. I have no routine to install debian using uart.
> Normal questions, answer. Ui was uncomfortable, but worked fine.
> Excluding the fact that no sdcard (or mmc) showed up.
> 
> Then, when i tried to boot: system booted from mmc (to debian installer or
> android if ejected).
> 
> Expected behavior, since no processing to cards was made.
> 
> > > System worked
> >
> > "System worked" as: The installer came alive and showed behaviour as
> > seen at other installs ???
>
> "System worked" mean that cb5 (with debian just installed) showed login prompt
>_(after additional steps (3 described)).
> 

Mmm, chips.  So a working Debian system,
but getting that far was NOT that easy as expected.


Regards
Geert Stappers

P.S.
Please keep the BTS, the Bug Tracking System, in the loop.
-- 
Silence is hard to parse

Bug#971606: installation-reports cubieboard 5

[Geert Stappers]

Control: tag -1 moreinfo

On Sat, Oct 03, 2020 at 12:17:51AM +0300, Валериан Пережигин wrote:
> Package: installation-reports
> 
> Boot method: hd-media/sd-card-images + usb (fat32) with
> 
> debian-cd debian-10.6.0-armhf-xfce-CD-1.iso.
> 
> I was using uart (pl2303).
> Image version: 
> https://mirror.yandex.ru/debian-cd/10.6.0/armhf/bt-cd/debian-10.6.0-armhf-xfce-CD-1.iso.torrent
> Date: 2020-10-01 20:12 MSK
> 
> Machine: cubietech cubietrick plus (cubieboard 5)
> Processor: soc A83t (2GHz ?)
> Memory: 2GiB (DDR3 at 672MHz)
> 
> Comments/Problems:
> 
> No sdcard demonstrated, only usb and sata.
> No dp or hdmi.
> Installation to sata (manually prepared dos partitioning, just select 
> filesystems) sucsessed.
> Installation of u-boot climed sucsess yet failed (system was not bootable).
> 
> By main pc:
> 1. copyed boot partition (from sata) to sdcard.
> 2. installed by dd u-boot (from u-boot-sunxi_2020.10~rc5+dfsg-1_armhf.deb) to 
> sdcard.

Acknowledge


> 3. insertied sdcard to cb5.
> 
> System worked.

"System worked" as:   The installer came alive and showed behaviour as
seen at other installs ???


> But no video, no network, no sdcard.
> Uart work fine.
> Usb came up after long delay (with some errors).
> 
> Kernel update yet again claim no errors, but bootloader is stil to be 
> installed.
> 
> I regret sdcard not showed up.

Please rerun the installer, find a shell,  do  `lsblk`
and pretty please report back.



Regards
Geert Stappers
-- 
Silence is hard to parse