ubotuNew bug: #182284 in xserver-xorg-video-intel (main) "no direct rendering after upgrade to hardy" [Undecided,New] https://launchpad.net/bugs/18228400:47
ubotuNew bug: #187281 in xserver-xorg-video-ati (main) "Graphic problems with ATI" [Undecided,New] https://launchpad.net/bugs/18728100:49
ubotuNew bug: #189147 in xorg (main) "X display freezes, slowly fades to black (video included)" [Undecided,New] https://launchpad.net/bugs/18914704:02
ubotuNew bug: #189167 in mesa (main) "Missing glClipPlane support in r300" [Undecided,New] https://launchpad.net/bugs/18916706:26
ubotuNew bug: #120619 in xorg (main) "[Gutsy] invalid resolution detected resulting in BIG fonts on i915" [Undecided,New] https://launchpad.net/bugs/12061908:53
Companyhrm, everybody asleep here, too09:00
Companyi'm wondering who to poke about https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/14784609:00
ubotuLaunchpad bug 147846 in xserver-xorg-video-ati "resolution out of sync with version 2:" [High,Incomplete] 09:00
tjaaltonCompany: do you have a radeon or intel?09:33
Companytjaalton: radeon09:38
Companytjaalton: (last reply to that bug is mine)09:39
tjaaltonyes I noticed09:39
tjaaltontry the driver from http://wiki.ubuntu.com/XorgOnTheEdge09:40
Companyradeonhd or ati?09:40
Companybrb (hopefully ;))09:42
Companylogging out and back in should be enough to restart X, right?09:45
tjaaltonI'm not sure what the gdm default is09:46
Companyi got to see the console in between09:46
tjaaltonI reckon it didn't help?09:46
Companystill the same issue: garbled screen andmanually having to xrandr without seeing a lot09:47
tjaaltonok, please open a new bug and attach your logfile and config.09:47
Companyhalf of that is easy - i have no config :)09:47
ubotuLaunchpad bug 189198 in xserver-xorg-video-ati "r100 video comes up garbled" [Undecided,New] 09:50
tjaaltonCompany: umm, on the other bug you said that resolutions such as 1920x1200 worked right? I'm not sure how 446Xpro is able to do that..10:00
Companytjaalton: i can definitely see it10:00
tjaaltonit's not a widescreen monitor..10:00
Companyi know10:01
ubotuNew bug: #189198 in xserver-xorg-video-ati (main) "r100 video comes up garbled" [Undecided,New] https://launchpad.net/bugs/18919810:01
Companyit looks pretty stretched and is flickering, but the image is vivible10:01
tjaaltonthe log shows that it's using 16x12, and you listed that as working?10:01
Companyit's using 1600x1024, no?10:03
Companyi was assuming that it does that, because the other modes work when i xrandr to them10:04
tjaaltonyou listed 1600x1024 as working too10:05
Companywait, i did?10:06
tjaaltonWORKS: 1920x1200, 1600x1200, 1600x1024...10:06
Companyi messed that up when copy/pasting, i'm sorry10:06
tjaaltonhmm, indeed it is trying to use 16x1010:06
Companyyep, 1680x1050 works10:07
Companylooks ugly, but works10:07
tjaaltonwhat if you generate the config? 'dpkg-reconfigure xserver-xorg'10:07
tjaaltonI meant it's using 1600x102410:08
Companyi was just checking what i'd written in the bug10:08
Companycan i dpkg-reconfigure while X is running?10:09
tjaaltonit doesn't probe or anything10:09
Companyhrm, the xorg.conf doesn't contain anything important10:12
Companyjust "configured device" for everything and a keyboard layout10:12
tjaaltonthat's enough10:12
tjaalton..for now10:13
* Company tries10:13
Companysame problem10:15
tjaaltonok, so you can force the resolution using these instructions: http://wiki.debian.org/XStrikeForce/HowToRandR1210:16
tjaalton"forcind a preferred mode"10:16
Companyyeah, that was pretty much what i was doing - i had set a preferred resolution on gnome login which caused an xrandr to 1280x102410:18
tjaaltonit would be cool if you could report this upstream10:18
Companybut the new gnome stopped auto-xrandr'ing10:19
Companywhat's the preferred irc channel for poking upstream people?10:21
tjaaltonask agd5f (some US timezone though..)10:22
Companywill do10:23
tjaaltonhmm, actually he's real name is alex deucher, so maybe he's German after all :)10:24
Companyhe works for ati now, so he probably is us-based nonetheless ;)10:24
Companygutsy shipped xorg 1.4?10:27
Companyhrm shouldn't matter, because it was caused by that patch removal10:28
tjaaltonnope, 1.310:28
tjaaltonyes, that patch basically forced the setting, which is equivalent to the PreferredMode10:29
Companyfreedesktop.org 1438310:36
tjaaltonadded a comment about the driver version10:40
Companyi'll try poking agd5f tonight or tomorrow10:41
tjaaltonok, cool10:42
=== seb128_ is now known as seb128
=== seb128_ is now known as seb128
=== imbrandon is now known as imbrandon_
=== mvo__ is now known as mvo
Q-FUNKis there a source tarball for this?16:40
Q-FUNKI was gonna add bartman's vcons patch and upload to my PPA, but no source tarball found.16:40
tjaaltonQ-FUNK: I'm about to upload a new merged version16:41
tjaaltonwith your patches16:41
tjaaltonthat version was never uploaded16:41
Q-FUNKincluding the vcons patch attached to 180742 ?16:42
Q-FUNKthere's a total of 3 patches against x86emu from Bart.  2 are attached to 140051 and 1 to 180742.16:43
tjaaltonthat's not included, the first two are16:43
Q-FUNKcan you check that third one, before you upload?16:43
tjaaltonbetter to test that separately?16:45
Q-FUNKhmm ok16:46
Q-FUNKI guess I'll make my PPA packages from your current upload.16:46
Q-FUNKwhich version is it?16:46
tjaaltonthe one that'll hit the archive in 10min :)16:47
Q-FUNKok :)16:49
Q-FUNKhow often is the PPA build queue processed, again?16:50
tjaaltonevery 30min/1h or so16:50
Q-FUNKsource was just accepted by PPA, but no binaries yet16:50
Q-FUNKah ok16:51
tjaaltonbryce: ok, xorg-server uploaded with those patches17:13
tjaaltonnow home ->17:14
Q-FUNKtjaalton: kiitos tästä.17:35
Q-FUNKone worry less for Hardy17:35
tjaaltonif it doesn't break anything :)17:52
tjaaltonbryce: maybe we should take a look at the fedora displayconf tool if dc-g isn't going to cut it anymore? looks like it has accumulated ~150 bugs so far17:55
bdmurraybryce: Is there a master bug for touchpad scrolling?17:57
tjaaltonbdmurray: ^^ :)17:58
tjaaltonbug 17341117:59
ubotuLaunchpad bug 173411 in xorg "[Hardy][Regression] Touchpad vertical scroll does not work" [Medium,Confirmed] https://launchpad.net/bugs/17341117:59
bdmurraytjaalton: thanks!18:00
brycetjaalton: really?  I looked at it a couple weeks ago but wasn't that impressed18:07
ubotuNew bug: #186899 in ubuntu "Scrolbar of my hp dv9646 laptop mouse doesn't work on Hardy (dup-of: 173411)" [Undecided,Triaged] https://launchpad.net/bugs/18689918:11
tjaaltonbryce: oh ok, what's it called? I'll dig it up to convince myself that it sucks :)18:13
brycesystem-config-display iirc18:13
brycehere are some (early) mockups of what they're working on to gain xrandr support - http://www.gnome.org/~clarkbw/designs/monitor-resolution-settings/18:14
tjaaltonyeah, that's the one18:15
bryceI think the layout that glatzor and mpt put together is a bit more usable.  I do want to have a graphical screen layout tool some day, but I've seen other prototypes I like better18:16
tjaaltonok I won't spend any time on that right now18:16
bryceso far, grandr's layout tools is the most interesting, however it takes up a lot of space18:16
tjaaltonbut we still need a tool which touches xorg.conf, imho18:16
brycehere's a screenshot:  http://www.redhat.com/magazine/014dec05/features/multihead/18:17
bryceyes I agree we need something which can manipulate xorg.conf, and I'm a bit uncertain about what to do there18:18
brycethere's three use cases I see18:18
bryce1.  bulletproof-x mode (a xrandr gui presumably won't cut it here)18:18
bryce2.  altering the Virtual settings to allow different layouts (but maybe this could simply be a script)18:19
bryce3.  general xorg.conf customization18:19
bryceI don't know though --- given my experience seeing how hard it's been for dcg to chase xorg.conf as it's format evolves, this seems like a really hard problem, and these three use cases don't represent as huge of an amount to gain, assuming people will be able to do more using xrandr now18:20
jcristaupyxf86config sounds nicer than shell to manipulate xorg.conf18:21
tjaaltonbryce: speaking of 1., do we want to get a recent -ati snapshot in? I'm tired of those r5xx bugs which fail to load vesa :)18:39
brycetjaalton: yeah probably a good idea; I've sort of lost track of where -ati is at since our last release18:39
tjaaltonbryce: deep in the snapshot-land :)18:40
tjaaltonor -jungle18:40
tjaaltonjcristau: I'll take a look at pyxf86config18:40
tjaaltonbryce: they do support accelerated 2D for r5xx, and maybe for r6xx too18:41
brycetjaalton: well, I'd like to avoid the situation we were in last time where we were putting out new -ati's right up until freeze...  the vesa issue is minor compared with some bugs we could risk unearthign18:42
tjaaltoncurrently r5xx-> can't get X up because of that, so it's not that minor :)18:42
brycetjaalton: maybe ask alex about any release plans for the month?18:42
tjaaltonyeah, good point18:43
tjaaltona coworker has a Thinkpad T-series with a recent ati card on it, so I could try some dailies on it every now and then18:45
bryceyes that's a really good idea18:45
bryceI think ScislaC may also be open to doing some testing, although usually he focuses on fglrx18:45
tjaaltonI'd like to personally see a machine failing to boot a livecd, otherwise it's much harder to fix anything18:48
bryceI think you might be the only person wishing for that ;-)18:49
tjaaltonhehe :)18:49
ubotuNew bug: #189343 in linux-restricted-modules-2.6.24 (restricted) "DRI doesn't work with fglrx 8.01" [Undecided,New] https://launchpad.net/bugs/18934319:31
ubotuNew bug: #187588 in xorg (main) "[hardy] wrong screen resolution on laptop HP nw8440" [Undecided,Incomplete] https://launchpad.net/bugs/18758820:32
brycetjaalton: I started that page on hardy driver status I mentioned the other day - https://wiki.ubuntu.com/X/Drivers21:37
bryceso far just -intel; going to do -fglrx after lunch21:38
bryceif you could, please review it and correct any inaccuracies - this is mostly taken from feedback from your testing, so I may have made mistakes in capturing it correctly21:38
tjaaltonbryce: ok, I'll have a look21:40
tjaaltonbryce: yep, looks good21:43
=== seb128_ is now known as seb128
bryceon to -fglrx22:11
tjaaltonfor some reason it seems to _require_ forcing 24bit mode on...22:12
brycewhat other issues?  I owe AMD a top 5 bug list, so if you have issues in mind I'll collect 'em22:14
tjaaltonDRI doesn't work for everyone etc22:15
tjaaltonlook at the l-r-m-2.6.24 bug list22:16
brycetjaalton: there doesn't seem to be that many fglrx errors in the lrm-2.6.24 bug list22:27
bryceabout a dozen22:27
tjaaltonright, but even more puzzling ones :)22:29
tjaaltonbut the fact is that not that many get past the broken-X phase22:30
tjaaltonI guess..22:30
tjaaltonthe bug list for 2.6.22 is more impressive22:30
brycecould be22:38
brycewill many of the 2.6.22 bugs still be relevant though?22:38
tjaaltonsome of them will22:42
tjaaltondon't know the percentage, but some of them are already running the latest driver(s)22:42
tjaaltonthose could be moved to .2422:42
bryceheya tormod23:13
tormodhi bryce23:14
brycehow things going tormod?23:15
tormodfine thanks. trying to not fall sick, flu all over Europe it seems.23:17
tormoddid you see my e-mail reply with another small patch?23:17
bryceI'll add it in now23:17
tormodyou can also remove the '/.git.*/' from -i I think, just -i removes all git/svn/etc23:18
bryceok done and pushed :-)23:20
tormodmy plans (some time) would be to rearrange the script in modules so it can be used as a shell library if needed.23:20
* bryce nods23:21
tormodfor instance build binaries, then change a few things for backports, build again (without downloading from git every time)23:21
bryceI got completely sidetracked by ubuntu-mobile stuff there around the holidays so haven't had time to work on the driver builder infrastructure more, but if/when I do, it'd be helpful to have the script modularized23:22
bryceI did take a shot at adding support for mesa before the holidays, but it never worked23:22
bryceI had the changes queued up in my tree (thus my procrastination merging more changes), but I think mesa just may be too complicated for it, so I just tossed that work for now.23:23
tormodis the ubuntu mesa maintained in git?23:25
brycejust xorg and xorg-server are in git for ubuntu so far23:29
tormodI guess it would be the next candidate.23:29
brycepossibly; although it's not a package we tend to do a lot of work on - I think we mostly just sync to debian23:30
tormodthat's the tendency for all xorg*, luckily23:30
bryceright.  xorg and xserver are the two main pieces where we have a significant amount of non-syncable / ubuntu-specific stuff23:31
bryceI've thought a bit that maybe one or two of the drivers would be next on the list, but typically what changes we make to drivers gets taken upstream swiftly so we rarely have more than a couple patches against them at a time23:32
brycetormod: hey did you see we got 100% caught up the other day on New bug triage for the major xorg bits? :-)23:33
bryce(well major aside from the binary drivers)23:33
tormodwow that's great23:34
brycetormod: http://people.ubuntu.com/~bryce/Plots/23:34
brycethings have crept up a bit since then but not much ;-)23:35
tormodlooks good :)23:35
tormodand displayconfig-gtk needs some love... any new plans for it?23:36
bryceindeed; I've been working on a replacement for it the last couple days23:36
tormodxrandr-aware I hope?23:37
brycemy code branch is at https://code.launchpad.net/gnome-control-center23:37
bryceit won't edit xorg.conf though, so we may still need a solution for that.23:38
tormodbtw, are we gonna update -ati soon, or wait for Debian (or for 6.8...)?23:38
brycetjaalton and I were just talking about that earlier23:38
tormodthe support for X1?00 cards would obsolete many vesa bugs...23:39
bryceit would be nice to not get stuck in a situation like last time where we were pushing new -ati's up until the last minute before release23:39
bryceI think tjaalton is going to check with alex about release plans in the near future23:39
brycetormod, have you tested against newish -ati snapshots?  How is it doing?23:40
tormodwell it just got better and better :)23:40
tormodworks well, and I ask people to test it whenever I can in bug reports.23:41
tormodI am a little afraid Alex doesn't have a release plan, as in planning wrt time23:42
ubotuNew bug: #189415 in xorg (main) "[Hardy] X serveur restart randomly with nvidia propriotary driver" [Undecided,Incomplete] https://launchpad.net/bugs/18941523:42
brycesince Hardy is an LTS release, it would be a bit uncomfortable shipping an -ati snapshot...23:43
tormodit seemed to settle and I was waiting for a release, then he merges atombios, same again, then he adds something else...23:44
brycehave you suggested to him that it would be good to put out a release before merging more stuff?23:45
tormodit would be better than 6.6.3 I guess ;)23:45
jcristauthe ati driver tends to have never-ending release candidate series these days23:45
tormodhmm no I haven't. I am maybe not the one to tell him. jcristau?23:46
jcristauyou could just pick whatever goes into F9 :)23:50
tormodtrue enough23:51

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