-
neuroserveare there omniosce AMIs to consume in AWS or do I have to import one? searching for the AMI IDs doesn't produce any results
-
andyfThere aren't any official AMIs any more, but it is fairly straightforward to build one using the published "cloud" images.
-
andyfThere are some instructions at omnios.org/dev/ec2
-
neuroservethanks - I found that - I just wanted to be sure, that "no official AMIs" was the correct search result
-
neuroservebecause they are still listed on omnios.org/setup/aws
-
andyfAh, thanks, we should do something about that page
-
andyfWe 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.
-
andyfand nobody was volunteering to maintain the AMIs
-
nomadLooking 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?
-
tsoomeprtconf -vd
-
nomadthanks... but where do I find the actual driver name in that wall of text?
-
andyf`/usr/lib/pci/pcieadm show-devs` is a nice way to display it, after installing the `diagnostic/pci` package
-
nomadthanks andyf. I presume in the following line the "mr_sas0" is the driver name.
-
nomad3b/0/0 PCIe Gen 3x8 mr_sas0 MegaRAID SAS-3 3108 [Invader]
-
andyf`mr_sas` is the driver, `0` is the instance number
-
nomadgreat, thanks!
-
nomadI'm adding diagnostic/pci package to my 'install everywhere' list.
-
richlowenomad: andy typoed, you want -D to show driver attachment
-
richlowe-d shows the pci.ids name
-
richlowe(and -v shows a wall of text)
-
richloweprtconf -dD might be closer to what you want
-
richlowe(especially for non-pci devices)
-
nomadthanks richlowe
-
nomadin this case I was looking for a PCI device but the info is useful.