Your message dated Wed, 5 Aug 2020 00:07:32 +0200
with message-id <20200805000732.bcd14bc42a1f57a24212c...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs --- round 2
has caused the Debian Bug report #766815,
regarding installation-reports: please omit "quiet" option
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
766815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766815
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
When booting the amd64 installer on a machine with a 32bit CPU, you get
so far as to the menu from which you can select the install options.
When you select "install", you're being left with a blue screen and a few
lines with colourful pixels on top of the screen, and nothing further
happens.
The xSeries 345 isn't the only machine this happens with. Perhaps the
problem is specific to old ATI cards like the mach64.
* What outcome did you expect instead?
There should be the message displayed that you need to use a
32bit version of the installer for a 32bit machine. (I didn't
know it was a 32bit machine and started to think that either
the install media is damaged, the hardware is broken or that
there's some issue with the graphics card ... Displaying the
32bit message right away would have saved quite some trouble and
time.)
The message is displayed correctly when you edit the kernel command
line before booting and remove the "quiet" option.
I strongly recommend to change the installer to *not* use the quiet
option. Especially with the installer, there is much point in being
able to see all messages, and not everyone installs Debian on up-to-date
and/or fully known hardware.
Besides, the "quiet" option shouldn't be used by default after the
installation has completed, either. If someone wants to suppress the
messages, they can always add this option later. I have resorted to
remove this option as part of the installation process and am getting
much better results simply because I can see what's going on.
*** End of the template - remove these lines ***
-- Package-specific info:
Boot method: cd,usb
Image version: current stable, 7.6, 7.7, netinst iso
Date: a couple days ago
Machine: IBM xSeries 345
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [E]
see above
--- End Message ---
--- Begin Message ---
Holger Wansing <hwans...@mailbox.org> wrote:
>
> I'm closing the reports below.
>
> That's installation-reports for Debian 7 with
> - undefined errors
> - problems which are likely to have been fixed in the meantime
> - successful installation
>
> Because of the age, there is no chance to analyse them further and therefore
> they are no longer relevant or of any use for current releases:
round 2:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759029
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759177
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760062
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760420
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760712
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761588
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762287
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762401
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762590
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763008
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764001
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764505
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764587
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764683
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765402
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764995
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765555
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765628
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766400
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766423
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766523
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766815
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767052
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767222
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767465
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767474
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768464
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768624
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768628
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769749
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769916
--
Holger Wansing <hwans...@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
