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