| === fabbione [~fabbione@port1845.ds1-khk.adsl.cybercity.dk] has joined #ubuntu-meeting | ||
| === mdz [~mdz@69-167-148-207.vnnyca.adelphia.net] has joined #ubuntu-meeting | ||
| fabbione | daniels: you here? | 10:25 |
|---|---|---|
| === ..[topic/#ubuntu-meeting:mdz] : Stuff | ||
| fabbione | we need to find a solution for that bug. | 10:26 |
| fabbione | simply because we do not agree within eachother | 10:26 |
| fabbione | i need to know kinda asap what to do | 10:26 |
| mdz | fabbione: what do you propose? | 10:27 |
| fabbione | 1) if we hit the via driver: we prompt for a warning and ask for the driver to use. We do not probe on via (never!) | 10:27 |
| === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting | ||
| fabbione | s/1)// | 10:27 |
| fabbione | the warning won't be translated (too bad but better than nothing) | 10:28 |
| mdz | if we ask, what do we present as the default? | 10:28 |
| mdz | because that is what everyone will use | 10:28 |
| fabbione | all the changes are contained in xserver | 10:28 |
| fabbione | mdz: we can default to vesa | 10:28 |
| fabbione | mdz: writing a proper warning isn't a problem | 10:28 |
| fabbione | mdz: explaning that the via driver is known to be buggy | 10:29 |
| mdz | if we default to vesa, we may as well not ask the question | 10:29 |
| mdz | if the user truly wants via, they can reconfigure | 10:29 |
| fabbione | mdz: i disagree | 10:29 |
| fabbione | the vesa driver fails | 10:29 |
| mdz | hopefully if they do so they will accept the consequences | 10:29 |
| fabbione | as much as the via does | 10:29 |
| fabbione | so between the 2 worst solutions i rather prefer the user to make a choise | 10:30 |
| mdz | it does? | 10:30 |
| fabbione | mdz: yes. it is the same reason why if we cannot detect the driver we ASK for it and we don't default to vesa anymore | 10:30 |
| mdz | knoppix falls back to vesa if it can't detect something better | 10:31 |
| mdz | and that has worked very well for me in the past | 10:31 |
| fabbione | well it is not good enough for everybody. there was a bug for it | 10:31 |
| fabbione | otherwise i would have left vesa as default | 10:32 |
| mdz | if we don't have a fallback to use when we can't detect, we are in trouble, because we will never be able to detect 100% | 10:32 |
| fabbione | we ask if we cannot detect | 10:33 |
| mdz | what was the bug with vesa? | 10:33 |
| fabbione | i need to check the bug number | 10:33 |
| fabbione | i can't remember it on the fly | 10:33 |
| mdz | do you remember what it was about? | 10:33 |
| fabbione | i am searching for it.... but basically the vesa driver didn't work at all on the card that was not detected | 10:35 |
| fabbione | i can't find the bug.. probably it was on the sounder mailing list | 10:37 |
| fabbione | but i am sure about it | 10:37 |
| fabbione | xfree86 (4.3.0.dfsg.1-6ubuntu5) warty; urgency=low | 10:38 |
| fabbione | * Do not ask for video card driver. If we cannot autodetect, we | 10:38 |
| fabbione | switch automatically to a sane default. | 10:38 |
| fabbione | xfree86 (4.3.0.dfsg.1-6ubuntu12) warty; urgency=low | 10:39 |
| fabbione | * Turned the video driver question back on if there is no autodetection. | 10:39 |
| fabbione | DEFAULT=vesa is not enough. | 10:39 |
| fabbione | it was somewhere on a mailing list | 10:39 |
| fabbione | there is no bug reference | 10:39 |
| daniels | fabbione: pong | 10:52 |
| daniels | hi, sorry | 10:52 |
| daniels | so, as far as I can tell, the status is: | 10:52 |
| daniels | a) via driver causes lockups, doesn't work on most machines | 10:52 |
| daniels | b) vesa doesn't cause lockups, but flat-out doesn't work on some machines | 10:52 |
| daniels | my position is that we shouldn't use the via driver at all, and should use vesa in all cases | 10:53 |
| daniels | but since we not only shouldn't use it to probe, but shouldn't use it at all, the fix needs to go in xserver-xfree86, which needs to either use vesa, or ask | 10:53 |
| daniels | the via driver is in the worst shape of all our drivers right now, afaict | 10:54 |
| mdz | ok | 11:01 |
| mdz | if we detect that we should use via, let's treat it the same as failed detection | 11:01 |
| mdz | the new user will just press enter, and hopefully that will work | 11:02 |
| mdz | the advanced user might select via, but then they will know what to do if it breaks | 11:02 |
| fabbione | mdz: ok so i will default to vesa and ask if we detect via | 11:04 |
| fabbione | in case of via i will still ban the probe | 11:04 |
| mdz | fabbione: yes. that is basically what you suggested, right? | 11:04 |
| fabbione | that means asking for resolution | 11:04 |
| fabbione | mdz: yes | 11:04 |
| fabbione | daniels: do you agree with this solution+ | 11:06 |
| fabbione | ? | 11:06 |
| daniels | fabbione: agreed | 11:06 |
| daniels | it seems like the best solution to me | 11:07 |
| fabbione | ok | 11:07 |
| fabbione | daniels: how safe is to use xresprobe vesa? | 11:07 |
| fabbione | i need to go and pick up my mother | 11:10 |
| fabbione | bbl | 11:10 |
| daniels | fabbione: it's perfectly safe | 11:12 |
| daniels | crt -> ddc probe -> ok | 11:12 |
| daniels | lcd -> no-op -> ask for res | 11:12 |
| daniels | pppconfig SHITS ME | 11:14 |
| fabbione | daniels: ok :-) | 11:51 |
| daniels | fabbione: see my comment on 1878 | 11:54 |
| fabbione | daniels: ok | 11:55 |
| fabbione | it's interesting to install in pt_BR language to test one bug ;) | 11:59 |
| fabbione | ok back to ubuntu-devel | 12:00 |
| fabbione | thanks guys | 12:00 |
| === fabbione [~fabbione@port1845.ds1-khk.adsl.cybercity.dk] has left #ubuntu-meeting [] | ||
| daniels | heh :) | 12:00 |
| === daniels [daniel@fooishbar.org] has left #ubuntu-meeting [] | ||
| === pitti_ [~martin@195.227.105.180] has joined #ubuntu-meeting | ||
| === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting | ||
| === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting | ||
| === pitti [~martin@195.227.105.180] has joined #ubuntu-meeting | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!