![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
In general, the X sync rates have no relation to text display. However, if can happen that starting and stopping X leaves the monitor in some state which is unsuitable for text display, especially when using a "multisync" monitor which has a mechanical relay which can be heard making a "click" or "clunk" noise when the display mode is changed. One trick with Linux to force a monitor to get control of itself on boot is to specify "vga=ask" on the kernel boot line and then to request a probe, even if you then pick the standard 80x25 mode. This is useful for setting a VGA monochrome display so you can read it, for example. Be aware that any monitor which has significant visible instability is a potential fire hazard, no matter how remote the chance of it actually bursting into flames, and should not be left turned on while unattended. The most common failure mode is internal charring and a horrendous burning odor, but not real flames as long as you are there to turn it off. -- Mike On 2000-05-02 at 08:50 -0400, Tewksbury, Chuck wrote: > Newbie question here... does the monitor rate you select in X affect the > command prompt interface? > > I have a monitor that is shaking like a leaf in certain modes in X but it > also shakes in text mode... so I am thinking it is not an X configuration > issue. - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |