/srv/irclogs.ubuntu.com/2010/02/05/#ubuntu-x.txt

kklimondahttp://pastebin.com/f3e32f86b00:01
kklimondaSarvatt, ^00:01
kklimondaSarvatt, I have a nvidia closed drivers no so you can see it at the end of dmesg but first time it crashed I haven't have it installed at all.00:01
kklimondaI thought I've blacklisted nvidia before rebooting laptop but it seems the module is now nvidia-current and not nvidia..00:03
bryce2Sarvatt, btw I talked to apw about the lbm-nouveau naming for the driver.  The alternative would be to include a full update of all the dri's (radeon and intel) at the same time, but it sounds like it'd make life hell on our end since we'd need to test all the various combinations of old and new drms for each driver, with mesa, etc.00:03
kklimondaSarvatt, also I don't see any plymouth debug messages (and I'm pretty sure I've run with plymouth:debug but I don't see a Command Line at all in this dmesg o.O)00:04
Sarvattyeah looks like it defaults to /var/log/boot.log which we dont use, ahh well00:04
Sarvattbryce2: that would be an awesome alternative in my opinion because there would be something in the archive we can point people to for fixes that dont make it to .32 :D but if we did that i doubt we could enable nouveau by default because everyone would have the newer things and wouldnt ever use the 2.6.32 ones if we did?00:09
bryce2Sarvatt, well we'd only put the nouveau binary package on the livecd00:10
Sarvatti'm planning on doing a full lbm with intel and radeon on edgers at any rate just for that purpose00:10
bryce2Sarvatt, but think about the mess it'd cause with mesa... wouldn't we end up needing to support two versions of mesa?  ick00:10
Sarvattwhat issues would it cause with mesa?00:11
superm1tseliot, what's this plugin that plymouth falls back to when ubuntu-logo doesn't work?  00:11
tseliotsuperm1: it's the text plugin00:12
tseliot(at least currently)00:12
superm1tseliot, hmm.  it seems to be misbehaving on text strings when I send multi line strings to it00:13
superm1tseliot, forgive the crappy quality, but http://imagebin.org/83425 is what's happening00:16
superm1when those should all be left oriented and lined up at the newline characters.  00:17
tseliotsuperm1: I don't know much about that plugin but you can ask in #plymouth. Eventually we won't fall back on the text plugin any more00:18
Sarvattkklimonda: anything at /var/spool/plymouth/boot.log ?00:18
superm1tseliot, you mean because of KMS being prevalent, or because the ubuntu-logo plugin will work on non KMS hardware too eventually?00:19
tseliotsuperm1: I need to get plymouth to work with 16 colours fbs such as the one provided by vga16fb00:20
tseliotso that non-kms drivers can have something better than the text plugin00:20
superm1OK. if that's the case, then i wont really bother with trying to drive a solution into the text plugin at this point00:20
tseliotok00:21
superm1the other thing I was seeing is that questions (ask-question) aren't working, which i suppose is just a deficiency where ask-question isn't yet implemented for ubuntu-logo00:21
tseliotSarvatt, RAOF: the name of that module is nouveau_lbm, right?00:24
Sarvattlbm-nouveau00:24
tseliotsuperm1: yes, only ask-password is implemented. I'm working on the new theme so I might as well implement ask-question too00:25
RAOFFor some reason nouveau_lbm seemed more natural to me, too; the first libdrm patch I wrote was broken because of that :)00:25
superm1tseliot, that would be spectacular :)00:25
tseliotSarvatt, RAOF: ok, thanks 00:25
kklimondaSarvatt, nothing - there is no boot.log nowhere in my /var/00:30
Sarvattoh RAOF, new xserver in lucid overwriting the PPA one00:47
Sarvattx200:47
Sarvattso nouveau autodetection with no xorg.conf was broken00:48
RAOFAh.  Do you want to upload a new one, or would you like me to?00:59
Sarvatti dont have your patches, was going to grab your source off launchpad and pull it out if you weren't around01:00
Sarvattthings are all kinds of screwed up here too it looks like01:04
RAOFOk.  I'm not currently near my nvidia laptop; I'll be leaving this rather pleasant café soon, though, so I can have a squiz.01:09
Sarvattso much [   67.240647] [lbm-drm] nouveau 0000:05:00.0: PFIFO_INTR 0x00000010 - Ch 1 spam I don't have anything but that in dmesg01:10
RAOFAh, a FIFO storm.  Yay.01:11
Sarvatthuh, did libdrm get updated in lucid or something?01:12
Sarvatt(EE) [drm] Could not set DRM device bus ID.01:13
Sarvatt(EE) NOUVEAU(0): [drm] error opening the drm01:13
Sarvattnope still using PPA ones, not that01:14
Sarvattcold boot fixed it :)01:24
Sarvatthmm this is new01:25
Sarvatt[    0.509445] fb0: EFI VGA frame buffer device01:25
Sarvatt[    3.335681] fb: conflicting fb hw usage nouveaufb vs EFI VGA - removing generic driver01:25
jcristaui had that too.  killed my console.  i blame grub2.01:26
Sarvattyeah i was just going to say, looks like the grub2 update01:26
RAOFHow are you getting an EFI framebuffer?01:26
Sarvattscreen is black till nouveau kicks efifb out01:26
jcristauRAOF: beats me01:27
RAOFWhat crazy hardware do you have that actually has EFI enabled?01:27
Sarvattanything with insyde bios?01:27
jcristauhere inteldrmfb didn't actually kick efifb out, so i had a black screen until X started.  and even then no console.01:28
Sarvattlike all laptops the past few years01:28
Sarvatthow long ago did you have it start jcristau?01:32
jcristauhappened today, but last reboot was on Jan 2301:36
Sarvattjcristau: think this is it - http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu/lucid/grub2/lucid/revision/1920/util/grub.d/10_linux.in02:04
jcristauSarvatt: seems likely02:08
Sarvatthttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=56724502:09
ubottuDebian bug 567245 in grub-pc "gfxpayload=keep broken" [Normal,Open]02:09
* jcristau upgrades the severity02:11
jcristausigh.  that moron closed the bug?02:12
Sarvatti have to cold boot the nouveau laptop, it cant handle a warm reboot with gfxpayload=keep02:12
Sarvattand no consoles at all on intel with KMS enabled, the same as you02:13
jcristauthere. reopened and set to 'grave'.02:17
jcristauSarvatt: thanks for the pointer02:21
Sarvattno worries! its fixed in ubuntu now \o/02:28
Sarvattbryce2: grub2 update in the past day making efifb load and breaking consoles with KMS02:29
bryce2ah yes02:30
Sarvattkklimonda: that probably fixed your problem02:30
Sarvatthttps://lists.ubuntu.com/archives/lucid-changes/2010-February/004893.html02:33
Sarvattcrazy week for bugs :(02:33
bryce2fun fun02:36
Sarvattseems like its when ureadahead profiling  happens i get hung on a splash screen03:23
kklimondaSarvatt, i've also had to downgrade xserver to version from your ppa03:26
Sarvattyou can just use the lucid stock xserver if you make an xorg.conf03:28
SarvattSection "Device"03:28
Sarvatt        Identifier      "Configured Video Device"03:28
Sarvatt        Driver          "nouveau"03:28
SarvattEndSection03:28
kklimondaach03:29
RAOFBah!  The latest xorg-core isn't in git yet.05:20
bryce2xorg-core?05:28
bryce2ah xorg-server.  pushed.05:30
bryce2sorry, sprint is kind of a madhouse05:30
RAOFThat's ok.05:30
* tseliot packaged the latest beta of the nvidia driver: https://launchpad.net/~albertomilone/+archive/proprietary-video-improvements05:33
tjaaltonhmm the sprint-bryce left.. I don't know what he means by having to ship two mesa's06:05
tjaaltonhaving the .33 drm in lbm would be great06:05
tjaaltonall the drivers, not just nouveau06:06
RAOFI guess that he might have been thinking that the .33 drm would require a different mesa as well?06:06
tjaaltonfor instance intel 2.10 is happy with .33 and mesa 7.7?06:06
RAOFFrom the looks of l-b-m-nouveau, adding intel & ati to that wouldn't be too hard.06:07
tjaalton(.32 is enough for intel)06:07
virtualdwill lucid l-b-m-nouveau always be based on .33?06:09
tjaaltonprobably06:09
tjaaltondoubt it'll get rebased06:09
virtualdok06:10
tjaaltonat that time there should be the kernel from MM backported to lucid06:10
RAOFThat's right; we're getting newer kernels in lucid, aren't we.06:10
tjaaltonthat's the plan aiui06:12
tjaaltonI'll merge & upload new mesa & libdrm today, you can push whatever you have before that?06:12
tjaaltonnew mesa = 7.7-branch snapshot from debian06:13
tjaaltonsince nouveau is a go06:13
tjaaltonso libdrm is ok to go as well06:13
RAOFlibdrm is pushed to pkg-xorg git.06:17
RAOFIt includes a merge of 2.4.17-1, so I may have done some of the work you wanted to do already :)06:17
tjaaltonyeah I noticed, that's great06:20
brycehheya07:13
brycehyeah I assume if we upversion the drm, we'll need a newer version of mesa to go with it.07:14
tjaaltonaiui 7.7 is enough for 2.4.1707:37
tjaaltonnewer nouveau ddx needs stuff on top of .17, but not mesa07:37
tjaaltonso the deps go the other way, ie. mesa/ddx depend on some libdrm version :)07:38
RAOFI think we can probably take it as read that nouveau wants git HEAD of everything :)07:44
tjaaltonI hope they'll ship a release when .33 kernel is released07:45
RAOFThey've still got (at least) one ABI break pending; I don't think they want to release until they've done that.07:51
RAOFAt least, that's what I recall from previous discussions.07:51
tjaaltonok07:54
RAOFThat said, they didn't want to be merged into mainline until after that ABI break.  Maybe that'll have changed their minds.08:22
brycehhttps://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/51743008:25
ubottuUbuntu bug 517430 in xserver-xorg-video-nouveau "[MIR] xserver-xorg-video-nouveau" [Undecided,New]08:25
RAOFbryceh: Thanks for that.08:29
brycehstarting to get a lot crossed off https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-lucid-xorg-driver-selection-for-nvidia-hardware08:30
brycehRAOF, is https://edge.launchpad.net/~xorg-edgers/+archive/nouveau just packages prepped for upload into lucid?08:34
brycehRAOF, tjaalton, for making xserver use nouveau over nv, should we just s/nv/nouveau/ in xserver, or should we look at resurrecting patch 104?08:39
bryceh(...or something else...?)08:40
tjaaltonbryceh: I think the ppa version already has something08:41
tjaaltonfedora has a patch which doesn't use nouveau for all the chips, don't know if it's still relevant08:43
brycehtjaalton, which ppa?  I checked 2:1.7.4.901~git20100122+server-1.7-branch.d3e54304-0ubuntu0sarvatt 08:43
tjaaltonI don't know :)08:43
brycehdaniels resigned from the x.org board?08:44
brycehaha, 106_nouveau_autodetect.patch in the nouveau ppa08:45
brycehok looks like raof resurrected 10408:45
brycehok good, looks like we can cross that item off too08:45
tjaaltonwhat's the url for that?08:50
brycehhttps://edge.launchpad.net/~xorg-edgers/+archive/nouveau/+packages08:50
brycehhttps://edge.launchpad.net/~xorg-edgers/+archive/nouveau/+files/xorg-server_1.7.3.902-1ubuntu12~ppa1.dsc08:51
tjaaltonthat's not good enough though08:52
tjaaltonnvidia should be dropped from it08:52
tjaaltonbecause if there's an xorg.conf on the system and no nvidia installed, it'll try nvidia and only that08:53
brycehtjaalton, did you look at the patch?  nvidia isn't listed08:53
tjaaltonuh crap08:53
tjaaltonlooked at the wrong patch :)08:54
bryceh106_nouveau_autodetect.patch08:54
tjaaltonyep08:56
tjaaltonlooks ok08:56
brycehis nouveau only for i386 and amd64?  does it support any other arch's?08:56
brycehpowerpc?08:56
bryceharm??  I see -nv is listed for arm...08:57
brycehwell hell, -nv is listed even for alpha ;-)08:57
tjaaltondebian likes to torture the buildd's alot :)08:58
brycehok so for now we only care about i386 and amd64 I guess08:59
brycehdoes -nv need to be removed from xserver-xorg-video-all or can -nv and -nouveau both exist side by side?08:59
tjaaltonbryceh: I noticed that ogra has tested touchscreens with the current stack. do you know if he used evdev or what?08:59
tjaaltonbryceh: no, nv is still needed for some chips, as noted in the patch09:00
brycehno I didn't talk to him about his testing09:00
tjaaltonmaybe tseliot knows more09:00
tjaaltonthe blueprint was updated recently09:00
brycehI saw martin marked the task done but dunno if he talked with ogra first or just figured it was already tested well enough09:00
brycehtjaalton, what I know is several people have tested and found it worked well (with -wacom)09:01
brycehbdmurray for instance09:01
brycehhe's got an HP laptop with a touchpad screen that we worked on a bit09:01
tjaaltonwacom is not evdev though09:01
brycehturned out it just needed a kernel driver enabled09:01
tjaaltonnor is it replacing evtouch09:01
brycehtjaalton, hm what's your question?09:02
tjaaltonbryceh: that there is no evtouch driver in lucid anymore, and whether evdev is good enough09:02
brycehwhat I've seen is that people need -wacom09:02
RAOFbryceh: nouveau definitely works with PPC; it should work on all archs which actually have nvidia hardware.09:02
* bryceh adds to vars.powerpc and vars.ppc6409:03
tjaaltonbryceh: some touchscreens have a wacom, yes. those need the wacom driver09:03
tjaaltonsome (like the X61 tablet here) have a serial wacom, which doesn't work yet09:03
tjaaltonOOTB anyway09:03
brycehRAOF, sparc? arm?09:04
brycehI'm not sure what all platforms have nvidia hardware09:04
tjaaltonthose three should be enough09:05
RAOFI don't actually know.  arm certainly does; that's tegra, right?  I don't know if nouveau would drive that, though.09:05
tjaaltonlunch ->09:05
brycehhm, well guess we can add as we go09:06
RAOFOh, this is for the seeds?  Otherwise, is there any particular reason to do arch restrictions?09:06
brycehtjaalton, anyway yeah ask pitti or tseliot if you have questions about what this has been tested against09:06
brycehRAOF, right seeding09:06
brycehjust getting the patch ready.  Figure I'll wait on uploading it until nouveau's in main09:07
RAOFDoes the nvidia binary driver still destroy the ability for other drivers to work with X, or has that been fixed by the alternatives work?09:09
RAOFIf so, xserver-xorg-video-nouveau should stop conflicting with nvidia-glx.09:09
* RAOF should test that.09:10
brycehtseliot was playing with that a bit today09:11
brycehhttp://launchpadlibrarian.net/38788005/nouveau.diff09:22
indushi10:10
indushello 10:18
indusi have some questions10:18
indushello11:08
indushello11:46
indusagain11:46
Sarvattbryceh: linux-backports-nouveau is only i386/amd64?12:28
Sarvattmeaning i dont think you want to add the nouveau ddx to the other arches yet.. 12:30
indusanyone here13:01
vish!ask | indus13:02
ubottuindus: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)13:02
indusvish, here too ?13:02
indusvish, you might have guessed, its the fglrx question13:02
indus:)13:02
indusvish, you are on the art team isnt it13:02
vishindus: I use ATI but havent used fglrx13:03
vishindus: yup13:03
indusvish, i saw your name on the membership wiki, that is approved?13:03
vishindus: its the coming week , but kinda off topic here ;p13:04
indusoops13:04
indusiam looking for ara13:34
indusor anyone really13:34
jcristauthen ask your question.  if someone can answer it they will.  if you don't ask, they won't.13:35
Sarvattodd  196_xvfb-fbscreeninit-handling.patch doesn't apply to server 1.7 branch even though hw/vfb/InitOutput.c hasn't changed in months, i must be missing something13:39
Sarvattguessing the git version is different than the one applied in the archives13:39
indusa ny one know about the fglrx in lucid13:43
tjaaltondoesn't work13:43
indusactually no, i have signed up for testing for the driver, so have some questions13:43
tjaaltonstill, doesn't work13:43
Sarvattyep git version was for -p0 instead of -p1, i'll fit it in git13:43
indusyes i know13:46
indusso question is, if it doesnt work, how can you test it13:46
tjaaltonyou can't13:46
Sarvattwhen there is one that you can test you'll get info on it, he sent out that email a bit too prematurely13:47
indusok thanks13:47
indusill wait for the email, just signed up today 13:47
indusbut it seems testing cases are valid 13:48
indusinstallation etc13:48
tjaaltonit won't install13:48
indusi installed already 13:48
indusits available in hardware drivers13:48
indusdoesnt work is a different thing13:48
tjaaltonah, so it doesn't provide the abi anymore.. nice13:48
tjaaltonbreaks systems for no reason13:49
industjaalton, whats abi13:49
Sarvatti wouldnt expect it in the near future though, its up to ATI to give us a driver that works and they aren't very good adopting changes in linux :D13:49
indusbut i say, it shouldnt be offered in hardware drivers if it wont work :)13:49
tjaaltonindus: the xserver conflicts with < xserver-xorg-video-6, which means that drivers providing -5 or earlier conflict with the server, and are removed on upgrade13:50
tjaaltondamn right it shouldn't13:50
indusxorg is 1.7 i belive in lucid 13:51
indus*believe13:51
indusor is that 7.513:51
jcristauxserver is 1.713:52
jcristauxorg is something close to 7.513:52
indusi would like to kno w the difference between xorg and xserver13:52
vishSarvatt: hmm , with ati , the -edgers ppa hung on boot with > http://pastebin.com/m717b8ca3 , i was dropped into a console and the errors kept running at light speed.. had to hard shutdown  ,happened twice :( , but was able to boot the next time around... still it does a freaky sort of hang during boot  , I'll have to see if it happens again13:53
vishs/with/in13:53
indusin any case, i guess the nvidia tests can go on13:53
indusok another question i have is, about s3tc compression, i compiled it but doesnt seem to work13:53
Sarvattvish: have you updated grub to 1ubuntu3?13:55
* vish checks13:55
Sarvatt1ubuntu2 was breaking KMS all kinds of bad ways here on all my machines13:55
indusis there a mesa channel?13:56
vishah , maybe , grub-pc is still ubuntu213:56
Sarvatt#dri-devel13:56
* vish reloads repos13:56
indusSarvatt, thank you ,btw do you know about s3tc ,probably yes13:56
Sarvattvish: open up your /etc/grub.d/10_linux and go down to where it says gfxpayload=keep13:57
Sarvattand delete that whole section13:57
Sarvattif you can pastebin your 10_linux i'll tell you the whole section to delete, its already deleted here so i dont have it13:57
Sarvattbut you can do that then sudo update-grub and it should hopefully fix it13:58
Sarvattor just update grub2 to 1ubuntu3 if its available, thats the only change14:00
Sarvattwas it a warm boot when it failed and a cold boot when it didnt? because thats what happened here, on warm boots i had all kinds of gpu resets and unable to talk to drm in X and no consoles because of that darn forced efifb change14:02
Sarvatti'm not using ati though, no idea what was happening there14:03
vishSarvatt: when i restarted , it hung , but when i hard shut it down and started it would boot14:04
Sarvattyeah thats what i was experiencing14:04
herman_Sarvatt, hi14:04
Sarvatthello14:05
herman_i was having problems with intel video graphic on ubuntu 9.0414:05
herman_do you remember?14:05
Sarvattyep! greedy helping or did you upgrade to karmic?14:06
herman_i upgrade to karmic14:06
herman_and now, it's better14:06
Sarvatthopefully you're not going to tell me its worse? :D14:06
Sarvattphew14:06
herman_but i'm having problems with web14:06
herman_my icon don't give me option to see the conections14:07
tjaaltonnot related to x14:08
Sarvattnetwork-manager is what you're having a problem with then, I'm afraid I can't help too much in that area14:08
herman_it saids something like this: "the device is not manageable"14:08
herman_ok14:08
herman_where can i find help about this14:09
vishherman_: #nm14:09
herman_anyway, thanks for the help14:09
Sarvatt#ubuntu would be the best place probably, I would just google "the exact error string" karmic with the exact error message you get in quotes like that14:10
herman_Sarvatt, yes, but my system is in portuguese14:11
herman_and i don't know exactly how the string will be in english14:11
herman_and my english is not so good14:11
Sarvattherman_ if you can type it in portuguese here I can tell you what it is in english14:15
Sarvatti've got network-manager-applet's pt.po open14:16
vishSarvatt: i think the update ubuntu3 removed the gfxpayload=keep section >  http://paste.ubuntu.com/369537/14:17
Sarvattyep thats what the 1ubuntu3 change did, hopefully that fixes things for you14:18
herman_Sarvatt, my icon says: "rede com fio: o dispositivo não é gerenciável" 14:20
Sarvattah thats pt_BR14:21
herman_Sarvatt, yes14:21
Sarvatttry googling network manager "device not managed" karmic14:22
herman_a lot of people are having this problem on karmic14:22
Sarvatthttp://www.google.com/search?sourceid=chrome&ie=UTF-8&q=network+manager+%22device+not+managed%22+karmic14:22
herman_ok, i will see14:22
Sarvatthopefully one of those ubuntuforums posts can help you out14:22
Sarvatthttp://ubuntuforums.org/showpost.php?p=6975928&postcount=3 looks like the solution, people upgrading from jaunty to karmic had that problem14:24
CobaltSarvatt: I had a talk with libv yesterday, from what he says, the Intel bugs aren't going to be fixed because things work fine with newer kernels, is that correct?14:25
Sarvattwhat intel bugs?14:25
CobaltWhere you get thrown back to the gdm greeter.14:26
SarvattI wouldn't say thats always true, there have been a steady stream of backported fixes from .33 to .32 upstream because its a LTS kernel for alot of distros14:27
CobaltI'm on .31.14:27
Cobalt.32 works, but introduces another couple of issues, which makes using it a little tricky.14:27
Sarvattoh .31 is pretty much dead, I wouldn't expect anything more from it :(14:27
Sarvattthe last point release was supposedly the final one14:28
CobaltIsn't the problem a regression introduced in the Xorg Intel drivers though, rather than a problem from the kernel itself?14:28
jcristauit's all mashed up together14:29
Sarvatt^14:29
CobaltThe 20100127 update caused a lock-up. Mouse was still working, but nothing else. Had to REISUB.14:29
Sarvattit seems like they are expecting newer kernels in the later git versions, i can't use git intel on .3114:30
Sarvattlots of random invalid bo alignment errors14:31
herman_Sarvatt, i already get wired connection14:31
herman_before, i didn't get14:31
Sarvattjust stick with 2.9.1 Cobalt is my recommendation14:31
Sarvatti have to do that regardless even on lucid because things are broken on 945 since the beginning of december :(14:32
CobaltFair enough.14:34
CobaltThey seem to have moved weird interface names to sane defaults, my ra0 has become wlan0. Which is nice.14:34
CobaltThings should have evened out a bit though, right, for when Lucid will come out in April?14:35
Sarvattthat sounds like you are using a mainline kernel that has staging disabled so you are using a different module for wireless14:36
CobaltNo, all the kernels I've been using have been from the Ubuntu repos. The .32 kernel I used was in the Lucid repo.14:36
herman_Sarvatt, i got it14:37
herman_i solve all my problems now14:37
Sarvattgood to hear :D14:37
Sarvatttheres 2 different ralink drivers in the kernel for alot of chipsets last i looked, wlan0 one is using mac80211 instead of the ralink specific stuff14:38
herman_i just era my file /etc/network/interface and i can acess my connections14:38
Sarvattis the module name the same Cobalt?14:38
* Sarvatt renames #ubuntu-x to #ubuntu-wireless :D14:38
CobaltSarvatt: It is, yeah.14:39
Cobaltrt2860sta.14:39
CobaltAlthough it loads the module fine, automatically, it does not put up the interface. I have to manually do that with ifconfig wlan0 up.14:40
herman_Sarvatt, you are helping me a lot14:40
herman_very thanks14:40
Sarvattmesa classic nouveau driver was pushed to master, time to enable it on edgers builds :D14:53
SarvattRAOF: would you mind updating the nouveau ubuntu git branch with your latest changes in debian/ whenever you get a chance?15:19
vishoh oh... "session active not inhibited" bug present in -edgers ppa :(15:24
Sarvattneed to update it to build against the newer libdrm in xorg-edgers, figured i'd pull the xorg-edgers/nouveau stuff into xorg-edgers/ppa directly incase anyone wanted to use the newer mesa with nouveau15:25
Sarvattthats gnome-power-manager vish15:25
Sarvattwhich you also just updated15:25
vishaw  , damn it.. gpm sneaked in an update :/15:26
vishhehe , i was thinking Lucid cycle was too quite without gpm problems :p15:31
Solariondid system76 die?15:33
SolarionI can't reach their servers anymore15:33
Sarvatt-rw-r--r-- root/root   2224748 2010-02-05 15:38 ./usr/lib/dri/nouveau_vieux_dri.so15:53
Sarvattbuilt find, now to find someone to try it :D15:53
jcristauheh, nouveau_vieux? :)15:54
Sarvatt3 feet of snow predicted... maybe I'll have time to package up nouveau_dri.so now :D16:04
tjaaltonwe got almost that much already :)16:20
bjsnidertseliot, what does envy do at this point? i thought it downloaded hte drivers from nvidia and installed them with its own packaging scripts. but i got an email from a guy who is using it to install drivers out of my ppa17:51
tseliotbjsnider: I've removed envy from the archive17:56
tseliotbjsnider: BTW I put the nvidia beta driver in my ppa17:56
bjsnidertseliot, does it grab those extra files too?17:56
tseliotyep17:56
bjsniderhow easy do you think it would be to take the new build scripts and replace the alternatives code with diversions code?17:57
bjsnidertseliot, i meant that they ere using envy in karmic, not lucid17:57
tseliotbjsnider: I think it's going to be bit of a mess but still doable17:58
bjsnidertseliot, are you planning to have a beta driver more or less permanently in the archive?18:02
tseliotdo you mean a -beta flavour?18:02
bjsniderwell, i don't care what you name it, i just mean a package that's an option, whatever it's called18:03
bjsniderbut nvidia-beta would be good18:03
bjsnideror nvidia-unstable18:03
Sarvattdunno how much of a point that would have since it probably wouldn't get updated post release :D18:05
tseliotI think it would be better to keep that in a PPA, maybe xorg-edgers18:05
tseliotSarvatt: good point18:05
bjsniderhow hard is it to get a new driver pushed through after a release?18:05
tseliotbjsnider: the SRU team would eat me alive ;)18:05
Sarvattsweet, thanks for making that newer nvidia-current tseliot18:06
bjsniderwhat does that acronym stand for?18:06
Sarvattstable release update18:06
bjsniderbut it's nvidia that takes on the responsibility for supporting their driver18:07
tseliotSarvatt: I hope it fixes some issues with suspend/resume in lucid18:07
tseliotbjsnider: if a package is in main, we take responsibility for it as it's officially supported (with the obvious limits of proprietary drivers)18:08
bjsnidertseliot, how can you support prebuilt libs and stuff like that? it would be a copyright violation for you to support it18:10
Sarvattthey throw lots of testing at it and verify the version shipped works, some people actually dont want to upgrade things like that that has the potential to break things (crazy I know)18:13
Sarvattespecially when you dont have access to the code so you dont know what could be breaking (or fix it)18:14
* tseliot nods18:33
bjsniderwell, i've actually told people who have emailed me about issues specific to nvidia that they should go there and complain18:40
bjsniderbut they use vbulletin to manage bug reporting which is nuts18:40
bjsniderbut whatever18:41
LLStarksbryce2. bryceh. is anyone else getting "libGL is too old"?18:41
LLStarksi think the nvidia blob is getting installed on intel machines and its interfering18:43
bryce2LLStarks, haven't heard that one before18:46
bryce2do you have any ppas installed?18:46
LLStarksnot using edgers at the moment.18:46
LLStarksbut the blob was basically disabling direct rendering for intel18:46
LLStarksentire screen would bug out and text flip if compiz was activated18:49
bryce2LLStarks, you should probably talk to tseliot about it18:53
tseliotLLStarks: what does "ldconfig -p |grep GL" say?18:54
LLStarksit's fixed now because i purged the drivers18:55
tseliotLLStarks: there's no need to do that. They can coexist with open drivers in lucid18:55
tseliotdisabling the driver with the latest release of jockey should do it. Or a simple command should do it too18:57
LLStarkslibGL.so (libc6) => /usr/lib/nvidia-current/libGL.so18:58
LLStarksthat doesn't belong.18:58
LLStarksit's the only thing added.18:58
tseliotLLStarks: sudo update-alternatives --config gl_conf (and select mesa)18:58
tseliotthen type "sudo ldconfig" and reboot18:59
LLStarkshttp://img94.imageshack.us/img94/7263/ohgodo.png18:59
LLStarksthat's what was happening before18:59
tseliotouch, I've seen that already. I'm not sure if it's related to this problem though19:00
LLStarksno, it is.19:00
LLStarksthat libgl causes it.19:00
tseliotmy two commands will fix it then19:01
LLStarksi know.19:01
Sarvatti'm guessing you had a ppa enabled with that screwed up mplayer bringing in the nvidia-current driver19:02
Sarvattsaw someone else that did that a few days ago19:03
LLStarksprobably.19:05
Sarvattanyone having problems with mutter on intel? http://pastebin.com/f726092cb20:37
Sarvattahh was a driconf option i had set20:39
Sarvattmutter is absolutely killing graphics performance here, qgears2 render backend ~20 fps gl backend 9 fps, under metacity its 38 and 1920:44
* Sarvatt cant wait to see the bug reports about the 70 fps glxgears under mutter in UNE :)20:45
Sarvattgnome-shell has come quite a long way in the past few months it looks like, the menu is actually usable on this 8.9" screen20:49
AlanBellhello20:54
AlanBellI was just wondering if there is anything I can do to help progress Bug #428769 20:54
ubottuLaunchpad bug 428769 in xserver-xorg-video-intel "compiz starts with a blank screen on a 2048x1152 monitor" [Undecided,Confirmed] https://launchpad.net/bugs/42876920:54
Sarvattalmost a 50% performance drop in openarena under mutter :(21:04
* Sarvatt starts liking compiz for some reason.21:09
* AlanBell likes compiz21:26
* AlanBell is stuck on 8.10 :-(21:27
* AlanBell doesn't like bug 42876921:27
ubottuLaunchpad bug 428769 in xserver-xorg-video-intel "compiz starts with a blank screen on a 2048x1152 monitor" [Undecided,Confirmed] https://launchpad.net/bugs/42876921:27
bjsniderwhy be stuck on intrepid?21:27
bjsnideris the nvidia-current driver broken?21:28
BUGabundoevening fellows21:29
bjsniderthere he is!21:29
BUGabundolucid and nvidia21:29
bjsniderrock and/or roll!21:29
BUGabundotwo failed reboots with X corruption21:29
BUGabundolaunched older kernel and got low resolution mode21:29
BUGabundopastebining X logs as we speak21:29
BUGabundo$ pastebinit Xorg.0.log21:30
BUGabundohttp://paste.ubuntu.com/369761/21:30
BUGabundo$ pastebinit Xorg.0.log.old 21:31
BUGabundohttp://paste.ubuntu.com/369762/21:31
BUGabundolet me know if you prefer me to file a new bug, or if this is know 21:31
BUGabundothanks in advance21:31
bjsnideralberto's not in here at the present time21:31
* BUGabundo goes into idle mode21:31
BUGabundowell not much I can do, right21:32
BUGabundonewest kernel seems unsuable21:32
BUGabundoand older won't work very well21:32
BUGabundogot some X updates, so let me do does and test again21:33
Sarvatti've seen that exact backtrace from people on ati intel and nvidia now since reenabling apport in xserver, hope thats not the cause :(21:36
jcristausigquit? wtf.21:37
BUGabundoSarvatt: me ?21:37
BUGabundoSarvatt: was that about my report ?21:42
BUGabundoif so, I better file a bug21:42
AlanBellbjsnider: the nvidia-current driver won't help much on my intel chipset :-)21:58
AlanBellbjsnider: although actually I got it wrong, I am stuck on 9.04 Jaunty21:59
BUGabundoFYI after last batch of updates, reboot went well21:59
BUGabundotook a bit to show GDM with lot of IO (KMS?), and sheduler fallback to Performance 21:59
BUGabundoother then that, everthing seems ok21:59
AlanBellthe intel driver in Karmic and Lucid won't do compiz with a 2048 wide monitor21:59
BUGabundoping me if anyone needs extra logs22:00
BUGabundothanks22:00
bjsniderAlanBell, why won't it do that?22:08
AlanBellI have no idea22:08
AlanBellwell 2048 is the max texture size of the card22:08
bjsniderwhat an outrage22:08
AlanBellso my monitor is equal22:08
bjsniderviolence must ensue22:08
AlanBellif the monitor was any bigger then compiz wouldn't run at all22:08
AlanBellbut the test is for less than or equal to max texture size22:09
bjsnideryou don't really have a 2k monitor though right? it's two monitors22:09
AlanBellso it runs. Successfully on 9.04 and not on 9.1022:09
merriamyes, there are cheap 2048 monitors.22:09
merriamI have one here.22:09
AlanBellI do have a 2048x1152 single screen22:09
bjsniderwhat's the physical size?22:10
AlanBelland it was relatively cheap, but I don't want to toss it away :-)22:10
merriamThis one is 23 inch.22:10
AlanBellerr about so big22:10
AlanBellyes 23 inches sounds about right22:10
AlanBellit is a samsung22:10
bjsniderwhat's the dot pitch? in the 120s?22:11
bjsniderit sure isn't 9622:11
AlanBelllooks like 20 inches for the 204822:12
AlanBellwouldn't be surprised if it was exactly 10022:12
BUGabundoI take back what I said22:13
BUGabundomy system just log off22:13
BUGabundowithout no aparent reason22:13
BUGabundoand went to GDM22:13
bjsniderBUGabundo, alberto is here now22:14
bjsniderAlanBell, what is the height of the screen in inches?22:15
AlanBellabout 11 1/4 inches22:16
bjsniderdot pitch: 102.422:16
AlanBellit has lots of dots22:17
bjsniderit's a little better than usual, not as good as an ebook reader or something22:18
AlanBellit is ace in portrait mode with full screen gedit and a big page full of python22:20
AlanBelljust broken compiz in 9.10 makes me sad :-(22:21
AlanBellI would be quite happy to dig about in some code to fix it, just I have no idea where to start22:22
bjsniderdid you tell intel about it?22:22
AlanBellI am not even certain whether it is a compiz thing, an intel driver thing or even a kernel thing22:23
merriamWhat makes me sad is that Compiz fails with a blank screen, so Ubuntu's install fails.  That may be less relevant here...22:23
AlanBellhow do I tell intel about it?22:23
bjsniderAlanBell, i've never submitted a bug to intel22:24
AlanBellit is an open source driver22:24
AlanBelland I have a bug in launchpad22:24
bjsniderit is created by intel developers22:24
bjsniderkieth packard et al.22:25
AlanBellok, where do I go to hassle them?22:26
bjsniderif you submit a bug to launchpad what happens is they'll wait until the intel guys fix it and then they'll close the bug22:26
bjsniderAlanBell, packard runs freedesktop.org, so i'd start there22:26
jcastroAlanBell: I just went through this, you make a bug report in the fdo bug tracker and link it in launchpad22:26
bjsnidercoolio22:26
jcastroAlanBell: here's an example: https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/51667622:27
ubottuUbuntu bug 516676 in xserver-xorg-video-intel "GPU hang on intel" [Unknown,Confirmed]22:27
bjsniderthere's another one other than packard...jesse something22:27
AlanBellok, so I did find a freedesktop.org bug that seemed similar (with some people on the thread reporting random different bugs)22:28
AlanBelland I linked that22:28
AlanBellhttps://bugs.freedesktop.org/show_bug.cgi?id=2299622:28
ubottuFreedesktop bug 22996 in Driver/intel "[945GM] external lcd does not work on high resolution" [Normal,Reopened]22:28
AlanBellI think I might file a new bug, that one is a bit confused22:32
AlanBelldo they have an IRC channel that you know of?22:33
bjsniderdunno22:33
AlanBell#intel-gfx would appear to be the place22:36
bjsnidercoolio22:36
* merriam again follows Mr Bell to a channel.22:44
merriamI think the seriousness of the bug is underestimated.22:45

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!