[03:28] <DBO> hello all, I know I must be sounding like a broken record.  I am growing more frustrated with trying to get suspend working
[03:28] <DBO> is there any way I can help debug an issue with the drm.ko module?  Removing it fixes my suspend (at the cost of hardware accel)
[04:03] <DBO> can I get some help trying to compile a new version of the i915 driver with some patches I found?
[12:25] <laga> amitk: hows aufs looking?
[12:26] <amitk> good, I am compiling the lpia kernel and upload that, then I apply your patches to ubuntu kernel, test with some live cds
[12:27] <amitk> laga: there won't be a kernel upload before beta it seems though. sorry.
[12:28] <amitk> unless we get a fix to the e1000e bug for which rtg has sent a patch
[12:32] <laga> i think i can live with that :)
[12:34] <amitk> laga: atleast the mobie team will be using your aufs for their live-usb-sticks. They have a separate kernel where I can push these patches today.
[12:34] <laga> yeah, i need it in generic for mythbuntu-diskless.
[12:34] <amitk> *your aufs patches, that is
[12:51] <tjaalton> amitk: what do you mean by "Signed-off:", I should use gpg-sign?-)
[12:54] <smb_tp> tjaalton, I guess he just meant that the patch should include a line "Signed-off-by: name <email>"
[12:54] <tjaalton> smb_tp: oh, ok
[12:54] <smb_tp> tjaalton, It also would be interesting: where did that patch come from? It wasn't in upstream yesterday
[12:55] <tjaalton> smb_tp: from the linuxwacom tarball
[12:55] <tjaalton> linuxwacom.sourceforge.net
[12:56] <tjaalton> src/linux-2.6.26, diff the files against our kernel
[12:57] <tjaalton> unless I've f****d things
[12:57] <tjaalton> +up :)
[12:58] <smb_tp> tjaalton, :) If it works for you. Just have to see whether this also goes upstream or has to be promoted.
[12:58] <amitk> tjaalton: exactly what smb_tp said. And it is good to know the provenance of the patch (where it came from)
[12:59] <tjaalton> amitk: ok, should've included the url then. I'll update the patch
[13:00] <tjaalton> my tablet doesn't seem to need the module at all, so I haven't tested it myself
[13:01] <amitk> tjaalton: in that case, do you know if it _does_ fix it for somebody? No point in applying the patch otherwise.
[13:01] <tjaalton> amitk: of course, as I said "bug foo confirms that .."
[13:02] <tjaalton> there are a couple of users who got it working by compiling this version of the module
[13:04] <amitk> tjaalton: ok. read through the bug now. Please send Signed-off line with a URL
[13:06] <tjaalton> amitk: like this? http://users.tkk.fi/~tjaalton/dpkg/wacom-1.49.patch
[13:06] <tjaalton> uh
[13:07] <tjaalton> ok there
[13:08] <amitk> tjaalton: looks ok
[13:13] <tjaalton> amitk: great
[13:59] <asac> hi. one questions. whats the idea for those 3g modems that also are storage devices. usually folks now write their own udev rules to get that working. is there anything we can do in general to prefer the modem driver vs. the storage thing?
[14:02] <amitk> asac: Arne showed me one that had two different USB ids. On insertion, it first acted as a mass storage device, then you had run some program to switch to the other device. If other devices are similar it seems like something that should be handled in userspace.
[14:03] <asac> amitk: well. i talked to dan williams at some point and he said that the storage thing should be blacklisted or something
[14:04] <asac> amitk: not really sure what he means by that. will try to ask him again
[14:05] <amitk> asac: i guess he means blacklisting a specific usb id from the storage driver. That would make the storage never work. Better ask him.
[14:06] <asac> amitk: right. but the storage thing is really just a tiny storage used to ship the windows drivers
[14:06] <asac> amitk: i had something similar for a wifi stick
[14:06] <asac> fwlanusb
[14:06] <asac> before i fixed the driver it was always storage
[14:06] <asac> with the windows driver on it
[14:07] <asac> but once fwlanusb driver was proper, things just worked (e.g. no storage device popping up)
[14:07] <asac> amitk: i think dan williams didnt say "blacklist", but "give the modem driver higher prio" ... does that make sense to you?
[14:08] <amitk> asac: not sure what giving higher prio means.
[14:09] <asac> amitk: maybe making udev first modprobe the modem driver before trying storage?
[14:10] <asac> anyway. i will try to get a word from the master on this ;)
[14:23] <Zhenech> asac, there are 3g sticks that really need an userspace app to tell them "no, dont do storage, do 3g"
[14:24] <Zhenech> i think option makes those
[14:24] <asac> Zhenech: ok. but there area also others that would do the right thing when the modem driver would be tried first?
[14:26] <Zhenech> asac, to be honest, I dont know, I only had "normal" modems and these "i need a app" sticks in my hands till now
[14:26] <amitk> asac: the ones Zhenech mentions are the only ones I have seen. If there are saner ones, then by all means we could blacklist them in the storage driver.
[14:27] <asac> ok. so in the end NM probably has to do that :(
[14:27] <Zhenech> you can find a lot of information about these on pharscape.org
[14:28] <Zhenech> asac, perfectly udev would do "oh, its a storage, but the id I know to be a 3g, lets call <tool> to enable modem"
[14:28] <Zhenech> so it happens on plugin of the modem directly
[14:28] <asac> Zhenech: yeah. but then how do we find all the ids of those devices?
[14:28] <Zhenech> as everyone uses udev, but not everyone uses NM
[14:29] <asac> Zhenech: yeah. but people not using NM are usually more skilled ;) and even like to find out about udev rules :-P
[14:29] <asac> but agreed
[14:29] <asac> at best this would happen at the lowest level possible
[14:30] <Zhenech> see this post http://www.pharscape.org/component/option,com_forum/Itemid,68/page,viewtopic/t,545/
[14:30] <Zhenech> it contains the utily I mentioned for option cards
[14:30] <Zhenech> and udev rules with all the shiny ids needed :)
[14:32] <Zhenech> here are probably more http://www.pharscape.org/component/option,com_forum/Itemid,68/page,viewtopic/t,425/
[14:32] <Zhenech> asac, sponsor me such a card and I'll package it :>
[14:33] <asac> Zhenech: show me where the source is ;)
[14:33] <asac> i cant find it :)
[14:33] <asac> (for ozercdoff)
[14:34] <Zhenech> the udev.tar.gz attached to the post has everything
[14:34] <Zhenech> the name is ... bad ;)
[14:34] <asac> Zhenech: isnt that released fro ma more official place?
[14:35] <Zhenech> not that I would know off
[14:35] <Zhenech> afaik linux support for the option hardware is only semi-official
[14:36] <asac> Zhenech: ok. but its hso-udev.tar.gz ... or is there a plain udev.tar.gz that i dont see?
[14:37] <Zhenech> http://www.pharscape.org/component/option,com_forum/Itemid,68/page,viewtopic/t,545/ lists only udev.tar.gz, 26kb big
[14:43] <Zhenech> (the other link has a hso-udev file)
[14:50] <DBO> ping abogani 
[15:01] <abogani> DBO: pong
[15:01] <DBO> abogani, can you help me understand why your kernel is the only kernel with which my machine will suspend?
[15:01] <DBO> i am on intrepid, using the linux-rt kernel you created
[15:02] <DBO> it suspends wonderfully, every other kernel hard locks on resume when the drm module is loaded (they work fine if I dont load drm)
[15:03] <abogani> It is very hard to say. Generally rt incur in suspend/hibernate problems...
[15:03] <DBO> i tried recompiling the latest -generic kernel for intrepid using your config, and I even tried using your config against the stable 2.6.26 kernel
[15:04] <DBO> i can't seem to grab the source for your kernel however, apt-get sourceing it just gets me a debian/
[15:04] <DBO> abogani, did you do anything special to the drm module?
[15:04] <abogani> rt config is very close to -generic one except for rt specific configurations.
[15:04] <abogani> No at all.
[15:05] <DBO> any clue why my console is screwed up in your -rt kernel... it blinks red and black off and on
[15:05] <abogani> What video driver are you using?
[15:05] <DBO> i915
[15:05] <DBO> I am just trying to piece it all together, maybe with enough hints I can figure out how to get a reliable machine =/
[15:06] <abogani> Sorry i don't have experience to this type of hardware.
[15:07] <DBO> abogani, I also experience some freezing with your kernel
[15:08] <DBO> something about bad page state
[15:08] <DBO> I had emailed you a backtrace to your ubuntu email right before contacting you here
[15:18] <abogani> DBO: I suspect that upstreams already have fix that bug. Anyway keep in account that -rt will be dropped in Intrepid.
[15:19] <DBO> intrepid is not going to have -rt at all?
[15:19] <abogani> Not provided by me at least.
[15:20] <abogani> Sorry
[15:20] <DBO> =/ sucky... its the only real kernel that works for me.
[15:20] <DBO> I can't be the only one out there with an intel x4500 integrated gpu
[15:20] <DBO> well I know I am not, there is at least one other guy with the same problem
[16:33] <munckfish> smb_tp: any news on the ports build?
[16:34] <smb_tp> munckfish, I've prepared something that should build but I still have to get someone to upload it...
[16:34] <munckfish> smb_tp: ok
[16:35] <munckfish> smb_tp: seeing as it's not uploaded now - if I wanted to get another patch in now before the beta would that be a PITA or easy?
[16:37] <smb_tp> munckfish, Well closer to PITA since I pushed the things needed for the upload to the repo already
[16:37] <munckfish> smb_tp: np I'll wait till after
[16:58] <elventear> Hello. I am looking for the netback.c file in the netback driver for the latest Hardy stable Kernel. I downloaded the source from the repo and cloned the hardy git repo and the file is missing. Where should I look for such file?
[17:01] <IntuitiveNipple> What is the kernel module name?
[17:02] <IntuitiveNipple> Isn't that in Xen?
[17:13] <elventear> IntuitiveNipple: Xen would be the Git Repo?
[17:16] <IntuitiveNipple> The only Ubuntu xen repo's I know of are Chuck Short's, for intrepid
[17:17] <elventear> Where do the sources for llinux Xen kernel would come from? The said file is not under Xen
[17:18] <elventear> Only Xenbus stuff is
[17:18] <IntuitiveNipple> elventear: I'm not sure
[17:19] <elventear> There is an Ugly bug in the Xen Kernel, and I am trying to debug it. I have been told that there is where the bug might reside
[17:19] <elventear> But I want the source that Ubuntu uses
[17:20] <IntuitiveNipple> elventear: For building it, last time I looked, it required the "custom-binary-xen" target in the Ubuntu kernel build process.
[17:20] <IntuitiveNipple> elventear: And "debian/rules custom-prepare-xen" should show the xen patches
[17:21] <elventear> Ok
[17:21] <elventear> Thanks
[17:21] <IntuitiveNipple> elventear: That info came from the kernel mailing-list in April, so it ought to be valid
[17:21] <IntuitiveNipple> elventear: Although, that was Hardy of course
[18:04] <superm1> BenC, , persia and i were looking at bluetooth support in intrepid and running into lots of issues with btusb.  is there any particular reason we are tied to switching to it when  the hci-usb stuff is still available?
[18:05] <superm1> (or anyone else whom is relatively informed on this)
[19:57] <fabbione> BenC: ping?
[19:58] <fabbione> rtg: ping?
[19:58] <rtg> fabbione: yo
[19:59] <fabbione> rtg: hey.. did any of you pulled from my gfs1/2 tree into intrepid (both normal and ports)?
[19:59] <fabbione> i can't see anything in the last kernel releases
[19:59] <rtg> fabbione: I remember doing it once, but nothing recently.
[20:00] <rtg> BenC has been leading the charge on Intrepid. I've been busy on other things.
[20:00] <fabbione> i did send another pull request after 2.6.27 was first uploaded to intrepid
[20:00] <rtg> lemme dredge through the list and find it.
[20:01] <fabbione> no BenC didn't pull
[20:02] <fabbione> you are shipping a broken gfs1 and gfs2
[20:02] <fabbione> s/you/BenC
[20:02] <fabbione> eek
[20:02] <fabbione> i said it correctly before :)
[20:02] <fabbione> BenC didn't pull
[20:03] <rtg> Did you send your pull request in September? I don't see it, but my eyes might be getting tired.
[20:03] <fabbione> probably august
[20:04] <rtg> https://lists.ubuntu.com/archives/kernel-team/2008-August/002854.html
[20:04] <fabbione> there is one from 27th of Aug
[20:04] <fabbione> in my sent folder
[20:05] <fabbione> https://lists.ubuntu.com/archives/kernel-team/2008-August/003004.html
[20:05] <fabbione> this one
[20:05] <fabbione> so 002854.html still has the request for -ports that has not been done at all
[20:05] <fabbione> the latter has extra for supported arches
[20:05] <fabbione> that has not been done either
[20:06] <rtg> fabbione: I'll sic smb on the https://lists.ubuntu.com/archives/kernel-team/2008-August/002854.html request, and handle the Intrepid pull myself.
[20:06] <superm1> rtg, can you check if the current patchset for btusb suspend support is added into the current 2.6.27 tree we're shipping with, i ididnt think it was? http://www.kernel.org/pub/linux/kernel/people/holtmann/patch-2.6.26-mh5.gz
[20:07] <fabbione> rtg: "sic smb"? 
[20:07] <smb_tp_> rtg, you do what?
[20:07] <rtg> superm1: uno momento
[20:07] <rtg> smb_tp_: maybe you should respin the -ports upload after pull fabbione's gfs2/gfs1 patches.
[20:08] <superm1> marcel posts these to http://www.bluez.org/, and this was just a few days old - so i'd think not generally
[20:08] <fabbione> ah ok
[20:08] <fabbione> got it
[20:08] <fabbione> rtg: anyway it's _very_ important you get the changes for supported arches
[20:08] <fabbione> rtg: what you have there for gfs1 is totally broken
[20:08] <fabbione> gfs2 is exporting unrequired symbols and other stuff
[20:08] <rtg> fabbione: ok, I'm getting the message :)
[20:09] <fabbione> ok..
[20:09] <fabbione> thanks
[20:09] <smb_tp_> rtg, hm. ok. munckfish isn't around but then I can take his one more thing as well
[20:19] <smb_tp_> fabbione, ports pulled
[20:20] <fabbione> smb_tp_: thanks
[20:29] <rtg> fabbione: I pulled after rebasing your tree. Its been long enough that I'm doing a test build before pushing it back out.
[20:45] <rtg> superm1: looks like that pathc is already in Linus' tree, so we'll pick it up on the next rebase.
[20:46] <rtg> s/pathc/patch/
[20:46] <superm1> rtg, any estimate on when that should be happening?
[20:47] <rtg> should be soon. -rc7 is close to week old now, isn't it?
[20:48] <rtg> fabbione: I pushed your bits
[20:48] <superm1> okay great, thanks rtg