[13:36] <xnox_> cking: apw: i got a new laptop. Booted xenial proposed ubiquity image, it did not find nvme hard drive. did a modprobe of nvme module, that didn't bring up any hard drives
[13:37] <cking> xnox_, let me check that on my nvme enabled kit
[13:38] <xnox_> this is skylake
[13:38] <xnox_> dell xps 15, not sure how to find more info about the drive
[13:38] <xnox_> 4.3.0-2-generic kernel
[13:39]  * cking shoves a drive in a spare box and gives it a spin
[13:41] <cking> xnox, i've just managed to mount an Intel nvme drive with 4.3.0-2, so perhaps it's drive specific
[13:42] <cking> xnox, lspci -v perhaps, assuming it is on the pci bus
[13:44] <xnox_> oh, i have a raid controller
[13:45] <xnox_> and nothing else
[13:46] <cking> hrm, interestingly, 4.4.0-rc3  can't see my drive either
[13:47] <cking> xnox_, i'm not sure, it seems 4.4 has an issue with my system so I can dig into that one
[17:10] <attente> hi, does anyone know why building the linux-image-4.3.0-custom-dbg takes so long?
[17:29] <apw> attente, it is humungous ?
[17:30] <apw> attente, it has something like 5G of stuff in, which then gets compressed
[17:53] <attente> apw: is there a way to disable it? i'm building it with make deb-pkg
[17:54] <apw> attente, there is i think
[17:55] <apw> skipdbg=true
[17:59] <attente> apw: is that an env var?
[18:03] <apw> attente, something you can change in the rules, or pass to them
[18:04] <attente> apw: ok, i'll try it, thanks
[19:09] <smoser> why does /proc/partitions print information in 1024 byte size ?
[19:10] <apw> smoser, ?
[19:10] <smoser> just came to find this significant as i realized that its size *1024 differed from that reported by blockdev --getsize64 or /sys/class/block/vda/vda1/size
[19:10] <smoser> (by 512 bytes)
[19:11] <smoser> just curious if there is any significance to the fact that /proc/partitions shows units of 1024.
[19:11] <smoser> http://paste.ubuntu.com/13902677/