Re: unhibernate failed: original kernel changed
On Mon, Jul 31, 2023 at 09:39:01PM +0200, Piotr K. Isajew wrote: > that's exactly what I got when I tried to resume after ZZZ on my > Lenovo machine with custom 7.3 kernel. Customization is primarily > to point swap and dump to non-default device: > > root on sd1a swap on sd0b dump on sd0b > > Full dmesg attached. > > Note that I'm not a heavy hibernate/suspend user. I have never > tried it with success on this machine. The message explained exactly what happened. What is unclear? > OpenBSD 7.3-stable (PKI) #27: Tue Jul 25 21:39:08 CEST 2023 > pki@zgred.localnet:/sys/arch/amd64/compile/PKI > real mem = 29892214784 (28507MB) > avail mem = 28966887424 (27624MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.3 @ 0xcb709000 (57 entries) > bios0: vendor LENOVO version "GKCN50WW" date 11/24/2021 > bios0: LENOVO 82JU > acpi0 at bios0: ACPI 5.0Undefined scope: \\_SB_.PCI0.PB2_ > > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP UEFI SSDT SSDT IVRS SSDT SSDT TPM2 POAT ASF! BOOT > HPET APIC MCFG SLIC WDAT WDRT SSDT SSDT VFCT SSDT SSDT SSDT SSDT CRAT CDIT > SSDT SSDT SSDT SSDT SSDT SSDT FPDT WSMT SSDT SSDT BGRT > acpi0: wakeup devices GPP0(S3) GPP1(S3) GPP2(S3) GPP3(S3) GPP4(S3) GPP5(S3) > GP17(S3) XHC0(S3) XHC1(S3) GP19(S3) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpihpet0 at acpi0: 14318180 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Ryzen 7 5800H with Radeon Graphics, 3200.00 MHz, 19-50-00 > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,WAITPKG,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 100MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: AMD Ryzen 7 5800H with Radeon Graphics, 3200.00 MHz, 19-50-00 > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu1: smt 1, core 0, package 0 > tsc: cpu0/cpu1: sync test failed > timecounter: active counter changed: tsc -> acpihpet0 > cpu2 at mainbus0: apid 2 (application processor) > cpu2: AMD Ryzen 7 5800H with Radeon Graphics, 3200.00 MHz, 19-50-00 > cpu2: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu2: smt 0, core 1, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: AMD Ryzen 7 5800H with Radeon Graphics, 3200.00 MHz, 19-50-00 > cpu3: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES > cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu3: smt 1, core 1, package 0 > cpu4 at mainbus0: apid 4 (application processor) > cpu4: AMD Ryzen 7 5800H with Radeon Graphics, 3200.00 MHz, 19-50-00 > cpu4: >
Re: Installing openBSD
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
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
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
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: Network VF 2
On Mon, Jul 31, 2023 at 06:48:42PM +0200, Robert Palm said: Cannot get network working on my VisionFive 2 (ping a different machine). Any ideas? Thanks! Does either side see ARP traffic for the other? (arp -an) Do you see traffic leaving your OpenBSD machine? (tcpdump(8) is your friend) Check for host firewalls on both sides. FreeBSD machine: [ snip ] media: Ethernet autoselect (100baseTX ) 100/half is a bit odd these days, is this machine able to communicate to other things on this ethernet link? -- Matthew Ernisse https://www.going-flying.com/
Re: Installing openBSD
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. > > > >
Network VF 2
Cannot get network working on my VisionFive 2 (ping a different machine). Any ideas? Thanks! FreeBSD machine: $ ifconfig re0 re0: flags=8943 metric 0 mtu 1500 options=8209b ether a8:a1:59:a2:50:45 inet 192.168.10.20 netmask 0xff00 broadcast 192.168.10.255 media: Ethernet autoselect (100baseTX ) status: active nd6 options=29 VF2: vf2# cat /etc/hostname.dwqe1 media media 100baseTX inet autoconf inet6 autoconf Same for dwqe0. vf2# dmesg | grep dwq dwqe0 at simplebus0 gmac 0: rev 0x00, address 6c:cf:39:00:1c:29 ytphy0 at dwqe0 phy 0: YT8531 10/100/1000 PHY, rev. 11 dwqe1 at simplebus0 gmac 1: rev 0x00, address 6c:cf:39:00:1c:2a ukphy0 at dwqe1 phy 0: Generic IEEE 802.3u media interface, rev. 8: OUI 0x00, model 0x0012 vf2# ifconfig dwqe1 dwqe1: flags=a48843 mtu 1500 lladdr 6c:cf:39:00:1c:2a index 2 priority 0 llprio 3 media: Ethernet 100baseTX status: active inet6 fe80::6ecf:39ff:fe00:1c2a%dwqe1 prefixlen 64 scopeid 0x2 vf2# ifconfig dwqe1 192.168.10.30 netmask 255.255.255.0 vf2# ifconfig dwqe1 dwqe1: flags=a48843 mtu 1500 lladdr 6c:cf:39:00:1c:2a index 2 priority 0 llprio 3 media: Ethernet 100baseTX status: active inet6 fe80::6ecf:39ff:fe00:1c2a%dwqe1 prefixlen 64 scopeid 0x2 inet 192.168.10.30 netmask 0xff00 broadcast 192.168.10.255 vf2# ping 192.168.10.20 PING 192.168.10.20 (192.168.10.20): 56 data bytes ping: sendmsg: Host is down ping: wrote 192.168.10.20 64 chars, ret=-1 ping: sendmsg: Host is down ping: wrote 192.168.10.20 64 chars, ret=-1 ping: sendmsg: Host is down ping: wrote 192.168.10.20 64 chars, ret=-1 ^C --- 192.168.10.20 ping statistics --- 9 packets transmitted, 0 packets received, 100.0% packet loss vf2# netstat -rn Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface 224/4 127.0.0.1 URS00 32768 8 lo0 127/8 127.0.0.1 UGRS 00 32768 8 lo0 127.0.0.1 127.0.0.1 UHhl 12 32768 1 lo0 192.168.10/24 192.168.10.30 UCn10 - 4 dwqe1 192.168.10.20 link#2 UHRLc 01 - 3 dwqe1 192.168.10.30 6c:cf:39:00:1c:2a UHLl 0 33 - 1 dwqe1 192.168.10.255 192.168.10.30 UHb00 - 1 dwqe1
Re: Installing openBSD
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
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
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
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
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
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
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
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
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
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.
