[12:32] <Teduardo> Just fyi; the 12.10 installer has a big problem with the new Romley based intel matrix raid SCU
[12:33] <xnox> Teduardo: boot with nodmraid option.
[12:33] <xnox> and setup your md raid partitions before hand from bios. Or assemble those by hand.
[12:34] <Teduardo> im not actually using raid it is just enabled in the bios
[12:34] <Teduardo> causes all sorts of kernel errors to stream down the screen
[12:34] <xnox> Teduardo: hence the nodmraid boot option is for you, or you can do ubiquity --nodmraid from try ubuntu session.
[12:35] <Teduardo> that seems like more of a workaround to a bug in the installer kernel than an actual solution to the problem but im sure they'll fix it in a later release
[12:37] <xnox> Teduardo: by default we activate raid controllers, if they are detected. Previously it was unusual to have a raid controller, and if one was present it was intended / desired.
[12:38] <Teduardo> its fine to activate the controller but the devices behind the controller are pass-through
[12:38] <xnox> with intel matrix raid putting it on all motherboards is shifting the factors to the "my machine has this and I had no clue it did"
[12:38] <Teduardo> and it for whatever reason won't detect the disks
[12:38] <Teduardo> after streaming tons of errors down the screen
[12:39] <xnox> well it detects the disks, and correctly shows that no raid volumes were setup. And it's a bit silly and doesn't offer any way to create raid volumes, nor to deactivate them.
[12:39] <Teduardo> the OS has direct access to the devices though
[12:39] <Teduardo> so it's doing something wrong
[12:40] <Teduardo> even in the dmesg it sees sda, sdb, and sdc
[12:41] <Teduardo> but in the [!!] Partition disks screen the only option is configure iscsi volumes
[12:41] <Teduardo> wacky
[12:42] <Teduardo> wonder if it's because of the ssd i have attached
[12:42] <Teduardo> its a server thank god real easy to pull a disk =)
[16:28] <cr3> cjwatson: if I recall, you mentionned it was now possible to choose a network interface based on mac address. if so, how's that done?
[16:32] <stgraber> cr3: set netcfg/choose_interface to the mac address
[16:33] <zyga> woot, thanks
[16:33] <cr3> stgraber: you must be kidding, that's freaking awesome!
[16:34] <stgraber> cr3: I did a quick grep through netcfg's code and it looks like that should work (and matches what I remembered of choose_interface)
[16:38] <cr3> stgraber: where's the source for netcfg?
[16:38] <stgraber> cr3: apt-get source netcfg
[16:44] <cjwatson> or IPAPPEND 2 in pxelinux and it'll do it automatically
[16:45] <cjwatson> based on the pxe interfaces
[16:45] <cjwatson> s/s$//
[16:46] <zyga> cjwatson: is this supported since precise?
[16:48] <zyga> cjwatson: literally "IPAPPEND 2"
[16:50] <cr3> cjwatson: it prompts for the network interface, em1 or wlan0
[16:57] <cjwatson> zyga: since oneiric
[16:58] <zyga> cjwatson: which part is doing that? grepping various udebs that are network related yields no hits
[16:58] <cjwatson> netcfg
[16:58] <cjwatson> you won't find it grepping for IPAPPEND - that causes pxelinux to stick BOOTIF=<mac addr> on the kernel command line
[16:58] <zyga> cjwatson: there is no IPAPPEND in netcfg source
[16:59] <zyga> hmm
[17:00] <cjwatson> cr3: oh, yeah, try adding netcfg/choose_interface=auto too
[17:00] <cjwatson> to say "just use the default, don't ask me"
[17:00] <cr3> cjwatson: thanks!
[17:03] <cr3> cjwatson: that worked!
[17:05] <cjwatson> good good
[17:05] <cr3> cjwatson: we thought it might be more desirable to test with that than keep using the old eth* names with biosdevname=0
[17:06] <cr3> cjwatson: not only because it's simpler but also because eth* interfaces are probably going to be unsupported sooner or later
[17:09] <cjwatson> I don't see eth* going away in any reality terribly near mine, but sure, the closer you are to defaults the better
[17:10] <cjwatson> (biosdevname's support is only a certain fraction of hardware, and I haven't noticed it growing terribly rapidly)
[18:20] <pjotr> Hello, I have encountered a showstopper bug in Ubiquity:
[18:20] <pjotr> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1070485
[18:20] <ubot2> Launchpad bug 1070485 in ubiquity (Ubuntu) "Ubiquity switches sda and sdb in Grub configuration, causing boot failure" [Undecided,Confirmed]
[18:22] <pjotr> This happens only with USB stick installations, not with the DVD. However, Live USB's are becoming increasingly important as install media.
[18:24] <pjotr> cjwatson: maybe you could look into this?
[18:24] <pjotr> if you have the time, of course.... :P
[18:51] <cjwatson> pjotr: not at the moment; I have a solid three days' work to fit into two days of work time before UDS in order to get raring open and unblock the rest of the dev team
[18:51] <cjwatson> (don't know if you got the previous answer, since my client reconnected two minutes later)
[19:34] <pjotr> cjwatson: I only received your answer about UDS. Was there an answer before that?
[19:40] <cjwatson> pjotr: no, just that
[19:40] <cjwatson> I repeated it, but I expect only one got through
[19:40] <pjotr> OK. :-)
[19:41] <pjotr> Good luck with Raring!
[21:09] <Berend1232336432> Hi guys, wondering if I can I'm at the right place to get some answers about installing ubuntu 12.10 with LVM and an existing encrypted home directory
[21:09] <xnox> Berend1232336432: please read the release notes first, if they do not make sense come back for a clarification.
[21:11] <Berend1232336432> ok, I'll start there
[21:13] <Berend1232336432> you mean this page? https://wiki.ubuntu.com/QuantalQuetzal/ReleaseNotes/UbuntuDesktop#Installation
[21:15] <Berend1232336432> the Ubuntu Desktop Guide doesn't seem to help either
[21:16] <Berend1232336432> just one question then
[21:17] <Berend1232336432> couldn't find the bootable flag option anywhere while installing (using manual approuch)
[21:22] <xnox> Berend1232336432: yes that page. Known Issues, Installation, Third point.
[21:22] <xnox> The desktop image installer cannot unlock existing encrypted (LUKS) volumes. If you need to make use of existing encrypted volumes during partitioning, then use the "Try Ubuntu without installing" boot option to start a live session, open the encrypted volumes (for example, by clicking on their icons in the Unity launcher), enter your password when prompted to unlock them, close them again, and run ubiquity to start the installer. (1066480)
[21:24] <Berend1232336432> ok, thx
[21:44] <Berend1232336432> I'll go try that, thanks a lot!