[02:53] https://edge.launchpad.net/~xorg-edgers/+archive/radeon-kms on top of Jaunty :) [02:53] https://edge.launchpad.net/~xorg-edgers/+archive/radeon-kms [02:53] http://pastebin.ca/1449325 [02:54] tormod: :-) [02:54] heh wobbly glxgears \o/ [02:55] How's the performance and stability of ati-kms? [02:56] not extraordinary [02:57] btw, I added a new PPA to ubuntu-x-swat, 'x-retro' [02:57] it is the inverse of 'x-updates'. Instead of providing packages newer than what's in the distro, it provides packages that are older. [02:57] like intel 2.4 for jaunty ? :) [02:57] precisely [02:58] if you ever run into cases where we need to carry reverted versions of -ati, that'll be where to put them [02:58] I was thinking of that once "xorg-aunties" [02:58] tormod: does xv work in kms? [02:58] firefox scrolling is slow [02:58] hang on [03:00] totem seems to struggle with aspect ratio, can this be related to kms? [03:01] how do I tell if it's really using xv [03:04] tormod, gstreamer-properties should allow you to force it to a particular approach [03:04] done that [03:05] so unless there is any fallback it runs xv [03:06] does not look great but it works [03:07] the film wobbles with the window in compiz [03:08] tormod: are sure it's xv or is it x11 fallback. Use mplayer from commandline, it'll tell what output it's using [03:08] use mplayer -vo xv filename [03:08] if you try radeon-kms ppa, you might need to add Driver "ati" to xorg.conf (at least in Jaunty) [03:09] and I would recommend to boot with "text" and use startx [03:10] If xv works properly, than I can deal with a few performance issues, but poor video playback is a deal breaker. Otherwise, I'd be glad to help test and debug issues [03:11] well try it out, you can always revert the packages [03:11] bryce, maybe you want to spin a live-cd with this ppa? [03:12] good night [03:13] tormod: yes, but will need to be next week [03:13] night tormod [03:13] I had wanted to do some ati/nouveau testing today but ended up mostly spending it on that #$%^% Jaunty X freeze bug... [07:16] heh, running two independent xorg's with their own physical cards, the mouse moves the cursor on both screens :) [16:42] The latest -video-ati makes mention of requiring firmware... what's the status of that? [17:32] What exactly is low graphics mode? Is it -video-vesa ? [19:08] maxb, can ya pastebin your /var/log/Xorg.0.log if you're still around? [19:20] phew, found a fix for the --enable-config-debus compile error for 1.7 post xi2 merge, but part of me wants to keep it disabled to figure out whats actually not working because I havent been able to for the past few days :) [19:20] even wacom's working right http://sarvatt.com/downloads/Xorg.0.log.txt [19:21] debus? [19:21] O_o [19:21] on a side note... [19:21] my X session is only 2 hours old. [19:21] apw, bryce: around? I have a kms iso to be mirrored [19:21] and gem_objects has overflowed already! [19:22] =( [19:22] i guess its time i should upgrade my wacom tablet to karmic [19:22] wow, your wacom tablet runs ubuntu? O_o [19:23] yes? [19:23] does it even have storage? [19:23] O_o [19:23] its a tabletPC [19:23] ah. [19:23] heheh [19:23] thank you very much, capt'n snark [19:23] * hyperair chuckles [19:23] =p [19:25] https://wiki.ubuntu.com/LaptopTestingTeam/ToshibaTecraM7 [19:27] fascinating [19:27] hmm i wonder if xD cards and sony memory sticks will get open source drivers anytime soon =\ [19:28] do you have any? [19:28] i've got an xD [19:28] everyone uses SD anyways [19:28] and a m2 memory stick, yes. [19:28] yeah true. [19:28] but sony ericsson phones use m2 [19:28] you're weird :P [19:28] memory sticks work fine, ubuntu just doesnt enable the modules [19:28] and olympus cameras use xD cards [19:28] Sarvatt: do they? [19:28] Sarvatt: which modules? [19:28] yeah I have one in right now [19:28] probably depends on the chipset [19:28] Sarvatt: and why aren't they enabled? [19:29] Ricoh. [19:29] theres a whole memory stick section in the kernel config [19:29] yeah ricoh and jmb work fine for me [19:29] hmm [19:29] Sarvatt: what are the config opts? [19:30] Sarvatt: and how come ubuntu doesn't enable them? [19:30] CONFIG_MEMSTICK=m [19:30] CONFIG_MEMSTICK_UNSAFE_RESUME=y [19:30] CONFIG_MSPRO_BLOCK=m [19:30] CONFIG_MEMSTICK_TIFM_MS=m [19:30] CONFIG_MEMSTICK_JMICRON_38X=m [19:31] i wonder if there's a choice between them and suspend / resume working [19:31] heck if i know [19:31] or if there's some patent to consider [19:31] suspend/resume works fine for me, i even enable unsafe resume on both sd and MS [19:31] probab [19:31] probably, unsafe resume is about the media write integrity, not the suspend [19:31] it was pretty new and not stable on 2.6.28 though [19:32] i see [19:33] i gave my SD cards to my dad [19:33] 512M each. [19:33] heh [19:33] i've got 2G usb sticks [19:33] tiny things [19:33] i have a 2gb microsd [19:33] and i think SDHC goes up to 32GB now? [19:33] heh [19:33] yeah i think so [19:33] need to have unsafe resume to be able to suspend/resume/hibernate with important things mounted on it, i've got /opt on a SD with some gnome applets in there [19:34] i see [19:34] i just use my hard disk =D [19:34] 160G. i wish it was bigger. [19:34] i guess thats one way to test out unstable builds [19:34] doesn't work? just pop the sd card out [19:35] yeah if only my aspire one supported booting from SD i'd be happy [19:35] im pretty sure my tablet does [19:37] hmm i've never tried O_o [19:38] how expensive are SD cards anyway? the last tiem i bought SD cards, they were pretty expensive [19:38] i paid 35 bucks for 2 16gb ones, real cheap now [19:39] that was 6 months ago too, sure its cheaper [19:40] * hyperair pokes Sarvatt to put back the two memleak patches =( [19:40] ya upgrade and it got worse? [19:40] 35 bucks for 2 16G eh.. [19:41] yes [19:41] very much worse [19:41] 2h and it's already showing negative memory usage [19:41] -1693499392 object bytes [19:41] i'll do it by monday if its not upstream, they dont really commit anything on weekends but it might go up monday [19:41] hmm cool [19:44] it would be nice if the patch could be fixed to not conflict with the commit i highlighted the other day [19:44] if you want a kernel to try to see if memory sticks work for you -- http://sarvatt.com/downloads/2.6.30-rc8/ [19:45] ripps and whoever wondered about radeon-kms and xv: it's fixed now [19:46] cool, thanks =) [19:47] a live cd is available from https://launchpad.net/~xorg-edgers/+archive/radeon-kms [19:48] but you will need to apt-get upgrade to get xv fixed in -ati/-radeon [19:49] we really need to start a Ubuntu kernel enthusiast support team [19:50] er what for? [19:50] i donno. maybe it's just me [19:50] just for newbies who might have questions or want to share custom configs/builds [19:51] tormod, which kernel are you using? the one with only ATI? [19:51] because apw made another with nouveau too [19:51] I used to build my own kernel on debian, but stopped when i switched to ubuntu. the official builds have only gotten more complicated [19:52] more complicated? they cut down on ubuntu specific stuff so much lately [19:53] perhaps its improved since i last looked [19:53] i used to compile my own kernel =\ [19:53] using make-kpkg [19:53] wasn't too hard [19:53] but very time consuming [19:53] yeah its just recently that its gotten really cut back on ubuntu specific stuff [19:54] -restricted-modules is a challenge to figure out [19:54] but its been quite a while since i last tried, and a while longer before i'll try again, so i'll pipe down [19:54] gotta get stunnel working on osx [19:55] dont even need that anymore in karmic [19:56] Sarvatt: the kernel from the radeon-kms ppa, so I guess no nouveau [19:56] linux-restricted-modules-common is only 90k, think it just has intel wireless firmware now? [19:56] now all we need is to get iwl firmware open. =D [19:57] dont even see a lrm branch on kernel.ubuntu.com for karmic anymore [19:57] ah right; that's my wifi chipset [19:58] but im pretty sure there's still an nvidia binary package [20:00] pwnguin: I guess you don't need a "team" to discuss kernel configs - there are forums for it [20:00] yeah, thats independant of the kernel though, uses dkms to build the modules every time you install a new kernel. wish i had a netbook with nvidia graphics because i love the binary drivers :D [20:01] for instance the "kernel master thread" on ubuntuforums [20:01] i need to figure out how to combine all the split configs so i can reconfigure things and split it up again some day so I can just build them on a PPA [20:03] nobody loves binary drivers in sovyet russia [20:06] so is kms working out for you tormod? [20:06] i might sit down and work out packaging gallium for nvidia this week so I can do some nouveau testing [20:08] expect from suspend/resume, I actually can not make it crash ! [20:08] nice! [20:08] 3d acceleration/dri working and everything? [20:09] so it's better than stock intrepid, jaunty, karmic [20:09] lol [20:09] dri2 you mean :) [20:09] its unstable for you on radeon-rewrite without the KMS kernel still isnt it? [20:10] radeon-rewrite on the old stack is still broken [20:10] ah [20:10] maybe it's an DRI (1) issue [20:10] did you get libdrm-radeon all packaged up? [20:11] yes good enough that it works [20:12] hmm you should try the xorg-testing stuff out, mesa and drivers should be older in there so wont upgrade those [20:13] oh the drm is newer [20:13] but I wonder why mesa fails on amd64. libdrm builds some objects first with -fPIC then without (for libdrm-radeon.a) and then mesa complains about missing fPIC like it is picking up the wrong library(?) [20:15] I can try xorg-testing again from a live-cd but it is not so long since last time [20:15] libdrm_radeon.a: could not read symbols: Bad valu [20:15] huge changes since last time though with the XI2 stuff [20:16] aha could be fun to try [20:16] tormod: sounds like libdrm_radeon.so is not there. missing dep somewhere? [20:16] jcristau: I am pretty sure I did not do the libdrm_radeon.so packaging properly, but it works in i386/lpia [20:17] mesa failing build log: http://launchpadlibrarian.net/27564711/buildlog_ubuntu-karmic-amd64.mesa_7.6.0~git20090606%2Bradeon-rewrite.c1ccc7d5-0ubuntu0tormod2_FAILEDTOBUILD.txt.gz [20:18] libdrm build log: https://edge.launchpad.net/~xorg-edgers/+archive/radeon-kms/+build/1060730/+files/buildlog_ubuntu-karmic-amd64.drm-snapshot_2.4.11+git20090604+libdrm-radeon.2cb4c64d-0ubuntu0tormod2_FULLYBUILT.txt.gz [20:19] lookin over the source now to see if i see anything [20:19] do you need a libdrm_radeon.pc.in set up tormod? [20:19] your libdrm-dev doesn't depend on -radeon1 [20:19] tormod: ^ [20:20] jcristau: aha [20:20] patch didnt add that [20:21] gotcha [20:21] oh and it worked on i386 because non-PIC in shared libs works there [20:21] it fails most everywhere else though [20:22] btw why are those libdrm_radeon libdrm_intel split out and not just shipped in libdrm2? [20:23] it is all in one in the modesetting-gem mesa/drm tree, looking at my source for the 2.4.4 from there i built the other day [20:24] tormod: so their sonames can change independently [20:25] right [20:26] but if they're from the same source, why would they have different sonames? [20:27] 'same source'? [20:27] you can remove a function from libdrm-intel without it affecting libdrm-radeon [20:27] or libdrm itself [20:28] ihmm tormod incase it helps any - http://cvs.fedoraproject.org/viewvc/rpms/libdrm/F-11/libdrm-radeon.patch?view=log [20:28] Sarvatt: thanks that looks awfully handy [20:34] maybe we should set up a bzr branch or git repo somewhere for the two libdrm branches to make things easier updating it with the scripts, need so many changes building current libdrm against origin/ubuntu just for the current 2.4.11. rules needed changing a bit and theres a bunch of new symbols to add [21:27] jcristau: mesa built on amd64 now, thanks! [21:32] tormod: np. have fun :) [22:10] Sarvatt: My problem turned out to be that I had "radeon" installed but not "ati", and the latest packages break the pciids detection in that situation. I've filed a bug [23:10] tormod: funny how that looks like the exact same problem we had building amd64 mesa 7.5+ with egl from the logs [23:12] true [23:12] same package that it was failing on i mean at least