=== lamont-away [n=lamont@mix.mmjgroup.com] has joined #ubuntu-kernel === BenC [n=bcollins@richmond-209-163-125-175.dynamic-dialup.coretel.net] has joined #ubuntu-kernel === BenC [n=bcollins@richmond-209-163-125-175.dynamic-dialup.coretel.net] has joined #ubuntu-kernel [01:36] merde [01:39] the new system of a down is gooooood.. === zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel [02:22] hmm... [02:22] Linux bart 2.6.15-1-686 #1 SMP Sun Nov 13 11:44:52 EST 2005 i686 GNU/Linux [02:23] couple of hardware regressions on my laptop though [02:23] ipw2200 couldnt load the firmware and usplash didnt work [02:28] usplash worked for me on my laptop and G4 [02:28] is that the buildd build? [02:29] my own build [02:29] from my git? [02:29] my git [02:29] but I mean does it have all the stuff from my git tree? [02:29] no wait...hmm...just a sec.. [02:29] yeah [02:30] yours and mine [02:35] any messages in kern.log about unresolved symbols in any modules? === Yagisan [n=jamie@60-240-77-39-nsw-pppoe.tpgi.com.au] has joined #ubuntu-kernel === maks_ [n=max@baikonur.stro.at] has joined #ubuntu-kernel === crimsun [i=crimsun@hacked.org] has joined #ubuntu-kernel === JaneW [n=JaneW@196.36.161.235] has joined #ubuntu-kernel === JaneW [n=JaneW@196.36.161.235] has joined #ubuntu-kernel [07:40] hmm how do you cherry pick with git? [08:51] mjg59: ping? === jane_ [n=JaneW@196.36.161.235] has joined #ubuntu-kernel === mdz [n=mdz@ca-studio-bsr1o-251.vnnyca.adelphia.net] has joined #ubuntu-kernel === JaneW [n=JaneW@196.36.161.235] has joined #ubuntu-kernel === chmj [n=chmj@wbs-146-191-41.telkomadsl.co.za] has joined #ubuntu-kernel === jane_ [n=JaneW@196.36.161.235] has joined #ubuntu-kernel [12:23] fabbione: Hi? [12:24] hey [12:24] mjg59: i was looking at one commit Ben did on .12 [12:24] after breezy release [12:24] * external-arch-i386-kernel-reboot_reboot-thru-bios: Remove [12:24] i assume this was coming from you [12:24] Yeah [12:24] We added a DMI patch to only do it on the machines that needed it [12:25] is it a whishlist for dapper or something absolutely important for breezy? [12:25] Some machines in Breezy don't reboot [12:25] Dropping that patch would probably fix them [12:25] ok so it is not even sure it will fix the problem, right? [12:26] I don't have any of the hardware concerned [12:26] ok [12:26] than i will kill the change [12:27] if it was sure and important i would have snicked in for -security [12:27] but given the status i will keep it as it is from breezy [12:27] there might be a -update for breezy anyway [12:28] mjg59: iirc, Karianne's laptop (HP something) doesn't reboot cleanly, so I guess I can have her test it. [12:29] Mithrandir: No, that one works now [12:30] mjg59: oh, ok === jbailey [n=jbailey@modemcable139.249-203-24.mc.videotron.ca] has joined #ubuntu-kernel === zul [n=chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel [03:33] BenC: sorry my wife was in a pissy mood last night and decided to take it out on me [03:33] that's what wives are for [03:34] yeah so uspalsh doesnt work for me on my laptop [03:51] any messages about vga16fb loading? [03:55] didnt see.. [03:56] ill have to check tonight when my laptop is powered back up [03:58] ok [04:17] Is the git in dapper useful for upstream kernel trees now? [04:20] well it was announced on lkml [04:22] Which it, sorry? [04:23] I don't follow lkml all the time. [04:25] jbailey: 0.99.x is suggested [04:25] 0.99.8 is what I have [04:25] 0.99.9 something or other is latest [04:25] I don't use cogito though, so I can't answer any questions about that :) [04:26] Oh? What do you use/ [04:30] just the git-* commands [04:30] But not packaged? [04:32] fabbione: ping [04:33] jbailey: not sure, but I don't think so [04:33] 'k === jbailey wonders if its worth packaging. [04:34] fabbione said he was going to do it [04:34] cogito contains the git commands, so maybe he was just going to update that [04:35] fabbione: Didja, didja, didja? huh huh huh? [04:35] =) [04:36] BenC: The linux-libc-header guys have been using a separate svn for their 'user abi' headers. I'm going to try and push them into using git and also keep that tree available. [04:36] Easier to merge the pieces that probably actually ought to be, and easier to track new changes. [04:37] yeah, would make things a lot easier [04:58] jbailey: im trying to package it [04:58] zul: Cool. Do you need help? [05:06] ROAR [05:06] "GIT 0.99.9i aka 1.0rc2 is found at usual places." [05:06] Is a stupid line to have at the top of an announcement mail. [05:06] BenC: pong [05:06] fabbione: re the reboot patch, it was tested by users [05:07] BenC: ok.. it will wait -updates if we will ever do one === ..[topic/#ubuntu-kernel:BenC] : Ubuntu kernel development discussion ONLY | New git tree for dapper: https://wiki.ubuntu.com/KernelGitGuide | 2.6.15-rc1-ubuntu2 uploaded (should build for x86, amd64, and ppc) [05:09] jbailey: not really its my first real debian package so its best that i learn how to do it and get you to look over it [05:09] zul: did you use debmake? :) [05:09] nope [05:10] BenC: did you actually uploaded k-p too? === BenC remembers those days [05:10] fabbione: yeah, and build-dep's on it [05:10] coooool [05:10] if i can get somebody to build a breezy ppc d-i for me [05:10] i might even get my powerbook to install [05:11] I'm trying to convince my wife to let me dual-boot ubuntu on her g5 so I can some extra testing there [05:11] BenC: i bought a new hard drive for my wife on condition that she dual boots [05:11] BenC: you have a ppc or two, rigth? [05:11] I need to get an amd64 machine so I can test boot that...I hate just saying "it built" [05:11] zul: Fair 'nuff. [05:11] zul: Are you updating cogito or just doing git? [05:11] fabbione: two G4's (one my desktop) and a G5 [05:12] ah [05:12] BenC: you just offered volunteer to do a d-i build for me [05:13] because i can't believe in 36 hours into my ppc experience and i still can't install linux :) [05:13] you can't install breezy? [05:13] BenC: are you running breezy? [05:13] BenC: no [05:13] apple did change PCI IDs on the latest powerbooks [05:13] yeah, breezy with dapper kernel (oooh, aaah, bad) [05:13] so now on davis [05:13] i have a .12 with the patch [05:14] BenC: can silo be built with something newer than gcc-2.95? [05:14] the kernel and udebs are already built [05:14] doko: silo is already building with gcc-4.0 [05:14] BenC: i need to build d-oi [05:14] doko: not last I checked [05:14] d-i [05:14] but davis has no B-D [05:14] and nobody around that can install them [05:15] not sure I can do that in a reasonable time frame [05:15] BenC: so would it be possible for you to build it for me? [05:15] fabbione, BenC: *lol* [05:15] oh, it only breaks on sparc32 with newer gcc, so ubuntu can do that :) [05:15] re: silo has been fixed to build with gcc-4.0 by David [05:16] fabbione: oh, right, I need to merge that patch into silo [05:16] BenC: the d-i build takes like 15 minutes.. please === BenC has been a bad upstream for silo for like 4 months now [05:16] i really really want to try to install this machine [05:16] ok, thanks, one compiler less ... [05:16] fabbionne: it's not the build, it's all the stuff I have to download :) [05:16] BenC: it's 3 udebs [05:16] really? [05:17] yes [05:17] email me the specifics of what I need [05:17] ok [05:18] I'm used to the old installer build I guess, where it needed a mostly complete base mirror [05:20] nah [05:20] it downloads some stuff from the net [05:20] but not much [05:22] BenC: you got mail [05:23] dude if you can get that done asap, i am going to put one portrait of you in my personal "Heros of my life" section in the temple [05:31] jbailey: just git [05:35] zul: git itself appears to have debian packaging already in it. [05:36] fabbione: ok, as long as it's atleast an 8x10 portrait [05:39] BenC: ehhehe [05:43] sweet, kernel-package is built, so 2.6.15-2.2 should follow soon [05:44] fabbione: at the very least, if I can get my e3k up this weekend, I can atleast do some builds for 2.6.15 kernels [05:45] the builds go pretty fast when you can through 6 cpu's and 6gigs of ram at it [05:45] s/through/throw/ [05:48] eheh i know [05:49] i have been building security kernels on a 2 x dual core amd64 with 8GB of ram today [05:49] pretty fast [05:51] jbailey: yeah i know fabbione said it sucked [05:52] fabbione: pretty fast?!?! [05:52] thats a bit of an understatement [05:52] as everything else that has a debian/ dir upstream [05:52] zul: it did start swapping approx 512MB with make -j750 [05:52] = the sucks [05:52] with -j500 was okish [05:53] heh...can i give you my ssh key ;) [05:53] give it to Mithrandir [05:54] it's his playtoy [05:54] hmmm.. [05:55] im off to lunch [05:55] Lunch sounds like a lovely idea. [06:05] with meat ;) [06:06] thai vegetarian ++ [06:06] jbailey: that resturant was really nice.. [06:07] i wouldn't mind to go there again [06:43] BenC: you can stop build d-i (if you started) [06:53] you have it? [06:53] yes [06:53] ok [06:53] i got Znarl to install b-d on davis [06:55] ok, cool [07:01] BenC: Got a moment for a stream of git questions? [07:01] sure [07:02] I'm looking at putting lkh into git. What I've noticed others have done is have a working branch and then a branch marked "for-linus" or some such for merging back in. [07:02] Are those truly just branches in the same .git file? [07:02] Or do they turn into multiple repositories that get merged back and forth? [07:05] same .git/ [07:06] you can merge from head to a branch, and branch to head [07:06] all in the same repo [07:06] Okay, cool. [07:06] so you can cherry-pick commits from head, into the branch, and do a pull request to linus, or whatever [07:07] Okay. [07:07] When doing commits, is it hard to go back afterwards and break things into better changesets? [07:08] At this point I need to just get it done, but I'd like to go back afterwards and start to split things up into changes that I think would be accepts back upstream, and changes that haven't a hope of going in. [07:08] well, let's say you do a large commit, then later you want break it down into smaller ones... [07:08] Right. [07:08] first you'd rebase the commit to the head (make the chageset against the latest code, instead of your older branch point) [07:09] then you could pull the diff, and revert the changeset [07:09] and re-apply into changesets as needed [07:09] it's not very straight forward, but it is possible [07:09] Okay, so it does understand the concept of "take this changeset out". Cool. [07:09] but if you have commits that depend on the large one, it gets ugly fast [07:09] yeah [07:10] Since it's just futzing with include files, it shouldn't be too bad for now. [07:10] the commit still shows in the log, but the revert does too [07:10] I'm sure they're probably used to that from folks new with the tool. =) [07:11] yeah, I have a few reverted commits in the ubuntu tree :) [07:16] Argh, I think I'm still confused. [07:16] So for my code that is never intended for Linux, I can just commit this to my checkout, yes? [07:16] s/Linux/Linus [07:17] Then when it comes time to hand changesets back, do I make a new branch then? [07:19] yes [07:19] you can make a branch at any time [07:19] best to pull things into the branch just after you check them into the head [07:23] dont do what i did === jbailey wonders what zul did... [07:39] Actually. [07:39] Does that include getting up this morning? [07:39] I could've avoided that easily enough. [07:54] I tried to avoid it, but the rest of the house wasn't having it [07:59] i managed to put it off for a few hours [08:07] hm [08:08] looks like we're skipping breezy on our desktop systems at work :/ [08:11] going straight to dapper? :) [08:11] probably [08:12] the problem is, we're running sarge on our servers, and dealing w/ the differences between gcc-3.3 and gcc-4.0 is a pain [08:12] w/ our in house software [08:12] oh well [08:19] jbailey: i didnt branch and that probably fucked things up [08:20] actually i dont remember what i did [08:21] dilinger: Is that going straight to dapper in 6 months, or is that, "Whee, let's ride the rollercoaster" on the way there? [08:24] jbailey: ooh, rollercoaster? [08:29] dilinger: Minor C++ abi transition, kernel update. glibc update, you know. The little things. [08:29] oh [08:29] going straight to dapper in 6mo [08:29] sticking w/ the same gcc/libc6 for now [08:30] my boss was actually talking about "breezy for sarge" [08:30] recompiling most of breezy against the older gcc/libc6 [08:32] Might not work in the case of the C++ bits. [08:32] Sounds like what you might want is a breezy server with a sarge chroot for now. [08:32] yea [08:32] i recommended the chroot [08:32] but it's just easier to stick w/ hoary for now [08:33] than to change how people work [08:40] It's all good. [08:41] The whole point of the long support cycle is to let you choose when to upgrade. [08:41] You're only in trouble if you're still running warty and can't upgrade soonish. [08:42] Do oldworld macs use PCI? I thoguht they did. [08:42] The only thing I think that the "SCSI drivers built into kernel" guy on u-d should need is to set his /etc/mkinitramfs/initramfs.conf to MODULES=dep [08:42] infinity: ^^ [08:42] infinity: I'll let you take that so that I actually can start pretending like initramfs-tools isn't mine anymore. =) [08:45] jbailey: the main problem is all the backporting i'm going to have to keep doing [08:47] dilinger: Hmm. The automatic backports and stuff aren't enabled for Hoary? [08:47] there's automatic backports? [08:48] i remember mako talking about the idea at UDU, but.. [08:49] I thought that it got done. I might be mistaken, though. [08:49] I know that there's supposed to be something crazy with backports going on/. [09:03] dilinger: remembet also that we don't support hoary -> dapper upgrades. You might have to jump via breezy anyway === doko [n=doko@dslb-084-059-089-166.pools.arcor-ip.net] has joined #ubuntu-kernel [09:42] later [09:44] fabbione: given how badly the 2 hoary->breezy upgrades went for me, i'm not that concerned :) [09:45] badly? ;) [09:45] yea [09:47] badly how? [09:47] #19477, #19478 [09:47] that was for my upgrade [09:47] a coworker did an upgrade that failed in various other places, but i couldn't file bugs because he needed his machine [09:48] -ENOBUGZILLA atm [09:49] misc packages that were missing conflicts/replaces [09:50] from within main? [09:50] or from universe? [09:52] main, i believe [09:53] i'd have fixed them myself if i had some sort of upload privileges; they seem like easy fixes [09:53] instead i just fixed them in a local repository === anavim [n=avavim@nat1.supportsoft.com] has joined #ubuntu-kernel [11:08] mjg59: ping [11:09] mjg59: just filed a bug report on usplash, it needs to load softcursor.ko first to work with 2.6.15, and the module path changed [11:13] ok [11:30] BenC : It does?... I just upgraded to 2.6.15 here, and usplash worked. [11:31] BenC : Or is this PPC specific, perchance? [11:31] no, this was i386 [11:31] it may "work", but it's broken early on [11:31] BenC : Also, if you're not yet aweare, the ipw2200 driver is looking for firmware named 'ipw-2.4-*', but we're shipping 'ipw-2.3-*'... A quick rename and my wireless worked again. [11:32] the first load attempt in the usplash initramfs script doesn't work because fbcon.ko needs softcursor.ko [11:32] \o/ [11:32] infinity: yeah, that's next on my list [11:32] I'll look into the usplash issue. [11:32] Was this with vga16fb? [11:32] Maybe I dodged the bullet with vesafb. [11:33] doesn't matter if it's vga16fb or vesa [11:33] Oh, also, damn you. You didn't switch to the New World Order of update-initramfs in your postinst. [11:33] I tried both [11:33] But we can fix that on your next ABI bump. [11:33] heh, yeah, I forgot :) [11:33] almost every upload between now and near 2.6.15 release will be an ABI bump [11:34] I assumed as much. [11:34] but other than ipw2200 it worked ok for you? [11:34] We'll have a ridiculously high ABI magic number in the package names. [11:34] Oh well. [11:34] Yeah, it's working okay right now. [11:34] Too early to say it's working "well", but it hasn't crashed yet. [11:34] it atleast booted, so that's promising [11:34] [11:35] I guess today will have to be LRM day for me. [11:35] inifinty: oh, and damn you, I've been watching family guy every night since I got back, trying ot watch them all :) [11:35] Especially if you want to update the linux-meta package. [11:35] productivity killer [11:35] Family Guy is good for the soul. [11:35] yeah, that would be nice [11:35] I have a machine that needs nvidia [11:36] Legacy or newskool? [11:36] I can always go for some testing. [11:36] fairly new [11:36] Zofia's machine is a 6800GT, so it can use both drivers. But I'd love a "legacy-only" machine to get some testing. [11:36] 0000:02:04.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 4000 AGP 8x] (rev c1) [11:37] not sure what's considered legacy, but that may be it [11:37] it's a mame machine, so I can give it some good testing :) [11:37] Not quite legacy yet, no. [11:37] nope, I think you need to have GF2MX or older. [11:37] Might be in another year. [11:38] But your machine can run both drivers, so you can do some testing of that setup for me. === infinity ponders. [11:38] I wonder if I'm going to have to wait for jbailey's glibc/lkh upload, followed by the new X building correctly, before I can update the ATI shit to something shiny and new. [11:39] Oh well, I can do nvidia at any rate, and build for the new kernel. [11:41] definitely, I'll test whatever I can [11:45] Hrm, core hours start in 15 minutes. Guess I should find some breakfats before I start working for real. [11:45] Or, some breakfast. [11:46] nice fatty bacon? :P [11:48] Or some fat breaks. === anavim [n=avavim@nat1.supportsoft.com] has left #ubuntu-kernel ["Leaving"] [11:50] are those like beats? [11:52] Well, like breakbeats, sure.