Haven't tried 9.1 yet, just the evaluation CD. Two show stoppers so far: 1. The eval CD (just like 9.0) misidentifies my monitor and so misconfigures X with out of range frequencies => blank screen. I have a Samsung SyncMaster 957MB. 9.0 misidentified this as a SyncMaster 4S, BTW. 8.2 had no problems with this monitor. 2. The dpt_i2o.o driver in 9.0 is broken (the version in 8.2 works flawlessly). dpt_i2o.o is not included in the 9.1 eval CD, so I can't test. Knoppix has no problem with either of my monitor or my RAID controller. Best regards, Mark "still on 8.2" -- _____________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.rnome.com
On Tue, 2004-05-04 at 20:24, L. Mark Stone wrote:
1. The eval CD (just like 9.0) misidentifies my monitor and so misconfigures X with out of range frequencies => blank screen. I have a Samsung SyncMaster 957MB. 9.0 misidentified this as a SyncMaster 4S, BTW. 8.2 had no problems with this monitor.
Not sure how to fix your problem but I would like to mention something. For years, every single linux distro I tried, with the exception of Knoppix, misdetected my monitor (LG Studioworks 55V). I e-mailed feedback (when the e-mail option was still around) and gave them my monitor's specs, and in the next release (9.0) my monitor was detected and setup correctly. Kind regards -- Hans du Plooy Newington Consulting Services hansdp at newingtoncs dot co dot za
On Thu, 2004-05-06 at 03:01, Hans du Plooy wrote:
On Tue, 2004-05-04 at 20:24, L. Mark Stone wrote:
1. The eval CD (just like 9.0) misidentifies my monitor and so misconfigures X with out of range frequencies => blank screen. I have a Samsung SyncMaster 957MB. 9.0 misidentified this as a SyncMaster 4S, BTW. 8.2 had no problems with this monitor.
Not sure how to fix your problem but I would like to mention something. For years, every single linux distro I tried, with the exception of Knoppix, misdetected my monitor (LG Studioworks 55V). I e-mailed feedback (when the e-mail option was still around) and gave them my monitor's specs, and in the next release (9.0) my monitor was detected and setup correctly.
I wonder what would be invloved in editing the monitor database in SuSE so that my Sony Multiscan 110 GS actually shows up and configs correctly. Mike
Mike McMullin wrote:
On Thu, 2004-05-06 at 03:01, Hans du Plooy wrote:
On Tue, 2004-05-04 at 20:24, L. Mark Stone wrote:
1. The eval CD (just like 9.0) misidentifies my monitor and so misconfigures X with out of range frequencies => blank screen. I have a Samsung SyncMaster 957MB. 9.0 misidentified this as a SyncMaster 4S, BTW. 8.2 had no problems with this monitor.
Not sure how to fix your problem but I would like to mention something. For years, every single linux distro I tried, with the exception of Knoppix, misdetected my monitor (LG Studioworks 55V). I e-mailed feedback (when the e-mail option was still around) and gave them my monitor's specs, and in the next release (9.0) my monitor was detected and setup correctly.
I wonder what would be invloved in editing the monitor database in SuSE so that my Sony Multiscan 110 GS actually shows up and configs correctly.
Mike
I had a similar problem with 9.0 and a Sony Tritron monitor. After setting upa system using an old monitor which 9.0 did tetect and correctly configure, I gave the system back to the owner for whom I was converting a win only box to a dual boot box. When he took it home and connected it to his monitor, the Sony, 9.0 refiesed to run in graphics mode. So he brought me the entire system to play with. I connected everything up and booted to failsafe mode and then ran sax2 -l. It immediately presented me with a 640 x 480 blue screen with tux in the corner. From there I had to work HARD to get the desired screen resolution as YaST just didn't want to cooperate, at all. But after roughly an hour of fussing with it I got it to behave nicely! (applause) Two things however struct me as odd. When I got into YaST and looked at the choice of monitor, YaST had already - prior to my doing anything to it - properly identified the monitor, a Sony Trinitron HMD-A200 AND the exact H (30 - 7- kHz) & V (48 - 120Hz) deflection frequencies for it! Yet, it had consistently REFUSED to boot into the gui. After my fooling around and setting the display to 1024 x 768 with 24 bit color it repeatedly booted into the gui. Seems VERY odd to me. Does this give you any ideas or help? dave
Mike McMullin wrote:
I wonder what would be invloved in editing the monitor database in SuSE so that my Sony Multiscan 110 GS actually shows up and configs I would really like to know also. I asked a similar question on thread [SLE] 3D Acceleration for Radeon 9200 in SUSE 9.0 Professional and one person said it was /usr/X11R6/lib/sax/api/data/cdb/Monitors but it seems to only put the monitor on the list for manual selection. The monitor still was not automatically detected. If anyone knows how to tamper with the database used for detection, I guess there are at least 2 of us who would like to know.
Damon Register
participants (5)
-
Damon Register -
David Johanson -
Hans du Plooy -
L. Mark Stone -
Mike McMullin