[11:14] cjwatson: xnox: reported a couple of bugs bug #1195690 and bug #1195676 for ubiquity crashes today. I could not figure out if both are of the same cause though [11:14] Launchpad bug 1195690 in ubiquity (Ubuntu) "Exception in GTK frontend during preseeded default installations" [Undecided,New] https://launchpad.net/bugs/1195690 [11:14] Launchpad bug 1195676 in ubiquity (Ubuntu) "ubiquity crashed with BrokenPipeError in command(): [Errno 32] Broken pipe during manual saucy desktop installations" [Medium,New] https://launchpad.net/bugs/1195676 [12:46] Hi folks - I'm trying to netboot a 13.04 amd64, which works fine, loads the kernel, but then it does another DHCP. The kernel seems to prefer the 10G interface, how can I make the netboot interface (1G) the first it does dhcp from, and preferably get that one named eth0 ? [12:48] If I do 'ip link' in busybox, it shows that the 10G card is p1p1, but I want to boot from p2p1. [12:52] Peanut: https://lists.ubuntu.com/archives/ubuntu-devel/2012-August/035670.html might be relevant. [12:53] Peanut: there are pxelinux.cfg parameters you can specify and then installer will use the same interface it was booted from. [12:55] By default, I specify 'interface=eth0' in the kernel boot line. But in busybox, 'ip link' shows no ethX, only p1p1 etc. [12:56] Peanut: don't do that. as from 12.10 and up 'eth0' names are not used. if you want to return back to legacy ethX names you also need biosdevname=0. [12:57] Peanut: if a were you i'd use "IPAPPEND 2" in pxelinux.cfg and remove interface preseeding, then the correct interface (the one that pxeboot happened from e.g. p1p1 or something else) will be used during installation. [12:57] eth0> depends on your hardware [12:57] fwiw [12:58] though indeed if Peanut is seeing p1p1 etc. then that's hardware that biosdevname supports :) [12:59] Does this mean that after the install, the interface will still be called p1p? [13:02] I would normally expect so [13:03] But xnox is right that it's better to select by either or by mac address if you can [13:04] I'd prefer to keep the config generic for all machines that I kickstart. A bit of Googling turned up 'ksdevice=bootif', or is that kickstart-specific? [13:05] that's kickstart-specific although it is supported by Ubuntu's kickstart implementation [13:05] Ah ok, but I'm using preseeding, d-i - which is different from kickstart, I presume. [13:06] right. but you can use kickstart with Ubuntu's d-i, and even mix and match it with preseeding if you want. [13:06] https://help.ubuntu.com/13.04/installation-guide/i386/ch04s06.html#kickstart [13:07] how much you'll actually be able to achieve your goal of keeping the config generic I'm not certain. [13:07] but you might perhaps be able to get it closer. [13:08] Where does ipappend go? Under the entries for one particular kernel, or at the same level as DEFAULT etc. ? [13:09] Ah, I found an example.. seems to go between 'kernel' and 'append'. [13:19] With 'ipappend 2' and 'ksdevice=bootif' in the kernel options, I still end up on the 'configure the network' requester :-( [13:21] ksdevice=bootif only does anything if you're actually using kickstart [13:21] but there's an equivalent you can use with plain d-i preseeding [13:21] Ah yes, that's what I was afraid of. I also tried 'interface=bootif', but that didn't work either, it tried to configure a device with the name bootif. [13:21] cjwatson: that equivalent is what I'm trying to find :-) [13:22] * cjwatson tries to remind self [13:22] interface=auto ? [13:23] that's the one [13:23] by default ipappend 2 just sets what the default value for that dialog is, but doesn't actually say "... and accept that default automatically" [13:23] interface=auto is "accept default" [13:24] Ok, I'll try that next, thanks. [13:39] I just did a quick install, and my interfaces are indeed called p2p1 etc. [13:39] Not sure I'm happy about that change, but I bet this is not the place to complain about that :-) [13:48] cjwatson: Just did a reboot with 'interface=auto', that does the trick. The interface ends up being named p2p1 which will require some changes to puppet templates or udev rules, but we'll see about that later. Thanks anyway. [13:59] cjwatson, does this patch look any better? https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1178618 [13:59] Ubuntu bug 1178618 in grub2 (Ubuntu) "--hotkey option does not work when the menu is hidden" [Medium,Triaged] [14:00] https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1178618/+attachment/3701890/+files/ubuntu_quiet_hotkey.patch === kentb-out is now known as kentb [14:11] ara: maybe. I need to consult upstream [14:12] (my review was a first-pass review before forwarding a patch that upstream would reject ...) [14:15] cjwatson, cool, thanks for that. Let us know what upstream thinks === kentb is now known as kentb-afk === kentb-afk is now known as kentb