Your message dated Thu, 6 Aug 2020 09:48:07 +0200
with message-id <20200806094807.1966cbbb91ce0f9e1b2db...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs --- round 3
has caused the Debian Bug report #798885,
regarding Boot problems after installation on ne
My original post to this bug report may have confused the issue I had
with the main kernel to the issue I had with the backports kernel. When
I came back to the system at a later date the monitor was turning off
when booting with a the jessie kernel while the storage problem was
happening with
On 13/09/15 21:02, Peter Michael Green wrote:
Unfortunately on reboot the system hung, attempting to boot with quiet removed
from the kernel
command line showd the last userland boot message as "Starting LSB: Prepare
console". Trying to
boot in recovery mode also hung showing ata related messag
Package: installation-reports
Severity: normal
-- Package-specific info:
Boot method: CD
Image version: Debian 8.1.0 Jessie amd64 CD1 20150606-14:19
Date:
Machine: Self-built desktop based on haswell i5
I'm filing this report from rescue mode, i'll file a followup mail with more
hardware det
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
please see attached draft installation-report.txt.gz
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlFqakgACgkQ5+rBHyUt5wtBlACgkI1+QwmjLAFtGlDC3qlpQckY
gt4AoI7h+91cMcsJldP0xNcTAQDZrAS2
=Cs5A
-END PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This issue was tested with the latest 3.8-rc-series Ubuntu-kernel and reported
formally
here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1107909
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlEOk4wACgkQ5+rBHy
Your message dated Wed, 11 Nov 2009 22:32:45 +
with message-id
and subject line Bug#548354: fixed in console-setup 1.46
has caused the Debian Bug report #548354,
regarding console-setup: Intermittent boot problems
to be marked as done.
This means that you claim that the problem has been
Quoting Dr A. J. Trickett (adam.trick...@iredale.net):
> > Could you comment the following lines in /etc/init.d/console-setup:
> >
> > if setupcon; then
> > log_action_end_msg 0
> > else
> > log_action_end_msg $?
> >
Quoting Adam Trickett (a...@iredale.net):
> This may not be critical and it may not be the cause of the problem, but
> since I upgraded
> xorg, and console-setup was installed I'm having persisteng boot problems.
> Sometimes the
> boot sequence stops and a power cycle is re
Package: console-setup
Version: 1.45
Severity: critical
Justification: breaks the whole system
This may not be critical and it may not be the cause of the problem, but since
I upgraded
xorg, and console-setup was installed I'm having persisteng boot problems.
Sometimes the
boot sequence
Your message dated Thu, 30 Mar 2006 03:38:02 +0200
with message-id <[EMAIL PROTECTED]>
and subject line housekeeping
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 reo
First the good news:
No more kernel panic from booting the CD! Consider that problem
fixed, at least on my Blade 100 with the netinstall image from
http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/sparc/current/.
The bad news:
Now that I can successfully boot from the CDROM, I am encounterin
Colleen Hatfield wrote:
> Sure, I'll try to test either the netinstall or businesscard image
> from the URL below on my Blade 100 tonight:
> http://cdimage.debian.org/pub/cdimage-testing/sid_d-i/sparc/current/
>
> If that's not correct, or if it matters which one I test from, just
> let me know an
On Wed, 13 Oct 2004 21:43:43 -0400, Joey Hess <[EMAIL PROTECTED]> wrote:
> Your both reported some debian-installer sparc cd boot problems a while ago.
> Can you check the current daily build (the sid_d-i build) of the
> installer and see if this is still a problem?
Sure, I'l
Your both reported some debian-installer sparc cd boot problems a while ago.
Can you check the current daily build (the sid_d-i build) of the
installer and see if this is still a problem?
--
see shy jo
signature.asc
Description: Digital signature
Petter Reinholdtsen wrote:
[Peter Green]
or just default to lilo altogether
unless there is some other major advantage to grub ofc
There are major advantages with grub. It understand several file
systems (no need to update the boot block if the kernel or initrd is
updated), and it contains
[Peter Green]
> or just default to lilo altogether
> unless there is some other major advantage to grub ofc
There are major advantages with grub. It understand several file
systems (no need to update the boot block if the kernel or initrd is
updated), and it contains a simple editor (so one can f
or just default to lilo altogether
unless there is some other major advantage to grub ofc
> -Original Message-
> From: Goswin von Brederlow [mailto:[EMAIL PROTECTED]
> Sent: 04 August 2004 22:18
> To: [EMAIL PROTECTED]
> Subject: Boot problems with grub and 4GB+
>
Hi,
grub still has problems booting on high end systems (4GB ram or
more). With ram getting cheaper and more used by the minute this could
affect more and more Debian installations.
(see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=254798)
Given the timeframe for the release it doesn't look
Frans Pop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 July 2004 16:26, Joey Hess wrote:
I doubt that it's loading the whole initrd in either case. Pass
initrd_size=1 or so.
Hmmm. What tftp server are you using?
You will need a TFTP server with 'tsize' support. On a Deb
Joey Hess wrote:
John wrote:
These are the 2.4 files:
2450662 Jul 7 02:33 initrd.gz
1208 Jul 7 02:33 initrd.list
3686400 Jul 7 02:33 mini.iso
811877 Jul 7 02:33 vmlinuz
This produces numerous modprobe messages that it can't find
/lib/modules/2.4.26-1-386/modules.dep and then st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 July 2004 16:26, Joey Hess wrote:
>
> I doubt that it's loading the whole initrd in either case. Pass
> initrd_size=1 or so.
Hmmm. What tftp server are you using?
You will need a TFTP server with 'tsize' support. On a Debian GNU/Li
John wrote:
> These are the 2.4 files:
> 2450662 Jul 7 02:33 initrd.gz
>1208 Jul 7 02:33 initrd.list
> 3686400 Jul 7 02:33 mini.iso
> 811877 Jul 7 02:33 vmlinuz
>
> This produces numerous modprobe messages that it can't find
> /lib/modules/2.4.26-1-386/modules.dep and the
On Wed, Jul 07, 2004 at 08:18:18PM +0800, John wrote:
> I guess that improved things. Now it can't find
> /var/lib/cdebconf/{questions,templates}.dat and is saying so repeatedly.
Sounds like an out-of-date rootskel. Unfortunately you didn't say which
image you were using. We need the URL from whi
Frans Pop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 July 2004 10:49, John wrote:
I'm PXE-booting. Here's the stanza, the same in each case:
label 4
kernel images/sarge/vmlinuz
append initrd=images/sarge/net-initrd.gz vga=6
You may need to add 'devfs=mount
Frans Pop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 July 2004 10:49, John wrote:
I'm PXE-booting. Here's the stanza, the same in each case:
label 4
kernel images/sarge/vmlinuz
append initrd=images/sarge/net-initrd.gz vga=6
You may need to add 'devfs=mount
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 July 2004 10:49, John wrote:
> I'm PXE-booting. Here's the stanza, the same in each case:
> label 4
> kernel images/sarge/vmlinuz
> append initrd=images/sarge/net-initrd.gz vga=6
>
You may need to add 'devfs=mount root
These are the 2.4 files:
2450662 Jul 7 02:33 initrd.gz
1208 Jul 7 02:33 initrd.list
3686400 Jul 7 02:33 mini.iso
811877 Jul 7 02:33 vmlinuz
This produces numerous modprobe messages that it can't find
/lib/modules/2.4.26-1-386/modules.dep and then stops.
The corresponding 2
ons 2003-06-18 klockan 23.44 skrev HARDIN,PAUL D (HP-Corvallis,ex1):
> 5. I as for an install of basic system and get the following
> message:
>
> P:0 100 Downloading Release file
> I: Retrieving file:///cdrom/dists/Sarge/Release
> Segmentation Fault
> Base installer's postinst exited with s
On Wed, Jun 18, 2003 at 02:44:54PM -0700, HARDIN,PAUL D (HP-Corvallis,ex1) wrote:
> Hi,
>
> I am trying to get the SARGE release loaded on a machine with a new, wiped
> disk and having problems.
>
> The SARGE implementation is the ISO image set of 9 cds. With no DOS
> directory or OS loaded I am
Hi,
I am trying to get the SARGE release loaded on a machine with a new, wiped
disk and having problems.
The SARGE implementation is the ISO image set of 9 cds. With no DOS
directory or OS loaded I am using the text based installer.
Machine is an old Dell Optiplex GXa Pentium2 266 and has a disk
On Thu, Apr 03, 2003 at 04:19:38PM +0200, Geert Stappers wrote:
> This mailing list is about development the set of programs
> that does the installation ( hardware detect, disk partitioning,
> copying programs from install media to hard disk, create first user )
True, but since this is the go-to
In the BIOS setup, change MPS to 1.1 instead of 1.4.
Xavier
On Thu, 3 Apr 2003, kpn wrote:
> Hello Linux-Support,
>
> I have several problems to install Linux on my computer. I have tested
> the distributions
> Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any
> possibility of hard
On Thu, Apr 03, 2003 at 01:18:52PM +, kpn wrote:
> Hello Linux-Support,
Hello André,
>
> I have several problems to install Linux on my computer. I have tested
> the distributions
> Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any
> possibility of hardware
> configuration.
>
Il gio, 2003-04-03 alle 15:18, kpn ha scritto:
> Hello Linux-Support,
>
> I have several problems to install Linux on my computer. I have tested
> the distributions
> Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any
> possibility of hardware
> configuration.
> Following I discribe
Hello Linux-Support,
I have several problems to install Linux on my computer. I have tested
the distributions
Debian Woody, Suse 8.1 and Knoppix 3.1 on my computer using any
possibility of hardware
configuration.
Following I discribe all of my computer components:
motherboard:
ASUS CUV266-D DUAL
After trying to do a tft boot network install today and reading through
the bug report stuff, here is my summary and suggestion for a way
forward.
1. include root.bin in tftpboot.img using mknbi
2. Document booting with pxe and with etherboot
The tftpboot.img files are broken, they do not include
Package: boot-floppies
Version: woody May 16 2002
I'm trying to boot a Gateway system off the LAN in order to install
Debian. There server's running RHL 7.2.
The gateway declined to boot with its bootrom so I got on from
rom-o-matic and I'm booting the "rom" from floppy.
It boots the rom, get
OTECTED]>
Sent: Saturday, February 02, 2002 6:50 PM
Subject: Re: Boot problems on an old TM5000
> On Sat, 2002-02-02 at 20:09, Chris Tillman wrote:
> > On Sat, Feb 02, 2002 at 12:33:40PM -0300, Pablo F. Gimenez Turk wrote:
> > > I've got an old Texas Instruments TravelM
On Sat, 2002-02-02 at 20:09, Chris Tillman wrote:
> On Sat, Feb 02, 2002 at 12:33:40PM -0300, Pablo F. Gimenez Turk wrote:
> > I've got an old Texas Instruments TravelMate 5000 notebook with a Pentium 75Mhz
>PCI-Bus and 24Mb RAM, just for testing purposes, and whatever installation package I
>se
On Sat, Feb 02, 2002 at 12:33:40PM -0300, Pablo F. Gimenez Turk wrote:
> I've got an old Texas Instruments TravelMate 5000 notebook with a Pentium 75Mhz
>PCI-Bus and 24Mb RAM, just for testing purposes, and whatever installation package I
>select (base, compact, idepci) always get the same after
I've got an old Texas Instruments
TravelMate 5000 notebook with a Pentium 75Mhz PCI-Bus and 24Mb RAM,
just for testing purposes, and whatever installation package I select
(base, compact, idepci) always get the same after the root:
prompt:
PCI: Discovered primary peer bus
XX
(where XX a
Hi !
I have some problems . I have installed Win2000 and
Debian on a Dual boot system on my hd . But now iam
getting inaccessible_boot_device errors from Win2000
nearly every time i try to start it up . it doesnt
seem to be regularly but it happens quite often .
The change from lilo to Grub did
Hallo,
I faced the following problem when trying to
install Debian GNU/linux 3.0 betaon my machine:
the boot process stops after detecting
hda/hdb/hdc drives. After reaching thislevel the screen gets black and
nothing is going on any more.I don´t know what to do, how to get Linux
insta
Sorry my reply has take so long.
Scott Kersey <[EMAIL PROTECTED]> writes:
> I am trying to install Debian GNU/Linux 2.2r2 (3 disks) on a Dell laptop.
> I ran through the initial installation off the CD using the default
> options. After that, I am not able to boot off the rescue CD,
>
Hello:
I am trying to install Debian GNU/Linux 2.2r2 (3 disks) on a Dell laptop.
I ran through the initial installation off the CD using the default
options. After that, I am not able to boot off the rescue CD,
hard drive, or rescue floppy. Any help would be greatly appreciated!
H
[EMAIL PROTECTED] writes:
> I have gotten ahold of 3 Toshiba Satellite T1960CS/200 Laptop
> computers. I wanted to install Debian on it, but I have had
> problems with the boot disk. I have used the Potato Stable version,
> and have tried the Normal, Compact, and IDEPCI boot disk. The
> Normal
([EMAIL PROTECTED])
10/18/00 05:12 cc: [EMAIL PROTECTED]
PM ([EMAIL PROTECTED])
Please respond Subject: Toshiba Sate
"George M. Butler" <[EMAIL PROTECTED]> writes:
> Thought I would give you and update. Finally I had to reinstall
> Debian becuase when I tried to configure XWindows it would not
> activate the mouse and so I would find myself in XWindows and no way
> to bring up a terminal window.
If you have
Goswin Brederlow wrote:
> Adam Di Carlo <[EMAIL PROTECTED]> writes:
>
> > Pierre Burri <[EMAIL PROTECTED]> writes:
> >
> > > Where do I find if it as a vanilla or a compact CD? (Sorry I'm new to
> > > Debian...)
> > > In the README.txt I found:
> > > This CD-ROM is labeled
> > > Debian GNU/Linux
Adam Di Carlo <[EMAIL PROTECTED]> writes:
> Pierre Burri <[EMAIL PROTECTED]> writes:
>
> > Where do I find if it as a vanilla or a compact CD? (Sorry I'm new to
> > Debian...)
> > In the README.txt I found:
> > This CD-ROM is labeled
> > Debian GNU/Linux 2.2 r0 "Potato" - Official i386 Binary-1
That is what I finally found to answer your question:
md5sum.txt:c23db926844df47ad491c739e6c3a5fa
./dists/potato/main/binary-i386/base/kernel-image-2.2.17-compact_2.2.17pre6-1.deb
md5sum.txt:8e28299bb029c8397d68dfbbdc00269f
./dists/potato/main/binary-i386/base/pcmcia-modules-2.2.17-compact_3.1.8
Pierre Burri <[EMAIL PROTECTED]> writes:
> Where do I find if it as a vanilla or a compact CD? (Sorry I'm new to
> Debian...)
> In the README.txt I found:
> This CD-ROM is labeled
> Debian GNU/Linux 2.2 r0 "Potato" - Official i386 Binary-1
>
> and I have the 3 Binary CDs.
I belive compact is t
For your report to be helpful, you need to let us know whether you
were using 'vanilla' disks or 'compact' disks.
Even so, there's probably very little we can do about it -- its purely
a Linux kernel issue. If you really think there are steps we can take
(not sure what that would be), then file
"George M. Butler" <[EMAIL PROTECTED]> writes:
> I I did repartition my hard drive and found a DOS boot disk that let me access
> the CD ROM from a: . I booted and put in the Debian CD number 1 inr and
> then ran boot.bat from the Install directory. The Debian install seem to go
> norm
Hi
I have tried for the first time to install Debian GNU/Linux Potato
from the official CDs. The kernel hangs while trying to recognize an ISA
scsi card that comes with a scanner Mustek Paragon 1200-SP. I know
there is no driver under Linux for this kind of cards, not even Windows
recognizes
Sorry for the late reply.
[EMAIL PROTECTED] writes:
> Never the less after that I decided to go ahead and install Debian.
> First problem was that I could not boot my machine from the CD rom.
> I tried to fix that by getting a rescue floppy and root floppy from the
> Debian CD. The install se
Randy Gordner <[EMAIL PROTECTED]> writes:
> After hitting enter the install kernel start to load, when it starts to
> probe for scsi controllers it throws up all over my QLogic ISP1020 card.
> The messages go by so fast I can't begin to tell you what they say.
> The screen is filled with all kin
To whom it may concern,
I am unable to install from the Debian 2.2 CD.
I can boot the CD to the "boot:" prompt.
After hitting enter the install kernel start to load, when it starts to
probe for scsi controllers it throws up all over my QLogic ISP1020 card.
The messages go by so fast I can't be
Hi,
I hope that I've got the right list.
I'm trying to install potato from CD and I keep
running into the same problem. Booting from CD1 or CD2 I get to a point and the
installation hangs. The last lines I receive are:
NCR53c406a:no abailable ports
sym53c416c:version 1.00
I have tried a
Sorry I can't be of more help. Never heard of that problem. Perhaps
just skip the swap partition for now?
Sounds like a kernel issue if not a configuration issue. Is the disk
good? You know disk failures are 80% of hardware failures
--
.Adam Di [EMAIL PROTECTED]http://www.onShore.
I am tying to boot from two floopies, rescue.bin and boot.bin, that I
copied using the imaining software provided on it. I think I messed
up the step when I was asked to partition a hard disk. I had free
space of about 2+gigs and made the whole free space into the swap
file and then tried to
Adam Di Carlo <[EMAIL PROTECTED]> wrote:
>
>> >kmod: runaway modprobe loop assumed and stopped
> I've never seen that.
This is just the unix.o loop. It's a harmless warning. We used to use a
patch which didn't print out a warning, but now a new patch has been
integrated into the upstream k
Martin Schulze <[EMAIL PROTECTED]> writes:
> This is the proper list, I'm forwarding.
> > Are there any fixes (or even diagnoses) yet for the following problem?
> > Has anyone else even seen these symptoms?
> > Earlier I reported a problem with installing potato (from scratch)
> > and getting e
This is the proper list, I'm forwarding.
Daniel Barclay wrote:
>
> Are there any fixes (or even diagnoses) yet for the following problem?
> Has anyone else even seen these symptoms?
>
>
>
> Earlier I reported a problem with installing potato (from scratch)
> and getting errors at boot time li
Jim Ziegler <[EMAIL PROTECTED]> writes:
> We have several ICS systems here that I would like to run
> Debian on. Some of them work fine, but some will not
> get past the syslinux stage, they get to the point of
> printing "Loading..." and then reboot.
You think maybe it's a syslinux problem?
>
We have several ICS systems here that I would like to run
Debian on. Some of them work fine, but some will not
get past the syslinux stage, they get to the point of
printing "Loading..." and then reboot.
This behavior occurs with both the slink and the
potato boot disks, including the "safe" ver
67 matches
Mail list logo
