=== thegodfather is now known as fabbione === \sh_away is now known as \sh [09:06] moin [09:37] Hello all [09:38] Any here who can enlighten me about Hardy, the tg3 driver and a Sunfire T1000 (sparc)? [12:34] Good morning people [12:35] hey BenC [12:36] hello :) === \sh is now known as \sh_away === \sh_away is now known as \sh [14:08] is there a git tree for lrm ? [14:09] alex_joni: No [14:09] BenC: ok, thanks. any pointers how it's handled? [14:09] alex_joni: Like normal packages [14:09] apt-get source ... [14:09] just apt-get source, update locally, repush ? [14:09] Yeah [14:09] yeah, ok.. thanks [14:12] BenC: I managed building kernel packages the "ubuntu" way (using apt-get source and debian/rules) [14:12] BenC: how do I create a new source package with all my changes? [14:12] I'm surely overlooking something, but can't find any info in the wiki or the source itself.. [14:13] dpkg-buildpackage -rfakeroot -S [14:14] alex_joni: what's the new source package for? [14:14] people that want to replicate my work mainly (so GPL compliance) === cjwatson_ is now known as cjwatson [14:29] BenC: the kernel packages alex_joni and I are working on have the "adeos ipipe" patch added. Our application uses rtai for realtime control. [14:30] jepler: sounds interesting [14:32] the infrastructure to help us make custom kernels seems to be improving with each ubuntu release (we've done 5.10, 6.06, and want to jump to 7.04 next), so thanks to all of you for that [14:33] er, I mean 8.04 of course [14:37] BenC: otoh, we understand this is an infrastructure that maybe a handfull of people use, so having in detail docs is not feasible.. right? [14:39] alex_joni: the docs are pretty complete, but it does assume basic knowledge of debian packaging and policies (which is documented elsewhere) [14:39] alex_joni: and it is also geared toward our maint of the package, as opposed to others reusing it for arbitrary things (which we can't easily document) [14:40] alex_joni: and after all, https://help.ubuntu.com/community/Kernel/Compile is a page we have no excuse for not improving [14:40] * alex_joni gets shut up :) [14:41] :) [14:42] BenC: were you referring to other docs besides what can be found online (help.ubuntu, wiki.ubuntu, etc) and in /usr/share/doc for the various components? [14:42] alex_joni: the main document that we support is the kernel maint document on wiki.ubuntu.com [14:43] all others (for custom compiles) are mainly community created/supported pages [14:43] The community ones may not always do the right thing, but I think they come close [14:44] alex_joni: I created the original custom compile wiki page, but it has been modified heavily since then [14:45] BenC: ok, thanks.. I'll read them again later [14:46] alex_joni: I would strongly suggest, for your purposes, that you create your kernel as a custom flavour (instead of just a modified -generic), since it will alleviate any clashes...not sure if you are already doing that, but it's worth noting [14:47] yeah, that's what we ended up doing [14:47] excellent [14:47] added another custom flavour, and built packages accordingly [14:47] had a bit of a struggle with lum, but I think jepler managed to convince it to work [15:04] I haven't *tested* anything from lum or lrm yet [15:04] but they did build [15:08] generally if they build, they will work [15:21] jepler: alex_joni : May I take this opportunity to pimp the KernelMaintenanceStarter page from https://wiki.ubuntu.com/KernelTeam/KnowledgeBase?action=show [15:22] it is meant as a quick start guide for newer members of the kernel team (they wrote it!) to wet their feet [15:23] amitk_: thanks for the link === amitk_ is now known as amitk [17:17] hi, the hardy kernel won't boot on my machine === \sh is now known as \sh_away === macd_ is now known as macd === lamont` is now known as lamont [18:05] what is a good version number scheme to use when building our rtai custom flavour? I chose 2.6.24-12.22linuxcnc1 somewhat arbitrarily (linuxcnc.org is the homepage of our project). we'll only distrbute linux-image-rtai and linux-headers-rtai from it, so binary package conflicts with official kernels are not expected.. [18:51] hi folks. is there anything else I can do to help with this recent regression in the framebuffer drivers? I filed this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/204319 [18:51] Launchpad bug 204319 in linux "radeonfb regression: disappearing fonts upon VT switch" [Undecided,New] [18:52] I have since figured out that it probably affects more than radeonfb; I added a comment stating that. === kylem_ is now known as kylem [22:18] bug 188226 [22:18] Launchpad bug 188226 in linux "Kernel should use CONFIG_FAIR_CGROUP_SCHED" [High,In progress] https://launchpad.net/bugs/188226