[00:00] http://git.gnome.org/browse/gnome-settings-daemon/log/?h=randr-rotate-wacom-tablet [00:02] thats the rotate stuff you're looking for I assume, automatically rotates the tablet with the display rotation settings [00:02] that is definitely a help [00:03] the other part is actually hooking the ACPI events for the lid rotation [00:03] so that it does something in the first place... [00:03] also, that code is a little scary [00:03] yeah thats a kernel problem, I think hp touchpads are the only ones that do that now [00:03] err hp touchbooks? whatever they are called [00:03] but mainly because snippets of your xorg configuration become part of the command line.... [00:04] you can do it on lenovo thinkpad x200t [00:04] which is what I have [00:04] but you need to add the ACPI event and handler scripts yourself.... [00:04] oh [00:04] you're kidding.... [00:04] looks like it's stopped working in Lucid [00:04] why's that... [00:05] needs udevification? [00:07] hmm [00:07] probably.... [00:07] can someone help me with xorg.conf in Ubuntu 10.04 [00:08] VladimirBG: if you're using KMS that option has no effect, you need to use a kernel module option instead (which should already be defaulted on if your card supports it) [00:08] if that question was in reference to dynclks that you asked about earlier [00:09] interesting, not firing the ACPI events :( [00:09] VladimirBG: echo "options radeon dynclks=1" | sudo tee /etc/modprobe.d/radeon.conf [00:10] Sarvatt, how do I implement that command, just copy/paste in terminal, or? [00:11] Alan: acpi_listen doesn't show it? [00:11] VladimirBG: yeah just copy/paste that into a terminal [00:11] VladimirBG: first though, check if its already enabled [00:11] I apologize for my ignorance, I'm a long time windows user... [00:12] cat /sys/module/radeon/parameters/dynclks [00:12] I pasted it, and got "-1" [00:13] Sarvatt: the events happen, acpid doesn't appear to be firing them... [00:13] also, i just tried to run acpid in the foreground to see what's happening, and Xorg crashed when i put the lid down... [00:13] weird stuff.. [00:14] WOW [00:14] nice [00:15] ay 3 23:55:43 scribus kernel: [ 200.579077] Xorg[1273]: segfault at 18 ip 00007f8bf27a17ce sp 00007fffc6581940 error 4 in wacom_drv.so[7f8bf2799000+12000] [00:17] In an unrelated note, Virtualbox needs to catch up and support a non-HAL'd Ubuntu :( [00:17] Alan: try wacomrotate from this PPA, this guy has the same tablet and set it all up as a deb - https://edge.launchpad.net/~thjaeger/+archive/tabletpc [00:17] Sarvatt, when I used the cat command, I got -1, does it mean it is already enabled? Also, http://manpages.ubuntu.com/manpages/lucid/en/man4/radeon.4.html shows an option called "ForceLowPowerMode", will that work? [00:18] VladimirBG: no the powermanagement options in xorg.conf don't work with KMS, if you really want to use them then just echo "options radeon modeset=0" | sudo tee /etc/modprobe.d/radeon.conf [00:19] ok [00:19] thanks [00:19] if you do that one then they'll all work and ya can go to town with all the stuff in the wiki [00:20] only thing you'll really notice is the boot will be uglier and your terminals ugly again, but things will be faster :D [00:20] it that command permanent? [00:20] meaning I don't need to use it after? [00:20] yeah, to remove it just sudo rm /etc/modprobe.d/radeon.conf [00:21] Sarvatt: will try that, thanks - such a thing didn't exist when i bought this laptop! [00:21] Sarvatt, done. so, after I reboot, I'll have power management enabled on my gpu and have longer battery life? [00:22] depends on if your GPU supports it :) you still have to add the xorg.conf options too [00:22] power management sucks on hd2000+ at the moment but they are working on it heavily upstream [00:24] so I need to make xorg.conf, add some generic stuff like this: http://pastebin.com/cJ2ynTRi and add Option "ForceLowPowerMode" "enable" ? [00:25] yup, add it to the device section underneath driver "radeon" and before EndSection [00:26] try adding Option "ClockGating" "1" Option "DynamicPM" "1" Option "ForceLowPowerMode" "1" [00:26] (all on seperate lines) [00:27] can you give me a pastebin of that? [00:27] please? [00:27] Sarvatt: that wacomrotate is doing exactly nothing [00:27] :( [00:27] http://pastebin.com/w3Tzg1ts [00:28] Alan: you rebooted? [00:28] thanks! [00:28] Sarvatt: yup [00:28] maybe he hasn't updated it for the latest stuff yet :( [00:28] by the way, what is KMS? [00:30] it puts the kernel in charge of low level things like managing the memory on the GPU and setting the resolution [00:30] (and power management in this case) [00:30] sad as it is i'd really recommend just using the crappy fglrx if you can and you're worried about power management [00:31] so, I need to also turn that off? [00:31] VladimirBG: thats what "options radeon modeset=0" | sudo tee /etc/modprobe.d/radeon.conf did [00:32] it's enabled by default for the pretty boot stuff [00:32] not that it makes much of a difference getting loaded so late in the boot process as it is now :) [00:34] I love Ubuntu... but getting little thing to work puts a lot of people off... But I guess that is the price of free... [00:35] VladimirBG: just curious, why don't you use the proprietary drivers on your system? [00:36] ah... used to be too much hasle a few years back [00:36] and video playback was bad [00:36] aside from power management, radeon is really nice [00:37] yeah its still crappy but its pretty much required if you care about battery life on a recent GPU, that will definitely change by 10.10 though [00:37] Sarvatt: hmm, methinks there's a bug here... :( [00:38] so, the lesson is next laptop has either nvidia or intel? [00:38] May 4 00:37:09 scribus kernel: [ 823.134541] Xorg[1241] general protection ip:7f3e7c4947ce sp:7fff89fe3540 error:0 in wacom_drv.so[7f3e7c48c000+12000] [00:38] more segfaults :( [00:39] VladimirBG, the linux graphics situation across the board is a disaster. you can't go right no matter what hardware you buy [00:40] what is the least bad solution? [00:40] There we go, "xsetwacom set stylus rotate cw" is enough to segfault Xorg :( [00:40] VladimirBG, it involves firearms [00:45] bjsnider, any light at the end of tunnel? Any hope for a good driver set? [00:46] for any manufacturer? [00:46] VladimirBG: you'll probably find something annoying no matter which you pick, ATI is good but power management with KMS is a sore spot with it at the moment, it getting a lot of work done on it and should be better with 2.6.35. nvidia has great binary drivers but you're stuck with problems like being unable to suspend/resume for months until they fix them. intel gpu's just suck in general :) [00:46] VladimirBG: *Modern* intel chips tend to be well supported, but they're pretty sucky chips. [00:47] well, we all thought gallium3d would solve most problems, but now the developers don't want it because there'd be too much pain and it's only a vmware thing. so mesa's crappiness remains [00:47] * RAOF concurs with Sarvatt: the open ATI drivers are most likely to get better fastest. [00:47] hey guys.. anyone having issues installing nvidia drivers from nvidia on lucid and also setting fast writes and sba on agp cards? [00:48] you cannot use the nvidia-installer on lucid [00:48] going to live dangerously and try xorg-edgers.... [00:49] bjsnider, i noticed :) [00:49] bjsnider, why is that/ [00:50] If I install fglrx from repo, it will disable radeon, and power management will work? [00:50] i'm tired of explaining why [00:50] cozzimoto, use jockey and do whatever it wants you to [00:50] bjsnider, wow i am tired of doing support myself with things [00:50] VladimirBG: Yup. Use System→Preferences→Hardware Drivers for the most-tested route. [00:50] bjsnider, well apparenlty i have no choice unfortunately [00:51] RAOF, I tried that, but fglrx isn't offered there, but I did find it in ubuntu software center [00:51] bjsnider, may add the reason in the topic :0 [00:51] cozzimoto, i'm for that [00:52] VladimirBG: Hm. If fglrx isn't offered there it's entirely possible that fglrx no longer supports your card. What *is* your card? [00:52] i meant to say "maybe add it" [00:52] that's certainly why. it scans for the pciid [00:52] it doesn't match a supported card [00:53] what about enabling fast writes and SBA on agp nvidia cards...nothing seems to work on lucid [00:53] RAOF, mobility radeon x1300 [00:54] yep, not supported [00:54] cozzimoto, how did you do that before lucid? [00:55] bjsnider, never on lucid just on pevious ubuntu versions on lucid it doesn work [00:55] i said before lucid [00:55] previous distros [00:56] bjsnider, i would edit /etc/modprobe.d/nvidia-kernel-nkc [00:57] alias char-major-195* nvidia [00:57] options nvidia NVreg_EnableAGPSBA=1 NVreg_EnableAGPFW=1 [00:57] reboot and magic happened :) [00:58] You'll probably need to s/nvidia/nvidia-current/g; the kernel module got renamed to allow parallel-installability. [00:59] if he even has it installed. it sounds like it isn't [00:59] RAOF, I tried that once no luck [00:59] bjsnider, the nvidia_current is installed I had no choice [01:00] what? [01:00] although on the one system i reinstalled karmic so I didnt have to deal with this :) [01:00] what do you mean you had no choice? [01:01] bjsnider, I cannot installe the current nvidia driver from nvidia,,which is what i started with [01:01] yes, because it will overwrite system files. that's always beent he problem with it [01:01] bjsnider, no I have never had issues with the official nvidia driver [01:02] only on lucid [01:02] but it has always overwritten and destroyed mesa files, you just didn't notice [01:03] bjsnider, mm that may have affected compiz at some point no? [01:04] no, it replaces mesa's libglx files with its own [01:04] sorry [01:04] i don't know why, since mesa works so smashingly well, and always has [01:05] bjsnider, well still I always preferred the official driver but with lucid "i have no choice" [01:05] oh, you can override the block if you really want to. i'm sure google has the instructions somewhere [01:05] ok I will try to figure out the fast writes and SBA at some point [01:06] RAOF, the intel chips may suck, but their windows driver destroys the linux driver in opengl performance in the recent phoronix tests [01:07] although he did note amusingly that they locked up the windows kernel on numerous occasions [01:07] bjsnider: Heh. [01:07] That's entirely possible; our graphics stack still hasn't had a bunch of optimisation work done. [01:09] Sarvatt: Thinking of which… are you building r300g in xorg-edgers alongside nouveau? My ati box isn't here yet, but I'm interested to see how it's going; as far as I've gathered it seems to be roughly equivalent to the classic driver ATM. [01:12] RAOF: yeah libgl1-mesa-dri-gallium [01:13] I suspect that we might want to be shipping that in Maverick. We probably want to have nouveau gallium in there, at least. [01:14] Discussions can be had in a week or so! :) [01:14] Sarvatt: OK, I get basically the same results with both 32 and 64 bit images, with and without modesetting: the panel does not appear to be on once X has started. [01:14] the intel drivers in windows are such an abomination compared to the linux ones, the 945g ones were lucky to get yearly updates the past few years and i had to do allll kinds of faking support for features to get games to work (which is probably where some of the performance losses are from since at least you get software fallbacks for those features in linux) [01:15] i had the 965gm drivers hacked up to work on 945 so anything recent that needed vertex shader support could work [01:16] Sarvatt: the system does seem to mostly boot up; sometimes I get the cheery ubuntu audio sound to make me think so. [01:25] I cant find any bugs with the same symptoms :( do you see the splash screen during the boot? [01:26] did you put the livecd's on a USB stick with persistant storage space so you can see the logs by any chance? [01:33] Sarvatt: I've not tried usb sticks. I can try to dig one up. [01:34] I get the little keyboardish icon on the bottom of the screen, and press a space bar so I can interact with the menu. [01:34] If KMS is off, I get the textish version of Ubuntu with dots that animate as it spins the CD a long time. [01:35] If KMS is on, I don't get that; the screen goes pretty close to black, while the CD spins a long time. [01:38] Sarvatt: I'll try to grab a usb stick tomorrow. do I have to do anything magic to get persistent storage? [01:46] choose it in usb-creator [04:59] good morning [05:46] hio [05:46] anyone messed with lucid & gma500 recently? [05:52] furan: Yes indeed. Both Sarvatt and Bernardo have been looking at it. [05:53] I saw a blip on an updated ppa(https://launchpad.net/~lucazade/+archive/ppa) but it's still building 32 bit [05:53] I was curious if I could just download and build myself [06:02] Is there anyone here crazy enough to be using Xinerama? If so, how's your lucid experience? I'm noticing a number of bugs with Xinerama being the tying theme. [06:08] hi all [06:09] hi [06:09] trying to get gma500 up on lucid, not sure where to start [06:09] lol [06:09] Lucazade set up a repository with me [06:09] all we need now is to fix dri [06:10] the googlecode one? [06:10] yes [06:10] ok [06:10] I've ported all Mandriva patches, including the renaming of drm to psb-drm to that repository [06:11] cool [06:11] what's left to do on dri? [06:11] Sarvatt here suggested the problem might be with udev, but even after renaming lbm-drm to psb-drm in the udev scripts it doens't work [06:11] I am getting very slow video playback with KMS enabled on Radeon 7000. Should I file a separate bug for this or reopen bug #544496? [06:11] Launchpad bug 544496 in xserver-xorg-video-ati "[RS100] desktop became slow after upgrading to Lucid" [Critical,Fix released] https://launchpad.net/bugs/544496 [06:12] I don't know... The problem is that the modules get loaded (psb and psb-drm), with debug enabled there is no error, but still /dev/dri never gets created, and the xorg psb driver fails because of that [06:15] I've already put my xorg log on the ubuntuforum thread, and my dmesg in dropbox, if you want to take a look [06:27] furan: the repository in googlecode is http://code.google.com/p/gma500/ [08:16] What cab the reason that for a particular resolution part of the UI goes off-screen? [08:17] Because you're connecting your display over a VGA cable, which sucks? [08:17] Or because you have a thrice-damned LCD TV that refuses to believe that digital inputs shouldn't be overscanned? [08:18] RAOF: Looks like either or both are possible. With KMS this resolution does not work at all. Without KMS some UI goes off screen. [08:19] Are you actually using a VGA cable? [08:19] yes. and connected to an year old LCD TV (32"). [08:20] Mmm, double the fun! [08:21] So, if the top and bottom go offscreen then the answer will be “televisions do that deliberately”, and if it's shifted left/right the answer should be “fiddle with the display settings until the TV has scaled the image correctly”. [08:21] Mostly. [08:22] the display is shifted left. But that happens only for 1360x768 resolution. So I am inclines to think that the frequencies used by TV are not getting detected properly. [08:24] Actually making what comes out of a VGA cable centred on a display is somewhat of a hack. Which is why displays which accept VGA input generally let you shift the output until it matches what it needs to be. [08:24] hmm [08:25] by the way, should reopen bug 544496 if the symptoms are still present? Or should I file a new bug. [08:25] Launchpad bug 544496 in xserver-xorg-video-ati "[RS100] desktop became slow after upgrading to Lucid" [Critical,Fix released] https://launchpad.net/bugs/544496 [08:25] Other answers include “you can fiddle with the ModeLine (xrandr --newmode is your friend) until it's shifted nicely” which is basically doing what fiddling with the TV's alignemnt thingy would do, but without useful guidance. [08:26] I will try that [08:29] I'd only try that if the TV really doesn't have any way to adjust the picture; fiddling with the modeline will be annoying and slow. [08:30] I guess another option would be to buy a DVI or HDMI cable (and potentially a new laptop to plug those in :)) [08:33] slytherin: I'd be happy for you to reopen that bug; the upstream bug is still open, and Bryce wasn't sure that commit would help. [08:35] vline seems to be pretty much the same as vsync, which is a serious performance impediment if your card isn't powerful enough to draw at or above the screen's refresh rate. [08:36] RAOF: After setting resolution on PC and using 'Auto Adjust' on TV it looks almost perfect. And looks like I will need to buy a new graphics card soon. [08:36] slytherin: Turning off kms doesn't resolve the performance problem? [08:36] It does. [08:37] That's why I added comment in bug first. [08:37] Right. My understanding is that vline is only enabled with kms, which makes your performance problems make sense. [08:37] Possibly the other reporter's card got a kms blacklist ;) [08:38] There is hope from the upstream bug; there's a suggestion that things will improve once DRI2 swapbuffers have been implemented. [08:38] also with KMS enabled EXA is being used which is known not to work with cards with low memory. With KMS disabled, XAA is used. [08:40] I am also wondering if I should first try "RenderAccel off" with KMS, if that is going to make any difference. [08:41] * RAOF is off to dinner [09:42] hi [10:02] hi === JanC_ is now known as JanC [15:00] RAOF: it looks to be our friend vga16fb causing the problem this time [15:01] vgaarb is screwing up the blob with multiple cards [15:10] Sarvatt: I uploaded a patch about the vga arbiter and multiple cards [15:10] (with nvidia) [15:10] oh nice! i haven't had the time to dig into it more but that seemed to be what the problem was [15:21] Sarvatt: bug #573557 [15:21] Launchpad bug 573557 in nvidia-graphics-drivers "nvidia-current 195.36.15 + kernel 2.6.32 + dual cards crashes system" [High,Confirmed] https://launchpad.net/bugs/573557 [15:23] yeah I saw in your changelog message, uploaded it with 195.36.24 to x-updates too [15:24] phew i'm lucky dch doesn't pick up maverick yet :) [15:27] I uploaded that to lucid-proposed too but it will have to be accepted [15:30] Sarvatt: do we have this patch in lucid? http://cvs.fedoraproject.org/viewvc/rpms/xorg-x11-server/F-13/xserver-1.8.0-dri2-fix-handling-of-redirected-pixmaps.patch?view=markup [15:36] nope because its a fix for another patch series that only applies to xserver 1.8 (and was reverted to be done a different way upstream even) and we dropped the glx 1.3+ stuff so it shouldn't be needed [15:36] that was fixing a problem where compiz was showing the same image for different windows sometimes on xserver 1.8.0 [16:04] hello [16:04] how to get fglrx insted of radeon? Tried ubuntu software center, but ubuntu still uses radeon [16:05] VladimirBG: try Jockey [16:05] nothing is offered there [16:06] VladimirBG: what card are you using? [16:06] graphics card [16:07] ati mobility x1300 [16:07] Sarvatt: what's the fix that upstream adopted? [16:08] VladimirBG: I don't think your card is still supported by the fglrx driver [16:08] :( [16:08] VladimirBG: fglrx doesn't support that card, the power management options you can do in xorg.conf is as good as it's going to get for those because they dont have all of the power options that newer cards do anyway [16:09] thanks [16:10] ugh libdrm-psb needs a complete packaging overhaul now [16:11] tseliot: they reverted the commit that needed that patch for now :D [16:12] Sarvatt: and what are we going to do in Ubuntu? The netbook remix causes compiz to crash (as it uses clutter) [16:12] that patch didn't fix any crashes, it just fixed a display problem afaik.. [16:13] what is crashing? [16:14] Sarvatt: "application calling glxCreatePixmap when glx 1.3 is not supported" [16:14] its still crashing? [16:14] I have just installed Ubuntu on my netbook [16:15] its valid for compiz to call glxCreatePixmap because it needs to to use GLX_EXT_texture_from_pixmap and compiz has always done that (except when we had the glx 1.4 enablement) [16:16] its just a harmless message in that case, if its crashing its something else probably.. [16:17] you're right, the gnome decorator was not installed [16:17] never mind [16:17] ah yeah i've seen a few reports of that too, any idea how you got into the situation of not having compiz-gnome installed? [16:18] yes, I installed some compiz packages manually (as they are not installed in UNE) and forgot to install the decorator [16:18] I guess ubuntu-desktop installs all of the required packages [16:30] hmm wonder why mandriva is setting up the alternatives for the standard libdri.so and libglx.so in libdrm-psb [16:34] darn Bernardo is gone, need to see what the contents of /proc/ are for him when booting with psb [16:41] anyone else working on the gma500 on lucid at the moment? [16:43] Sarvatt: because poulsbo works with a rather old version libdrm [16:47] was it libdrm 2.3 ? [16:47] s/works/used to work/ [16:47] I believe its 2.3 indeed [16:48] but poulsbo doesn't work on lucid, myself and a couple of other guys are trying to get it working for a few days now [16:48] most credit goes to the other guys :p [16:50] credit goes to intel [16:50] not a big fan of intel at the moment [16:50] no working driver for x-server 1.7 from them! [16:50] I think it was powervr + intel [16:50] but yes... [16:51] yeah you're right powervr are the real bastards [16:51] i'm working on it here too but its rough without access to any actual hardware to see whats happening - https://edge.launchpad.net/~sarvatt/+archive/psb/+packages [16:52] do they packages use alternatives? [16:52] haven't gotten to the parts that need changing to alternatives yet :) [16:53] some guys think the problem is in drm [16:54] http://code.google.com/p/gma500/ [16:54] that's the repo we're using, maybe you can check if you're on the same path? [16:55] jbernardo found the problem - libdrm2 now installs to /lib instead of /usr/lib [16:55] yay svn [16:55] I removed /lib/libdrm.so.*, and the driver loaded! [16:55] svn + psb. all the fail in one place. [16:55] ;) [16:56] @lucazade: do you need to compile libdrm manual or did anyone edit the debian files? [16:56] back in a minute... [16:57] change the install rule to usr/lib/lib*.so.* /lib to fix that [16:57] ok... going to try it [16:57] lucazade: does it mean that the driver works or just that the module can be loaded? [16:57] the drivers works [16:57] *driver [16:58] interesting [16:59] jbernardo had anyway a segfault, and was dumped out of X [16:59] tseliot: yeah mandriva got the driver working with xserver 1.7 [16:59] ouch [16:59] so, err, rather than introducing yet another set of fucked up alternatives for psb, i don't suppose it's possible to rename the psb libdrm to libdrm_psb or so, and rename its symbols.. [17:01] but i guess "blob" means no [17:01] I guess it's possible but I don't remember why we didn't do it when we maintained the driver [17:01] i believe jbernardo already renamed the module to work with the mandriva patches (haven't checked myself) [17:03] "Rename of the module to contemplate the changes (drm to psb-drm, psb_ added to various prefixes, added mandriva patches), and most changes applied" revision6 === |Bernardo| is now known as Bernardo [17:06] HI [17:07] I only changed the kernel module (drm to psb-drm) [17:07] I was thinking of doing the same to the lindrm [17:07] libdrm [17:08] hi [17:09] seems like I lost tseliot by a couple of minutes [17:09] Sarvatt said: change the install rule to usr/lib/lib*.so.* /lib to fix that [17:09] It is not enough [17:10] http://sarvatt.com/downloads/patches/02_fix_kms_detection_with_psb.diff [17:10] I've already changed the preinstall and postrm scripts, just need to change the rules file to install in /lib [17:11] @Bernardo have you seen my pm? got some issue compiling xpsb-glx [17:11] lucazade: I'm booting my netbook now, will check that asap [17:11] ok thanks [17:12] Sarvatt: that is to apply to the "standard" libdrm2, or to the hacked libdrm-poulsbo? [17:13] all of the mesa stuff is going to need a huge amount of changes for the way things work in lucid [17:18] ok, I guessed as much, when the driver started crashing like crazy [17:19] lucazade: I cleaned xpsb-glx, I'm uploading it to svn asap [17:19] just need to check if my tree is "clean" [17:20] Bernardo: ok [17:21] outlaw45: give lucazade or me your email so we can add you to the project [17:21] quach.c@gmail.com [17:21] adding [17:21] I've also updated libdrm-poulsbo, just need to add this patch from Sarvatt, what did you do? [17:21] gonna install psb-kernel-source package from sarvatt and then build libdrm [17:22] are there many diffs between sarvatt's and ours? [17:22] outlaw45: added to the project [17:23] :p [17:24] Error! Could not find module source directory [17:24] outlaw45: did you check the diff's between sarvatt's source and ours? [17:24] that's what I get if I try to install the package.. [17:24] which are you building? [17:24] sarvatt's [17:24] Try ours... :) [17:25] and try purging the previous version before installing the new one, that usually helps with that error [17:26] purging did the trick :) thx [17:27] installing the one from svn at the moment [17:28] lucazade: I am building xpsb-glx, if it finishes without problems I'll upload it to svn [17:30] Bernardo: perfect... there also some redudant .patch inside xorg-xserver-video-psb [17:31] lucazade: I think I left one or two that have been superseeded, I'll check if I can remove them also [17:33] rev 19 has the libdrm changes for /lib [17:33] but still needs to be tested === apachelogger is now known as huntlogger [17:36] Sarvatt's patch doesn't apply, I'll check why before adding it [17:37] crappy system hear, multiple versions of psb.ko and drm-psb.ko [17:37] try to clean and retry [17:39] removed psb-kernel-source but still have [17:39] /lib/modules/2.6.32-21-generic/extra/psb.ko [17:39] /lib/modules/2.6.32-21-generic/updates/char/drm/psb.ko [17:40] anyone one know where they're from? [17:40] psb-kernel-modules [17:40] remove the package and those two [17:41] just rm? [17:43] yes [17:44] * Bernardo kicks svn, seems like my tree is borked (again) [17:48] restart.. [17:48] lucazade: rev20 has the correct xpsb-glx [17:49] ok checking [17:56] dh_install --sourcedir=debian/tmp -Xlibdrm.la --list-missing [17:56] dh_install: libdrm-poulsbo-dev missing files (usr/lib/lib*.a), aborting [17:56] that's what I get if I compile libdrm [17:56] outlaw45: just fixed that on rev 21 :) [17:57] :p [17:57] I had made the changes as I was compiling xpsb-glx and didn't check them :( [17:57] building again ;) [17:57] xpsb-glx gives me same error [17:58] trying also libdrm latest rev [17:58] strange... Let me check again [17:59] libdrm same error of outlaw45 [17:59] yep. I am going to delete it from svn and re-add it [17:59] ok [17:59] lucazade: which svn rev? [17:59] 20 [17:59] I've fixed libdrm on rev 21 [18:00] haven't seen [18:01] build libdrm and installing now.. [18:01] installed.. I'll try xpsb-glx now [18:02] wait [18:02] I'm uploading the fixed one in a few secs [18:04] commiting now the working sources from lucazade's tar, will tell you when it finishes uploading [18:05] ok i'll wait [18:08] dpkg-checkbuilddeps: error: syntax error in debian/control at line 23: block lacks a package field [18:08] if I build xpsb [18:09] yes xpsb-glx is broken.. bernardo is uploading a new one [18:09] ow ok.. [18:09] still uploading... it is big [18:09] gives me some time to finish my pizza :D [18:09] lol [18:10] and xpsb-glx is one of the huge problems with the psb driver - it basically installs a older version of mesa [18:11] another thing: echo "blacklist i915" | sudo tee -a /etc/modprobe.d/blacklist.conf [18:11] is still necessary? [18:11] maybe intel releases an IEGD version which works with xserver 1.7 in the future.. [18:11] lucazade: no idea [18:12] but psb still corrupts the screen if you try to load it in fb mode [18:12] outlaw45: they have already made some noises to the effect that they will jump 1.7 and work on 1.8 [18:13] yeah I read.. [18:13] and the mythical driver using gallium3d tech seems to have vanished [18:14] like duke nukem 3d [18:26] ok, rev 23 commited [18:28] still need to change dependencies, it is looking for libdrm [18:29] somewhere inside configure [18:29] time to check my backups again [18:30] ;) [18:30] lucazade: had you managed to build it in lucid? [18:31] no.. haven't been able to compile on lucid [18:32]