Bug#342285: marked as done (Debian Installer Sparc)
Your message dated Wed, 08 Sep 2010 03:58:08 +0000
with message-id <E1OtBnU-0004z8-2F@ravel.debian.org>
and subject line Closing old installation report #342285
has caused the Debian Bug report #342285,
regarding Debian Installer Sparc
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 owner@bugs.debian.org
immediately.)
--
342285: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=342285
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Debian Installer Sparc
- From: Casper van der Bilt <bilca68@yahoo.com>
- Date: Tue, 6 Dec 2005 12:52:46 -0800 (PST)
- Message-id: <20051206205246.23327.qmail@web30911.mail.mud.yahoo.com>
Package: Debian installer Sparc r3.1 sarge (Net install boot cd's), kernel 2.4.x
System: Sun Ultra 10, different speeds, mem 256or 512, 9.5 Gb hd, frame buffer,
Solaris 9 installed on hd
Issue: Boot cd hangs during boot process
Work around: format the hd on an other machine / os than Sol 9 or Debian Sparc.
I used a Debian cd & i386 machine for the job.
It seems that the installer hang when writing to the Solaris 9 swap at the beginning of the partition table. It tries to write something and stops reporting to press L1-A to start again....
The bug is reproducable on the systems I have available. Frame buffer, mem size, CD image ed did not matter.
(2.6 kernel with sarge R3.1 CD image hangs with MMU problem but that is a other bug)
BR, Casper
Yahoo! Personals
Let fate take it's course directly to your email.
See who's waiting for you Yahoo! Personals
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---
Reply to: