[00:22] <infinity> tron103: Define "the latest kernel"?
[01:16] <Fudge> thanks cyphermox  and cjwatson
[01:23] <cyphermox> Fudge: np. lemme see if I can find something out quick
[02:16] <Fudge> :)
[02:52] <cyphermox> there may be a trick, by enabling espeakup as a module early on (you'd need to add things to the command line, or roll your own d-i image)
[02:52] <cyphermox> but I found some hints that it might be broken because of kernel changes
[03:19] <cyphermox> Fudge: so, the additional command-line entry you'd probably need would be "modules=espeakup-udeb", but it's not shipped on the server CD, so in a current case, at best you'd have to get online somehow through the menus before it would download the udeb
[03:20] <cyphermox> so, the answer is most likely that if you want to make this work, for the time being it means building your own ISO if you want espeakup-udeb to be available
[03:21] <cyphermox> (or rebuild d-i, making it included in the mini.iso, but that means you'll need to bump the disk size it allows
[03:21]  * cyphermox goes to bed
[03:23] <tron103> I've installed ubuntu-server 14.04 with the 3.16.0-30-generic kernel and a custom network driver that is needed. Is there a way to build an initrd/kernel combo for this version? The downloaded netboot installer is an older version of the kernel and won't accept my kernel modules.
[03:24] <Fudge> cyphermox:  that is very helpful mate, thank you so much
[11:20] <infinity> tron103: There's no way the netboot installer uses an older kernel than that (In fact, I'm looking right now, and it's 3.16.0-45, currently).
[11:21] <infinity> tron103: You're building for a kernel that's 7 months old.
[16:19] <tron103> Infinity: My cd ISO installed ubuntu-server 14.04 is at 3.16.0-30-generic, the real problem is that the netinstaller initrd is version 3.13.0-24-generic at http://us.archive.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/netboot/netboot.tar.gz
[16:20] <cjwatson> you want to use trusty-updates not trusty
[16:20] <tron103> lol
[16:20] <tron103> why is that?
[16:20] <cjwatson> trusty is the version released with 14.04 on release day, it doesn't get updated
[16:20] <cjwatson> just like the archives, post-release updates go in trusty-updates
[16:22] <tron103> thank you cj, ill keep that in mind
[16:23] <tron103> I ended up finding the kernel-version specific modules and can now bring up the inifiniband interface, but it won't get dhcp for some reason. seems to only see ipv6
[16:24] <tron103> I could try and rebuild everything with http://us.archive.ubuntu.com/ubuntu/dists/trusty-updates/main/installer-amd64/current/images/netboot/ubuntu-installer/amd64/initrd.gz
[16:30] <tron103> wow... the current netboot is at 3.13.0-61-generc
[16:30] <tron103> grrr
[16:30] <tron103> still smaller than my install version
[16:31] <infinity> tron103: There are netboot directories for each of 3.13, 3.16, and 3.19
[16:31] <infinity> tron103: http://cdimage.ubuntu.com/netboot/trusty/
[16:32] <tron103> thank you a bunch for that
[16:32] <tron103> so I have to look at cdimage instead of the archive
[16:33] <infinity> tron103: That page links to the archive, it's just nicer than remembering the deep links.
[16:34] <tron103> ah. its something called "vivid"... not just trusty
[16:34] <infinity> tron103: 3.16 would be lts-utopic, actually, not lts-vivid.
[16:35] <tron103> right you are :)
[16:41] <tron103> nice. its 3.16.0-45-generic.
[16:42] <cjwatson> Not sure the lts-utopic kernel is still supported though, since utopic isn't
[16:43] <tron103> hmm now i wonder if the kernel modules from  3.16.0-30-generic will insert into 3.16.0-45-generic
[16:44] <cjwatson> No
[16:44] <cjwatson> At least I doubt it, the point of changing the ABI number is that the ABI changed
[16:44] <infinity> lts-utopic is supported until 3mo after 16.04 comes out.
[16:44] <cjwatson> infinity: oh really?  ok
[16:45] <infinity> cjwatson: Says so on the handy cdimage/netboot page. :)
[16:45] <infinity> So it must be true, cause I wrote it.
[16:45] <infinity> *handwave*
[16:45] <cjwatson> fair enough
[16:46] <infinity> cjwatson: But, basically, we support all the lts-N kernels until the .5 point release, where lts-next-lts becomes the only one supported with a highly-encouraged and annoying upgrade message.
[16:59] <tron103> thats a nope to inserting 3.16.0-30-generic modules into 3.16.0-45-generic
[17:00] <tron103> so my secret way of finding my compiled modules is to google: site:http://packages.ubuntu.com/ ib_addr.ko 3.13.0-24-generic
[17:01] <infinity> tron103: Err, wait.  What?  ib_addr should be included already, why do you need to compile your own?
[17:02] <tron103> ib_addr is not included in any of the netboot initrds ive looked at
[17:03] <tron103> and im not compiling them though, someone else helpfully did it and put it up on packages.ubuntu.com
[17:04] <tron103> I'm merely trying to add them into my netboot so i can bring up ib0 and dhcp it.
[17:05] <infinity> tron103: That "someone else" is us. :P
[17:06] <tron103> <3
[17:06] <infinity> tron103: But indeed, infiniband stuff seems to be missing from d-i.  Have you filed a bug about your use-case so we can fix it?
[17:06] <tron103> ... no, i just assumed noone cares about infiniband haha
[17:06] <tron103> how do i file?
[17:08] <tron103> if you guys add it, I've been reading in the mellanox documentation that a "specially compiled version of dhclient is needed". tho i'm not sure if that is true since the redhat dracut-based setup was able to np
[17:08] <infinity> tron103: "ubuntu-bug linux" and mention something about needing infiniband support in d-i.  It might not be something we can fix without some investigation (as you mention, it might be more than just pulling in some modules), but a bug is still nice.
[17:10] <infinity> tron103: Perhaps best to hold off on filing the bug until you've proven yourself that adding some modules does or doesn't work, so you have a bit more data for us than just "please fix".
[17:10] <tron103> yeah
[17:10] <tron103> just setting up launchpad for now
[17:10] <infinity> tron103: Especially since I think we have exactly two machines with the right hardware to test, and I don't have access to them, so I'd be working slightly blind. :P
[17:11] <tron103> again, i'm able to bring up the interfaces once I load the 10+ modules in the super-specific order
[17:11] <tron103> its just no dhcp
[17:11] <tron103> sigh
[17:12] <tron103> maybe itll work on this new kernel
[17:13] <infinity> Bah, who needs DHCP?  Kids and your modern whiz-bang gadgets.
[17:13] <tron103> theforeman uses it to provision
[17:13] <infinity> (I was being sarcastic)
[17:13] <tron103> thank you for your help tho infinity and cj
[17:16] <infinity> apw: Actually, you might know, since Chris seems AFK and you decided to join. :P
[17:16] <apw> heh ... i missred the line and alert :)
[17:16] <infinity> apw: We have a user here who's trying to do infiniband in d-i which, at the very least, requires a bunch of modules we don't ship in the initrd.
[17:17] <infinity> apw: Chris was working with people on that at some point, right?  I feel like we also needed userspace changes that we've not yet made, but I have no idea if someone has a checklist of stuff that still needs doing.
[17:17] <apw> yeah i think you had the right victom :)
[17:17] <apw> i think i think the same as you, but have no details for you
[17:17] <infinity> Fair enough.
[17:18] <infinity> tron103: So... WIP, no ETA.  But I'll poke around to see if it got stalled/forgotten. :P
[17:18] <infinity> Would certainly be nice to sort it by 16.04, if feasible.
[17:19] <tron103> jah jah. I'll probably get infiniband support. I'll make sure to post the fix..... somwhere
[17:19] <infinity> arges: Oh sure, join now, after I grill Andy on your behalf.
[17:19] <infinity> apw: We have a user here who's trying to do infiniband in d-i which, at the very least, requires a bunch of modules we don't ship in the initrd.
[17:19] <infinity> apw: Chris was working with people on that at some point, right?  I feel like we also needed userspace changes that we've not yet made, but I have no idea if someone has a checklist of stuff that still needs doing.
[17:19] <infinity> arges: ^-- s/apw/arges/
[17:20] <arges> infinity: ok let me try to remember which bug this was...
[17:20] <infinity> arges: And, to be clear, I think he's doing IPoIB, not using any ethernet emulation layers.
[17:20] <infinity> arges: And, AFAIR, pure IB support was still a WIP.
[17:20] <tron103> yes. ipoib is correct
[17:21] <infinity> tron103: FWIW, I think doing ethernet or whatever on mellanox cards Just Works, which might be a workaround.  Run d-i in ethernet emulation mode, switch to IB post-install.
[17:21] <arges> infinity: bug 1469482
[17:21] <infinity> tron103: Though you might still hit the DHCP issue on the installed system.
[17:23] <infinity> arges: Oh good, a proper bug.
[17:23] <infinity> tron103: You might want to just subscribe to that bug instead of filing a new one.
[17:23] <infinity> arges: I suspect there are still userspace changes we need to make too, to enable DHCP over IB.  But I guess we'll find out, if someone's actually working on testing this.
[17:23] <arges> infinity: yea so tinoco was going to work on that and give some proper information about impact etc. He has access to the hardware which makes it a bit easier for him to confirm
[17:24] <infinity> arges: Thanks for the pointer, at any rate.
[17:25] <tron103> subscribed. Thank you arges infinity!
[17:27] <arges> no problem
[18:00] <tron103> smh. on the initrd of 3.16.0-45-generic, modprobe ib_ipoib just hangs lol. Guess ill go back to 3.13.0-x
[18:13] <tron103> yes!
[18:13] <tron103> nm I got it
[18:13] <tron103> ib_ipoib doesn't hang when I don't screw with modules.d
[18:17] <tron103> to recap: when using the 3.16.0-45-generic initrd.gz (aka utopic), manually loading the infiniband modules allows me to use dhcp with ipoib
[18:18] <tron103> last question: how in the world do I get my script that loads the modules in the proper order to run at init time before the installer tries to detect my net hardware?
[18:18] <tron103> sorry if thats a super n00b question, I just can't figure it out
[18:20] <tron103> anyone in pacific northwest? I'll get a round
[21:05] <tron103> so how do I properly load my infiniband modules during netboot? I added them to /init but it just gives kernel panic and hangs....
[21:06] <tron103> (added right before the last line that says exec $init)
[21:07] <tron103> lib/debian-installer[-startup].d/S99loadinfiniband didn't run as well as adding in a line for inittab