Re: How to customize disk partition in UEFI?

2023-07-23 Thread Nick Holland

On 7/22/23 15:44, ykla wrote:

For OpenBSD installation, I choose custom disk in partition. And I set the
first partition is MSDOS and mountpoint is /boot/efi and the second
partition is /, the last partition is swap. And I continue install openbsd,
but at least it warning me that boot install failed, the system will not
boot.

And set none mountpoint is also be errors.

Last I Automated partition first and delete all partition except i that is
MSDOS partition. Then everything is fine.

So how to customize disk partition in UEFI except Auto creates EFI
partition?

ykla


I think you are confusing the fdisk and disklabel parts of the install,
and you aren't providing enough details about what you are trying to do.

During the fdisk stage, you don't worry about root and swap.  During
the disklabel stage, you don't worry about the efi stuff.

So ... let's assume you are doing an OpenBSD-only UEFI install.
In the installer, pick "Whole Disk GPT" or something similar to set up
the UEFI partition and the OpenBSD partition.  Done.

IF you are trying to multi-boot and adjust your fdisk partitions, I'd
suggest starting with the OS that is most picky and/or gives you the
least control over the install -- probably Linux or Windows.  Then boot
the OpenBSD installer, and work an OpenBSD partition into available
space, and do the install as normal.

Now customize the disklabel partitions as you wish.  You went out
of your way to mention swap and root, and nothing else.  I'm taking
this as meaning you are intending to do things wrong by making a root-
only system.  Please stop and reconsider your life choices here, this
one is probably not one of your better ones.

Nick.



Re: how to startx with kde?

2023-07-23 Thread Greg Thomas
On Sat, Jul 22, 2023 at 2:46 PM Martin Schröder  wrote:

> Am Sa., 22. Juli 2023 um 23:15 Uhr schrieb Greg Thomas
> :
> > Have you read:
> >
> > https://www.openbsd.org/faq/faq11.html
>
> Where does that mention KDE?
>

It doesn't.  But it also doesn't mention many desktop environments and
display managers.

That being said I clearly haven't kept up with KDE development so I went
down the KDE/Wayland rabbit hole.  For the OP:

https://undeadly.org/cgi?action=article;sid=20210124113220


> P.S.: Please learn to quote


Mea culpa.

Greg


OpenBSD Successfully Installed On A Logical Slice, But The Bootloader Does Not Load It; Wireless Device

2023-07-23 Thread Jay F. Shachter


Esteemed Colleagues:

Although it is unsupported, I have successfully installed OpenBSD on a
logical slice within the extended slice of an MBR-partitioned disk.
It took days.  I may post, to this mailing list, a description of how
I figured out how to do it; but the write-up would take hours, so it
may not appear right away.

Here is the edited output from "disklabel sd0" and from "fdisk -v sd0":

  m5# fdisk -v sd0  
  Primary GPT:
  Not Found

  Secondary GPT:
  Not Found

  MBR:
  Disk: sd0 geometry: 58369/255/63 [937703088 Sectors]
  Offset: 0 Signature: 0xAA55
  Starting Ending LBA Info:
   #: id  C   H   S -  C   H   S [   start:size ]
  
---
  *0: 0C  57389 130  22 -  58369  80  30 [   921962496:15740559 ] Win95 
FAT32L
   1: 07 13   0  52 -  19594  64  54 [  208896:   314572800 ] NTFS
   2: 07  0  32  33 - 13   0  51 [2048:  206848 ] NTFS
   3: 05  19594  64  55 -  57389 130  21 [   314781696:   607180800 ] Extended 
DOS
  Disk: sd0 geometry: 58369/255/63 [937703088 Sectors]
  Offset: 314781696 Signature: 0xAA55
  Starting Ending LBA Info:
   #: id  C   H   S -  C   H   S [   start:size ]
  
---
   0: 8E  19594  97  24 -  26121 118  45 [   314783744:   104857600 ] Linux LVM
   1: 05  26121 118  47 -  30037 215   2 [   419641345:62916607 ] Extended 
DOS
   2: 00  0   0   0 -  0   0   0 [   314781696:   0 ] unused
   3: 00  0   0   0 -  0   0   0 [   314781696:   0 ] unused
  Disk: sd0 geometry: 58369/255/63 [937703088 Sectors]
  Offset: 419641345 Signature: 0xAA55
  Starting Ending LBA Info:
   #: id  C   H   S -  C   H   S [   start:size ]
  
---
   0: A6  26121 151  16 -  30037 215   2 [   419643393:62914559 ] OpenBSD
   1: 05  30037 215   5 -  31212 215  43 [   482557954:18876414 ] Extended 
DOS
   2: 00  0   0   0 -  0   0   0 [   419641345:   0 ] unused
   3: 00  0   0   0 -  0   0   0 [   419641345:   0 ] unused
 [ omitted lines ]
  m5# disklabel sd0 
  # /dev/rsd0c:
 [ omitted lines ]
  16 partitions:
  #size   offset  fstype [fsize bsize   cpg]
a: 57358559419643393  4.2BSD   2048 16384 12960 # /
b:  5556000477001952swap# none
c:9377030880  unused
d:   860160627273728   MSDOS# /mnt/boot
i:   206848 2048NTFS# 
/Windows-Boot
j:314572800   208896NTFS# /Windows
k: 15740592921962496   MSDOS# /FreeDOS
l:104857600314783744 unknown
  m5#

(If anyone is wondering about /dev/sd0l, it is the LVM volume group
containing Linux logical volumes, on which my collection of Linux
operating systems resides.  These are visible on FreeBSD.  If anyone
on this mailing list knows how to make Linux logical volumes visible
on OpenBSD as they are on FreeBSD, I would welcome seeing the
information on this mailing list.)

There is still, however, one problem (which may be related to the
fact that installation on a logical slice is unsupported, although I
don't see how it is): the bootloader does not work.  This is not
fatal, because I can get GRUB to boot the kernel directly, with
"kopenbsd /bsd -r sd0a" (more on that later).  But it is troubling.

I have two operating systems on my computer that can install GRUB:
Solaris and Linux.  Both of them ought to be able to boot OpenBSD by
chainloading to the OpenBSD bootloader, thus:

   set root=(hd0,6)
   chainloader +1

Here is the output of "installboot -nv sd0":

  m5# installboot -v sd0  
  Using / as root
  installing bootstrap on /dev/rsd0c
  using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot
  copying /usr/mdec/boot to //boot
  looking for superblock at 65536
  found valid ffs2 superblock
  //boot is 6 blocks x 16384 bytes
  fs block shift 2; part offset 419643393; inode block 56, offset 2928
  expecting 64-bit fs blocks (incr 4)
  master boot record (MBR) at sector 0
partition 0: type 0x0C offset 921962496 size 15740559
partition 1: type 0x07 offset 208896 size 314572800
partition 2: type 0x07 offset 2048 size 206848
partition 3: type 0x05 offset 314781696 size 607180800
  extended boot record (EBR) at sector 314781696
partition 0: type 0x8E offset 2048 size 104857600
partition 1: type 0x05 offset 104859649 size 62916607
  extended boot record (EBR) at sector 4

amd microcode

2023-07-23 Thread Christer Solskogen
I just saw https://undeadly.org/cgi?action=article;sid=20230723185853
and was wondering how I can check if it works? Does or should the
microcode update show up in dmesg or in some other log?

-- 
chs