On 08.04.23 01:15, Cyril Brulebois wrote:
Adjusting title since I suppose you spotted #1031643 and forgot to
change the title when filing this bug about something else.
Should have been "interface=auto", not "hostname=auto" in the subject.
Thanks for improving it.
Possible workarounds:
-
Processing control commands:
> retitle -1 Wireless interfaces trigger error messages about invalid WPA
> passphrases
Bug #1034072 [installation-reports] installation-reports: Preseed with
hostname=auto gets stuck during install
Changed Bug title to 'Wireless interfaces trigger err
Control: retitle -1 Wireless interfaces trigger error messages about invalid
WPA passphrases
Adjusting title since I suppose you spotted #1031643 and forgot to
change the title when filing this bug about something else.
Reto Schneider (2023-04-08):
> Until in Bullseye and Bookworm Alph
Your message dated Fri, 21 Aug 2020 04:58:02 +0200
with message-id <20200821045802.07acb7c9ded347064600d...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs --- round 5
has caused the Debian Bug report #874314,
regarding Boot fail after install - lots of console
Your message dated Fri, 03 Apr 2020 04:48:27 +
with message-id
and subject line Bug#955507: Removed package(s) from unstable
has caused the Debian Bug report #451121,
regarding lilo-installer: doesn't show descriptive error messages
to be marked as done.
This means that you claim tha
Package: installation-reports
Boot method: USB network install
Image version: Date: debian-9.1.0-amd64-netinst.iso
Machine: Acer Predator
https://www.newegg.com/Product/Product.aspx?Item=N82E16883101469
Processor: Intel Core i7
Memory: 32gb
Partitions: Single partition on 1tb drive
Output of
On Fri, Feb 06, 2015 at 06:53:30AM +0100, Christian PERRIER wrote:
>Quoting Phillip Susi (ps...@ubuntu.com):
>>
>> Recently a new message was added to d-i:
>>
>> This machine's firmware has started the installer in UEFI mode but
>> it looks like there may be existing operating systems already
>
Quoting Phillip Susi (ps...@ubuntu.com):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Package: partman-efi
> Version: 59
>
> Recently a new message was added to d-i:
>
> This machine's firmware has started the installer in UEFI mode but
> it looks like there may be existing operating
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: partman-efi
Version: 59
Recently a new message was added to d-i:
This machine's firmware has started the installer in UEFI mode but
it looks like there may be existing operating systems already
installed using "BIOS compatibility mode". I
severity 663638 wishlist
thanks
On Tue, Mar 13, 2012 at 02:26:46AM +0530, shirish शिरीष wrote:
>Package: debian-cd
>Severity: normal
>
>Dear Maintainer,
>Going to http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-dvd/
>we do not get any idea something is wrong apart from the date. Going
Your message dated Thu, 21 Oct 2010 14:48:21 +
with message-id
and subject line Bug#591436: fixed in busybox 1:1.17.1-5
has caused the Debian Bug report #591436,
regarding busybox-syslogd: initscript prints many error messages
to be marked as done.
This means that you claim that the problem
Package: busybox-syslogd
Version: 1:1.15.3-1
Severity: normal
The busybox-syslogd and -klogd initscripts generate lots of error messages like
this:
cut: /proc/447/stat: No such file or directory
cut: /proc/452/stat: No such file or directory
cut: /proc/453/stat: No such file or
Package: lilo-installer
Version: 1.25
I was trying to install lilo using current testing installer. I made a raid0
from my disks, and when I was trying to put lilo here Debian installer showed
my error message sth. like this: Running lilo failed - error number "1". It
hard to guess what it means.
Package: partman-partitioning
Severity: wishlist
Tags: d-i
Currently the failure messages when partition resizing fails are quite
unhelpful ("unknown error"). It would be good if we could improve these
messages.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". T
Your message dated Mon, 06 Sep 2004 21:02:02 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#269804: fixed in base-installer 1.05
has caused the attached Bug report 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 no
On Thu, May 20, 2004 at 12:48:37AM -0500, Joe Hester wrote:
> Numerous error messages at boot:
> JEDEC: Found no ICH2 rom device at location zero
>
> Stopped the error messages by adding a line to
> /etc/discover-modprobe.conf
>
> skip ="ich2rom"
The only PCI ID t
coding: 7bit
From: Andrew Pollock <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: discover: sprays lots of daunting error messages during boot
X-Mailer: reportbug 2.37
Date: Sat, 06 Mar 2004 18:48:28 +1100
Message-Id: <[EMAIL PROTECTED]>
Sender: Andr
Numerous error messages at boot:
JEDEC: Found no ICH2 rom device at location zero
Stopped the error messages by adding a line to
/etc/discover-modprobe.conf
skip ="ich2rom"
lspci:
:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM
Controller/Host-Hub Interface (re
On Thu, Mar 11, 2004 at 03:09:42AM -0500, David Nusinow wrote:
> On Sun, Mar 07, 2004 at 07:43:01AM +1000, Andrew Pollock wrote:
> >
> > i810_rng's for the random number generator isn't it? Would I need to load
> > anything at all?
>
> I don't know. From the rest of discover-data, every single PC
On Sun, Mar 07, 2004 at 07:43:01AM +1000, Andrew Pollock wrote:
> On Sat, Mar 06, 2004 at 02:03:24PM -0500, David Nusinow wrote:
> > Hi Andrew,
> >Could you please send me the output of lspci and lspci -n? If you
> > also know, or could find the correct module that should be loaded in
> > place
David Nusinow wrote:
> Hi Andrew,
>Could you please send me the output of lspci and lspci -n? If you
> also know, or could find the correct module that should be loaded in
> place of i810_rng I need that as well to fix this. Thank you!
>
> - David Nusinow
>
>
> --
> To UNSUBSCRIBE, email
David Nusinow wrote:
> Hi Andrew,
>Could you please send me the output of lspci and lspci -n? If you
> also know, or could find the correct module that should be loaded in
> place of i810_rng I need that as well to fix this. Thank you!
>
> - David Nusinow
>
>
> --
> To UNSUBSCRIBE, email
On Sat, Mar 06, 2004 at 02:03:24PM -0500, David Nusinow wrote:
> Hi Andrew,
>Could you please send me the output of lspci and lspci -n? If you
> also know, or could find the correct module that should be loaded in
> place of i810_rng I need that as well to fix this. Thank you!
Howdy,
[EMAIL P
Hi Andrew,
Could you please send me the output of lspci and lspci -n? If you
also know, or could find the correct module that should be loaded in
place of i810_rng I need that as well to fix this. Thank you!
- David Nusinow
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "un
Processing commands for [EMAIL PROTECTED]:
> reassign 236423 discover-data
Bug#236423: discover: sprays lots of daunting error messages during boot
Bug reassigned from package `discover' to `discover-data'.
> quit
Stopping processing here.
Please contact me if you need assista
reassign 236423 discover-data
quit
On Sat, Mar 06, 2004 at 06:48:28PM +1100, Andrew Pollock wrote:
> This is the output from running discover:
>
> Detecting hardware: agpgart eepro100 es1370 i810_rng ich2rom ide-scsi
> usb-uhci
> Loading agpgart module.
> Loading eepro100 module.
> Loading es1370
Package: discover
Version: 1.5-1.4.3
Severity: normal
Hi,
I'm doing test installs of d-i, and one of the points of feedback I had
was that on my system, when discover ran during the boot of the newly
installed system, it sprayed a lot of daunting looking error messages.
For me, this is o
Your message dated Wed, 25 Feb 2004 13:57:55 -0500
with message-id <[EMAIL PROTECTED]>
and subject line fixed
has caused the attached Bug report 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
On Thu, 2002-04-11 at 18:48, Eduard Bloch wrote:
> severity 142359 minor
> tags 142359 + unreproducible
> thanks
>
> #include
> Oliver Elphick wrote on Thu Apr 11, 2002 um 02:40:28PM:
>
> > On an old 486, many messages like this were seen while booting the
> > default installation root.bin:
> >
> This is an old problem. The kernel tries to load a module while
Err, of course. I misread the beginning of the report.
> booting. Since the kernel and modules aren't installed, it
> fails, spamming the console as it retries. On new machines,
> dbootstrap hides these messages before most use
Processing commands for [EMAIL PROTECTED]:
> tag 142359 -unreproducible
Unknown tag/s: -unreproducible.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help
security upstream pending.
Bug#142359: boot-floppies: Error messages from modprobe during boot
Tags ad
tag 142359 -unreproducible
thanks
On Thu, Apr 11, 2002 at 07:48:25PM +0200, Eduard Bloch wrote:
> #include
> Oliver Elphick wrote on Thu Apr 11, 2002 um 02:40:28PM:
>
> > On an old 486, many messages like this were seen while booting the
> > default installation root.bin:
> >
> > modprobe: m
Processing commands for [EMAIL PROTECTED]:
> severity 142359 minor
Bug#142359: boot-floppies: Error messages from modprobe during boot
Severity set to `minor'.
> tags 142359 + unreproducible
Bug#142359: boot-floppies: Error messages from modprobe during boot
Tags added: unreproducibl
severity 142359 minor
tags 142359 + unreproducible
thanks
#include
Oliver Elphick wrote on Thu Apr 11, 2002 um 02:40:28PM:
> On an old 486, many messages like this were seen while booting the
> default installation root.bin:
>
> modprobe: modprobe: Can't open dependencies file /lib/modules/2
Package: boot-floppies
Version: N/A; reported 2002-04-11
Severity: normal
On an old 486, many messages like this were seen while booting the
default installation root.bin:
modprobe: modprobe: Can't open dependencies file /lib/modules/2.2.20/modules.dep
On a newer machine they go past so fast
On Sun, Jan 27, 2002 at 09:26:25PM +, Philip Blundell wrote:
> On Sun, 2002-01-27 at 20:52, I. Middlemas wrote:
> > Here is what the partition table indicates:
> > /dev/hda1 /target/bootLinux native5.12 MB
> > /dev/hda2 swapLinux swap 5.12 M
On Sun, 2002-01-27 at 20:52, I. Middlemas wrote:
> Here is what the partition table indicates:
> /dev/hda1 /target/bootLinux native5.12 MB
> /dev/hda2 swapLinux swap 5.12 MB
> /dev/hda3 /target Linux native5.12 MB
> /de
Hi,
I'm attempting to install Debian to an NEC UltraLite VERSA laptop
(12 MB Ram, 180 MB Drive) using 1.44 MB floppy disks. The laptop
doesn't have a CD ROM.
Here is what the partition table indicates:
/dev/hda1 /target/bootLinux
native5.12
MB
/dev/hda2 swap
38 matches
Mail list logo
