Your message dated Sat, 20 Jul 2013 01:07:31 +0200 with message-id <201307200107.51378.holger@layer-acht.org> and subject line dealing with old installation-reports has caused the Debian Bug report #588919, regarding Installation problem on DL 380 G3 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.) -- 588919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588919 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bugs <submit@bugs.debian.org>
- Subject: Installation problem on DL 380 G3
- From: Joey Schulze <joey@infodrom.org>
- Date: Tue, 13 Jul 2010 14:41:23 +0200
- Message-id: <20100713124123.GN31750@finlandia.home.infodrom.org>
Package: installation-reports Boot method: PXE network Image version: Installer build: 20100211+b1 Date: Tue Jul 13 13:03:01 CEST 2010 Machine: HP ProLiant DL 380 G3 Processor: Dualcore 2.8GHz intel Memory: 6GB Partitions: <df -Tl will do; the raw partition table is preferred> Filesystem Type 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p1 ext3 33514984 858100 30954400 3% / tmpfs tmpfs 1947392 0 1947392 0% /lib/init/rw udev tmpfs 10240 644 9596 7% /dev tmpfs tmpfs 1947392 0 1947392 0% /dev/shm Output of lnspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: Broadcom CMIC-LE Host Bridge (GC-LE chipset) [1166:0014] (rev 33) Kernel modules: sworks-agp 00:00.1 Host bridge [0600]: Broadcom CMIC-LE Host Bridge (GC-LE chipset) [1166:0014] Kernel modules: sworks-agp 00:00.2 Host bridge [0600]: Broadcom CMIC-LE Host Bridge (GC-LE chipset) [1166:0014] Kernel modules: sworks-agp 00:03.0 VGA compatible controller [0300]: ATI Technologies Inc Rage XL [1002:4752] (rev 27) 00:04.0 System peripheral [0880]: Compaq Computer Corporation Integrated Lights Out Controller [0e11:b203] (rev 01) Kernel modules: hpwdt 00:04.2 System peripheral [0880]: Compaq Computer Corporation Integrated Lights Out Processor [0e11:b204] (rev 01) Kernel driver in use: hpilo Kernel modules: hpilo 00:0f.0 ISA bridge [0601]: Broadcom CSB5 South Bridge [1166:0201] (rev 93) Kernel driver in use: piix4_smbus Kernel modules: i2c-piix4 00:0f.1 IDE interface [0101]: Broadcom CSB5 IDE Controller [1166:0212] (rev 93) Kernel driver in use: Serverworks_IDE Kernel modules: serverworks 00:0f.2 USB Controller [0c03]: Broadcom OSB4/CSB5 OHCI USB Controller [1166:0220] (rev 05) Kernel driver in use: ohci_hcd Kernel modules: ohci-hcd 00:0f.3 Host bridge [0600]: Broadcom CSB5 LPC bridge [1166:0225] Kernel modules: sworks-agp 00:10.0 Host bridge [0600]: Broadcom CIOB-X2 PCI-X I/O Bridge [1166:0101] (rev 05) Kernel modules: sworks-agp 00:10.2 Host bridge [0600]: Broadcom CIOB-X2 PCI-X I/O Bridge [1166:0101] (rev 05) Kernel modules: sworks-agp 00:11.0 Host bridge [0600]: Broadcom CIOB-X2 PCI-X I/O Bridge [1166:0101] (rev 05) Kernel modules: sworks-agp 00:11.2 Host bridge [0600]: Broadcom CIOB-X2 PCI-X I/O Bridge [1166:0101] (rev 05) Kernel modules: sworks-agp 01:03.0 RAID bus controller [0104]: Compaq Computer Corporation Smart Array 5i/532 [0e11:b178] (rev 01) Kernel driver in use: cciss Kernel modules: cciss 02:01.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet [14e4:16a7] (rev 02) Kernel driver in use: tg3 Kernel modules: tg3 02:02.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet [14e4:16a7] (rev 02) Kernel driver in use: tg3 Kernel modules: tg3 03:01.0 RAID bus controller [0104]: Compaq Computer Corporation Smart Array 64xx [0e11:0046] (rev 01) Kernel driver in use: cciss Kernel modules: cciss 06:1e.0 PCI Hot-plug controller [0804]: Compaq Computer Corporation PCI Hotplug Controller [0e11:a0f7] (rev 14) Kernel driver in use: compaq_pci_hotplug Kernel modules: cpqphp Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card: [O] (required tigon/tg3_tso.bin, provided via USB stick, worked fine) Configure network: [O] Detect CD: [O] (n/a) Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [ ] Install base system: [ ] Clock/timezone setup: [ ] User/password setup: [ ] Install tasks: [ ] Install boot loader: [ ] Overall install: [ ] Comments/Problems: I have no ide what caused the problem. This machine uses a HP SmartArray 641 array which used the CCISS driver. The module was loaded and both logical volumes /dev/cciss/c0d0 and /dev/cciss/c1d0 have been found. However, the installer told me that no drives were found. After this failed, I switched to the lenny installer and it was able to detect the disk and install Debian on them. Unfortunately, the system went in production use already so I cannot retry a future installer version. Regards, Joey -- Never trust an operating system you don't have source for!
--- End Message ---
--- Begin Message ---
- To: 590190-done@bugs.debian.org, 590170-done@bugs.debian.org, 588919-done@bugs.debian.org, 588642-done@bugs.debian.org, 588640-done@bugs.debian.org, 587381-done@bugs.debian.org, 586854-done@bugs.debian.org, 585901-done@bugs.debian.org, 585835-done@bugs.debian.org, 579088-done@bugs.debian.org, 578315-done@bugs.debian.org
- Subject: dealing with old installation-reports
- From: Holger Levsen <holger@layer-acht.org>
- Date: Sat, 20 Jul 2013 01:07:31 +0200
- Message-id: <201307200107.51378.holger@layer-acht.org>
Hi, 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 have been from a development phase where things were not stable and/or - they are very old, more than 2.5 years. 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. cheers, HolgerAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---