/srv/irclogs.ubuntu.com/2007/11/02/#ubuntu-x.txt

Q-FUNKbryce_: did OLPC's Bernie manage to find you?13:36
bryce_yes, we chatted a bit13:37
bryce_more about inkscape than -amd though13:37
Q-FUNKah13:37
bryce_I talked with ogra about -amd briefly as well - he said "the current -amd fails to work for 80% of the people, and that we should go to the previous -amd, which worked fine."13:38
bryce_I asked him if he'd talked to you about this, and he said no, so I told him he needed to speak with you about it first.13:38
Q-FUNKit's not a question of previous -amd as much as current X13:38
bryce_it was the first I'd heard of an issue13:38
Q-FUNKogra fails to see the big picture:  X since 7.2 leaves many drivers that work just fine with 7.1 in the dust, -amd being just one of many.13:39
Q-FUNKit gets even worse with 7.313:40
Q-FUNKmodularisation allows upstream X to crank out new releases of the core more often, but this comes at the price of chipset drivers requiring more frequent updates.13:41
Q-FUNKfor widespread drivers that sometimes include paid coders from the manufacturer, such as ati, mga, intel and nvdia, this works well.13:42
Q-FUNKfor all other chipsets, their stability falls behind one API/ABI chunk at  atime.13:42
* bryce_ nods13:44
bryce_so it's a case that even if we went back to the previous -amd, it'd still be broken?13:44
bryce_that is sort of what I suspected13:45
Q-FUNKyup13:49
Gadibryce: ping13:50
Q-FUNKI tried going back to really old CVS snapshots and I get the same result:  the X core simply has changed in too many ways startign with 7.213:50
Q-FUNK7.2 was sort-of compatible with 7.1, but 7.3 definitely isn't13:51
Q-FUNKbryce_: Gadi here has his ThinCan with him at UDS13:51
Q-FUNKbryce_: can you introduce him to Bernie?13:52
Q-FUNKbryce_: and sbalneav is the one that merged -amd support for edubuntu. he has a ThinCan too, though not with him at UDS13:53
* Gadi is sitting along the window with Dave Trask atm13:54
Gadiand I have to leave in a few mins13:54
Gadiso....13:54
Q-FUNKoh...13:55
Gadii am happy to hand off the thincan13:55
GadiI am meeting up with the rest of the LTSP gang in Maine tomorrow13:55
Gadiand can get it back then13:55
Q-FUNKok13:55
Q-FUNKthat could work well too13:55
Q-FUNKdoes the LTSP gang ever gather up in EU?13:57
bryce_heya sbalneav13:58
bryce_I've got a session starting now but think I'm free after13:58
tepsipakkiQ-FUNK: in what way is the -amd driver broken atm?14:02
tepsipakkimajority of the drivers have not changed in between xserver releases, so I wonder why those still work14:03
sbalneavHey bryce_ 14:04
Q-FUNKtepsipakki: auto-configuration fails on recent X versions that support it. vice-versa, on recent X, ctrl-alt-Fx fails to change console.14:04
sbalneavyeah, changing the console hangs up the whole box.14:04
Q-FUNKwell, i get the exact same problem on an unrelated driver -siliconmotion  14:05
Q-FUNKhere, it doesn't hang the whole box, but I cannot get an image back after.  I can still ssh into the box, thoguh.14:06
sbalneavAh, well, when I say "hang", I haven't tested to see if I can still ssh in.  Keyboard becomes unresposive, however.14:07
Q-FUNKmy problems with -siliconmotion are described in a bug I filed on LP14:07
Q-FUNKthe problems described by sbalneav with -amd are similar to those I experience with -siliconmotion. those problems did not exist on Feisty, which has an older X release.14:07
Q-FUNKotherwise, almost the same source code, in both cases.14:08
Gadiok14:09
tepsipakkiQ-FUNK: ok14:09
GadiI gave the thincan to Dave Trask14:09
Q-FUNKI've had to pin xserver-xorg-core and xserver-xorg-dev to 7.1 in both cases14:09
Gadibryce_: you're welcome to it for the day, but please give it back to him or another LTSP person headed to Maine14:09
tepsipakkiactually there is a problem with -sis that it hangs on logout14:10
tepsipakkiusing feisty14:10
Q-FUNK7.2 works but you cannot change console and if the X built-in screensaver kicks-in, you can never recover video.14:10
Q-FUNKhang on logout is also something i experience with siliconmotion, if I let it upgrade to gutsy14:10
Q-FUNK7.3 is even worse.14:11
Q-FUNKsomething tells me that -amd might need a partial upgrade to work with the new XrandR14:11
Q-FUNKit might also need a shuffle of the BIOS env parts, as decribed in the bug report for -amd14:12
Q-FUNKI wouldn't be surprised if other drivers need a similar cleanup14:13
bryce_that seems likely14:23
bryce_do you have additional information on specifics of what changes are needed?14:23
bryce_Q-FUNK: btw, I'm going to be in and out today so don't think I should take the thincam (not really sure even how to use it)14:27
sbalneavbryce_: if it would help, I'd be happy to lend you my thincan, and ship it to you, when I get back to winnipeg.14:32
bryce_I suspect I need the high level overview first; I've never heard of 'thincan' before14:33
Q-FUNKbryce_: a thin client based on the AMD Geode chipset.15:13
Q-FUNKworks well with LTSP, except for the new bugs introduced by X >=7.215:15
Q-FUNKbryce_: dtrask has the thincan left by Gadi, if you need it15:16
Q-FUNKtepsipakki: alternately, since you live here, it could be very easy for me to loan you one, if you feel like working on it.15:16
tepsipakkiQ-FUNK: hmm :)15:26
mvohello! what is the current plan for xlib with xcb support? is there any timeline for this yet? we want to switch to compiz 0.7 and it will be a requirement there15:27
tepsipakkiQ-FUNK: I'm not sure if I'd be able to find the problem though15:28
tepsipakkimvo: uploaded!15:28
mvorock!15:28
* mvo hugs tepsipakki15:28
tepsipakkilibx11-xcb* is sitting in new :)15:28
bryce_mvo, as soon as the xserver build is through, you should be good to go15:28
* tepsipakki hugs mvo back15:28
tepsipakkibryce_: it doesn't really need the server, it's just a lib :)15:30
Q-FUNK:)15:32
bryce_ah15:33
bryce_Q-FUNK: do you have a detailed write-up of the work needed for -amd?15:44
Q-FUNKthe details provided by Anti in the bug are as close to a checklist as I've got15:48
bryce_hmm, I don't remember the bug id offhand15:58
bryce_ok, going out for a bit.  bbl15:58
ubotuNew bug: #159556 in xorg-server (main) "[Hardy] xserver-xorg-core incorrectly conflicting with xserver-xorg-video?" [Undecided,New] https://launchpad.net/bugs/15955616:36
tepsipakkihah16:38
tepsipakkithat bug ^^16:38
tepsipakkisomeone actually running hardy16:38
_berniehello19:23
Q-FUNKsbalneav: I found Bernie :)19:24
_bernieanythink I can do...19:24
_bernieare you maintainers of amd_drv in Xorg?19:25
Q-FUNK_bernie: Jordan said that you might be able to help us bring -amd in line with X.org 7.3 specs19:25
_berniewe currently just rebuild it with no patches19:25
Q-FUNKwe currently have a situation where it fails autoconfiguration on recent X releases.19:26
_berniebut we don't use Xorg as upstream19:26
Q-FUNKyou have oyur own fork?19:26
_berniehttp://dev.laptop.org/git?p=xf86-amd-devel;a=summary19:27
_bernieunfortunately19:27
_berniejordan says the version on fd.o is not suitable for us19:27
Q-FUNKhttps://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amd/+bug/14005119:27
_bernieprobably some DCON changes, I never got around to diff them.19:27
ubotuLaunchpad bug 140051 in xserver-xorg-video-amd "amd driver fails to autoconfigure" [High,Triaged] 19:27
Q-FUNKyes, DCON.  we don't have those 19:28
_bernieif you have commit access on the fd.o git repository, it would be nice to pull from us and resync the source19:28
_bernieI hate forks19:28
Q-FUNKI cannot sync as-is19:28
Q-FUNKyou guys have too many OLPC-specific changes that would need to be #ifdef'ed19:29
_bernieI had that segfault too!19:29
_bernieI can't remember how I fixed it though... just a moment19:29
Q-FUNKthat's why Jordan has been acting as a sort of gate keeper between both trees19:29
Q-FUNKif/when you get around haivng proper #ifdef on all OLPC-specific stuff, we 'd love to merge trees and maintian everything at f.d.org19:30
_bernieare you sure you're building with 100% 7.3 headers?19:30
Q-FUNKyup19:30
Q-FUNKbut 7.2 already is problematic19:30
_bernieI had to delete my /usr/include/X11 and /usr/include/xorg dirs at some point when I was testing stuff locally19:30
Q-FUNKbuilding against anything more recent than 7.1 cuases all sorts of issues19:30
_bernieI can't test on anything but OLPC. I have no other amd boards... this is why I can't easily help making our patches available for the fd.o version19:31
_bernieI build against 7.3 and everything is fine19:31
Q-FUNKI think that the most pressing issue is to fix auto-configuration. as far as we can tell, this requires shuffling BIOS environmnet parsing around.19:32
_bernieso the fix is somewhere in our tree19:32
_berniehow about cherry-picking the easy to merge patches and retry?19:32
Q-FUNK_bernie: please look for dtrask at UDS. he has a more generic board made with an LX on it.  it's the same that LTSP guys have been playing with.19:32
_bernieargh, I'm already back at One Cambridge Center19:33
Q-FUNKoh19:33
_bernieI'm looking for bits where we explicitly require DCON in our driver19:34
_bernieI don't see them... We always check for it before any access as far as I see.19:34
_berniewe're nearby a big feature freeze. that would be today.19:35
_bernieso maybe next week I could start submitting patches19:36
Q-FUNKlovely!19:36
_berniehave you being building from a pristine git's master?  Or do you have debian or ubuntu specific patches on top of it?19:37
Q-FUNKnothing debian/ubuntu specific19:38
Q-FUNKwe build against a pristine f.d.org tree19:38
_bernieI see there are _several_ patches on fd.o19:43
_bernietry pulling from our git repo and see what happens19:43
_bernieif your bug goes away, then you know where to look19:43
Q-FUNKon fd.o ?19:43
Q-FUNKthe current 2.7.7.3 includes all the latest.19:43
Q-FUNK...except for OLPC additions19:44
Q-FUNKgit head on fd.o = 2.7.7.3 19:44
_bernieI mean, try building the source from git://dev.laptop.org/xf86-amd-devel19:46
Q-FUNKI just diffed it20:02
Q-FUNKvery few differences, oddly enough20:02
Q-FUNKmostly DCON stuff20:02
_bernielooking20:03
Q-FUNKI also added that diff to the bug.20:07
Q-FUNKand includes that have been either eliminated or shuffled around20:08
_bernieI don't see anything that would be clearly responsible for your particular segfault20:09
_berniewell, try building our driver and see what it does20:10
_berniecan you do a quick test?20:10
Q-FUNKsure20:12
Q-FUNKmidn you, you guys are using a fixed resolution with a config, aren't you?20:13
Q-FUNKI'm also wondering why you removed amd.h from so many files20:13
ubotuNew bug: #34146 in xserver-xorg-input-hyperpen (universe) "appearance of constant full pressure" [Medium,New] https://launchpad.net/bugs/3414620:32
_berniehttp://dev.laptop.org/git?p=xf86-amd-devel;a=commitdiff;h=1d6f6bdcb0aac722e50ac58ff94e4df5c5f0220b20:41
_berniedan williams says it caused a build error20:41
_bernieI recall something messing with _X_INLINE20:41
_berniehttp://dev.laptop.org/git?p=xf86-amd-devel;a=commitdiff;h=63d72f8c1ff1b7e534fc533a6aae8683e83fc0ca20:42
_bernie^^^ this was also a good idea20:42
_bernieQ-FUNK: yes, we hardcode the resolution in xorg.conf, since the LCD size is fixed.20:43
_berniebut we shouldn't. I'd like to get rid of xorg.conf alotgether20:43
Q-FUNKfor that, you'd need to manage to fix the above ubuntu bug :)20:44
ubotuNew bug: #159617 in xserver-xorg-input-hyperpen "tablet does not work" [Undecided,New] https://launchpad.net/bugs/15961720:45
_bernie:-/20:45
Q-FUNKbasically, BIOS parsing has to be cleaned up and parts of it shuffled around, for autoconfiguration to work.20:50
Q-FUNKour Anti did most of the ground work in his coments to the bug20:50
Q-FUNK_bernie: I get a big hard freeze with the olpc tree, as soon as X tries to load22:08

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