[09:41] what the.. why do I get a newly generated xorg.conf after a reboot. the old one works fine [09:42] happened on two machines, both using nvidia blob and both had their cards changed [09:45] physically? [09:46] nvidia ships an xorg.conf file munger; perhaps it runs automatically now, I donno. [09:46] tjaalton: btw, im running intrepid now, testing wacom. [09:46] no, it's the xorg.conf dexconf would produce [09:47] and I've seen bugreports where people complain that they need to reinstall the driver after every boot [09:47] I think bp-x kicks in somehow [09:51] yep, definately bp-x [09:55] oh right, no extra power on the card [09:55] *cable connected [09:56] but the other machine still ran dexconf for no reason [10:03] bah, no time to debug it now [11:02] I tried to test various intel drivers from .deb packages and git repos and how I can't get direct rendering to work around [11:03] "glxinfo | grep direct" says direct rendering is disabled [11:03] how can I reinstall x.org and all drivers etc so make sure I get the normal hardy xorg+driver again ?? [12:50] guys, isn't there any way we can get -all to depend on -geode rather than -amd for hardy.1 ? [12:50] I know thta hardy.1 froze a while back and is currently being rollled out in hardy-updates, but still... [12:51] as much as I try, the only way to fix this geode issue permanently is to make -all stop depending on -amd and to use my new package structure, where the symbolic link is in the transitional -amd [16:46] http://q-funk.blogspot.com/2008/06/kuradne-geode-draiveri.html [20:06] bryce: yesterday was the deadline for the specs on launchpad. How does it work? Do we need someone to approve the spec?