| [19:06] <johanbr> bryce: About the Radeon lockup I asked you about a few days ago, there's a bug filed now (bug #234811). Hardy locks up completely when running 1440x900. Gutsy works fine. | |
| [19:06] <ubottu> Launchpad bug 234811 in xorg "[Hardy] system freezes after setting resolution to 1440 x 900 with Radeon 7500 graphics card, when using DVI output, Acer AL1916W monitor" [Undecided,New] https://launchpad.net/bugs/234811 | |
| [19:17] <bryce> johanbr: ok thanks, looking | |
| [19:23] <tseliot> tjaalton: the drivers are ready however I would like to know which versioning scheme we should adopt. For example shall we put something like this in the changelog? nvidia-graphics-drivers-2.6.24 (2.6.24.500-500.30) intrepid; urgency=low | |
| [19:25] <tseliot> I have adopted Debian's name schemes | |
| [19:33] <tjaalton> tseliot: no need for the kernel version being there.. | |
| [19:34] <tjaalton> better use the nvidia versions like debian | |
| [19:38] <johanbr> bryce: Is it really possible to do anything (apart from maybe SysReq traces) when the machine locks up completely? | |
| [19:43] <tseliot> tjaalton: one of the packages will be named nvidia-glx and should replace nvidia-glx-new. We have to make sure that we don't break dist-upgrades from Hardy to Intrepid therefore | |
| [19:44] <tseliot> we should be careful about the version and about the control file | |
| [19:45] <tseliot> maybe adding something like this to nvidia-glx would solve part of the problem: | |
| [19:45] <tjaalton> tseliot: of course, but the version number is irrelevant if it Replaces another package | |
| [19:45] <tseliot> Conflicts: nvidia-glx-src, nvidia-xconfig, nvidia-glx | |
| [19:45] <tseliot> Replaces: nvidia-glx-src, nvidia-glx (<< 170.12+2.6.24.500-500.24) | |
| [19:45] <tseliot> Provides: nvidia-glx, xserver-xorg-video-2 | |
| [19:45] <tseliot> tjaalton: yes, of course | |
| === federico3 is now known as f_shower | |
| [19:47] <tseliot> tjaalton: this wouldn't automatically replace nvidia-glx-new with nvidia-glx in case of upgrade though | |
| [19:48] <tjaalton> missing -new | |
| [19:49] <tjaalton> oh | |
| [19:49] <tjaalton> I thought it would make sense to rename current nvidia-glx as -legacy-96xx like in debian | |
| [19:50] <tseliot> and I did it. I'm talking about nvidia-glx-new | |
| [19:50] <tseliot> all the three flavours provide nvidia-glx | |
| [19:50] <tseliot> maybe this is confusing you? | |
| [19:50] <tjaalton> why?-) | |
| [19:51] <tjaalton> why do they provide nvidia-glx | |
| [19:51] <tseliot> so that they conflict with each other | |
| [19:51] <tjaalton> and it should replace nvidia-glx-new, not nvidia-glx | |
| [19:51] <tseliot> nvidia-glx-new becomes nvidia-glx | |
| [19:51] <tseliot> nvidia-glx becomes nvidia-glx-legacy-96xx | |
| [19:52] <tjaalton> right | |
| [19:52] <tseliot> nvidia-glx-legacy becomes nvidia-glx-legacy-71xx | |
| [19:52] <tjaalton> but the lines from control are wrong | |
| [19:53] <tseliot> those lines, which I haven't changed yet, belong to what used to be the nvidia-glx-new-envy package | |
| [19:53] <tseliot> any suggestions for the new control file? | |
| [19:54] <tjaalton> make it ready first and I'll review it then | |
| === f_shower is now known as federico3 | |
| [20:47] <bryce> johanbr: yeah ssh in from another box and attach to the process | |
| [20:47] <bryce> johanbr: see wiki.ubuntu.com/X/Backtracing for directions | |
| [20:50] <johanbr> bryce: The network dies too. | |
| [20:51] <bryce> hmm, then the issue may be in the kernel | |
| [20:52] <johanbr> An all-Gutsy installation works, but Hardy with the Gutsy kernel hangs, so it doesn't appear to be in the kernel. | |
| [20:53] <bryce> in any case, without a backtrace there is not more troubleshooting that can be done on it | |
| [20:54] <bryce> make sure you're using a wired connection | |
| [20:55] <johanbr> Is there a way of installing the Gutsy version of the radeon driver on Hardy, or has the X server changed too much? | |
| [20:57] <bryce> well, you could apt-get the source and rebuild it against your xserver. It ought to work ok I should think. | |
| [20:57] <johanbr> Alright, I'll walk him through that and we'll see what happens. Thanks for the help. | |
| [20:57] <bryce> sure, good luck | |
| [21:11] <bryce> mesa 7.1 rc1 was announced :-) | |
| [21:18] <tjaalton> yep, finally :) | |
| [21:24] <bryce> tjaalton: have you ever tried device Option "DRI2" ? | |
| [21:28] <tjaalton> bryce: no.. haven't built snapshots in a while | |
| [22:04] <tjaalton> seems that DRI2 is not happening until the TTM/GEM mess is settled | |
| [22:04] <bryce> :-/ | |
| [22:04] <bryce> I was afraid of that | |
| [22:24] <kushal1> jedimind, looking back, I don't know what I was thinking trying to add everything by hand. I cannot even believe I added over 60 of those by hand. I wish I could drag and drop using default settings | |
| [22:37] <kushal1> Hello, I am making a home DVD with about 200 short clips using Devede. I have already added about 60 files one at a time but my hand is starting to hurt. It is also really boring. Is there a way for me to add a bunch of mpg files on to the devede list like a batch or drag and drop? please let me know. thanks (please answer) | |
| [22:38] <bryce> kushal1: I think you may be asking on the wrong channel | |
| [22:38] <bryce> kushal1: this channel is only for discussing X11 | |
| [22:44] <kushal1> sorry, bryce | |