I reinstalled it with the last snapshots.
Installation process using http method: OK
At startup, i get the black screen after this line:
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
Noway to connect from an other computer: no pings and no ssh;
So init doesnt start /etc/rc (so no dmesg.boot in /var/run)
The only way i found, is to make screenshots :
http://snag.gy/lnqUE.jpg
http://snag.gy/aQg7a.jpg
http://snag.gy/9eRyC.jpg
http://snag.gy/ruCob.jpg
http://snag.gy/Fk6zI.jpg
http://snag.gy/TEcWt.jpg
Hope this will help to debug.
2014-12-12 20:12 GMT+04:00 Theo de Raadt :
>
> > >Synopsis: UKC>
>
> > OpenBSD 5.6-current (GENERIC.MP) #609: Thu Dec 11 21:36:32 MST 2014
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
> > cpu0: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz ("GenuineIntel" 686-class)
> 3.06 GHz
> > cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,LAHF,PERF,ITSC
> > real mem = 3144695808 (2999MB)
> > avail mem = 3080982528 (2938MB)
> > User Kernel Config
> > UKC> disqbl\^H \^H\^H \^H\^H \^Hable acpi
> > 492 acpi0 disabled
> > UKC> di\^H \^H\^H \^Hquit
> > Continuing...
> > mpath0 at root
> > scsibus0 at mpath0: 256 targets
> > mainbus0 at root
> > bios0 at mainbus0: AT/286+ BIOS, date 11/30/09, BIOS32 rev. 0 @ 0xf0010,
> SMBIOS rev. 2.6 @ 0xfbac0 (45 entries)
> > bios0: vendor Dell Inc. version "A02" date 11/30/2009
> > bios0: Dell Inc. Inspiron 580
> > acpi at bios0 function 0x0 not configured
> > mpbios0 at bios0: Intel MP Specification 1.4
>
> A major problem.
>
> You have now disabled acpi. Now your machine is using mpbios. And
> that means everything changes. Your dmesg is now useless to us.
> Everything before the acpi line is uninteresting and uninformative,
> but everything after the mpbios line influenced by MPBIOS, so it is
> not very useful either.
>
> One day you guys are going to stop following the 'disable acpi'
> recipe, but until then the replies will remain the same: What you just
> submitted as a bug report is useless. A 'disable acpi' dmest does not
> help find the problem.
>
> What you should have done is get the machine setup well enough that
> you can login from remote in the failing configuration, then collect
> the information.
>
--
==wma
