philips 190B4C monitor trouble

scary · n00b Joined: 17 Apr 2004 Posts: 47

hi all,
I cannot manage to get my philips 19" lcd monitor to work properly. if I start X, the screen becomes black and the monitor tells me to switch to a supported resolution, such as 1280x1024@60Hz.
I put the refresh rates found on the monitor manual in XF86Config and also tried adding a "Modeline" string to the config file calculating it on some website. I've also erased every mode apart from 1280x1024, with no success at all. The problem also appears when I try to use a vesafb console, following the bootsplash guide found on this forum caused the screen to get black suddenly after the lilo prompt, even if I give the boot parameter vga=normal ...
the strange thing is, during gentoo setup from LiveCD, the autoconfigurator managed to get a higher resolution in the console. Any ideas?

Radeon 7200 VIVO, Philips 190B4CG. I can post my XF86Config or XFree86.0.log or whatever else is needed. thanks!

vdboor · Posted: Sat Apr 17, 2004 3:29 pm Post subject:

You could try to run xf86cfg, and xf86config. I did this to find out how a LCD screen needed to be configured, and it worked for me.

_________________
The best way to accelerate a windows server is by 9.81M/S²
Linux user #311670 and Yet Another Perl Programmer
[ screenies | Coding on KMess ]

scary · n00b Joined: 17 Apr 2004 Posts: 47

actually I used xf86config to create the current XF86Config I was using and I've just tried xf86cfg, which brought me to the same problem, black screen and "please switch to a supported video mode, such as 1280x1024@60Hz.

do lcd monitors need special parameters ? I just put the refresh rates found on the manual, nothing seems to be different from a normal crt monitor conf.. am I missing something ?

vdboor · Posted: Sat Apr 17, 2004 7:59 pm Post subject:

yes, LCD monitors often work at 60Hz only. (you won't notice it's 60hz, because an lcd screen doesn't flicker, the pixels jjust change)

You can try to omit a lot of settings. X detects quite a lot by default.

for example;
(these settings were based on xf86cfg, with an tft flatscreen)

Anime_Fan · Posted: Sat Apr 17, 2004 8:59 pm Post subject:

You can also try forcing a 60Hz refresh rate... Your GFX card probably can pump out a much higher refresh rate, so it tries to by default.

scary · n00b Joined: 17 Apr 2004 Posts: 47

thanks for helping,, actually neither removing config strings from XF86Config nor adding a /60Hz in the Modes section solved my problem. It's always the same thing, to think that X even reads EDID data from the monitor through the radeon driver and recognizes it .. what should I do ? could posting XFree86.log help?

scary · n00b Joined: 17 Apr 2004 Posts: 47

Actually by adding to the video card section a
Option "DDCMode" "on"
I managed to run X ... only now when I try to go back to console the same problem comes up again so this time I'm stuck on X after I start it !

And I still cannot make the framebuffer console work, neither with the standard vesafb driver nor with the radeonfb driver....

vdboor · Posted: Mon Apr 19, 2004 8:43 pm Post subject:

IF you're really desparate, you should try out the fbdev driver. It runs X through the framebuffer device, (and only with the resolution of your framebuffer), but I think it's easy to fix this.

scary · n00b Joined: 17 Apr 2004 Posts: 47

I don't really understand how is this going to solve my X problems since not even the framebuffer console is working ? I'll give it a try anyway.. is this supposed to fix the problem when I switch from console to X ? thanks for your help anyway !

vdboor

No, the fbdev driver only works if your framebuffer is working. It runs X with the same settings as your framebuffer has. In my case, this causes tv-out to work all of a sudden.