Re: [Raspberry Pi 4] Installing OpenBSD 7.5 with difficulty

[Douglas Silva]

> Did you inject RPI UEFI firmware into the BOOT partition?


Are you talking about some third-party bootloader software? No, I'm 
using the default U-Boot that comes with the miniroot. No modification 
required.

Re: [Raspberry Pi 4] Installing OpenBSD 7.5 with difficulty

[Douglas Silva]

I've upgraded from 7.4 to 7.5 and had no issues with the Raspberry Pi 4 model 
B. Ethernet works for me - during the installation and afterwards. I use it as 
a home server.

To connect to it, I use the serial console. The root storage device is a USB 
(v3.X) stick, and it's encrypted with a keydisk. No SD card (it broke some time 
ago).

Re: [Raspberry Pi 4] Installing OpenBSD 7.5 with difficulty

[Peter J. Philipp]

On Tue, Apr 16, 2024 at 06:08:13PM +0200, Peter J. Philipp wrote:
> On Tue, Apr 16, 2024 at 04:35:23PM +0100, Polarian wrote:
> 
> > Does anyone have any suggestions on what I could try?

> OpenBSD 7.5-current (GENERIC.MP) #11: Thu Apr 11 17:03:03 MDT 2024
> dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP

Oops that was the wrong dmesg:

-pjp

OpenBSD 7.5-current (GENERIC.MP) #11: Thu Apr 11 17:03:03 MDT 2024
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 8432803840 (8042MB)
avail mem = 8131481600 (7754MB)
random: good seed from bootblocks
mainbus0 at root: ACPI
psci0 at mainbus0: PSCI 1.1, SMCCC 1.2
efi0 at mainbus0: UEFI 2.7
efi0: https://github.com/pftf/RPi4 rev 0x1
smbios0 at efi0: SMBIOS 3.3.0
smbios0: vendor https://github.com/pftf/RPi4 version "UEFI Firmware v1.21" date 
11/13/2020
smbios0: Raspberry Pi Foundation Raspberry Pi 4 Model B
cpu0 at mainbus0 mpidr 0: ARM Cortex-A72 r0p3
cpu0: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache
cpu0: 1024KB 64b/line 16-way L2 cache
cpu0: CRC32,ASID16
cpu1 at mainbus0 mpidr 1: ARM Cortex-A72 r0p3
cpu1: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache
cpu1: 1024KB 64b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: ARM Cortex-A72 r0p3
cpu2: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache
cpu2: 1024KB 64b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: ARM Cortex-A72 r0p3
cpu3: 48KB 64b/line 3-way L1 PIPT I-cache, 32KB 64b/line 2-way L1 D-cache
cpu3: 1024KB 64b/line 16-way L2 cache
apm0 at mainbus0
ampintc0 at mainbus0 nirq 256, ncpu 4 ipi: 0, 1, 2: "interrupt-controller"
agtimer0 at mainbus0: 54000 kHz
acpi0 at mainbus0: ACPI 6.3
acpi0: sleep states
acpi0: tables DSDT FACP CSRT DBG2 GTDT IORT APIC PPTT SSDT BGRT
acpi0: wakeup devices
acpiiort0 at acpi0
"BCM2849" at acpi0 not configured
"BCM2835" at acpi0 not configured
"BCM2854" at acpi0 not configured
"ACPI0004" at acpi0 not configured
xhci0 at acpi0 XHC0 addr 0x6/0x1000 irq 175, xHCI 1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Generic xHCI root hub" rev 3.00/1.00 
addr 1
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
"ACPI0004" at acpi0 not configured
"BCM2848" at acpi0 not configured
"BCM2850" at acpi0 not configured
"BCM2856" at acpi0 not configured
"BCM2845" at acpi0 not configured
"BCM2841" at acpi0 not configured
"BCM2841" at acpi0 not configured
"BCM2838" at acpi0 not configured
"BCM2839" at acpi0 not configured
"BCM2844" at acpi0 not configured
pluart0 at acpi0 URT0 addr 0xfe201000/0x1000 irq 153
"BCM2836" at acpi0 not configured
"BCM2EA6" at acpi0 not configured
"MSFT8000" at acpi0 not configured
sdhc0 at acpi0 SDC1 addr 0xfe30/0x100 irq 158
sdhc0: base clock frequency unknown
"BCM2855" at acpi0 not configured
bse0 at acpi0 ETH0 addr 0xfd58/0x1 irq 189: address dc:a6:32:cc:db:a7
brgphy0 at bse0 phy 1: BCM54210E 10/100/1000baseT PHY, rev. 2
"PNP0C06" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
acpitz0 at acpi0: critical temperature is 90 degC
acpipwrres0 at acpi0: PFAN, resource for FAN0
uhub1 at uhub0 port 1 configuration 1 interface 0 "VIA Labs USB2.0 Hub" rev 
2.10/4.21 addr 2
uhidev0 at uhub1 port 3 configuration 1 interface 0 "American Power Conversion 
Back-UPS CS 650 FW:817.v9.I USB FW:v9" rev 1.10/0.06 addr 3
uhidev0: iclass 3/0, 98 report ids
upd0 at uhidev0
uhid0 at uhidev0 reportid 1: input=0, output=0, feature=1
uhid1 at uhidev0 reportid 2: input=0, output=0, feature=1
uhid2 at uhidev0 reportid 3: input=0, output=0, feature=1
uhid3 at uhidev0 reportid 4: input=0, output=0, feature=1
uhid4 at uhidev0 reportid 5: input=0, output=0, feature=1
uhid5 at uhidev0 reportid 6: input=0, output=0, feature=2
uhid6 at uhidev0 reportid 8: input=0, output=0, feature=2
uhid7 at uhidev0 reportid 9: input=0, output=0, feature=2
uhid8 at uhidev0 reportid 10: input=0, output=0, feature=2
uhid9 at uhidev0 reportid 11: input=0, output=0, feature=2
uhid10 at uhidev0 reportid 12: input=1, output=0, feature=1
uhid11 at uhidev0 reportid 13: input=2, output=0, feature=2
uhid12 at uhidev0 reportid 14: input=0, output=0, feature=2
uhid13 at uhidev0 reportid 15: input=0, output=0, feature=1
uhid14 at uhidev0 reportid 16: input=0, output=0, feature=2
uhid15 at uhidev0 reportid 17: input=0, output=0, feature=1
uhid16 at uhidev0 reportid 18: input=0, output=0, feature=2
uhid17 at uhidev0 reportid 19: input=0, output=0, feature=3
uhid18 at uhidev0 reportid 20: input=0, output=0, feature=1
uhid19 at uhidev0 reportid 21: input=0, output=0, feature=2
uhid20 at uhidev0 reportid 22: input=1, output=0, feature=1
uhid21 at uhidev0 reportid 23: input=0, output=0, feature=1
uhid22 at uhidev0 reportid 24: input=0, output=0, feature=2
uhid23 at uhidev0 reportid 25: input=0, output=0, feature=2
uhid24 at uhidev0 reportid 26: input=0, output=0, feature=2

Re: [Raspberry Pi 4] Installing OpenBSD 7.5 with difficulty

[Peter J. Philipp]

On Tue, Apr 16, 2024 at 04:35:23PM +0100, Polarian wrote:

> Does anyone have any suggestions on what I could try?

Hi, I too have a RPI 4b that is currently my workstation.  Near the time of
release I was building my own base and packages, which was right near the
times of the ld.so changes, things stopped working.  For a while I was X11
forwarding browsers to this because everything else failed.

I finally gave up, and installed a snapshot and packages from cdn.

Right now everything seems to work great.

My status report for you,
-pjp

PS: I'll share a dmesg (from /var/run/dmesg.boot) below my signature:

-- 
my associated domains:  callpeter.tel|centroid.eu|dtschland.eu|mainrechner.de


OpenBSD 7.5-current (GENERIC.MP) #11: Thu Apr 11 17:03:03 MDT 2024
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 4185792512 (3991MB)
avail mem = 3971813376 (3787MB)
random: good seed from bootblocks
mainbus0 at root: ACPI
psci0 at mainbus0: PSCI 1.0, SMCCC 1.1
efi0 at mainbus0: UEFI 2.7
efi0: EDK II rev 0x1
smbios0 at efi0: SMBIOS 3.0.0
smbios0: vendor Hetzner version "2017" date 11/11/2017
smbios0: Hetzner vServer
cpu0 at mainbus0 mpidr 0: ARM Neoverse N1 r3p1
cpu0: 64KB 64b/line 4-way L1 PIPT I-cache, 64KB 64b/line 4-way L1 D-cache
cpu0: 1024KB 64b/line 8-way L2 cache
cpu0: 
DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL,LRCPC,DPB,ASID16,PAN+ATS1E1,LO,HPDS,VH,HAFDBS,CSV3,CSV2,SSBS+MSR
cpu1 at mainbus0 mpidr 1: ARM Neoverse N1 r3p1
cpu1: 64KB 64b/line 4-way L1 PIPT I-cache, 64KB 64b/line 4-way L1 D-cache
cpu1: 1024KB 64b/line 8-way L2 cache
apm0 at mainbus0
agintc0 at mainbus0 shift 4:4 nirq 288 nredist 2 ipi: 0, 1, 2: 
"interrupt-controller"
agintcmsi0 at agintc0
agtimer0 at mainbus0: 25000 kHz
acpi0 at mainbus0: ACPI 5.1
acpi0: sleep states
acpi0: tables DSDT FACP APIC GTDT MCFG SPCR DBG2 IORT BGRT
acpi0: wakeup devices
acpimcfg0 at acpi0
acpimcfg0: addr 0x401000, bus 0-255
acpiiort0 at acpi0
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
pluart0 at acpi0 COM0 addr 0x900/0x1000 irq 33
pluart0: console
"LNRO0015" at acpi0 not configured
"LNRO0015" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
acpipci0 at acpi0 PCI0
pci0 at acpipci0
"Red Hat Host" rev 0x00 at pci0 dev 0 function 0 not configured
virtio0 at pci0 dev 1 function 0 "Qumranet Virtio 1.x GPU" rev 0x01
viogpu0 at virtio0: 1024x768, 32bpp
wsdisplay0 at viogpu0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
virtio0: msix per-VQ
ppb0 at pci0 dev 2 function 0 "Red Hat PCIE" rev 0x00: irq 37
pci1 at ppb0 bus 1
virtio1 at pci1 dev 0 function 0 "Qumranet Virtio 1.x Network" rev 0x01
vio0 at virtio1: address 96:00:02:1f:61:38
virtio1: msix shared
ppb1 at pci0 dev 2 function 1 "Red Hat PCIE" rev 0x00: irq 37
pci2 at ppb1 bus 2
xhci0 at pci2 dev 0 function 0 "Red Hat xHCI" rev 0x01: msix, xHCI 0.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Red Hat xHCI root hub" rev 3.00/1.00 
addr 1
ppb2 at pci0 dev 2 function 2 "Red Hat PCIE" rev 0x00: irq 37
pci3 at ppb2 bus 3
virtio2 at pci3 dev 0 function 0 "Qumranet Virtio 1.x Console" rev 0x01
virtio2: no matching child driver; not configured
ppb3 at pci0 dev 2 function 3 "Red Hat PCIE" rev 0x00: irq 37
pci4 at ppb3 bus 4
virtio3 at pci4 dev 0 function 0 "Qumranet Virtio 1.x Memory Balloon" rev 0x01
viomb0 at virtio3
virtio3: irq 37
ppb4 at pci0 dev 2 function 4 "Red Hat PCIE" rev 0x00: irq 37
pci5 at ppb4 bus 5
virtio4 at pci5 dev 0 function 0 "Qumranet Virtio 1.x RNG" rev 0x01
viornd0 at virtio4
virtio4: irq 37
ppb5 at pci0 dev 2 function 5 "Red Hat PCIE" rev 0x00: irq 37
pci6 at ppb5 bus 6
virtio5 at pci6 dev 0 function 0 "Qumranet Virtio 1.x SCSI" rev 0x01
vioscsi0 at virtio5: qsize 128
scsibus0 at vioscsi0: 255 targets
cd0 at scsibus0 targ 0 lun 0:  removable
sd0 at 

Re: Installing OpenBSD amd64 on UTM on Intel Mac?

[Adam Retter]

Here is my blog post on how I got this working -
https://blog.adamretter.org.uk/running-openbsd-74-under-utm/

On Sat, 13 Jan 2024 at 19:55, Adam Retter  wrote:
>
> I've had some success with this on Intel Mac, although it requires some 
> workarounds. I'm in the process of writing a blog, I'll post it here in the 
> next few days if I can...
>
> On Fri, 12 Jan 2024, 22:32 Implausibility,  wrote:
>>
>> Hi.
>>
>> Since there's some uncertainty around the future of VMware Fusion on the 
>> Mac, I've decided to switch to UTM (with QEMU under the covers) -- but I 
>> can't seem to get OpenBSD .isos (7.3 or 7.4) to boot -- instead, I get 
>> dumped into the UEFI shell, which is a dead end.
>>
>> I've done a number of searches (on the mailing list and the web in general), 
>> and all of the results are for running the ARM64 port on the M-series Macs 
>> -- but my target machine has an Intel CPU.
>>
>> Can anyone provide some insight into running OpenBSD under UTM on a Mac?
>>
>> Thanks.
>>


-- 
Adam Retter

skype: adam.retter
tweet: adamretter
http://www.adamretter.org.uk

Re: Installing OpenBSD amd64 on UTM on Intel Mac?

[David Demelier]

> On Jan 12, 2024, at 21:31, Implausibility  wrote:
> 
> Hi.
> 
> Since there's some uncertainty around the future of VMware Fusion on the Mac, 
> I've decided to switch to UTM (with QEMU under the covers) -- but I can't 
> seem to get OpenBSD .isos (7.3 or 7.4) to boot -- instead, I get dumped into 
> the UEFI shell, which is a dead end.
> 
> I've done a number of searches (on the mailing list and the web in general), 
> and all of the results are for running the ARM64 port on the M-series Macs -- 
> but my target machine has an Intel CPU.

I've installed OpenBSD on my Mac Studio m2 max, you need a few tweaks but it 
works, keep it mind that running a desktop is near to impossible because really 
laggy.

1. Create a new VM
2. Select Skip ISO boot option
3. Add a new drive and import the .img file

Now it should boots fine. IIRC, I've followed these instructions [0].

[0]: https://nomnp.com/plaintext/utmopenbsd

HTH,

-- 
David

Re: Installing OpenBSD amd64 on UTM on Intel Mac?

[Nowarez Market]

Sorry if I pop up in the thread with my argument:

before all, anyone know the shortcut to boot a Mac Pro from a usb stick
to install OpenBSD?


> N0\/\/@r€Z
> --
>    /\/\@rk€T

Re: Installing OpenBSD amd64 on UTM on Intel Mac?

[Adam Retter]

I've had some success with this on Intel Mac, although it requires some
workarounds. I'm in the process of writing a blog, I'll post it here in the
next few days if I can...

On Fri, 12 Jan 2024, 22:32 Implausibility,  wrote:

> Hi.
>
> Since there's some uncertainty around the future of VMware Fusion on the
> Mac, I've decided to switch to UTM (with QEMU under the covers) -- but I
> can't seem to get OpenBSD .isos (7.3 or 7.4) to boot -- instead, I get
> dumped into the UEFI shell, which is a dead end.
>
> I've done a number of searches (on the mailing list and the web in
> general), and all of the results are for running the ARM64 port on the
> M-series Macs -- but my target machine has an Intel CPU.
>
> Can anyone provide some insight into running OpenBSD under UTM on a Mac?
>
> Thanks.
>
>

Installing OpenBSD amd64 on UTM on Intel Mac?

[Implausibility]

Hi.

Since there's some uncertainty around the future of VMware Fusion on the Mac, 
I've decided to switch to UTM (with QEMU under the covers) -- but I can't seem 
to get OpenBSD .isos (7.3 or 7.4) to boot -- instead, I get dumped into the 
UEFI shell, which is a dead end.

I've done a number of searches (on the mailing list and the web in general), 
and all of the results are for running the ARM64 port on the M-series Macs -- 
but my target machine has an Intel CPU.

Can anyone provide some insight into running OpenBSD under UTM on a Mac? 

Thanks.

Re: Installing openBSD

[bsdprg]

Aug 4, 2023, 08:19 by jfsimon1...@gmail.com:

> Further multi-boot is absolutely not a good idea from experience. Some OS
> just don't care about your boot, they claim they own the platform and will
> occasionally quite mess with it.
>
> That's not just Windows.
>

Some OSs including OpenBSD overwrite BOOT/BOOTx64.efi because UEFI systems may 
not always boot the latest added boot entry as the default, and simply boot 
BOOTx64 fallback entry. So, not overwriting BOOTx64 can sometimes lead to 
unbootable systems.
With efibootmgr and refind, this issue can be fixed easily, and we can get a 
nice prompt to boot whichever OS we want to.
Buying another drive simply for this issue is an overkill.



> Best option is multi drive and select bootable drive on bios short-key but 
> each
> one is essentially its own complete OS/Boot partition independently from the
> others.
>
> That's pretty safe and working not too bad.
>
> Regard
>
> Jean-François
>
> On 7/31/23 19:08, Theo de Raadt wrote:
>
>> Multiboot support will never be a priority in OpenBSD.
>>
>> None of the developers are using multiboot scenarios.  We develop and
>> test OpenBSD to support what we use, that is why it is so good at what
>> it does, and that is also also why it sucks ass for multiboot.
>>
>> I suggest you get over it.  If that is a dealbreaker, I guess OpenBSD
>> is not for you!
>>
>> We'll be perfectly happy if people insisting on multiboot go elsewhere.
>> They'll be happier also.
>>
>> ykla  wrote:
>>
>>> Actually, I think it's a bug that OpenBSD cannot create EFI partitions 
>>> manually. File
>>> systems that write MSDOS, mount points that write /boot/efi, or none at all 
>>> are not
>>> recognized by the system, and the installer will indicate that it can't 
>>> install the
>>> boot and fail to boot the system. If you want to use a custom partition, 
>>> you must
>>> first use AutoPartition to create a number of partitions, including an 
>>> i-partition,
>>> i.e., an efi partition. Then do it manually by deleting the partitions 
>>> other than the
>>> i-partition. This is the only way to customize the partition. Any manually 
>>> created efi
>>> partition system will not be recognized.
>>>
>>> Umgeher Torgersen  于 2023年8月1日周二 上午12:21写道：
>>>
>>>  On Mon, Jul 31, 2023 at 09:37:13AM -0600, Theo de Raadt wrote:
>>>  > Omar Polo  wrote:
>>>  >
>>>  > > On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
>>>  > > >
>>>  > > > Hi,
>>>  > > >
>>>  > > > But fdisk also has an option to edit the existing partition table.
>>>  > >
>>>  > > only if you want to do stuff manually, which from the thread I assume
>>>  > > you don't need.
>>>  > >
>>>  > > > This
>>>  > > > allows me to delete only the partitions related to PfSense without
>>>  > > > deleting the (U)EFI partition.
>>>  > >
>>>  > > yeah, if you ask to do things by yourself, you get to do the things
>>>  > > manually :)
>>>  > >
>>>  > > > The question here is whether I will need
>>>  > > > it to boot openBSD's root partition.
>>>  > >
>>>  > > choose 'use whole disk' and let the installer nuke and re-create the
>>>  > > partition table.  it'll do the right thing for a standard
>>>  > > installation.
>>>  > >
>>>  >
>>>  > Karel,
>>>  >
>>>  > I will be going for a walk first.
>>>  >
>>>  > I'm trying to figure out if I should put my left foot first.
>>>  > Or should it be the right?
>>>
>>>  both
>>>
>>>  > I'm so terribly confused!  I would not want to put the wrong foot first.
>>>  >
>>>

Re: Installing openBSD

[Jean-François Simon]

Further multi-boot is absolutely not a good idea from experience. Some OS
just don't care about your boot, they claim they own the platform and will
occasionally quite mess with it.

That's not just Windows.

Best option is multi drive and select bootable drive on bios short-key 
but each

one is essentially its own complete OS/Boot partition independently from the
others.

That's pretty safe and working not too bad.

Regard

Jean-François

On 7/31/23 19:08, Theo de Raadt wrote:

Multiboot support will never be a priority in OpenBSD.

None of the developers are using multiboot scenarios.  We develop and
test OpenBSD to support what we use, that is why it is so good at what
it does, and that is also also why it sucks ass for multiboot.

I suggest you get over it.  If that is a dealbreaker, I guess OpenBSD
is not for you!

We'll be perfectly happy if people insisting on multiboot go elsewhere.
They'll be happier also.

ykla  wrote:


Actually, I think it's a bug that OpenBSD cannot create EFI partitions 
manually. File
systems that write MSDOS, mount points that write /boot/efi, or none at all are 
not
recognized by the system, and the installer will indicate that it can't install 
the
boot and fail to boot the system. If you want to use a custom partition, you 
must
first use AutoPartition to create a number of partitions, including an 
i-partition,
i.e., an efi partition. Then do it manually by deleting the partitions other 
than the
i-partition. This is the only way to customize the partition. Any manually 
created efi
partition system will not be recognized.

Umgeher Torgersen  于 2023年8月1日周二 上午12:21写道：

  On Mon, Jul 31, 2023 at 09:37:13AM -0600, Theo de Raadt wrote:
  > Omar Polo  wrote:
  >
  > > On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
  > > >
  > > > Hi,
  > > >
  > > > But fdisk also has an option to edit the existing partition table.
  > >
  > > only if you want to do stuff manually, which from the thread I assume
  > > you don't need.
  > >
  > > > This
  > > > allows me to delete only the partitions related to PfSense without
  > > > deleting the (U)EFI partition.
  > >
  > > yeah, if you ask to do things by yourself, you get to do the things
  > > manually :)
  > >
  > > > The question here is whether I will need
  > > > it to boot openBSD's root partition.
  > >
  > > choose 'use whole disk' and let the installer nuke and re-create the
  > > partition table.  it'll do the right thing for a standard
  > > installation.
  > >
  >
  > Karel,
  >
  > I will be going for a walk first.
  >
  > I'm trying to figure out if I should put my left foot first.
  > Or should it be the right?

  both

  > I'm so terribly confused!  I would not want to put the wrong foot first.
  >

Re: Installing openBSD

[Jean-François Simon]

Always the right one

On 7/31/23 17:37, Theo de Raadt wrote:

Omar Polo  wrote:


On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:

Hi,

But fdisk also has an option to edit the existing partition table.

only if you want to do stuff manually, which from the thread I assume
you don't need.


This
allows me to delete only the partitions related to PfSense without
deleting the (U)EFI partition.

yeah, if you ask to do things by yourself, you get to do the things
manually :)


The question here is whether I will need
it to boot openBSD's root partition.

choose 'use whole disk' and let the installer nuke and re-create the
partition table.  it'll do the right thing for a standard
installation.


Karel,

I will be going for a walk first.

I'm trying to figure out if I should put my left foot first.
Or should it be the right?

I'm so terribly confused!  I would not want to put the wrong foot first.

Re: Installing openBSD

[Nick Holland]

On 8/3/23 16:48, Karel Lucas wrote:


Hi,

My openBSD installation was successful! I first removed all partitions
except for the EFI partition, which I left. Second I created one openBSD
partition(type A6) on the freed space, after which I partitioned that
partition with auto layout. Then I continued with the regular
installation, and after reboot I got the login prompt. So in hindsight
it was wise to leave the EFI partition. Perhaps others can benefit from
this experience.


So you leapt from "This didn't break the shit out of my computer" to
"everyone should do it this way".  Creative.  But wrong.

NO.  If you don't have reason to retain the EFI partition (i.e.,
multibooting), just pick whole disk GPT and quit wasting time.

If you don't know what is in your EFI partition, you SHOULD overwrite
it so you know you have a clean and trustable system.

OpenBSD is designed to be able to install on wiped disks, new disks,
or co-exist with other systems.  You seem to think that if you go
out a buy a new hard disk at the store, you couldn't possibly
install OpenBSD on it because there's no existing EFI partition.
A lot of people can assure you this is incorrect.

Nick.




Op 01-08-2023 om 07:04 schreef patric conant:
Hitting enter in the installer to use the whole disk will take care of 
you. As pointed out repeatedly, there are no requirements from pfsense 
to install or maintain openbsd. In the same way that pfsense didn't 
need anything form OpenBSD to install, OpenBSD can create all the 
necessary partitions for successful EFI experience, and doesn't need 
anything from pfsense.


On Sun, Jul 30, 2023 at 12:41 PM Karel Lucas  wrote:


Hi all,

I'm going to install openBSD on a small PC that currently has
PfSense on
it. This PC boots this OS via (U)EFI, and therefore has an EFI
partition
on the existing SSD. The current partition table looks like, as
shown by
openBSD fdisk:

  0: efiboot0
  1: gptboot0
  2: swap0
  3: zfs0.

Should I keep the (U)EFI partition? And if so, how do I mount the
future
openBSD root partition to this (U)EFI installation? Are there any
other
things I should watch out for? I look forward to receiving responses
from this community. Sincerely, Karel.



--
Patric Conant
Mirage Computing Lead Consultant
@MirageComputing on twitter
https://m.facebook.com/MirageComputing/
316 409 2424

Re: Installing openBSD

[David Demelier]

On Thu, 2023-08-03 at 22:48 +0200, Karel Lucas wrote:
> 
> Hi,
> 
> My openBSD installation was successful!

Have fun on OpenBSD.

> I first removed all partitions
> except for the EFI partition, which I left.

Sure, the EFI partition isn't supposed to be formatted/recreated but
shared among systems.


-- 
David

Re: Installing openBSD

[Karel Lucas]

Hi,

My openBSD installation was successful! I first removed all partitions 
except for the EFI partition, which I left. Second I created one openBSD 
partition(type A6) on the freed space, after which I partitioned that 
partition with auto layout. Then I continued with the regular 
installation, and after reboot I got the login prompt. So in hindsight 
it was wise to leave the EFI partition. Perhaps others can benefit from 
this experience.



Op 01-08-2023 om 07:04 schreef patric conant:
Hitting enter in the installer to use the whole disk will take care of 
you. As pointed out repeatedly, there are no requirements from pfsense 
to install or maintain openbsd. In the same way that pfsense didn't 
need anything form OpenBSD to install, OpenBSD can create all the 
necessary partitions for successful EFI experience, and doesn't need 
anything from pfsense.


On Sun, Jul 30, 2023 at 12:41 PM Karel Lucas  wrote:


Hi all,

I'm going to install openBSD on a small PC that currently has
PfSense on
it. This PC boots this OS via (U)EFI, and therefore has an EFI
partition
on the existing SSD. The current partition table looks like, as
shown by
openBSD fdisk:

  0: efiboot0
  1: gptboot0
  2: swap0
  3: zfs0.

Should I keep the (U)EFI partition? And if so, how do I mount the
future
openBSD root partition to this (U)EFI installation? Are there any
other
things I should watch out for? I look forward to receiving responses
from this community. Sincerely, Karel.



--
Patric Conant
Mirage Computing Lead Consultant
@MirageComputing on twitter
https://m.facebook.com/MirageComputing/
316 409 2424

Re: Installing openBSD

[Abel Abraham Camarillo Ojeda]

On Wed, Aug 2, 2023 at 7:31 AM David Demelier  wrote:

> On Tue, 2023-08-01 at 01:00 +0800, ykla wrote:
> > Actually, I think it's a bug that OpenBSD cannot create EFI
> > partitions manually.
>
> I've installed OpenBSD many times in dualboot with linux (for some
> things we can't do right now on OpenBSD such as ESP32 development). And
> my take is to install Linux first, actually quite simple to go for a
> dual boot afterwards. I go back to linux and configure the bootloader
> (i.e. efibootmgr, grub, whatever you like).
>
> macOS and Windows are not really friendly in that area either. I can't
> blame an OS to not spend effort for those topics, being able to boot
> any OS from EFI is already good enough.
>
> --
> David
>
>
Note that multiboot with refind is trivial (UEFI only), it automatically
detects windows, linux and openbsd.
Just install them in that order, and refind at the end.

Re: Installing openBSD

[David Demelier]

On Tue, 2023-08-01 at 01:00 +0800, ykla wrote:
> Actually, I think it's a bug that OpenBSD cannot create EFI
> partitions manually.

I've installed OpenBSD many times in dualboot with linux (for some
things we can't do right now on OpenBSD such as ESP32 development). And
my take is to install Linux first, actually quite simple to go for a
dual boot afterwards. I go back to linux and configure the bootloader
(i.e. efibootmgr, grub, whatever you like).

macOS and Windows are not really friendly in that area either. I can't
blame an OS to not spend effort for those topics, being able to boot
any OS from EFI is already good enough.

-- 
David

Re: Installing openBSD

[Chris Bennett]

On Mon, Jul 31, 2023 at 04:08:49PM +0200, Karel Lucas wrote:
> 
> Hi,
> 
> Multi-boot is not an option here. The intention is to replace the entire
> PfSense installation with openBSD. Eventually this computer becomes a
> firewall with PF, so the current installation is unnecessary. But my
> question remains whether I need the (U)EFI partition for that or not. Can
> anyone give me some helpful advice?
> 

Also, give some serious thought about the partition sizes AND order that
you create them.

The order matters if you ever suspect that you will need to make a
partition bigger. Read the growfs man page. You can only make a
partition bigger by sacrificing the immediate partition after it.

So if you have /home then /usr/local and you need /home bigger. Bad
ordering of the partitions.
But if you have /home followed by /usr/kittens and you can get rid of having
/usr/kittens as a partition (but back it up!) and just add it to the /usr
directory afterwards 

Also, don't create "useless" partitions. If you will never use /usr/src
as a separate partition, don't put it in it's own partition. Developers
or people wanting to play around with source code like having it.
Please read the entire FAQ page.

growfs can only make a partition bigger ( and you keep existing files as
a bonus ). There isn't a tool to make them smaller and keep data on it.

Also, the partitions that are normally created has a big effect on
security.
nodev, nosuid, wxallowed are important.

Most important is to not get freaked out. Just do it and see what
happens. Screwing up is half the fun! Cleaning up isn't fun, but a good
way to learn. ;-}

-- 
Chris Bennett

Re: Installing openBSD

[Steve Litt]

Karel Lucas said on Mon, 31 Jul 2023 16:08:49 +0200

>Hi,
>
>Multi-boot is not an option here. The intention is to replace the
>entire PfSense installation with openBSD. Eventually this computer
>becomes a firewall with PF, so the current installation is
>unnecessary. But my question remains whether I need the (U)EFI
>partition for that or not. Can anyone give me some helpful advice?

Once you delete the EFI partition it's gone. I've had mobos that booted
EFI but not MBR, mobos that booted MBR but not EFI, and mobos that
could boot either if the partition/media was correctly created for the
MBR or EFI. So I understand your concern and your desire to get an
answer to your question.

I understand that your question is about making sure you can get a
working install, rather than the desire to dual boot or manually
specify all partitions and mountpoints.

It's been awhile since I installed OpenBSD, so I don't remember exactly
what goes where. Why don't you install OpenBSD on a VM somewhere, check
out the directory layout, manually create that layout on your hard disk
after deleting all but the EFI partition and directory containing it.
The EFI partition isn't all that big, so if you later don't need it,
you're not wasting much room.

As you know, the MBR/EFI legacy/EFI decision for the motherboard is
done in the bios.  

HTH,

SteveT

Steve Litt 
Autumn 2022 featured book: Thriving in Tough Times
http://www.troubleshooters.com/bookstore/thrive.htm

Re: Installing openBSD

[Brian Conway]

On Mon, Jul 31, 2023, at 12:00 PM, ykla wrote:
> Any manually created efi
> partition system will not be recognized.

I can assure you, it will (when done correctly). I have done so 
manually/scripted with EFI+GPT and EFI+MBR many times. An example of the less 
common EFI+MBR approach for the installer ramdisk is here:

https://github.com/openbsd/src/blob/master/distrib/amd64/ramdisk_cd/Makefile#L19

Maybe you can work backwards from it to see what you're doing wrong.

Brian

Re: Installing openBSD

[Theo de Raadt]

Multiboot support will never be a priority in OpenBSD.

None of the developers are using multiboot scenarios.  We develop and
test OpenBSD to support what we use, that is why it is so good at what
it does, and that is also also why it sucks ass for multiboot.

I suggest you get over it.  If that is a dealbreaker, I guess OpenBSD
is not for you!

We'll be perfectly happy if people insisting on multiboot go elsewhere.
They'll be happier also.

ykla  wrote:

> Actually, I think it's a bug that OpenBSD cannot create EFI partitions 
> manually. File
> systems that write MSDOS, mount points that write /boot/efi, or none at all 
> are not
> recognized by the system, and the installer will indicate that it can't 
> install the
> boot and fail to boot the system. If you want to use a custom partition, you 
> must
> first use AutoPartition to create a number of partitions, including an 
> i-partition,
> i.e., an efi partition. Then do it manually by deleting the partitions other 
> than the
> i-partition. This is the only way to customize the partition. Any manually 
> created efi
> partition system will not be recognized.
> 
> Umgeher Torgersen  于 2023年8月1日周二 上午12:21写道：
> 
>  On Mon, Jul 31, 2023 at 09:37:13AM -0600, Theo de Raadt wrote:
>  > Omar Polo  wrote:
>  > 
>  > > On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
>  > > > 
>  > > > Hi,
>  > > > 
>  > > > But fdisk also has an option to edit the existing partition table.
>  > > 
>  > > only if you want to do stuff manually, which from the thread I assume
>  > > you don't need.
>  > > 
>  > > > This 
>  > > > allows me to delete only the partitions related to PfSense without 
>  > > > deleting the (U)EFI partition.
>  > > 
>  > > yeah, if you ask to do things by yourself, you get to do the things
>  > > manually :)
>  > > 
>  > > > The question here is whether I will need 
>  > > > it to boot openBSD's root partition.
>  > > 
>  > > choose 'use whole disk' and let the installer nuke and re-create the
>  > > partition table.  it'll do the right thing for a standard
>  > > installation.
>  > > 
>  > 
>  > Karel,
>  > 
>  > I will be going for a walk first.
>  > 
>  > I'm trying to figure out if I should put my left foot first.
>  > Or should it be the right?
> 
>  both
> 
>  > I'm so terribly confused!  I would not want to put the wrong foot first.
>  > 
> 

Re: Installing openBSD

[ykla]

Actually, I think it's a bug that OpenBSD cannot create EFI partitions
manually. File systems that write MSDOS, mount points that write /boot/efi,
or none at all are not recognized by the system, and the installer will
indicate that it can't install the boot and fail to boot the system. If you
want to use a custom partition, you must first use AutoPartition to create
a number of partitions, including an i-partition, i.e., an efi partition.
Then do it manually by deleting the partitions other than the i-partition.
This is the only way to customize the partition. Any manually created efi
partition system will not be recognized.


Umgeher Torgersen  于 2023年8月1日周二 上午12:21写道：

> On Mon, Jul 31, 2023 at 09:37:13AM -0600, Theo de Raadt wrote:
> > Omar Polo  wrote:
> >
> > > On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
> > > >
> > > > Hi,
> > > >
> > > > But fdisk also has an option to edit the existing partition table.
> > >
> > > only if you want to do stuff manually, which from the thread I assume
> > > you don't need.
> > >
> > > > This
> > > > allows me to delete only the partitions related to PfSense without
> > > > deleting the (U)EFI partition.
> > >
> > > yeah, if you ask to do things by yourself, you get to do the things
> > > manually :)
> > >
> > > > The question here is whether I will need
> > > > it to boot openBSD's root partition.
> > >
> > > choose 'use whole disk' and let the installer nuke and re-create the
> > > partition table.  it'll do the right thing for a standard
> > > installation.
> > >
> >
> > Karel,
> >
> > I will be going for a walk first.
> >
> > I'm trying to figure out if I should put my left foot first.
> > Or should it be the right?
>
> both
>
> > I'm so terribly confused!  I would not want to put the wrong foot first.
> >
>
>

Re: Installing openBSD

[Umgeher Torgersen]

On Mon, Jul 31, 2023 at 09:37:13AM -0600, Theo de Raadt wrote:
> Omar Polo  wrote:
> 
> > On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
> > > 
> > > Hi,
> > > 
> > > But fdisk also has an option to edit the existing partition table.
> > 
> > only if you want to do stuff manually, which from the thread I assume
> > you don't need.
> > 
> > > This 
> > > allows me to delete only the partitions related to PfSense without 
> > > deleting the (U)EFI partition.
> > 
> > yeah, if you ask to do things by yourself, you get to do the things
> > manually :)
> > 
> > > The question here is whether I will need 
> > > it to boot openBSD's root partition.
> > 
> > choose 'use whole disk' and let the installer nuke and re-create the
> > partition table.  it'll do the right thing for a standard
> > installation.
> > 
> 
> Karel,
> 
> I will be going for a walk first.
> 
> I'm trying to figure out if I should put my left foot first.
> Or should it be the right?

both

> I'm so terribly confused!  I would not want to put the wrong foot first.
> 

Re: Installing openBSD

[Matthew Ernisse]

On Sun, Jul 30, 2023 at 07:30:27PM +0200, Karel Lucas said:
Should I keep the (U)EFI partition? And if so, how do I mount the 
future openBSD root partition to this (U)EFI installation? Are there 
any other things I should watch out for? I look forward to receiving 
responses from this community. Sincerely, Karel.


As others have said the OpenBSD installer is able to re-use the entire 
disk and will install the nessicary components to boot OpenBSD.  I'll simply 
add that you would do well to read and understand the Installation Guide [1] 
and the INSTALL file for the architecture you are using (likely amd64[2] 
since you mention EFI) before you attempt the installation, they should 
answer nearly all of your questions -- even the ones you don't know you 
have yet.


[1] https://www.openbsd.org/faq/faq4.html
[2] https://ftp.openbsd.org/pub/OpenBSD/7.3/amd64/INSTALL.amd64

--
Matthew Ernisse
https://www.going-flying.com/

Re: Installing openBSD

[Theo de Raadt]

Omar Polo  wrote:

> On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
> > 
> > Hi,
> > 
> > But fdisk also has an option to edit the existing partition table.
> 
> only if you want to do stuff manually, which from the thread I assume
> you don't need.
> 
> > This 
> > allows me to delete only the partitions related to PfSense without 
> > deleting the (U)EFI partition.
> 
> yeah, if you ask to do things by yourself, you get to do the things
> manually :)
> 
> > The question here is whether I will need 
> > it to boot openBSD's root partition.
> 
> choose 'use whole disk' and let the installer nuke and re-create the
> partition table.  it'll do the right thing for a standard
> installation.
> 

Karel,

I will be going for a walk first.

I'm trying to figure out if I should put my left foot first.
Or should it be the right?

I'm so terribly confused!  I would not want to put the wrong foot first.

Re: Installing openBSD

[Omar Polo]

On 2023/07/31 17:19:59 +0200, Karel Lucas  wrote:
> 
> Hi,
> 
> But fdisk also has an option to edit the existing partition table.

only if you want to do stuff manually, which from the thread I assume
you don't need.

> This 
> allows me to delete only the partitions related to PfSense without 
> deleting the (U)EFI partition.

yeah, if you ask to do things by yourself, you get to do the things
manually :)

> The question here is whether I will need 
> it to boot openBSD's root partition.

choose 'use whole disk' and let the installer nuke and re-create the
partition table.  it'll do the right thing for a standard
installation.

Re: Installing openBSD

[Karel Lucas]

Hi,

But fdisk also has an option to edit the existing partition table. This 
allows me to delete only the partitions related to PfSense without 
deleting the (U)EFI partition. The question here is whether I will need 
it to boot openBSD's root partition.


Op 31-07-2023 om 16:10 schreef Theo de Raadt:

Karel Lucas  wrote:


Multi-boot is not an option here. The intention is to replace the entire
PfSense installation with openBSD. Eventually this computer becomes a
firewall with PF, so the current installation is unnecessary. But my
question remains whether I need the (U)EFI partition for that or not.
Can anyone give me some helpful advice?

you are overthinking it

the default way through the installer reuses the whole disk.

Re: Installing openBSD

[Theo de Raadt]

Karel Lucas  wrote:

> Multi-boot is not an option here. The intention is to replace the entire 
> PfSense installation with openBSD. Eventually this computer becomes a 
> firewall with PF, so the current installation is unnecessary. But my 
> question remains whether I need the (U)EFI partition for that or not. 
> Can anyone give me some helpful advice?

you are overthinking it

the default way through the installer reuses the whole disk.

Re: Installing openBSD

[Karel Lucas]

Hi,

Multi-boot is not an option here. The intention is to replace the entire 
PfSense installation with openBSD. Eventually this computer becomes a 
firewall with PF, so the current installation is unnecessary. But my 
question remains whether I need the (U)EFI partition for that or not. 
Can anyone give me some helpful advice?


Op 31-07-2023 om 14:33 schreef Peter N. M. Hansteen:

On Mon, Jul 31, 2023 at 07:52:02AM -0400, Nick Holland wrote:

IF you want to multiboot, just don't until you can answer questions like
this yourself.  Multibooting is very complicated, and requires a mastery
of the boot process of ALL the OSs installed.  People often consider it
a way to "learn" a new OS, I disagree, it is a good way to get massively
frustrated and lose a lot of data.

I could not agree more.

Unless you are specifically interested in learning how to develop bootloaders
and that is something that yo consider essential to your career plan going
forward, please do not mess with multibooting.

If your plan is to learn anything besides bootloader internals, please
do the sane thing and either run the one you are trying to learn on bare
hardware (the best you can afford) or if you are comfortable with a
virtualization platform, use that.

Multibooting will always be a painful distraction unless bootloaders
and their interactions with OSes and random hardware is what you want
to spend the bulk of your time on.

- Peter

Re: Installing openBSD

[Karel Lucas]

Hi,

It is not intended to be a dual boot installation. Therefore, the 
PfSense installation must be replaced by open BSD. My question is what I 
should do with the (U)efi partition, and how I can possibly link open 
BSD to it. Does anyone have some good suggestions for me?



Op 31-07-2023 om 00:06 schreef Saïd AARAB:

Hi,

It depends if you want to keep the existing psfsens install or if you 
want dual boot.


If looking to install beside pfsens, I would beleive that installing 
OpenBSD along any existing OS should be no different than installing 
linux or windows along another OS, as you would need to prepare the 
block device (SDD) by making space if possible (and if you dont have 
any) for another partition in which you would install OpenBSD. so any 
documentation (explaining how to shrink existing partitions, create 
another partion, handle dual boot) that is not necessarily specific to 
OpenBSD should help.
Im not very familiar with how pfsens work and if it did install a 
bootloader, if not you might need to install one like GRUB and 
configure it to be able to select between the two OS at startup.


Overall installing dual boot is very tricky and you should be carefull 
to not wipe your existing data, a backup is advised




On Jul 30, 2023 19:30, Karel Lucas  wrote:


Hi all,

I'm going to install openBSD on a small PC that currently has
PfSense on
it. This PC boots this OS via (U)EFI, and therefore has an EFI
partition
on the existing SSD. The current partition table looks like, as
shown by
openBSD fdisk:

 0: efiboot0
 1: gptboot0
 2: swap0
 3: zfs0.

Should I keep the (U)EFI partition? And if so, how do I mount the
future
openBSD root partition to this (U)EFI installation? Are there any
other
things I should watch out for? I look forward to receiving responses
from this community. Sincerely, Karel.

Re: Installing openBSD

[Peter N. M. Hansteen]

On Mon, Jul 31, 2023 at 07:52:02AM -0400, Nick Holland wrote:
> 
> IF you want to multiboot, just don't until you can answer questions like
> this yourself.  Multibooting is very complicated, and requires a mastery
> of the boot process of ALL the OSs installed.  People often consider it
> a way to "learn" a new OS, I disagree, it is a good way to get massively
> frustrated and lose a lot of data.

I could not agree more. 

Unless you are specifically interested in learning how to develop bootloaders
and that is something that yo consider essential to your career plan going 
forward, please do not mess with multibooting. 

If your plan is to learn anything besides bootloader internals, please
do the sane thing and either run the one you are trying to learn on bare
hardware (the best you can afford) or if you are comfortable with a
virtualization platform, use that.

Multibooting will always be a painful distraction unless bootloaders
and their interactions with OSes and random hardware is what you want
to spend the bulk of your time on.

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
https://bsdly.blogspot.com/ https://www.bsdly.net/ https://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Installing openBSD

[Nick Holland]

On 7/30/23 13:30, Karel Lucas wrote:


Hi all,

I'm going to install openBSD on a small PC that currently has PfSense on
it. This PC boots this OS via (U)EFI, and therefore has an EFI partition
on the existing SSD. The current partition table looks like, as shown by
openBSD fdisk:

   0: efiboot0
   1: gptboot0
   2: swap0
   3: zfs0.

Should I keep the (U)EFI partition? And if so, how do I mount the future
openBSD root partition to this (U)EFI installation? Are there any other
things I should watch out for? I look forward to receiving responses
from this community. Sincerely, Karel.



The OpenBSD installer is designed to be able to install to a totally blank
hard disk, so there is no need to retain any of the current partitions.

IF you are trying to do simple wipe and load, just chose the "entire disk
GPT" option and everything will happen as you wish, most likely.

If you think your hardware is special, you might want to test on another
disk, at least temporarily.

IF you want to multiboot, just don't until you can answer questions like
this yourself.  Multibooting is very complicated, and requires a mastery
of the boot process of ALL the OSs installed.  People often consider it
a way to "learn" a new OS, I disagree, it is a good way to get massively
frustrated and lose a lot of data.

Nick.

Re: Installing openBSD

[Chris Bennett]

On Sun, Jul 30, 2023 at 07:30:27PM +0200, Karel Lucas wrote:
> 
> Hi all,
> 
> I'm going to install openBSD on a small PC that currently has PfSense on it.
> This PC boots this OS via (U)EFI, and therefore has an EFI partition on the
> existing SSD. The current partition table looks like, as shown by openBSD
> fdisk:
> 
>  0: efiboot0
>  1: gptboot0
>  2: swap0
>  3: zfs0.
> 
> Should I keep the (U)EFI partition? And if so, how do I mount the future
> openBSD root partition to this (U)EFI installation? Are there any other
> things I should watch out for? I look forward to receiving responses from
> this community. Sincerely, Karel.
> 

If you can afford a 2nd hard drive, that makes life very easy. Just have
a partition that is MSDOS if you need exchange files between all OS's

If you can't install a 2nd hard drive, OpenBSD runs fantastic on USB
sticks. (Assuming that the BIOS allows it.)

Plus, you can put it in your pocket and boot other computers somewhere
else. 
Plus, you can get USB SSD or spinning hard drives.

However, if you are doing disk intensive work, USB is slow.

-- 
Chris Bennett

Re: Installing openBSD

[rturner93]

Good morning,
I'll preface this with: I'm a new OpenBSD user.
Yes you should keep the EFI partition...but the OpenBSD installer is
pretty thorough and easy to use if you don't have any special
circumstances.
I too started with pfsense and swapped to OpenBSD as a learning
exercise.  But I did that after a pretty good base in Linux systems
including your question here.  I'd encourage you to thoroughly study Pf
and how to configure rules.  Handwriting rules is a bit easier to get
wrong than the pfsense interface.
Good luck!
On 31 Jul 2023 01:30, Karel Lucas  wrote:


  Hi all,

  I'm going to install openBSD on a small PC that currently has PfSense
  on
  it. This PC boots this OS via (U)EFI, and therefore has an EFI
  partition
  on the existing SSD. The current partition table looks like, as shown
  by
  openBSD fdisk:

   0: efiboot0
   1: gptboot0
   2: swap0
   3: zfs0.

  Should I keep the (U)EFI partition? And if so, how do I mount the
  future
  openBSD root partition to this (U)EFI installation? Are there any
  other
  things I should watch out for? I look forward to receiving responses
  from this community. Sincerely, Karel.

Re: Installing openBSD

[Saïd AARAB]

Hi,
It depends if you want to keep the existing psfsens install or if you
want dual boot.

If looking to install beside pfsens, I would beleive that installing
OpenBSD along any existing OS should be no different than installing
linux or windows along another OS, as you would need to prepare the block
device (SDD) by making space if possible (and if you dont have any) for
another partition in which you would install OpenBSD. so any
documentation (explaining how to shrink existing partitions, create
another partion, handle dual boot) that is not necessarily specific to
OpenBSD should help.Im not very familiar with how pfsens work and if it
did install a bootloader, if not you might need to install one like GRUB
and configure it to be able to select between the two OS at startup.
Overall installing dual boot is very tricky and you should be carefull to
not wipe your existing data, a backup is advised


On Jul 30, 2023 19:30, Karel Lucas  wrote:


  Hi all,

  I'm going to install openBSD on a small PC that currently has PfSense
  on
  it. This PC boots this OS via (U)EFI, and therefore has an EFI
  partition
  on the existing SSD. The current partition table looks like, as shown
  by
  openBSD fdisk:

   0: efiboot0
   1: gptboot0
   2: swap0
   3: zfs0.

  Should I keep the (U)EFI partition? And if so, how do I mount the
  future
  openBSD root partition to this (U)EFI installation? Are there any
  other
  things I should watch out for? I look forward to receiving responses
  from this community. Sincerely, Karel.

Installing openBSD

[Karel Lucas]

Hi all,

I'm going to install openBSD on a small PC that currently has PfSense on 
it. This PC boots this OS via (U)EFI, and therefore has an EFI partition 
on the existing SSD. The current partition table looks like, as shown by 
openBSD fdisk:


 0: efiboot0
 1: gptboot0
 2: swap0
 3: zfs0.

Should I keep the (U)EFI partition? And if so, how do I mount the future 
openBSD root partition to this (U)EFI installation? Are there any other 
things I should watch out for? I look forward to receiving responses 
from this community. Sincerely, Karel.

Re: Installing OpenBSD on MacbookPro 8,1 (Late/Early 2011)

[Anders Andersson]

On Thu, May 18, 2023 at 10:05 AM Daniele B.  wrote:
>
> Don't think your platform is supported:
> https://www.openbsd.org/plat.html
> https://www.openbsd.org/macppc.html
>
> otherwise let us know, I will install it on mine too ;d)

Top-posting is messy but I'll try it this way!

OPs states that his macbook is Intel i5, so macppc is irrelevant. This is amd64.



> May 18, 2023 08:39:07 yellowcutterpillow :
>
> > I wanted to install OpenBSD on my Macbook Pro 8,1 (Early/Late 2011)
> > but seem to fail. When I boot up install73.img or miniroot73.img, they
> > boot up, but when I actually boot up the ramdisk, bsd or bsd.rd, they
> > stuck up at a message about aicp0 being remapped or something. I would
> > try to diagnose it but I can't since when I boot with -c flag, the
> > cursor glitches, or the keyboard stops working, because I can't type
> > anything.
> >
> > I've set up a QEMU emulation of OpenBSD on my Linux box and it works
> > fine. The reason I did so is because I've sort read that I can configure
> > the kernel using it though I lost the reference, so now I don't have any
> > idea on how I can even turn on the ``verbose`` flag in the kernel. I
> > can't also access ``dmesg,`` so if anyone has any idea, I'd be more than
> > happy for your help. Some info, MBP 8,1 is Intel i5, QUAD CORE, and
> > UEFI. No BIOS options, not sure if it supports CMS.

Re: Installing OpenBSD on MacbookPro 8,1 (Late/Early 2011)

[Daniele B.]

Don't think your platform is supported:
https://www.openbsd.org/plat.html
https://www.openbsd.org/macppc.html

otherwise let us know, I will install it on mine too ;d)


-- Daniele Bonini


May 18, 2023 08:39:07 yellowcutterpillow :

> Hello!
> 
> I wanted to install OpenBSD on my Macbook Pro 8,1 (Early/Late 2011)
> but seem to fail. When I boot up install73.img or miniroot73.img, they
> boot up, but when I actually boot up the ramdisk, bsd or bsd.rd, they
> stuck up at a message about aicp0 being remapped or something. I would
> try to diagnose it but I can't since when I boot with -c flag, the
> cursor glitches, or the keyboard stops working, because I can't type
> anything.
> 
> I've set up a QEMU emulation of OpenBSD on my Linux box and it works
> fine. The reason I did so is because I've sort read that I can configure
> the kernel using it though I lost the reference, so now I don't have any
> idea on how I can even turn on the ``verbose`` flag in the kernel. I
> can't also access ``dmesg,`` so if anyone has any idea, I'd be more than
> happy for your help. Some info, MBP 8,1 is Intel i5, QUAD CORE, and
> UEFI. No BIOS options, not sure if it supports CMS.
> 
> Thank you very much!

Installing OpenBSD on MacbookPro 8,1 (Late/Early 2011)

[yellowcutterpillow]

Hello!

I wanted to install OpenBSD on my Macbook Pro 8,1 (Early/Late 2011)
but seem to fail. When I boot up install73.img or miniroot73.img, they
boot up, but when I actually boot up the ramdisk, bsd or bsd.rd, they
stuck up at a message about aicp0 being remapped or something. I would
try to diagnose it but I can't since when I boot with -c flag, the
cursor glitches, or the keyboard stops working, because I can't type
anything.

I've set up a QEMU emulation of OpenBSD on my Linux box and it works
fine. The reason I did so is because I've sort read that I can configure
the kernel using it though I lost the reference, so now I don't have any
idea on how I can even turn on the ``verbose`` flag in the kernel. I
can't also access ``dmesg,`` so if anyone has any idea, I'd be more than
happy for your help. Some info, MBP 8,1 is Intel i5, QUAD CORE, and
UEFI. No BIOS options, not sure if it supports CMS.

Thank you very much!

Re: Installing OpenBSD on new Chromebook

[David Coppa]

Il Sab 29 Ott 2022, 01:02 Jeff Ross  ha scritto:

> Hi all,
>
> I got a nice new laptop at Costco for under $200.  I did the developer
> mode to get to a linux shell and installed a bunch of programs but I'd
> rather just wipe the whole disk and install OpenBSD.
>
> All of places I'm finding with directions on how to do this are from
> circa 2015 and do not work now.
>
> Anybody have a pointer to a more updated set of directions I can try?
>
> Thanks!
>
> Jeff Ross
>

There's also this detailed howto by jcs@:

https://jcs.org/2016/08/26/openbsd_chromebook

Bye,
David

Re: Installing OpenBSD on new Chromebook

[Chris Eidem]

You can't just boot any old USB from a Chromebook. It has a locked down 
BIOS. More information here:


https://mrchromebox.tech/

On 10/28/22 17:59, Jeff Ross wrote:

Hi all,

I got a nice new laptop at Costco for under $200.  I did the developer 
mode to get to a linux shell and installed a bunch of programs but I'd 
rather just wipe the whole disk and install OpenBSD.


All of places I'm finding with directions on how to do this are from 
circa 2015 and do not work now.


Anybody have a pointer to a more updated set of directions I can try?

Thanks!

Jeff Ross

Re: Installing OpenBSD on new Chromebook

[Jeff Ross]

On 10/29/22 8:50 AM, Nick Holland wrote:

On 10/29/22 10:11, Jeff Ross wrote:



On 10/29/22 1:29 AM, Stuart Henderson wrote:

On 2022-10-28, Gabriel Busch de Brito  wrote:


All of places I'm finding with directions on how to do this are 
from circa

2015 and do not work now.

Anybody have a pointer to a more updated set of directions I can try?

I suggest that you follow the installation guide at the FAQ section of
the website.


Chromebooks aren't standard computers and usually come with a
locked-down bootloader that will need disabling to install another OS.

Also if it's arm rather than x86 there will be additional challenges
beyond this.

So there's not enough information in the original post to give any kind
of pointer.



Thanks Stuart.

It's an HP Chromebook 14a-na1083d with an Intel Celeron N4500 with 4G
ram and 128 eMMC drive.

Booting up in developer mode it tells me that it is Model LANTIS-MEXL if
that helps.



Just install it, see what happens.  If you want a guarantee, buy me one
exactly like it, and I'll do what I'm suggesting you do. :)  (and then
you will discover why I call model numbers "market position statements",
not "unique HW configuration identification systems")

Or maybe better yet, see if it will boot from an OpenBSD install image
on a USB drive, if it does, set up a full OpenBSD install on a USB drive
and see what happens. I've had pretty good luck with HP PC-like systems
that weren't sold with "standard" operating systems on them, but past
experience is no indicator yada-yada-yada.

Pain points if you get past booting are likely to be wireless and graphics.

If you can get it to boot from a USB drive to test, you are probably good
for an install.  If you can't, probably not worth the effort.  There MAY be
tricks you can do, but you can put a lot of time and effort into forcing
something to install OpenBSD and then find out X doesn't work.  Or there's
no functioning network.  Or both.

Nick.



All good points, Nick.  I have tried booting it from an install USB 
stick with no luck.  Off list I was directed to https://mrchromebox.tech 
 and that tells me that this is at least possible, and includes the 
crucial step I didn't know about to enable booting from an external disk 
and bypassing the check for an official ChromeOS disk.


I'll be noodling around with this over the weekend--hopefully I'll be 
able to report success and, of course, include a dmesg.


Jeff

Re: Installing OpenBSD on new Chromebook

[Nick Holland]

On 10/29/22 10:11, Jeff Ross wrote:



On 10/29/22 1:29 AM, Stuart Henderson wrote:

On 2022-10-28, Gabriel Busch de Brito  wrote:



All of places I'm finding with directions on how to do this are from circa
2015 and do not work now.

Anybody have a pointer to a more updated set of directions I can try?

I suggest that you follow the installation guide at the FAQ section of
the website.


Chromebooks aren't standard computers and usually come with a
locked-down bootloader that will need disabling to install another OS.

Also if it's arm rather than x86 there will be additional challenges
beyond this.

So there's not enough information in the original post to give any kind
of pointer.



Thanks Stuart.

It's an HP Chromebook 14a-na1083d with an Intel Celeron N4500 with 4G
ram and 128 eMMC drive.

Booting up in developer mode it tells me that it is Model LANTIS-MEXL if
that helps.



Just install it, see what happens.  If you want a guarantee, buy me one
exactly like it, and I'll do what I'm suggesting you do. :)  (and then
you will discover why I call model numbers "market position statements",
not "unique HW configuration identification systems")

Or maybe better yet, see if it will boot from an OpenBSD install image
on a USB drive, if it does, set up a full OpenBSD install on a USB drive
and see what happens. I've had pretty good luck with HP PC-like systems
that weren't sold with "standard" operating systems on them, but past
experience is no indicator yada-yada-yada.

Pain points if you get past booting are likely to be wireless and graphics.

If you can get it to boot from a USB drive to test, you are probably good
for an install.  If you can't, probably not worth the effort.  There MAY be
tricks you can do, but you can put a lot of time and effort into forcing
something to install OpenBSD and then find out X doesn't work.  Or there's
no functioning network.  Or both.

Nick.

Re: Installing OpenBSD on new Chromebook

[Wolfgang Pfeiffer]

As it seems to be an x86_64 machine why not try a fresh OpenBSD
Live system via USB or DVD and and see what happens?
https://fuguita.org/

Wolfgang

On Sat, Oct 29, 2022 at 08:11:15AM -0600, Jeff Ross wrote:



On 10/29/22 1:29 AM, Stuart Henderson wrote:

On 2022-10-28, Gabriel Busch de Brito  wrote:



All of places I'm finding with directions on how to do this are from circa
2015 and do not work now.

Anybody have a pointer to a more updated set of directions I can try?

I suggest that you follow the installation guide at the FAQ section of
the website.


Chromebooks aren't standard computers and usually come with a
locked-down bootloader that will need disabling to install another OS.

Also if it's arm rather than x86 there will be additional challenges
beyond this.

So there's not enough information in the original post to give any kind
of pointer.



Thanks Stuart.

It's an HP Chromebook 14a-na1083d with an Intel Celeron N4500 with 4G
ram and 128 eMMC drive.

Booting up in developer mode it tells me that it is Model LANTIS-MEXL
if that helps.

I can get a linux dmesg from the linux VM if that helps at all.  Not
sure how much the VM would represent the actual hardware though.

Jeff


--
"Altars are burnin' with flames far and wide
 The foe has crossed over from the other side
 They tip their caps from the top of the hill
 You can feel them come, more brave blood to spill"

Bob Dylan: "'Cross The Green Mountain"

Re: Installing OpenBSD on new Chromebook

[Jeff Ross]

On 10/29/22 1:29 AM, Stuart Henderson wrote:

On 2022-10-28, Gabriel Busch de Brito  wrote:



All of places I'm finding with directions on how to do this are from circa
2015 and do not work now.

Anybody have a pointer to a more updated set of directions I can try?

I suggest that you follow the installation guide at the FAQ section of
the website.


Chromebooks aren't standard computers and usually come with a
locked-down bootloader that will need disabling to install another OS.

Also if it's arm rather than x86 there will be additional challenges
beyond this.

So there's not enough information in the original post to give any kind
of pointer.



Thanks Stuart.

It's an HP Chromebook 14a-na1083d with an Intel Celeron N4500 with 4G 
ram and 128 eMMC drive.


Booting up in developer mode it tells me that it is Model LANTIS-MEXL if 
that helps.


I can get a linux dmesg from the linux VM if that helps at all.  Not 
sure how much the VM would represent the actual hardware though.


Jeff

Re: Installing OpenBSD on new Chromebook

[Stuart Henderson]

On 2022-10-28, Gabriel Busch de Brito  wrote:
>
>> All of places I'm finding with directions on how to do this are from circa
>> 2015 and do not work now.
>> 
>> Anybody have a pointer to a more updated set of directions I can try?
> I suggest that you follow the installation guide at the FAQ section of
> the website.

Chromebooks aren't standard computers and usually come with a
locked-down bootloader that will need disabling to install another OS.

Also if it's arm rather than x86 there will be additional challenges
beyond this.

So there's not enough information in the original post to give any kind
of pointer.

-- 
Please keep replies on the mailing list.

Re: Installing OpenBSD on new Chromebook

[Gabriel Busch de Brito]

> All of places I'm finding with directions on how to do this are from circa
> 2015 and do not work now.
> 
> Anybody have a pointer to a more updated set of directions I can try?
I suggest that you follow the installation guide at the FAQ section of
the website.

Best,
G

Re: Installing OpenBSD on new Chromebook

[Jérôme Desquilbet]

Hi all,

I got a nice new laptop at Costco for under $200.  I did the developer 
mode to get to a linux shell and installed a bunch of programs but I'd 
rather just wipe the whole disk and install OpenBSD.


All of places I'm finding with directions on how to do this are from 
circa 2015 and do not work now.


Anybody have a pointer to a more updated set of directions I can try?

Thanks!

Jeff Ross


Hi Jeff,
To check your machine:
* 

To install and everything:
* 
  (this where to always look first)

Also, some up-to-date pages:
* 
  (more for a server, but useful anyway)
* 

Best,
Jérôme.

Installing OpenBSD on new Chromebook

[Jeff Ross]

Hi all,

I got a nice new laptop at Costco for under $200.  I did the developer 
mode to get to a linux shell and installed a bunch of programs but I'd 
rather just wipe the whole disk and install OpenBSD.


All of places I'm finding with directions on how to do this are from 
circa 2015 and do not work now.


Anybody have a pointer to a more updated set of directions I can try?

Thanks!

Jeff Ross

Re: installing openbsd on raspberry pi 4

[Benjamin Ludwig]

Hello,

I'm not Sure but shouldn't it be 
cd: /mnt/usr/share/zoneinfo 
instead of:
cd: /mnt/user/share/zoneinfo
?

regards 

Am 13. September 2021 15:48:02 MESZ schrieb Sandeep Gupta 
:
>Hello,
>
> I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to
>boot the openbsd installer off  of USB
> drive using  UEFI boot loader (on sd card). However the installer
>fails at the step "What timezone are you in?".
> It doesn't like any timezone I input. Just before this step I get the
>error "cd: /mnt/user/share/zoneinfo -- No such file or directory".
> I am not able to tell installer to skip this step.
>
>Another issue I am facing is that installer giving warning:
>"Are you *SURE* your install is complete without bsd" and other
>similar warnings.
>where should I place bsd, bsd.mp, and other files for installer to
>pick those up. On the usb drive I have only
>written miniroot68.img. This creates two partitions. None of these
>partitions seems like there correct place
>for bsd and other distribution sets files. Any pointers/help would be great.
>
>Thanks
>-S
>

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

installing openbsd on raspberry pi 4

[Sandeep Gupta]

Hello,

 I am stuck on installing openbsd 6.8 (or 6.9) on rpi 4. I am able to
boot the openbsd installer off  of USB
 drive using  UEFI boot loader (on sd card). However the installer
fails at the step "What timezone are you in?".
 It doesn't like any timezone I input. Just before this step I get the
error "cd: /mnt/user/share/zoneinfo -- No such file or directory".
 I am not able to tell installer to skip this step.

Another issue I am facing is that installer giving warning:
"Are you *SURE* your install is complete without bsd" and other
similar warnings.
where should I place bsd, bsd.mp, and other files for installer to
pick those up. On the usb drive I have only
written miniroot68.img. This creates two partitions. None of these
partitions seems like there correct place
for bsd and other distribution sets files. Any pointers/help would be great.

Thanks
-S

Installing OpenBSD on Oracle Cloud

[Anirudh Oppiliappan]

Hi,

I tried installing OpenBSD on an Oracle Cloud arm64 VM. Here's what I
did:

1. Download the arm64/install69.img
2. dd if=install69.img of=/dev/sda conv=fsdatasync bs=4096
3. echo b > /proc/sysrq-trigger

During step 2, I downloaded the install69.img into /run, which is a
ramdisk. The host was Oracle Linux.

Finally, I monitored the boot log via a serial connection (Console
Connection option in Oracle Cloud). Here's the output:

disks: sd0* sd1
>> OpenBSD/arm64 BOOTAA64 1.4
boot>
cannot open sd0a:/etc/random.seed: No such file or directory
booting sd0a:/bsd: 2478840+686516+12990752+632808 
[204131+109+602136+225211]=0x13fa278
FACP APIC GTDT MCFG SPCR IORT BGRT
type 0x2 pa 0x4000 va 0x0 pages 0x4000 attr 0x8
type 0x7 pa 0x4400 va 0x0 pages 0x1eb576 attr 0x8
type 0x2 pa 0x22f576000 va 0x0 pages 0xf71 attr 0x8
type 0x1 pa 0x2304e7000 va 0x0 pages 0x2a attr 0x8
type 0x3 pa 0x230511000 va 0x0 pages 0xdf attr 0x8
type 0x9 pa 0x2305f va 0x0 pages 0x10 attr 0x8
type 0x2 pa 0x23060 va 0x0 pages 0x6 attr 0x8
type 0x3 pa 0x230606000 va 0x0 pages 0xaa attr 0x8
type 0x6 pa 0x2306b va 0xa3863000 pages 0x50 attr 0x8008
type 0x5 pa 0x23070 va 0xa38b3000 pages 0x50 attr 0x8008
type 0x6 pa 0x23075 va 0xa3903000 pages 0x50 attr 0x8008
type 0x5 pa 0x2307a va 0xa3953000 pages 0x50 attr 0x8008
type 0x6 pa 0x2307f va 0xa39a3000 pages 0xc0 attr 0x8008
type 0x5 pa 0x2308b va 0xa3a63000 pages 0x60 attr 0x8008
type 0x6 pa 0x23091 va 0xa3ac3000 pages 0xa0 attr 0x8008
type 0x5 pa 0x2309b va 0xa3b63000 pages 0x50 attr 0x8008
type 0x6 pa 0x230a0 va 0xa3bb3000 pages 0x50 attr 0x8008
type 0x5 pa 0x230a5 va 0xa3c03000 pages 0xf0 attr 0x8008
type 0x2 pa 0x230b4 va 0x0 pages 0x4 attr 0x8
type 0x7 pa 0x230b44000 va 0x0 pages 0x1732 attr 0x8
type 0x4 pa 0x232276000 va 0x0 pages 0x77f attr 0x8
type 0x7 pa 0x2329f5000 va 0x0 pages 0x79 attr 0x8
type 0x4 pa 0x232a6e000 va 0x0 pages 0xfca attr 0x8
type 0x7 pa 0x233a38000 va 0x0 pages 0xa attr 0x8
type 0x3 pa 0x233a42000 va 0x0 pages 0x3de attr 0x8
type 0x5 pa 0x233e2 va 0xa6fd3000 pages 0x90 attr 0x8008
type 0x7 pa 0x233eb va 0x0 pages 0x10 attr 0x8
type 0x6 pa 0x233ec va 0xa7073000 pages 0x120 attr 0x8008
type 0x7 pa 0x233fe va 0x0 pages 0x1f attr 0x8
type 0x4 pa 0x233fff000 va 0x0 pages 0x21 attr 0x8
type 0x7 pa 0x23402 va 0x0 pages 0x349d attr 0x8
type 0x4 pa 0x2374bd000 va 0x0 pages 0x21 attr 0x8
type 0x3 pa 0x2374de000 va 0x0 pages 0x69 attr 0x8
type 0x4 pa 0x237547000 va 0x0 pages 0x96f attr 0x8
type 0x3 pa 0x237eb6000 va 0x0 pages 0x12 attr 0x8
type 0x4 pa 0x237ec8000 va 0x0 pages 0x101 attr 0x8
type 0x3 pa 0x237fc9000 va 0x0 pages 0x32 attr 0x8
type 0x4 pa 0x237ffb000 va 0x0 pages 0x5 attr 0x8
type 0xb pa 0x400 va 0xa7193000 pages 0x4000 attr 0x8001
type 0xb pa 0x901 va 0xab193000 pages 0x1 attr 0x8001
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2021 OpenBSD. All rights reserved.  https://www.OpenBSD.org

OpenBSD 6.9 (RAMDISK) #1060: Sun Apr 18 02:12:44 MDT 2021
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/RAMDISK
real mem  = 8432631808 (8041MB)
avail mem = 8047411200 (7674MB)
random: boothowto does not indicate good seed
mainbus0 at root: ACPI
psci0 at mainbus0: PSCI 1.0, SMCCC 1.1
cpu0 at mainbus0 mpidr 0: ARM Neoverse N1 r3p1
cpu0: 64KB 64b/line 4-way L1 PIPT I-cache, 64KB 64b/line 4-way L1 D-cache
cpu0: 1024KB 64b/line 8-way L2 cache
cpu0: 
DP,RDM,Atomic,CRC32,SHA2,SHA1,AES+PMULL,LRCPC,DPB,ASID16,PAN+ATS1E1,LO,HPDS,HAFDBS,CSV3,CSV2
efi0 at mainbus0: UEFI 2.7
efi0: EDK II rev 0x1
agintc0 at mainbus0 shift 4:4 nirq 288 nredist 2: "interrupt-controller"
agintcmsi0 at agintc0: unsupported type 0x0001ef71
agtimer0 at mainbus0: 25000 kHz
acpi0 at mainbus0: ACPI 5.1
acpi0: tables DSDT FACP APIC GTDT MCFG SPCR IORT BGRT
acpimcfg0 at acpi0
acpimcfg0: addr 0x401000, bus 0-255
acpiiort0 at acpi0
"ACPI0007" at acpi0 not configured
"ACPI0007" at acpi0 not configured
pluart0 at acpi0 COM0 addr 0x900/0x1000 irq 33: console
"LNRO0015" at acpi0 not configured
"LNRO0015" at acpi0 not configured
"QEMU0002" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO0005" at acpi0 not configured
"LNRO00

Re: Will windows 10 boot after installing openBSD?

[Kevin Chadwick]

You can also install Windows after and boot OpenBSD quite easily by following
the faq. This is not easy on grub/Linux as grub is greedy. Atleast the guides
that I found for grub/Linux, failed to work. I have no interest in running Linux
these days though and little interest then. I had the notion that my mum might
find updating easier. Now the opposite is certainly true. In fact, I had to tell
a grafana user on slack about apt-get dist-upgrade recently just to install
grafana. Also, when I did try a wifi experiment with fedora, it's recovery
kernel managed to break *itself* (yum or rather it's new name, broke/failed to
update it over time). Perhaps it had something to do with building the wifi
module, but recovery kernels should not break!

Well done on many counts, OpenBSD!

Re: Will windows 10 boot after installing openBSD?

[Abel Abraham Camarillo Ojeda]

On Monday, April 13, 2020, Никита Степанов 
wrote:

>
Yes

Will windows 10 boot after installing openBSD?

[Никита Степанов]

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

On Fri, 29 Nov 2019, Clay Daniels wrote:


Date: Fri, 29 Nov 2019 12:55:43 -0600
From: Clay Daniels 
To: "misc@openbsd.org" 
Subject: Re: Installing OpenBSD -current snapshots

Thanks to everyone who responded. If I knew all the answers I would not
have asked. And I should have read deeper into the documentation before
asking, and am in the process of doing so now.

What I decided was to stick with the release install66.fs boot image. It
works to completely install everything without floundering around to find
the file sets. I really have no need to run current OpenBSD. Maybe after a
few months of study I will think about it again.

Also I'm going to unsubscribe with this email account, and re-subscribe
with my account with sdf.org where I will not be stuck with google's
"top-posting". I don't like it either, same as everyone else.


Ok, this is my real unix email, run on netbsd. I use it via ssh in 
good old alpine. No more top-posting for me!

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Thanks to everyone who responded. If I knew all the answers I would not
have asked. And I should have read deeper into the documentation before
asking, and am in the process of doing so now.

What I decided was to stick with the release install66.fs boot image. It
works to completely install everything without floundering around to find
the file sets. I really have no need to run current OpenBSD. Maybe after a
few months of study I will think about it again.

Also I'm going to unsubscribe with this email account, and re-subscribe
with my account with sdf.org where I will not be stuck with google's
"top-posting". I don't like it either, same as everyone else.

Clay

Re: Installing OpenBSD -current snapshots

[Nick Holland]

On 2019-11-29 02:26, Clay Daniels wrote:
> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I would not be better off doing what Bruno & Marc
> suggested and run sysupgrade. Thanks to them for the advice.

sysupgrade does upgrades of existing systems.  Very slick.  However, it
isn't for fresh installs, and if you have convenient console access, it's
not the preferred way of doing it.  And based on the questions here,
NO WAY.  You need to understand what's going on before you start doing
unattended upgrades.

It also (by default) assumes network upgrades, and if you are wanting
everything on local media, there are existing better solutions.

And yes, following current is a never-ending quest.  However, problems
are relatively rare and usually not a big deal, and generally fixed on
the next snapshot.
 
> If I do decide to put the filesets on the the install thumbdrive, I see a
> total of 26 files in the directory. Obviously some are not necessary like
> the floppy or both the .fs & .iso (just one needed), nor the test
> instructions, etc.
> So which files do I REALLY need on my usb thumbdrive to get a complete
> install, x included?


STOP STOP STOP STOP.
You need to re-read what I wrote and the install part of the FAQ some
more times.
The install66.fs file is an image with the *entire install set included*.
You do not want to add things.  You COULD do some voodoo to add stuff to
the miniroot66.fs, but PLEASE DON'T...you would just be re-inventing the
install66.fs, poorly and with more difficulty.

> 
> Please excuse the "top-posting". That's the only way my darn google mail
> does reply's. Kind of irritating, to me and the reader too.
 
Bottom posting was invented for those who can't write in complete thoughts
with context.  You know, like most of the computer world. :-/

Nick.




> Clay
> 
> 
> 
> 
> On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 
> wrote:
> 
>> On 2019-11-27 21:29, Edgar Pettijohn wrote:
>> > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> >> I have successfully installed OpenBSD 6.6 release and would like to give
>> >> the Current Snapshots a try. I went to a mirror, and to:
>> >>
>> >> Index of /pub/OpenBSD/snapshots/amd64/
>> >>
>> >> I saw install66.fs (probably for usb memstick) and install66.iso (surely
>> >> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> >> thumbdrive, and it starts the install. When i get into the install it
>> asks
>> >> where are the file sets? Humm, maybe it gets these online and it tries
>> to
>> >> do this but no luck. It was late last night, and I checked to see if it
>> had
>> >> written anything to my disk, which it had not, and went to bed. This
>> >> evening I'm looking a bit deeper at the snapshot directory and I
>> suspect I
>> >> need to provide the install with base66.tzg at ~239Mb.
>>
>> NO!
>>
>> [snip misleading stuff]
>> > I noticed this also, but hadn't had time to figure out if I had messed
>> up or
>> > the installer had. As a general rule I assume its me that messed up. Its
>> odd
>> > if you mount the install66.fs you can see the pub/amd64 directory, but
>> during
>> > installation it can't seem to find the directory regardless of what I
>> have
>> > tried.
>> >
>> > Edgar
>>
>> First of all...nothing at all to do about snapshots -- the OpenBSD
>> installation process has remained amazingly stable over the last 20
>> years.
>> New options here and there, but overall, very similar.  Unless something
>> changed in the last few days, installing a snapshot is identical to
>> installing 6.6.
>>
>> The installXX.iso and installXX.fs are complete, stand-alone installation
>> kits.  Everything you need is on them.  You can boot from them, and all
>> the installation files are right there.  Look Ma!  No network needed!
>> ...well...unfortunately there is the issue of firmware files, which are
>> legally not feasible to put on the install media, so you will need network
>> for most machines eventually.  But let's ignore that for now. :)
>>
>> Once the system has booted on the install kernel, you have three devices
>> you are working with:
>> 1) the install kernel's internal "RAM disk" that is part of bsd.rd which
>>   you booted from,
>> 2) your target disk
>> 3) the USB drive with the install files on it.
>>
>> The reason you can't see the install files on the USB stick from the
>> install kernel is they aren't mounted.  You didn't boot from the entire
>> USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
>> to be sitting on the big USB stick...but as far as bsd.rd is concerned,
>> the USB stick isn't part of the booted environment (yet).
>>
>> You aren't booting from a "Live Media".  You are booting from a tiny kernel
>> with a built in file system that's sitting on the same inert file 

Re: Installing OpenBSD -current snapshots

[Mihai Popescu]

> BTW, why do you want to run -current?
> There are only 2 real reasons to do that
> [ ... ]

Total nonsense ...

Re: Installing OpenBSD -current snapshots

[Eric Furman]

On Fri, Nov 29, 2019, at 2:26 AM, Clay Daniels wrote:
> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I would not be better off doing what Bruno & Marc
> suggested and run sysupgrade. Thanks to them for the advice.

BTW, why do you want to run -current?
There are only 2 real reasons to do that
1: You HAVE to (for various reasons)
2: You want to help with development and test things. This is a great reason, 
but
you better be prepared for a lot of work. Know what you are doing and file bug 
reports.
Else you won't be a whole lot of actual help.

If these don't apply then you might be better off just running Release.
Not trying to be an A hole here. Just giving you heads up of what is expected of
you if you run -current.
Good luck

Re: Installing OpenBSD -current snapshots

[Bodie]

On 29.11.2019 08:45, Clay Daniels wrote:

Another question. I know I need to write the boot file to the usb drive
thus:
# dd if=install66.fs of=/dev/da0 bs=1M conv=sync
But can I just use plain old "cp base66.tgz /mnt" etc for the other 
files?




Sounds like you are rushing too quickly and too much being used to
wrong approach learned on Linux.

How about to start here first:

https://www.openbsd.org/faq/faq4.html

then:

https://www.openbsd.org/faq/faq1.html#ManPages
https://www.openbsd.org/faq/faq10.html

followed by anything more you will need.

Trust me, you will be surprised how many questions will not need to be
asked at all in future ;-)

On Fri, Nov 29, 2019 at 1:26 AM Clay Daniels 


wrote:

Nick, thanks for straightening me out about what is actually going on 
here
with the install. I see that there is now a fresh snapshot with 
today's
date, not the one I downloaded and ran yesterday. This might tend to 
keep
one busy. I'm not sure I would not be better off doing what Bruno & 
Marc

suggested and run sysupgrade. Thanks to them for the advice.

If I do decide to put the filesets on the the install thumbdrive, I 
see a
total of 26 files in the directory. Obviously some are not necessary 
like

the floppy or both the .fs & .iso (just one needed), nor the test
instructions, etc.
So which files do I REALLY need on my usb thumbdrive to get a complete
install, x included?

Please excuse the "top-posting". That's the only way my darn google 
mail

does reply's. Kind of irritating, to me and the reader too.

Clay




On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 


wrote:


On 2019-11-27 21:29, Edgar Pettijohn wrote:
> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> I have successfully installed OpenBSD 6.6 release and would like to
give
>> the Current Snapshots a try. I went to a mirror, and to:
>>
>> Index of /pub/OpenBSD/snapshots/amd64/
>>
>> I saw install66.fs (probably for usb memstick) and install66.iso
(surely
>> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> thumbdrive, and it starts the install. When i get into the install it
asks
>> where are the file sets? Humm, maybe it gets these online and it tries
to
>> do this but no luck. It was late last night, and I checked to see if
it had
>> written anything to my disk, which it had not, and went to bed. This
>> evening I'm looking a bit deeper at the snapshot directory and I
suspect I
>> need to provide the install with base66.tzg at ~239Mb.

NO!

[snip misleading stuff]
> I noticed this also, but hadn't had time to figure out if I had messed
up or
> the installer had. As a general rule I assume its me that messed up.
Its odd
> if you mount the install66.fs you can see the pub/amd64 directory, but
during
> installation it can't seem to find the directory regardless of what I
have
> tried.
>
> Edgar

First of all...nothing at all to do about snapshots -- the OpenBSD
installation process has remained amazingly stable over the last 20
years.
New options here and there, but overall, very similar.  Unless 
something

changed in the last few days, installing a snapshot is identical to
installing 6.6.

The installXX.iso and installXX.fs are complete, stand-alone 
installation
kits.  Everything you need is on them.  You can boot from them, and 
all

the installation files are right there.  Look Ma!  No network needed!
...well...unfortunately there is the issue of firmware files, which 
are
legally not feasible to put on the install media, so you will need 
network

for most machines eventually.  But let's ignore that for now. :)

Once the system has booted on the install kernel, you have three 
devices

you are working with:
1) the install kernel's internal "RAM disk" that is part of bsd.rd 
which

  you booted from,
2) your target disk
3) the USB drive with the install files on it.

The reason you can't see the install files on the USB stick from the
install kernel is they aren't mounted.  You didn't boot from the 
entire
USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just 
happened
to be sitting on the big USB stick...but as far as bsd.rd is 
concerned,

the USB stick isn't part of the booted environment (yet).

You aren't booting from a "Live Media".  You are booting from a tiny
kernel
with a built in file system that's sitting on the same inert file 
system

as
the install files.

Read that over and over until you understand what I'm saying, not 
what you
are assuming is going on.  It's really important to understand.  It's 
very
different from many Linux installation processes -- you are running 
off a
file only 10MB in size which is now completely in RAM.  That file 
JUST

HAPPENED to come from a USB stick that's much bigger.

So, when it comes to answering where your install files are, they are 
on
a disk, but it's NOT a mounted disk.  It's on your USB drive that's 
not
mounted now, and won't be after installation, but could be useful 
shortly.


Your next problem is...WHICH 

Re: Installing OpenBSD -current snapshots

[Peter N. M. Hansteen]

On Fri, Nov 29, 2019 at 01:45:37AM -0600, Clay Daniels wrote:
> Another question. I know I need to write the boot file to the usb drive
> thus:
> # dd if=install66.fs of=/dev/da0 bs=1M conv=sync
> But can I just use plain old "cp base66.tgz /mnt" etc for the other files?

the installnn.fs image will have the file sets in there already. No need to 
copy.

- Peter

-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Another question. I know I need to write the boot file to the usb drive
thus:
# dd if=install66.fs of=/dev/da0 bs=1M conv=sync
But can I just use plain old "cp base66.tgz /mnt" etc for the other files?

On Fri, Nov 29, 2019 at 1:26 AM Clay Daniels 
wrote:

> Nick, thanks for straightening me out about what is actually going on here
> with the install. I see that there is now a fresh snapshot with today's
> date, not the one I downloaded and ran yesterday. This might tend to keep
> one busy. I'm not sure I would not be better off doing what Bruno & Marc
> suggested and run sysupgrade. Thanks to them for the advice.
>
> If I do decide to put the filesets on the the install thumbdrive, I see a
> total of 26 files in the directory. Obviously some are not necessary like
> the floppy or both the .fs & .iso (just one needed), nor the test
> instructions, etc.
> So which files do I REALLY need on my usb thumbdrive to get a complete
> install, x included?
>
> Please excuse the "top-posting". That's the only way my darn google mail
> does reply's. Kind of irritating, to me and the reader too.
>
> Clay
>
>
>
>
> On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 
> wrote:
>
>> On 2019-11-27 21:29, Edgar Pettijohn wrote:
>> > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> >> I have successfully installed OpenBSD 6.6 release and would like to
>> give
>> >> the Current Snapshots a try. I went to a mirror, and to:
>> >>
>> >> Index of /pub/OpenBSD/snapshots/amd64/
>> >>
>> >> I saw install66.fs (probably for usb memstick) and install66.iso
>> (surely
>> >> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> >> thumbdrive, and it starts the install. When i get into the install it
>> asks
>> >> where are the file sets? Humm, maybe it gets these online and it tries
>> to
>> >> do this but no luck. It was late last night, and I checked to see if
>> it had
>> >> written anything to my disk, which it had not, and went to bed. This
>> >> evening I'm looking a bit deeper at the snapshot directory and I
>> suspect I
>> >> need to provide the install with base66.tzg at ~239Mb.
>>
>> NO!
>>
>> [snip misleading stuff]
>> > I noticed this also, but hadn't had time to figure out if I had messed
>> up or
>> > the installer had. As a general rule I assume its me that messed up.
>> Its odd
>> > if you mount the install66.fs you can see the pub/amd64 directory, but
>> during
>> > installation it can't seem to find the directory regardless of what I
>> have
>> > tried.
>> >
>> > Edgar
>>
>> First of all...nothing at all to do about snapshots -- the OpenBSD
>> installation process has remained amazingly stable over the last 20
>> years.
>> New options here and there, but overall, very similar.  Unless something
>> changed in the last few days, installing a snapshot is identical to
>> installing 6.6.
>>
>> The installXX.iso and installXX.fs are complete, stand-alone installation
>> kits.  Everything you need is on them.  You can boot from them, and all
>> the installation files are right there.  Look Ma!  No network needed!
>> ...well...unfortunately there is the issue of firmware files, which are
>> legally not feasible to put on the install media, so you will need network
>> for most machines eventually.  But let's ignore that for now. :)
>>
>> Once the system has booted on the install kernel, you have three devices
>> you are working with:
>> 1) the install kernel's internal "RAM disk" that is part of bsd.rd which
>>   you booted from,
>> 2) your target disk
>> 3) the USB drive with the install files on it.
>>
>> The reason you can't see the install files on the USB stick from the
>> install kernel is they aren't mounted.  You didn't boot from the entire
>> USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
>> to be sitting on the big USB stick...but as far as bsd.rd is concerned,
>> the USB stick isn't part of the booted environment (yet).
>>
>> You aren't booting from a "Live Media".  You are booting from a tiny
>> kernel
>> with a built in file system that's sitting on the same inert file system
>> as
>> the install files.
>>
>> Read that over and over until you understand what I'm saying, not what you
>> are assuming is going on.  It's really important to understand.  It's very
>> different from many Linux installation processes -- you are running off a
>> file only 10MB in size which is now completely in RAM.  That file JUST
>> HAPPENED to come from a USB stick that's much bigger.
>>
>> So, when it comes to answering where your install files are, they are on
>> a disk, but it's NOT a mounted disk.  It's on your USB drive that's not
>> mounted now, and won't be after installation, but could be useful shortly.
>>
>> Your next problem is...WHICH disk?  On a minimal system, it would be the
>> next sd device after your install disk -- assuming you are installing to
>> sd0, your USB stick might be sd1.  HOWEVER, if you have a flash media
>> reader
>> on your system, who knows where 

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Nick, thanks for straightening me out about what is actually going on here
with the install. I see that there is now a fresh snapshot with today's
date, not the one I downloaded and ran yesterday. This might tend to keep
one busy. I'm not sure I would not be better off doing what Bruno & Marc
suggested and run sysupgrade. Thanks to them for the advice.

If I do decide to put the filesets on the the install thumbdrive, I see a
total of 26 files in the directory. Obviously some are not necessary like
the floppy or both the .fs & .iso (just one needed), nor the test
instructions, etc.
So which files do I REALLY need on my usb thumbdrive to get a complete
install, x included?

Please excuse the "top-posting". That's the only way my darn google mail
does reply's. Kind of irritating, to me and the reader too.

Clay




On Thu, Nov 28, 2019 at 12:34 PM Nick Holland 
wrote:

> On 2019-11-27 21:29, Edgar Pettijohn wrote:
> > On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> >> I have successfully installed OpenBSD 6.6 release and would like to give
> >> the Current Snapshots a try. I went to a mirror, and to:
> >>
> >> Index of /pub/OpenBSD/snapshots/amd64/
> >>
> >> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> >> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> >> thumbdrive, and it starts the install. When i get into the install it
> asks
> >> where are the file sets? Humm, maybe it gets these online and it tries
> to
> >> do this but no luck. It was late last night, and I checked to see if it
> had
> >> written anything to my disk, which it had not, and went to bed. This
> >> evening I'm looking a bit deeper at the snapshot directory and I
> suspect I
> >> need to provide the install with base66.tzg at ~239Mb.
>
> NO!
>
> [snip misleading stuff]
> > I noticed this also, but hadn't had time to figure out if I had messed
> up or
> > the installer had. As a general rule I assume its me that messed up. Its
> odd
> > if you mount the install66.fs you can see the pub/amd64 directory, but
> during
> > installation it can't seem to find the directory regardless of what I
> have
> > tried.
> >
> > Edgar
>
> First of all...nothing at all to do about snapshots -- the OpenBSD
> installation process has remained amazingly stable over the last 20
> years.
> New options here and there, but overall, very similar.  Unless something
> changed in the last few days, installing a snapshot is identical to
> installing 6.6.
>
> The installXX.iso and installXX.fs are complete, stand-alone installation
> kits.  Everything you need is on them.  You can boot from them, and all
> the installation files are right there.  Look Ma!  No network needed!
> ...well...unfortunately there is the issue of firmware files, which are
> legally not feasible to put on the install media, so you will need network
> for most machines eventually.  But let's ignore that for now. :)
>
> Once the system has booted on the install kernel, you have three devices
> you are working with:
> 1) the install kernel's internal "RAM disk" that is part of bsd.rd which
>   you booted from,
> 2) your target disk
> 3) the USB drive with the install files on it.
>
> The reason you can't see the install files on the USB stick from the
> install kernel is they aren't mounted.  You didn't boot from the entire
> USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
> to be sitting on the big USB stick...but as far as bsd.rd is concerned,
> the USB stick isn't part of the booted environment (yet).
>
> You aren't booting from a "Live Media".  You are booting from a tiny kernel
> with a built in file system that's sitting on the same inert file system as
> the install files.
>
> Read that over and over until you understand what I'm saying, not what you
> are assuming is going on.  It's really important to understand.  It's very
> different from many Linux installation processes -- you are running off a
> file only 10MB in size which is now completely in RAM.  That file JUST
> HAPPENED to come from a USB stick that's much bigger.
>
> So, when it comes to answering where your install files are, they are on
> a disk, but it's NOT a mounted disk.  It's on your USB drive that's not
> mounted now, and won't be after installation, but could be useful shortly.
>
> Your next problem is...WHICH disk?  On a minimal system, it would be the
> next sd device after your install disk -- assuming you are installing to
> sd0, your USB stick might be sd1.  HOWEVER, if you have a flash media
> reader
> on your system, who knows where it is.  One trick would be to unplug your
> USB drive and plug it back in and look at the white-on-blue console message
> that come up at you.  Yes, you are unpluging your boot device, sounds bad,
> but read what I wrote earlier, it's no longer using that -- the boot has
> completed, and it's running from RAM now, it's completely ignoring that
> USB drive.  So let's say you do this and 

Re: Installing OpenBSD -current snapshots

[Nick Holland]

On 2019-11-27 21:29, Edgar Pettijohn wrote:
> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
>> I have successfully installed OpenBSD 6.6 release and would like to give
>> the Current Snapshots a try. I went to a mirror, and to:
>> 
>> Index of /pub/OpenBSD/snapshots/amd64/
>> 
>> I saw install66.fs (probably for usb memstick) and install66.iso (surely
>> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
>> thumbdrive, and it starts the install. When i get into the install it asks
>> where are the file sets? Humm, maybe it gets these online and it tries to
>> do this but no luck. It was late last night, and I checked to see if it had
>> written anything to my disk, which it had not, and went to bed. This
>> evening I'm looking a bit deeper at the snapshot directory and I suspect I
>> need to provide the install with base66.tzg at ~239Mb.

NO!

[snip misleading stuff]
> I noticed this also, but hadn't had time to figure out if I had messed up or
> the installer had. As a general rule I assume its me that messed up. Its odd
> if you mount the install66.fs you can see the pub/amd64 directory, but during
> installation it can't seem to find the directory regardless of what I have 
> tried.
> 
> Edgar

First of all...nothing at all to do about snapshots -- the OpenBSD
installation process has remained amazingly stable over the last 20 years.  
New options here and there, but overall, very similar.  Unless something
changed in the last few days, installing a snapshot is identical to
installing 6.6.

The installXX.iso and installXX.fs are complete, stand-alone installation
kits.  Everything you need is on them.  You can boot from them, and all
the installation files are right there.  Look Ma!  No network needed!
...well...unfortunately there is the issue of firmware files, which are
legally not feasible to put on the install media, so you will need network
for most machines eventually.  But let's ignore that for now. :)

Once the system has booted on the install kernel, you have three devices
you are working with:
1) the install kernel's internal "RAM disk" that is part of bsd.rd which
  you booted from,
2) your target disk 
3) the USB drive with the install files on it.

The reason you can't see the install files on the USB stick from the
install kernel is they aren't mounted.  You didn't boot from the entire
USB stick, you booted from ONE TINY LITTLE bsd.rd file, that just happened
to be sitting on the big USB stick...but as far as bsd.rd is concerned,
the USB stick isn't part of the booted environment (yet).

You aren't booting from a "Live Media".  You are booting from a tiny kernel
with a built in file system that's sitting on the same inert file system as
the install files.

Read that over and over until you understand what I'm saying, not what you
are assuming is going on.  It's really important to understand.  It's very
different from many Linux installation processes -- you are running off a
file only 10MB in size which is now completely in RAM.  That file JUST
HAPPENED to come from a USB stick that's much bigger.

So, when it comes to answering where your install files are, they are on
a disk, but it's NOT a mounted disk.  It's on your USB drive that's not
mounted now, and won't be after installation, but could be useful shortly.

Your next problem is...WHICH disk?  On a minimal system, it would be the
next sd device after your install disk -- assuming you are installing to
sd0, your USB stick might be sd1.  HOWEVER, if you have a flash media reader
on your system, who knows where it is.  One trick would be to unplug your
USB drive and plug it back in and look at the white-on-blue console message
that come up at you.  Yes, you are unpluging your boot device, sounds bad,
but read what I wrote earlier, it's no longer using that -- the boot has
completed, and it's running from RAM now, it's completely ignoring that
USB drive.  So let's say you do this and you see it's sd4.  Tell the
installer the files are coming from a file system not currently mounted
and when it asks, tell it "sd4"

Nick.

Re: Installing OpenBSD -current snapshots

[Marc Espie]

On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:

Just run sysupgrade -s

Done.

Re: Installing OpenBSD -current snapshots

[Edgar Pettijohn]

On Nov 28, 2019 2:15 AM, Bruno Flueckiger  wrote:
>
> On 27.11., Clay Daniels wrote:
> > I have successfully installed OpenBSD 6.6 release and would like to give
> > the Current Snapshots a try. I went to a mirror, and to:
> >
> > Index of /pub/OpenBSD/snapshots/amd64/
> >
> > I saw install66.fs (probably for usb memstick) and install66.iso (surely
> > for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> > thumbdrive, and it starts the install. When i get into the install it asks
> > where are the file sets? Humm, maybe it gets these online and it tries to
> > do this but no luck. It was late last night, and I checked to see if it had
> > written anything to my disk, which it had not, and went to bed. This
> > evening I'm looking a bit deeper at the snapshot directory and I suspect I
> > need to provide the install with base66.tzg at ~239Mb.
> >
> > My question now is after downloading the base, do I need to un-tar it, and
> > how to I provide it to the install? I wrote the install66.fs to the usb
> > with the dd command. Not clear to me how to either manually copy the base
> > file set to the usb, or maybe leave it on an accessible directory on my
> > machine. Any help would be appreciated.
> >
> > Clay Daniels
>
> I would recommend using sysupgrade(8) with the parameter -s to you.
>
> Cheers,
> Bruno
>

It's a fresh install unfortunately.

Re: Installing OpenBSD -current snapshots

[Bruno Flueckiger]

On 27.11., Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
>
> Index of /pub/OpenBSD/snapshots/amd64/
>
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> thumbdrive, and it starts the install. When i get into the install it asks
> where are the file sets? Humm, maybe it gets these online and it tries to
> do this but no luck. It was late last night, and I checked to see if it had
> written anything to my disk, which it had not, and went to bed. This
> evening I'm looking a bit deeper at the snapshot directory and I suspect I
> need to provide the install with base66.tzg at ~239Mb.
>
> My question now is after downloading the base, do I need to un-tar it, and
> how to I provide it to the install? I wrote the install66.fs to the usb
> with the dd command. Not clear to me how to either manually copy the base
> file set to the usb, or maybe leave it on an accessible directory on my
> machine. Any help would be appreciated.
>
> Clay Daniels

I would recommend using sysupgrade(8) with the parameter -s to you.

Cheers,
Bruno

Re: Installing OpenBSD -current snapshots

[Robert Klein]

On Wed, 27 Nov 2019 20:29:27 -0600
Edgar Pettijohn  wrote:

> On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> > I have successfully installed OpenBSD 6.6 release and would like to
> > give the Current Snapshots a try. I went to a mirror, and to:
> > 
> > Index of /pub/OpenBSD/snapshots/amd64/
> > 
> > I saw install66.fs (probably for usb memstick) and install66.iso
> > (surely for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote
> > it to a usb thumbdrive, and it starts the install. When i get into
> > the install it asks where are the file sets? Humm, maybe it gets
> > these online and it tries to do this but no luck. It was late last
> > night, and I checked to see if it had written anything to my disk,
> > which it had not, and went to bed. This evening I'm looking a bit
> > deeper at the snapshot directory and I suspect I need to provide
> > the install with base66.tzg at ~239Mb.
> > 
> > My question now is after downloading the base, do I need to un-tar
> > it, and how to I provide it to the install? I wrote the
> > install66.fs to the usb with the dd command. Not clear to me how to
> > either manually copy the base file set to the usb, or maybe leave
> > it on an accessible directory on my machine. Any help would be
> > appreciated.
> > 
> > Clay Daniels  
> 
> I noticed this also, but hadn't had time to figure out if I had
> messed up or the installer had. As a general rule I assume its me
> that messed up. Its odd if you mount the install66.fs you can see the
> pub/amd64 directory, but during installation it can't seem to find
> the directory regardless of what I have tried.
> 
> Edgar
> 

You'll have to select “installation set is on disk” and “not mounted”.

Best regards
Robert

Re: Installing OpenBSD -current snapshots

[Edgar Pettijohn]

On Wed, Nov 27, 2019 at 08:05:30PM -0600, Clay Daniels wrote:
> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
> 
> Index of /pub/OpenBSD/snapshots/amd64/
> 
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> thumbdrive, and it starts the install. When i get into the install it asks
> where are the file sets? Humm, maybe it gets these online and it tries to
> do this but no luck. It was late last night, and I checked to see if it had
> written anything to my disk, which it had not, and went to bed. This
> evening I'm looking a bit deeper at the snapshot directory and I suspect I
> need to provide the install with base66.tzg at ~239Mb.
> 
> My question now is after downloading the base, do I need to un-tar it, and
> how to I provide it to the install? I wrote the install66.fs to the usb
> with the dd command. Not clear to me how to either manually copy the base
> file set to the usb, or maybe leave it on an accessible directory on my
> machine. Any help would be appreciated.
> 
> Clay Daniels

I noticed this also, but hadn't had time to figure out if I had messed up or
the installer had. As a general rule I assume its me that messed up. Its odd
if you mount the install66.fs you can see the pub/amd64 directory, but during
installation it can't seem to find the directory regardless of what I have 
tried.

Edgar

Re: Installing OpenBSD -current snapshots

[Clay Daniels]

Never mind, I found the instructions the the same mirror directory,in a
plain text file called "INSTALL.amd64".

Forgive the dummy here,

Clay

On Wed, Nov 27, 2019 at 8:05 PM Clay Daniels 
wrote:

> I have successfully installed OpenBSD 6.6 release and would like to give
> the Current Snapshots a try. I went to a mirror, and to:
>
> Index of /pub/OpenBSD/snapshots/amd64/
>
> I saw install66.fs (probably for usb memstick) and install66.iso (surely
> for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
> thumbdrive, and it starts the install. When i get into the install it asks
> where are the file sets? Humm, maybe it gets these online and it tries to
> do this but no luck. It was late last night, and I checked to see if it had
> written anything to my disk, which it had not, and went to bed. This
> evening I'm looking a bit deeper at the snapshot directory and I suspect I
> need to provide the install with base66.tzg at ~239Mb.
>
> My question now is after downloading the base, do I need to un-tar it, and
> how to I provide it to the install? I wrote the install66.fs to the usb
> with the dd command. Not clear to me how to either manually copy the base
> file set to the usb, or maybe leave it on an accessible directory on my
> machine. Any help would be appreciated.
>
> Clay Daniels
>

Installing OpenBSD -current snapshots

[Clay Daniels]

I have successfully installed OpenBSD 6.6 release and would like to give
the Current Snapshots a try. I went to a mirror, and to:

Index of /pub/OpenBSD/snapshots/amd64/

I saw install66.fs (probably for usb memstick) and install66.iso (surely
for a cd/dvd) at ~450Mb. I picked the install66.fs, wrote it to a usb
thumbdrive, and it starts the install. When i get into the install it asks
where are the file sets? Humm, maybe it gets these online and it tries to
do this but no luck. It was late last night, and I checked to see if it had
written anything to my disk, which it had not, and went to bed. This
evening I'm looking a bit deeper at the snapshot directory and I suspect I
need to provide the install with base66.tzg at ~239Mb.

My question now is after downloading the base, do I need to un-tar it, and
how to I provide it to the install? I wrote the install66.fs to the usb
with the dd command. Not clear to me how to either manually copy the base
file set to the usb, or maybe leave it on an accessible directory on my
machine. Any help would be appreciated.

Clay Daniels

Re: Blank screen after installing OpenBSD 6.5 - solved

[oxstone]

Hello,

I reinstalled using the OpenBSD/amd64 install65.fs file.

It works. =)

Thank you very much to all of you for your help !

Nicolas.


> Gesendet: Mittwoch, 17. Juli 2019 um 13:32 Uhr
> Von: "Stefan Sperling" 
> An: oxst...@gmx.net
> Cc: misc@openbsd.org
> Betreff: Re: Blank screen after installing OpenBSD 6.5
>
> On Wed, Jul 17, 2019 at 01:15:26PM +0200, oxst...@gmx.net wrote:
> > Hello,
> > 
> > I recently installed OpenBSD 6.5 on an i386 router.
> > The intallation process went fine. However, I got a black screen after 
> > rebooting.
> > 
> > I tried opening a SSH session, but the computer doesn't reply.
> > 
> > The screen is attached using a VGA cable. The computer send a signal over 
> > that cable. If I detach it from the router, the screen turns off. If I plug 
> > it back, the screen turns on (but nothing is displayed).
> > 
> > I send you the dmesg output. I took pictures of the output and used an OCR 
> > to convert them to text format.
> > 
> > Thank you !
> 
> Your CPU should be capable of running OpenBSD/amd64.
> 
> Please try to install that instead of OpenBSD/i386.
>  
> > OpenBSD 6.5 (RAMDISC_CD) #1326: Sat Apr 13 15:26:51 MDT 2019
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISC_CD
> > real mem  = 2029793280 (1935MB)
> > avail mem = 1983680512 (1891MB)
> > mainbus0 at root
> > bios0 at mainbus0: date 04/13/12, SMBIOS rev. 2.7 @ 0xeb530 (73 entries)
> > bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016
> > bios0: INTEL Corporation ChiefRiver
> > acpi0 at bios0: rev 2
> > acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT
> > acpimadt0 at acpi0 addr 0xfee0: PC—AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz ("Genuinelntel" 686-class) 
> > 1.80 GH
> > z, 06-3a-09
> > 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
> > .EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NX
> > E,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SHEP,ERMS,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> 
>

Re: Blank screen after installing OpenBSD 6.5

[Jonathan Gray]

On Wed, Jul 17, 2019 at 01:32:37PM +0200, Stefan Sperling wrote:
> On Wed, Jul 17, 2019 at 01:15:26PM +0200, oxst...@gmx.net wrote:
> > Hello,
> > 
> > I recently installed OpenBSD 6.5 on an i386 router.
> > The intallation process went fine. However, I got a black screen after 
> > rebooting.
> > 
> > I tried opening a SSH session, but the computer doesn't reply.
> > 
> > The screen is attached using a VGA cable. The computer send a signal over 
> > that cable. If I detach it from the router, the screen turns off. If I plug 
> > it back, the screen turns on (but nothing is displayed).
> > 
> > I send you the dmesg output. I took pictures of the output and used an OCR 
> > to convert them to text format.
> > 
> > Thank you !
> 
> Your CPU should be capable of running OpenBSD/amd64.
> 
> Please try to install that instead of OpenBSD/i386.

Or an i386 snapshot.  There were known problems running the linux 4.4 based
drm that was part of OpenBSD 6.5 on ivy bridge with i386 that don't show up
with the linux 4.19 based drm we have in -current.

>  
> > OpenBSD 6.5 (RAMDISC_CD) #1326: Sat Apr 13 15:26:51 MDT 2019
> > dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISC_CD
> > real mem  = 2029793280 (1935MB)
> > avail mem = 1983680512 (1891MB)
> > mainbus0 at root
> > bios0 at mainbus0: date 04/13/12, SMBIOS rev. 2.7 @ 0xeb530 (73 entries)
> > bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016
> > bios0: INTEL Corporation ChiefRiver
> > acpi0 at bios0: rev 2
> > acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT
> > acpimadt0 at acpi0 addr 0xfee0: PC???AT compat
> > cpu0 at mainbus0: apid 0 (boot processor)
> > cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz ("Genuinelntel" 686-class) 
> > 1.80 GH
> > z, 06-3a-09
> > 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
> > .EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NX
> > E,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SHEP,ERMS,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> 

Re: Blank screen after installing OpenBSD 6.5

[Stefan Sperling]

On Wed, Jul 17, 2019 at 01:15:26PM +0200, oxst...@gmx.net wrote:
> Hello,
> 
> I recently installed OpenBSD 6.5 on an i386 router.
> The intallation process went fine. However, I got a black screen after 
> rebooting.
> 
> I tried opening a SSH session, but the computer doesn't reply.
> 
> The screen is attached using a VGA cable. The computer send a signal over 
> that cable. If I detach it from the router, the screen turns off. If I plug 
> it back, the screen turns on (but nothing is displayed).
> 
> I send you the dmesg output. I took pictures of the output and used an OCR to 
> convert them to text format.
> 
> Thank you !

Your CPU should be capable of running OpenBSD/amd64.

Please try to install that instead of OpenBSD/i386.
 
> OpenBSD 6.5 (RAMDISC_CD) #1326: Sat Apr 13 15:26:51 MDT 2019
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISC_CD
> real mem  = 2029793280 (1935MB)
> avail mem = 1983680512 (1891MB)
> mainbus0 at root
> bios0 at mainbus0: date 04/13/12, SMBIOS rev. 2.7 @ 0xeb530 (73 entries)
> bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016
> bios0: INTEL Corporation ChiefRiver
> acpi0 at bios0: rev 2
> acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT
> acpimadt0 at acpi0 addr 0xfee0: PC—AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz ("Genuinelntel" 686-class) 1.80 
> GH
> z, 06-3a-09
> 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
> .EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NX
> E,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SHEP,ERMS,SENSOR,ARAT,XSAVEOPT,MELTDOWN

Re: Blank screen after installing OpenBSD 6.5

[Tom Smyth]

have a look at man boot ...
you need to set tty to the correct serial port com0 com1 etc...
and you need to set the Baud rate... spec .. depending rotuer baud settings
115200  and N 8 1 ...

On Wed, 17 Jul 2019 at 12:22,  wrote:

> Hello,
>
> I recently installed OpenBSD 6.5 on an i386 router.
> The intallation process went fine. However, I got a black screen after
> rebooting.
>
> I tried opening a SSH session, but the computer doesn't reply.
>
> The screen is attached using a VGA cable. The computer send a signal over
> that cable. If I detach it from the router, the screen turns off. If I plug
> it back, the screen turns on (but nothing is displayed).
>
> I send you the dmesg output. I took pictures of the output and used an OCR
> to convert them to text format.
>
> Thank you !
>
> OpenBSD 6.5 (RAMDISC_CD) #1326: Sat Apr 13 15:26:51 MDT 2019
> dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISC_CD
> real mem  = 2029793280 (1935MB)
> avail mem = 1983680512 (1891MB)
> mainbus0 at root
> bios0 at mainbus0: date 04/13/12, SMBIOS rev. 2.7 @ 0xeb530 (73 entries)
> bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016
> bios0: INTEL Corporation ChiefRiver
> acpi0 at bios0: rev 2
> acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT
> acpimadt0 at acpi0 addr 0xfee0: PC—AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz ("Genuinelntel" 686-class)
> 1.80 GH
> z, 06-3a-09
> 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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
>
> .EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NX
>
> E,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SHEP,ERMS,SENSOR,ARAT,XSAVEOPT,MELTDOWN
> cpu0: apic clock running at 99MHz
> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
> cpu at mainbus0: not configured
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> acpiprt0 at acpi0: bus (PCI0)
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (P0P1)
> acpiprt2 at acpi0: bus 1 (RP01)
> acpiprt3 at acpi0: bus 2 (RP02)
> acpiprt4 at acpi0: bus 3 (RP03)
> acpiprt5 at acpi0: bus 4 (RP04)
> acpiprt6 at acpi0: bus 5 (RP05)
> acpiprt7 at acpi0: bus 6 (RP06)
> acpiprt8 at acpi0: bus -1 (RP07)
> acpiprt9 at acpi0: bus -1 (RP08)
> acpiprt10 at acpi0: bus -1 (PEG0)
> acpiprt11 at acpi0: bus -1 (PEG1)
> acpiprt12 at acpi0: bus -1 (PEG2)
> acpiprt13 at acpi0: bus -1 (PEG3)
> acpiec0 at acpi0: not present
> acpicpu at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpipwrres at acpi0 not configured
> acpitz at acpi0 not configured
> acpitz at acpi0 not configured
> "PNP0A08" at acpi0 not configured
> acpicmos0 at acpi0
> "PNP0C0C" at acpi0 not configured
> "PNP0C0B" at acpi0 not configured
> "PNP0C0B" at acpi0 not configured
> "PNP0C0B" at acpi0 not configured
> "PNP0C0B" at acpi0 not configured
> "PNP0C0B" at acpi0 not configured
> bios0: ROM list: 0xc/0xf000
> pci at mainbus0 bus 0: configuration mode 1 (bios)
> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 2500" rev 0x09
> wsdisplay0 at vgal mux 1: console (80x25, vt100 emulation)
> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI
> 1.0
> usb0 at xhciO: USB revision 3.0
> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev
> 3.00/1.00 ad
> dr 1
> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int
> 16
> usbl at ehci0: USB revision 2.0
> uhubl at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev
> 2.00/1.00 ad
> dr 1
> "Intel 7 Series HD Audio" rev 0x04 at pcio dev 27 function 0 not configured
> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: apic 2 int
> 16
> pci1 at ppb0 bus 1
> em0 at pci1 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address
> 0c:e8:5c:68:c
> e:88
> ppb1 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 17
> pci2 at ppb1 bus 2
> em1 at pci2 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address
> 0c:e8:5c:68:c
> e:89
> ppb2 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 18
> pci3 at ppb2 bus 3
> em2 at pci3 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address
> 0c:e8:5c:68:c
> e:8a
> ppb3 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 19
> pci4 at ppb3 bus 4
> em3 at pci4 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address
> 0c:e8:5c:68:c
> e:8b
> ppb4 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 16
> pci5 at ppb4 bus 5
> em4 at pci5 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address
> 0c:e8:5c:68:c
> e:8c
> ppb5 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 17
> pci6 at ppb5 

Blank screen after installing OpenBSD 6.5

[oxstone]

Hello,

I recently installed OpenBSD 6.5 on an i386 router.
The intallation process went fine. However, I got a black screen after 
rebooting.

I tried opening a SSH session, but the computer doesn't reply.

The screen is attached using a VGA cable. The computer send a signal over that 
cable. If I detach it from the router, the screen turns off. If I plug it back, 
the screen turns on (but nothing is displayed).

I send you the dmesg output. I took pictures of the output and used an OCR to 
convert them to text format.

Thank you !

OpenBSD 6.5 (RAMDISC_CD) #1326: Sat Apr 13 15:26:51 MDT 2019
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/RAMDISC_CD
real mem  = 2029793280 (1935MB)
avail mem = 1983680512 (1891MB)
mainbus0 at root
bios0 at mainbus0: date 04/13/12, SMBIOS rev. 2.7 @ 0xeb530 (73 entries)
bios0: vendor American Megatrends Inc. version "4.6.5" date 07/10/2016
bios0: INTEL Corporation ChiefRiver
acpi0 at bios0: rev 2
acpi0: tables DSDT FACP APIC FPDT MCFG HPET SSDT SSDT
acpimadt0 at acpi0 addr 0xfee0: PC—AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) CPU 1037U @ 1.80GHz ("Genuinelntel" 686-class) 1.80 GH
z, 06-3a-09
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,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX
.EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,XSAVE,NX
E,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SHEP,ERMS,SENSOR,ARAT,XSAVEOPT,MELTDOWN
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus (PCI0)
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (P0P1)
acpiprt2 at acpi0: bus 1 (RP01)
acpiprt3 at acpi0: bus 2 (RP02)
acpiprt4 at acpi0: bus 3 (RP03)
acpiprt5 at acpi0: bus 4 (RP04)
acpiprt6 at acpi0: bus 5 (RP05)
acpiprt7 at acpi0: bus 6 (RP06)
acpiprt8 at acpi0: bus -1 (RP07)
acpiprt9 at acpi0: bus -1 (RP08)
acpiprt10 at acpi0: bus -1 (PEG0)
acpiprt11 at acpi0: bus -1 (PEG1)
acpiprt12 at acpi0: bus -1 (PEG2)
acpiprt13 at acpi0: bus -1 (PEG3)
acpiec0 at acpi0: not present
acpicpu at acpi0 not configured
acpipwrres at acpi0 not configured
acpipwrres at acpi0 not configured
acpipwrres at acpi0 not configured
acpipwrres at acpi0 not configured
acpipwrres at acpi0 not configured
acpitz at acpi0 not configured
acpitz at acpi0 not configured
"PNP0A08" at acpi0 not configured
acpicmos0 at acpi0
"PNP0C0C" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
"PNP0C0B" at acpi0 not configured
bios0: ROM list: 0xc/0xf000
pci at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09
vga1 at pci0 dev 2 function 0 "Intel HD Graphics 2500" rev 0x09
wsdisplay0 at vgal mux 1: console (80x25, vt100 emulation)
xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi, xHCI 1.0
usb0 at xhciO: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 ad
dr 1
"Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured
ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16
usbl at ehci0: USB revision 2.0
uhubl at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 ad
dr 1
"Intel 7 Series HD Audio" rev 0x04 at pcio dev 27 function 0 not configured
ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: apic 2 int 16
pci1 at ppb0 bus 1
em0 at pci1 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address 0c:e8:5c:68:c
e:88
ppb1 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 17
pci2 at ppb1 bus 2
em1 at pci2 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address 0c:e8:5c:68:c
e:89
ppb2 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 18
pci3 at ppb2 bus 3
em2 at pci3 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address 0c:e8:5c:68:c
e:8a
ppb3 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 19
pci4 at ppb3 bus 4
em3 at pci4 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address 0c:e8:5c:68:c
e:8b
ppb4 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 16
pci5 at ppb4 bus 5
em4 at pci5 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address 0c:e8:5c:68:c
e:8c
ppb5 at pci0 dev 28 function "Intel 7 Series PCIE" rev 0xc4: apic 2 int 17
pci6 at ppb5 bus 6
em5 at pci6 dev 0 function 0 "Intel 8258V" rev 0x00: msi, address 0c:e8:5c:68:c
e:8d
ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23
usb2 at ehci1: USB revision 2.0
uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 ad
dr 1
pcib0 at pci0 dev 31 function 0 "Intel HM76 LPC" rev 0x04
ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3
ahci0: port 0: 6.0Gb/s
scsibus0 at ahci0: 

Re: hardware security (was Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Joseph A Borg]

apparently the F-35 project sources motherboards for key instrumentation 
from China.

This is a new economic cold war. Do what you feel best but a big part of  
this is politics.

Maybe the list should qualify when a mail thread is verging on personal 
politics and out of strictly technical subject the list is supposed to handle.

regards

> On 16 Jun 2019, at 21:28, Luke A. Call  wrote:
> 
> And I think I read that Supermicro is moving production 
> out of China because of the perceptions of risk (and/or actual 
> risks) of sensitive electronics manufacturing there. 
> 
> Forgive/ignore if this question is excessive here, but I 
> wonder if anyone has knowledge or educated perspective to share 
> on this:  I have avoided Chinese products (like Lenovo) due to 
> government history/means/motive/opportunity to put in backdoors
> or things with which I might be less comfortable than the
> backdoors unfortunately inserted by someone else.  Just like I've 
> been favoring AMD due to Intel's track record and evident attitude.)
> Yes, the US government has been reported to waylay hardware 
> during shipping, etc., and Bruce Schneier and/or others
> have said the problem of vetting hardware is beyond
> the ability of individuals or most businesses, given the 
> extreme economic and technical complexity involved.  (And 
> I realize that suspicion can be carried too far, and cost/benefit 
> estimates can sometimes even favor less caution, but one has to
> choose whom to work with, given tradeoffs and an imperfect world.
> I know Theo has said in efffect that hardware security is not 
> a problem OBSD can address, and if that is the final answer, OK.)
> 
> But I wonder sometimes if anyone knows of a laptop &/or desktop
> vendor where the odds seem most favorable, maybe why you 
> think so, and where they are likely to work with OBSD. (System76, 
> librem, dell, small/local manufacturers)?  (My audio, video, and 
> battery needs are minimal, but *quiet* effective thermal management, &
> 16GB+ RAM are important, and reliability & compilation speed.)  
> AMD CPUs preferred, as going exotic sounds like more $ and 
> harder to get spare parts.  And I probably don't have the ability
> now or later to become expert at choosing many individual 
> components.  Thanks in advance.
> -- 
> Luke Call
> Things I want to say to many (a lightly-loading site):
> http://lukecall.net  (updated 2019-06-09)
> 
> 
> On 06-15 15:11, Stuart Henderson wrote:
>> On 2019-06-15, ms  wrote:
>>> There were some serious security issues with hardware and software from 
>>> Supermicro (espionage chips, firmware)
>> 
>> Assuming you mean the allegations in that Bloomberg piece, there was no
>> evidence found supporting them.
>> 
>> https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc
>> 
>> There are the usual problems with BMC security, cpu bugs, etc, but those
>> are by no means unique to supermicro.
>> 
>> 
> 

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[lists]

Sun, 16 Jun 2019 05:23:36 +0200 ms 
> "It looks like at least the reengineering of the firmware
> 
> and the analysis of the code could increase the security, to avoid 
> security wholes"
>  ^^

Your clock is off.  Wrong time is a serious reliability & security flaw.
Before you look for the security problems in firmware, fix obvious ones.

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Stuart Henderson]

On 2019-06-15, ms  wrote:
> https://www.golem.de/news/supermicro-diskussion-um-ueberwachungschips-1810-136965.html
>
> https://www.heise.de/security/meldung/Bericht-Winzige-Chips-spionierten-in-Cloud-Servern-von-Apple-und-Amazon-4181461.html

Those are based on the discredited Bloomberg piece I mentioned.

> Now a day backdors are already on the silicon level (inside chips). They 
> are declared as debugging interfaces..

You'll find that sort of crap whichever way you look.

hardware security (was Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Luke A. Call]

And I think I read that Supermicro is moving production 
out of China because of the perceptions of risk (and/or actual 
risks) of sensitive electronics manufacturing there. 

Forgive/ignore if this question is excessive here, but I 
wonder if anyone has knowledge or educated perspective to share 
on this:  I have avoided Chinese products (like Lenovo) due to 
government history/means/motive/opportunity to put in backdoors
or things with which I might be less comfortable than the
backdoors unfortunately inserted by someone else.  Just like I've 
been favoring AMD due to Intel's track record and evident attitude.)
Yes, the US government has been reported to waylay hardware 
during shipping, etc., and Bruce Schneier and/or others
have said the problem of vetting hardware is beyond
the ability of individuals or most businesses, given the 
extreme economic and technical complexity involved.  (And 
I realize that suspicion can be carried too far, and cost/benefit 
estimates can sometimes even favor less caution, but one has to
choose whom to work with, given tradeoffs and an imperfect world.
I know Theo has said in efffect that hardware security is not 
a problem OBSD can address, and if that is the final answer, OK.)

But I wonder sometimes if anyone knows of a laptop &/or desktop
vendor where the odds seem most favorable, maybe why you 
think so, and where they are likely to work with OBSD. (System76, 
librem, dell, small/local manufacturers)?  (My audio, video, and 
battery needs are minimal, but *quiet* effective thermal management, &
16GB+ RAM are important, and reliability & compilation speed.)  
AMD CPUs preferred, as going exotic sounds like more $ and 
harder to get spare parts.  And I probably don't have the ability
now or later to become expert at choosing many individual 
components.  Thanks in advance.
-- 
Luke Call
Things I want to say to many (a lightly-loading site):
http://lukecall.net  (updated 2019-06-09)


On 06-15 15:11, Stuart Henderson wrote:
> On 2019-06-15, ms  wrote:
> > There were some serious security issues with hardware and software from 
> > Supermicro (espionage chips, firmware)
> 
> Assuming you mean the allegations in that Bloomberg piece, there was no
> evidence found supporting them.
> 
> https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc
> 
> There are the usual problems with BMC security, cpu bugs, etc, but those
> are by no means unique to supermicro.
> 
> 

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Stuart Longland]

On 16/6/19 1:23 pm, ms wrote:
>>> Now a day backdors are already on the silicon level (inside chips). They
>>> are declared as debugging interfaces..
>> Must have happened around the time when school dropouts went to business.
> 
> What do you want to say? Do you have experience in chip design?

Do you design and make your own x86 chips?  Do you inspect the dies of
all off-the-shelf chips you buy?
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[ms]

I am sorry for NOT reading my content again before posting it, my fault.


On 16.06.19 06:35, li...@wrant.com wrote:

Sat, 15 Jun 2019 23:52:18 +0200 ms 

Now a day backdors are already on the silicon level (inside chips). They
are declared as debugging interfaces..

Must have happened around the time when school dropouts went to business.


What do you want to say? Do you have experience in chip design?

Probably not ..



It looks like at least the reengineering of the frimware an it is
analyzing of the code could increase security wholes

Wonderful day for some misspelled general Failure statements.. is it not?


"It looks like at least the reengineering of the firmware

and the analysis of the code could increase the security, to avoid 
security wholes"




I am curious if someone on this list had tried to do it and had achieved
helpfull results..

No, but if you need an English textbook, computers are not your strength.

Obviously you missed the topic of the thread and the hardware specifics..

Or at the least just try to say something OpenBSD related for any points.


The OpenBSD related point is, that people are using OpenBSD because of 
security and it does not really make sense to run OpenBSD on unsecure 
hardware / firmware.



Have you got it now?

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[lists]

Sat, 15 Jun 2019 23:52:18 +0200 ms 
> Now a day backdors are already on the silicon level (inside chips). They 
> are declared as debugging interfaces..

Must have happened around the time when school dropouts went to business.

> It looks like at least the reengineering of the frimware an it is 
> analyzing of the code could increase security wholes

Wonderful day for some misspelled general Failure statements.. is it not?

> I am curious if someone on this list had tried to do it and had achieved 
> helpfull results..

No, but if you need an English textbook, computers are not your strength.

Obviously you missed the topic of the thread and the hardware specifics..

Or at the least just try to say something OpenBSD related for any points.

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[ms]

https://www.golem.de/news/supermicro-diskussion-um-ueberwachungschips-1810-136965.html

https://www.heise.de/security/meldung/Bericht-Winzige-Chips-spionierten-in-Cloud-Servern-von-Apple-und-Amazon-4181461.html

Now a day backdors are already on the silicon level (inside chips). They 
are declared as debugging interfaces..



It looks like at least the reengineering of the frimware an it is 
analyzing of the code could increase security wholes


https://resources.infosecinstitute.com/reversing-firmware-part-1/#gref


I am curious if someone on this list had tried to do it and had achieved 
helpfull results..



On 15.06.19 17:11, Stuart Henderson wrote:

On 2019-06-15, ms  wrote:

There were some serious security issues with hardware and software from
Supermicro (espionage chips, firmware)

Assuming you mean the allegations in that Bloomberg piece, there was no
evidence found supporting them.

https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc

There are the usual problems with BMC security, cpu bugs, etc, but those
are by no means unique to supermicro.

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Patrick Dohman]

My understanding is that a well known linux vendor was disabling kernel ACPI 
APEI & EINJ parameter support by default.

"ACPI provides an error injection mechanism, EINJ, for debugging and testing
the ACPI Platform Error Interface (APEI) and other RAS features. If
supported by the firmware, ACPI specification 5.0 and later provide for a
way to specify a physical memory address to which to inject the error.

Injecting errors through EINJ can produce errors which to the platform are
indistinguishable from real hardware errors. This can have undesirable
side-effects, such as causing the platform to mark hardware as needing
replacement.

While it does not provide a method to load unauthenticated privileged code,
the effect of these errors may persist across reboots and affect trust in
the underlying hardware, so disable error injection through EINJ if
securelevel is set."

Regards
Patrick

> On Jun 15, 2019, at 3:02 AM, Richard Laysell  
> wrote:
> 
> 
> Hello,
> 
> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
> Atom CPU (Denverton).  The board boots but most devices are not
> detected because ACPI can't be enabled.
> 
> Does anyone know if this is likely to be supported at some point?
> 
> Full dmesg is below
> 
> OpenBSD 6.5 (RAMDISK_CD) #3: Sat Apr 13 14:55:38 MDT 2019
>dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17125621760 (16332MB)
> avail mem = 16602619904 (15833MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
> bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
> bios0: Supermicro Super Server
> acpi0 at bios0: rev 2, can't enable ACPI
> cpu0 at mainbus0: (uniprocessor)
> cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
> cpu0: 
> FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 2MB 64b/line 16-way L2 cache
> cpu0: cannot disable silicon debug
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> pci0 at mainbus0 bus 0
> 0:31:5: mem address conflict 0xfe01/0x1000
> pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11
> pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11
> vendor "Intel", unknown product 0x19a2 (class system subclass root complex 
> event, rev 0x11) at pci0 dev 5 function 0 not configured
> ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11
> pci1 at ppb0 bus 1
> vendor "Intel", unknown product 0x19e2 (class processor subclass 
> Co-processor, rev 0x11) at pci1 dev 0 function 0 not configured
> ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11
> pci3 at ppb2 bus 3
> ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11
> pci4 at ppb3 bus 4
> ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
> pci5 at ppb4 bus 5
> "ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, 
> rev 0x11) at pci0 dev 18 function 0 not configured
> ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 
> 0x11: unable to map interrupt
> ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 
> 0x11: unable to map interrupt
> xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 
> 0x11: couldn't map interrupt
> ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11
> pci6 at ppb5 bus 6
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 
> 0x11) at pci6 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 
> 0x11) at pci6 dev 0 function 1 not configured
> ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11
> pci7 at ppb6 bus 7
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 
> 0x11) at pci7 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 
> 0x11) at pci7 dev 0 function 1 not configured
> vendor "Intel", unknown product 0x19d3 (class communications subclass 
> miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured
> vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) 
> at pci0 dev 31 function 0 not configured
> vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, 
> rev 0x11) at pci0 dev 31 function 2 not 

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Stuart Henderson]

On 2019-06-15, ms  wrote:
> There were some serious security issues with hardware and software from 
> Supermicro (espionage chips, firmware)

Assuming you mean the allegations in that Bloomberg piece, there was no
evidence found supporting them.

https://hackaday.com/2019/05/14/what-happened-with-supermicro/ etc

There are the usual problems with BMC security, cpu bugs, etc, but those
are by no means unique to supermicro.

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[ms]

There were some serious security issues with hardware and software from 
Supermicro (espionage chips, firmware)


For me a NoGo!



On 15.06.19 12:52, Andrew Luke Nesbit wrote:

On 15/06/2019 10:36, Jonathan Gray wrote:

On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:

Hello,

I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
Atom CPU (Denverton).  The board boots but most devices are not
detected because ACPI can't be enabled.

Does anyone know if this is likely to be supported at some point?

Try a snapshot.  ACPI changes were made for a similiar machine
(Lanner NCA-1510) in May.

However there is no support for the integrated X553 Ethernet at the
moment.

Jonathan, thank you for the update.

Richard, I am in the market for one of these boards too, or some other
C3000 series model.  I'm a big fan of Supermicro's C2000 boards because
they are so versatile for low-power applications.  They are also
excellent home servers due to this and the correspondingly low heat and
noise.  Of course if you have a C2000 series board you would need to
ensure that it doesn't suffer from the notorious Erratum AVR.54 defect [1].

Please could you keep us updated re: your progress of getting OpenBSD
installed along with the support status of all devices?  If so this
would be greatly appreciated.  Thanks!!

[1] A little-known fact is that if you look through Intel's data sheets
and whitepapers you can find similar defects in the stepping errata for
other SoC's.  In my case I found an almost identical example in a recent
Celeron or Pentium J-series SoC.  To add to my disappointment, I later
discovered, entirely coincidentally, that it was used on the controller
boards for a model of Synology NAS that I was considering purchasing.

Andrew

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Richard Laysell]

On Sat, 15 Jun 2019 19:36:23 +1000
Jonathan Gray  wrote:

> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
> > 
> > Hello,
> > 
> > I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an
> > Intel Atom CPU (Denverton).  The board boots but most devices are
> > not detected because ACPI can't be enabled.
> > 
> > Does anyone know if this is likely to be supported at some point?  
> 
> Try a snapshot.  ACPI changes were made for a similiar machine
> (Lanner NCA-1510) in May.
> 
> However there is no support for the integrated X553 Ethernet at the
> moment.
> 

Thanks Jonathan.

For those interested the dmesg from the latest snapshot (2019-06-15) is
below.  Significant improvement, but (as Jonathan mentions) no Ethernet
as yet.

OpenBSD 6.5-current (RAMDISK_CD) #27: Fri Jun 14 22:24:30 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17125621760 (16332MB)
avail mem = 16602619904 (15833MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
bios0: Supermicro Super Server
acpi0 at bios0: ACPI 6.1
acpi0: tables DSDT FACP FPDT FIDT SPMI MCFG WDAT APIC BDAT HPET UEFI SSDT DMAR 
HEST BERT ERST EINJ WSMT
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 4 (boot processor)
cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
cpu0: 
FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 2MB 64b/line 16-way L2 cache
cpu0: cannot disable silicon debug
cpu0: apic clock running at 25MHz
cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
cpu at mainbus0: not configured
cpu at mainbus0: not configured
cpu at mainbus0: not configured
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 6 (VRP0)
acpiprt2 at acpi0: bus -1 (PEX0)
acpiprt3 at acpi0: bus 1 (VRP2)
acpiprt4 at acpi0: bus 7 (VRP1)
acpiprt5 at acpi0: bus 2 (PEX1)
acpiprt6 at acpi0: bus 3 (PEX6)
acpiprt7 at acpi0: bus 4 (PEX7)
acpiprt8 at acpi0: bus 5 (BR28)
acpicpu at acpi0 not configured
"PNP0A08" at acpi0 not configured
"PNP0003" at acpi0 not configured
acpicmos0 at acpi0
"IPI0001" at acpi0 not configured
"PNP0C33" at acpi0 not configured
pci0 at mainbus0 bus 0
0:31:5: mem address conflict 0xfe01/0x1000
pchb0 at pci0 dev 0 function 0 "Intel C3000 Host" rev 0x11
pchb1 at pci0 dev 4 function 0 "Intel C3000 GLREG" rev 0x11
"Intel C3000 RCEC" rev 0x11 at pci0 dev 5 function 0 not configured
ppb0 at pci0 dev 6 function 0 "Intel C3000 PCIE" rev 0x11
pci1 at ppb0 bus 1
"Intel C3000 QAT" rev 0x11 at pci1 dev 0 function 0 not configured
ppb1 at pci0 dev 10 function 0 "Intel C3000 PCIE" rev 0x11: msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 16 function 0 "Intel C3000 PCIE" rev 0x11
pci3 at ppb2 bus 3
ppb3 at pci0 dev 17 function 0 "Intel C3000 PCIE" rev 0x11
pci4 at ppb3 bus 4
ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
pci5 at ppb4 bus 5
"ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
"Intel C3000 SMBus" rev 0x11 at pci0 dev 18 function 0 not configured
ahci0 at pci0 dev 19 function 0 "Intel C3000 AHCI" rev 0x11: msi, AHCI 1.3.1
scsibus0 at ahci0: 32 targets
ahci1 at pci0 dev 20 function 0 "Intel C3000 AHCI" rev 0x11: msi, AHCI 1.3.1
scsibus1 at ahci1: 32 targets
xhci0 at pci0 dev 21 function 0 "Intel C3000 xHCI" rev 0x11: msi, xHCI 1.0
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 
addr 1
ppb5 at pci0 dev 22 function 0 "Intel C3000 PCIE" rev 0x11
pci6 at ppb5 bus 6
"Intel X553 SGMII" rev 0x11 at pci6 dev 0 function 0 not configured
"Intel X553 SGMII" rev 0x11 at pci6 dev 0 function 1 not configured
ppb6 at pci0 dev 23 function 0 "Intel C3000 PCIE" rev 0x11
pci7 at ppb6 bus 7
"Intel X553 SGMII" rev 0x11 at pci7 dev 0 function 0 not configured
"Intel X553 SGMII" rev 0x11 at pci7 dev 0 function 1 not configured
"Intel C3000 ME HECI" rev 0x11 at pci0 dev 24 function 0 not configured
"Intel C3000 LPC" rev 0x11 at pci0 dev 31 function 0 not configured
"Intel C3000 PMC" rev 0x11 at pci0 dev 31 function 2 not configured
"Intel C3000 SMBus" rev 0x11 at pci0 dev 31 function 4 not configured
"Intel C3000 SPI" rev 0x11 at pci0 dev 31 function 5 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
efifb0 at mainbus0: 1920x1200, 32bpp
wsdisplay at efifb0 not configured
uhidev0 at uhub0 port 1 configuration 1 interface 0 "Logitech 

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Andrew Luke Nesbit]

On 15/06/2019 10:36, Jonathan Gray wrote:
> On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
>>
>> Hello,
>>
>> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
>> Atom CPU (Denverton).  The board boots but most devices are not
>> detected because ACPI can't be enabled.
>>
>> Does anyone know if this is likely to be supported at some point?
> 
> Try a snapshot.  ACPI changes were made for a similiar machine
> (Lanner NCA-1510) in May.
> 
> However there is no support for the integrated X553 Ethernet at the
> moment.

Jonathan, thank you for the update.

Richard, I am in the market for one of these boards too, or some other
C3000 series model.  I'm a big fan of Supermicro's C2000 boards because
they are so versatile for low-power applications.  They are also
excellent home servers due to this and the correspondingly low heat and
noise.  Of course if you have a C2000 series board you would need to
ensure that it doesn't suffer from the notorious Erratum AVR.54 defect [1].

Please could you keep us updated re: your progress of getting OpenBSD
installed along with the support status of all devices?  If so this
would be greatly appreciated.  Thanks!!

[1] A little-known fact is that if you look through Intel's data sheets
and whitepapers you can find similar defects in the stepping errata for
other SoC's.  In my case I found an almost identical example in a recent
Celeron or Pentium J-series SoC.  To add to my disappointment, I later
discovered, entirely coincidentally, that it was used on the controller
boards for a model of Synology NAS that I was considering purchasing.

Andrew
-- 
OpenPGP key: EB28 0338 28B7 19DA DAB0  B193 D21D 996E 883B E5B9

Re: Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Jonathan Gray]

On Sat, Jun 15, 2019 at 09:02:11AM +0100, Richard Laysell wrote:
> 
> Hello,
> 
> I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
> Atom CPU (Denverton).  The board boots but most devices are not
> detected because ACPI can't be enabled.
> 
> Does anyone know if this is likely to be supported at some point?

Try a snapshot.  ACPI changes were made for a similiar machine
(Lanner NCA-1510) in May.

However there is no support for the integrated X553 Ethernet at the
moment.

> 
> Full dmesg is below
> 
> OpenBSD 6.5 (RAMDISK_CD) #3: Sat Apr 13 14:55:38 MDT 2019
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
> real mem = 17125621760 (16332MB)
> avail mem = 16602619904 (15833MB)
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
> bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
> bios0: Supermicro Super Server
> acpi0 at bios0: rev 2, can't enable ACPI
> cpu0 at mainbus0: (uniprocessor)
> cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
> cpu0: 
> FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
> cpu0: 2MB 64b/line 16-way L2 cache
> cpu0: cannot disable silicon debug
> cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
> pci0 at mainbus0 bus 0
> 0:31:5: mem address conflict 0xfe01/0x1000
> pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11
> pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11
> vendor "Intel", unknown product 0x19a2 (class system subclass root complex 
> event, rev 0x11) at pci0 dev 5 function 0 not configured
> ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11
> pci1 at ppb0 bus 1
> vendor "Intel", unknown product 0x19e2 (class processor subclass 
> Co-processor, rev 0x11) at pci1 dev 0 function 0 not configured
> ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11
> pci2 at ppb1 bus 2
> ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11
> pci3 at ppb2 bus 3
> ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11
> pci4 at ppb3 bus 4
> ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
> pci5 at ppb4 bus 5
> "ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, 
> rev 0x11) at pci0 dev 18 function 0 not configured
> ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 
> 0x11: unable to map interrupt
> ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 
> 0x11: unable to map interrupt
> xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 
> 0x11: couldn't map interrupt
> ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11
> pci6 at ppb5 bus 6
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 
> 0x11) at pci6 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 
> 0x11) at pci6 dev 0 function 1 not configured
> ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11
> pci7 at ppb6 bus 7
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 
> 0x11) at pci7 dev 0 function 0 not configured
> vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 
> 0x11) at pci7 dev 0 function 1 not configured
> vendor "Intel", unknown product 0x19d3 (class communications subclass 
> miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured
> vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) 
> at pci0 dev 31 function 0 not configured
> vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, 
> rev 0x11) at pci0 dev 31 function 2 not configured
> vendor "Intel", unknown product 0x19df (class serial bus subclass SMBus, rev 
> 0x11) at pci0 dev 31 function 4 not configured
> vendor "Intel", unknown product 0x19e0 (class serial bus unknown subclass 
> 0x80, rev 0x11) at pci0 dev 31 function 5 not configured
> isa0 at mainbus0
> com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> com0: console
> com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
> efifb0 at mainbus0: 1920x1200, 32bpp
> wsdisplay at efifb0 not configured
> softraid0 at root
> scsibus0 at softraid0: 256 targets
> root on rd0a swap on rd0b dump on rd0b
> erase ^?, werase ^W, kill ^U, intr ^C, status ^T
> 
> Welcome to the OpenBSD/amd64 6.5 installation program.
> (I)nstall, 

Installing OpenBSD on Supermicro A2SDi-4C-HLN4F

[Richard Laysell]

Hello,

I was trying OpenBSD on a Supermicro A2SDi-4C-HLN4F which uses an Intel
Atom CPU (Denverton).  The board boots but most devices are not
detected because ACPI can't be enabled.

Does anyone know if this is likely to be supported at some point?

Full dmesg is below

OpenBSD 6.5 (RAMDISK_CD) #3: Sat Apr 13 14:55:38 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
real mem = 17125621760 (16332MB)
avail mem = 16602619904 (15833MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7f0c3000 (35 entries)
bios0: vendor American Megatrends Inc. version "1.1b" date 12/17/2018
bios0: Supermicro Super Server
acpi0 at bios0: rev 2, can't enable ACPI
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Atom(TM) CPU C3558 @ 2.20GHz, 2200.41 MHz, 06-5f-01
cpu0: 
FPU,VME,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,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,CX16,xTPR,PDCM,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,FSGSBASE,SMEP,ERMS,MPX,RDSEED,SMAP,CLFLUSHOPT,PT,SHA,IBRS,IBPB,STIBP,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 2MB 64b/line 16-way L2 cache
cpu0: cannot disable silicon debug
cpu0: mwait min=64, max=64, C-substates=0.2.0.2, IBE
pci0 at mainbus0 bus 0
0:31:5: mem address conflict 0xfe01/0x1000
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x1980 rev 0x11
pchb1 at pci0 dev 4 function 0 vendor "Intel", unknown product 0x19a1 rev 0x11
vendor "Intel", unknown product 0x19a2 (class system subclass root complex 
event, rev 0x11) at pci0 dev 5 function 0 not configured
ppb0 at pci0 dev 6 function 0 vendor "Intel", unknown product 0x19a3 rev 0x11
pci1 at ppb0 bus 1
vendor "Intel", unknown product 0x19e2 (class processor subclass Co-processor, 
rev 0x11) at pci1 dev 0 function 0 not configured
ppb1 at pci0 dev 10 function 0 vendor "Intel", unknown product 0x19a5 rev 0x11
pci2 at ppb1 bus 2
ppb2 at pci0 dev 16 function 0 vendor "Intel", unknown product 0x19aa rev 0x11
pci3 at ppb2 bus 3
ppb3 at pci0 dev 17 function 0 vendor "Intel", unknown product 0x19ab rev 0x11
pci4 at ppb3 bus 4
ppb4 at pci4 dev 0 function 0 "ASPEED Technology AST1150 PCI" rev 0x03
pci5 at ppb4 bus 5
"ASPEED Technology AST2000" rev 0x30 at pci5 dev 0 function 0 not configured
vendor "Intel", unknown product 0x19ac (class system subclass miscellaneous, 
rev 0x11) at pci0 dev 18 function 0 not configured
ahci0 at pci0 dev 19 function 0 vendor "Intel", unknown product 0x19b2 rev 
0x11: unable to map interrupt
ahci1 at pci0 dev 20 function 0 vendor "Intel", unknown product 0x19c2 rev 
0x11: unable to map interrupt
xhci0 at pci0 dev 21 function 0 vendor "Intel", unknown product 0x19d0 rev 
0x11: couldn't map interrupt
ppb5 at pci0 dev 22 function 0 vendor "Intel", unknown product 0x19d1 rev 0x11
pci6 at ppb5 bus 6
vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 
0x11) at pci6 dev 0 function 0 not configured
vendor "Intel", unknown product 0x15e4 (class network subclass ethernet, rev 
0x11) at pci6 dev 0 function 1 not configured
ppb6 at pci0 dev 23 function 0 vendor "Intel", unknown product 0x19d2 rev 0x11
pci7 at ppb6 bus 7
vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 
0x11) at pci7 dev 0 function 0 not configured
vendor "Intel", unknown product 0x15e5 (class network subclass ethernet, rev 
0x11) at pci7 dev 0 function 1 not configured
vendor "Intel", unknown product 0x19d3 (class communications subclass 
miscellaneous, rev 0x11) at pci0 dev 24 function 0 not configured
vendor "Intel", unknown product 0x19dc (class bridge subclass ISA, rev 0x11) at 
pci0 dev 31 function 0 not configured
vendor "Intel", unknown product 0x19de (class memory subclass miscellaneous, 
rev 0x11) at pci0 dev 31 function 2 not configured
vendor "Intel", unknown product 0x19df (class serial bus subclass SMBus, rev 
0x11) at pci0 dev 31 function 4 not configured
vendor "Intel", unknown product 0x19e0 (class serial bus unknown subclass 0x80, 
rev 0x11) at pci0 dev 31 function 5 not configured
isa0 at mainbus0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
efifb0 at mainbus0: 1920x1200, 32bpp
wsdisplay at efifb0 not configured
softraid0 at root
scsibus0 at softraid0: 256 targets
root on rd0a swap on rd0b dump on rd0b
erase ^?, werase ^W, kill ^U, intr ^C, status ^T

Welcome to the OpenBSD/amd64 6.5 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell?


Regards,

Richard

Re: Problem with installing OpenBSD 6.4 on VirtualBox

[jean-yves boisiaud]

hello,

I upgraded VirtualBox from 5.1 to 5.2 and ... it works !

as the solution was so easy, i feel confused...

thanks for your help.

Le mar. 13 nov. 2018 à 22:07, jean-yves boisiaud <
jean-yves.boisi...@alcor-consulting.fr> a écrit :

> hello Dumitru,
>
> thanks for your answer.
>
> Le mar. 13 nov. 2018 à 21:50, Dumitru Moldovan  a écrit :
>
>> On Tue, 13 Nov 2018 20:51:09 +0100, jean-yves boisiaud <
>> jean-yves.boisi...@alcor-consulting.fr> wrote:
>>
>> > I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint
>> host.
>> > Please note that 6.0, ... 6.3 worked fine, only 6.4 failed.
>>
>> I've been running 6.4 with no issues on VirtualBox 5.0.x (initially) and
>> now 5.2.x.  But it's a VM installed with OpenBSD 5.6 and upgraded over the
>> years, not installed from latest stable media.
>>
>> Judging by the latest releases, the 5.1.x VirtualBox series is out of
>> maintenance, and the last 5.1.x version is dated before OpenBSD's 6.4
>> release (the same is true for 5.0.x).  Maybe try latest stable release,
>> 5.2.22 at the moment?
>
>
> ok, I'll try.
>
>> And make sure you choose the right OS template when creating the VM?
>>
>
> Yes. BSD - OpenBSD 64 bits.
>
>
>>
>> > The boot sequence starts, and restarts forever.
>> >
>> > I recorded the console of the VM, the last message displayed before
>> reboot
>> > is :
>> >
>> > isa0 at mainbus0
>> > pckbc0 at isa0 port 0x60/5 irq 1 irq 12
>>
>> These two lines are common on both my VM and my desktop.  The next two
>> lines are:
>>
>> pckbd0 at pckbc0 (kbd slot)
>> wskbd0 at pckbd0: console keyboard
>>
>> Uneducated guess here, but is there anything out of normal with your
>> keyboard setup in the VM or with the keyboard options chosen during
>> install?
>
> keyboard is the default.
>
>
>> Can you try the defaults?
>>
>
> Yes. 64 still fails and 63 still works...
>
> I will upgrade VirtualBox to 5.2. and make a try.
>
>
> --
> Jean-Yves Boisiaud - Alcor Consulting
> 49, rue du Chemin Vert
> 49300 Cholet
> mobile : +33 6 63 71 73 46
>


-- 
Jean-Yves Boisiaud - Alcor Consulting
49, rue du Chemin Vert
49300 Cholet
mobile : +33 6 63 71 73 46

Re: Problem with installing OpenBSD 6.4 on VirtualBox

[jean-yves boisiaud]

hello Dumitru,

thanks for your answer.

Le mar. 13 nov. 2018 à 21:50, Dumitru Moldovan  a écrit :

> On Tue, 13 Nov 2018 20:51:09 +0100, jean-yves boisiaud <
> jean-yves.boisi...@alcor-consulting.fr> wrote:
>
> > I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint
> host.
> > Please note that 6.0, ... 6.3 worked fine, only 6.4 failed.
>
> I've been running 6.4 with no issues on VirtualBox 5.0.x (initially) and
> now 5.2.x.  But it's a VM installed with OpenBSD 5.6 and upgraded over the
> years, not installed from latest stable media.
>
> Judging by the latest releases, the 5.1.x VirtualBox series is out of
> maintenance, and the last 5.1.x version is dated before OpenBSD's 6.4
> release (the same is true for 5.0.x).  Maybe try latest stable release,
> 5.2.22 at the moment?


ok, I'll try.

> And make sure you choose the right OS template when creating the VM?
>

Yes. BSD - OpenBSD 64 bits.


>
> > The boot sequence starts, and restarts forever.
> >
> > I recorded the console of the VM, the last message displayed before
> reboot
> > is :
> >
> > isa0 at mainbus0
> > pckbc0 at isa0 port 0x60/5 irq 1 irq 12
>
> These two lines are common on both my VM and my desktop.  The next two
> lines are:
>
> pckbd0 at pckbc0 (kbd slot)
> wskbd0 at pckbd0: console keyboard
>
> Uneducated guess here, but is there anything out of normal with your
> keyboard setup in the VM or with the keyboard options chosen during
> install?

keyboard is the default.


> Can you try the defaults?
>

Yes. 64 still fails and 63 still works...

I will upgrade VirtualBox to 5.2. and make a try.


-- 
Jean-Yves Boisiaud - Alcor Consulting
49, rue du Chemin Vert
49300 Cholet
mobile : +33 6 63 71 73 46

Re: Problem with installing OpenBSD 6.4 on VirtualBox

[Dumitru Moldovan]

On Tue, 13 Nov 2018 20:51:09 +0100, jean-yves boisiaud 
 wrote:

> I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint host.
> Please note that 6.0, ... 6.3 worked fine, only 6.4 failed.

I've been running 6.4 with no issues on VirtualBox 5.0.x (initially) and now 
5.2.x.  But it's a VM installed with OpenBSD 5.6 and upgraded over the years, 
not installed from latest stable media.

Judging by the latest releases, the 5.1.x VirtualBox series is out of 
maintenance, and the last 5.1.x version is dated before OpenBSD's 6.4 release 
(the same is true for 5.0.x).  Maybe try latest stable release, 5.2.22 at the 
moment?  And make sure you choose the right OS template when creating the VM?

 
> The boot sequence starts, and restarts forever.
> 
> I recorded the console of the VM, the last message displayed before reboot
> is :
> 
> isa0 at mainbus0
> pckbc0 at isa0 port 0x60/5 irq 1 irq 12
 
These two lines are common on both my VM and my desktop.  The next two lines 
are:

pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard

Uneducated guess here, but is there anything out of normal with your keyboard 
setup in the VM or with the keyboard options chosen during install?  Can you 
try the defaults?

Problem with installing OpenBSD 6.4 on VirtualBox

[jean-yves boisiaud]

hello,

I 'm trying to install OpenBSD 6.4 on VirtualBox 5.1.38 on a LinuxMint host.
Please note that 6.0, ... 6.3 worked fine, only 6.4 failed.

The boot sequence starts, and restarts forever.

I recorded the console of the VM, the last message displayed before reboot
is :

isa0 at mainbus0
pckbc0 at isa0 port 0x60/5 irq 1 irq 12

I used the last install64.iso file. I also tried with install64.fs, same
problem.

How could I install obsd 6.4 ?

Thank you for your help.

-- 
Jean-Yves Boisiaud - Alcor Consulting
49, rue du Chemin Vert
49300 Cholet - France
mobile : +33 6 63 71 73 46

Re: Installing openbsd on MacBook air 2014

[Joerg Jung]

> On 17. May 2017, at 13:51, flipchan  wrote:
> 
> Yeah the amd64 works to install and it boots but it disabled all port 
> includeing the keyboard:
> 
> I have tried both 6.1 6.0 and 5.9 all same 
> error: [drm:pid0:intel_uncore_check_errors] eERROR Unclaimed register before 
> interupt
> nvram invalid checksum
> uhub0: device problem, disabling port 1,3,5,12

Are you sure that you bootet a amd64 6.1 or 6.0? If I remember correctly, the 
“nvram invalid checksum” 
message was removed earlier. 
Are your EFI/SMC/firmwares up2date (patched via OSX)? Does any other OS boot 
and work, e.g. can 
you rule out that the hub is is not broken? I used similar MacBook Air's from 
various generations all 
working fine here.

> On May 16, 2017 3:49:57 PM GMT+02:00, Stefan Sperling  wrote:
>> On Tue, May 16, 2017 at 12:22:18PM +, flipchan wrote:
>>> Here is the output:
>>> 
>>> 
>>> first boot didnt work so i searched around and found this blog post
>> http://www.sacrideo.us/openbsd-on-macbook/ and i tried typing in the
>> mkdir commands i it booted
>>> 
> OpenBSD/i386 BOOT 3.31
>>> boot>
>>> boot>mkdir cd-dir
>>> boot>cd cd-dir
>>> boot>mkdir -p 4.2/i386
>>> boot>mkdir -p etc
>>> boot>cp ~/cdboot ~/cdbr ~/bsd.rd 4.2/i386
>>> boot>config -ef 4.2/i386/bsd.rd
>> 
>> These aren't commands for the boot loader. This guide recommends that
>> you create a custom ISO image. It's very outdated. I would not rely on
>> it.
>> 
>>> Welcome to the OpenBSD/i386 6.1 installation program:
>> 
>> Please try amd64 instead of i386.
> 
> -- 
> Take Care Sincerely flipchan layerprox dev

Re: Installing openbsd on MacBook air 2014

[flipchan]

Yeah the amd64 works to install and it boots but it disabled all port 
includeing the keyboard:

I have tried both 6.1 6.0 and 5.9 all same 
error: [drm:pid0:intel_uncore_check_errors] eERROR Unclaimed register before 
interupt
nvram invalid checksum
uhub0: device problem, disabling port 1,3,5,12



On May 16, 2017 3:49:57 PM GMT+02:00, Stefan Sperling  wrote:
>On Tue, May 16, 2017 at 12:22:18PM +, flipchan wrote:
>> Here is the output:
>> 
>> 
>> first boot didnt work so i searched around and found this blog post
>http://www.sacrideo.us/openbsd-on-macbook/ and i tried typing in the
>mkdir commands i it booted
>> 
>> >>OpenBSD/i386 BOOT 3.31
>> boot>
>> boot>mkdir cd-dir
>> boot>cd cd-dir
>> boot>mkdir -p 4.2/i386
>> boot>mkdir -p etc
>> boot>cp ~/cdboot ~/cdbr ~/bsd.rd 4.2/i386
>> boot>config -ef 4.2/i386/bsd.rd
>
>These aren't commands for the boot loader. This guide recommends that
>you create a custom ISO image. It's very outdated. I would not rely on
>it.
> 
>> Welcome to the OpenBSD/i386 6.1 installation program:
>
>Please try amd64 instead of i386.

-- 
Take Care Sincerely flipchan layerprox dev

Re: Installing openbsd on MacBook air 2014

[Stefan Sperling]

On Tue, May 16, 2017 at 12:22:18PM +, flipchan wrote:
> Here is the output:
> 
> 
> first boot didnt work so i searched around and found this blog post 
> http://www.sacrideo.us/openbsd-on-macbook/ and i tried typing in the mkdir 
> commands i it booted
> 
> >>OpenBSD/i386 BOOT 3.31
> boot>
> boot>mkdir cd-dir
> boot>cd cd-dir
> boot>mkdir -p 4.2/i386
> boot>mkdir -p etc
> boot>cp ~/cdboot ~/cdbr ~/bsd.rd 4.2/i386
> boot>config -ef 4.2/i386/bsd.rd

These aren't commands for the boot loader. This guide recommends that
you create a custom ISO image. It's very outdated. I would not rely on it.
 
> Welcome to the OpenBSD/i386 6.1 installation program:

Please try amd64 instead of i386.

Re: Installing openbsd on MacBook air 2014

[flipchan]

Here is the output:


first boot didnt work so i searched around and found this blog post 
http://www.sacrideo.us/openbsd-on-macbook/ and i tried typing in the mkdir 
commands i it booted

>>OpenBSD/i386 BOOT 3.31
boot>
boot>mkdir cd-dir
boot>cd cd-dir
boot>mkdir -p 4.2/i386
boot>mkdir -p etc
boot>cp ~/cdboot ~/cdbr ~/bsd.rd 4.2/i386
boot>config -ef 4.2/i386/bsd.rd

pci11 at ppb10 bus 4
ahci0 at pci11 dev 0 function 0 vendor "Marvell", unknown product 0x9183 rev 
0x14: msi, AHCI 1.0
ahci0: port 0: 6.0Gb/s
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed 
naa.5001b44c33d7ff40
sd0: 115712MB, 512 bytes/sector, 236978176 sectors, thin
pcib0 at pci0 dev 31 function 0 "Intel 8 Series LPC" rev 0x04
"Intel 8 Series SMBus" rev 0x04 at pci0 dev 31 function 3 not configured
isa0 at pcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
uhub0: device problem, disabling port 1
uhub0: device problem, disabling port 3
uhub0: device problem, disabling port 5
uhub0: device problem, disabling port 12

Welcome to the OpenBSD/i386 6.1 installation program:
(I)nstall, (Upgrade), (A)utoinstall or (S)hell

i cant do anything cuz my keyboard is disabled


On May 16, 2017 1:31:02 PM GMT+02:00, Stefan Sperling  wrote:
>On Tue, May 16, 2017 at 08:43:39AM +, flipchan wrote:
>> Hi the install61.fs boots up but it gets frozen giveing errors 
>> 
>> Link to pic :
>https://www.file-upload.net/download-12501308/2017-05-1610.41.54.jpg.html
>
>Sorry, I tried a few times, enabled some java script in firefox
>along the way, and then gave up. I cannot see your image.
>
>> Maybe I'm missing something
>
>Please do not send image attachements, or links like this.
>
>If you want help, please describe your problem in plain text.
>If necessary type off your screen. Yes it feels very silly to do that,
>but it saves everyone else a bit of time.

-- 
Take Care Sincerely flipchan layerprox dev