Devuan logs - #293, boring messages

Message sent to [email protected], [email protected]:

Subject: bug#293: Image for Raspberry Pi 2 will not boot
Reply-To: Paul Bryan Roberts <[email protected]>, [email protected]
Resent-From: Paul Bryan Roberts <[email protected]>
Resent-To: [email protected]
Resent-CC: [email protected]
Resent-Date: Thu, 14 Feb 2019 15:18:01 UTC
Resent-Message-ID: <[email protected]>
Resent-Sender: [email protected]
To: [email protected]
From: Paul Bryan Roberts <[email protected]>
Message-ID: <[email protected]>
Date: Thu, 14 Feb 2019 15:03:30 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.8.0
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="------------C6509FA0EB6695BD88BED45A"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------C6509FA0EB6695BD88BED45A
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Package: armhf_raspi2
Version: ascii_2.0.0


"You need to supply a correct |Package| line in the pseudo-header in 
order for the bug tracking system to deliver the message to the 
package's maintainer."

Can't get as far a dpkg -S

  * The /exact/ and /complete/ text of any error messages printed or
    logged. This is very important!

NO ERROR MESSAGES just a blank screen - the colour spectrum of the 
Raspberry PI boot rom is replaced by a blank screen, nothing logged on 
the screen, no log-in prompt.

  * Exactly what you typed or did to demonstrate the problem.

NOTHING TYPED - I inserted the microSD card, then the HDMI cable, then 
the power supply.

  * A description of the incorrect behaviour: exactly what behaviour you
    were expecting, and what you observed. A transcript of an example
    session is a good way of showing this.

I was expecting lots of logging to the console and finally a log-in 
prompt.  See Details below.

  * A suggested fix, or even a patch, if you have one.

Sadly I have none, else I probably would not be wasting your/our time.

  * Details of the configuration of the program with the problem.
    Include the complete text of its configuration files.

Um ... I am not sure what would be relevant here.  I looks to me like 
that the boot-rom does not recognise the micro-SD card.  It is just as 
if it were not there.

Include any detail that seems relevant - you are in very little danger 
of making your report too long by including too much information.

OK. *Details* ...

I have an RPi 2 and an RPi 3 and three microSD cards.

Card 1 has 2018-11-13-raspbian-stretch as a sanity check.  It will boot 
all the way through to X-11 in both the RPi 2 and RPi 3, as expected.  
Ergo nothing obviously wrong with the kit.

Card 2 has devuan_ascii_2.0.0_arm64_raspi3.img, which I have been using 
for several weeks in the RPi 3.  When in the RPi 2, there is some boot 
console output before the Linux kernel crashes and halts, as expected.

Card 3 is devuan_ascii_2.0.0_armhf_raspi2.img, which I expect to boot in 
the RPi 3 and well as in the RPi 2.  It does not boot in either.

I installed devuan_ascii_2.0.0_arm64_raspi3.img on Card 3 and, in the 
RPi 3, it boots through to the log-in prompt, as expected. Ergo nothing 
obviously wrong with the microSD card.

I downloaded devuan_ascii_2.0.0_armhf_raspi2.img again and verified the 
MD5SUM (f33aa344956f1a75dab54a51312ba9af) was the same as last time and 
copied the new image to the microSD card using the instructions in 
https://files.devuan.org/devuan_ascii/embedded/README.txt.

Still no joy but I infer there is/was nothing obviously wrong with my 
download plus copy to SD card methodology.

I tried the gpg notes in 
https://files.devuan.org/devuan_ascii/embedded/README.txt and I got:

pbr:devuan$ gpg --verify SHA256SUMS.asc && sha256sum -c SHA256SUMS
gpg: directory `/home/pbr/.gnupg' created
gpg: new configuration file `/home/pbr/.gnupg/gpg.conf' created
gpg: WARNING: options in `/home/pbr/.gnupg/gpg.conf' are not yet active 
during this run
gpg: keyring `/home/pbr/.gnupg/pubring.gpg' created
gpg: Signature made Wed 06 Jun 2018 12:25:01 BST using RSA key ID F78637DE
gpg: Can't check signature: public key not found

This suggests to me there is something 'intuitive' about this that 
wasn't common knowledge at the time I was born.  I cannot see how it is 
relevant.

I have inserted the 'not working image/card' into the running Raspbian 
image and both partition are mounted.  I have unmounted them and run 
fsck -f on each partition and neither is reported as corrupt.  I have 
had a quick peek in /var/log of the mounted image and there is nothing 
there more recent than 06 Jun 2018.

This is not the kind of thing I can work around or debug so, as 
recommended in 
https://files.devuan.org/devuan_ascii/embedded/README.txt, I am trying 
to raise a bug report but, sadly, without knowing either the package 
name or the maintainer's name.

Here's hoping your hair is having a better day than mine ...

    P-B Roberts



--------------C6509FA0EB6695BD88BED45A
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <pre>Package: armhf_raspi2
Version: ascii_2.0.0
</pre>
    <br>
    "You need to supply a correct <code>Package</code> line in the
    pseudo-header in order for the bug tracking system to deliver the
    message
    to the package's maintainer."<br>
    <br>
    Can't get as far a dpkg -S<br>
    <ul>
      <li>The <em>exact</em> and <em>complete</em> text of any error
        messages printed or logged. This is very important! </li>
    </ul>
    <p>NO ERROR MESSAGES just a blank screen - the colour spectrum of
      the Raspberry PI boot rom is replaced by a blank screen, nothing
      logged on the screen, no log-in prompt.<br>
    </p>
    <ul>
      <li>Exactly what you typed or did to demonstrate the problem.</li>
    </ul>
    <p>NOTHING TYPED - I inserted the microSD card, then the HDMI cable,
      then the power supply.<br>
    </p>
    <ul>
      <li>A description of the incorrect behaviour: exactly what
        behaviour you were expecting, and what you observed. A
        transcript of an example session is a good way of showing this.</li>
    </ul>
    <p>I was expecting lots of logging to the console and finally a
      log-in prompt.  See Details below.<br>
    </p>
    <ul>
      <li>A suggested fix, or even a patch, if you have one. </li>
    </ul>
    <p>Sadly I have none, else I probably would not be wasting your/our
      time.<br>
    </p>
    <ul>
      <li>Details of the configuration of the program with the problem.
        Include the complete text of its configuration files.
      </li>
    </ul>
    <p>Um ... I am not sure what would be relevant here.  I looks to me
      like that the boot-rom does not recognise the micro-SD card.  It
      is just as if it were not there.<br>
    </p>
    <p>Include any detail that seems relevant - you are in very little
      danger
      of making your report too long by including too much information.
      <br>
    </p>
    <p>OK. <b>Details</b> ...<br>
    </p>
    <p>I have an RPi 2 and an RPi 3 and three microSD cards.</p>
    <p>Card 1 has 2018-11-13-raspbian-stretch as a sanity check.  It
      will boot all the way through to X-11 in both the RPi 2 and RPi 3,
      as expected.  Ergo nothing obviously wrong with the kit.</p>
    <p>Card 2 has devuan_ascii_2.0.0_arm64_raspi3.img, which I have been
      using for several weeks in the RPi 3.  When in the RPi 2, there is
      some boot console output before the Linux kernel crashes and
      halts, as expected.</p>
    <p>Card 3 is devuan_ascii_2.0.0_armhf_raspi2.img, which I expect to
      boot in the RPi 3 and well as in the RPi 2.  It does not boot in
      either.<br>
    </p>
    <p>I installed devuan_ascii_2.0.0_arm64_raspi3.img on Card 3 and, in
      the RPi 3, it boots through to the log-in prompt, as expected. 
      Ergo nothing obviously wrong with the microSD card.</p>
    <p>I downloaded devuan_ascii_2.0.0_armhf_raspi2.img again and
      verified the MD5SUM (f33aa344956f1a75dab54a51312ba9af) was the
      same as last time and copied the new image to the microSD card
      using the instructions in
      <a class="moz-txt-link-freetext" href="https://files.devuan.org/devuan_ascii/embedded/README.txt">https://files.devuan.org/devuan_ascii/embedded/README.txt</a>.</p>
    <p>Still no joy but I infer there is/was nothing obviously wrong
      with my download plus copy to SD card methodology.</p>
    <p>I tried the gpg notes in
      <a class="moz-txt-link-freetext" href="https://files.devuan.org/devuan_ascii/embedded/README.txt">https://files.devuan.org/devuan_ascii/embedded/README.txt</a> and I
      got:<br>
    </p>
    <p>pbr:devuan$ gpg --verify SHA256SUMS.asc &amp;&amp; sha256sum -c
      SHA256SUMS<br>
      gpg: directory `/home/pbr/.gnupg' created<br>
      gpg: new configuration file `/home/pbr/.gnupg/gpg.conf' created<br>
      gpg: WARNING: options in `/home/pbr/.gnupg/gpg.conf' are not yet
      active during this run<br>
      gpg: keyring `/home/pbr/.gnupg/pubring.gpg' created<br>
      gpg: Signature made Wed 06 Jun 2018 12:25:01 BST using RSA key ID
      F78637DE<br>
      gpg: Can't check signature: public key not found<br>
      <br>
    </p>
    <p>This suggests to me there is something 'intuitive' about this
      that wasn't common knowledge at the time I was born.  I cannot see
      how it is relevant.</p>
    <p>I have inserted the 'not working image/card' into the running
      Raspbian image and both partition are mounted.  I have unmounted
      them and run fsck -f on each partition and neither is reported as
      corrupt.  I have had a quick peek in /var/log of the mounted image
      and there is nothing there more recent than 06 Jun 2018.</p>
    <p>This is not the kind of thing I can work around or debug so, as
      recommended in
      <a class="moz-txt-link-freetext" href="https://files.devuan.org/devuan_ascii/embedded/README.txt">https://files.devuan.org/devuan_ascii/embedded/README.txt</a>, I am
      trying to raise a bug report but, sadly, without knowing either
      the package name or the maintainer's name.</p>
    <p>Here's hoping your hair is having a better day than mine ...</p>
    <p>   P-B Roberts</p>
    <p><br>
    </p>
  </body>
</html>

--------------C6509FA0EB6695BD88BED45A--

Message sent:

X-Loop: [email protected]
From: [email protected] (Devuan bug Tracking System)
To: Paul Bryan Roberts <[email protected]>
Subject: bug#293: Acknowledgement (Image for Raspberry Pi 2 will not boot)
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]>
Precedence: bulk
X-Devuan-PR-Message: ack 293
X-Devuan-PR-Package: armhf_raspi2
X-Devuan-PR-Keywords: 
Reply-To: [email protected]

Thank you for the problem report you have sent regarding Devuan.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers mailing list for
their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 [email protected]

If you wish to submit further information on your problem, please send
it to [email protected] (and *not* to
[email protected]).

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Devuan Bugs Owner
(administrator, Devuan bugs database)

Message received at [email protected]:

Date: Sun, 26 Jan 2020 15:21:52 +0000
From: Mark Hindley <[email protected]>
To: [email protected]
Subject: Housekeeping reassignments from non-existent packages
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.23 (2014-03-12)

reassign 43 devuan-project
reassign 229 devuan-installer
reassign 87 arm-sdk
reassign 117 devuan-installer
reassign 235 arm-sdk
reassign 288 arm-sdk
reassign 293 arm-sdk
reassign 311 arm-sdk
reassign 335 arm-sdk
reassign 338 arm-sdk
thanks