[00:30] <yotux> I saw request for help with Nvidia Drivers I would like to help out
[00:32] <RAOF> Which request?  Nouveau or the binary nvidia drivers?
[00:33] <yotux> proprietary drivers, so I think binary
[00:34] <yotux> Sorry I failed to read who to email
[00:46] <bryceh> yotux, contact ara
[00:47] <yotux> am going to do so thank you
[03:54] <tjaalton> bryceh: merged mesa 7.7-4, though it pulled from the stable branch and probably would need some paperwork
[03:55] <tjaalton> didn't upload of course due to a3
[03:58] <bryceh> tjaalton, ok
[04:01] <tjaalton> do you think we need standing FFe's for mesa & xserver? there's 7.7.1 coming late March and 1.7.6 "some time"
[04:13] <bryceh> tjaalton, as long as we can justify them as bug-fix only releases, I think we're covered by the point release policy
[04:14] <bryceh> tjaalton, although it couldn't hurt to do an FFe anyway if you think it'd help to have added visibility on them
[04:16] <tjaalton> bryceh: alright, maybe when those point-releases happen then :)
[04:17] <bryceh> btw, I've started tagging bugs by the release they were reported against, so when looking at bugs we can query for has_tag==lucid
[04:18] <tjaalton> is there a tag for edgers=
[04:18] <tjaalton> ?
[04:18] <bryceh> no, but there probably should be
[04:18] <bryceh> do you like 'edgers'?  I can add that to the processor
[04:20] <tjaalton> it's alright I guess
[04:20] <bryceh> done
[04:21] <bryceh> the script runs once a week on saturday
[04:23] <tjaalton> ok
[04:36] <bryceh> 1.6.4 feels sooo old
[04:38] <tjaalton> ancient..
[18:07] <toabctl_> hi
[18:08] <toabctl> hi
[18:08] <toabctl> can anybody help with bug #527912 ?
[19:09] <tjaalton> toabctl: http://sourceforge.net/mailarchive/forum.php?thread_name=4B3A8A6B.20205%40openwebboard.org&forum_name=linuxwacom-discuss
[19:11] <toabctl> tjaalton, why do you know that the kernel component doesn't support the tablet?
[19:12] <tjaalton> toabctl: because the id isn't listed there
[19:12] <toabctl> ok
[19:16] <tjaalton> none of the new bamboo's are
[19:22] <toabctl> hm. shit
[19:34] <Sarvatt> tjaalton: i'm pretty sure mesa shouldn't require a FFe, i dont see any new features since our snapshot just bugfixes? xserver probably would though since it reenables the record extension though then again thats just fixing something that was broken.. :D kklimonda: got a dmesg from it failing with the newer nouveau? I added the no firmware required patch to that one
[19:36] <tseliot> Sarvatt: what change in mesa?
[19:36] <Sarvatt> 7.7-4 from 7.7-3
[19:37] <tseliot> ok
[19:39] <Sarvatt> maybe we should drop mach64 since its not in the kernel and would save ~1MB of cd space
[19:40] <Sarvatt> if squashfs compresses similar to gzip -9 that is
[19:40] <Sarvatt> makes almost no difference in the deb size since its lzma but its about 930k at gzip -9
[19:41] <Sarvatt> it required building the drm kernel modules from libdrm 2.4.15 or older and all that was dropped from libdrm
[19:41] <tjaalton> Sarvatt: ok
[19:42] <tjaalton> is the cd-size an issue still?
[19:43] <Sarvatt> i see them talking about dropping language packs all the time in -devel and not being able to fit french or german right now
[19:43] <jcristau> Sarvatt: seems sane to me..
[19:43] <tjaalton> heh, ok
[19:46] <Sarvatt> i810 and sis i'm unsure about too, i never was able to get sis to work at all but I havent found any more info on it
[19:57] <kklimonda> Sarvatt: I got nothing in dmesg but there was a "CtxProg is still running" message printed on vt along with some other message - I didn't have a camera to make screenshot and couldn't get it to display again later so I guess it doesn't help :)
[19:58] <kklimonda> Sarvatt: no - wait, I have it
[19:59] <kklimonda> Sarvatt: http://pastebin.com/u3yLdEvW - SAK is from me trying to get some response from system :)
[20:14] <bryceh> Sarvatt, -sis we should keep; I periodically get bug reports on it so someone must use it
[20:14] <bryceh> i810 can go, that's long obsolete
[20:15] <bryceh> I think with disk space, the dropping of Gimp bought a bit of breathing room, but we're adding nouveau bits now so if there's stuff we can excise from the cd it'd be a nice thing to do
[20:15] <bryceh> and of course debdiffs welcome :-)
[20:24] <toabctl> tjaalton, in xf86-input-wacom-0.10.4/src/wcmUSB.c are some lines like:{ 0xD3, 2540, 2540, &usbBamboo     }, /* CTL-660 */
[20:24] <toabctl> but there is no line for the cth-661
[20:25] <toabctl> i would like to add a line but i don't know what the 3 parameters stand for.
[20:28] <tjaalton> toabctl: so the cth-661 and ctl-660 share the same id
[20:28] <tjaalton> no need to change anything
[20:29] <tjaalton> linuxwacom has the needed kernel bits
[20:29] <tjaalton> too bad that the git repo doesn't
[20:30] <toabctl> tjaalton, linuxwacom==linuxwacom-0.8.4 ? and git==xf86-input-wacom? right?
[20:30] <jcristau> for the kernel, git == linux-2.6.git, i guess
[20:31] <toabctl> tjaalton, i don't know where to find the kernel module for wacom
[20:31] <tjaalton> wacom-kernel git actually
[20:34] <tjaalton> toabctl: get the linuxwacom tarball
[20:34] <tjaalton> 0.8.5-10
[20:35] <toabctl> tjaalton, and there's the code for the kernel module? (the code organisation looks very confusing for me)
[20:35] <tjaalton> yes (and it is)
[20:38] <toabctl> tjaalton, and where can i find the kernel driver in the ubuntu repository?
[20:39] <jcristau> comes with your kernel.  /lib/modules/*/kernel/drivers/input/tablet/wacom.ko
[20:41] <tjaalton> right
[20:41] <toabctl> jcristau, and how to find out from which source this module was build? from 0.8.4? or 0.8.5.10 ?
[20:41] <tjaalton> toabctl: what came with the kernel
[20:42] <tjaalton> linuxwacom used to ship the code as well
[20:42] <tjaalton> see what version it declares
[20:42] <tjaalton> in the linuxwacom kernel source
[20:42] <toabctl> tjaalton, so the module is shiped by the mainline kernel? it's not a ubuntu patch?
[20:42] <tjaalton> right
[20:42] <toabctl> ah. ok. 
[20:45] <tjaalton> the kernel code was split into wacom-kernel git, but seems like it's not being updated
[20:52] <toabctl> tjaalton, and how do i know which kernel version i need for linuxwacom-0.8.5-10? this version doesn't compile for me..
[20:53] <tjaalton> toabctl: you don't want or need to compile the whole of linuxwacom
[20:53] <tjaalton> diff the kernel code and patch the kernel sources, or just copy the files and then build the kernel
[21:25] <toabctl> tjaalton, thanks for the help. but i think it's to complex for me to fix it.
[21:25] <tjaalton> toabctl: :)
[21:26] <toabctl> tjaalton, do you think it's a big thing or will tha tablet be supported in some weeks? or no idea?
[21:27] <tjaalton> toabctl: I'm not sure it'll be supported in lucid at all, tbh
[21:27] <tjaalton> judging by what was said on #ubuntu-kernel earlier
[21:27] <toabctl> tjaalton, ok. thanks a lot for the help and information!
[21:31] <superm1> tseliot, is it intended that users are switched from nvidia->nouveau on karmic->lucid upgrade?
[21:32] <superm1> i just upgraded one of my installs two days ago and this happened to me
[21:32] <tseliot> superm1: I don't think so
[21:32] <superm1> would it be expected if I had nvidia-glx-195 installed (rather than -190) though?
[21:33] <superm1> er -190 rather than -185 that is
[21:34] <bjsnider> also, what happens to the nvidia-xxx-libvdpau package in such a situation?
[21:35] <superm1> i can file a bug with whatever logs came up for this to help diagnose
[21:35] <superm1> but i suspect it's the same thing that will happen to anyone using that ppa of yours bjsnider 
[21:35] <superm1> would the appropriate thing be 'ubuntu-bug update-manager' to grab all such logs?
[21:36] <bjsnider> superm1, you were using the 190 driver out of my ppa?
[21:36] <superm1> bjsnider, i'm not sure if it was your PPA or the ~mythbuntu PPA.  it's basically the same packaging either way though
[21:37] <tseliot> superm1: we have 195 in Lucid now and, unless your package was epoched it should have gone well
[21:37] <superm1> certainly wasn't
[21:38] <bjsnider> tseliot, why not add a conflicts: nvidia-xxx-libvdpau to nvidia-current?
[21:38] <superm1> but nvidia-glx-185 might not have been installed 
[21:38] <superm1> because of it being named differently in the ppa's
[21:38] <superm1> so the upgrade process might not have known what to do about it
[21:38] <tseliot> superm1: I guess my packages only replace nvidia-glx-185
[21:39] <superm1> well i'll file the bug when i get home and we can all look and see what's possible for a solution
[21:39] <superm1> i'm certain there's lots of users using these PPAs for newer drivers, so it would be best to try to cover as many of them as possible
[21:39] <superm1> even if the solution is pushing something new to those PPAs for people to upgrade to before the upgrade
[21:40] <bjsnider> i could do that
[21:40] <superm1> it was certainly a poor experience when i tried to go play a recording and the machine just hung there because it couldn't find a suitable vdpau backend anymore :)
[21:41] <bjsnider> superm1, you mean it went to nouveau without you realizing it at the time?
[21:41] <superm1> bjsnider, yup
[21:41] <superm1> i mean there wasn't any tell-tale signs since i didn't use 3d, and i still had 1080p being output
[21:42] <superm1> i only used the video playback acceleration of vdpau
[21:42] <bjsnider> nouveau must work pretty well on your hardware
[21:42] <bjsnider> you wouldn've had kms too
[21:43] <superm1> i didn't pay attention to the bootup - the tv was off, so i have no idea if KMS was working
[21:43] <superm1> i did notice the redraws were a little slow in the menus though
[21:44] <bjsnider> superm1, what is the difference between mythbuntu and mythtv?
[21:44] <superm1> bjsnider, mythbuntu is a preconfigured installation with lots of things to better integrate with the OS setup for you
[21:45] <superm1> and extra tools for configuration of other pieces that aren't part of mythtv either
[21:45] <superm1> you can certainly add any of them to an ubuntu install though
[21:45] <bjsnider> such as what extra things?
[21:45] <superm1> mythbuntu-control-center is the biggest
[21:45] <superm1> it's kinda a one-stop shop for configuration of anything HTPC related on the box
[21:45] <bjsnider> so it's supposed to integrate with ubuntu better than mythtv by itself would?
[21:46] <superm1> well all the stuff is in the ubuntu archive, so you can achieve the same results yourself by installing all the pieces if you want
[21:46] <superm1> the stuff on the PPA's is just daily builds of mythtv
[21:48] <bjsnider> i see
[21:48] <superm1> some of the goals of the ubuntu desktop clash with what you would normally use an HTPC for too, so this only gives you the components you're gonna need for HTPC usage
[21:48] <bjsnider> is it built for multiple distros?
[21:49] <superm1> No, it's ubuntu only
[21:49] <tseliot> superm1: what's the PPA?
[21:49] <superm1> our cdimages are produced on cdimages.ubuntu.com etc 
[21:49] <superm1> tseliot, the ~mythbuntu PPA?
[21:49] <tseliot> superm1: the one with the nvidia packages
[21:49] <bjsnider> superm1, i mean different ubuntu distros, like jaunty, intrepid etc.
[21:49] <superm1> tseliot, it was either this https://edge.launchpad.net/~mythbuntu/+archive/trunk-0.22 or the vdpau ppa
[21:49] <tseliot> BTW I made 195 available in my proprietary drivers PPA
[21:49] <superm1> bjsnider, oh yeah it's been since 7.10
[21:50] <bjsnider> cool
[21:50] <superm1> project is a few years old now
[21:50] <bjsnider> nvidia-current is the 195 at this point isn't it?
[21:50] <superm1> i'm pretty sure our nvidia-graphics-drivesr-190 on that PPA came from the vdpau PPA
[21:50] <tseliot> bjsnider: yep
[21:51] <superm1> it was just put here because mythtv had to be built against libvdpau for it to work
[21:51] <bjsnider> superm1, i just updated it last week or something. i hope you're staying current with it
[21:51] <tseliot> superm1: maybe it was some libvdpau that caused the problem? I'm too tired to tell ;)
[21:52] <superm1> tseliot, i haven't even reviewed the logs yet.  i was still sorting out other upgrade problems
[21:52] <bjsnider> against ibvdpau?
[21:52] <superm1> i'll get the bug filed tonight with all the pieces
[21:52] <bjsnider> my driver doesn't install it, i use the external package
[21:52] <superm1> bjsnider, no it hasn't been updated.  is it something important?
[21:53] <bjsnider> which 190 is it? is it .42?
[21:53] <superm1> 190.53
[21:53] <bjsnider> that driver does not come with libvdpau anymore
[21:54] <bjsnider> only the nvidia vdpau driver is packaged in that one
[21:54] <superm1> yeah, hence we have the external libvdpau on that PPA too
[21:54] <superm1> and that's what mythtv had to build against
[21:54] <bjsnider> oh, ok
[21:54] <superm1> particularly libvdpau-dev
[21:55] <bjsnider> wel, hte most recent update added execstack in karmic, updated prerm/postrm scripts, basically in line with the standard karmic package
[21:55] <superm1> okay so for the users, if they're up and working probably not critical stuff
[21:56] <bjsnider> no
[21:56] <bjsnider> but whatever, a lot of them probably use the vdpau ppa
[21:56] <tjaalton> bryceh: hey, shouldn't the apport hook links be named according to the source package?
[21:56] <bjsnider> we don't have any stats or numbers of any kind do we?
[21:58] <superm1> i dont think so, but that would be awfully nice
[21:58] <superm1> it would help  to know which PPAs to give priority to keeping more stable
[21:58] <bjsnider> i know ppa usage stats were proposed at one point
[21:58] <bjsnider> i'd like to know how many people are using old distros, because i think it's a lot
[21:58] <bryceh> tjaalton, for manual reporting, yes
[21:58] <bjsnider> i get emails from jaunty and even intrepid people all the time
[21:59] <bryceh> tjaalton, for crash detection it needs to be against the binary package
[21:59] <bryceh> tjaalton, did you spot an inconsistency?
[22:00] <tjaalton> bryceh: yeah, there's no xf86-input-evtouch, -wacom..
[22:00] <tjaalton> probably others too
[22:01] <bryceh> tjaalton, heh, I just happened to fix a whole bunch just yesterday
[22:02] <bryceh> tjaalton, unreleased but check the xorg git tree
[22:02] <tjaalton> you removed xf86-input-evtouch and wacom-tools?
[22:02] <bryceh> tjaalton, a second set of eyes to doublecheck that everything's correct would help
[22:02] <tjaalton> er, evtouch was renamed
[22:03] <bryceh> well, replaced it with source_xserver-xorg-input-wacom.py
[22:03] <tjaalton> but the source package is xf86-input-wacom :)
[22:03] <tjaalton> so maybe they both need to be there, for crashers and manual stuff
[22:04] <tjaalton> wacom-tools is good to go, since lucid doesn't have it anymore
[22:04] <bryceh> $ apt-cache search wacom  
[22:04] <bryceh> xserver-xorg-input-wacom - X.Org X server -- Wacom input driver
[22:04] <bryceh> weird.
[22:05] <bryceh> anyway yeah feel free to add whatever to the x11-common.links file
[22:05] <tjaalton> that's the binary package
[22:05] <bryceh> I don't look at updating it as often as I probably should
[22:05] <tjaalton> apt-cache show xserver-xorg-input-wacom |grep Source
[22:06] <tjaalton> yeah I'll add those
[22:21] <BUGabundo> boas noutes
[22:27] <tjaalton> toabctl: usb.ids is missing a bunch of wacoms, like all the intuos4's
[22:28] <tjaalton> but it has nothing to do with the funcionality of the driver
[22:28] <tjaalton> +t
[22:28] <toabctl> tjaalton, but it's a first step, isn't it?
[22:28] <tjaalton> toabctl: no, it's a "good to have for a nicer lsusb output", but that's it
[22:29] <tjaalton> my intuos4 works just fine without that
[22:29] <toabctl> tjaalton, ah.ok
[22:29] <toabctl> tjaalton, your intuos4 works with lucid?
[22:29] <tjaalton> yes
[22:29] <toabctl> then i know what to buy next :)
[22:31] <toabctl> tjaalton, the newest kernel driver for wacom is available in the wacom-kernel git in drivers/input/tablet, right?
[22:31] <tjaalton> toabctl: no, it's not updated yet. it's in the latest linuxwacom tarball
[22:32] <toabctl> tjaalton, in which directory? the names ended with 2.6.27
[22:32] <tjaalton> there
[22:33] <tjaalton> diff it against the ones in 2.6.33 and you see what has changed
[22:34] <tjaalton> hmm, there's thel linuxwacom cvs too
[22:34] <tjaalton> -l
[22:34] <toabctl> lol
[22:35] <tjaalton> http://linuxwacom.cvs.sourceforge.net/viewvc/linuxwacom/linuxwacom-dev/
[22:38] <tjaalton> the commits are really messy.. "Updated new Bamboo support and fix a tablet rotation issue
[22:38] <tjaalton> "
[22:38] <toabctl> tjaalton, i installe the latest xorg driver now (xf86-input-wacom-0.10.4) and the kernel module from linuxwacom-0.8.5-10 and when i insert the tablet now, i got in /var/log/message:
[22:38] <toabctl> Feb 25 23:37:19 zitrone kernel: [ 8308.664191] usb 3-1: USB disconnect, address 3
[22:38] <toabctl> Feb 25 23:37:25 zitrone kernel: [ 8315.380103] usb 3-1: new full speed USB device using uhci_hcd and address 4
[22:38] <toabctl> Feb 25 23:37:25 zitrone kernel: [ 8315.546334] usb 3-1: configuration #1 chosen from 1 choice
[22:38] <toabctl> Feb 25 23:37:26 zitrone kernel: [ 8315.553354] input: Wacom BambooFun 2FG 6x8 Pen2 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.0/input/input18
[22:38] <toabctl> Feb 25 23:37:26 zitrone kernel: [ 8315.568645] input: Wacom BambooFun 2FG 6x83 as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1:1.1/input/input19
[22:38] <tjaalton> that also includes support for intuos4 OLEDS
[22:39] <tjaalton> ok, that's better
[22:39] <toabctl> and something happen when i move my finger over the tablet and when i press anywhere. but it's not usable..
[22:39] <tjaalton> what does udevadm info --export-db show now?
[22:39] <tjaalton> or the Xorg.0.log?
[22:40] <tjaalton> does the pen work?
[22:40] <bryceh> tjaalton, btw do you know why it is that debian renames xf86 -> xserver-xorg ?
[22:41] <tjaalton> bryceh: no..
[22:41] <tjaalton> takes longer to type?-)
[22:41] <bryceh> seems to me that for consistency sake, -evtouch and -wacom ought to be renamed to match
[22:41] <toabctl> the pen works more or less (maybe it's me who don't know how to use)
[22:41] <tjaalton> yes, but they are not maintained by xsf
[22:41] <bryceh> otherwise I wonder why not just go with xf86- and become consistent with upstream
[22:42] <bryceh> tjaalton, are they ubuntu-only packages?
[22:42] <tjaalton> they are going to be merged to the server anyway, so
[22:42] <tjaalton> bryceh: no, -evtouch is maintained by malattia, -wacom by ron
[22:42] <tjaalton> toabctl: ok, that's great then
[22:43] <toabctl> tjaalton, here's the output of udevadm info
[22:43] <tjaalton> toabctl: do you have the module somewhere? if it's i386 and built for the -14-generic kernel I might try it on mine
[22:43] <toabctl> http://paste.ubuntu.com/384000/
[22:44] <toabctl> tjaalton, yes arch=i386 and the newest kernel from repository
[22:44] <toabctl> and i updated the package of xf86-input-wacom with uupdate
[22:45] <toabctl> i'll write it down in the bug report how to fix it.
[22:45] <tjaalton> toabctl: hmm it loads synaptics and evdev too
[22:45] <toabctl> do you want to have the kernel module?
[22:45] <tjaalton> so maybe the udev rules need an update
[22:45] <tjaalton> yes please
[22:45] <tjaalton> one more test before I pass out :)
[22:49] <tjaalton> toabctl: well?
[22:49] <toabctl> tjaalton, https://code.launchpad.net/~toabctl/+junk/bamboo
[22:49] <toabctl> tjaalton, can i finetune the response of the tablet anyway?
[22:49] <tjaalton> toabctl: it loads the wrong driver for it
[22:50] <tjaalton> the touch function that is. I see synaptics being loaded
[22:50] <tjaalton> could be that wacom doesn't support that yet
[22:50] <toabctl> tjaalton, ah. so new udev rules should fix this?
[22:50] <tjaalton> I don't know, check the wacom lists
[22:51] <toabctl> tjaalton, the pen only work if i don't touch the tablet. i have to "fly" over the tablet with the pen
[22:51] <tjaalton> that's probably evdev then
[22:51] <tjaalton> yes you could try to fix the udev rules
[22:53] <toabctl> tjaalton, should i report a bug against the actual kernel? is it possible that the new driver from linuxwacom will be merged into the ubuntu lucid kernel?
[22:53] <tjaalton> I get an error "invalid module format"
[22:53] <toabctl> tjaalton, i build with generic-pae kernel
[22:53] <tjaalton> toabctl: I added the linux task already
[22:53] <tjaalton> ok, I don't have pae here
[22:53] <tjaalton> anyway, that's ok
[22:54] <toabctl> tjaalton, i filled already a bugreport to debian that they should update xf86-input-wacom to 0.10.4
[22:54] <tjaalton> and I'm not sure if this will be added to lucid
[22:54] <tjaalton> heh, good luck
[22:54] <toabctl> tjaalton, why? because ron don't answer?
[22:55] <tjaalton> toabctl: if he thought 0.10.4 was worth it, it would've been packaged already I think
[22:55] <tjaalton> but he's right most of the time too
[22:56] <toabctl> ok
[22:56] <tjaalton> the current one is patched, since vanilla 0.10.3 didn't work properly
[22:59] <toabctl> tjaalton, to get the pen working correct, what i have to do?
[22:59] <tjaalton> not load evdev for it
[22:59] <toabctl> tjaalton, and how to do that?
[22:59] <tjaalton> ie. make it match in the wacom udev rules
[22:59] <toabctl> with udev?
[22:59] <toabctl> ok
[23:00] <tjaalton> so it doesn't fall through the cracks so that the evdev rules catch it
[23:00] <tjaalton> anyway, been up 20h already and can't sit straight anymore. night!
[23:01] <toabctl> tjaalton, bye and thanks a lot!!!
[23:01] <toabctl> tjaalton, you are my hero!:-)
[23:05] <Sarvatt> bryceh: I was talking about the mesa dri drivers, sorry