Bug 154732 - Monitor no longer detected in 10.1
Summary: Monitor no longer detected in 10.1
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Beta 6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 156075
  Show dependency treegraph
 
Reported: 2006-03-02 16:08 UTC by Chad Groneman
Modified: 2006-03-09 03:06 UTC (History)
2 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
output from hwinfo --monitor --log=xxx (206.38 KB, application/octet-stream)
2006-03-06 13:56 UTC, peter czanik
Details
output from hwinfo --monitor --log=xxx i386 (181.52 KB, application/octet-stream)
2006-03-06 14:43 UTC, peter czanik
Details
getsysinfo (129.49 KB, application/x-gzip)
2006-03-06 19:14 UTC, peter czanik
Details
getsysinfo for x86-64 (NEC Multisync LCD 1735NXM) (108.24 KB, application/x-gzip)
2006-03-07 01:09 UTC, Chad Groneman
Details
hwinfo --monitor --log=... x86-64 (NEC Monitor) (231.51 KB, text/x-log)
2006-03-07 01:12 UTC, Chad Groneman
Details
gzip of one of the y2log files (91.42 KB, application/x-gzip)
2006-03-08 15:56 UTC, Chad Groneman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chad Groneman 2006-03-02 16:08:27 UTC
Beginning around 10.1 beta4, my monitor was no longer automatically detected.  It is an NEC MultiSync LCD 1735NXM.  It used to be selectable in the list of monitors, but no longer is.  Now it is detected as a vesa monitor.

The monitor definitely is in 10.0, and I'm 95% sure it showed up correct with 10.1 beta3.  The monitor is not in the list with beta4 and beta6.
Comment 1 peter czanik 2006-03-03 08:42:46 UTC
I have the same problem with a ViewSonic Professional Series P90f
Comment 2 Marcus Schaefer 2006-03-06 13:33:20 UTC
If you don't mind provide the information from

  hwinfo --monitor

from 10.1 of course

Thanks
Comment 3 Steffen Winterfeldt 2006-03-06 13:46:21 UTC
I would need the log of 'hwinfo --monitor --log=xxx', actually.
Comment 4 peter czanik 2006-03-06 13:56:25 UTC
Created attachment 71362 [details]
output from hwinfo --monitor --log=xxx
Comment 5 Steffen Winterfeldt 2006-03-06 14:05:44 UTC
Uuuh, that is powerpc. Chad, you are using ppc as well, or a more common
i386-like machine?

Peter, you're sure it worked before beta 4? If so, could you attach the
same log where it detected the monitor successfully?
Comment 6 peter czanik 2006-03-06 14:42:24 UTC
I don't have earlier betas any more, but as far as I can remember, it worked earlier.

On my i386 using the same monitor I could not get this far in installation (some kernel trouble), but hwinfo seems to have correct info. I'll attach it.
Comment 7 peter czanik 2006-03-06 14:43:09 UTC
Created attachment 71376 [details]
output from hwinfo --monitor --log=xxx i386
Comment 8 Chad Groneman 2006-03-06 15:14:06 UTC
I am using an x86-64.  I'll attach my logs when I get home from work.
Comment 9 Steffen Winterfeldt 2006-03-06 15:20:21 UTC
Peter, please run getsysinfo and attach it.
Comment 10 peter czanik 2006-03-06 19:14:05 UTC
Created attachment 71449 [details]
getsysinfo
Comment 11 Chad Groneman 2006-03-07 01:09:07 UTC
Created attachment 71493 [details]
getsysinfo for x86-64 (NEC Multisync LCD 1735NXM)
Comment 12 Chad Groneman 2006-03-07 01:12:07 UTC
Created attachment 71494 [details]
hwinfo --monitor --log=... x86-64 (NEC Monitor)

It looks to me like this does detect the monitor correctly, but it doesn't show up in sax2 that way.
Comment 13 Steffen Winterfeldt 2006-03-08 13:58:50 UTC
Ok, then this is something completely different.

I've splitted the bug up. Lets track the sax2 issue that Chad has here
and the ppc issue with hwinfo that Peter found in bug 156075.
Comment 14 Chad Groneman 2006-03-08 14:21:51 UTC
Interestingly, Sax2 does now detect my monitor as what it really is.  Let me do a re-install to verify that my problem happens again.  I'll aim to have that done by tomorrow.
Comment 15 Marcus Schaefer 2006-03-08 15:37:25 UTC
So it works for you now ? Please file a new bug report if you get that
problem again
Comment 16 Chad Groneman 2006-03-08 15:53:57 UTC
I think I may not have to reinstall, but I'll do it again anyway.  Let me know if you want a new bug or just re-open this one.  From the y2log:

2006-03-01 18:50:07 <1> chad2(4136) [Interpreter] x11/x11Dialog.ycp:280 Calling YaST client x11_proposal (arguments: ["MakeProposal", $["force_reset":false, "language_changed":false]])
2006-03-01 18:50:07 <1> chad2(4136) [YCP] clients/x11_proposal.ycp:73 Loading library cache...
2006-03-01 18:50:21 <1> chad2(4136) [YCP] clients/x11_proposal.ycp:79 Reading libsax cache data...
2006-03-01 18:50:21 <1> chad2(4136) [Interpreter] x11/x11Dialog.ycp:280 Called YaST client returned: $["links":["sax-monitor", "sax-resolution", "sax-displaysize", "sax-colors", "sax-3d", "sax-ext-vga", "sax-test"], "preformatted_proposal":"<ul><li>Graphics card: NVidia GeForce 6600 GT</li><li>Monitor: <a href=\"sax-monitor\">--> VESA 1280X1024@60HZ</a> (<a href=\"sax-displaysize\">17 Inches, Aspect 5:4</a>) - (<a href=\"sax-resolution\">1280x1024</a>)</li><li>Colordepth: <a href=\"sax-colors\">24</a> Bit (16.7 Mio. Colors)</li><li><a href=\"sax-test\">Test the Configuration</a></li></ul>"]
Comment 17 Chad Groneman 2006-03-08 15:56:52 UTC
Created attachment 71795 [details]
gzip of one of the y2log files

The section mentioned above begins on line 27631.
Comment 18 Chad Groneman 2006-03-09 03:06:38 UTC
Hmm..  I reinstalled and it detected just fine this time.  Not sure why it didn't the first time.  I'll keep my eyes open to see if it happens again.