Hi Todd, im sorry to hear that you are having that hassle... the only other thing I can think of is to clear the partition table (if you have no other data stored) on the hard disk, I have had trouble with other installers (that said, not OpenBSDs) where if I had one OS installed on the disk before I would not be able to install because of some bug in the way the Partition tables were written by the other OS.
Ok just to confirm you are writing the install67.fs or install68.img to the USB drive... the usb drive is not encrypted.. you are not writing the install6.7fs or install68.img to the internal nvme disk of your laptop when you boot your laptop you get the usual OpenBSD boot prompt and you just hit enter ? looking at the dmesg it is saying softraid0 ... (which im assuming would only be relevant if you were loading an encrypted drive or a raid that is strange) I had not noticed that in a dmesg of a standard installer (I could be wrong) On Sun, 18 Oct 2020 at 04:13, Todd Brewster <toddbrewste...@icloud.com> wrote: > > Hi Tom, > > Unfortunately, 6.8 stops exactly at the same point. I disabled almost > anything in BIOS or set it to a setting I considered the safest option. > > I verified that the USB flash works fine with the W540 I mentioned earlier. > > I specifically bought this laptop as it is officially fully supported to run > Fedora (which it actually does) and this made me assume that OpenBSD would > also run fine. I guess I run Fedora for now and try with 6.9 in a bit. > > Thanks and all the best, > > Todd > > On 15 October 2020 at 8:36, Tom Smyth <tom.sm...@wirelessconnect.eu> wrote: > > Hey Todd, > Can you try to run one of the current snapshots just in case > there is some new hardware in the P1 that is not recognised > > last of the hardware checks what INtel SGX setting do you have ? > and what intel TXT Settting do you have ? > > Im running 6.8 current myself... > > On Thu, 15 Oct 2020 at 03:37, Todd Brewster <toddbrewste...@icloud.com> wrote: > > > Hi Folks, > > > I played around a bit, still no luck. > > boot -s, does not work > > boot -c, works; I can list the devices and I can switch on verbose. Verbose > does not provide additional insights, system is stuck exactly at the same > point. > > > Any t-shoot ideas are very much appreciated. > > > Thanks and all the best, > > > Todd > > > > > -- > Kindest regards, > Tom Smyth. -- Kindest regards, Tom Smyth.
