13:33:49 #join #omnios 14:23:47 as there been some talk about Intel nics for a couple of days, but nothing (yet) today.. I have a ixgbe / Intel 82599 that I've tried for a couple of days to accept an unsupported SFP+ transceiver. I've ad-hoc modified the /kernel/drv/ixgbe.conf for several times now, but it wont apply the allow_unsupported_sfp = 1 which I from a thread dated in November 2016 saw hints about a less restrictive 14:23:53 declaration together with unit-address only.. the driver won't apply that; In afterlight I would have gone for a chelsio from what I've read.. but ebay found this nic for my motherboard.. I feel puzzled about the name= and parent= construct - in my case it seeems parent is pci8086 which doesn't feel right to me :/ 14:26:09 My setup https://pastebin.pl/view/8843f039 - in my interpretation it should then be rewritten as: name = "pciex8086,10fb" parent = "/pci@0,0/pci8086,\6f08@3" unit-address = "2" ? 14:32:49 you should be able to just allow it globally.. that might be easier than trying to get the notation to apply it to just one NIC 14:41:10 That was my thought, as I will never care about supported gbics at home (and the other ixgbe controller which is built-in is 10GBASE-T anyway).. I restored the file and ran: echo "allow_unsupported_sfp = 1;" >> /kernel/drv/ixgbe.conf but it dont care: "Sep 29 16:35:45 lunar ixgbe: [ID 611667 kern.warning] WARNING: ixgbe2: Unsupported SFP+ module detected. Please replace it with a supported SFP+ module 14:41:16 per Intel documentation, or bypass this check" 14:57:18 what distro? 15:03:38 omnios 15:05:46 you might need to do 'bootadm update-archive'.. but it will require a reboot regardless after making the change 15:06:16 (techincally there are ways around doing a reboot, but it can get complicated) 15:08:13 (while not 100% true, generally the .conf files are used when the driver is loaded, so changes made after that won't take effect until the driver is reloaded) 16:00:26 I forgot about the 'bootadm update-archive v' which contained a ` changed /kernel/drv/ixgbe.conf 16:03:27 but still, no change after a reboot. And no worries about reboot here.. this is my 4th capable Linux-hypervisor that ends up becoming a illumos instead very recently, and I lost my unix beard anyway when family member this weekend rebooted my server as a first resort (when it should've been the last).. :-) 17:51:56 jbk: I tried to ppt it to a bhyve FreeBSD guest but their driver responds with similar message with the similar method.. so I might have to get that Intel gbic instead.. Thanks for your suggestion anyhow! 17:57:27 the driver source for most platforms (including illumos) derives from code provided by Intel, so I'm guessing that check is probably in that common code that everyone is using 18:00:47 [illumos-gate] 15006 Implement pre-auth integrity for fksmbd -- Gordon Ross 18:12:46 yeah, but through websearches I saw suggests that this Intel driver is a disaster apparently with different teams / code bases for each platform and that both the illumos/FreeBSD versions was inferior (and I've been foolish to think that Intel always was a stable choice) 18:16:23 [illumos-gate] 13923 zpool list -v output is misaligned -- Brian Behlendorf 19:02:27 [illumos-gate] 15020 HBA_LoadLibrary needs to close config file when done -- Rick McNeal 19:20:20 I even tried a ppt to a Linux bhyve guest.. same same.. while at the same time a DAC works in the same port.. so time for some more ebay shopping :) 20:34:07 hrm.. is it me, or would requesting the results of a query be paged into groups of X suggested you want to process the results in groups of X? 20:34:25 and not say 'gather all the results, and then return all of them' 20:35:05 which would seem to defeat a major point of paginating results