Below is a capture from a serial console during the installation.
Note that I've reduced most of the repeated messages a la [last
message repeated x times]; otherwise, this would be a 7000 line post.
Aside: how about a 3-wire serial console option that doesn't need DCD
driven? My beloved Cisco serial cables don't drive DCD; I had to dig
deeply into my big bag o' adapters to find an old-school null modem to
do it. But I guess I'll appreciate that feature if I ever need a
serial console through a modem. :)
This should also answer a previously posted question on a related
failed ProLiant install: "Why axe(4)?" Because it seemed like a good
idea at the time to the kernel. It wasn't a user selection. All
hardware is HP-supplied with the system; nothing added here.
I first tried this with the PS/2 keyboard that came with the unit, but
it was unresponsive by the time I got to a prompt, hence the MS
Natural Pro plugged in.
If anyone cares, it looks like Ubuntu 6.06LTS will install on it (and
the PS/2 keyboard IS responsive under that OS.) I'll go ahead and
install that for the hell of it. If anyone wants dmesg from that, let
me know.
Either this will work soon, or it's going back; I can't afford to have
a science project sitting around. But if any developers want
something tried out, let me know and I'll assist as I can. I can also
hang it on a public IP if that helps.
OpenBSD/i386 BOOT 2.10
boot>
booting fd0a:/bsd: 4692244+739940=0x52e4c0
entry point at 0x200120*
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2006 OpenBSD. All rights reserved. http://www.OpenBSD.org
OpenBSD 4.0 (RAMDISK_CD) #39: Sat Sep 16 19:34:26 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/RAMDISK_CD
cpu0: Intel(R) Xeon(R) CPU 3040 @ 1.86GHz ("GenuineIntel" 686-class) 1.87 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CF
LUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX
16
real mem = 1071788032 (1046668K)
avail mem = 971149312 (948388K)
using 4256 buffers containing 53690368 bytes (52432K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(7b) BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xfd460,
SMB
IOS rev. 2.4 @ 0xdc010 (47 entries)
bios0: HP ProLiant ML110 G4
pcibios0 at bios0: rev 2.1 @ 0xfd460/0xba0
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdee0/256 (14 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371FB ISA" rev 0x00)
pcibios0: PCI bus #10 is the last bus
bios0: ROM list: 0xc0000/0x8000 0xdc000/0x4000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel E7230 MCH" rev 0xc0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01
pci1 at ppb0 bus 2
ppb1 at pci0 dev 28 function 4 "Intel 82801G PCIE" rev 0x01
pci2 at ppb1 bus 3
vga1 at pci2 dev 0 function 0 vendor "Matrox", unknown product 0x0522 rev
0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
ppb2 at pci0 dev 28 function 5 "Intel 82801G PCIE" rev 0x01
pci3 at ppb2 bus 4
bge0 at pci3 dev 0 function 0 "Broadcom BCM5721" rev 0x21, BCM5750 C1
(0x4201):
irq 12, address 00:18:fe:79:02:af
brgphy0 at bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: irq 10
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: irq 5
usb1 at uhci1: USB revision 1.0
uhub1 at usb1
uhub1: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: irq 11
usb2 at uhci2: USB revision 1.0
uhub2 at usb2
uhub2: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: irq 7
usb3 at uhci3: USB revision 1.0
uhub3 at usb3
uhub3: Intel UHCI root hub, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: irq 10
ehci0: timed out waiting for BIOS
usb4 at ehci0: USB revision 2.0
uhub4 at usb4
uhub4: Intel EHCI root hub, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
ppb3 at pci0 dev 30 function 0 "Intel 82801BA AGP" rev 0xe1
pci4 at ppb3 bus 10
ichpcib0 at pci0 dev 31 function 0 "Intel 82801GB LPC" rev 0x01: PM disabled
pciide0 at pci0 dev 31 function 1 "Intel 82801GB IDE" rev 0x01: DMA, channel 0
c
onfigured to compatibility, channel 1 configured to compatibility
atapiscsi0 at pciide0 channel 0 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: <HL-DT-ST, RW/DVD GCC-4482B, 2.02> SCSI0 5/cdrom
r
emovable
cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 disabled (no drives)
pciide1 at pci0 dev 31 function 2 "Intel 82801GB SATA" rev 0x01: DMA, channel
0
configured to native-PCI, channel 1 configured to native-PCI
pciide1: using irq 5 for native-PCI interrupt
wd0 at pciide1 channel 0 drive 0: <ST3808110AS>
wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide1:0:0): using PIO mode 4, Ultra-DMA mode 5
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom0: console
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
biomask efe5 netmask ffe5 ttymask ffe7
rd0: fixed, 3800 blocks
uhub5 at uhub1 port 2
uhub5: vendor 0x045e product 0x001c, rev 1.10/5.00, addr 2
uhub5: 3 ports with 2 removable, bus powered
axe0 at uhub3 port 1 configuration 1 interface 0
axe0: ServerEngines SE USB Device, rev 1.10/0.01, addr 2, AX88172, address
09:23
:20:d0:00:00
axe0: read PHY failed
axe0: read PHY failed
axe0: read PHY failed
ukphy0 at axe0 phy 0: Generic IEEE 802.3u media interface, rev. 15: OUI
0xffffff
ff, model 0x003f
axe0: write PHY failed
axe0: read PHY failed
[last message repeated 19 times]
uhidev0 at uhub5 port 1 configuration 1 interface 0
uhidev0: vendor 0x045e Microsoft Natural Keyboard Pro, rev 1.10/1.14, addr 3,
ic
lass 3/1
ukbd0 at uhidev0
axe0: read PHY failed
[last message repeated 8 times]
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub5 port 1 configuration 1 interface 1
uhidev1: vendor 0x045e Microsoft Natural Keyboard Pro, rev 1.10/1.14, addr 3,
ic
lass 3/0
axe0: read PHY failed
uhidev1: 2 report ids
uhid at uhidev1 reportid 1 not configured
uhid at uhidev1 reportid 2 not configured
axe0: read PHY failed
[last message repeated 19 times]
uhidev2 at uhub5 port 2 configuration 1 interface 0
uhidev2: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM), rev
1.10/3.00,
addr 4, iclass 3/1
axe0: read PHY failed
uhid at uhidev2 not configured
axe0: read PHY failed
[last message repeated 59 times]
ukphy1 at axe0 phy 1: Generic IEEE 802.3u media interface, rev. 15: OUI
0xffffff
ff, model 0x003f
axe0: write PHY failed
axe0: read PHY failed
[last message repeated 99 times]
axe0: write PHY failed
axe0: read PHY failed
[last message repeated 4 times]
ukphy2 at axe0 phy 2: Generic IEEE 802.3u media interface, rev. 15: OUI
0xffffff
ff, model 0x003f
axe0: write PHY failed
axe0: read PHY failed
[last message repeated 99 times]
axe0: write PHY failed
axe0: read PHY failed
[last message repeated 4 times]
[sequence repeats for ukphy3-30 at axe0 phy3-30]
ukphy31 at axe0 phy 31: Generic IEEE 802.3u media interface, rev. 15: OUI
0xffff
ffff, model 0x003f
axe0: write PHY failed
axe0: read PHY failed
[last message repeated 99 times]
axe0: write PHY failed
axe0: read PHY failed
axe0: read PHY failed
axe1 at uhub3 port 1 configuration 1 interface 0
axe1: ServerEngines SE USB Device, rev 1.10/0.01, addr 2, AX88172, address
09:23
:20:d0:00:00
axe1: read PHY failed
axe1: read PHY failed
axe1: read PHY failed
ukphy32 at axe1 phy 0: Generic IEEE 802.3u media interface, rev. 15: OUI
0xfffff
fff, model 0x003f
axe1: write PHY failed
[last message repeated 105 times]
ukphy33 at axe1 phy 1: Generic IEEE 802.3u media interface, rev. 15: OUI
0xfffff
fff, model 0x003f
axe1: write PHY failed
axe1: read PHY failed
[last message repeated 99 times]
axe1: write PHY failed
axe1: read PHY failed
[last message repeated 4 times]
ukphy34 at axe1 phy 2: Generic IEEE 802.3u media interface, rev. 15: OUI
0xfffff
fff, model 0x003f
axe1: write PHY failed
axe1: read PHY failed
[last message repeated 99 times]
axe1: write PHY failed
axe1: read PHY failed
[last message repeated 4 times]
[sequence repeats for ukphy35-62 at axe0 phy3-30]
ukphy63 at axe1 phy 31: Generic IEEE 802.3u media interface, rev. 15: OUI
0xffff
ffff, model 0x003f
axe1: write PHY failed
axe1: read PHY failed
[last message repeated 99 times]
axe1: write PHY failed
axe1: read PHY failed
axe1: read PHY failed
wd0: no disk label
dkcsum: wd0 matches BIOS drive 0x80
root on rd0a
rootdev=0x1100 rrootdev=0x2f00 rawdev=0x2f02
erase ^?, werase ^W, kill ^U, intr ^C, status ^T
(I)nstall, (U)pgrade or (S)hell? i
axe0: read PHY failed
axe0: read PHY failed
axe0: read PHY failed
axe0: media change failed
axe0: read PHY failed
axe0: read PHY failed
axe0: read PHY failed
axe1: read PHY failed
axe1: read PHY failed
axe1: read PHY failed
axe1: media change failed
axe1: read PHY failed
axe1: read PHY failed
axe1: read PHY failed
Welcome to the OpenBSD/i386 4.0 install program.
This program will help you install OpenBSD in a simple and rational way. At
any prompt except password prompts you can run a shell command by typing
'!foo', or escape to a shell by typing '!'. Default answers are shown in []'s
and are selected by pressing RETURN. At any time you can exit this program by
pressing Control-C and then RETURN, but quitting during an install can leave
your system in an inconsistent state.
Terminal type? [vt220]
kbd(8) mapping? ('L' for list) [none]
IS YOUR DATA BACKED UP? As with anything that modifies disk contents, this
program can cause SIGNIFICANT data loss.
It is often helpful to have the installation notes handy. For complex disk
configurations, relevant disk hardware manuals and a calculator are useful.
Proceed with install? [no] y
Cool! Let's get to it.
You will now initialize the disk(s) that OpenBSD will use. To enable all
available security features you should configure the disk(s) to allow the
creation of separate filesystems for /, /tmp, /var, /usr, and /home.
No disks found.
#
--
Ron Oliver
