=== jedubarbo [n=eduardo@200.139.100.177.dialup.gvt.net.br] has left #ubuntu-kernel ["Ex-Chat"] === doko_ [n=doko@dslb-088-073-126-081.pools.arcor-ip.net] has joined #ubuntu-kernel === ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-kernel [12:53] BenC: ping [12:54] ...if you arent watching football [01:13] BenC: Yeah, I could do with another fgrlx version bump. I'll prepare it today. === tormod [n=tormod@80-219-112-71.dclient.hispeed.ch] has left #ubuntu-kernel ["Ex-Chat"] [03:08] zul:games over, skins won [03:08] zul: what's up? [03:18] BenC: whats with the ubuntu-edgy gits [03:33] zul: Tollef fixed some arch includes in your xen git tree, apparently. Mind doing an upload of that, so xen-restricted-modules doesn't FTBFS? [03:34] infinity: sure [03:34] oh btw the new git archive is http://dev.laptop.org/git.do?p=projects/ubuntu-xen-2.6.17;a=summary [03:35] Not much plan here to do anything with it. I was only fixing xen-r-m for you, out of the kindness of my heart (or because I was bored yesterday; pick one) [03:36] i would like to think its kindness but im picking bored :) [03:41] In the future, try to remember to use the LRM orig.tar.gz for XRM... Uploading 90 MB to make a few K of fixes was unfun. :) [03:41] (I'll rev XRM for you when I bump fglrx in LRM) [03:41] thanks [03:42] sorry...wont happen again [03:43] Is your git tree synced with the main kernel? [03:44] If so, I was wondering if it might not be a bad idea to artificiall bump your ABI to match, so people know that the xen kernels have the same set of fixes/drivers. [03:44] If the source isn't even close to common, then don't do that, obviously. :) === infinity -> shower. [03:45] no it hasnt been synced up yet unforuntaely.. === zul_ [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel [04:24] zul_: ubuntu-edgy gits are where edgy kernel is coming from now [04:24] I'm taking some time to merge ubuntu-2.6 to latest kernel [04:24] start getting out some daily builds early for bleeding edgy fools like me :) [04:25] 2.6.19 development is probably going to lead out about 2 months into our next release, so I want to get a head start...have packages ready the day edgy+1 opens up [04:25] plus make packages available for jbailey and doko for edgy+1 toolchain === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel [05:34] BenC: ping? === User75 [n=root@202.87.217.146] has joined #ubuntu-kernel === User75 [n=root@202.87.217.146] has left #ubuntu-kernel ["Leaving"] [06:33] BenC: dude.. you didn't pull the PROM_CONSOLE patch in 10.25... [06:33] we need that to fix the CPU softlookups on NIagara === fabbione prepares a kernel upload === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === makx_ [n=max@baikonur.stro.at] has joined #ubuntu-kernel === lfittl [n=lfittl@194.50.115.210] has joined #ubuntu-kernel === Keybuk [n=scott@syndicate.netsplit.com] has joined #ubuntu-kernel === _human_blip_ [n=mike@220.157.65.29] has joined #ubuntu-kernel === fabbione [i=fabbione@gordian.fabbione.net] has joined #ubuntu-kernel === lfittl [n=lfittl@81-223-149-226.rasumofskygasse.xdsl-line.inode.at] has joined #ubuntu-kernel === lloydinho [n=andreas@stop.codon.org.uk] has joined #ubuntu-kernel === Lure_ [n=lure@external-7.hermes.si] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === rodarvus [n=rodarvus@ubuntu/member/rodarvus] has joined #ubuntu-kernel [01:21] is there a reason for using git instead of quilt/quilt-like for the ubuntu kernel tree ? [01:21] I see other distro are using a quilt like process [01:22] and that way you can cleanly see the different features they added === tonfa was looking at the apport patch [01:24] Much easier to cherry-pick changes from upstream with git. [01:25] but couldn't it be converted to a patch ? [01:25] "it"? [01:25] cherry-pick is just patch importing + 3-way merge, right [01:25] the cherry-picked changeset [01:26] You want a massive "ubuntu" patch to see against the upstream kernel, or you want every one of our patches broken out? [01:26] The latter is a serious pain, because then you can't easily use git anymore to merge as both we and upstream move. [01:26] infinity: could you kick 3.0.3~rc1 in the butt its still stuck in binary-new [01:26] that's the same workload as akpm [01:26] (for instance, Ben is currently merging our 2.6.17 with upstream's 2.6.19... Much simpler without dealing with hundreds of patches outside of git) [01:27] quilt pop -a ; update to upstram ; quilt push -a [01:27] *upstream [01:27] Erm, no. You're not quite grasping it. [01:27] you will have to resolve conflicts during the push, of course [01:28] If you have a revision history that says "I pulled changeset 1234 from 2.6.18", and 2.6.19 has the same in its history, the merge is seamless. If we have a bunch of patches, we have to hand-merge them or examine each one to see if we should discard it. [01:28] The latter is far more effort, for very little gain. [01:28] zul: I'll poke it in a sec. I've been pitti's bitchs with mangling security builds for a while. [01:29] infinity: coolio...thanks [01:30] zul: Are you going to give me an unbroken xen-source-2.6.17? :P [01:31] i just uploaded it last night [01:31] argh...it timed out on me.. [01:31] yeah ill upload it again [01:31] Kay. xen-3.0 processed. [01:32] thanks.. === gnomefreak [n=gnomefre@adsl-221-54-152.rmo.bellsouth.net] has joined #ubuntu-kernel [01:40] infinity: but you can first drop all the backports, when merging to the upstream version [01:41] right im off to work [01:43] tonfa: This implies we only have one upstream. [01:43] what is the other upstream ? [01:43] tonfa: We merge patches from all over, and prefer to merge from git repos that all merge to<->from linus, so it all sort of self-resolves (with exceptions, of course) [01:44] so upstream is linus-2.6 [01:44] tonfa: We're certainly not just backporting from one branch, is my point. [01:45] Anyhow, not much point in arguing it, the decision was made during the dapper cycle, it's worked well for us, I don't think Ben (who has to do the majority of the work) is itching to switch. [01:45] ok, I understand that it makes the work easier for you [01:46] (but not necessarly for other people, distro) [01:46] yes, we're aware that patch-digging becomes a bit more difficult. [01:46] But that's not really our number one goal either. === ph8 [n=ph8@0-12-3f-d7-62-c8.it.roam.dur.ac.uk] has joined #ubuntu-kernel [02:11] utrace looks interesting for implementing apport [02:44] god...i love monday mornings dns died at work [02:45] fabbione: ping [02:59] BenC: ping [03:03] zul: pong [03:06] BenC: the kernel-package patch i was talking about is at http://70.29.61.171/ubuntu/kernel-package-debdiff.patch [03:13] zul: thanks === AnAnt [n=anant@81.10.9.182] has joined #ubuntu-kernel [03:15] there is a bug in the kernel I think [03:15] when I insert my MMC card it doesn't get mounted [03:15] I have to manually modprobe tifm_sd [03:17] mmc layer isn't very hotplug friendly [03:18] huh ? [03:18] BenC: but it used to work in 2.6.15 when I patched the kernel [03:19] BenC: I patched the kernel for MMC4 [03:19] it was a couple of lines only [03:19] I don't think that this patch did anything to hotplug, and it worked in Dapper [03:20] by hotplug I mean that the drivers either provide the right information so that hotplug knows to load the module, or it loads the module itself [03:21] tifm wasn't in dapper, IIRC [03:21] hmm [03:21] so it won't be fixed at stable release ? === ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-kernel [03:24] hi [03:26] BenC: i could upload the fix if you want [03:38] BenC: pong === pschulz01 [n=paul@202.174.42.5] has joined #ubuntu-kernel [03:50] BenC: i need to take my son out for a walk. will try to pass by later [03:59] zul: the fix you talk about is for the MMC ? [04:00] wha? [04:00] zul: nevermind [04:00] i need the context [04:02] BenC: what are the chances of getting xen into the edgy+1 kernel? [04:02] i mean i can do the necessary grunt work though [04:05] zul: Well, I'm starting from scratch on the edgy+1 kernel [04:05] I want to take a different route with some of the stuff we've been doing [04:05] BenC: will you consider using a queue of patches ? [04:05] mainly, I want all our external drivers in an ubuntu/ sub directory to keep things cleaner [04:05] tonfa: no [04:06] ok [04:06] BenC: ah ok so what like debian is doing now [04:06] tonfa: But the subdirectory for our custom drivers will make it easier to diff things and such [04:06] s/custom/third-party/ [04:06] heh well let me know when you have something and i can beat it in [04:07] there's way too many conflicts when I go from one major version to another === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel [04:22] BenC: we've never mounted /proc/bus/usb with special permissions to give other people write access [04:22] that would be bad [04:27] BenC: re [04:28] Keybuk: I don't disagree with the permissions, but I disagree that doing it that way would solve the problem [04:28] fabbione: where can I pull your kenrel upload changes from? [04:28] BenC: the patch is the same as the one i did send via email to you and davem. [04:29] i had to do the upload without git, because you created the edgy branch and i wasn't sure from which one you did release 10.24 [04:29] fabbione: most likely from edgy? :) [04:29] BenC: kernel.org/git doesn't show any history for that branch.. only 2 commits [04:29] that's why... [04:29] otherwise i would have done it :) [04:30] i admit i got confused [04:30] no problem [04:30] but i can resend you the debdiff === mayday_jay [n=mayday_j@gimel.nas.net] has joined #ubuntu-kernel [04:30] you did use the .orig.tar.gz, right? [04:30] yes [04:30] excellent [04:30] i used apt-get source [04:30] + the patch + changelog [04:30] of course mv debian/abi/foo to match the upload [04:31] no more no less [04:31] BenC: which problem? === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel [04:37] Keybuk: The problem where vmware can't access USB devices [04:37] I've no idea what vmware does to that directory [04:37] then they had that problem with dapper [04:37] it reads/writes to the dev entries [04:37] dapper didn't give anything other than root access to them [04:38] I'm not arguing that [04:38] the fix is easy [04:38] make vmware look in /dev/bus/usb first [04:38] and then the user running vmware will have permission to write to any usb devices that the user has permission to write to [04:39] if vmware were configurable to do that, we wouldn't be discussing this :) [04:39] I personally don't care either way, and I'm not pushing for a real fix [04:39] the whole point of our relationship with vmware is that we can get them fix this kind of thing, no? [04:40] I'm just saying that if proc/bus/usb gets mounted like you are saying, there's no point in doing so [04:40] the reason /dev/bus/usb was *invented* was this problem - giving non-root users access to usb devices [04:40] I'm out of the loop on this [04:40] like I said, I'm just pointing out that it's useless to mount it with 0600 perms if it's not going to help [04:41] I'm not saying mount it with other perms, just don't mount it at all if the security issues are the case [04:41] haven't people claimed that mounting it (with the default 644 perms) fixes it? [04:41] yes, it does [04:41] how does that fix it? [04:41] it can't write to the devices still [04:41] err, well not really [04:41] 644 allows vmware to see the device, but not use it [04:43] ok [04:43] doesn't vmware just use its kernel modules of doom to do this kind of thing? [04:44] Keybuk: how does one get perms for /dev/bus/usb/ devices? [04:44] /etc/udev/rules.d [04:44] Keybuk: no, it doesn't use the kernel module since the internal API changes a lot more than the userspace one does [04:44] e.g. /etc/udev/rules.d/45-libgphoto2.rules [04:46] I wish dev/bus/usb had a devices file, we could just bind mount it [04:48] we could probably fake one :p [04:48] have a udev rule that updates it every time a usb device is added or removed [04:48] reads from sysfs [04:48] and writes out the file [04:49] /win 11 [04:49] oops [04:49] probably easier to just mount usbfs somewhere hidden, bind mount /dev/bus/usb to /proc/bus/usb and copy the file when usb devices are added or removed [04:51] for some reason my vmware has started running slow as balls [04:52] loadavg is 0.00, and vmware is crawling [04:52] Keybuk: copying the file and bind mount dev/bus/usb to proc/bus/usb seems to let vmware see the device [04:53] I'm trying to test if it actually can use it after I manually changed the perms === Atthar [i=atthar2@85.133.179.30] has joined #ubuntu-kernel [04:57] hi room [04:58] i want to download linux driver for my modem, what is kernel of 6.06 LTS version? [04:59] Atthar: uname -a [05:00] im in windows now! [05:00] its 2.6.15 [05:02] tnx, but plz see this page: http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php i need full number of kernel [05:02] Atthar: that's why you need to use that command: uname -a [05:03] or atleast uname -r [05:03] ok, tnx BenC [05:03] there are at least 5 different kernels types (flavours) in dapper x86, and depending on if you have the latest kernel version, at least 4 revisions [05:05] ok, firs i will install the ubuntu and then use uname -a, tnx and good luck :) === Atthar [i=atthar2@85.133.179.30] has left #ubuntu-kernel [] [05:07] Keybuk: also, why do you want to make proc/bus/usb 0600, when the devices under dev/bus/usb are 0664? [05:07] I don't suggest making it anything? [05:07] it'd probably be whatever the default is [05:07] which appears to be 0644 [05:08] your first email said 600 [05:08] devmod=600 is what you sent [05:08] oh, maybe I was on crack for that one === BenC takes the pipe away from Keybuk [05:09] Keybuk: I think the bind mount and coping of the devices list is going to be our best bet if you are willing to implement it [05:09] where to mount it though? === tuxmaniac [n=aanjhan@59.92.87.3] has joined #ubuntu-kernel [05:10] hide mount usbfs somewhere with really strict perms, and bind mount dev/bus/usb to proc/bus/usb, copying the devices file on events [05:10] dev/bus/usb/.usbfs ? [05:12] *nods* [05:12] can do that in mountdevsubfs [05:17] what was linux-meta ? [05:17] (that's mentionned in : https://wiki.ubuntu.com/KernelTeam) [05:19] tonfa: linux-meta is a set of meta packages that makes sure you always have the latest kernel and associated packages with it [05:20] ok, thanks === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === AnAnt [n=anant@62.139.225.211] has joined #ubuntu-kernel [05:27] I removed the quiet option to get boot messages [05:28] the problem is that it corrupts the scroll bar [05:28] is there a way to change the position in which the boot messages appear ? [05:28] more of a question for #ubuntu [05:28] I'm talking about Edgy not Dapper [05:28] remove the splash option too [05:29] BenC: but I won't get splash screen then ? [05:29] dapper or edgy, it's still an issue of #ubuntu...not kernel related :) [05:29] oh [05:29] AnAnt: nope [05:29] BenC: nope = I won't get splash screen ? [05:29] correct [05:30] thanks === AnAnt [n=anant@62.139.225.211] has left #ubuntu-kernel [] === Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel === kbyrd [n=Miranda@mailout1.vmware.com] has joined #ubuntu-kernel === jwest- [n=jwest@unaffiliated/jwest/x-422957] has joined #ubuntu-kernel === lfittl [n=lfittl@chello080109027166.17.14.vie.surfer.at] has joined #ubuntu-kernel [06:25] BenC: devmode only takes effect for the devices themselves, not for the "devices" file [06:27] Keybuk: right [06:27] devices file is the listmode= option [06:28] there's {dev,bus,list}{uid,gid,mode} [06:28] dev is the files, bus is the subdirs, and list is the "devices" file itself [06:28] so we could just symlink it :) [06:30] drwxr-xr-x 2 root root 40 2006-10-02 17:29 .usbfs/ [06:30] drwxr-xr-x 2 root root 80 2006-10-02 08:21 001/ [06:30] drwxr-xr-x 2 root root 60 2006-10-02 08:21 002/ [06:30] drwxr-xr-x 2 root root 60 2006-10-02 08:21 003/ [06:30] lrwxrwxrwx 1 root root 14 2006-10-02 17:30 devices -> .usbfs/devices [06:30] ah, sub-mounts don't follow bind mounts [06:30] boo === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === Keybuk tries --rbind instead [06:34] Keybuk: Ah, true [06:35] link it to /dev/bus/usb/.usbfs/devices directly would work too [06:35] link which to? [06:35] oh, I see === mayday_jay [n=mayday_j@gimel.nas.net] has joined #ubuntu-kernel === lfittl [n=lfittl@217.19.46.18] has joined #ubuntu-kernel === tuxmaniac [n=aanjhan@unaffiliated/tuxmaniac] has joined #ubuntu-kernel === tormod [n=tormod@80-219-112-71.dclient.hispeed.ch] has joined #ubuntu-kernel === jwest- [n=lore@83.110.124.122] has joined #ubuntu-kernel === Lure_ [n=lure@clj46-234.dial-up.arnes.si] has joined #ubuntu-kernel === lfittl_ [n=lfittl@217.19.46.10] has joined #ubuntu-kernel === ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-kernel === marcin_ant [n=marcin@194.114.146.122] has joined #ubuntu-kernel [10:03] right later === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === poptones [n=poptones@206.41.235.163] has joined #ubuntu-kernel [10:29] hello? === poptones [n=poptones@206.41.235.163] has left #ubuntu-kernel [] === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === jldugger [n=jldugger@adsl-71-149-200-224.dsl.tpkaks.sbcglobal.net] has joined #ubuntu-kernel [10:40] is there a known issue with nvidia-glx working on -10-386 and not -10-generic? [10:43] how bad is it that "modprobe toshiba_acpi" segfaults? === tormod [n=tormod@80-219-112-71.dclient.hispeed.ch] has left #ubuntu-kernel ["Ex-Chat"] === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === zul [n=chuck@CPE0006258ec6c1-CM000a73655d0e.cpe.net.cable.rogers.com] has joined #ubuntu-kernel === gnomefreak [n=gnomefre@ubuntu/member/gnomefreak] has joined #ubuntu-kernel === lfittl [n=lfittl@chello080109027166.17.14.vie.surfer.at] has joined #ubuntu-kernel [12:05] who works with nvidia-glx in here?