HI I know for sure 6.5 does not work. I think 6.4 also did not work, because I thought it was a hardware issue at the time, and 6.5 came round before I got a machine up again, but I did not write anything down.
I can't say which versions of ldomctl are involved, because there is no "version" option, no version in the man page, and help does not say which version it is. I can't think of any other way to identify the version. I think it is safe to say 6.3 is good, 6.4 is bad, but if you really can't spot the problem, I can test - but not until after 7th November. Andrew On Mon, 1 Nov 2021, 15:11 Klemens Nanni, <[email protected]> wrote: > On Wed, Oct 27, 2021 at 04:22:27PM +0100, Andrew Grillet wrote: > > Thanks ... > > > > Oracle Advanced Lights Out Manager CMT v1.7.9 > > Sun-Fire-T2000 System Firmware 6.7.10 2010/07/14 16:35 > > Host flash versions: > > OBP 4.30.4.b 2010/07/09 13:48 > > Hypervisor 1.7.3.c 2010/07/09 15:14 > > POST 4.30.4.b 2010/07/09 14:24 > > AFAIK, this is the latest available publicly. > > > > I had to recreate the factory default each time. > > Now I have the system running, I am quite reluctant to go back and mess > it > > up. > > If you look in my zip, you will see two config directories. These were > each > > built with a fresh factory-default and the exact same ldom.conf (its > there > > for > > you to check if I messed up!) > > > > The process is: > > 1) do a factory reset > > 2) download the one you wish to test > > 3) attempt to boot. > > > > The bsd63 one will boot and run fine. > > The oct2021 version will give : > > ----%<---------------------- > > > > {0} ok boot > > > > SC Alert: Host System has Reset > > > > ERROR: /pci@780: Invalid hypervisor argument(s). function: b4 > > > > ERROR: /pci@780: Invalid hypervisor argument(s). function: b4 > > > > ERROR: /pci@780: Invalid hypervisor argument(s). function: b5 > > > > > > Sun Fire(TM) T1000, No Keyboard > > Copyright (c) 1998, 2011, Oracle and/or its affiliates. All rights > reserved. > > OpenBoot 4.30.4.d, 2048 MB memory available, Serial #77558134. > > Ethernet address 0:14:4f:9f:71:76, Host ID: 849f7176. > > > > Boot device: net File and args: > > ERROR: boot-read fail > > > > Evaluating: > > > > Can't locate boot device > > > > ----%<---------------------- > > After this, my device tree is empty. > > I'm not sure what you mean by that. > You mean you end up in OBP but there are no devices you can boot from? > > > Resetting to factory-default recovers the device tree, and the system > will > > boot. > > > > (Note this is from the T1000, but the T2000 results were the same apart > > from some differences in > > ID numbers and white space AFAICR). > > > > I can continue to test on the T1000 > > Can you bisect OpenBSD releases, i.e. ldomctl versions, on this box? > > Apparently configurations generated with 6.3 work while those out of 6.9 > don't, so it'd be helpful to a closer timeframe, then I can look at > ldomctl changes between the last good and first bad versions. >
