[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#692196: marked as done (Debian installer 7.0 beta 3 on sparc Ultra 2 fails)

Your message dated Thu, 29 Aug 2013 23:28:11 +0200
with message-id <201308292328.29265.holger@layer-acht.org>
and subject line dealing with old installation-reports
has caused the Debian Bug report #692196,
regarding Debian installer 7.0 beta 3 on sparc Ultra 2 fails
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

692196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692196
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---

Package: installation-reports

Boot method: boot cdrom with net install version of ISO for installer 7, beta 3, sparc
Image version: http://cdimage.debian.org/cdimage/wheezy_di_beta3/sparc/iso-cd/debian-wheezy-DI-b3-sparc-netinst.iso
Date: Nov 2, 2012

Machine: Sun Ultra 2 Processor: 2 x 400 Mhz
Memory: 1 GB
Partitions: 2 internal SCSI disks, left 10 MB free at disk start.  RAID 1 partitions for
 /boot 90 MB
 /     30 GB
 /tmp   2 GB
 non-RAID swap partition with remaining space on each disk.

Each file system was set as ext3.

Output of lspci -knn (or lspci -nn): non-working, cannot produce

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [E]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems: System hung during package installs for Desktop Environment, SSH services
and basic system package sets.  System hang was reproducible at same spot.
Watched VT screen of F4 and there was no kernel dump or error.
The system became unresponsive.  Pressing numlock or caps lock
had no effect on LED for same.  One first attempt, used apt repo at Dal.ca.  On second
attempt used apt repo at uwaterloo.ca Computer Science club.  No difference.

Sorry I don't have the final line of the package that was being downloaded
at the time the system stopped responding.  I can tell you it did download
perhaps 100 to 300 packages before it seized.  It gave no error.  It behaved
as if it was taking a long time to download or whatever, except
that when I checked after 30 minutes or so of no progress, I saw the keyboard
wasn't responding with the standard numlock/capslock LED test of system health.
Control-Alt F1, etc. were also attempted to see what another VT might show.
Finally, a Stop-A was done, which should cause the PROM to pop us out to a ok >
prompt, and it did nothing.

This failure was observed twice, once with the progress bar view,
and once with the details view from F4 virtual terminal.

System seemed healthy prior to install attempt - it had been running Solaris 10 with ZFS
mirrored RAID on same disks for a few years and no hardware problems.

--Donald Teed

--- End Message ---
--- Begin Message ---
reasign 691666 debian-installer
severity 691666 wishlist
merge 704768 691666
retitle 704768 please suport neo2, dvorak, french bépo, ..., keyboard layouts 
tags 704768 +wontfix
retitle 685801 Wheezy LXDE live system can't boot on Asus EeePC 1015BX netbook


thank you for submitting installation reports, much appreciated.

I read through all the bugs mentioned here (and I'm sure they were read by 
several people at the time they were submitted) and am closing them now as/if
- they (finally) indicated success and/or
- I know from first hand experience that the functionality is working in 
Wheezy and/or
- they only contained very little information and/or
- they contained user errors and/or
- they were caused by broken hardware and/or
- they have been from a development phase where things were not stable and/or
- they are quite old (and thus likely fixed today) and/or
- moreinfo was asked and not given.

If I've closed a bug incorrectly please do reply (it's easy to reopen and I'll 
do if requested) or just file a new one - thats often better, as the bug log 
will be clearer and shorter and not contain cruft.


Attachment: signature.asc
Description: This is a digitally signed message part.

--- End Message ---

Reply to: