=== asac_ is now known as asac
=== alex_jon1 is now known as alex_joni
[15:08] <_gAri-> hi there, can please someone help me how can I get the kernel patches of ubuntu individually, not a whole big patch? I just cloned the git repository
[15:10] <mjg59> _gAri-: git log will show you the logs. git show hashvalue will then give you the individual patch associted with that commmit.
[15:13] <_gAri-> hm I do not need a patch associated with one commit, I need a patch that consists of apparmor for example
[15:13] <smb_tp> _gAri-, And git-format-patch -o <dir> "<from id>..<to id>" will write individual patches to the dir you give. E.g. "git-format-patch -o .. Ubuntu-2.6.24-21.40..HEAD" will write all patches since the commit tagged as that release...
[15:14] <_gAri-> any way to achieve that?
[15:15] <mjg59> _gAri-: No
[15:16] <mjg59> There isn't "an apparmor patch". There's a series of commits that result in apparmor in the Ubuntu kernel being in its current form.
[15:16] <smb_tp> _gAri-, No, mjg59 is right. You will have to search for "apparmor" in the commit msgs and gather yourself
[15:17] <pwnguin> a simple grep of git log should do the trick
[15:24] <maks> apparmor is not of much use anyway
=== maks is now known as maks_
=== mkrufky is now known as mkrufky-lunch
[18:37] <hyperair> hello there. does anybody notice that the 2.6.24-21 kernel for hardy doesn't seem to work with bluetooth?
[18:37] <hyperair> i'm using a lenovo y410 with integrated broadcom bluetooth
[18:38] <hyperair> lsusb doesn't show anything when press the bluetooth button
[18:38] <hyperair> Fn+F6
[18:40] <adamwood> hyperair: is this new with the -21 kernel?
[18:40] <hyperair> yeah
[18:40] <hyperair> with the -20 kernel it works
[18:42] <hyperair> adamwood, ^
[18:43] <adamwood> hyperair: is it similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/90955 
[18:45] <hyperair> nope
[18:45] <hyperair> nothing appears in the acpid log
[18:48] <adamwood> hyperair: I'll have to get my bluetooth adapter out and see if it still works. Can you file a new bug in launchpad for this and attach your logs?
[18:48] <hyperair> what logs?
[18:48] <hyperair> my logs don't show _anything_ related
[18:48] <hyperair> nothing changes
[18:48] <hyperair> there's just no response
[18:48] <hyperair> and lsusb doesn't show anything
[18:48] <hyperair> what kernel modules are involved?
[18:49] <adamwood> hyperair: There is a list of logs that are useful for bug reports here - https://wiki.ubuntu.com/KernelTeamBugPolicies
[18:50] <adamwood> hyperair: typing lsmod will tell you which modules you are using
[18:50] <hyperair> yeah but which are the bluetooth modules
[18:50] <hyperair> adamwood, ^
[18:51] <hyperair> need i do lspci in this case?
[18:51] <hyperair> bluetooth stuff goes in usb don't they?
[18:51] <adamwood> hyperair: they can also be pcmcia I think.
[18:51] <hyperair> oh
[18:52] <hyperair> well mine appears in lsusb when in -20
[18:52] <hyperair> as if it is suddenly plugged into a usb slot
[18:52] <adamwood> hyperair: for usb I think the hci_usb.ko module is a core module
[18:52] <hyperair> socket*
=== mkrufky-lunch is now known as mkrufky
[18:53] <hyperair> adamwood, is there anything in the kernel that controls the Fn keys?
[18:53] <hyperair> there isn't any dmesg log entries when pressing the button
[18:53] <hyperair> and lsusb doesn't work either
[18:55] <adamwood> hyperair: as far as I know they act like most other keys but maybe some laptops work differently. I'm pretty sure there isn't an "event" that tells the kernel to load the modules that can be caused by pressing the keys
[18:56] <hyperair> the so-called "event" is the same event as plugging in an external bluetooth module
[18:56] <hyperair> you get the whole lot of dmesg initialization messaegs
[18:56] <hyperair> *messages
[18:56] <adamwood> hyperair: Some laptop FN keys can start and stop power getting to a device which makes it look to the kernel like it's being plugged in or out
[18:56] <hyperair> yeah that's probably how it's done
[18:56] <adamwood> hyperair: yeah, are you seeing anything in dmesg?
[18:57] <hyperair> nope
[18:57] <hyperair> not at all
[18:57] <hyperair> [  577.021928] usb 7-4: new high speed USB device using ehci_hcd and address 4
[18:57] <hyperair> [  577.053077] usb 7-4: configuration #1 chosen from 1 choice
[18:57] <hyperair> [  577.053458] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (04f2:b008)
[18:57] <hyperair> this is what happens when i do the Fn+Esc (turn on/off webcam)
[18:58] <hyperair> [  584.033429] usb 7-4: USB disconnect, address 4 <-- this s what happens when it's turned off
[18:58] <hyperair> similar stuff happens with bluetooth in -20
[18:58] <adamwood> hyperair: can you boot a -20 kernel and check which module is being loaded?
[18:58] <hyperair> mm
[18:58] <hyperair> oka
[18:58] <hyperair> i'll take al ook
[19:03] <hyperair> okay i'm back
[19:03] <hyperair> this time in -20
[19:03] <adamwood> welcome back
[19:04] <hyperair> [  162.144186] usb 1-2: new full speed USB device using uhci_hcd and address 2
[19:04] <hyperair> [  162.160429] usb 1-2: configuration #1 chosen from 1 choice
[19:04] <hyperair> [  162.293854] Bluetooth: HCI USB driver ver 2.9
[19:04] <hyperair> [  162.295278] usbcore: registered new interface driver hci_usb
[19:04] <hyperair> bluetooth              61156  7 hci_usb,rfcomm,l2cap
[19:04] <hyperair> lsmod said that
[19:04] <hyperair> lsmod | grep blue
[19:05] <adamwood> hyperair: try lsmod | grep bcm
[19:05] <hyperair> nothing
[19:06] <adamwood> my broadcom bluetooth device uses bcm203x module
[19:06] <hyperair> is it?
[19:06] <hyperair> ah well
[19:06] <hyperair> can you modinfo hci_usb?
[19:06] <adamwood> hyperair: yours could be different
[19:06] <hyperair> it seems mine is 2.9
[19:07] <adamwood> hyperair: I think you need to file a launchpad bug with all the information because I don't think we can fix this quickly
[19:07] <hyperair> okay
[19:07] <hyperair> file against what package?
[19:08] <hyperair> adamwood, could you try running modinfo hci_usb and see if what that tells you?
[19:08] <hyperair> s/if//
[19:08] <adamwood> hyperair: version 2.9 - but that doesn't mean much
[19:09] <adamwood> hyperair: as for the package file it against Linux (ubuntu hardy). I think....
[19:10] <hyperair> okay
[19:26] <hyperair> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/259151
[19:26] <hyperair> oh damn he went
[22:10] <sander_m> Hi all. Does the 8.04 Live CD kernel have support for LVM? I'm trying to acess the LVM volumes on my hard drives using the Live CD but I can't make it go. It doesn't find the device maper kernel module
[22:17] <smb_tp> sander_m, I cannot really speak about the CD. If "sudo modprobe dm-mod " fails it might have been thrown away to save space...
[22:18] <sander_m> It fails....
[22:18] <sander_m> :-(
[22:20] <smb_tp> sander_m, This is normally part of the linux-image package. I wonder if you can apt-get that on the live system...
[22:25] <sander_m> Yeah, i works :-)
[22:26] <smb_tp> sander_m, Then you only have to apt-get lvm2 and might be happy. :)
[22:26] <sander_m> Did that already and found out that the mapper was missing. I can access my LVM now :-)
[22:30] <chris_goe> _ruben: re: CONFIG_MD_RAID10, a bit late, but: thanks, I shall use a different kernel then
[22:30] <chris_goe> I think I've installed jeos, and CONFIG_MD_RAID10 was not enabled.
[22:40] <sander_m> Do you guys also happen to know about making mdadm find existing devices on a Live CD? I have a working mdadm.conf but mdadm says it can't find any devices