Re: failure trying to install bullseye on Cubox-i

[Rick Thomas]

On Sun, Jul 17, 2022, at 6:37 PM, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep
> around for testing purposes.
>
> I followed the instructions at:
>
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images
>
> Then I dd'ed the resulting complete image onto an 8GB microSD card,
> which I then inserted into the microSD slot in the Cubox-I. When I
> applied power, I got the attached log on the serial console.
>
> Does anyone know what I'm doing wrong? Is this a bug in the installer?
> If so, what's the best way for me to volunteer to help as a tester in
> debugging it.
>
> Rick
> Attachments:
> * screenlog

In case it helps, the two components I used in this experiment are:

http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/20210731+deb11u4/images/netboot/SD-card-images/firmware.MX6_Cubox-i.img.gz

and

http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/20210731+deb11u4/images/netboot/SD-card-images/partition.img.gz

On the web page, these files are dated 2022-07-05 15:57 .

Any clues are appreciated!
Rick

[to...@tuxteam.de]

On Sun, Jul 17, 2022 at 06:37:55PM -0700, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for testing purposes.
>
> I followed the instructions at:
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images
>
> Then I dd'ed the resulting complete image onto an 8GB microSD card, which I then inserted into the microSD slot in the Cubox-I. When I applied power, I got the attached log on the serial console.

Disclaimer: I have no idea what a Cubox-i4Pro is, so take the
following with one or two fists of salt.

Going through the attached log, this calls my attention:

> MMC: FSL_SDHC: 1, FSL_SDHC: 2^M
> Loading Environment from MMC... *** Warning - bad CRC, using default environment^M

which seems to mean that the bootloader isn't finding what it
expects. This could be due to a bad MMC card, or to something
going wrong with the dd, or to the Cubox needing something
different than what you have got. Unless you are quite sure
about the third, I'd try to eliminate the first two ones.

Typically such an installer is a partitioned disk: if you insert
the card into your Linux box: can you see the partitions? Can
you mount them?

Then this:

> mmc1 is current device^M
> Card did not respond to voltage select! : -110^M
> CACHE: Misaligned operation at range [e59ff01c, e59ff91c]^M
> timeout exit!^M
> CACHE: Misaligned operation at range [e59ff01c, e59ff91c]^M
> timeout exit!^M

Are you sure your MMC card is working as it should? They are known
to be of... varying quality.

Cheers
--
t

[Vagrant Cascadian]

On 2022-07-17, Rick Thomas wrote:
> I'm experimenting with installing Bullseye on a Cubox-i4Pro I keep around for testing purposes.
>
> I followed the instructions at:
> http://http.us.debian.org/debian/dists/bullseye/main/installer-armhf/current/images/netboot/SD-card-images/README.concatenateable_images


> Then I dd'ed the resulting complete image onto an 8GB microSD card,
> which I then inserted into the microSD slot in the Cubox-I. When I
> applied power, I got the attached log on the serial console.

Those sound like reasonable steps...

What's confusing is your screen logs shows a u-boot from bookworm/sid:

U-Boot SPL 2022.04+dfsg-2+b1 (May 14 2022 - 21:25:25 +0000)

So either the images you downloaded were not the images you thought you
downloaded... or you saved the wrong screenlog file... or the bullseye
images contain u-boot from the wrong release... or somehow you're
loading u-boot from some other media, such as eMMC?

I actually need to reinstall a cuboxi4pro maybe by the end of the week,
so I will test it myself then.


live well,
vagrant