Has anybody ever seen 'WARNING: ixgbe0: failed callback (action=0, ret=-1)' only appears on the primary console, in my case ttya. I went back to my serial logs and boot I did on Dec 8 15:57:04 with a omnios-bloody be create on 20221205 was fine It started showing up on Jan 9th with a omnios-bloody be create on 20230109. It's been there every reboot since. It doesn't seem to cause any harm so far. I also did not spot any ixgbe related changes

between 20221205 and 20230109.

hah, OI uploads a new SPARC ISO a day before I decide to test SPARC

toasterson: no usb image for that may 2023 image?

from what I remember all of these slimline DVD drives in these systems are pretty marginally working

Like even on the T4 with Solaris 11 it failed 4 times before I had to give up and try 3 or 4 thumb drives

KungFuJesus: Not for sparc no. Only x86 has USB.

I mean the old image had one from 2022, right?

in any case, I'm having issues booting from the slimline dvd drive in here. Claims "the file just loaded doesn't appear to be executable"

that's with "boot cdrom" from the boot prompt. Any tips? I really really don't want to have to try to netboot, lol. I swear I managed to get OpenSXCE on this thing via this dvdrom time a handful of years ago

sjorge - I would look at all commits in that range, not just ixgbe as the framework it's using is centra. At least it's a fairly short range.

*central

The old one had a .img but the new one has't gottan any. Did I intrucude you to the Sparc person? I can also ask if he can do a new USB img

If you only have a CDROM the Min image will get you started

it definitely has a dvdrom but yeah it's possible the cd laser might be in better shape so I'll try that one

I sent you my email but I haven't heard from anyone

The V240 has even worse specs than I can remember, heh. Only has 2GB of memory in it, it would seem, not ideal. Could max it out if I could actually find reasonably price reliable ECC DDR

also is an oddball in that it has a smart card reader connecting to the same daughterboard

Managed to finally get the thing to boot. I think mechanically the contacts on the cdrom where they mate with the daughterboard are a bit worn? Like, forcing the drive further in a bit harder during "boot cdrom" eventually hits the installer

lol, well that's fun. On the text installer in the date screen starting with a 2 says it's out of range. Of course it might be that I just swapped out the battery and the clock seems to think it's the year 2000?

hmm, think I finally got it to install properly but it involved wiping the label that was on there and destroying remnants of a zpool, creating a new zpool, and doing the "install to existing zpool" configuration. I'm not sure this is going to be bootable in the end, though

I probably should have kept the opensxce installation there and installed into the same pool, that likely would have been a more bootable outcome

moment of truth, it's spinning at the boot prompt, heh

wow, actually booting. Color me impressed, I had low hopes of that working

andyf: there are some (lib)dladm ones