Extract what would be the random effects from a mixed model from
a gam object. Assumes an mgcv model of the form gam(... + s(g, bs='re'))
.
extract_ranef(model, re = NULL, ci_level = 0.95, digits = 3)
| model | A gam or bam model |
|---|---|
| re | Filter results to a specific random effect/grouping variable. |
| ci_level | Level for the confidence interval. Must be between 0 and 1. |
| digits | Rounding for the output. |
A tibble
or data frame with the random effect,
its standard error, and its lower and upper bounds. The bounds are based
on a simple normal approximation using the standard error.
Returns a data frame of the the component
type, the estimated
random effect re
, the estimated se
, and approximate lower
and upper
bounds. Note that the standard errors are Bayesian
estimates (see gamObject
, specifically type Vp
). The re
will only reflect smooth terms whose basis function is 're', i.e. of class
random.effect
. Others will be ignored.
mgcv
strips the level names for 're' smooth terms, so this attempts
to get them back. This may not work under every circumstance, but the
attempt is made to extract the names of random effect groups based on how
they are ordered in the data (which is how the model matrix would be
constructed), and in the case of random slopes, detect that second variable
in the 're' specification would be the grouping variable. This will not
work for continuous x continuous smooths of type 're', but I can't think of
a reason why you'd use that given your other options with mgcv
.
library(mgcv) library(lme4) lmer_model <- lmer(Reaction ~ Days + (Days || Subject), data = sleepstudy) ga_model <- gam(Reaction ~ Days + s(Subject, bs = "re") + s(Days, Subject, bs = "re"), data = sleepstudy, method = "REML" ) ranef(lmer_model)#> $Subject #> (Intercept) Days #> 308 1.5126648 9.3234970 #> 309 -40.3738728 -8.5991757 #> 310 -39.1810279 -5.3877944 #> 330 24.5189244 -4.9686503 #> 331 22.9144470 -3.1939378 #> 332 9.2219759 -0.3084939 #> 333 17.1561243 -0.2872078 #> 334 -7.4517382 1.1159911 #> 335 0.5787623 -10.9059754 #> 337 34.7679030 8.6276228 #> 349 -25.7543312 1.2806892 #> 350 -13.8650598 6.7564064 #> 351 4.9159912 -3.0751356 #> 352 20.9290332 3.5122123 #> 369 3.2586448 0.8730514 #> 370 -26.4758468 4.9837910 #> 371 0.9056510 -1.0052938 #> 372 12.4217547 1.2584037 #> #> with conditional variances for “Subject”extract_ranef(ga_model)#> # A tibble: 36 x 7 #> group_var effect group value se lower_2.5 upper_97.5 #> <chr> <chr> <chr> <dbl> <dbl> <dbl> <dbl> #> 1 Subject Intercept 308 1.51 13.3 -24.5 27.5 #> 2 Subject Intercept 309 -40.4 13.3 -66.4 -14.3 #> 3 Subject Intercept 310 -39.2 13.3 -65.2 -13.2 #> 4 Subject Intercept 330 24.5 13.3 -1.51 50.5 #> 5 Subject Intercept 331 22.9 13.3 -3.11 48.9 #> 6 Subject Intercept 332 9.22 13.3 -16.8 35.2 #> 7 Subject Intercept 333 17.2 13.3 -8.87 43.2 #> 8 Subject Intercept 334 -7.45 13.3 -33.5 18.6 #> 9 Subject Intercept 335 0.579 13.3 -25.4 26.6 #> 10 Subject Intercept 337 34.8 13.3 8.74 60.8 #> # … with 26 more rows


You receive one line of input and you simply have to repeat this input. You have to write a program which functions as an echo.
One line of text without any further restrictions.
The same text which can be read under input.
Input:
42
Output:
42
Input:
ECHO
Output:
ECHO


is an opensource HTML5 mapping javascript library that provides developers the ability to integrate existing mapping platforms to provide a rich HTML5 experience.
Tile5 is an initiative of cross-platform mobile development firm,
Close


This is a sample page. There are a few block elements below that will console.log() as you reach them by scrolling down. They will also console.log() when you scroll back up and they are gone again.
Scroll down...
Here is some random block of content...(keep scrolling)
Here is some random block of content...(keep scrolling)
All done.


Modeline Database
From MythTV
Database of standard modelines as well as user created modelines for specific HD Televisions.
Note: Most of the time the driver will pick the optimum values for your TV or monitor automatically, especially when using a digital connection (DVI or HDMI).  Custom modelines should be a last resort.
Note: Modelines are ignored by NVIDIA, ATI and Intel drivers when using the TV-Out ability of these chipsets. Instead they use an internal and unmodifiable list of valid modes (which are often incorrect).
Note: The different inputs for your TV or monitor may have different allowable resolutions and scanrates. For example, some Sony TVs will not allow 1920x1080 at 50 Hz via the VGA connector, but will allow it via the HDMI input.
EDID Modelines (Data from your Monitor)
Most modern monitors/TVs can be probed for EDID data concerning their capabilities and requirements. EDID stands for "Extended Display Identification Data".
EDID data are recorded in PROM (programmable read-only memory) or EEPROM (electrically erasable PROM) within the monitor/TV itself. The modelines recorded in the EDID data, are those recommended by the manufacturer (and as such, usually give great results (although, occasionally, the manufacturer supplied data is incorrect)).
EDID modelines are recorded for many different monitor/TV screen resolutions.
EDID information includes manufacturer name, product type, phosphor or filter type, timings supported by the display, display size, luminance data and (for digital displays only) pixel mapping data.
On Linux the EDID modelines can be found by running the command:
startx -- -logverbose 6
from the console. The EDID information is written to the file /var/log/Xorg.0.log (or /var/log/XFree86.0.log).
As an example: Some of the EDID data for a Philips 170S 17" TFT.
EDID Version : 1.3 Manufacturer : PHL Monitor Name : Philips 170S Product ID : 2078 32-bit Serial Number : 693129 Serial Number String : CF 693129 Manufacture Date : 2003, week 32 DPMS Capabilities : Standby Suspend Active Off Prefer first detailed timing : Yes Supports GTF : No Maximum Image Size : 340mm x 270mm Valid HSync Range : 30.0 kHz - 82.0 kHz Valid VRefresh Range : 56 Hz - 76 Hz EDID maximum pixel clock : 140.0 MHz
Validating Mode "1280x1024": 1280 x 1024 @ 60 Hz Mode Source: EDID Pixel Clock : 108.00 MHz HRes, HSyncStart : 1280, 1328 HSyncEnd, HTotal : 1440, 1688 VRes, VSyncStart : 1024, 1025 VSyncEnd, VTotal : 1028, 1066 H/V Polarity : +/+ Mode is valid. Validating Mode "1280x960": 1280 x 960 @ 60 Hz Mode Source: EDID Pixel Clock : 108.00 MHz HRes, HSyncStart : 1280, 1376 HSyncEnd, HTotal : 1488, 1800 VRes, VSyncStart : 960, 961 VSyncEnd, VTotal : 964, 1000 H/V Polarity : +/+ Mode is valid. Validating Mode "1152x864": 1152 x 864 @ 70 Hz Mode Source: EDID Pixel Clock : 96.76 MHz HRes, HSyncStart : 1152, 1224 HSyncEnd, HTotal : 1344, 1536 VRes, VSyncStart : 864, 865 VSyncEnd, VTotal : 868, 900 H/V Polarity : -/+ Mode is valid. and many more such.
The modelines obtained from the three results above, are:
ModeLine "1280x1024_60.00" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x960_60.00" 108.0 1280 1376 1488 1800 960<PHONE_NUMBER> +hsync +vsync
ModeLine "1152x864_70.00" 96.76 1152 1224 1344 1536 864 865 868 900 -hsync +vsync
The term in the quotes, e.g., 1280x1024_60.00, is just a user defined name for the mode.
For more see: A list of Common Video Mode-Lines.
An on-line modeline calculation tool is available at: http://www.tkk.fi/Misc/Electronics/faq/vga2rgb/calc.html. Using this tool usually does not give you the result you want. However, it costs nothing, but a little of your time, to try it out. It is best to use the standard modelines listed on this page.
 Be careful in using these, some may cause your TV/monitor problems, so use them sparingly! Figure out which options you absolutely need.
From the NVIDIA readme,
Option "ModeValidation" "string" This option provides fine-grained control over each stage of the mode validation pipeline, disabling individual mode validation checks. This option should only very rarely be used. The option string is a semicolon-separated list of comma-separated lists of mode validation arguments. Each list of mode validation arguments can optionally be prepended with a display device name. "<dpy-0>: <tok>, <tok>; <dpy-1>: <tok>, <tok>, <tok>; ..." Possible arguments: "AllowNon60HzDFPModes": some lower quality TMDS encoders are only rated to drive DFPs at 60Hz; the driver will determine when only 60Hz DFP modes are allowed. This argument disables this stage of the mode validation pipeline. "NoMaxPClkCheck": each mode has a pixel clock; this pixel clock is validated against the maximum pixel clock of the hardware (for a DFP, this is the maximum pixel clock of the TMDS encoder, for a CRT, this is the maximum pixel clock of the DAC). This argument disables the maximum pixel clock checking stage of the mode validation pipeline. "NoEdidMaxPClkCheck": a display device's EDID can specify the maximum pixel clock that the display device supports; a mode's pixel clock is validated against this pixel clock maximum. This argument disables this stage of the mode validation pipeline. "AllowInterlacedModes": interlaced modes are not supported on all NVIDIA GPUs; the driver will discard interlaced modes on GPUs where interlaced modes are not supported; this argument disables this stage of the mode validation pipeline. "NoMaxSizeCheck": each NVIDIA GPU has a maximum resolution that it can drive; this argument disables this stage of the mode validation pipeline. "NoHorizSyncCheck": a mode's horizontal sync is validated against the range of valid horizontal sync values; this argument disables this stage of the mode validation pipeline. "NoVertRefreshCheck": a mode's vertical refresh rate is validated against the range of valid vertical refresh rate values; this argument disables this stage of the mode validation pipeline. "NoWidthAlignmentCheck": the alignment of a mode's visible width is validated against the capabilities of the GPU; normally, a mode's visible width must be a multiple of 8. This argument disables this stage of the mode validation pipeline. "NoDFPNativeResolutionCheck": when validating for a DFP, a mode's size is validated against the native resolution of the DFP; this argument disables this stage of the mode validation pipeline. "NoVirtualSizeCheck": if the X configuration file requests a specific virtual screen size, a mode cannot be larger than that virtual size; this argument disables this stage of the mode validation pipeline. "NoVesaModes": when constructing the mode pool for a display device, the X driver uses a built-in list of VESA modes as one of the mode sources; this argument disables use of these built-in VESA modes. "NoEdidModes": when constructing the mode pool for a display device, the X driver uses any modes listed in the display device's EDID as one of the mode sources; this argument disables use of EDID-specified modes. "NoXServerModes": when constructing the mode pool for a display device, the X driver uses the built-in modes provided by the core XFree86/Xorg X server as one of the mode sources; this argument disables use of these modes. Note that this argument does not disable custom ModeLines specified in the X config file; see the "NoCustomModes" argument for that. "NoCustomModes": when constructing the mode pool for a display device, the X driver uses custom ModeLines specified in the X config file (through the "Mode" or "ModeLine" entries in the Monitor Section) as one of the mode sources; this argument disables use of these modes. "NoPredefinedModes": when constructing the mode pool for a display device, the X driver uses additional modes predefined by the NVIDIA X driver; this argument disables use of these modes. "NoUserModes": additional modes can be added to the mode pool dynamically, using the NV-CONTROL X extension; this argument prohibits user-specified modes via the NV-CONTROL X extension.
NTSC (Analog)
# 712x486 @ 29.97Hz, 15.7kHz, itu-r bt.470 M/ntsc, 711 dots displayed ModeLine "712x486@30i" 13.5 712 736 799 858 486 492 498 525 interlace -hsync -vsync # 704x480 @ 29.97Hz, 15.7kHz, itu-r bt.470 M conformant, mpeg ModeLine "704x480@30i" 13.5 704 728 791 858 480 486 492 525 interlace -hsync -vsync # 720x480 @ 29.97Hz, 15.7kHz, itu-r bt.601, mpeg ModeLine "720x480@30i" 13.5 720 736 799 858 480 486 492 525 interlace -hsync -vsync #ModeLine "NTSCspec-59.94i" 14.318 768 784 848 910 483 484 492 525 Interlace #ModeLine "NTSCspec-59.94p" 28.636 768 784 848 910 483 484 492 525 #ModeLine "Laserdisk-59.94i" 10.762 567 583 647 684 483 484 492 525 Interlace #ModeLine "Laserdisk-59.94p" 21.524 567 583 647 684 483 484 492 525
Note: Analog equipment expects a 711x485 image with an aspect ratio of 4/3. Thus, setting the aspect ratio of 704x480 to 4/3 and of 720x480 to 15/11 is approximative up to 0.5 per mille.
PAL 625
# 702x576 @ 25Hz, 15.6kHz, itu-r bt.470 PAL, analog broadcast ModeLine "702x576@25i" 13.5 702 722 785 864 576 581 586 625 interlace -hsync -vsync # 704x576 @ 25Hz, 15.6kHz, itu-r bt.470 PAL, mpeg, 702 dots displayed ModeLine "704x576@25i" 13.5 704 723 786 864 576 581 586 625 interlace -hsync -vsync # 720x576 @ 25Hz, 15.6kHz, itu-r bt.601 PAL, mpeg ModeLine "720x576@25i" 13.5 720 732 795 864 576 581 586 625 interlace -hsync -vsync # 768x576 @ 25Hz, 15.6kHz, square dot itu-r bt.470 PAL, TV-monitor, 767 dots displayed ModeLine "768x576@25i" 14.75 768 789 858 944 576 581 586 625 interlace -hsync -vsync # 720x576 @ 50Hz, 31.25kHz, itu-r bt.1358 625/50/p/1:1, RGB, YPbPr, HDMI ModeLine "720x576@50" 27 720 732 795 864 576 581 586 625 -hsync -vsync # 768x576 @ 50Hz, 31.25kHz, progressive square dot itu-r bt.470 PAL ModeLine "768x576@50" 29.5 768 789 858 944 576 581 586 625 -hsync -vsync # nonstandard PAL (Works with BOB deinterlace) It is 60Hz but works well with nVIDIA PAL-B TV-OUT # Nvidia option: Option "TVStandard" "PAL-B" ModeLine "720x576@60" 32.7 720 744 816 912 576 577 580 597 # This modeline is 50Hz interlaced and works well with kerneldeint: ModeLine "720x576i" 13.875 720 744 808 888 576 581 586 625 -hsync -vsync interlace
PAL 625 broadcast equipment using a 13.5 MHz reference frequency sets the image aspect ratio of 704x576 to 1.33=4/3 and of 720x576 to 1.3636=15/11. This ensures compatibility with analog TV's which expect 702x575 at a ratio of 4/3. Video monitors can display the whole image, including the extra dots on the left and right, by depressing the underscan switch. Analog broadcast cameras typically output a 14.75 MHz square dot resolution of 786x581 from a 816x606 CCD frame.
However, 720x576 at 13.5 MHz with an image aspect ratio of 4/3 is employed by dvb-c set top boxes and upgraded analog TV channels.
 Native resolution is 1366x768. Running the screen at 1368x768 will result in a little line running up the image from time to time. 1360x768 is much better, but scene changes flicker a bit some times. My 7100 nvidia card can't do the 1366x768 resolution and I'm guessing that would fix the issue.
Device section:
# Option "ExactModeTimingsDVI" # Option "ModeValidation" "NoDFPNativeResolutionCheck"
Monitor section:
SubSection "Display" Modes "1360x768"
Apex
Apex LD 4088 40" LCD
Device section:
Option "ModeValidation" "NoEdidModes"
Monitor section:
ModeLine "1920x1080" 74.25 1920 2008 2052 2200 1080 1084 1094 1124 +hsync +vsync Interlace Option "ExactModeTimingsDVI" "TRUE" SubSection "Display" Modes "1920x1080"
Dell
Dell 2405FPW
## (at native 1920x1200) # Modeline "1920x1200"<PHONE_NUMBER> 1960 1992 4040 1200 1201 1204 1232 -hsync ## I have to use an older driver (1.0-7174) which does not limit the bandwidth: # Modeline "1920x1200" 161.75 1920 2020 2052 2184 1200 1202 1208 1235 -hsync -vsync
Fujitsu
Fujitsu-Siemens, Amilo LSL 3230T
Found from the monitors EDID. # 1920x1080 @ 60Hz hsync: 67.5kHz (EDID from Fujitsu-Siemens, Amilo LSL 3230T) Modeline "1920x1080" 148.5 1920 2008 2052 2200 1080 1089 1095 1125 +hsync +vsync
Fujitsu 50" Plasma
## Fujitsu 50" HD Plasma (1366x768@60Hz native) ## I'm using a nVidia card so the resolution must be a multiple of 8, I use 1368x768. ## This is the modeline i got from PowerStrip. Add this to the "Monitor" section. # Modeline "1368x768" 85.478 1368 1424 1536 1792 768 771 777 795 +hsync +vsync ## To get this working on my computer I had to disable EDID, "UseEDID" did not work so I read through the nVidia driver ## documentation and added everything to do with disabling monitor checks (there's probably a bit of redundancy here). ## Check the latest driver documentation for more info. This can go in the "Device" or "Screen" section. # Option "UseEDID" "False" # Option "FlatPanelProperties" "Scaling = native" # Option "ExactModeTimingsDVI" "true" # Option "ModeValidation" "AllowNon60HzDFPModes, NoEdidMaxPClkCheck, NoMaxPClkCheck, NoHorizSyncCheck, NoVertRefreshCheck, NoEdidDFPMaxSizeCheck, NoEdidModes"
Hitachi
Hitachi 42PD380TA
##(42"/106cm Standard Definition Plasma) ## Note: you can fine tune position and size from TV's Menu # Modeline "1280x720@60" 74.48 1280 1468 1604 1664 720 721 724 746 +hsync +vsync ## Works for nVidia FX 5200 PCI -> DVI to HDMI -> Sony KDF60WF655 LCD HDTV # The "Monitor" Section should include # # Option "IgnoreEDID" # Note: For newer versions of the NVIDIA driver the line above has to be replaced with the following two lines: # Option "UseEDID" "FALSE" # Option "ExactModeTimingsDVI" "TRUE" # # HorizSync 15 - 46 # VertRefresh 59 - 61 # Modeline "1280x720p_at60Hz" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
InFocus
InFocus ScreenPlay 5000
# ModeLine "ATSC-720-59.94p" 74.176 1280 1320 1376 1650 720 722 728 750 # ModeLine "ATSC-720-60p" 74.25 1280 1320 1376 1650 720 722 728 750
InFocus X1A
# Modeline "800x600" 31.00 800<PHONE_NUMBER> 600 602 603 632 # 31 MHz, 31.0 kHz, 49.1 Hz
LG
DU-37LZ30
ATSC 720p @ 60 Hz no overscan on VGA input
ModeLine "ATSC-720-60p-no-over" 74.16 1192 1310 1343 1648 672 700 705 750 +HSync +VSync
ATSC 1080i @ 60 Hz no overscan on VGA input
ModeLine "ATSC-1080-60i" 74.25 1778 1899 2002 2200 1010 1052 1068 1125 Interlace +HSync +VSync
32LG3000
(Probably the same for 32LG2000 and maybe all xxLG3000 and xxLG2000)
The native resolutions of the 32LG3000 is 1366x768.
# monitor-edid #Name: LG TV #EISA ID: GSM75ef #Screen size: 70.0 cm x 39.0 cm (31.55 inches, aspect ratio 16/9 = 1.78) DisplaySize 700 390 #Gamma: 2.2 #Analog signal #Max video bandwidth: 150 MHz HorizSync 28-67 VertRefresh 50-75 # Monitor preferred modeline (59.8 Hz vsync, 47.7 kHz hsync, ratio 16/9) (bad ratio) ModeLine "1360x768" 84.75 1360 1432 1568 1776 768 771 776 798 +hsync -vsync # Monitor preferred modeline (60.0 Hz vsync, 67.5 kHz hsync, ratio 16/9) ModeLine "1920x1080" 148.5 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
I have also managed to use the following modelines:
# gtf 1366 768 59.8 # 1368x768 @ 59.80 Hz (GTF) hsync: 47.54 kHz; pclk: 85.57 MHz Modeline "1368x768_59.80" 85.57 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync
# gtf 1366 768 60 # 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz Modeline "1368x768_60.00" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync
# gtf 1360 768 60 # 1360x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 84.72 MHz Modeline "1360x768_60.00" 84.72 1360 1424 1568 1776 768 769 772 795 -HSync +Vsync
# gtf 1360 768 59.8 # 1360x768 @ 59.80 Hz (GTF) hsync: 47.54 kHz; pclk: 84.43 MHz Modeline "1360x768_59.80" 84.43 1360 1424 1568 1776 768 769 772 795 -HSync +Vsync
# Selfmade: Modeline "1366x768" 85.500 1366 1494 1624 1798 768 770 776 795 +hsync -vsync
The modeline above gives perfect 1:1 pixelmapping on the screen when sent from my Intel G35 onboard graphics card (Asus P5E-VM HDMI) using a plain HDMI-HDMI cable (no DVI dongle). The "Just Scan" option is only available for true 1080p, 1080i and 720p, so I set it to "16/9" and still get a perfect image. Great.
In the "Monitor" section of my xorg.conf I use the following option to choose the preferred mode:
#Option "PreferredMode" "1360x768" #Option "PreferredMode" "1368x768_59.80" Option "PreferredMode" "1366x768"
Judaz 08:31, 27 January 2009 (UTC)
37LG7000
Custom modeline modified by hand from 1920x1080 60Hz to get 1920x1080 50Hz. This happens to work with LG7000. It has the same pixel clock as the 1920x1080_60 (CVT-RB) from LG7000's EDID.
- 1920x1080 50 Hz custom modeline (vsync width: 7)
Modeline "1920x1080_50c" 138.5 1920 2378 2410 2490 1080 1083 1090 1113 +hsync -vsync
26LC3R
# 720p @ 50Hz no overscan on HDMI ModeLine "1157x685" 74.25 1157 1658 1698 1980 685 707 712 750 +hsync +vsync # On NVIDIA ION you also need Option "ExactModeTimingsDVI" "TRUE"
Mitsubishi
Mitsubishi HC-1500
## Doesn't claim to support native (1280x720) over VGA, but it does just fine # ModeLine "720p" 74.25 1280 1392 1448 1650 720 722 728 750
Mitsubishi WT-46809
## Detected as 1080i # ModeLine "960x540p" 37.26<PHONE_NUMBER> 1104 540 542 548 563 +hsync +vsync
Mitsubishi WS-55513
## 1080 on DVI with a 5200 # ModeLine "in1080i" 74.5 1760 1888 2096 2208 960 1012 1028 1126 -hsync -vsync interlace
Mitsubishi WS-48313
## I had to add the following ## HorizSync 15-75 ## Option "UseEdidFreqs" "FALSE" # Modeline "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsync
Mitsubishi HC3000u Projector
# (naitive DLP chip resolution 1280x768) # 1280x768 at 59.94 Hz - VGA output of an nvidia 6150 graphics chip (Asus A8N-VM CSM motherboard) # Modeline "1280x768-Mitsubishi" 83.05 1280 1376 1504 1736 768 771 778 798 -hsync -vsync
NEC
NEC 2090UXi
These slightly reduced blanking modes work for the analog and the digital input. The lower dot clock frequency allows to use a DVI cable of 15 m long.
## 1600x1200 @ 50Hz, 62.5 kHz hsync, nec 2090uxi #Modeline "1600x1200@50" 120 1600 1628 1788 1920 1200 1201 1204 1250 # ## 1600x1200 @ 60Hz, 75 kHz hsync, nec 2090uxi #Modeline "1600x1200@60" 144 1600 1628 1788 1920 1200 1201 1204 1250
NEC PX-50XM5 50" HD Plasma
This panel has a native resolution of 1365x768@60Hz and can be driven at this resolution using the DVI port. I tried to make it sync at 50Hz (due to PAL) with no luck.
Section "Screen" Monitor "NEC PX-50XM5" DefaultDepth 24 Option "UseEDID" "FALSE" Option "UseEDIDFreqs" "FALSE" Option "ModeValidation" NoEdidModes,AllowNon60HzDFPModes,NoMaxPClkCheck,NoMaxSizeCheck,NoDFPNativeResolutionCheck,NoPredefinedModes,NoVesaModes,NoVirtualSizeCheck,NoWidthAlignmentCheck,NoVertRefreshCheck,NoHorizSyncCheck,NoMaxSizeCheck,NoEdidMaxPClkCheck,NoDFPNativeResolutionCheck" Option "XvmcUsesTextures" "true" Option "RenderAccel" "true" Option "ExactModeTimingsDVI" "true" Option "FlatPanelProperties" "Scaling = Native" Option "UseEvents" "TRUE" Option "DPMS" Option "NoLogo" "TRUE" SubSection "Display" Viewport 0 0 Depth 24 Modes "1365x768" EndSubSection EndSection Section "Monitor" Identifier "NEC PX-50XM5" HorizSync 15.0 - 110.0 VertRefresh 50.0 - 120.0 ModeLine "1365x768" 72.149 1365 1416 1466 1526 768 772 776 788 +hsync +vsync EndSection
Olevia
Olevia LT26HVX
## This TV has a decent screen for the cost, but VGA and DVI input is ## problematic, since it reports a mode of 1280x1024 in EDID, though the native ## resolution is 1366x768, something which I wanted to take advantage of to display ## 1080i with maximum detail. After much trial and error I found several modelines ## that work when it's connected to my Radeon 8500 via DVI; I didn't have as much ## luck connected to an Nvidia card, with Windows and X. The TV doesn't seem to have ## a way to disable scaling, so even with a mode of 1360x768 or 1366x768, pixels ## don't line up perfectly. It seems close enough for video, if not for ## desktop use. It also doesn't recognize image sizes larger than 1280x1024, so I had ## tweak those modes carefully with xvidtune to get the image centered. I use ## 'Option "IgnoreEDID" "true"' in the Screen section. ## ## DisplaySize 586 330 ## VertRefresh 50-70 ## # Modeline "1280x768@60" 80 1280 1312 1608 1640 768 783 791 807 # Modeline "1360x768" 85.50 1360 1476 1588 1776 768 771 777 795 +hsync +vsync # Modeline "1368x768" 85.50 1368 1478 1590 1776 768 771 777 795 # ## This works over VGA. The panel will not accept a signal over DVI with more than 720 ## vertical pixels. (displays "Not Support") # # Modeline "1366x768" 85.50 1366 1478 1590 1776 768 771 777 795 # ## On my display, to get this as close to pixel perfect as I can tell, set in ## "Advance Picture Adjust": ## Vertical Position 18 ## Horizontal Position 115 ## Phase 13 ## Manual Clock 117
Olevia LT26HVX - alternate
#Using a current nvidia driver and the VGA port i was unable to use any of the modelines in the #original example, but found a modeline somewhere else that worked. I have not used the #"Advance Picture Adjust" menu on my Olevia at all - I just used the auto-adjust feature after #configuring xorg.conf as follows: # # #Section "Monitor" # Identifier "LT26HVX" # VendorName "Syntax" # ModelName "Olevia 26 HVX" # HorizSync 30.0 - 85.0 # VertRefresh 50.0 - 70.0 # DisplaySize 586 330 # Option "dpms" # Modeline "1366x768" 85.500 1360 1440 1552 1792 768 771 777 795 +hsync +vsync #EndSection # #Section "Device" # Identifier "GeForce FX5500" # Driver "nvidia" # Option "UseEDID" "false" #EndSection # #Section "Screen" # Identifier "Default Screen" # Device "GeForce FX5500" # Monitor "LT26HVX" # Option "RenderAccel" "true" # DefaultDepth 24 # SubSection "Display" # ViewPort 0 0 # Depth 24 # Modes "1366x768" # EndSubSection #EndSection # #The dpms option is probably worthless because this display just gives me a blue screen #when dpms is triggered instead of powering off the panel.
Olevia LT32HVE
(--) NVIDIA(0): EDID Version : 1.0 (--) NVIDIA(0): Manufacturer : DMI (--) NVIDIA(0): Monitor Name : DMI LCD Multi-Media Display (--) NVIDIA(0): Product ID : 0 (--) NVIDIA(0): 32-bit Serial Number : 66 (--) NVIDIA(0): Serial Number String : (--) NVIDIA(0): Manufacture Date : 2004, week 17 (--) NVIDIA(0): DPMS Capabilities : Standby (--) NVIDIA(0): Prefer first detailed timing : Yes (--) NVIDIA(0): Supports GTF : No (--) NVIDIA(0): Maximum Image Size : 40mm x 30mm (--) NVIDIA(0): Valid HSync Range : 31.5 kHz - 80.0 kHz (--) NVIDIA(0): Valid VRefresh Range : 56 Hz - 75 Hz (--) NVIDIA(0): EDID maximum pixel clock : 135.0 MHz
I use an Nvidia GeForce 7900GT/GTO. Somehow, after a recent software upgrade, the 1280x768 mode that I have been using has disappeared from the Nvidia driver's mode pool. So I added new modelines to match the native resolution of 1366x768. Since 1366 is not divisible by 8, the closest I got was 1368x768 (like the LT26HVE above). Similarly, I couldn't get a pixel-by-pixel match. Both 1368 and 1280 gave a clear picture that can be used as a monitor or TV output. The choice of number of scan lines was more important in clarity. Anything other than 768 made it very blurry.
I did not have to set "useEDID" to false or play with the TV's picture settings.
Here are the modes obtained using the GTF utility (also see some usage examples elsewhere on this page):
# 1368x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 85.86 MHz Modeline "1368x768_60.00" 85.86 1368 1440 1584 1800 768 769 772 795 -HSync +Vsync # 1280x768 @ 60.00 Hz (GTF) hsync: 47.70 kHz; pclk: 80.14 MHz Modeline "1280x768_60.00" 80.14 1280 1344 1480 1680 768 769 772 795 -HSync +Vsync # 1280x720 @ 60.00 Hz (GTF) hsync: 44.76 kHz; pclk: 74.48 MHz Modeline "1280x720_60.00" 74.48 1280 1336 1472 1664 720 721 724 746 -HSync +Vsync
--Cengique 23:16, 24 December 2009 (UTC)
Olevia 537h
#Section "Monitor" # Identifier "OleviaHDTV" # VendorName "Olevia" # ModelName "537h" # VertRefresh 50-80 # HorizSync 30-85 # Modeline "1360x768" 72.000 1360 1424 1456 1560 768 771 776 790 -hsync +vsync # DisplaySize 457 812 #EndSection
With an nvidia 6200LE, the above did not work for my 537h. X started, but the screen was blank. The following worked for me:
#Section "Monitor" # Identifier "OleviaHDTV" # VendorName "Olevia" # ModelName "537h" # VertRefresh 50-80 # HorizSync 30-85 # Modeline "1360x768" 84.50 1360 1392 1712 1744 768 783 791 807 #EndSection
Panasonic
Panasonic TX-32LED8F
## panel has a native res of 1366*768 but doesn't accept this over HDMI, as is specified on the user manual. ## The TV seems to work perfectly with the timings provided by EDID, but not without specifing them on xorg.conf ## These settings have been tested with fglrx proprietary and radeon drivers Section "Monitor" Identifier "Monitor-0" Option "VendorName" "Panasonic" Option "ModelName" "TX-32LED8F" Option "DPMS" "true" VertRefresh 23-61 HorizSync 15-68 Modeline "1280x720" 74.2 1280 1720 1760 1980 720 725 730 750 EndSection
Panasonic TX32LXD52
## panel has a native res of 1366*768 but doesn't accept this (AFAIK) over HDMI. ## I am running an nvidia card and custom interlaced modes over DVI/HDMI are currently ## difficult to get working. ## A good summary of the issue here - http://www.nvnews.net/vbulletin/showthread.php?t=69255 ## This mode is a 1216*684@60Hz mode that I came up with through trial and error. ## Exactly what switches you pass for DPI and other checks may vary from what I have. ## ## NB: the vast array of ModeValidation arguments have arisen today since moving to 9629 ## driver release of the last few days. Tweak according to what is needed to validate the ## mode by your driver version. # #Section "Monitor" # Identifier "Monitor0" # VendorName "Panasonic" # ModelName "32in HDTV" # Mode "1216x684p60" # DotClock 74.160 # HTimings 1216 1356 1396 1648 # VTimings 684 707 712 750 # Flags "+hsync" "+vsync" # EndMode #Section "Device" # Identifier "NVIDIA Corporation NV45 [GeForce 6800GT]" # Driver "nvidia" # BusID "PCI:2:0:0" # Option "UseDisplayDevice" "DFP" # Option "FlatPanelProperties" "Scaling = native" # Option "IgnoreDisplayDevices" "TV, CRT" # Option "ExactModeTimingsDVI" "1" # Option "NoLogo" "1" # Option "UseEDIDDpi" "0" # Option "UseEDIDFreqs" "0" # Option "ModeValidation" "AllowNon60HzDFPModes,NoEdidMaxPClkCheck,NoVertRefreshCheck,NoHorizSyncCheck,NoDFPNativeResolutionC heck,NoVesaModes,NoEdidModes,NoXServerModes,NoPredefinedModes" #EndSection
Panasonic PT-AE700 Projector
#Section "Monitor" # Identifier "AE-700" # Option "DPMS" # # Modeline "1280x720@60" 74.160 1280 1352 1392 1648 720 725 730 750 -hsync -vsync #EndSection
To get DVI output to work on ATI cards using the open source driver, try setting some options in the device section.
#Section "Device" # Identifier "ATI Technologies Inc RV280 [Radeon 9200 PRO]" # Driver "radeon" # # Option "AGPMode" "4" # Option "MonitorLayout" "TMDS, NONE" # Option "DDCMode" "on" # Option "PanelSize" "1280x720" #EndSection
Panasonic PT-AE900U Projector
#Section "Monitor" # Identifier "Monitor0" # VendorName "Panasonic" # ModelName "PT-AE900U" # Option "DPMS" "true" # # From the User's Manual, page 62 # HorizSync 30.0 - 70.0 # VertRefresh 50.0 - 87.0 # # From the the User's Manual, page 62 the dot clock must be < 108 MHz # ModeLine "1280x720" 74.52 1280 1312 1368 1676 720 724 730 750 +hsync +vsync #EndSection
Panasonic PT-AX100U Projector
#Section "Monitor" # Identifier "Configured Monitor" # VendorName "Panasonic" # ModelName "PT-AX100U" # Option "DPMS" # HorizSync 30 - 70 # VertRefresh 50 - 87 # Modeline "1280x720@60" 74.160 1280 1308 1344 1672 720 725 730 750 -hsync -vsync #EndSection
Panasonic TH-50PX600A, TH-50PX60A, TH-50PX70A
According to Nvidia, older drivers had a limitation where they could not accept resolutions of odd sizes: nVidia Release
This limitation has now been fixed and it is possible to run these TVs in their native resolutions (768p (1366x768)). When running with a VGA cable it seems that these TVs will not provide any EDID data. As 1366x768 is a non standard resolution you need to add a modeline to your monitor section that specifies 1366x768:
# Modeline "1366x768" 85.500 1360 1440 1552 1792 768 771 777 795 +hsync +vsync
When running with nvidia cards you may also need to add a line that reads:
Option "ModeValidation" "NoDFPNativeResolutionCheck"
into your Device section.
Also take note that these TVs have a 'input resolution' setting which defaults to XGA and gives very poor results when running in their native resolutions. If the picture looks strange try pressing the 'menu' button on the remote, then going to 'Setup', 'PC setup' then changing the 'Input resolution' from XGA to WXGA. When running in native resolution also make sure you are in 16:9 mode, by pressing the 'aspect' button on the remote to bring up the 'Aspect selection' menu.
The following has been tested and works without problems:
## Plasma panel has a native res of 1366*768 but the 9xxx series of nVidia drivers only ## accept resolutions which divide by 8. So the nearest I got was 1280 x 768. No EDID is ## passed through the PC connection to the TV - to get EDID I believe you need to connect ## via HDMI. You can find out what the valid resolutions, HorizSync and VertRefresh settings ## are by looking in the TV manual (p39) or at ## http://panasonic.com.au/products/specifications.cfm?objectID=3406 ## HorizSync range is 31.46 - 68.38 and the VertRefresh range is 60-85. # #Section "Monitor" # Identifier "Monitor0" # VendorName "Panasonic" # ModelName "TH-50PX70A" # HorizSync 31.46 - 68.38 # VertRefresh 60 - 85 # ## Modeline for non standard 1366x768 resolution. You may not need this if running ## With HDMI, though I haven't tested. # Modeline "1366x768" 85.500 1360 1440 1552 1792 768 771 777 795 +hsync +vsync #EndSection # #Section "Screen" # Identifier "Screen0" # Device "Videocard0" # Monitor "Monitor0" # DefaultDepth 24 # SubSection "Display" # Viewport 0 0 # Depth 24 # Modes "1280x768_60" "1280x720_60" "1024x768_60" "800x600" "640x480" # EndSubSection # ### Force 100x100 dpi as that's what MythTV is designed to run at. # Option "DPI" "100 x 100" #EndSection
Panasonic TH-50PX80A
Similar to the TH-50PX70A above, but I found this modeline worked better:
ModeLine "1366x768_60" 88.0 1384 1424 1704 1816 770 770 782 808
The 1366x768 (really 1360x768) modeline given above didn't use all available screen real estate. This panel lets you move the image around, but not stretch it.
Similar to the TH-50PX70A, you'll get better results with the WXGA mode over XGA.
Panasonic TH-42PX7A
Should work for most Panasonic 1024x768 plasma panels (in test at the moment for a TH-42PX80a):
"1024x768custom" 28.043 1024 1050 1186 1344 768 771 777 806 -hsync -vsync
Panasonic TX-42PX75U
This widescreen panel's native resolution is 1024x768. The manual says that it does not take inputs at this resolution and I have been unsuccessful when trying to drive it at this resolution. So we have to settle with a non-native resolution and put up with awful-looking text. I decided to send 720p at 60Hz.
Section "Monitor" ... Modeline "1208x679" 74.25 1208 1353 1393 1650 679 707 712 750 +hsync +vsync EndSection
The TV's overscan seems to vary by a few pixels each time it is turned on so one cannot fill the screen perfectly every time. The modeline above compensates for this by being slightly smaller and leaving a few rows or columns of black (porch) pixels on either side of the viewable screen.
Improvements welcome.
Panasonic TH-P50G10A
This a one of the new releases for 2009 for Panasonic - Has a native of 1920x1080@50/60/24
Section "Monitor" Identifier "Monitor0" VendorName "Panasonic-TV" ModelName "P50G10A" HorizSync 15.0 - 68.0 VertRefresh 23.0 - 61.0 Option "DPMS" # 1920x1080p @ 50Hz ModeLine "1920x1080@50" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync # 1920x1080p @ 60Hz ModeLine "1920x1080@60" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync # 1920x1080p @ 24Hz ModeLine "1920x1080@24" 74.16 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +hsync EndSection
Philips
Philips 170S (17 inch LCD Monitor)
Found from the monitors EDID. # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
Philips 190S (19 inch LCD Monitor)
Found from the monitors EDID. # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
Philips 190b6 TFT LCD
## Native dotclock list: 94.5(31.5) 100 108(13.5,27,36) 120(30,40) 130(65) 135 MHz ## HorizSync 30.0 - 83.0 ## VertRefresh 49-76 ## Option "IgnoreEDID" ## ## 1280x1024 @ 50 Hz, 56.25 kHz, analog and digital # Modeline "1280x1024@50" 94.5 1280 1320 1460 1680 1024 1025 1028 1125 ## ## The following doesn't work over VGA since the firmware invariably assumes 556 ## visible lines when driving 625@50Hz (preset: 30MHz 688x556@50Hz 960x625). ## 800x600 @ 50 Hz, 31.25 kHz, digital # Modeline "800x600@50" 30 800 814 884 960 600 601 606 625 +hsync +vsync
Philips 190b8 TFT LCD
The monitor's firmware rejects any mode with a vertical frequency outside the 55-76 Hz range. Also, the resynchronization delay is just below 2 seconds for a distant modeswitch. Displaying a 25 frame/s video without judder requires the 75 Hz modeline below.
## Native dotclock: 100 108(13.5,27,36) 120(30,40) 126(31.5,94.5) 130(65) 135 MHz ## HorizSync 30.0 - 83.0 ## VertRefresh 55-76 ## Option "IgnoreEDID" ## ## 1280x1024 @ 60 Hz, 67.5 kHz, philips 170b5 190b6 190b8 # Modeline "1280x1024@60" 108 1280 1328 1440 1600 1024 1025 1028 1125 ## ## 1280x1024 @ 75 Hz, 78.75 kHz, philips 170b5 190b6 190b8 # Modeline "1280x1024@75" 126 1280 1328 1440 1600 1024 1025 1028 1050
Philips 50" Cineos Plasma 50PF9631D/10
Still needs to be connected to the graphics card at boot up to recognise the display. Works well in 1080i, I prefer 720p for normal tv / dvd.
Section "Monitor" HorizSync 31-145 Identifier "Monitor[0]" ModelName "1920X1080@55HZ" VendorName "Philips" VertRefresh 50-75 UseModes "Modes[0]" Option "ModeValidation" "NoVertRefreshCheck, AllowNon60HzDFPModes, AllowInterlacedModes, NoHorizSyncCheck, NoVirtualSizeCheck, NoDFPNativeResolutionCheck " Option "ConnectedMonitor" "DFP" Option "UseDisplayDevice" "DFP-0" EndSection Section "Modes" Identifier "Modes[0]" Modeline "1920x1080@60i" 77.60 1920 1952 2240 2272 1080 1104 1110 1135 interlace Section "Screen" Option "UseEvents" "True" DefaultDepth 24 SubSection "Display" Depth 15 Modes "1920x1080_60i" "1280x720_60" "720x480_60" EndSubSection
Samsung
Samsung HL-R5678W
## Samsung HL-R5678W DLP (in 1920x1080p [over VGA input]), all resolutions without -XX are 60Hz ## The 1920x1080 (@60Hz) Modeline is confirmed working for the Samsung HL-R5078W in same manner as above ## # Modeline "1920x1200"<PHONE_NUMBER> 1984 2016 2080 1200 1203 1209 1235 +hsync -vsync # Modeline "1920x1080"<PHONE_NUMBER> 1984 2016 2096 1080 1082 1087 1111 +hsync -vsync # Modeline "1600x1200"<PHONE_NUMBER> 1672 1864 2160 1200 1201 1204 1250 +hsync +vsync # Modeline "1600x1024"<PHONE_NUMBER> 1712 1880 2144 1024 1025 1028 1060 -hsync +vsync # Modeline "1280x1024"<PHONE_NUMBER> 1344 1456 1688 1024 1025 1028 1066 +hsync +vsync # Modeline "1280x1024-70"<PHONE_NUMBER> 1384 1520 1728 1024 1025 1028 1066 -hsync +vsync # Modeline "1280x1024-72"<PHONE_NUMBER> 1384 1520 1728 1024 1025 1028 1067 -hsync +vsync # Modeline "1280x1024-75"<PHONE_NUMBER> 1312 1456 1688 1024 1025 1028 1066 +hsync +vsync # Modeline "1280x960"<PHONE_NUMBER> 1392 1504 1800 960<PHONE_NUMBER> +hsync +vsync # Modeline "1280x768" 79.464 1280 1360 1488 1664 768 771 778 798 -hsync +vsync # Modeline "1280x768-70" 95.055 1280 1368 1504 1696 768 769 772 800 -hsync +vsync # Modeline "1280x768-72" 97.839 1280 1368 1504 1696 768 769 772 801 -hsync +vsync # Modeline "1280x768-75"<PHONE_NUMBER> 1376 1504 1696 768 771 778 805 -hsync +vsync # Modeline "1280x720" 74.453 1280 1448 1584 1696 720 721 724 746 -hsync +vsync # Modeline "1152x864"<PHONE_NUMBER> 1232 1360 1616 864 865 868 900 +hsync +vsync # Modeline "1024x768" 74.871 1024 1064 1200 1344 768 771 777 806 -hsync -vsync # Modeline "800x600-56" 36.018 800<PHONE_NUMBER> 600 601 603 625 +hsync +vsync # Modeline "800x600" 40.025 800<PHONE_NUMBER> 600 601 605 628 +hsync +vsync
Samsung LE32R51B / LE26Rx / LE37R4 / LE40R5 / LE32R71 (B/W)
## DisplaySize 349 196 # Modeline "1360x768" 85.500 1360 1424 1536 1792 768 771 777 795 +Hsync +Vsync
Samsung LE40F8
# Modeline "1920x1080@60" 138.5 1920 1960 1995 2083 1080 1082 1087 1109 +hsync -vsync
Samsung LA40S71BX / LA40S71BX/XSA
This is a 1360x768 resolution monitor with VGA and HDMI inputs (amongst others). However according to the Samsung Manual, it is not correct to connect a computer to the HDMI input. Samsung state: "Do not attempt to connect the HDMI/DVI connector to a PC or Laptop Graphics Card." (Section 2, "Quick guide", "Setup").
However a note in the Ubuntu Forums suggests that configuring output to be 1280x720 (i.e.: "720p") is a workaround. Connecting DVI->HDMI gives a 1280x720 X-Desktop regardless of the modeline setting, so perhaps the above workaround is the only full-digital option.
A 1360x768 desktop via (analogue) VGA works perfectly though.
Samsung LA40R81BD
## Samsung LA40R81BD LCD TV [over HDMI2 input] # Modeline "1360x768@60" 85.800 1360 1440 1552 1792 768 771 777 795 +hsync +vsync # DisplaySize 349 196 # # You will probably have to disable DDC/EDID # So will need these also. (They work for 1360x768@60 but not sure if they are totally correct.) # HorizSync 30-61 # VertRefresh 60-75 # # Also in Device disable DDC/EDID # e.g. For Xorg Radeon driver # Section "Device" # Identifier "ATIVideocard0" # Driver "radeon" # #### # Remove DDC # Option "NoDDC" "on" # Option "DDCMode" "off" # Option "IgnoreEDID" "on" # EndSection
Samsung LA46M81BDX
For a 50Hz modeline to prevent judder on stock/news tickers and scrolling credits when viewing PAL DVB:
Section "Device" Option "ModeValidation" "NoMaxPClkCheck, AllowNon60HzDFPModes" # Samsung LA46M81BDX LCD TV [over HDMI2 input] Modeline "1920x1080@50" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 EndSection
Samsung LNR328W
# Modeline "1360x768" 85.5 1360 1416 1528 1792 768 771 777 795 +hsync +vsync
Samsung LNR3255W
# Modeline "1360x768" 84.50 1360 1392 1712 1744 768 783 791 807 +hsync +vsync
Samsung LNS3241D / LNS3251D
## Used `get-edid | parse-edid` to determine this modeline: # Modeline "1360x768" 85.50 1360 1424 1536 1792 768 771 777 795 +HSync +VSync ## Also had to set the Horizontal/Vertical Freq.: # HorizSync 47.7 - 47.7 # VertRefresh 60.0 - 60.0 ## Don't know if this is necessary for correct DPI, but the display size is: # DisplaySize 692 394
Samsung LNT4661F / LNT4061F / LNT4065F / LNT4665F / LNT5265F
# Samsung LNT4661F (VGA input). Given that the manual is identical, this should also # work for models LNT4061F, LNT4065F, LNT4665F and LNT5265F Section "Monitor" Identifier "Monitor0" VendorName "Samsung" ModelName "LNT4661F" HorizSync 15.0 - 80.0 VertRefresh 50.0 - 100.0 Modeline "1920x1080"<PHONE_NUMBER> 1960 1995 2083 1080 1082 1087 1109 +hsync -vsync Option "dpms" EndSection # Video card is an NVidia GeForce FX 5200. Using the binary driver from NVidia, I appear # to need this line in my "Screen" section. It's likely some of these options are not needed # but I've been too lazy to figure out which ones. Option "ModeValidation" "AllowNon60HzDFPModes,NoEdidMaxPClkCheck,NoVertRefreshCheck,NoHorizSyncCheck,NoDFPNativeResolutionCheck,NoVesaModes,NoEdidModes,NoXServerModes,NoPredefinedModes" #
Samsung 2343BW
# 23" 16:9 monitor. Power use: 44W running, 1W standby. Display area 509.952 mm(H) X 286.848 mm(V) # Max pixel clock: 157MHz # # Scan frequencies: VESA, 2048 X 1152 70.992 59.909 156.750 +/- # What seems really weird is that the manual says sync H/V +/- while what acually works is -HSync +VSync # Manual: http://downloadcenter.samsung.com/content/UM/200905/20090526185745109/BN59-00950A-02Eng.pdf # Section "Monitor" Identifier "VGA" ModelName "Samsung 2343BW" HorizSync 30-92 VertRefresh 56-85 Mode "2048x1152" DotClock 156.75 HTimings 2048 2096 2128 2208 VTimings 1152 1155 1160 1185 Flags "-HSync" "+VSync" EndMode EndSection
Sanyo
Sanyo ViZZon DP42647 42" LCD
## Samsung Sanyo DP42647 42 inch LCD TV ModeLine "1280x720" 74.48 1280 1468 1604 1664 720 721 724 746 +hsync +vsync # If doesn't fill the screen, use the TV's aspect ratio to fix
Sanyo PLV Z4/Z5
## Samsung Sanyo PLV Z4 and PLV Z5 projector # DisplaySize 325 182 # For 1280x720 at 100dpi (16:9) # HorizSync 30.0 - 62.0 # VertRefresh 50.0 - 85.0 # Modeline "1280x720@60Hz" 73.78 1280 1312 1592 1624 720 735 742 757 # Modeline "1280x720@50Hz" 59.42 1280 1312 1536 1568 720 735 741 757
Sceptre
Sceptre X37SV-Naga
## (37" 1920x1080 60Mhz native resolution LCD) ## Using Nvidia FX5200 DVI->HDMI cable connected to the LCD ## I had to use the following options for any modes greater than 1280x1024 to work when using the DVI->HDMI ## output, I didn't need these options for VGA output to the LCD. # Option "ModeValidation" "NoMaxPClkCheck, NoEdidMaxPClkCheck" # Option "UseDisplayDevice" "DFP" # # Modeline for the LCD's native resolution # ModeLine "1920x1080p"<PHONE_NUMBER> 2024 2072 2200 1080 1084 1094 1124 -hsync -vsync
Sharp
Sharp LC-37D65E
Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 30.0 - 82.0 VertRefresh 60.0 - 76.0 # 1024x768 @ 60Hz (VESA) hsync: 48.4kHz ModeLine "1024x768_VESA" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync # 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz ModeLine "1280x1024_VESA" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync # 1360x768 @ 60 Hz (EDID) HSync: 47.7121 kHz ModeLine "1360x768" 85.50 1360 1424 1536 1792 768 771 778 795 -Hsync -Vsync EndSection
Sharp LC-37D6U
# Modeline "1080x680" 79.68 1080 1492 1532 1752 680 722 724 758
Sharp LC-40C32U
## with ubuntu edgy's x.org and the nvidia 8776 drivers, a simple mode of "1360x768" works without ## the custom modeline #Section "Monitor" # Identifier "Sharp LC-40C32U" # HorizSync 24-62 # VertRefresh 49-76 # # modelines from the web generator at # http://xtiming.sourceforge.net/cgi-bin/xtiming.pl # Modeline "1360x768@60" 84.50 1360 1392 1712 1744 768 783 791 807 # # EDID-derived modelines # ModeLine "1360x768@60" 85.5 1360 1424 1536 1792 768 771 777 795 +hsync +vsync #EndSection
On Fedora Core 6, with the nVidia 9746 driver, the following will work for 1360x768 mode using a DVI connection:
Section "Monitor" Identifier "Monitor0" VendorName "Sharp" ModelName "LC-40C32U" Option "ModeValidation" "NoDFPNativeResolutionCheck" Option "DPMS" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1360x768" "1024x768" EndSubSection EndSection
The monitor sends back an inaccurate maximum DFP size, making it necessary to disable the native resolution check.
NOTE: This TV requires that you manually select a 1360x768 input signal through the on-screen menu. See your TV's manual for details.
Sharp LC-46D64U
ModeLine "1920x1080@65"<PHONE_NUMBER> 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
Sharp LC-46D92U
Using the nvidia binary drivers version 9746. Outputting 1920x1080 over DVI to the display. Graphics card is a GeForce 6600 with 256MB of VRAM.
This is the same modeline as the Vizio GV47L and I got it from this wiki. So thanks to the person who put it there.
I had to disable native resolution check because the EDID information returned by the display was reporting a max resolution of "1280x1024". This configuration is also known to work on the Vizio VS42LF. Here is the Monitor section:
Section "Monitor" Identifier "Sharp LCD HDTV" ModeLine "1920x1080_60-Sharp_D92U" 148.35 1920 2008 2052 2200 1080 1085 1090 1125 +hsync +vsync Option "ExactModeTimingsDVI" "TRUE" Option "ModeValidation" "NoDFPNativeResolutionCheck" EndSection
Sharp LC-37X20E
Running an Nvidia 6150 onboard graphic @ 1920 x 1080 (MSI MS-7329, Media Live). These setting were provided bei the WinXP Nvidia settings, which fixed my "black-bar-on-left-side" issue with (k)ubuntu. Settings with 50Hz looks almost similar as the LC-46X20E one's.
Section "Monitor" Identifier "Generic Monitor" Option "DPMS" Modeline "1920x1080" 148.5 1920 2448 2492 2640 1080 1084 1089 1125 +hsync -vsync HorizSync 20-500 VertRefresh 50-61 EndSection
Sharp LC-46X20E
Im using Onboard Intel X3100 graphic Card with Intel driver... EDID workes only for 50Hz, this Modelines enable 60Hz and 24Hz. Im using "xrandr --output TMDS-1 --mode 1920x1080@24 for switching...
Section "Monitor" Identifier "Sharp LC-46X20E" Modeline "1920x1080@24" 74.250 1920 2560 2608 2752 1080 1084 1089 1125 +hsync +vsync Modeline "1920x1080@50"<PHONE_NUMBER> 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline "1920x1080@60"<PHONE_NUMBER> 2008 2056 2200 1080 1084 1089 1125 +hsync +vsync EndSection
Sony
Note that some Sony models (e.g. KDL-46WE5) do not allow 50Hz inputs using the PC input (i.e. VGA DB15 connection). To get 50Hz modelines to work you must use an HDMI input- for example by using an inexpensive ($10) DVI to HDMI converter attached to your graphics card.
Song KDL-26S3000
# Nvidia 9500GT over HDMI with overscan correction for 720p at 50Hz for UK DVB Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "SONY TV" HorizSync 14.0 - 48.0 VertRefresh 48.0 - 62.0 Option "ExactModeTimingsDVI" "TRUE" Modeline "1280x720@50" 74.25 1216 1690 1730 1980 670 705 710 750 +hsync +vsync EndSection
Sony KDL-46X3100
# Device nVidia 9400GT, DVI->HDMI cable # Monitor section: ## This allows 1920x1080/24p 1920x1080/50p 1920x1080/60p (otherwise only 60Hz mode work) # Modeline "1920x1080@24" 74.250 1920 2560 2608 2752 1080 1084 1089 1125 +hsync +vsync # Modeline "1920x1080@50"<PHONE_NUMBER> 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync # Modeline "1920x1080@60"<PHONE_NUMBER> 2008 2056 2200 1080 1084 1089 1125 +hsync +vsync # HorizSync 20.0 - 150.0 # VertRefresh 24.0 - 90.0 # Option "ExactModeTimingsDVI" "True" # Option "UseEDIDDpi" "False" # Option "UseEDIDFreqs" "False" # Option "RenderAccel" "True" # Option "AllowGLXWithComposite" "true"
Sony KP-46WT520
# Device "NVIDIA Corporation NV18 [GeForce4 MX 440 AGP 8x]" # HorizSync 15.0 - 46.0 # VertRefresh 59.0 - 61.0 # Option "DPMS" # Option "IgnoreEDID" # ModeLine "1160x652" 74.48 1160 1208 1328 1664 652 653 656 746 -hsync +vsync
Sony KF-50WE610
## nVidia FX5200, DVI ## HorizSync 15.0 - 46.0 ## VertRefresh 59.0 - 61.0 # Modeline "1152x648" 74.2 1152 1288 1328 1648 648 689 694 750 +hsync +vsync
Sony KDF-E42A10
## You'll also need to add Option "IgnoreEDID" "true" to the Screen section ## since the TV incorrectly reports as 1920x540. ## For 1920x1080 I had to add ## Option "ModeValidation" "NoVertRefreshCheck" ## to the device section. Tested w/ FX5200 DVI -> HDMI using nvidia drivers. # ModeLine "1280x720" 74.25 1280 1390 1430 1648 720 725 732 752 +hsync +vsync # ModeLine "1920x1080" 74.25 1920 2008 2052 2200 1080 1088 1091 1121 +hsync +vsync
Sony KDF-46E2000
## Valid widescreen modes from the manual are 1280x768_60 and 1152x648_60 # Option "metamodes" "1280x768_60 +0+0; 1152x648_60 +0+0; 640x480 +0+0"
Sony Bravia KLV-S32A10E (KLV-S40A10E, KLV-S32A10E, KLV-S26A10E, KLV-S23A10E, KLV-S19A10E)
#Section "Monitor" # Identifier "KDL-S32A12U" # Option "DPMS" # HorizSync 31-60 # VertRefresh 56-75 # Modeline "1280x768" 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync #EndSection # #Section "Screen" # Identifier "Default Screen" # Device "VIA Technologies, Inc. VT8623 [Apollo CLE266] integrated CastleRock graphics" # Monitor "KDL-S32A12U" # DefaultDepth 24 # SubSection "Display" # Depth 24 # Modes "1280x768" "1024x768" # EndSubSection # EndSection
Sony Bravia KDL-26P2530
## I couldn't get the TV to display through HDMI properly - but this configuration works through VGA just fine ## Note: "UseEDID" "False" and "AllowNon60HzDFPModes" are only there as they seem to speed up the length of ## time it takes for the TV to display the signal; they are NOT required. # #Section "Monitor" # Identifier "KDL_26P2530" # VendorName "Sony" #EndSection #Section "Device" # Identifier "Card0" # Driver "nvidia" # VendorName "nVidia Corporation" # BoardName "NV41 [GeForce 6800 GS]" # BusID "PCI:1:0:0" # Option "UseEDID" "False" # Option "ModeValidation" "AllowNon60HzDFPModes,NoHorizSyncCheck" #EndSection #Section "Screen" # Identifier "Screen0" # Device "Card0" # Monitor "KDL_26P2530" # DefaultDepth 24 # SubSection "Display" # Modes "1280x768" # Viewport 0 0 # Depth 24 # EndSubSection #EndSection
Sony KDL-40W2000 (European model)
## 1080p native LCD ## For some reason the native 1080p modes were failing the validation due to incorrectly checking the maxpixelclock ## You need the "NoMaxPClkCheck" to get 1080p and "AllowNon60HzDFPModes" to use 50Hz (1920x1080_50) ## The last 3 are optional just to limit to EDID modes reported by the screen only ## ## Section "Device" ## Identifier "dev2" ## Driver "nvidia" ## BusID "PCI:1:0:0" ## Option "UseFBDev" "true" ## Option "ModeValidation" "NoMaxPClkCheck, AllowNon60HzDFPModes, NoVesaModes, NoXServerModes, NoPredefinedModes" ## Screen 1 ## EndSection
Sony KDL-40V2500
## I used DVI to HDMI on the HDMI input 6 (the one with RCA audio jacks). ## Make sure you have display area set to full otherwise you will be tricked into thinking you have overscan -- see pages 29 and 30 of the product manual on how to set to full ## The picture looks great from an nVidia 7600 GS ## #Section "Monitor" # Identifier "Monitor[0]" # VendorName "Sony" # ModelName "SonyHDTV" # UseModes "Modes[0]" # DisplaySize 320 180 # HorizSync 20.0 - 150.0 # VertRefresh 30.0 - 90.0 # Option "UseDisplayDevice" "DFP" # Option "IgnoreDisplayDevices" "TV, CRT" # Option "ExactModeTimingsDVI" "1" # Option "NoLogo" "0" # Option "UseEDIDDpi" "0" # Option "UseEDIDFreqs" "0" # Option "RenderAccel" "true" # Option "AllowGLXWithComposite" "true" # Option "ConnectedMonitor" "DFP" # Option "ModeValidation" #EndSection #Modeline "1920x1080p60" 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +Hsync +Vsync ## NOTE the 'Option "ModeValidation"' line with no args -- I had issues getting this mode to validate -- so this just seems to make all happy. ## NOTE DisplaySize is fudged to get a reasonably large font from X, if you use the real dimensions -- you will be doing alot of squinting...
Sony KDS-R60XBR1
## Make sure that you don't use the IgnoreEDID option becase it work with this option ## unlike some other Sony models. ## The picture is still does not fit perfect but pretty close. I am using 1152x648 now. ## HorizSync 31.5 - 37.9 ## VertRefresh 59.9 - 60.1 # ModeLine "1280x720" 74.2 1280 1390 1426 1646 720 725 727 747 +hsync +vsync # ModeLine "1920x1080" 74.2 1920 2008 2052 2200 1080 1088 1091 1121 +hsync +vsync interlace # ModeLine "1152x648" 74.2 1152 1288 1328 1648 648 689 694 750 +hsync +vsync
Sony KDL-40S2000
I am able to get the picture exactly as it is with XP under Ubuntu with these settings.
HorizSync 30-66 VertRefresh 30-61 Modeline "1360x768" 85.500 1360 1432 1544 1792 768 771 777 795
Sony KDL-32M3000
This works great for me with VGA cable connection.
Horizsync 31.5-48.0 Vertrefresh 56.0 - 65.0 ModeLine "1360x768" 85.500 1360 1424 1536 1792 768 771 777 795 +Hsync +Vsync
Sony KDL-40W4000
This works for me with a VGA cable connection, and an NVIDIA 9400, which really struggles with the EDID. It is, however, a bit of a sledgehammer...
Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "CRT-0" DisplaySize 884 495 HorizSync 31.5 - 64.0 VertRefresh 60.0 - 75.0 Option "DPMS" Option "RenderAccel" ModeLine "1920x1080" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 9400" Option "ModeValidation" "NoMaxPClkCheck, AllowNon60HzDFPModes, NoVirtualSizeCheck, NoEdidMaxPClkCheck, NoMaxSizeCheck, NoHorizSynCheck, NoVertRefreshCheck, NoWidthAlignmentCheck, NoExtendedGpuCapabilitiesCheck, NoTotalSizeCheck" Option "UseEDID" "False" Option "NoBandWidthTest" "True" EndSection
Sony KDL-40W4100
Thru HDMI the EDID info seems off by one count for HBlank_end. EDID specifies 2200 but using 2201 syncs the tv to native resolution. With fglrx driver, unfortunately EDID override is not easy. Using any predefined mode (1920x1080) seems to return the driver to EDID sync specifications. Working solution is to define a 1919x1080 modeline:
Section "Monitor" Identifier "KDL40W4100" HorizSync 15.0 - 70.0 VertRefresh 58.0 - 62.0 ModeLine "1919x1080" 148.50 1919 2030 2052 2201 1080 1084 1089 1125 +hsync +vsync Option "DPMS" "FALSE" Option "DPI" "100x100" EndSection Section "Screen" Identifier "Default Screen" Device "Configured Video Device" Monitor "KDL40W4100" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1919x1080" EndSubSection EndSection
Toshiba
Toshiba 42A3000A
## ATI 9250 AGB, DVI ## Have not figured out how to force Xorg to set it all up automatically so I have to use xrandr) ## 42 Inch widescree tv ## HorizSync 15-46 ## VertRefresh 49-61 # Modeline "1280x720" 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync # TV will start in lower resolution, Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz) # Script to run after logging on to my computer xrandr --output DVI-0 --newmode 1280x720 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync xrandr --addmode DVI-0 1280x720 xrandr --output DVI-0 --mode 1280x720 #If anyone knows how to configure xorg and force it to do this in xorg.conf, feel free to email me with info. #martin(youknowwhat)forest(d)gen(d)nz
Toshiba 42H83
## nVidia FX5200, DVI ## (obsolete by X.org-7.0 and NVidia-8774; 1280x720 built-in mode now works) ## DisplaySize 93 52 ## HorizSync 31-46 ## VertRefresh 59-61 ## Option "DPMS" # Modeline "960x540p" 40.86<PHONE_NUMBER> 1176 540 551 557 568 +HSync +VSync
Toshiba 52HM84
# overscan cannot be avoided from dvi/hdmi interface # Section "Monitor" # Identifier "Monitor0" # VendorName "Unknown" # ModelName "TSB-HM84s" # HorizSync 15.0 - 46.0 # VertRefresh 59.0 - 61.0 # Option "UseEDID" "FALSE" # ModeLine "1280x720_60" 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsync # EndSection # # to force the modeline when using kvm or monitor is off, add the following to Screen section # Option "ModeValidation" "NoEdidDFPMaxSizeCheck,NoDFPNativeResolutionCheck" # Option "ExactModeTimingsDVI" "TRUE" # Monitor section # Option "UseEDID" "FALSE"
Toshiba 50H81
## Connected through an Audio Authority Scan Converter (Model A960) ## *I have these settings to help protect TV if I play with other modes later: ## HorizSync 15 - 33.85 ## VertRefresh 29.9 - 60.1 ## Last revised Oct-2006 ## ## Use in540p for menus/mythplugins ( 880x480p ) ## Use 640x480p to playback SD recordings ( 640x480p ) ## Use 1080i for HD Content ( 1760x960i ) # ModeLine "in540p" 37.26<PHONE_NUMBER> 1104 480 506 520 563 +hsync +vsync # Modeline "640x480p" 26.964 640 704 768 856 480 486 492 525 -hsync -vsync # ModeLine "in1080i" 74.52 1760 1888 2096 2208 960 1012 1028 1126 -hsync -vsync interlace
Toshiba HD51
## Note: using an NVidia GeForce 6200 w/ Component Video dongle -- does not work with S-Video connected at the same time # Option "TVStandard" "HD720p" # Option "TVOutFormat" "SVIDEO" # Option "ConnectedMonitor" "TV" # Option "NoLogo" "True" # Option "NvAGP" "1" # # ModeLine "720p" 73.8 1280 1320 1368 1640 720 722 724 751 +hsync +vsync
Toshiba 56HM66 DLP
##Despite the manual stating it cannot be connected to a computer ## I have mythtv running in 720p (the native mode of the tv) using an NVidia fx5200 via dvi->hdmi cable Section "Monitor" Identifier "Monitor0" VendorName "Toshiba 56HM66" ModelName "56HM66" HorizSync 44.9 - 45.1 VertRefresh 59.9 - 61.1 Modeline "1280x720" 75.288 1280 1397 1445 1672 720 725 730 750 +hsync +vsync EndSection
Toshiba REGZA 52" 1080p LCD 52HL167
# Note: this assumes Nvidia video card connected via DVI->HDMI. These modes # are primarily useful if the TV is not on when X is started or # an HDMI switching receiver isn't set to the proper input when X # is started. Section "Monitor" Identifier "Monitor0" VendorName "Toshiba" ModelName "Toshiba REGZA 52HL167" # Connected via DVI (may not be able to detect if TV off otherwise) Option "ConnectedMonitor" "DFP" Option "USEEDIDDpi" "FALSE" Option "DPI" "100 x 100" # Necessary as if TV is not on, default Freqs are not right Option "UseEDIDFreqs" "FALSE" # Necessary otherwise states max size is 640x480 Option "ModeValidation" "NoDFPNativeResolutionCheck" # Necessary or cannot calculate timings errors Option "ExactModeTimingsDVI" "true" # Refresh timings as per EDID info on TV. Necessary if TV is off HorizSync 15.000 - 68.000 VertRefresh 23.000 - 61.000 # Modes taken from EDID of TV: # 1080p @ 60Hz ModeLine "1920x1080" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync # 720p @ 60Hz ModeLine "1280x720" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync # 480p @ 60Hz ModeLine "720x480" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync EndSection
ViewSonic
ViewSonic N2750w
## HorizSync 30.0 - 80.0 ## VertRefresh 50.0 - 75.0 ## Option "dpms" ## DisplaySize 325 182 # Modeline "1280x720" 75 1280 1336 1472 1664 720 725 730 75
ViewSonic N3251w (or ViewSonic N3760w)
## -- Monitor Section -- ## Actual native for the monitor is 1366x768, however my nVidia card requires it to be either ## 1360x768 or 1368x768. ## ## HorizSync 30.0 - 64.0 ## VertRefresh 60.0 - 75.0 # Modeline "1368x768" 85.478 1368 1424 1536 1792 768 771 777 795 +hsync +vsync ## -- Device Section -- # Option "IgnoreEDID" "True"
ViewSonic VG2230wm
# EDID derived values with 170 being the maximum pixel clock of my nVidia card. Section "Monitor" Identifier "Monitor-Center" VendorName "ViewSonic" ModelName "VG2230wm" DisplaySize 470 300 HorizSync 30.0 - 82.0 VertRefresh 50.0 - 75.0 ModeLine "1680x1050" 170.00 1680 1784 1960 2240 1050 1053 1059 1089 +hsync +vsync Option "dpms" EndSection
ViewSonic N4280p
#Mode line i got from powerstrip, very close to the ATSC1080 modeline - #couldn't get this to work with either at 9800pro or a X1600 (the X1600 did #work on a windows xp machine). Put a geforce 7600 in the machine and it works #like a dream. Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" HorizSync 30 - 64 VertRefresh 60 - 75 Modeline "1920x1024"<PHONE_NUMBER> 2008 2052 2200 1080 1084 1089 1125 +Hsync +Vsync #1920x1080 Display Size #DisplaySize 487 274 #this is nvidia specific -- Have to over ride this to get #it to use DisplaySize Option "DPI" "100 x 100" EndSection
Vizio
Vizio L37HDTV 37" LCD 720p (1360x768 PC)
# Note: this assumes Nvidia video card connected via RGB. # Could not get DVI/HDMI to work reliably on this screen without lots of overscan. # Tested on MSI NX7300LE-TD256EH GeForce 7300LE 256MB 64-bit GDDR2 PCI Express x16 Video Card. Section "Monitor" Identifier "Configured Monitor" Vendorname "VIZIO" Modelname "VIZIO L37HDTV" Horizsync 31-70 Vertrefresh 50-85 Mode "1360x768" # vfreq 59.815Hz, hfreq 47.553kHz Dotclock 85.500000 Htimings 1360 1494 1624 1798 Vtimings 768 770 776 803 Flags "-HSync" "+VSync" EndMode EndSection # Also added this for optimal performance Section "Screen" Identifier "Default Screen" Device "Configured Video Device" Monitor "Configured Monitor" Option "DPI" "100 x 100" Defaultdepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1360x768" EndSubSection SubSection "Display" Viewport 0 0 Depth 16 Modes "1360x768" EndSubSection SubSection "Display" Viewport 0 0 Depth 15 Modes "1360x768" EndSubSection EndSection Section "Module" Load "glx" Load "v4l" EndSection Section "Device" Identifier "Default Device" Driver "nvidia" Option "NoLogo" "True" Option "AddARGBVisuals" "True" # Important!!! need this option to use nvidia card at 1360 x 768 Option "NvAGP" "1" # Needed for ACPI suspend to RAM Option "AddARGBGLXVisuals" "True" Option "ModeValidation" "NoWidthAlignmentCheck" # Causes Screen tearing... # Option "TripleBuffer" "True" Option "UseEvents" "True" # Option "DynamicTwinView" "false" Option "CoolBits" "1" Option "NoFlip" "1" EndSection
Vizio VO22L 22" LCD 720p (1680x1050 PC)
# Note: this assumes Nvidia video card connected via DVI->HDMI. These modes # are primarily useful if the TV is not on when X is started or # an HDMI switching receiver isn't set to the proper input when X # is started. Tested on integrated GeForce 8200 MiniITX board. Section "Monitor" Identifier "Monitor0" VendorName "Vizio" ModelName "Vizio VO22L" # Connected via DVI Option "ConnectedMonitor" "DFP" Option "USEEDIDDpi" "FALSE" Option "DPI" "100 x 100" # Necessary as if TV is not on, default Freqs are not right Option "UseEDIDFreqs" "FALSE" # Necessary otherwise states max size is 640x480 Option "ModeValidation" "NoDFPNativeResolutionCheck" # Necessary or cannot calculate timings Option "ExactModeTimingsDVI" "true" # Refresh timings as per EDID info on TV. Necessary if # TV is off HorizSync 31.000 - 70.000 VertRefresh 50.000 - 77.000 # 720p @ 60Hz -- taken from TV modeline ModeLine "1280x720" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync # 1680x1050 @ 60Hz -- not provided by TV's EDID, but advertised native resolution. # Works and is the clearest resolution for fonts ModeLine "1680x1050" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 +hsync +vsync EndSection
Westinghouse
Westinghouse LVM-42W2 42" LCD
Section "Monitor" Identifier "Monitor1" VendorName "Westinghouse" ModelName "LVM-42w2" ### From /var/log/Xorg.0.log: ### # Supported additional Video Mode: # clock: 138.5 MHz Image Size: 930 x 520 mm # h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0 # v_active: 1080 v_sync: 1082 v_sync_end 1087 v_blanking: 1111 v_border: 0 # Ranges: V min: 50 V max: 75 Hz, H min: 30 H max: 80 kHz, PixClock max 150 MHz VertRefresh 50.0 - 75.0 HorizSync 30.0 - 80.0 ModeLine "1920x1080" 138.5 1920 1968 2000 2080 1080 1082 1087 1111 Option "DPMS" "true" Option "UseEdidDpi" "FALSE" Option "DPI" "100 x 100" EndSection
Westinghouse SK-32H240S (32" LCD)
This is an inexpensive 32-inch 720p HDTV set sold by several retailers. Also, it doesn't put out EDID information over the VGA port (maybe it does on HDMI).
Section "Monitor" Identifier "Monitor" VendorName "Westinghouse" ModelName "SK-32H240S" DisplaySize 710 401 HorizSync 30 - 49 VertRefresh 50 - 75 Option "DPMS" "True" Modeline "1368x768" 73.250 1368 1408 1440 1496 768 771 776 816 +hsync -vsync EndSection
Zenith
Zenith P60W26 60" Plasma
# Connected directly to the VGA input # Modeline "1280x720_70.00" 89.04 1280 1352 1488 1696 720 721 724 750 -HSync +Vsync
Others
AWA 81cm LCD
## AWA 81cm LCD ## HorizSync 30-80 ## VertRefresh 56-85 ## Option "UseEdidFreqs" "false" # ModeLine "1360x768" 84.6 1360 1424 1568 1776 768 769 774 795
Tevion or Medion 41427 (Aldi)
## Tevion or Medion 41427 (also sold as Aldi LCD) 60Hz modeline # Modeline "1280x720@60" 74.20 1280 1390 1430 1650 720 725 730 750 +hsync +vsync
Vizio GV47L
## Modeline for 1080p -- 1920x1080_60 for the Vizio GV47L # ModeLine "1920x1080_60-GV47L" 148.35 1920 2008 2052 2200 1080 1085 1090 1125 +hsync +vsync ## Nvidia drivers (at least the current 9746) require the following options in the card "Device" section of the xorg.conf file # Option "ExactModeTimingsDVI" "True" # Option "ModeValidation" "NoDFPNativeResolutionCheck"
Vizio l47
This modeline gets my l47 displaying 720p correctly:
Modeline "720p" 82.61 1368 1424 1579 1754 768 770 757 793 +hsync +vsync # WORKS
Polaroid (Proview) FLM-3232
No modelines are really necessary for this one over the VGA. Here are the relevant xorg.conf pieces to display at the max resolution of 720p:
Section "Monitor" HorizSync 30.0 - 81.0 VertRefresh 56.0 - 75.0 Identifier "Monitor0" VendorName "Polaroid" ModelName "FLM-3232" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "XFX" BoardName "XFX nVidia GeForce 6200" Option "RenderAccel" "1" Option "NvAGP" "2" Option "NoLogo" "true" Option "UseEvents" "True" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1920x1080_60" "1280x720_60" "720x480_60" # 1080p 720p 480p EndSubSection EndSection
Tatung 32" 81cm HDTV
# Scaling by the DFP, ModeLine necessary, plus validation checks switched off: Section "Monitor" Identifier "Mon1" HorizSync 15.0 - 46.0 VertRefresh 49.0 - 61.0 ModeLine "1920x1080" 74.250 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync # Option "DPMS" EndSection Section "Device" Identifier "NV2" Driver "nvidia" Option "AddARGBGLXVisuals" "True" Option "DisableGLXRootClipping" "true" Option "NoVertRefreshCheck" Option "ModeValidation" "NoVertRefreshCheck,NoDFPNativeResolutionCheck,NoEdidMaxPClkCheck,NoHorizSyncCheck,NoMaxPClkCheck" Option "UseEDIDDpi" "false" Option "ExactModeTimingsDVI" "true" Option "FlatPanelProperties" "Scaling=Native" BusID "PCI:5:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen1" Device "NV2" Monitor "Mon1" DefaultDepth 24 Subsection "Display" Depth 24 Modes "1920x1080_60i" # "1280x720" "640x480" ViewPort 0 0 # initial origin if mode is smaller than desktop EndSubsection EndSection
Ventura Wide
Modelines to run the full resolution of 1366x768, on a Ventura Wide panel. In Denmark sold by Mermaid Computers.
## Modeline for 1366 # ModeLine "1366x768" 85.9 1366 1438 1626 1798 768 769 772 795 +hsync +vsync ## Nvidia drivers require the following options in the card "Device" section of the xorg.conf file # Option "ExactModeTimingsDVI" "True" # Option "ModeValidation" "NoWidthAlignmentCheck, NoDFPNativeResolutionCheck"


You're going to give some random person money to become a millionair. This person will spend it on cars or...cars. Really, this money will be waisted. Don't do it.
Seriously, don't buy these tokens.
 After the 1 million dollar homepage was redone in cryptoland. This had to happen. This will be history. At least your money will be. The grind for money continues. Crypto this crypto that. Kitties here. Punks there. Let's reinvent the world on the blockchain! You fell for an ICO trap and will not fall for this one as well. This ICO is honest and useless. Do not invest.
The MDT ICO transparently offers investors no value, so there will be no expectation of gains. No gains means few investors, few investors means few transactions, and few transactions means no Ethereum network lag—not to mention no depressing posts on /r/ethtrader about people losing all their savings!
Might be secure, definitely not audited
I learned all about Ethereum in a few hours, copied here and there. Copied all mostly. But hey, aren't most ICO's?
Also, I definitely didn't have any smart contract experts look at the contract before I launched it. I mean, why bother? All the other ICOs go through weeks of auditing and they still end up with bugs and vulnerabilities in their contracts.
Guaranteed token value
Unlike with every other token sale on the market, I can guarantee here and now that the value of MDT will not (in fact, can not) reduce during or after the ICO. Since these tokens aren't worth anything to start with, there's nowhere to go but up!
But remember—this is a completely honest ICO, which means I don't want anyone to mistakenly expect the value of the tokens to go up, either.
The crowdsale started on:
Jan 2nd, 2018 at 2:00 P.M. UTC
and will run until:
$1,000,000 worth of ETH is contributed
(or until I feel like ending it)
To participate in the MDT ICO, just send as much Ether as you want to the MDT token/crowdsale contract. Make sure you provide enough gas for the transaction—100,000 or so ought to do it.
0x9d1e27d75622cc16e35efb482cfbfa987da331a9
The more Ether everyone contributes, the more tokens you get.
The base token distribution formula is very simple: for every 1 ETH you contribute, you'll receive 100 MDT, and if you contribute at least 0.01 ETH, you'll also receive an additional 1 MDT for every Ether that's been contributed in total. Like this:
| Transaction | Ether sent | Total Ether sent | MDT received |
|---|---|---|---|
| #1 | 1.000 ETH | 1.000 ETH | 101.000 MDT |
| #2 | 3.000 ETH | 4.000 ETH | 304.000 MDT |
| #3 | 0.005 ETH | 4.005 ETH | 0.500 MDT |
| #4 | 0.500 ETH | 4.505 ETH | 54.505 MDT |
Every block has a 1 in 256 chance of issuing bonus tokens.
When purchasing MDT, the smart contract will take a hash of the current block's coinbase, number, and timestamp. If the first byte of the hash is 0x00, the block becomes a bonus block. During a bonus block, the smart contract counts the number of bits set in the second byte of the hash and uses that number as a bonus multiplier.
Every MDT purchase of at least 0.01 ETH worth during the bonus block will receive, in addition to the base distribution, an additional 100 MDT per Ether multiplied by the bonus multiplier. That means that contributors have a chance of receiving a total of nine times the number of tokens they expected!
Wait… is this another joke? Is it a scam?
Neither! This is real—and it's 100% transparent. You're literally giving your money to someone on the internet and getting completely useless million dollar tokens in return.
There are no “whitepapers,” no “products,” and no “experts.”
Why are you doing this?
Who knows? Maybe it's because I lost money in the GDAX flash crash. Maybe I got inspired by the guy who crowdfunded the potato salad. Maybe I'm just way too bored and need a better hobby.
What can I do with MDT?
MDT is a standard ERC20 token, so you can hold it and transfer it.
Other than that… nothing. Absolutely nothing.
(Seriously, don't buy this. Why are you even still reading these?)
Will MDT be traded on any exchanges?
I hope so. You have no idea how much I hope so.
In fact, if it does get picked up by any of the major exchanges, I promise to use some of the ICO proceeds to constantly and incessantly manipulate the market.
Will there be more chances to buy MDT?
That's a great question! It totally depends on how the ICO performs in the beginning. If I don't make enough money to buy at least one car, I'll probably keep the ICO open longer than initially stated.
How do I get a refund for the tokens I bought?
You're kidding, right?


| Up | TOC | Index | |||||
| << 8 API Reference | < 9.31 Version 2.2 WIN32+DOS32 January 14, 2000 | Up: 9 Release Notes | 9.33 Version 2.2 Linux November 22, 1999 > | 10 Index >> |
9.32 Version 2.2 Beta WIN32+DOS32 December 23, 1999
Most of the new library routines developed for Euphoria 2.2 on Linux, have now been ported to WIN32 and DOS32. These are: sleep(), chdir(), flush(), lock_file(), unlock_file(), crash_file(), get_screen_char() and put_screen_char(). For a description of these routines refer to the Linux release notes below, or LIBRARY.DOC.
Some cross-platform bug fixes and other miscellaneous improvements were made during the Linux port. These bug fixes and improvements have now been ported back to WIN32+DOS32. See the Linux release notes (below).
In addition, the following improvements have been made specifically for WIN32 and DOS32:
- exw.exe now contains a Euphoria icon that is displayed automatically by Windows. The icon was contributed by Gary Dumer. Registered users may change this icon when they bind a program.
- exw.exe is now a compressed executable of just 73K (or so). It's compressed using the UPX compression tool for .exe files.
- ex.exe has been updated with the latest release of the CauseWay DOS extender. A problem where CauseWay would sometimes limit you to 64Mb of memory under some DOS configurations has been eliminated, and a few other minor bugs were fixed.
- bug fixed: The error traceback could sometimes crash or be misprinted when a type_check failure occurred. It could only happen when 1 was added to an expression, and the non-integer result of the expression was assigned to a variable declared as integer.
- bug fixed: If text_rows() was called as the first routine needing a WIN32 console window, Euphoria would fail to set the new number of lines of text on the console.


PUT /gists/:gist_id/star
Note that you'll need to set Content-Length to zero when calling out to this endpoint. For more information, see "HTTP verbs."
Content-Length
Status: 204 No Content


This application has been created as bachelor's thesis at Brno University of Technology, Faculty of Information Technology.
This version is more or less experimental and has only limited functionality.


Unless I'm mended very soon, I'm scared I might fall off.


an interactive chinese learning tool
Chinese the Right Way uses interactive lessons and toys to make the learning experience more engaging and interesting for students.
Flashcards, dice, quizzes, and other activities are used to break up the monotany of memorizing characters by rote. Students can create accounts to track their learning process, bookmark activies for later, and request help from their peers and volunteer teachers.
One proble with learning the Chinese language as a westerner is the perceived difficulty of the written language. Chinese the Right Way aims to alleviate the stress of learning the Chinese language by making lessons fun, easy, and interactive.
For millenia, Chinese natives have learned Chinese through herriatage, tradition, and stories. Chinese the Right Way aims to bring those traidtions and stories to the west so more people can learn Chinese. Chinese the Right Way uses an emphasis on traditional learning strategies and storytelling in order to make the Chinese language fun and easy to learn.
This webservice is developed by Cody Lee with the guidance of Mercer University's Dr. Martin Zhao. The website is provided "as is" to help other students develop their chinese skills.
Data is pooled from public sources such as HanziDB or Unihan to increase the amount of information provided. Other content is developed internally to supplement the learning experience.
Chinese the Right Way includes lessons and books written by Dr. Martin Zhao which will help new learners not only learn about the written and oral aspects of the Chinese language, but also enrich the student's understanding of Chinese culture.


Sunday 1 March 2020
by Simon Hall
Problem Solving
So I had this problem...
Problem solving in code is difficult at times. I have a method that I trust for solving problems but the code itself, or more accurately, my beginner level of understanding of the language, can compound the problem.
For example while doing the katas I needed to write a function that would return a specific value. I approached the problem in my typical way which is this:
Understand the problem
The first thing to do is to get to the root of the problem. What is it specifically that you're trying to achieve and why? There is no point working on a difficult problem that could be resolved by solving an earlier much simpler problem!
In my particular case the problem was an exercise that was written for me so understanding the problem was a matter of reading the instructions and paying attention to the test results after each successful prior solution.
Planning
What are the ways this problem can be solved. I do this with a pen and try to think about the problem in a number of different ways and come up with either a really simple solution, or for bigger problems I will come up with many solutions that come at the problem from different angles.
It's important to write these solutions down and test them out with some initial planning. In coding problems this is what developers call psuedocode. It's writing in plain language what you want the code to do step by step.
For the problem that I was trying to solve I needed to write a function that took an array of numbers and returned an array with only even numbers. I planned this out that I would need to filter the array so that it only kept numbers that had no remainder when divided by two. This was simple enough.
Research
If I'm confident of a solution I might skip this step but typically I like to research to see if someone has had the same problem and if someone has already solved it.
This can often provide rewards in a number of ways as well as risks. I could find someone that has already solved the problem in an elegant way. I could find someone that has tried the solution that I'm about to try and had problems with it that I don't foresee. Or it might yield no particularly useful information.
The risks of research is that I don't always understand what I'm looking at in a solution. I can find a solution that appears to solve my particular problem. Then it can take me a bit of time researching the parts of the solution to see how and why it works only to find out that it won't actually work in my situation.
I limited my research for this problem to reference resources only. I didn't want to find someone else's solution, the point was to create my own. I still conducted research though but focused on learning about the different methods available to me in building my function.
Try something
A big part of problem solving is to try something. Try a solution see if it works. If necessary use the results of your attempt to inform future attempts.
This is a fun part of problem solving. It works best though if you've done a bit of planning and thinking first.
My solution made sense. The research said it would work. But it wasn't passing the test. This was frustrating. Very frustrating.
Review
Taking what you've learned start the process again. Identify the problem, plan, research, try something...etc.
This is where I solved the problem. I looked back at the start. What is the problem, what am I trying to do. I want to return an array...wait a minute! My function isn't returning anything!. I typed a line to return the resulting array from my function and SUCESSS!!!! (This is the most fun part of problem solving).
Take a Break!
Sometimes spending too much time on a problem prevents us from seeing something that can be really obvious. Already there have been two occassions where I've been unsure how to solve a problem and after spending an hour or so on it will walk away and come at it fresh in the morning only to sovle it in five minutes. Taking time to let your brain restructure itself and consolidate your learning from the attempts you have already made to solve it can help you solve it. If it's a big enough problem you might even work away at it for years before coming up with a solution.
Which brings us to the final point...
Stickability
Sticking at a problem until it is solved. Einstein didn't consider himself a genius or smarter than anyone else. He said he's just better at sticking at a problem longer. This is about adopting that growth mindset and knowing you can do it, you just haven't done it YET!!


2019 Wallace Stevens
Poem Broadside
For the 56th Annual Wallace Stevens Writing Program, Design Center Studio designed the annual limited-edition letterpress broadside. The poetry piece for the 2019, 56th Edition was written by Claudia Rankine, an acclaimed author and poet. The untitled piece of prose poetry speaks about the narrative between two people. In order to give voice and authority to the poem, abstract imagery was used to reference a conversation without detracting from the prose.
This broadside design won a Gold Award at the 44th Annual Award Show of the Connecticut Art Director's Club.


{% extends 'templates/checkout/preview.html' %} {% block payment_method %}
Payment will be taken with GoCardless


Home
Mammals
Birds
JavaScript
The mammals of New Zealand
Click a category on the top nav bar for another class, or click a picture for more information.


Class that evaluates a poker hand to see if it has won or lost
| Constructor and description |
|---|
Evaluator
() |
| Type | Name and description |
|---|---|
boolean |
checkFlush(Hand hand) |
boolean |
checkFourKind(Hand hand) |
boolean |
checkFullHouse(Hand hand) |
boolean |
checkJacksOrBetter(Hand hand) |
boolean |
checkPair(Hand hand) |
boolean |
checkRoyalFlush(Hand hand) |
java.lang.Integer |
checkSize(ArrayList cards, int sizeToCheck) Returns the number of cards that whose values show up in the hand multiple times |
boolean |
checkStraight(Hand hand) |
boolean |
checkStraightFlush(Hand hand) |
boolean |
checkThreeKind(Hand hand) |
boolean |
checkTwoPair(Hand hand) |
Map |
evaluate(Hand hand, int round) Cycles through all the check functions to see if the game should pay out for a win. |
ArrayList |
ordinalHandler(ArrayList<Map> cards) Retrieves the numeric value of each card. |
ArrayList |
suitHandler(ArrayList<Map> cards) Retrieves the suit of each card. |
| Methods inherited from class | Name |
|---|---|
class java.lang.Object |
java.lang.Object#wait(long, int), java.lang.Object#wait(long), java.lang.Object#wait(), java.lang.Object#equals(java.lang.Object), java.lang.Object#toString(), java.lang.Object#hashCode(), java.lang.Object#getClass(), java.lang.Object#notify(), java.lang.Object#notifyAll() |
Stores the payout chart and descriptions.
Returns the number of cards that whose values show up in the hand multiple times
sizeToCheck
- the number of matches to check for.Cycles through all the check functions to see if the game should pay out for a win. Starts from the end of the results array to make sure the highest possible payout is used.
Retrieves the numeric value of each card. Groovy's collect closure tells the cards ArrayList that on every card, run the code get("value"), collect those items into a list and return it.
Retrieves the suit of each card. Also uses Groovy's collect closure.
Groovy Documentation


| Module | SoftwareHeretics::ActiveRecord::SimplyVersioned::VersionsProxyMethods |
| In: |
lib/simply_versioned.rb
|
If the model instance has more versions than the limit specified, delete all excess older versions.
# File lib/simply_versioned.rb, line 170 170: def clean_old_versions( versions_to_keep ) 171: find( :all, :conditions => [ 'number <= ?', self.maximum( :number ) - versions_to_keep ] ).each do |version| 172: version.destroy 173: end 174: end
Get the Version instance corresponding to this models for the specified version number.
# File lib/simply_versioned.rb, line 152 152: def get_version( number ) 153: find_by_number( number ) 154: end


Over the last few months, Jonathan had been involved in many of his friends’ and families’ weddings. All of them were using Microsoft Excel to manage the administrative side of things, such as keeping track of the RSVP from guests, managing the guest list for multiple events (wedding ceremony, wedding dinner, wedding reception) etc.
However, as most of them were not very experienced with Excel, many had trouble managing their wedding plans efficiently. Having multiple spreadsheets containing overlapping information caused some of them to get confused, resulting in errors and mere frustration.
Thus, we have decided to help to-be-wed couples by making an easy-to-use web app as our Orbital project. It will help them manage guests and events list with greater ease, removing the need for over complicated Excel spreadsheets.