|
Bugzilla – Full Text Bug Listing |
| Summary: | sax2: NoModelines profile not working properly | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Stefan Dirsch <sndirsch> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mrmazda |
| Version: | RC 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | SaX.log | ||
|
Description
Stefan Dirsch
2007-09-27 14:18:34 UTC
Created attachment 175203 [details]
SaX.log
BTW, there are two entries in Driver.map for nv driver as you can see. :-( I also don't understand why nv uses the NVidia profile ... # /.../ # Mapping table for X11 driver to profile # ===================================================== # Driver Name | Profile # ----------------------------------------------------- nv : Depth24,NVidia nvidia : Depth24,NVidia radeon : Depth24,Radeon i810 : Depth24,NoDDC,LinearAlloc sis : SiS,Depth24 fglrx : FireGL tseng : VideoRAM intel : Depth24,Intel nv : NoModelines fbdev : NoModelines the gui may add a modeline depending on the gui actions. If the added modeline is valid I don't see a reason why this is a bug in sax2. If the fglrx driver can't handle correct and valid modelines fix the driver ;) If I remove adding the modeline by the gui action I would solve your problem and re-open another one. So I'm sorry this is a wontfix I do not understand your comment, Marcus. I thought the purpose of NoModelines profile was to *not* generate any Modelines in xorg.conf at all ? Am I that wrong here? At least then the name of this profile would be rather misleading. And for a standard mode like 1280x1024 really no modeline is required. Which is generated even with "sax2 -r -a", so no GUI action is involved at all. Not to forget comment #2 ... * in reply to comment #2: if you have nv in use and install the binary nvidia driver you need to detect that this has happened. The NVidia profile checks if the real nvidia driver is installed and if not it remains to use the nv driver. Anyway the driver map is wrong there are two nv entries in it. Don't know who added that... changed it * in reply to comment #4: the profile does what it should do but the GUI can add modelines if needed. I added a check to the variables set in the profile file package available on BS Thanks for explanation and fixing this issue, Marcus! > Anyway the driver map is wrong there are two nv entries in it. Don't know > who added that... changed it ------------------------------------------------------------------- Thu Apr 26 10:11:26 CEST 2007 - ms@suse.de - disabled modeline calculation for nv driver (#230961) Thanks for merging the two nv driver lines in Driver.map. For some reasons the fix doesn't work for me. The Modeline is still generated. :-( I've tested the current SaX2 version from the buildsystem. * Fr Sep 28 2007 ms@suse.de - fixed modeline trigger in GUI (#328939) I can provide a machine for you for testing. Just set to NEEDINFO. :-) really fixed and tested now Indeed. Thanks a lot! |