ubuntu 9.04 Starý CRT monitor, nvidia - jak nastavit rozlišení a refresh

Googlujte použití příkazu "xrandr".

Snažil jsme se, ale našel jsme řešení jen pro více monitorů a nevím co by mi z toho pomohlo..

Problém je (jak už naznačil rádce z abclinuxu) v tom, že z nějakého důvodu tvůj monitor nedodává (nebo správně nedodává) DDC informace (to ostatně potvrzuješ i sám, že jsi to ve windows nastavoval ručně)

Zde máš troubleshooting problémů s DDC, krok za krokem (předpokládám, že umíš anglicky): https://wiki.ubuntu.com/X/Troubleshooting/Resoluti on

Neumím :)

hm.. tak to máš dost blbý

Můžeš zkusit translate.google.com

Ano, mám.Zbyl mi doma a je mi ho líto vyhodit. A nemám auto a benzín je také drahý, krom toho nezabere moc místa

No teď sem na to jen koukl a jak jsem to pochopil, tak se musí ručně editovat xorg.conf.
Nejde to nějak naklikat? :D

ano, v zásadě to je tak. Těch postupů je tam několik, v závislosti na tom, s jakým problémem se potýkáš.

Tebe se týká toto:

In either case, the troubleshooting process is similar.

1. Run xrandr and compare it's output with what you expected.

A common thing to check is if the TV Out output is enabled - this has been a problem especially on Intel hardware using the -intel driver; for this particular bug, the solution is to add a tv-out quirk to xserver-xorg-video-intel: Simply file a bug with the xrandr output and your chipset subsystem pci id (just include your Xorg.0.log and/or lspci -vvnn and we can get the pci id from that).

If xrandr shows the right resolutions, but the Screen Resolution tool isn't presenting that exact list to you, then that tool has a bug. File a bug including both the xrandr output and a screenshot of what Screen Resolution is offering (and of course always include your Xorg.0.log when reporting X bugs.) Meanwhile, you can use the xrandr command line tool to set your resolution.

If xrandr shows the right resolutions, but X just didn't pick the preferred one, there is probably some secondary thing going on. For instance, you may have stray gconf or .gnome2/monitors.xml settings - which you can check by logging in as a different user and seeing if you get the correct resolution. Or something else in the X startup processes may be interfering. Or perhaps your monitor failed to correctly indicate the 'preferred' resolution, or it did, but something in the process ignored that; this can be the case if you're using a CRT and want to use a resolution less than the maximum that your CRT and video card can support. Carry forth to #2.

If xrandr is *not* showing the right resolutions you expect, then there is something wrong at a lower level. Proceed on to #3.

2. Review your /var/log/Xorg.0.log.

While complex, reading through this file can show a lot of the decision making process that X goes through to decide what resolutions to use. It will indicate, for instance, resolutions that can't be used due to memory limitations, resolutions it thinks are out of range, and so on.

A particular issue to watch out for is if it has mis-understood what monitor you have attached, it may start throwing out perfectly good resolutions because it thinks they're out of sync range.

Other issues can occur if the EDID information for your monitor is incorrect; sometimes this can be fixed via quirks to xorg-server; other times you'll have to manually configure. Move on to #3.

3. Run sudo ddcprobe and/or sudo get-edid|parse-edid and see if the timings match with xrandr

A particular bug to look for is the results indicate an 'EDID fail'. If this happens, you'll probably have to manually configure your monitor settings in xorg.conf. See edidfail

If there is a huge discrepancy between ddcprobe or get-edid, and what's available in xrandr, then something is borked up either in xorg-server or your video driver. File a bug with all the information collected so far.

4. Test working around manually

In general, you can bypass all the autodetection madness by using the old school method of configuring your hardware. In your xorg.conf, specify the correct device driver, monitor vrefresh and hsync, resolutions, bit depths, etc. If you can get it to work yourself, then file a bug with your original and fixed xorg.confs, along with your Xorg.0.log, the exact make and model of your monitor, the output from ddcprobe and get-edid, and so on. Often the situation is that a special quirk needs to be constructed for your hardware, and we'll need to work with upstream to determine it, so all this info will help fill in details.

If you are certain you have a correct configuration, and it *still* won't work, then it is possible you may need to generate your own modeline for the hardware. This is extraordinarily rare, but it can happen for really old or obscure monitors, or for situations where there is a very bad bug in the X code. Guides for creating modelines are googleable; please note there is risk of monitor damage if you issue a bad modeline, so take care to research properly before taking this route.

Máš nějaký závažný důvod používat 15" CRT monitor? Můžu ti věnovat 17" za odvoz.