now I got the installation log of current trying the amd64 distro:
-
CD-ROM: 9F
Loading /5.2/AMD64/CDBOOT
probing: pc0 mem[620K 2046M a20=on]
disk: hd0+* cd0
>> OpenBSD/amd64 CDBOOT 3.19
boot>
booting cd0a:/5.2/amd64/bsd.rd: 3046708
8]=0xb8eb78
entry point at 0x1001e0 [7205c766, 34
indeed. Looks like the mixed it up. As long as I get the 'current' log I'll
send it to the list.
Thanks
On Mon, Dec 3, 2012 at 6:23 PM, Sebastian Reitenbach <
sebas...@l00-bugdead-prods.de> wrote:
>
> Am Montag, 03. Dezember 2012 17:57 CET, Tony Berth <
> tonybe...@googlemail.com> schrieb:
>
> >
2012/12/3 Tony Berth :
> it is the current one (2012-12-02)
Well, this is actual snapshot:
> OpenBSD 5.2-current (RAMDISK_CD) #86 Sun Dec 2 13:59:04 MST 2012
--
Michał Markowski
Am Montag, 03. Dezember 2012 17:57 CET, Tony Berth
schrieb:
> it is the current one (2012-12-02)
> > 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
but dmesg says its not so current like you think it is.
it is the current one (2012-12-02)
Thanks
On Mon, Dec 3, 2012 at 6:52 PM, Kenneth R Westerback wrote:
> On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
> > here is the installation dmesg when trying to install the 5.2 i386
> snapshot:
>
> And the installation dmesg from a -current s
On Mon, Dec 03, 2012 at 06:08:34PM +0200, Tony Berth wrote:
> here is the installation dmesg when trying to install the 5.2 i386 snapshot:
And the installation dmesg from a -current snapshot would be even
more useful.
Ken
>
> -
> LSI Logic Corp. MPT IME BIOS
> Copyright 1995-2005 LSI
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
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.
The most significant changes t
Thanks
Both i386 and amd64 fail! But, are that many differences between stable and
current?
On Thu, Nov 29, 2012 at 11:20 AM, MichaÅ Markowski
wrote:
> 2012/11/29 Tony Berth :
> > s a fresh install! I couldn't find a CD image for current or did I
> > miss something?
>
> Try latest snapshot, e
2012/11/29 Tony Berth :
> 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
this is a fresh install! I couldn't find a CD image for current or did I
miss something?
The machine is right now somehow 'isolated' and doesn't have any floppy or
serial console attached :(
I don't know if its a way to capture the dmesg other than the ones
described in:
http://openbsd.org/faq/f
On Wed, Nov 28, 2012 at 6:55 PM, Tony Berth wrote:
> Dear group,
>
> I was trying to install OBSD 5.2 on a Fujitsu-Siemens PRIMERGY RX200 S2
> (dual CPU) and I get following errors:
By any chance ability to try current?
>
>
> mpi0: timeout
> mpi0: phys disk Async at 0 MHz wi
2012/11/28 Tony Berth :
> I aslo saw that the bsd.rd kernel was used during the boot process. Meaning
> that the smp mode is not used?
No. http://openbsd.org/faq/faq4.html#bsd.rd
--
Michał Markowski
Dear group,
I was trying to install OBSD 5.2 on a Fujitsu-Siemens PRIMERGY RX200 S2
(dual CPU) and I get following errors:
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
14 matches
Mail list logo
