Dear Peter and all. Unfortunately I celebrated to early it seems. :-/
In my last post I described a hack in which I let the OpenBSD partition start at "sector 0" in order to avoid BIOS hangup. When I now tried this way of setup with a SSD disk instead of HDD, after a succesful install, OpenBSD boots with the following Kernel panic: "openbsd panic root filesystem has size 0" For this I found the following post talking about "partition offset" [1]. It explains: "Sector 0 can't be used for a partition, because it's occupied by the MBR partition table" So I believe the "Sector 0" hack is actually breaking things (as the fdisk output of the result parition table also suggests). Dear Peter, can you remember more details how you got OpenBSD to work on that Clevo W840-SU by any chance? Did you use SSD or HDD for the booting disk? > March 20, 2019 8:46 AM, "Peter N. M. Hansteen" <[email protected]> wrote: > "I *think* what I did back then was set the all parts to size zero, except > the OpenBSD part which I set to the largest > the program would let me." What were the other parts (partitions)? Any further ideas and hints what I could try? Thank you very much. Fox --- [1] https://unix.stackexchange.com/questions/148589/partition-offset-at-63-or-64
