09:02:18 are there omniosce AMIs to consume in AWS or do I have to import one? searching for the AMI IDs doesn't produce any results 09:04:13 There aren't any official AMIs any more, but it is fairly straightforward to build one using the published "cloud" images. 09:04:30 There are some instructions at https://omnios.org/dev/ec2 09:07:46 thanks - I found that - I just wanted to be sure, that "no official AMIs" was the correct search result 09:08:30 because they are still listed on https://omnios.org/setup/aws 09:08:50 Ah, thanks, we should do something about that page 09:09:45 We could look at maintaining some again, but the focus shifted to the more generic cloud images that can be used at a lot of places. 09:27:54 and nobody was volunteering to maintain the AMIs 19:08:28 Looking at the output of prtconf -v, I've identified a specific PCI device but need to know what driver is attached. What's the easiest way to do this? 19:11:15 prtconf -vd 19:17:59 thanks... but where do I find the actual driver name in that wall of text? 19:24:59 `/usr/lib/pci/pcieadm show-devs` is a nice way to display it, after installing the `diagnostic/pci` package 19:26:18 thanks andyf. I presume in the following line the "mr_sas0" is the driver name. 19:26:26 3b/0/0 PCIe Gen 3x8 mr_sas0 MegaRAID SAS-3 3108 [Invader] 19:26:30 `mr_sas` is the driver, `0` is the instance number 19:26:41 great, thanks! 19:28:37 I'm adding diagnostic/pci package to my 'install everywhere' list. 19:44:09 nomad: andy typoed, you want -D to show driver attachment 19:44:14 -d shows the pci.ids name 19:44:19 (and -v shows a wall of text) 19:44:29 prtconf -dD might be closer to what you want 19:44:40 (especially for non-pci devices) 19:59:48 thanks richlowe 20:00:20 in this case I was looking for a PCI device but the info is useful.