Package: installation-reports
Version: 20040830/netinst
Debian-installer-version: 20040830/netinst
uname -a: Linux (none) 2.4.26-1-386 #2 Sat May 1 16:31:24 EST 2004 i686 unknown
Date: Mon, 30 Aug 2004 20:07:31 -0700
Method: CD, fb console
Machine: HP ProLiant dl360g3
Processor: dual socket Pentium4 3.2GHz
Memory: 2GB (only 1GB shows up with the install kernel?)
Root Device: Compaq SmartArray (cciss driver)
Root Size/partition table: used guided partitioning (see #4)
Output of lspci and lspci -n:
lspci
=======================================================================
0000:00:00.0 Host bridge: ServerWorks CMIC-LE Host Bridge (GC-LE chipset) (rev
3
3)
0000:00:00.1 Host bridge: ServerWorks CMIC-LE Host Bridge (GC-LE chipset)
0000:00:00.2 Host bridge: ServerWorks CMIC-LE Host Bridge (GC-LE chipset)
0000:00:03.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
0000:00:04.0 RAID bus controller: Compaq Computer Corporation Smart Array
5i/532
(rev 01)
0000:00:05.0 System peripheral: Compaq Computer Corporation Integrated Lights
Ou
t Controller (rev 01)
0000:00:05.2 System peripheral: Compaq Computer Corporation Integrated Lights
Ou
t Processor (rev 01)
0000:00:0f.0 ISA bridge: ServerWorks CSB5 South Bridge (rev 93)
0000:00:0f.1 IDE interface: ServerWorks CSB5 IDE Controller (rev 93)
0000:00:0f.2 USB Controller: ServerWorks OSB4/CSB5 OHCI USB Controller (rev
05)
0000:00:0f.3 Host bridge: ServerWorks CSB5 LPC bridge
0000:00:11.0 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05)
0000:00:11.2 Host bridge: ServerWorks CIOB-X2 PCI-X I/O Bridge (rev 05)
0000:01:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X
Gigabi
t Ethernet (rev 02)
0000:04:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X
Gigabi
t Ethernet (rev 02)
=======================================================================
lspci -n
=======================================================================
0000:00:00.0 0600: 1166:0014 (rev 33)
0000:00:00.1 0600: 1166:0014
0000:00:00.2 0600: 1166:0014
0000:00:03.0 0300: 1002:4752 (rev 27)
0000:00:04.0 0104: 0e11:b178 (rev 01)
0000:00:05.0 0880: 0e11:b203 (rev 01)
0000:00:05.2 0880: 0e11:b204 (rev 01)
0000:00:0f.0 0601: 1166:0201 (rev 93)
0000:00:0f.1 0101: 1166:0212 (rev 93)
0000:00:0f.2 0c03: 1166:0220 (rev 05)
0000:00:0f.3 0600: 1166:0225
0000:00:11.0 0600: 1166:0101 (rev 05)
0000:00:11.2 0600: 1166:0101 (rev 05)
0000:01:02.0 0200: 14e4:16a7 (rev 02)
0000:04:02.0 0200: 14e4:16a7 (rev 02)
=======================================================================
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [O] see #0
Configure network HW: [O] see #1
Config network: [E] see #2
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O] see #3
Partition hard drives: [O] see #4
Create file systems: [O]
Mount partitions: [O]
Install base system: [E] see #5
Install boot loader: [ ]
Reboot: [ ]
Comments/Problems:
0.) HP ProLiant systems have a remote management device called an "intergrated
Lights Out" ("iLO"). This device intercepts the system's vga text and keyboard
and makes it available via telnet. As long as the system stays in vga text
mode it works great but if you try to use framebuffer it tells you "the system
is in graphics mode". So I am able to start the installer with
"debian-installer/framebuffer=false" and that works fine. The problem is that
the initial bootloader uses a framebuffer splash screen. If you know to hit F1
at that point then you get the text back and boot without framebuffer. Is
there going to be be boot media for i386 that doesn't use the spash screen?
1.) The installer correctly determined that the system has two "BROADCOM
Corporation NetXtreme BCM5703X Gigabit Ethernet", and I can pick one, but...
2.) The installer complains that "eth0 does not seem to be connected to any
sort of network." even though a working network cable is connected (I know
this because it worked with the previous woody install). Looking on the dhcp
server I don't see a dhcp request. I'm given the options "Go Back", "Yes", and
"No". The option "Go Back" doesn't and proceeded to ask me for the hostname.
"Yes" allows me to configure statically and that works fine. If I configure
statically when I get to the hostname/domain config screens the hostname and
domain are pre-inserted so I know the networking is working and it was able to
do a lookup.
3.) This system uses a Compaq SmartArray controller which uses the cciss
driver and weird /dev names. It found the single controller and worked great!
So good job on that. I will try to test with multiple configured arrays and
multiple controllers if I get a chance.
4.) I tried the guided partitioning thing and it looks like "single", "one
partition for /home", and "multiuser" all picked reasonable partition sizes.
If you know what you're doing this works fine but I predict that these screens
will be "scary" to people without Debian experience (like reviewers).
5.) During the base install, the installer complained "debootstrap exited with
an error (return value 1)" /var/log/messages says
=======================================================================
Errors were encountered while processing:
exim4-daemon-light
at
exim4
exim4-config
mailx
exim4-base
=======================================================================
looking in the logs it appears to be exim4-config with the problem,
=======================================================================
Setting up exim4-config (4.34-4) ...
hostname: Host name lookup failure
Adding system-user for exim (v4)
/usr/sbin/exim4: error while loading shared libraries: libgnutls.so.10: cannot
$
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp
not installing /var/lib/exim4/config.autogenerated.tmp to
/var/lib/exim4/config.autogenerated
dpkg: error processing exim4-config (--configure):
subprocess post-installation script returned error exit status 1
=======================================================================
(The "hostname: Host name lookup failure" shows up if I didn't configure the
network by hand when it failed in #2. If I do then it goes away. The rest is
the same regardless)
If I attempt to proceed with installing grub it tries to run the base install
again with the same result.
I used a shell to chroot into /target but the system is not yet self aware
dpkg-wise so I couldn't install anything.
Installation failed :)
--
Matt Taggart
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
