here is the installation dmesg when trying to install the 5.2 i386 snapshot:
----- LSI Logic Corp. MPT IME BIOS Copyright 1995-2005 LSI Logic Corp. MPTBIOS-IME-5.13.08 CD-ROM: 9F Loading /5.2/I386/CDBOOT probing: pc0 apm pci mem[616K 2046M a20=on] disk: hd0+* cd0 >> OpenBSD/i386 CDBOOT 3.17 boot> booting cd0a:/5.2/i386/bsd.rd: 5973772+958284 [52+229744+218028]=0x709d1c entry point at 0x200128 Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 19995-2012 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.2 (RAMDISK_CD) #287: Wed Aug 1 10:19:00 MDT 2012 der...@i386.openbsd.org:/usr/src/sys/sys/arch/i386/compile/RAMDISK_CD cpu0: Intel(R) Xeon(TM) CPU 3.00 GHz ("GenuineIntel" 686-class) 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,NXE,LONG,SSE3,MWAIT,DS-CPL,CNXT- ID, CX16,xTPR real mem = 2146414592 (2046MB) avail mem = 2183640064 (2006MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 09/16/85, BIOS32 rev. 0 @ 0xfd418, SMBIOS rev. 2.33 @ 0xdc010 (58 entries) bios0: vendor FSC version "6.8 Rev. R04A5F1.1790" date 09/16/2005 bios0: FUJITSU SIEMENES PRIMERGY RX200S2 acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP MCFC SPCR APIC BOOY SSDT acpimadt0 at acpi0 addt 0xfee00000: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 200MHz cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioacpi0 at mainbus0: apid 2 pa 0xfec00000, version 20, 24 pins ioacpi1 at mainbus0: apid 3 pa 0xfec80000, version 20, 24 pins ioacpi2 at mainbus0: apid 4 pa 0xfec80400, version 20, 24 pins acpiprt0 at acpi0: bus 2 (P2P3) acpiprt1 at acpi0: bus 3 (P2P4) acpiprt2 at acpi0: bus 0 (PCI0) acpiprt3 at acpi0: bus 4 (PCIB) bios0: ROM list: 0xc0000/0x8000 0xc8000/0x4000 0xdc000/0x4000! pci0 at mainbus0 bus 0: configuration mode 1 (bios) pchb0 at pci0 dev 0 function 0 "Intel E7520 Host" rev 0x09 "Intel E7520 Error Reporting" rev 0x09 at pci0 dev 0 function 1 not configured ppb0 at pci0 dev 2 function 0 "Intel E7520 PCIE" rev 0x09 pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 "Intel 6700PXH PCIE-PCIX" rev 0x09 pci2 at ppb1 bus 2 "Intel IOxAPIC" rev 0x09 at pci1 dev 0 function 1 not configured ppb2 at pci1 dev 0 function 2 "Intel 6700PXH PCIE-PCIX" rev 0x09 pci3 at ppb2 bus 3 em0 at pci3 dev 3 function 0 "Intel PRO/1000MT (82545CM)" rev 0x04: apic 2 int1 6, address 00:04:23:c4:01:16 mpi0 at pci3 dev 5 function 0 "Symbios Logic 53c1030" rev 0x07: msi scsibus0 at mpi0: 16 targets, initiator 7 sd0 at scsibus0 targ 1 lun 0: <LSILOGIC, 1030 IM, 1000> SCSI2 0/direct fixed sd0: 34700MB, 512 bytes/sector, 71065600 sectors mpi0: timeout mpi0: timeout mpi0: timeout mpi0: timeout mpi0: timeout mpi0: timeout mpi0: phys disk Async at 0 MHz width 8bit offset 0 QAS 0 DT 0 IU 0 em1 at pci3 dev 6 function 0 "Intel PRO/100MT (82546GB)" rev 0x03: apic 2 int 1 6uvm_fault (0xd07f31d8, 0x0, 0, 1) -> e fatal page fault (6) in supervisor mode trap type 6 code 0 eip 0 cs 50 eflags 10282 cr2 0 cpl 50 panic: trap type 6, code=0, pc=0 The operating system has halted Please press any key to reboot --------------- Thanks On Thu, Nov 29, 2012 at 2:25 PM, Nick Holland <n...@holland-consulting.net>wrote: > On 11/29/12 06:42, Tony Berth wrote: > > Thanks > > > > Both i386 and amd64 fail! But, are that many differences between stable > and > > current? > > You caught us, nothing has changed in OpenBSD since 1995, we just drink > beer and increment the version number every six months. > </sarcasm> > > The most significant changes tend to take place just AFTER unlocking of > a new version of OpenBSD -- i.e., BEFORE the CDs ship. So yes, -current > is significantly different than the most recent release. > > Now, step away from the "!" key, and lets see if we can help you help us > help you. > > Here's the situation... apparently, no one has been installing OpenBSD > on this particular machine before. Never heard of it myself, whatever > that means. A quick google showed me a lot of PDF files I don't wish to > look at, but apparently it is a rack-mount server. > > There's apparently a problem between this machine and OpenBSD. > > You have three choices I see: > 1) provide one or two of these machines to developers. > 2) provide useful information to developers > 3) give up, as without either 1 or 2, we aren't going to be able to help > you. > > I'm going to guess you don't have the spare money/machine to provide a > few machines to the project. > > The first piece of useful information we could use would be a COMPLETE > dmesg, collected via a serial port as an install kernel boots. So, grab > a null modem cable and another computer, and gather that for us...then > maybe we can give you some suggestions. The dmesg tells us what is in > your machine, how it is connected, and sometimes, an idea of what went > wrong. > > Nick. > > > > > > > On Thu, Nov 29, 2012 at 11:20 AM, MichaÅ Markowski > > <markows...@gmail.com>wrote: > > > >> 2012/11/29 Tony Berth <tonybe...@googlemail.com>: > >> > s a fresh install! I couldn't find a CD image for current or did I > >> > miss something? > >> > >> Try latest snapshot, e.g. > >> http://ftp.icm.edu.pl/pub/OpenBSD/snapshots/i386/ (or amd64, you > >> didn't specify) > >> > >> -- > >> MichaÅ Markowski
