[01:46] <rexxx> #join tor
[02:22] <Angelus> if i compiled a kernel using make-kpkg not usib debian/rules script. and i wanna compile the restricted-modules. what abi version should i put in the control script of the restricted-modules?
[02:23] <Angelus> sorry i disconnected by mistake
[02:24] <Angelus> so my question was: if i compiled a kernel using make-kpkg not using the debian/rules script, and i wanna compile the restricted-modules, what abi version should i put in the control script of the restrected modules ?
[02:28] <Angelus> sorry , i meant what abi version should i put in the debian/rules script of the restricted-modules
[07:51] <kraut> moin
=== zul_ is now known as zul
=== asac_ is now known as asac
[09:40] <Daviey> Hey, anybody tinkered with 2.6.24-rc1 here?
[09:52] <havoque>  is there some boot parameter that should be entered at the gutsy install prompt to force the use of old pata drivers, because with the default install options the new libata subsystem loads, thus treating my hdd as sda instead of hda, and imposes a limit of 15 partitions, i have 20, and want to install gutsy in hda17(/) and hda 18 (/home)?
[09:53] <havoque> i don't know where to ask this question really
[10:04] <fdv> Hi. anybody know how to specify a custom name suffix when building a kernel using debian/rules? https://help.ubuntu.com/community/Kernel/Compile doesn't really get into that, and the result isn't really named any differently from the stock kernels either.
[10:04] <fdv> sorry if this is the wrong channel for support requests like this
[13:57] <sridhar> hi everbody, I need to create live come install CD for our distro which is based on debian, but iam following the procedure of "https://help.ubuntu.com/community/LiveCDCustomization", but iam getiing error, while loading kernel " /init: .: 163: Can't open /scripts/casper  Kernel panic - not syncing: Attempted to kill init!" plz
[14:12] <gene6482> if there is a bug in the kernel (already reported) is this where one would go to discuss it?
[14:13] <abogani> sridhar: You must install casper package into squashfs file.
[14:19] <JanC> gene6482: in theory, yes, but the developers are at the UDS in Boston
[14:20] <gene6482> JanC: thanks, I'm just trying to get my sound working and apparently it's a kernel bug, and I'm bashing my head off a wall trying to figure it out :-)
[15:15] <zul> lamont: you are evil
[15:30] <lamont> zul: ??
[15:30] <lamont> what did I do now/
[15:30] <lamont> ?
[15:30] <zul> lamont: you were talking about that planet post..
[15:30] <lamont> oh
[15:30] <lamont> ok
[15:31]  * zul is listening in btw
[15:32] <zul> noooooooo..
[15:41] <gene6482> i have an issue where even though i use a custom dsdt(worked with feisty - toshiba p100) the kernel seems to ignore it and thus i have no sound, any ideas?
[15:46] <zul> BenC: is is just going to be -generic for the daily builds?
[15:48] <gene6482> this is the url for the bug https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/136469
[15:49] <ubotu> Launchpad bug 136469 in linux-source-2.6.22 "toshiba p100 series dsdt acpi error no sound, works with acpi turned off." [Medium,Triaged] 
[15:56] <lamont> zul: generic only in the daily builds
[16:25] <fritsch> I found two patches applied in 2.6.22-14-generic which break suspend to ram on my thinkpad system (on this model for everybody else), i have filed this as a bug
[16:25] <fritsch> should i provide a patch which reverts these two patches?
=== asac_ is now known as asac
=== asac_ is now known as asac
[17:06] <Daviey> Where can i find the Hardy git tree?
[18:03] <Hammerhead> anyone using shfs and Fiesty?
[18:03] <Hammerhead> Hello all  BTW
[18:03] <Hammerhead> Can't get it to suild
[18:05] <Hammerhead>  make[4]: *** [/usr/src/modules/shfs/Linux-2.6/dir.o] Error 1               ▒
[18:05] <Hammerhead>                 │ make[3]: *** [_module_/usr/src/modules/shfs/Linux-2.6] Error 2             ▒
[18:05] <Hammerhead>                 │ make[3]: Leaving directory `/usr/src/linux-headers-2.6.20-16-generic'      ▒
[18:05] <Hammerhead>                 │ make[2]: *** [default] Error 2                                             ▒
[18:05] <Hammerhead>                 │ make[2]: Leaving directory `/usr/src/modules/shfs/Linux-2.6'               ▒
[18:05] <Hammerhead>                 │ make[1]: *** [binary-modules] Error 2                                      ▒
[18:05] <Hammerhead>                 │ make[1]: Leaving directory `/usr/src/modules/shfs'                         ▮
[18:05] <Hammerhead>                 │ make: *** [kdist_build] Error 2  
[18:05] <Hammerhead> sorry for the paste
=== ivoks_ is now known as ivoks
[20:21] <TheMuso_Boston> 1/c
[20:22] <TheMuso_Boston> ugh
[23:06] <havoque> is there some boot parameter that forces the gutsy install process to use the old ide drivers rather than the new libata subsystem which treats hda as sda and thus limiting the number of allowed partitions to 15, i have 20 partitions as i am a multidistro user/tester and can't install gutsy at the moment, my hdd is pata, not scsi
[23:06] <mjg59> No
[23:07] <havoque> so, no gutsy for me?
=== ivoks_ is now known as ivoks
[23:26] <Mithrandir> you could just use lvm instead of a bajillion partitions
[23:30] <havoque> isn't lvm for peeple who have not already configured partitions?
[23:33] <fdv> I've added a string to EXTRAVERSION in debian/rules.d/0-common-vars.mk. This works when compiling and installing, but apparently not when building debs (compiled using 'AUTOBUILD=1 fakeroot debian/rules binary-debs'). Does anybody know where this is governed?
[23:35] <fdv> or, I might be mistaken, it might not be the deb compilation that fails, but rather the initrd step
[23:41] <fdv> the point is that at some point in the installation process, files are expected to be found under 2.6.22-14-386, rather than 2.6.22-14-386-slab (as I set EXTRAVERSION to 14-386-slab), meaning there must be someplace else I need to update as well
=== chuck__ is now known as zul
[23:57] <gene6482> is there a place where one could check on changes between kernel versions, i have a regression in audio support since i've upgraded to gutsy and it appears to be kernel related, wasn't sure where to go (bug is already filed)
[23:58] <havoque> when will, and will ever, libata-pata allow more than 15 partitions