[01:54] <MTecknology> Any idea why I'm getting these errors? http://dpaste.com/140771/
[05:18] <MTecknology> really quiet in here...
[05:19] <MTecknology> anybody have an idea?
[05:21] <crimsun> kinda lacking in detail, there
[05:21] <crimsun> e.g., what's the base linux source? 
[05:23] <MTecknology> crimsun: Ubuntu-2.6.32-9.13
[05:24] <crimsun> which config options did you change?
[05:24] <crimsun> a pristine copy of linux_2.6.32-9.13 gets past that point ok
[05:24] <MTecknology> I tried using the same .config I was using from karmic
[05:25] <crimsun> is it available somewhere?
[05:26] <MTecknology> http://paste.ubuntu.com/351086/
[05:32] <MTecknology> crimsun: I was hoping it was a simple little thing but it seems I have something pretty screwed up..
[05:44] <crimsun> heh
[05:44] <crimsun> pretty straightforward, actually:
[05:44] <crimsun> ~/tmp/linux-2.6.32 $ grep -ni initrd .config                               
[05:44] <crimsun> 106:# CONFIG_BLK_DEV_INITRD is not set
[05:45] <crimsun> ot/config-2.6.32-9-generic                                                              <
[05:45] <crimsun> 127:CONFIG_BLK_DEV_INITRD=y
[05:46] <crimsun> i.e., init/initramfs.c
[05:46] <crimsun> see commit 29f1e2 of ubuntu-lucid.git
[05:49] <MTecknology> crimsun: how do you see a certain commit?
[05:49] <crimsun> do you have a local copy of ubuntu-lucid.git ?
[05:49] <MTecknology> ya
[05:50] <MTecknology> I found it on gitweb, but I'd like to learn how to do it with git too
[05:51] <crimsun> git log -p 29f1e2
[05:56] <MTecknology> crimsun: is there any part of kernel work that's simple and easy?
[05:57] <crimsun> MTecknology: sure, there are quite a few classes of low-hanging fruit
[05:58] <MTecknology> crimsun: if I want to just dive in; where would you suggest doing it?
[05:59] <MTecknology> I guess I should go through the .config and where it says something isn't set and set it
[06:00] <crimsun> MTecknology: depending on experience and comfort with C, there're a few ways (at least)
[06:01] <crimsun> MTecknology: the recommended bug lists that Leann releases is one
[06:01] <MTecknology> I know very very little C; mostly only what I learned from bash scripting
[06:02] <crimsun> MTecknology: you could try easing into the janitors project
[06:02] <crimsun> #kernelnewbies, OFTC
[06:03] <MTecknology> where's teh list lean puts out?
[06:03] <crimsun> http://qa.ubuntu.com/reports/ogasawara/kernel-buglist.html
[06:06] <MTecknology> crimsun: thanks, I'll muck around that once I have this compile works
[06:12] <MTecknology> crimsun: so the fix should have been to just do CONFIG_BLK_DEV_INITRD=y; right?
[06:13] <crimsun> MTecknology: depends whether you want the simple way
[06:13] <MTecknology> I'd prefer not have any initrd
[06:14] <crimsun> arguably there's little point to async population if you aren't using an initrd, so you could just fix the patch
[06:14] <MTecknology> he, me fix something?
[06:15] <crimsun> I don't know the best way to do it, because I didn't write it, and I don't know the intricate implications of conditionalising that particular code
[06:19] <MTecknology> crimsun: thanks for that info; taught me more than I wanted to learn today :P
[06:21] <MTecknology> crimsun: I tried to built it after setting that and it changed back to is not set
[06:35] <MTecknology> crimsun: that's a big list, non of them look very simple
[10:05] <MTecknology> crimsun: I almost have it... I'm getting this error during but and it hangs at maintainance shell, I do Ctrl+D and it reboots "
[10:05] <MTecknology> mountall: could not connect to Plymouth"
[10:06] <MTecknology> I think it's something to work on for tomorrow... 04:06 here
[10:07] <unggnu> hi all
[10:07] <MTecknology> unggnu: hi
[10:07] <unggnu> What is the status of Nouveau and the Kernel in Lucid?
[10:07] <unggnu> hi MTecknology
[10:09] <MTecknology> unggnu: what's with the nick?
[10:10] <unggnu> MTecknology: ?
[10:10] <MTecknology> why did you pick it?
[10:10] <MTecknology> I kinda like it... the "un-gnu" part
[10:11] <unggnu> MTecknology: I don't know, a palindrome and some other things :D
[10:13] <MTecknology> unggnu: You should apply for Ubuntu membership.. Just looking at the work you've been doing
[10:14] <MTecknology> unggnu: You have any idea what would be needed in the lucid kernel that the lack of would cause this message? "mountall: could not connect to Plymouth"
[10:14] <unggnu> MTecknology: I am pretty sure that the Plymouth part isn't ready yet, at least it wasn't the last time I have checked
[10:16] <MTecknology> unggnu: I'm trying to compile my own slimmed down kernel. I'm using my .config from karmic and trying to make it compile with the lucid source. I got it to compile with the help of crimsun but now when I boot I get that error.
[10:16] <unggnu> MTecknology: https://wiki.ubuntu.com/FoundationsTeam/LucidBootExperience
[10:16] <unggnu> MTecknology: I got this error even with the default Lucid kernel
[10:16] <unggnu> At least some weeks ago
[10:17] <MTecknology> hurray
[10:17] <MTecknology> the current generic kernel gave no errors
[10:19] <MTecknology> unggnu: so summing it up; wait a couple weeks before I try to mess with it again?
[10:23] <unggnu> MTecknology: I still got the message with the generic kernel
[10:23] <unggnu> just switch to terminal f8
[10:24] <MTecknology> brb
[10:31] <MTecknology> unggnu: I couldn't switch to tty8; I couldn't mount anything either; / was mounted but that was it
[10:32] <MTecknology> unggnu: this might just be an issue I need to wait out
[10:32] <MTecknology> it's 04:30 though - I should get some sleep
[10:32] <MTecknology> unggnu: thanks
[10:33] <unggnu> MTecknology: good night :)
[13:14] <tim> hi all, compiling the nvidia kernel module 190.53 for 2.6.33-rc2 fails with the error message http://pastebin.com/d3b8ac89b ... any idea, what is going wrong?
[13:14] <tim> i am running: dkms build -m nvidia -v 190.53  -k 2.6.33-rc2 --kernelsourcedir /usr/src/linux-headers-2.6.33-rc2/
[15:42] <rtg> Keybuk, wrt to bug #499491, is building TUN/TAP into the kernel really the right solution? Seems like its a class of problems, e.g., what about other boot essential drivers?
[15:42] <ubot3`> Malone bug 499491 in openvpn "tun module no longer automatically available (was: Euca 1.6.2 fails to boot an instance)" [High,Invalid] https://launchpad.net/bugs/499491
[15:45] <Keybuk> yeah it's a long established class of problems
[15:45] <Keybuk> basically since the introduction of devfs!
[15:45] <Keybuk> things like ppp, tun, etc.
[15:45] <Keybuk> pretty much all "network class" devices
[15:45] <rtg> so, shall I just work around this one?
[15:46] <Keybuk> if the code for them is in a module, the device node doesn't exist in /dev
[15:46] <Keybuk> which means you can't use them without loading the module
[15:46] <Keybuk> but these things are designed to be used by normal users
[15:46] <Keybuk> who can't load the moduel
[15:46] <rtg> there is no real downside to building it in other then size increase
[15:46] <Keybuk> right
[15:46] <Keybuk> and we were force-loading tun anyway before
[15:46] <rtg> ok
[15:47] <Keybuk> which meant it was in the initramfs
[15:47] <Keybuk> which is an even greater size penalty
[15:47] <Keybuk> and wasn't possible to blacklist
[15:48] <Keybuk> ironically, most network class things don't have this problem, because they use sockets not device nodes
[15:48] <Keybuk> and since the socket is opened from userspace
[15:48] <Keybuk> but the "internal open" happens in kernelspace
[15:48] <Keybuk> the kernel *can* call modprobe ;)
[15:48] <rtg> yeah, TUN is special.
[15:48] <Keybuk> (there's a chapter in my book about this :p)
[15:49] <rtg> are you kidding about the book?
[15:50] <Keybuk> no
[15:51] <Keybuk> has been my holiday project to make a start on it
[15:51] <rtg> ah, guess thats why I had not heard about it.
[15:51] <rtg> the kernel team will be at Millbank next week. will you drop by one day?
[15:51] <Keybuk> I'm in Sydney most of next week
[15:51] <Keybuk> the bits of it that I'm not, I'm in the air
[15:52] <Keybuk> but I may drop by on the way to Heathrow if I have some time
[15:52] <rtg> Sydney? I thought linux-conf.au was in NZ this time?
[15:52] <rtg> oh, but its the following week
[15:52] <Keybuk> book is going to be called the Linux Plumbers Handbook, it basically covers the kernel userspace interfaces, and all the bits that plug into them up to the X server
[15:52] <Keybuk> right, Sydney is holida
[15:52] <rtg> cool
[15:52] <Keybuk> I'm not flying half way around the world and not chilling out in Sydney first ;)
[15:53] <ogra> slacker ! you just had one !
[15:53] <ogra> (happy new year etc :) )
[15:54] <Keybuk> ogra: I had very little holiday last year :p
[15:54] <ogra> heh, me too ... as little that david forced me to take december off 
[15:55] <Keybuk> and, well
[15:55] <Keybuk> LCA
[15:55] <Keybuk> Sydney holiday is mandatory
[15:55] <ogra> i thik this was the first 3 weeks in a row i ever took since working here 
[15:55] <Keybuk> it's one of those airports I refuse to just transit through
[15:55] <Keybuk> because it's a beautiful city
[15:55] <Keybuk> and LCA is in NZ
[15:55] <Keybuk> so I obviously need to take some holiday there too and see the island
[15:55] <rtg> seems like a wise policy to me :)
[15:55] <ogra> yeah, indeed, i wasnt serious :)
[16:56] <Q-FUNK> smb: howdy! :)
[16:56] <Q-FUNK> ogasawara: hi!
[16:57] <Q-FUNK> any suggestion on how to proceed with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/396286
[16:57] <ubot3`> Malone bug 396286 in linux "[Geode LX] [OLPC] 2.6.31-generic: kernel panic near the end of initramfs" [High,In progress] 
[16:58] <smb> Q-FUNK, Hi, not a better one than either get the kernel build with the suggestions from hpa or succeed on making them reproduce it 
[16:59] <Q-FUNK> smb: it fails to build, here.  it repeatedly dies with a "truncated file" error.
[16:59] <smb> Q-FUNK, are you using ccache?
[16:59] <Q-FUNK> ccache ??
[17:00] <Q-FUNK> probably not.  never heard about it
[17:00] <smb> Q-FUNK, If you don't know, then never mind. :)
[17:01] <Q-FUNK> heck, even simply trying to build the kernel without hpa's patch fails as above.
[17:01] <Q-FUNK> something in either gcc or the kconfig defaults makes it fail to build on this geode.
[17:01] <smb> Q-FUNK, Is there even the slightest chance that your machine could have a hardware problem?
[17:02] <smb> IOW do we have anybody else seeing the same problems as you do on another machine?
[17:02] <Q-FUNK> rolling back to jaunty and building those kernels works.
[17:02] <Q-FUNK> or running any stock kernel package from the ubuntu vanilla collection until 2.6.30 works
[17:03] <Q-FUNK> only vanilla kernel packages after 2.6.30 flatly don't run
[17:04] <Q-FUNK> until 2.6.30, whether self-built, jaunty generic or ubuntu vanilla package, it all works fine
[17:04] <Q-FUNK> it's only since during karmic development phase, after the generic kernel was switched from 2.6.30 to 2.6.31 that generic kernsl fail to run or build.
[17:07] <Q-FUNK> I'm thus wondering whether the kernel might have acquired some new code that makes it fail to boot on older hardware, the same way that changes that came in 2.6.23 make the kernel stop booting on older geode GX1 hardware.
[17:08] <Q-FUNK> well, there's a few people subscribed to the bug, so I'm guessing that others are affected too.
[17:09] <Q-FUNK> or were some defaults changes in -generic that only make it work on 686 or newer?
[17:10] <Q-FUNK> am I supposed to use the -486 kernel on older hardware?
[17:10] <Q-FUNK> erm, sorry, 386
[17:10] <smb> Q-FUNK, The problem was that the bisect went for code that is quite unrelated and also the "working" kernels I build for you were just adding delays. So either its not the real cause and its another patch or there is a hw specific problem that just surfaces in certain timing conditions
[17:10] <Q-FUNK> could be
[17:11] <Q-FUNK> hpa points to some distros having changed GCC defaults as a possible cause.  does that affect ubuntu?
[17:12] <smb> Q-FUNK, I think the main reason for 386 was something else which I don't remember atm. We did not change the gcc options for the kernel build afaik
[17:13] <Q-FUNK> hpa refers to gcc built-in defaults changes
[17:14] <Q-FUNK> well, could hpa's patch be applied to the ubuntu kernel anyhow, just to be safe?
[17:21] <Q-FUNK> smb: I'm curious as to whether a test package of 2.6.32 generic without your kprint additions and with hpa's patch instead would wokr.  however, it flat out fails to build here.
[17:22] <smb> Q-FUNK, I will try to build you a package tomorrow.
[17:23] <Q-FUNK> smb: thanks!
[19:48] <bdmurray> apw: could you update bug 429257 for pitti?
[19:48] <ubot3`> Malone bug 429257 in gvfs "MMC cards no longer auto mount" [Undecided,Incomplete] https://launchpad.net/bugs/429257
[19:49] <rtg> bdmurray, apw is not back until tomorrow
[19:50] <bdmurray> rtg: okay, maybe he'll see it then ;-)
[20:14] <jarek> Anyone know about Mantis drivers for Ubuntu 10.04?
[20:14] <jarek> They exist in linux-next now
[20:16] <jarek> a lot of people waiting for this driver, also its shouldn't mess anything
[20:17] <jarek> is possible to backport this driver?
[20:59] <lamont> anybody got thoughts on 503109 ? other than that it's a eglibc issue
[21:22] <MTecknology> If you guys put the "view" of Linux into one line, what would it be?
[21:22] <MTecknology> fully free and open wouldn't work because some proprietary code exists afaik..