[03:55] <kyle___> iv compiled the kernel using git and the command "CONCURRENCY_LEVEL=2 AUTOBUILD=1 NOEXTRAS=1 fakeroot debian/rules binary-generic" . I need to execute the "sudo dpkg -i linux-image-<version>.deb" command but no dice. Where are the deb files?
[03:57] <kyle___> im sorry... they tricked me and put them in the home folder
[03:57] <kyle___> im an idiot
[04:15] <kyle___> After a kernel compile and install (git) nVidia graphic drivers no longer work. I didn't modify the kernel config in any way. Is their a kernel option I need to have before the prop nividia drivers will work?
[04:39] <mase_work> Hi guys, i am going through the suspend resume script on some laptops i have at work  but i am running into some problems with a few of them. Basically it gets to various stages in the test cycle, some further than others and on resume it logs me out
[04:39] <mase_work> so i log back in again
[04:39] <mase_work> run the script
[04:39] <mase_work> and it starts again from scratch
[04:40] <mase_work> i can never get it to provide feedback
[09:37] <amitk> smb_tp: the thinkpad-acpi maintainer was on here during the weekend looking for a git tree to target his patches to
[09:37] <amitk> perhaps it would be help to consult him too regarding this problem
[09:38] <smb_tp> That would be helpful, what nick was he using?
[09:40]  * amitk checks his logs
[09:40] <smb_tp> The problems seems to be two sided. The state of the hw loudness seems to automatically change, when pressing the thinkpad buttons. Plus there is no way to see the state of it through the alsa mixer interface
[09:41] <apw> no way to read it huh, that would make life tricky
[09:42] <smb_tp> You can read it
[09:42] <smb_tp> The thinkpad acpi exporses the values through its interface
[09:42] <amitk> smb_tp: his nick is hmh. And log of his conversation is here: http://pastebin.ubuntu.com/154556/
[09:43] <smb_tp> But as it is a separate place it can get a) confusing and b) it is not visible if you look at the mixers in the gui
[09:44] <apw> sounds like there may be some patches coming, if only we knew what they were to fix"
[09:44] <apw> !
[09:45] <amitk> might help to contact him directly
[09:45] <smb_tp> Probably the first good step is not to tie the keys to changes on the hw-mixer
[09:45] <apw> amitk, yeah am looking for his email addy
[11:00] <Kano> hi, does 2.6.30 branch boot?
[11:00] <Kano> could not get it working with intel g35 chipset
[11:13] <amitk> Kano: it does for some people
[11:14] <Kano> i guess that fast boot does not work for me
[11:48] <emgent> it`s possible make an udev hack for manage the kernel module product keys and id ?
[11:48] <emgent> for example A module have: { USB_DEVICE(0x0c88, 0x17da) },
[11:48] <emgent> it`s possible make an alias from it to { USB_DEVICE(0x19d2, 0x0001) }, ?
[12:23] <anubhav> emgent, you can do it through /sys  using  new_id
[13:47] <Kano> hi rtg , how to disalbe that fastboot mode of 2.6.30? it does not start here
[13:48] <rtg> AFAIK you can't yet. I read that Garzik is having problems also, so Arjan is working on an option fast boot setting.
[13:49] <broonie> Yes, there was a thread on lkml on Friday or so.
[14:21] <asac> what bugmail goes to the ubuntu linux-bugs mailing list? all bug mail for linux* packages?
[14:21] <asac> err kernel-bugs i mean ;)
[14:43] <Keybuk> rtg: when I do a config commit, I should run updateconfigs first?
[14:43] <Keybuk> when I do that, several things shift that I didn't expect
[14:43] <Keybuk> seems to have been a while since anyone ran it
[14:43] <Keybuk> ok to just not run updateconfigs?
[14:45] <rtg> Keybuk: if you're making changes to configs, you should run updateconfigs before you make the commit. 
[14:46] <smb_tp> True, seems there was someone forgetting this for armel changes to Jaunty
[14:46] <Keybuk> rtg: but then the patch will include random chaff
[14:47] <rtg> Keybuk: usually it doesn't. you just got lucky.
[14:47] <Keybuk> heh
[14:47] <Keybuk> ok
[14:47] <Keybuk> so about the change
[14:47] <Keybuk> I'd like to disable "libusual" and "ub"
[14:47] <Keybuk> nobody maintains them anymore
[14:47] <Keybuk> RedHat and SuSE don't use them
[14:47] <Keybuk> and they break this Latitude XT that pgraner has promised me I can keep if it's fixed <g>
[14:47] <Keybuk> because libusual causes the kernel to run "modprobe usb-storage" by itself
[14:47] <Keybuk> and it does it before the initramfs has called depmod
[14:48] <rtg> hmm, I don't even know what libusual is.
[14:48] <Keybuk> it's a crazy-arsed thing
[14:48] <Keybuk> it takes all of the aliases away from usb-storage
[14:48] <Keybuk> and builds them into the kernel instead
[14:48] <Keybuk> in theory so you can override it and use "ub" instead of usb-storage
[14:48] <Keybuk> all pre-modalias I guess
[14:49] <Keybuk> so it works by doing the probe match in libusual, then running "modprobe usb-storage" if it's not yet loaded
[14:49] <Keybuk> of course, nobody maintains ub anymore either
[14:49] <rtg> Keybuk: are you proposing this for Jaunty?
[14:49] <Keybuk> Karmic
[14:50] <rtg> oh, no problem for Karmic. send a patch
[14:50] <Keybuk> but since this is a fails-to-boot-from-USB issue for at least one laptop, and reading the code, is going to fail even more I *might* try and persuade it for jaunty
[14:50] <Keybuk> depends whether you're planning another kernel build or not
[14:50] <rtg> Keybuk: there will certainly be -updates uploads. I think smb_tplikely has one about ready to go.
[14:51] <Keybuk> ok
[14:51] <smb_tp> rtg, Not exactly ready to go for Jaunty, but there have been a few changes queueing  up
[14:51] <Keybuk> let me finish testing this, and I'll toss towards ubuntu-kernel the karmic patch and jaunty one "just in case"
[14:52] <Keybuk> (where I'll talk to pete and steve first)
[14:52] <rtg> Keybuk: yeah, I'd like to hold off on any -updates uploads until after Thursday release
[14:53] <Keybuk> this should be config-updates template right?
[14:54] <Keybuk> or patch?
[14:54] <rtg> Keybuk: For Jaunty make it a patch template sine it'll require an SRU. For Karmic, an updates template is fine.
[14:56] <Keybuk> updates doesn't have a bug# field though?
[14:56] <rtg> Keybuk: thats OK for Karmic.
[14:57] <Keybuk> but I want to include the bug# don't I?
[14:58] <rtg> Keybuk: you can if you like. I'm not requiring it for Karmic. In fact, I'll be making lots of changes to Karmic over the next month or so, most of them without a bug reference.
[14:58] <Keybuk> ok
[15:01] <Keybuk> oh arsebiscuits
[15:01] <Keybuk> The ABI Checking strikes...
[15:01] <Keybuk> You die
[15:01] <rtg> Karmic? It should be effectively disabled.
[15:01] <Keybuk> no, testing on jaunty
[15:02] <Keybuk> used HEAD instead of .18
[15:02] <rtg> ah
[15:02] <Keybuk> you'd added a .19 ;)
[15:02] <rtg> I did? or smb_tp ?
[15:02] <Keybuk> you
[15:03] <Keybuk> ff8428c
[15:04] <smb_tp> .19 ? that sounds quite old for Jaunty...
[15:04] <rtg> Keybuk: I'm not sure what you're referring to. Jaunty is at ABI 11, e.g. 2.6.28-11
[15:04] <smb_tp> -11.42
[15:06] <Keybuk> oh...
[15:06] <Keybuk> arse
[15:06] <Keybuk> fetch and forgot to pull ;)
[15:07]  * Keybuk does the lazy man's just make this origin
[15:07] <rtg> Keybuk: you shouldn't be pulling anyway, you should be 'git fetch origin && git rebase origin'.
[15:08] <Keybuk> rebase ?!
[15:08] <Keybuk> rebase is just temptation to not get my patches to you
[15:08] <Keybuk> git fetch origin && git reset --hard origin/master
[15:08] <rtg> Keybuk: correct. that keeps your local changes at the top of the tree.
[15:10] <Keybuk> sure ;)  I don't keep any local changes
[15:10] <Keybuk> if I do any, they're on a topic branch
[15:42] <RainCT> Hi
[15:45] <RainCT> Is some dev around? On Jaunty (since around alpha 5, perhaps a earlier) my filesystem gets corrupted on a daily basis (often when I start fsck will want to run because of unclean shutdown -even though I powered of correctly-, ask me to fix manually and find hunderts or problems, and sometimes it will even switch to read only while I'm using it and be corrupted)
[15:47] <RainCT> This happens with both ext3 and ext4, but only with Jaunty's kernel. I tried Debian Lenny with the default 2.6.26 kernel and 2.6.29 from unstable and those worked fine, and now I'm trying Jaunty with 2.6.29 from kernel.ubuntu.com and I haven't had any problems neither
[15:59] <Keybuk> EE: Missing modules (start begging for mercy)
[15:59] <Keybuk> !!
[16:01] <rtg> Keybuk: you'll need an ignore.modules file. see debian/scripts/module-check for the various options.
[16:02] <Keybuk> oh, I just put a - in the way of the check ;)
[16:04] <Keybuk> but yeah, looks like my patch involves symbols moving and missing modules
[16:04] <Keybuk> not sure how much of a worry that is for -updates
[16:05] <rtg> Keybuk: is it an ABI bumper?
[16:05] <smb_tp> It will need an ABI bump, but the next updates for Jaunty will need one anyway
[16:05] <amitk> didn't we revert a bunch of patches that were bumping abi
[16:05] <amitk> ?
[16:06] <smb_tp> amitk, One I know of. wireless iirc
[16:06] <rtg> amitk: yeah, I postponed one for wireless resume IIRC
[17:20] <xnguard> Can anyone comment on the progress of getting #297213 resolved, or tell me what I can do to work around it in the meantime?
[17:41] <bradf> xnguard: I can look into this, however, it will not make it into the initial Jaunty release
[17:42] <xnguard> bradf: Thanks.
[17:42] <bradf> xnguard: Jaunty kernel is now frozen and only SRU will be accepted
[17:42] <xnguard> Yeah, I sort of guessed it was too late for a kernel module written specifically for a package in universe. :)
[17:43] <bradf> xnguard: I've assigned the bug to myself. Not promising that it will get fixed but If it doesn't for some reason, I will add information to the bug.
[17:44] <xnguard> bradf: Great, thanks.  Any update at all is appreciated at this point. :)
[18:00] <amitk> rtg: union filesystem ---> http://valhenson.livejournal.com/36620.html
[18:01] <Kano> rtg: will you add aufs2?
[18:03] <rtg> Kano: we won't decide until after UDS
[18:04] <Kano> why decide, just add to try it
[18:05] <Kano> you would only need to packag new aufs2 tools
[18:06] <Kano> if you dont add you can not try
[18:18] <speakman> hi folk. I can't find PPP in kernel menuconfig. Do I have to enable anything to see it?
[18:20] <speakman> Oh, it was in device driver menu. Strange
[18:24] <Keybuk> BEFORE
[18:24] <Keybuk> wing-commander scott% modinfo usb-storage | grep "^alias:" | wc -l
[18:24] <Keybuk> 0
[18:24] <Keybuk> AFTER
[18:24] <Keybuk> wing-commander nolibusual% modinfo lib/modules/2.6.28-11-generic/kernel/drivers/usb/storage/usb-storage.ko | grep "^alias:" | wc -l
[18:24] <Keybuk> 350
[23:07] <jameswf> Echo echo echo..
[23:08] <jameswf> Stefan/Brian Rogers apparently commited a fix for #268502 Anyway to get saifd files without cloning the whole git tree