[01:53] <Frogging101-chan> In kernel 4.2.1 from kernel.ubuntu.com, 0001-base-packing.patch has "+drivers/scsi/scsi_dh.ko" in generic.inclusion-list. I think it's supposed to be "+drivers/scsi/device_handler/scsi_dh.ko", since that's where that file actaully is
[01:53] <Frogging101-chan> And in 4.2 it has the subdirectory in the path
[01:53] <Frogging101-chan> Because when I try and build it, I get errors about that file not being found
[01:54] <Frogging101-chan> 4.2 works, 4.2.1 doesn't
[01:58] <Frogging101-chan> So, why was that changed? The file is still where it was before, but the path is now wrong
[07:30] <silidan> apw: i suppose they did not yet contact you?
[07:31] <silidan> apw: i mean manufcaturer/dev of camera SDK with the short URB broblem
[07:41] <apw> Frogging101-chan (N,BFTL), we build all of those without extras to avoid that kind of things, you should too ... add do_extras_package=false
[07:41] <apw> silidan, no they did not
[10:17] <silidan1> apw: did they contact you?
[10:32] <silidan1> apw: i found an open source capture application which also implements an open source low level access to the camera via libusb, the essential call to libusb_bluk_transfer is definitly made with the right size (1228800 bytes = 1280x960x1byte), the URB in wireshark still report a length of 61504, with the URB containing: "URB Length = 1228800" and "Data Length = 61440" interesting.. 
[10:38] <silidan1> apw: could this short URBs data length be a limitation of usbmon itself?
[10:58] <silidan1> apw: according to gdb, the libusb_bulk_transfer call returns with exactly the amount of data it expected...
[11:45] <apw> silidan1, it is possible that is a capture length, strace has a similar thing, you can often change it
[12:00] <silidan1> apw: any hint how? there seems to be no manpage for usbmon, at least on my system
[12:01] <apw> silidan1, sorry no
[12:12] <silidan1> apw: can you point me where i should ask about usbmon if not here?
[12:19] <apw> silidan1, sorry i have no additional info on that tool
[12:40] <silidan1> does anyone here know if the usbmon kernel module has a limitation on the size of captured frames?
[12:41] <silidan> does anyone here know if the usbmon kernel module has a limitation on the size of captured frames?
[12:55] <TJ-> silidan: look at the drivers/usb/mon/ source
[12:57] <TJ-> silidan: default buffer for binary capture looks to be ~300KB, and the max 1.2MB, but it looks like that is in total, not per-packet
[13:49] <silidan> apw: a little question, lets assume in my app is using libusb, i know i want to receive 30fps from my camera and my camera can provide them. Can I just issue 30 libusb_bulk_transfers every second to achive that? 
[13:49] <apw> silidan, i have no idea, but in their sceario they are sending continious packets without having to receieve one, which makes a difference
[13:50] <silidan> apw: you refer to their winxp scenario?
[13:50] <apw> yes
[13:51] <silidan> apw: but arent these receiveing bulk transfer also issued from the host controller via URBs? i mean doesnt just the app send the URB for bulk in, and waits for the kernel to basically return it with data in?
[13:52] <apw> silidan, nope, it sends some vendor specific control message at the start, and never speaks again
[13:53] <silidan> apw: but usb 2.0 devices cant initiate a bulk transfer on their own.. this is done from host side if im not mistaken... like host asks device for bulk transfer... waits till device sendit, and returns the data to the app.. 
[13:53] <apw> silidan, that is not what the trace says
[13:54] <silidan> apw: but the trace just reports the URBs send to the kernel and their contents, the kernel operates based on that data, ie reads from it or writes to it and then just issues a callback if i got that right from reading so far?
[13:55] <silidan> apw: o wait, you said trace, you meant the strace output?
[16:00] <mikkqu> hey there, can i have some help?
[16:01] <mikkqu> i have latest ubuntu version available and i want to recompile the kernel with custom parameters
[16:01] <jpds> Why?
[16:01] <mikkqu> is there any easy way to achieve that? i failed at "sudo apt-get source linux-image-`uname -r`" step
[16:02] <jpds> mikkqu: https://help.ubuntu.com/community/Kernel/Compile
[16:02] <mikkqu> actually, there are two points why: 1. for learning purposes and to find out how it works in ubuntu, 2. i just want to experiment with option MODULE_FORCE_UNLOAD to be able to unload broken modules
[16:02] <mikkqu> and I know that's not safe, i just want to get some experience with that
[16:04] <mikkqu> jpds: I've seen the page, but there is no (yet) instructions for 15.04 which I have
[16:04] <jpds> mikkqu: I can't imagine that they change that much
[16:04] <mikkqu> I'm stuck with downloading the kernel source archive for my currently using kernel
[16:04] <mikkqu> there is a necessary step for obtaining the source: sudo apt-get source linux-image-`uname -r`
[16:04] <mikkqu> and it's just don't work for me for some reason
[16:05] <mikkqu> Picking 'linux-lts-raring' as source package instead of 'linux-image-3.8.0-19-generic'
[16:05] <mikkqu> E: Unable to find a source package for linux-lts-raring
[16:05] <mikkqu> maybe I need to have some special repository enabled for that?
[16:05] <mikkqu> and I have no clue why it suggesting me to pick "linux-lts-raring" which is not found anyway
[16:07] <jtaylor> mikkqu: are you on ubuntu 12.04?
[16:07] <mikkqu> no, i'm on the latest available, (not lts) - 15.04
[16:07] <mikkqu> according to lsb_release -a
[16:07] <jtaylor> and running a 3.8 kernel?
[16:08] <mikkqu> yes, it's just by default. i didn't touch anything
[16:08] <mikkqu> since i've installed the latest upgrade
[16:08] <jtaylor> hm 15.04 should use 3.19
[16:09] <jtaylor> use apt-get source linux and you should get the latest source for 15.04
[16:09] <mikkqu> hmm.. that makes sense actually. i've been tricked that 3.8 is latter than 3.19
[16:09] <jtaylor> if you need 3.8 you have to download it manually from launchpad
[16:09] <mikkqu> but now I see that it's not
[16:10] <mikkqu> i think i should switch my kernel to 3.19 first, then
[16:14] <mikkqu> hmm.. i 100% remember i did "sudo apt-get dist-upgrade" (actually, two times)
[16:14] <mikkqu> why my kernel wasn't switched automatically?
[16:15] <jtaylor> maybe you removed the linux-generic package so it didn't upgrade
[16:16] <mikkqu> ops, looks like you're right
[16:18] <arges> rtg: whats the numbering scheme for the raspi tags in ubuntu-wily git tree
[16:18] <arges> rtg: 1008 is the starting ABI and will just grow
[16:18] <arges> ?
[16:18] <rtg> arges, monotonically increasing ?
[16:19] <arges> rtg: ok, just making sure (since its the first one). thanks
[16:20] <rtg> arges, we used to have some package name conflicts, so haveing an ABI number like this is a bit historical. blame it on ppisati (cause he's not here)
[16:21] <arges> gotcha
[17:11] <bjf> jpds, https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel is often an easier starting point for folks wanting to build their own kernel
[17:23] <rtg> jsalisbury, https://bugs.launchpad.net/ubuntu/wily/+source/linux/+bug/1440103/comments/16
[17:25] <jsalisbury> rtg, awesome.  Thanks!
[17:29] <mikkqu> thanks guys, i've updated to the latest kernel and i've been able to download ubuntu kernel sources with apt-get source
[17:30] <mikkqu> there is a directory called "linux/", and some gz archive "diff.gz", i guess it's diff between ubuntu and vanilla linux kernel
[17:30] <mikkqu> i think, it's already applied to the files in "linux/" directory? no need to apply it, so it's just for reference?
[17:31] <mikkqu> when i'm trying to run "fakeroot debian/rules editconfigs" i still getting a lot of errors
[17:32] <mikkqu> i'm getting the same errors as in this question, created a month ago. would be great if you could take a look
[17:32] <mikkqu> http://unix.stackexchange.com/questions/225020/check-config-errors-on-linux-3-19-0-kernel-configured-under-ubuntu-15-04-x86-64
[17:41] <mikkqu> ok, it worked in the "old-fashioned" way
[17:45] <apw> mikkqu, i owuld normally recommend you start from the git repository rather than a source packag
[17:45] <apw> mikkqu, as that is what we all do when working with the very same source
[17:52] <mikkqu> apw: hmm, yeah, git might be a more convenient way, but I'll try to stick to packaging method just this one time
[17:52] <mikkqu> how it'll work well. i should probably modify grub somehow, to be able to choose between kernels in case of fail
[17:53] <apw> mikkqu, some of the permissions bits get lost in the package on things you use when modifying the package 
[17:53] <apw> mikkqu, so don't be supprised
[17:54] <mikkqu> apw: i guess, in case of permission problems, the worst case is just the broken build near the end
[17:55] <mikkqu> but something still could go wrong
[17:57] <mikkqu> never thought kernel build takes so much time. is it possible to shorten the build time with ccache or something like this? in case if you have to build it a lot?
[18:19] <apw> mikkqu, to build it "the way the archive does" is tricky to do those tricks
[18:19] <apw> mikkqu, then again i normally build in a PPA because that uses someone elses compute
[18:32] <mikkqu> oh crap! build actually failed, after about an hour of work
[20:32] <th3s3_3y3s> What process runs bluetooth or is it in kernel?
[20:57] <th3s3_3y3s> The thing crashes and respawn.
[20:58] <th3s3_3y3s> And says bluetooth process is it talking about bluetoothd?
[21:22] <th3s3_3y3s> Mbp
[22:36] <th3s3_3y3s> Looks like btusb is disabled
[22:36] <th3s3_3y3s> It doesn't load where is the block list?