=== netjoined: irc.freenode.net -> kornbluth.freenode.net === TheMuso [~luke@dsl-202-173-132-131.nsw.westnet.com.au] has joined #ubuntu-kernel === desrt wonders why all of this work is being done on 2.6.12 [12:26] mjg59_: btw - sent someone your way wrt latest thinkpad acpi stuff. [12:26] lamont__: Ah, thanks === lamont__ adds one beer to what he owes mjg59_ [02:15] lamont__: pong [02:19] .c [02:19] crap === TheMuso [~luke@dsl-202-173-132-131.nsw.westnet.com.au] has left #ubuntu-kernel [] === weridcreep [re@c-24-99-206-125.hsd1.ga.comcast.net] has joined #ubuntu-kernel [02:33] hello [02:35] jbailey: figured it out... although... [02:35] what's the easiest way to abuse an initrd to debug in it? [02:35] what kernel does ubuntu run [02:36] lamont__: Existing one, or can you create a new one? [02:36] jbailey: (original question involved a brainfart trying to mount the initrd locally to look)( [02:36] Editting existing ones is teh suck. [02:36] given the recipie, I could create a new one... [02:36] Okay, edit /etc/mkinitrd/mkinitrd.conf [02:36] Set DELAY=5 and BUSYBOX=yes [02:36] (Make sure busybox-cvs-static is installed) [02:36] as root: [02:37] mkinitrd -o /boot/initrd.img-$(uname -r) $(uname -r) [02:37] NOTE: This will overwrite your current initrd. [02:37] yeah - I see that [02:37] If you have a sane bootloader (That is, grub grub or grub), you can make it /boot/initrd or something like that and just change it at boot time. [02:38] jbailey: elilo :-( [02:39] Add an entry for your testing then. [02:39] yep [02:39] You won't get grub2 for efi for another couple of months. [02:39] (although someone has now started on it) [02:39] actually, the current state is that 'Linux' doesn't boot, and 'Good' does. :-) [02:39] Great! Overwrite the one for Linux then, nothing to lose. [02:39] yeah [02:39] Oh! [02:39] yeah [02:39] Missed a step. [02:39] ?? [02:40] Edit /etc/mkinitrd/modules and add the modules you need to have a working keyboard. [02:40] serial atm [02:40] 'k =) === lamont__ has a 2700+ line config diff, and somewhere in there is a fatal option [02:40] *blink* [02:41] config? [02:41] happy happy joy joy. binary searches are _SO_MUCH_FUN_!!! [02:41] kernel config [02:41] defconfig vs itanium [02:41] I didn't think there were 2700 options in there. [02:41] 'sthis breezy? [02:41] rather, defconfig vs breezy/itanium [02:41] just a sec and I'll dump stats for you - Good has almost booted. [02:42] If you feel up to it after this, I'd appreciate feedback on the initramfs-tools, since it's scheduled to become default on Friday. [02:42] Since I will be away this weekend, I'd rather clobber as few UndercluedUsers as possible. [02:43] (You know... For the racks of Itaniums running Breezy out there...) [02:43] diff -u debian/config/itanium debian/config/ia64/itanium | wc [02:43] 2732 5643 61682 [02:43] *ouc* [02:43] +h [02:43] yeag [02:50] must run [02:50] back later === lamont__ [~lamont@15.238.5.126] has joined #ubuntu-kernel [06:33] morning [06:33] word. [06:34] i have a question that i asked earlier after you'd gone to bed :P [06:34] why are you packaging 2.6.12? [06:36] what should i be packaging? [06:37] 2.6.13-rc's [06:37] no [06:37] we are in UVF [06:37] Upstream Version Freeze [06:37] we need to release quite soon [06:37] since how long? [06:37] hmm [06:37] 3 weeks? [06:37] more or less [06:37] so 2.6.12 is the breezy kernel [06:37] weird [06:37] yes [06:38] ok. that's a good reason :) [06:39] that's what in our conffile [06:39] ops [06:41] is gnome a blanket exception to UVF or is 2.11 considered like a 2.12 prerelease? [06:41] gnome is an exception [06:42] it has been since the beginning [06:42] it's a good exception :) [06:54] infinity: ping? === lamont__ starts to fade fast, heads for home [07:13] any chance of getting a working version of ipw2200 into the kernel soon? [07:13] fabbione: still here? [07:13] calc: ipw2200 is working [07:14] 1.0.4 -> 1.0.1 for WEP but broke WPA completely [07:14] calc: 1.0.4 did break completely ipw2100 [07:14] and i had no time for that release to test 1.0.6 [07:14] too bad its not even for the ipw2100 [07:15] i have 1.0.4 on ipw2200 and it works more or less fine [07:15] also.. people should read what's on the ipw2x00 sties [07:15] sites [07:15] i get those error messages about resetting firmware but 1.0.4 does actually work 1.0.1 doesn't at all [07:15] 1.0.X releases [07:15] for x = 0 stable [07:15] for x > 0 development [07:15] 1.0.6 = development [07:15] 1.x.y [07:15] x is stable [07:15] when x = 0 [07:16] or else why not go all the way back to 1.0.0 ? :) [07:16] Versions with the last number is not a zero is an unstable release, for example 1.0.1, 1.1.3, etc. [07:16] yes [07:16] 1.0.0 is basically useless [07:16] 1.0.1 is nearly that way [07:16] because ipw2100 is alligned with 1.0.1 ipw2200 [07:16] what does ipw2100 have to do with ipw2200? [07:17] so your x.y interpration is wrong [07:17] calc: they share ieee8$something layer [07:17] they splitted only recently in 3 projects [07:17] that doesn't avoid the point that ubuntu is still using a development driver and one that is more broken than the current one which fixes about an additional 30 bugs [07:17] ah yea i see about the 802.11 stuff [07:18] calc: the plan was to revert to a more stable release [07:18] and than try the new split in the next kernel [07:18] before the ieee code was duplicated and misalligned between the 2 [07:18] (ipw2x00) [07:18] so it was creating all sorts of problems [07:18] only recently they splitted ieee out of the 2 trees [07:18] and that needs to be tested [07:18] ok i'll just hang onto my -3 kernel since its the only one that will work for the forseeable future then [07:19] so if you can be nice to give us the time to merge [07:19] you will get it [07:19] i thought you said earlier that the final kernel will be out within 3 weeks? [07:19] who said so? [07:19] 23:37 < fabbione> we need to release quite soon [07:19] 23:37 < fabbione> 3 weeks? [07:20] 3 weeks was related to UVF [07:20] 3 weeks ago... [07:20] the release will probably be tomorrow [07:20] there is no final kernel until breezy releases [07:20] oh is this just a temporary colony freeze? [07:20] ok :) [07:20] and we will start doing only security updates to the kernel approx 2/3 weeks before final release [07:20] sorry i was confused === fabbione starts fetching the latest ipw2*00 crack... [07:27] calc: will you be able to test for me? [07:28] yea [07:29] what types of tests do you need run? [07:29] hmm this also means another ABI change... [07:29] SUCKAGE [07:29] changing the driver causes abi change? [07:29] calc: yes. the ieee thing has an abi change [07:29] and ipw2* depends on it [07:30] you can't change interchange the modules at your own pleasure [07:30] oh [07:32] oh btw i am using 2915abg on amd64 arch [07:35] what's that? [07:35] i am not 100% familiar with all these wireless drivers.. [07:35] i only use cisco stuff [07:38] its the intel 802.11a/b/g minipci [07:39] uses same driver as ipw2200 [07:39] ah ok [07:40] i'm going to bed now, bbl [07:43] night [07:50] I'm using a 2915abg on i386. ;) === JaneW [~JaneW@wbs-146-168-164.telkomadsl.co.za] has joined #ubuntu-kernel [08:04] hey JaneW [08:21] see... [08:21] even after the split they are still not synced properly [08:21] GRRRRRRRRRRRRRRRRRRRRR [08:27] #define IPW_HEADER_802_11_SIZE sizeof(struct ieee80211_header_data) [08:28] infinity: do you have any clue about the size of that struct? [08:29] never mind.. i found it [08:29] now they share code... === JaneW [~JaneW@wbs-146-168-164.telkomadsl.co.za] has joined #ubuntu-kernel [08:29] so let's TRIPLICATE all the definitions [08:34] JaneW: i will need a name for tomorrow my far far away so lovely lady :) === doko [~doko___@dsl-084-059-076-040.arcor-ip.net] has joined #ubuntu-kernel === fabbione hopes he got the define right or ipw2100 won't work [08:53] JaneW: ?? [09:07] ok guys we need a name for the kernel [09:07] + release [09:07] JaneW disappeared... [09:09] The: [09:09] begin 644 - [09:09] 41S%"0C!2($TS(%0S2"!#4C1#2PH` [09:09] ` [09:09] end [09:09] Release [09:13] that's an interesting name [09:13] eheh === desrt g1bb0rs you some cr4ck [09:13] nah i did set it to something more normal [09:14] people have lost the sense of humor.. [09:14] they won't get the joke part [09:14] boo to people [09:15] desrt: i know.. i am talking from experience [09:15] i have to issue to write *interesting* stuff :) [09:16] time to start the build orgy :) [09:16] exciting. === desrt thinks we should have a build-pr0n package to lure former-gentoo users to ubuntu land [09:17] aha [09:17] just videos of compiles scrolling by [09:17] HAHHAAH [09:17] desrt: if you collect the videos and make them BSD/GPL licence [09:17] i am going to upload them as gentoo-emulator [09:17] :) [09:18] we can make it as a screensaver or something [09:18] hey.. that'd be a pretty sexy screensaver [09:18] similar to cappuccino [09:18] mmm. i think gnome-screensaver needs a module called "gentoo" :) [09:19] desrt: ehehe sure... [09:19] if you do it, i will upload it for you [09:19] just the code.. no need to package it [09:20] making a deb for it will take 2 minutes [09:20] hmmm :) [09:20] ok. i'll look into it [09:20] actually [09:20] it would be even more cool to use the kernel screen blanking [09:20] CONFIG_GENTOO_EMULATION [09:20] ....as compared to the X one? [09:20] oooh. [09:21] i see [09:21] that you can enable or disable with a syscall/ioctl or whatever [09:21] and you can have a bunch of kernel options [09:21] that will just fake to compile hello.c millions of times :) [09:21] [*] Include build log from Xorg [09:21] [*] Include build log from kernel source [09:21] ahahah [09:21] etc [09:21] the problem is that it would bloat the kernel or the module... [09:21] nah [09:21] including these logs [09:21] you gotta imagine that build logs compress really well [09:22] every single line is like gcc -flags -flags -flags -Dsomething -Isomething blah blah blah flags filename.c [09:22] desrt: X builg log is 10MB uncompressed [09:22] and the only part that changes is filename.c [09:22] even if you compress it to death is still 300K [09:22] hmm [09:22] this is problematic. [09:22] ! [09:22] i know [09:22] we launch a project [09:22] gentoo@home [09:22] as an outreach programme to gentoo users [09:22] aHAHAHA [09:23] donate our spare CPU cycles to actually help them compile [09:23] desrt: it would be easier to write a name generator to print gcc -O31337 blablabla foo.c [09:23] you forgot to omit the framepointer [09:23] man... it's so easy to get caught-up in the gentoo-teasing [09:24] i used to use gentoo... and i liked it a lot... i still do [09:24] if, for example, sadfdl were to ever pull another ubuntu_spatial type thing i'd go back to gentoo :P [09:28] eheheh [09:28] i doubt he is going to do it again === chmj [~chmj@196.36.161.235] has joined #ubuntu-kernel [10:38] ok [10:38] my screensaver is about done now :) [10:41] ehehhe [10:41] so far it just says "test" once per second [10:41] i have to find something more interesting for it to say [10:41] desrt: can i see the code? [10:41] it's pretty rough [10:41] but sure [10:41] we can work on it together... [10:42] given i just uploaded the kernel i have the right for 10 minutes free :) [10:42] http://manic.desrt.ca/gentoovision.c [10:44] heheh [10:45] hmm === desrt encounters chicken + egg problem [10:46] fabbione; if you want to help, there's a good task needs to be done [10:46] desrt: i first need to figure where is gtk.h :) [10:46] there needs to be a program that opens a pseudotermial or listens on a pipe and gets the output of a compile complete with timing information [10:46] gcc -o gentoovision gentoovision.c -Wall `pkg-config --cflags --libs gtk+-2.0` [10:47] it might segfault :) [10:47] gentoovision.c:118: warning: passing argument 2 of 'gtk_timeout_add' from incompatible pointer type [10:47] tsk :) [10:47] pfft [10:47] i didn't feel like looking up the right cast type :) [10:47] it's some (GTimeoutFunc) or something [10:47] ahah [10:47] it works here :) [10:48] so what's the task? [10:48] there needs to be a program that opens a pseudotermial or listens on a pipe and gets the output of a compile complete with timing information [10:48] i think the file format will be like [10:48] 1234:gcc -o some compile output blah blah blah [10:48] where 1234 is how many ms that output should stay on the screen [10:49] why not just generating random gcc stuff? [10:49] it'd be cool to have authentic builds :) [10:49] they'd be the new ringtones [10:50] instead of downloading a blink182 ringtone for your phone you download a glibc build log for your screensaver :) [10:50] actually... gentoo@home is an easy project to do :) [10:50] well.. there's already distcc... [10:50] exactly :) === Seveas [~seveas@ksl403-uva-141.wireless.uva.nl] has joined #ubuntu-kernel [11:17] fabbione; are you working on that program? [11:21] desrt: not right now.. sorry.. i did a little mistake building on hppa [11:22] s'ok [11:22] i'm gonna go to bed now anyway :P [11:22] it's waay past my bedtime [11:22] eheh good night :) === Nafallo [nafallo@nafallo.user] has joined #ubuntu-kernel [12:19] could you please sync rt2400 && rt2500 from CVS before next upload? [12:24] fabbione: I'm a bit stuck getting stuff integrated until I actually have internet connectivity here. What are you defining as feature freeze in the context of the kernel? [12:26] mjg59_: like the rest of the distro and i will be vac from tomorrow [12:26] Nafallo: why? [12:26] fabbione: lot's of bugfixes. [12:27] Nafallo: i will look if i have the time [12:27] fabbione: Sure, but what's a feature in terms of the kernel? [12:27] fabbione: it might actually begin to work without all those ifdown && ifups I have to do now :-) [12:27] mjg59_: adding new crack.. bug fixes are ok of course [12:27] fabbione: k, kewl. [12:28] fabbione: Ok. There's one (trivial) driver that I'd like to push, but there's no way I can generate a dpatch by tomorrow. [12:28] I just don't have bandwidth at the moment [12:31] mjg59_: for the next 2 weeks (while i am away) infinity will take care of the kernel [12:31] iirc Feature Freeze is by the 5th of Aug [12:31] or something around that [12:31] so you have sometime [12:31] but don't count on me being around [12:31] so you will have to triple check everything [12:32] from patches to configs to portability and so on... [12:32] 11th of August [12:32] Ok, no problem === swarm [~swarm@151.97.253.246] has joined #ubuntu-kernel [01:48] fabbione: There's a load of PCI drivers that need fixing up for suspend/resume to work. I'm looking into it. [01:48] mjg59_: *sighs* [01:49] (biggest problem is with sound cards, since we unload network drivers) [01:49] hmm what has net to do with sound? [01:49] Basically, due to ACPI changes (to fix a bug) PCI drivers all need to call pci_disable_device on suspend and pci_enable_device on resume [01:50] The same bug is present in sound and network drivers, but we unload network drivers [01:50] JEEEEEE [01:51] dude that patch is going to be A BIG FAT MOFO to maintain [01:51] It's only a problem with devices on shared interrupts, so IDE isn't an issue [01:51] USB is, but we unload that as well, so... [01:53] Which leaves, uh, 47 drivers to fix up. Hmph. [01:53] The ALSA people may already have done it. I'll check their tree. === zul [~chuck@CPE0006258ec6c2-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel [01:55] i have the feeling that with all these big fat crack .12 is going to suck more than .10 [01:55] hey zul [01:55] hey fabbione [02:00] fabbione: The alternative is to revert that hunk, which takes us back to .10 for that behaviour [02:00] zul: yay! maybe you should do what I asked fabbione earlier? :-) [02:00] However, it is a real bug that gets fixed [02:00] zul: update rt2400 && rt2500 from CVS. fixes lots of bugs. [02:01] zul: also we might want to consider rt2570? [02:01] mjg59_: ok.. try to contain the mess :)) [02:01] Nafallo: please stop nagging [02:01] it's the 3rd time you ask the same [02:02] gimme a break and the time to do it [02:02] Oh argh. [02:02] fabbione: oki. [02:02] Alsa has its own power management layer. How horrible. === ..[topic/#ubuntu-kernel:fabbione] : Ubuntu kernel development discussion ONLY | http://www.ubuntulinux.org/wiki/KernelTeam | There are no kernel bugs.. only broken hardware | http://people.u.c/~lamont/Archives/kernel-team@ubuntu.com--2005/ playground: kernel-debian--preX,6--2.6.12 [02:04] wtf? [02:04] zul: what? [02:04] oops...typo...was commenting code [02:04] ahha [02:05] holy crap Nafallo i just woke up and am at work so its not going to be done anytime soon [02:07] oki. I will not ask before they fix another one of those _really_ irritating bugs that seems to be in the driver :-). [02:08] Nafallo: let me explain [02:08] between your request and time i can upload such change [02:08] i need AT LEAST 4 hours [02:08] you asked this morning.. wait [02:08] AT LEAST = update the patch, build everywhere, fix the breakage, go back [02:08] the build = 3 hours [02:09] if you are in such a hurry, you can provide us with .dpatches directly [02:09] tested of course... [02:09] so i can save 4 hours [02:09] and you can spend 2 days building around... [02:09] because the patch needs to work on N arches [02:09] fabbione: I know. I didn't know if you saw it this morning. and last time they fixed a big one I do not believe it was updated. that's why I asked when you where alive aswell. [02:10] Nafallo: this morning i did even answer to you [02:10] and we did talk [02:10] so.. i fail to see how i could have missed that... [02:11] 12:19Nafallocould you please sync rt2400 && rt2500 from CVS before next upload? [02:11] 12:26fabbioneNafallo: why? [02:11] 12:26Nafallofabbione: lot's of bugfixes. [02:11] 12:27fabbioneNafallo: i will look if i have the time [02:13] so that was 2 hours ago :) [02:13] fabbione: I asked in #ubuntu-devel earlier (I belive yesterday after checking the logs). [02:14] Nafallo: that's why i said 3 times.. [02:14] when i read the backlog you were not around.. [02:15] fabbione: anyway. no hard feelings. those bugs keeps me on cable, that's why I wanted to make sure you knew. and the when zul came along, I asked him because he's been my SPOC on this driver :-). [02:15] until now indeed... [02:17] oh if im not needed ill just go away..thanks.. [02:18] besides i dont see you submitting patches [02:20] zul: I will not touch the kernel before I got lot's more experience. I watch the changelogs on this driver, and that's all I will do :-). I belive the issue is sorted now anyway :-). [02:20] sorry for the nagging, now I'm sure this will get fixed and can get on with MOTU-things. === chmj [~chmj@196.36.161.235] has joined #ubuntu-kernel [02:30] chmj: I thought someting interesting was happening here [02:31] what you mean ? [02:32] JaneW: O.o [03:24] morning JaneW [03:25] hey lamont [03:25] lamont: do you happen to remember why you were pinging me yesterday? [03:25] fabbione: actually running out the door... need to leave 5 min ago. [03:25] ok [03:25] ttyl [03:25] about 45-60 min [03:25] sure [03:55] heh i might be conververting my boss from fedora to ubuntu === doko [~doko___@dsl-084-059-089-064.arcor-ip.net] has joined #ubuntu-kernel [04:09] hi lamont === JaneW is off to a meeting === lamont [~lamont@15.238.5.126] has joined #ubuntu-kernel [04:39] Adding console on ttyS0 at MMIO 0xff5e0000 (options '9600n8') [04:39] RAMDISK: cramfs filesystem found at block 0 [04:39] RAMDISK: Loading 9152KiB [1 disk] into ram disk... done. [04:39] XFS: bad magic number [04:39] XFS: SB validate failed [04:39] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,3) [04:39] hrm... clearly I'm missing something important... [04:40] is that ia64? [04:45] yeah... I mutilated the .config, and it booted. now to add some more stuff back. [04:45] Is it an XFS filesystem? [04:45] mjg59_: no [04:46] ext3 everywhere, although hda1 is fat [04:46] actually vfat [04:46] oh you have a copy of Windows IA64? [04:46] elilo partition is vfat [04:46] ah ok [04:47] because vfat is so cool. that and intel engineers are windoze-centric, so that's what they made it. [04:47] you should see the builtin editor in efi... [04:47] notepad? ;) [04:47] or word? [04:48] notepad like/nano-like. but absolutely sucky termio [04:49] brrrrrr [04:50] ok .. last universe full kick back before starting to check the c++ transition status... [04:53] and that's it for today... [04:53] i can't work anylonger... === lamont pushes the kernel back to the top of the hill again [04:53] so.. should i try to remount some extra i386 hw or should i mount the 2 mk68k ?? [04:53]