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

Bug#315224: marked as done (Debian Installer errors - Sun Blade 1000)



Your message dated Wed, 08 Sep 2010 03:58:00 +0000
with message-id <E1OtBnM-0004jh-Jr@ravel.debian.org>
and subject line Closing old installation report #315224
has caused the Debian Bug report #315224,
regarding Debian Installer errors - Sun Blade 1000
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.)


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

Debian-installer-version: June 21, 12:00 AEST -
http://http.us.debian.org/dists/sarge/main/installer-sparc/current//images/sparc64/netboot/2.6/boot.img
uname -a: not available
Date: June 21 12:30 AEST

Method: Installed using tftp from laptop. Did Stop-A, then "boot net".
        tftp server and rarp server setup on laptop, boot.img copied
        to tftp directory, symlinked boot.img to C0A80101 (hex of
        192.168.1.1). No proxy.

Machine: SUN SunBlade 1000
Processor: 900MHz UltraSparc-III
Memory: 2048Mb
Root Device: Root dev SCSI ( 2 x 73Gb FC drives)
Peripherals: USB Type 6 Mouse and Keyboard.
Root Size/partition table: See Below

Output of lspci and lspci -n:

beast # lspci
0000:00:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module
0000:00:05.0 Bridge: Sun Microsystems Computer Corp. RIO EBUS (rev 01)
0000:00:05.1 Ethernet controller: Sun Microsystems Computer Corp. RIO GEM (rev 0
1)
0000:00:05.2 FireWire (IEEE 1394): Sun Microsystems Computer Corp. RIO 1394 (rev
 01)
0000:00:05.3 USB Controller: Sun Microsystems Computer Corp. RIO USB (rev 01)
0000:00:06.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37)
0000:00:06.1 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 37)
0000:01:00.0 Host bridge: Sun Microsystems Computer Corp. Schizo PCI Bus Module
0000:01:04.0 SCSI storage controller: QLogic Corp. QLA2200 64-bit Fibre Channel
Adapter (rev 05)

beast # lspci -n
0000:00:00.0 Class 0600: 108e:8001
0000:00:05.0 Class 0680: 108e:1100 (rev 01)
0000:00:05.1 Class 0200: 108e:1101 (rev 01)
0000:00:05.2 Class 0c00: 108e:1102 (rev 01)
0000:00:05.3 Class 0c03: 108e:1103 (rev 01)
0000:00:06.0 Class 0100: 1000:000f (rev 37)
0000:00:06.1 Class 0100: 1000:000f (rev 37)
0000:01:00.0 Class 0600: 108e:8001
0000:01:04.0 Class 0100: 1077:2200 (rev 05)

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

Initial boot worked:    [O]
Configure network HW:   [O]
Config network:         [O]
Detect CD:              [ ]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [E]
Create file systems:    [O]
Mount partitions:       [O]
Install base system:    [O]
Install boot loader:    [O]
Reboot:                 [O]

Comments/Problems:

My appologies if this list is long and boring, but here's what
happened.

1. Booted OK from boot.img via "boot net"
2. Installer downloaded and started hardware detection - attempted to
install qlogicisp module - incorrect, as qlogicfc is needed.
3. manually did "modprobe -v qlogicfc" - short delay, module loaded.
4. detected both disks OK, used auto-partitioning as multi-user
workstation. Only partitioned a total of 18Gb of the drive. No free
space evident.
5. manually partitioned the second drive as /home, same space problem
(suspect incorrect drive geometery or LBA support)
6. Installed base system.
7. rebooted.
8. Get message "remapping the kernel", then "fast data access mmu
miss", then back to the "ok" prompt.




--- 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: