[Solved] Minimalist setup with no video tearing

Hello all,
I maybe jumping the gun a bit here (as I still have other issues with flash and can't really test properly - see here), but here goes.
After lots of reading and experimenting, I came to the conclusion that I really like the minimalistic approach of using Openbox and adding stuff as I need (Tint2 etc.).
However, It also came clear pretty soon that should I want to make things look a bit nicer (that is, using some sort of composite manager), I will most likely end with screen tearing to some degree, using one of the non-opengl composite managers (xcompmgr, cairo commgr, compton).
That is when I came across the option of using Compiz as a standalone WM, with no DE, which should solve the problem of tearing and still remain pretty minimalistic.
Compiz, however, if I understand correctly, is going through some development "difficulties" this days (mainly used in-house by Ubuntu).
Bottom line, my options, as I'm aware of, are:
1. Openbox + no composite manager - should have no tearing, as minimalistic as it gets, a bit rough.
2. Openbox + some composite manager (most likely compton) - will probably have tearing, still minimalistic, a bit nicer.
3. Compiz 0.8.8 from repos - not sure, actually, except from the fact that I will probably not have video tearing and that it's a bit outdated as the 0.9.x line is considered stable by Canonicial.
4. Compiz 0.9.7 (or 0.9.x should I feel adventurous) - I think I've read somewhere the 0.9.x line isn't really suited to be used as a standalone WM, something to do with the absence of Emerald (not too sure, though).
Any input regarding those 4 options is highly appreciated, Adam.
Last edited by adam777 (2012-06-05 21:36:30)

Doesn't matter what video card you have. OpenGL is OpenGL. Older cards support older versions of it, but it should still be enough for basic desktop effects.
I was thinking of using a script that kills (or pauses) the composite manager if the media player window is fullscreen, since video tearing is more noticeable in fullscreen videos than windowed. Maybe adapt this script? Bah. I'm too lazy... Right now I can't be bothered with eye-candy. I used to have the tint2 clock set to right click and left click. One killed xcompmgr and refreshed the desktop and the other one started it, and restarted tint2 (for the true transparency to kick in). It's doable but I kinda gave up on it and went with vanilla Openbox + pseudo-transparency in tint2, guake and aterm because that's the only 3 programs that I wanted transparency in. And I can live without shadows. Easier on the resources too.

Similar Messages

[SOLVED]Radeon R9 280x Glamor problems (video tearing, error messages)

When switching from Catalyst to xf86-video-ati, a few problems occurred.
I tried to enable EXA rendering by setting the option in my Xorg.conf, but I got the message that EXA isn't supported on my card and that Glamor will be used. I'm fine with using Glamor, but using it gives me some weird problems. For instance, when I play a video, the top 5% of the screen has horizontal tearing, as explained in this bug report: https://www.libreoffice.org/bugzilla/sh … i?id=78717
It seems unfortunately that there is no way to solve the video tearing problem with Glamor. I tried playing my videos with mpv and vlc and with different video output options (xv, gl-hq, gl, vdpau), but they all gave horizontal tearing in the top 5% of the screen.
When playing a video or running glxgears, I get the following error messages:
radeon: Failed to allocate a buffer:
radeon: size : 0 bytes
radeon: alignment : 4096 bytes
radeon: domains : 4
And this goes on and on when running the program.
There are also messages appearing in dmesg when those problems occur:
[ 1587.499789] [drm:radeon_gem_object_create] *ERROR* Failed to allocate GEM object (0, 6, 4096, -22)
[ 1587.516597] [TTM] Illegal buffer object size
[ 1587.516606] [TTM] Illegal buffer object size
My full xorg.log:
http://pastebin.com/Jpi3wF7H
I understand that solving tearing is not a priority now with Glamor, but at least I want to get rid of the error messages. Any ideas?
lspci reports my card as:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
The card that I use is this one http://www.sapphiretech.com/presentatio … 2022&lid=1 , the SAPPHIRE DUAL-X R9 280X 3GB GDDR5 OC
Last edited by robin007bond (2015-01-26 15:17:46)

dpcismael wrote:
Sorry for the late reply, but I happen to have recently built a similar setup (Arch Linux + Radeon R9 280) and I'm also getting the "Failed to allocate a buffer" (of size 0) messages whenever I run something that seems to use the radeonsi driver (i.e. games, 3D, shaders...). However, I do not have the video tearing issue, and I don't get the messages when playing a video either (well, at least not with VLC, which is the only software I've tried for this). I can't really help you more with the video tearing issue, but I filed a specific bug report for the "Failed to allocate a buffer" messages here :
https://bugs.freedesktop.org/show_bug.cgi?id=82783
Thanks for reporting the bug! I hope that there'll be a solution for both of us.
Good to hear that you don't see tearing. It only happens on fast sequences.
An example:
https://www.youtube.com/watch?v=HU8CYlqoQJQ (in VLC)

Newbie with a Motif ES8 - optimum setup with a minimalistic approach?

hi,
I'm trying to decide on the optimum setup with a minimalistic approach!
I a newbie with the Motif ES8 and am at cross roads deciding on the type of computer setup for my VST.
PC + Cubase vs. MAC + Logic Pro or Logic Pro Express?
With MAC, how far do I need to go;i.e. MACBook Pro a must?
how many USB ports (types 400 vs 800), etc?
With Logic Pro, is Express going to be sufficient for a full soup to nuts recording and mastering given that this is for a home studio setup though with an idealist running it?
I'm a one woman show and so don't need too many inputs/outputs. I'd be recording a track at a time and my songs take up less than 16 tracks.
I would really appreciate any and all responses.
Roya
macbook pro Mac OS X (10.4.7)

thanks for the detailed response PK
so, the extra USB port on the HD would facilitate a
hub type interface i.e. once you hook up another\
device to the HD via USB, you're really hooked up to
the computer.. right? and so, if I get a powered USB
Hub, this wouldn't really matter.. correct?
For the most part, you have to be careful hooking
too many devices up to a computer WHEN you are trying
to do some sound work. When they say a computer
can do ABC we sometimes think that should include D.
As for the sound interface, I already have an
Audiophile that has midi in/out, firewire to
computer, RCA jack for i/o. I know its not the high
end stuff but I hope to do a stepwise upgrade here if
at all possible..
That actually might work, if it supports at least
16 bit 44.1 khz that is the lowest you want to go.
Ideally it should be 24 bit to take advantage of Logics
24bit environment. You might be able to run the ES8
straight into those RCA jacks if they are SPDIF and your
keyboard has the same on the back.
There are a bunch of people on Motifator discussion
groups that warn against Apple's lack of support for
Logic. Not sure if the concern is only regarding the
combination of Yamaha (Motif) and Apple (Logic).
I went and read that thread, here are some of my thoughts
on some of this.
Can't comment on MAC, but a dear friend of mine who is an audio engineer said >he had walked away from Logic after Apple bought them out. "Straight downhill" >I think is how he put it.
Many windows users just hate Apple and their products.
I think much of it is ignorance. They will say
Macs are junk but when I ask them why
they never have an answer or say something
that is false. It sounds like this "professional"
did not even wait to see that Logic did get better.
Apple charges 200.00 for support of it's Professional
applications. You really do not need it since there are
so many experienced Logic users here that I never had
a question go unanswered. I've noticed on those forums
the same small group of people do most of the problem
solving. I am not overly impressed with Yamaha's support.
I had my questions about my keyboard answered quicker
by those forums. So I guess both companies need work
in this area. Frankly, for recording, I think the Motif
and Logic are a Killer combination. Both have steep
learning curves but once you get up to speed I think
the results speak for themselves. The main difference
in my opinion is that the Motif is the ultimate
performance tool and Logic is the ultimate studio toolshop.
After having a Motif for over a month, I am convinced
it has a steeper learning curve than Logic take for instance
that thread on getting your keyboard to record it's own
audio output. The list of things to do each time is as long
as my arm. In case you did not read it here it is.
First thing – STORE your MIX setup and SAVE the Song to SmartMedia (or USB mass storage device) before resampling it so you have a backup. You would create a mix to balance the instruments the way you like them.
* Select a target track, then press the [INTEGRATED SAMPLING] button.
Setup the parameters for resampling:
* Press [F1] DEST
* Select a TRACK and [KEYBANK] (note) into which you will record the resampled data. You can target either an empty track or the track on which you are going to play (if you are going to play along). If all tracks are full, don't worry, you can still resample anyway.
* Press [F2] SOURCE. Set the source parameters as follows:
- Type = Sample - with this type the Integrated Sampling Sequencer will not create any NOTE-ON data in your sequencer, it will just simply add a new sample waveform to the waveform list
- Source = Resample
- Mono/Stereo = Stereo
- Next = OFF
- Frequency = 44.1k
* Press [F6] REC This will place the sampling sequencer in Standby mode. Set the TrggrMode paramter to Manual
* Press Start on the sequencer and check your levels. If too low set the REC GAIN higher +6bB or +12dB, if the level is to high (clipping- you will see a lightning bolt) lower the GAIN to -6dB or -12dB. When you have checked the levels, press STOP and return to the top of the SONG.
* Press F6 REC to start the Resample, Press [>] (play) to begin recording the resample. The Motif ES will draw the wave as it samples.
* When the song is over press [F6] STOP. The Motif ES will take a few moments to gather the data.
To create the .wav file:
* Press [FILE]
* Press [F1] CONFIG
* Press [SF1] CURRENT
* If you will be saving the resampled song to a SmartMedia Card set the Current parameter to CARD. To save to a USB device, set this parameter to USB
* Press [F2] SAVE
* Set the data TYPE field to WAV
* Cursor down and Name the wave
* (If desired, navigate to the subdirectory where you want to save the *.wav file.)
* Press [ENTER]
* The ES will ask you which TRACK and NOTE to save as a wave file. Enter the values you selected as the sample destination in the procedure above.
* Press and hold the AUDITION button to make sure your sample is there.
* Press [ENTER] and the Motif ES will export the sample as a .wav to your SmartMedia card or USB device.
Once you have configured Logic which are takes about
3 minutes (and only has to be done once)
and set up the keyboard which takes 30 seconds.
(this has to be done once for each session)
you plug your keyboard into your audio interface then
Hit Record
that is the whole list, two words.
Once it is in Logic, you have many way to edit it
and process if needed. The midi is much
easier to manipulate and there are more
ways than the ES has keys. Plus you can add to the
sounds with the internal instruments which are
as sophisticated and as high quality as the ES.
Then if your happy with it you can create MP3's
and burn Red book compliant CD's for
commercial duplication.
It really is a complete setup.
But at any rate I'm going to do some more research on
another scenario, i.e. what about MAC and Cubase? As
you may know Yamaha just acquired Cubase..
I dont think I would be the best to comment on that.
Maybe ask one of the Gurus on the unofficial
website for Cubase, The Cubinator.
Sorry, I just couldn't resist.
you've been very helpful - thanks again
cheers,
Roya
Cheers!
P.S. I agree with Dave, If you have a Macbook
Pro you dont need another computer. If you
wanta desktop whatever reasons I understand
Oh and btw, what's QWERTY?
They are the first 6 keys (top row/left to right)
on your computer keyboard

It's all green with xf86-video-ati. [Solved]

Firstly, I am running an updated install of Arch with KDE. My graphics card is an ATI Radeon HD 4800
After following the directions on the wiki (http://wiki.archlinux.org/index.php/ATI), my entire screen is shaded dark green. I can see things through it, bit it makes changes difficult.
Before the problem, I enabled early start KMS as per the directions, this did not seem to affect anything after a restart or two.
I moved on to generating a xorg.conf file using HWD and configuring it to use xf86-video-ati. Upon running hwd -x, I found it odd that it only generated a xorg.conf.mesa file, but assumed that I could make the changes that I wanted myself. I made a copy of the generated configuration file and named it xorg.conf and began editing. At this point in time, my computer was green screen free. The default generated config file worked fine using mesa, but I wanted to utilize my GPU. I found the "Devices" section and commented out:
Driver "vesa"
and added
Driver "radeon"
This is where my problems began. Upon rebooting, I was presented with a green KDM. Logging in or switching consoles did nothing to save me from my newly made green Frankenstein computer. So, I renamed my xorg.conf file to xorg.conf.bak and rebooted. Everything was back to normal (no green, no xorg.conf). I checked my Xorg.0.log file, but couldn't make out any errors. I've included my xorg.conf file as well as my the last part of my log file to aid anyone brave enough to do battle with the green. It would be great if anyone could help me out with this, I think that I'm a bit in over my head. Also, I would use the proprietary catalyst drivers, but they don't yet support the newest version of xorg that I'm running. I've tested the catalyst drivers in other installs and the GPU works perfectly, so I'm positive that it isn't a hardware problem.
If there is any more information that I can provide, just let me know.
xorg.conf
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
# Serial Mouse not detected
# USB Mouse not detected
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "AutoAddDevices" "False"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
# Load "synaptics"
Load "drm"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 28.0 - 96.0 # Warning: This may fry old Monitors
VertRefresh 50.0 - 75.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
#Driver "vesa"
Driver "radeon"
VendorName "All"
BoardName "All"
Option "AccelMethod" "EXA"
Option "RenderAccel" "on"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Xorg.0.log (not complete)
Dac detection success
(II) RADEON(0): Output: DVI-1, Detected Monitor Type: 0
Unhandled monitor type 0
(II) RADEON(0): EDID vendor "SAM", prod id 292
(II) RADEON(0): Using EDID range info for horizontal sync
(II) RADEON(0): Using EDID range info for vertical refresh
(II) RADEON(0): Printing DDC gathered Modelines:
(II) RADEON(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 30.24 640 704 768 864 480 483 486 525 -hsync -vsync (35.0 kHz)
(II) RADEON(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
(II) RADEON(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
(II) RADEON(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz)
(II) RADEON(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) RADEON(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
(II) RADEON(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
(II) RADEON(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
(II) RADEON(0): Output: DVI-0, Detected Monitor Type: 1
(II) RADEON(0): EDID data from the display on output: DVI-0 ----------------------
(II) RADEON(0): Manufacturer: SAM Model: 124 Serial#: 1296707895
(II) RADEON(0): Year: 2004 Week: 51
(II) RADEON(0): EDID Version: 1.3
(II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.700 V
(II) RADEON(0): Sync: Separate Composite
(II) RADEON(0): Max Image Size [cm]: horiz.: 34 vert.: 27
(II) RADEON(0): Gamma: 2.20
(II) RADEON(0): DPMS capabilities: Off; RGB/Color Display
(II) RADEON(0): First detailed timing is preferred mode
(II) RADEON(0): redX: 0.650 redY: 0.330 greenX: 0.330 greenY: 0.600
(II) RADEON(0): blueX: 0.150 blueY: 0.080 whiteX: 0.313 whiteY: 0.329
(II) RADEON(0): Supported established timings:
(II) RADEON(0): 720x400@70Hz
(II) RADEON(0): 640x480@60Hz
(II) RADEON(0): 640x480@67Hz
(II) RADEON(0): 640x480@72Hz
(II) RADEON(0): 640x480@75Hz
(II) RADEON(0): 800x600@56Hz
(II) RADEON(0): 800x600@60Hz
(II) RADEON(0): 800x600@72Hz
(II) RADEON(0): 800x600@75Hz
(II) RADEON(0): 832x624@75Hz
(II) RADEON(0): 1024x768@60Hz
(II) RADEON(0): 1024x768@70Hz
(II) RADEON(0): 1024x768@75Hz
(II) RADEON(0): 1280x1024@75Hz
(II) RADEON(0): 1152x864@75Hz
(II) RADEON(0): Manufacturer's mask: 0
(II) RADEON(0): Supported standard timings:
(II) RADEON(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) RADEON(0): #1: hsize: 1152 vsize 864 refresh: 75 vid: 20337
(II) RADEON(0): Supported detailed timing:
(II) RADEON(0): clock: 108.0 MHz Image Size: 338 x 270 mm
(II) RADEON(0): h_active: 1280 h_sync: 1328 h_sync_end 1440 h_blank_end 1688 h_border: 0
(II) RADEON(0): v_active: 1024 v_sync: 1025 v_sync_end 1028 v_blanking: 1066 v_border: 0
(II) RADEON(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 81 kHz, PixClock max 140 MHz
(II) RADEON(0): Monitor name: SyncMaster
(II) RADEON(0): Serial No: H9NXC27207
(II) RADEON(0): EDID (in hex):
(II) RADEON(0): 00ffffffffffff004c2d240137314a4d
(II) RADEON(0): 330e01036c221b782aaaa5a654549926
(II) RADEON(0): 145054bfef808180714f010101010101
(II) RADEON(0): 010101010101302a009851002a403070
(II) RADEON(0): 1300520e1100001e000000fd00384b1e
(II) RADEON(0): 510e000a202020202020000000fc0053
(II) RADEON(0): 796e634d61737465720a2020000000ff
(II) RADEON(0): 0048394e584332373230370a20200010
(II) RADEON(0): EDID vendor "SAM", prod id 292
Output CRT1 disable success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Blank CRTC 1 success
Disable CRTC memreq 1 success
Disable CRTC 1 success
Blank CRTC 0 success
Disable CRTC memreq 0 success
Disable CRTC 0 success
Output CRT1 disable success
Enable CRTC 0 success
Enable CRTC memreq 0 success
Unblank CRTC 0 success
Output CRT1 enable success
Last edited by ryeguy146 (2009-11-20 02:20:55)

ryeguy146 wrote:
The proprietary driver doesn't yet support XOrg 7.5, so unless I want to rip out X and downgrade, that's out of the question. Hell, I don't even know where I'd get the source for 7.4 (latest supported) if I wanted it. MadTux suggests that ATI may be releasing the next version of the Catalyst soon, so maybe they'll support 7.5 with that. Maybe not. I don't have this problem using, say, ubuntu with the old XOrg.
The xf86-video-radeon gives me a black screen, so that's out, though I haven't tried either the xf86-video-radeon-git or the xf86-video-ati-git, I may just bust those out and see what it gets me.
Flamelab's suggestion seems plausable. Installing xf86-video-ati-git and using his xorg.conf sample; I'll try that out now and report back shortly.
Edit:
Well that's interesting. Trying flamelab's suggestion does seem to work perfectly. No green, no black screen, just good stuff. Glxgears runs nicely (which I assume is OpenGL). My xorg.conf is as follows:
Section "Device"
Identifier "My Graphics Card"
Driver "radeon"
Option "DRI" "on"
Option "AccelMethod" "EXA"
Option "DMAForXv" "on"
Option "RenderAccel" "on"
EndSection
So that's something. Compositing still doesn't wish to work, but I think that I'm getting to where I want to be. Thanks for the tip, M177ER.
In order to see 3D with xf86-video-ati-git or you'll wait for linux kernel 2.6.32 (coming soon), or you can build the -git versions of mesa,libgl,ati-dri, kernel etc which can cause trouble if you don't know what to do. See here if you have time : http://bbs.archlinux.org/viewtopic.php?id=79509
As for the PKGBUILD: Xorg-server is a bit strict with full xorg.conf files lately. So creating a lite xorg.conf, can solve most problems.

Video tearing with xcompmgr and mplayer

Hello, recently I've noticed a lot of tearing when playing movies with xcompmgr loaded. When i kill xcompmgr it goes away (almost) completely and when I enable it again the tearing starts to reappear. I'm running kernel 2.6.29, xorg 1.6 and the latest nvidia beta.
I run into this tearing no matter what video output i select, xv, vdpau or gl, it doesn't matter, video still tears.
Since I really like the effects of xcompmgr + openbox (fast but still reasonably looking) and don't really want to do without xcompmgr, I was wondering if anyone here have experienced the issue and came up with some kind of solution to this issue.
Thanks, GBG-Johan.
I forgot to mention that the video tearing still occurs when i use xine-ui instead of mplayer, so I guess it's not an issue related to which player i use.
Last edited by göteborg-johan (2009-04-18 21:46:59)

System info :
Dell Studio 14z
NVidia 9400 M
built-in monitor and Sharp 1080p TV connected via HDMI
KDE 4.4
X.Org version: 1.7.5
NVidia Driver Version: 190.53
uname -a :
Linux shinny 2.6.32-ARCH #1 SMP PREEMPT Tue Feb 9 15:12:10 CET 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz GenuineIntel GNU/Linux
I am experiencing video tearing when using VDPAU output with mplayer. If I use XV output instead, there is no tearing. If I use Dragon Player (which doesn't support VDPAU) there is also no tearing. Playing around with the VSync option in nvidia-settings only has an effect if I'm using XV.
On my other box running Funtoo, I had experienced the same issue. After some searching on the Web, I found that someone suggested to add :
Section "Extensions"
Option "Composite" "Disable"
EndSection
to /etc/X11/xorg.conf. On my Funtoo system this fixed the issue. However, doing the same on my Archlinux Studio 14z didn't fix the problem.
I also tried recompiling mplayer (as if that would change anything...) to no avail.
The issue also occurs even if I use the laptop screen without any external monitor connected.
Does anyone have a clue of what else I should try? The suggestion to use only XV is not suitable because I have some 1080p content that I can not decode fast enough using only the CPU.
Another test I might try is to run my Funtoo on my laptop. This will tedious and it might not be exactly the same, since the kernel on my Funtoo machine is custom built with only the drivers for the hardware in that box.
Last edited by Prozzaks (2010-02-19 03:28:19)

[Solved] Unbootable USB with both BIOS and UEFI setup

I'm installing Arch to a USB flash drive to be bootable across a wide-range of computers (like the Arch ISO for USB) - both with legacy BIOS and with UEFI support (32bit instead of 64bit for greatest compatibility). I've installed Arch successfully and everything with it works fine.
To get the flash drive to bootup on legacy BIOS systems, I've installed Grub. This went without a hitch and this boots up on every legacy BIOS machine I've tried.
However, I cannot for the life of me get UEFI working. I only have one UEFI-enabled machine to test on. I've tied settings up both Gummiboot and Grub for UEFI support and they both seem to get to the same place. I get their boot entries to show up in the UEFI's boot up menu, but it boots the UEFI installation already present on the system (another Arch installation). If I remove the UEFI entry for the Arch installation on the machine, it lists the flash drive in the boot-up menu but clicking on it tells me that there were no bootable mediums found. So I'm guessing there is a configuration error somewhere.
The Arch ISO disk boots up successfully over UEFI on the machine without a hitch. SafeBoot is disabled on the UEFI machine machine. The UEFI machine has a working UEFI Arch installation by Grub2 which works fine - I setup the flash drive pretty much the same was as detailed below but it doesn't work.
Here is my setup:
Disk /dev/sda: 57.9 GiB, 62176362496 bytes, 121438208 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7AF2949B-01DA-4A5D-96B5-C716601BF56B
Device Start End Sectors Size Type
/dev/sda1 2048 10487807 10485760 5G EFI System
/dev/sda2 10487808 10489855 2048 1M BIOS boot
/dev/sda3 10489856 121438174 110948319 52.9G Linux filesystem
It is a GPT formatted flash drive, with an EFI partition, a BIOS Boot partition (for Grub) and finally a LUKS encrypted file system. (I have also tried the system without LUKS and I still get the same results as above).
ESP partition with Gummiboot (/boot): (ls -LR /boot)
EFI grub initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img loader vmlinuz-linux
./EFI:
Boot gummiboot
./EFI/Boot:
BOOTIA32.EFI BOOTX64.efi
./EFI/gummiboot:
gummibootia32.efi
./loader:
entries loader.conf
./loader/entries:
arch.conf
(with BOOTIA32.EFI copied to BOOTX64.EFI so UEFI would recognize the flash drive.)
ESP partition with Grub (/boot): (ls -LR /boot)
EFI grub initramfs-linux-fallback.img initramfs-linux.img intel-ucode.img loader vmlinuz-linux
./EFI:
Boot gummiboot
./EFI/boot:
bootx64.efi
./EFI/grub:
grubia32.efi
grub.efi
I've tried copying both grub.efi to bootx64.efi and grubia32.efi to bootx64.efi. Both seem to be the same file.
BLKID
/dev/sda1: UUID="E3BA-7D68" TYPE="vfat" PARTLABEL="EFI System" PARTUUID="d3619522-56c7-4a18-9997-3a9649809506"
/dev/sda2: PARTLABEL="BIOS boot partition" PARTUUID="40132eb6-2994-44b8-a6c4-8380fbd45a98"
/dev/sda3: UUID="a7392099-0853-4b03-a1e9-82e298eaab95" TYPE="crypto_LUKS" PARTLABEL="Linux filesystem" PARTUUID="300f4171-f1b5-4407-beee-060ae8fb8dee"
/dev/mapper/Root: LABEL="Root" UUID="679ba330-de69-4805-ba12-59d479ea12fc" TYPE="ext4"
fstab (using default mount options from fstab generator)
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/Root LABEL=Root
UUID=679ba330-de69-4805-ba12-59d479ea12fc / ext4 defaults,relatime 0 1
# /dev/sda1
UUID=E3BA-7D68 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
Grub for legacy BIOS was setup with the commands:
grub-install --target=i386-pc --recheck --debug /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg
Grub configuration from /boot/grub/grub.cfg
GRUB_CMDLINE_LINUX_DEFAULT="cryptdevice=UUID=a7392099-0853-4b03-a1e9-82e298eaab95:Root"
I've tried both Gummiboot and Grub2 (not at the same time) alongside Grub for the legacy BIOS bootup. BIOS bootup works fine.
UEFI configuration with Gummiboot:
gummiboot --path=/boot install
/boot/loader/loader.conf
default arch
timeout 4
/boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options cryptdevice=PARTUUID=300f4171-f1b5-4407-beee-060ae8fb8dee:Root root=UUID=679ba330-de69-4805-ba12-59d479ea12fc ro
UEFI Configuration with GRUB2:
grub-install --target=i386-efi --efi-directory=/boot --bootloader-id=grub --recheck
grub-mkconfig -o /boot/grub/grub.cfg
mkdir /boot/EFI/boot
cp /boot/EFI/grub/grubia32.efi /boot/EFI/boot/bootx64.efi
I have to copy grubia32.efi to bootx64.efi so my UEFI system detects the flash drive.
I have done all of these steps on a BIOS machine, and a UEFI machine, both with the same results. The machine recognizes the flash drive in the bootup menu and lists it as an option to boot from, but it tells me no bootable device was found. I don't care which method I need to use to get the flash drive to bootup over UEFI, gummiboot or Grub, I'm just trying to get it to work.
Last edited by awbs (2015-05-17 18:25:19)

It sounds like you are on the right track. I got it to work using a similar method. Here is my setup: 16GB USB 2.0 Corsair Voyager.
gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.0
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 31950720 sectors, 15.2 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0C83EC1E-9109-4E1E-9EB8-01373E2339D4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 31950686
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)
Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF02 BIOS boot partition
2 206848 616447 200.0 MiB EF00 EFI System
3 616448 31950686 14.9 GiB 8300 Linux filesystem
As you can see, I made 3 partitions on a GPT labeled USB stick. You need to format the EF00 and 8300 partitions:
mkfs.vfat -F32 /dev/sdb2
mke2fs -t ext4 -L isofiles /dev/sdb3
"isofiles" is the label I used for the ext4 partition. You can change this. Now install Grub for EFI on the ESP partition:
mount /dev/sdb2 /mnt
mkdir -p /mnt/boot
grub-install --target x86_64-efi --efi-directory /mnt --boot-directory /mnt/boot --removable
Place your grub.cfg file in /mnt/EFI/BOOT.
Install GRUB for legacy BIOS on the bios_boot partition:
umount /mnt
mount /dev/sdb3 /mnt
mkdir -p /mnt/boot
grub-install --no-floppy --target i386-pc --boot-directory /mnt/boot /dev/sdb
Place your grub.cfg file in /mnt/boot/grub. On some systems, it is /mnt/boot/grub2.
Copy all of your ISO files, e.g., arch, gparted, clonzilla, etc, to the ext4 partition. you will need the UUID of the ext4 partition:
blkid /dev/sdb3
This is because we are using a UUID search method to find the ISO's before loop mounting them. You can obtain the grub menu entries for various distros here. I used the following grub.cfg to boot arch and gparted in EFI mode:
set default="0"
function load_video {
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_fb
insmod video_cirrus
insmod all_video
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set timeout=10
submenu 'GParted -->' {
set default="1"
set isofile='/gparted-live-0.22.0-1-amd64.iso'
menuentry 'GParted -- default settings' --class gparted --class gnu-linux --class os {
search --no-floppy --fs-uuid --set=root THIS_IS_YOUR_UUID
loopback loop $isofile
set root=loop
linuxefi /live/vmlinuz boot=live username=user config components quiet noswap noeject ip= nosplash findiso=$isofile
initrdefi /live/initrd.img
submenu 'Arch Linux -->' {
menuentry 'Install Arch Linux' --class arch --class gnu-linux --class os {
set isofile='/archlinux-2015.04.01-dual.iso'
search --no-floppy --fs-uuid --set=root YOUR_UUID
loopback loop $isofile
set root=loop
linuxefi /arch/boot/x86_64/vmlinuz archisolabel=ARCH_201504 img_label=isofiles img_loop=$isofile earlymodules=loop
initrdefi /arch/boot/x86_64/archiso.img
The legacy grub.cfg file is identical to the above, except that you use "linux" and "initrd" instead of "linuxefi" and "intrdefi". Note that unfortunately you have to use two grub.cfg file, one for UEFI and the other for legacy placed in the locations described above. However, they are very similar.
When you boot the machine, if it is an ASUS board, let's assume, press F8 during POST. You should see "Corsair - UEFI" and "Corsair". They should both work. Good Luck.

Video tearing on my 24" iMac

I have been having an issue with my 24" iMac for the past couple of months and I was wondering if you have heard of this issue before. I am getting what I guess would be described as video tearing. On occasion, and with no obvious pattern to it, I will get a weird horizontal line of noise that goes across just a certain open window, not the entire screen. I have been able to take screenshots of this, but I don't think I can post those in the discussions.
Anyhow, it happens in Firefox, Word, Mail, etc. There does not seem to be any program that is immune to this issue, and it doesn't happen all the time. It appears to be quite random.
I have checked the Apple Support site and the only thing I found were some old discussions about a tearing issue with previous generation iMacs. If I remember correctly, they were pretty old iMacs. Nothing about this issue in the recent past.
The video tearing sometimes goes away if I scroll up/down the window, and sometimes it doesn't. Though, more often than not, it goes away by scrolling.
My machine is coming up on a year old next month, so if I need to use my warranty, I need to do it soon.
Have you heard about this issue at all? Any help would be greatly appreciated!
My system specs are as follows:
24" Intel iMac purchased 9/06
2.16 GHz Intel Core 2 Duo processor
1 GB 667 MHz DDR2 SDRAM
I have not upgraded the hardware in anyway.
Thanks again for your help!

Hello lizardsrdizzy!
Did this video tearing issue for sure just start happening, or did you just notice it for the first time? I ask only because this sounds like the known Apple/ATI issue that many of us with ATI video cards have had, but only eventually noticed.
HOWEVER, since you do NOT have an ATI video card, I'd definitely recommend you need to pursue this flaw immediately within warranty/AppleCare.
http://docs.info.apple.com/article.html?artnum=86823
I strongly recommend adding AppleCare to maintain the value of your iMac, either for your own use, or for eventual resale. Considering the original cost of your setup and the still rather high cost of replacing a 24-inch display, at full cost AppleCare will be a bargain and that cost will either be fully returned to you the first time you need to use it, or when you resell your iMac. Discounted it's available from Amazon and various Mac sellers.
If you need to get a bigger bargain, occasionally they show up, but give yourself time to find one on eBay, and refer to my recent post here:
http://discussions.apple.com/message.jspa?messageID=4980575#4980575
Best of luck, and please return to let us know the resolution of the matter.
Message was edited by: myhighway

Video tearing on iMac (Late 2006)

Hi,
My iMac has been suffering from what i think is video-tearing and horrible refreshrate for a week now. I'm thinking hardware problems.
The video-tearing mainly comes up when the screensaver goes on but it's still annoying.
The refreshrate is always bad.
I have the iMac(late 2006) 2.16GHz with 2GB ram and the ATI Radeon X1600 with 128MB VRAM.
What to do?

Same Model, same problem here. Much worse i think, picture cuts in half, fonts break. Happened after some update back in March. I was away for some time not using it but now few updates later still no resolution, Display looks fine in XP (bootcamp)

How to change sharing settings with no video?

I have a macbook pro that does not have any sort of video output. Unfortunately remote login/screen sharing/ssh are all disabled and my version of realvnc is apparently just below the one that works with Lion causing the realvnc window on the remote server to crash when I attempt to connect.
I have hooked the hard drive up to my desktop (windows 7 x64) and have attempt to make the hard drive a vmware installation, but I have not succeeded with that at all. I have made it where I can view the partition in windows using MacDrive, but I am unable to change any of the system files and I'm not even sure if I could change preferences this way.
Is there anything I can do to enable remote login?
Thanks.

Hi,
Let me say to start with, that with no video output, some of what I'm about to suggest is guess work.
1. Tap away at f1 as soon as you press the power button - this should launch the Bios Menu.
2. Press the right arrow One time - this should hopefully select the Advanced tab.
3. Press the down arrow twice and hit Enter - this should open the sub-menu for the Primary Video Adapter.
4. Press the down arrow One time and hit Enter - this should select the PCI-E option.
5. Press f10 and hit Enter to save this setting.
Let me know
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

[SOLVED] Can't get xf86-video-r128 to work...

Hello! Arch newbie here, so far bumpy, but so far so good. Currently posting from TWM for kicks...
Anyways, my old junker of a computer was where I installed arch, so I could get a hang of it. The graphics card is a ATi RAGE XL AGP 2X... having no luck with xf86-video-ati, I installed xf86-video-r128, and got graphics working for the first time in arch. Hooray!
Unfortunately, I can't seem to get my monitor's native resolution of 1280x1024. If I try, the monitor refuses to display, and errors out with "Out of Range". I know it's definitely possible, since other linux installations have auto-configured it so far. So, I'm wondering what I need to modify in xorg.conf to get 1280x1024 working.
It seems like a refresh rate problem, but when I looked over the file, I noticed that "Driver" was set to "vesa". Changing it to "r128" did nothing, as the X server refused to start because it couldn't find any devices.
I will post my xorg.conf shortly.
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "dbe"
Load "dri2"
Load "dri"
Load "record"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Jean"
ModelName "Unknown"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
VendorName "ATI Technologies Inc"
BoardName "Rage XL AGP 2X"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1024x768" "800x600"
EndSubSection
EndSection
Section "ServerFlags"
Option "DontZap" "False"
EndSection
As you can see, the Modes section under 24-bit depth doesn't have "1280x1024", but if I add it in, the X server will default to it (correctly), but I won't be able to see anything.
Last edited by kareeser (2009-05-30 21:25:23)

Karol, thanks for replying so quickly
I tried your suggestion to replace "vesa" with "ati" in the "Driver" line. X failed to start, but for some reason, there was some leftover code in xf86-video-ati that caused it to look for the mach64 driver... which as I understand, used to be installed with xf86-video-ati, but no longer... hrm! A quick "pacman -S xf86-video-mach64" later, I now have a working 1280x1024 resolution. Excellent! Changed the DefaultDepth to 16, and now my system is nice and zippy.
A similar problem is that I still cannot get 1280x1024 in vc1. In /boot/grub/menu.lst, I have "vga=773" added, but that's as high as I can go, vga=775 won't work with the same reason above.
Small problems in the grand scheme of things. I'm glad the main issue is solved
Last edited by kareeser (2009-05-30 01:34:01)

Horizontal video tearing in xfce and ion graphics (nvidia)

Hello all,
I have arch + xfce running no problems, but there is significant horizontal video tearing when I play videos (in vlc or firefox/flash). I have already enabled 'Sync to VBlank' within the nvidia-utils control panel. I think the problem arises from the xfce monitor settings window that only allows the frequency output to the monitor to be 50Hz. Can someone confirm this and/or offer advice?
Thanks again,
DF

Since Devotedfollower is using a nvidia ion card he will get the best results without compositing at all.
If you want to use a nvidia card along with compiz without tearing, I found these additional steps to be necessary:
put
Option "TripleBuffer" "True"
under Section "Device" in your /etc/X11/xorg.conf (if you don't have one, run "nvidia-xconfig" once as root)
put "nvidia-settings -l" into your startup applications
install and launch ccsm, open up the general options and look for a tick called "Sync to VBlank" and activate it
within these general options there is a tick called "recognize refresh rate" (or something alike); deactivate it
try playing around with the refresh rate slider (I got the best results when using the exact refresh rate for my display or something higher)
Note that these steps are only necessary if you really want to use compiz on nvidia cards. They worked with several GTX cards for me. Don't know about your ION though.
My netbook has an ION but it was one of the first ones. As far as I can remember it had no tearing on xfce without compositing but on compiz it had a bit tearing at the top of screen even with all the steps above.
Nevertheless I wish you best luck!
P.S. Tearing has always been a huge problem on Linux for me. After a lot research I found compiz being the only compositor able to almost eliminate tearing. So the only choice for nvidia users to get rid of video tearing is either to use no compositing at all (which results in teary desktop graphics) or to use compiz along with vdpau...

Video "tearing" on monitors

I am using Premiere CS5.5. I have a GTX 460 card with the MPE GPU acceleration turned on. I am using the DVI output from the card to my GUI monitor and the HDMI output to a second computer monitor (Samsung - supposedly hi-def, though I know this is not the same as a true hi-def production video monitor).
I am still working with a lot of SD footage. It seems like anytime there is significant camera movement in an SD clip, there will be tearing somewhere across the middle of the image. This is true in my source monitor, my program monitor and my second full-screen monitor. The location of the tearing can vary with each playback. If I look at the same clip with the VLC player, I don't see the tearing. Is there something I can do in Premiere to stop this from happening?
J. D.

DVI/HDMI Monitoring is a smart solution and has a lot of benefits (e.G. GPU processed video can send directy out to the monitor) but also has drawbacks becaus sometimes you are at risk of occasionally stuttering (SDI framebuffer cards are more stable at this currently) and you have to set the screen refresh rate for yourself (50Hz, 59,976Hz, 60Hz, 48Hz...)
--> Video tearing is a thing that should not occour on a modern computer with a GTX 460.
Do you also have video tearing with VLC media player or Windows Media Player?
--> You have to check you Video driver settings to get rid of the tearing I think...
I don't have any video tearing with my Nvidia Cards exept one really old 8400GS in a server...

Problems with Flash Video

OK - I have had intermittent problems with Flash video, basically it gets choppy, usually after about 20 minutes - half an hour of watching - recently this problem has gotten worse - coinciding with a recent system update perhaps? - it's more or less anytime I stream something, and it happens on all browsers, even when the movie has clearly downloaded and is buffered way in advance of the playhead.
On 2 occasions recently leaving the movie to play just to see what happens has led to a kernel panic.
I've heard alot about Flash video generally being a resource hog and not playing ball sometimes - is there a way to solve this issue? Things I have tried - reset sound to 16 bit 44.1 khz in audio/midi manager; fixed permissions; run Tech Tool - everything seems to be fine hardware wise - I think there are some incompatible driver issues that are meesing up RAM usage but have no idea what or how to solve this... Any ideas anybody?
Thanks.

If, as you show, you are running 10.5.2, that is out of date. You need to install the 10.5.8 combo updater.
It is also possible that your FlashPlayer is out of date.
The latest version of Adobe FlashPlayer can be obtained from here:
http://www.adobe.com/shockwave/download/download.cgi?P1ProdVersion=ShockwaveFlash
(You can check here: http://www.adobe.com/products/flash/about/ to see which version you should install for your Mac and OS.
You should first uninstall any previous version of Flash Player, using the uninstaller from here (make sure you use the correct one!):
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14157
and also that you follow the instructions closely, such as closing ALL applications first before installing. You must also carry out a permission repair after installing anything from Adobe.

Iam trying to import a short video in final cut express and I'm getting this error... File Error: 1 file(s) recognized, 0 access denied, 1 unknown. How do I solve this problem? The video is on my desktop it's an mpg.

Iam trying to import a short video in final cut express and I'm getting this error... File Error: 1 file(s) recognized. 0 access denied, 1 unknown. How do I solve this problem? The video is on my desktop and it's an mpg file. Please help me

Get a copy of MPEG Streamclip and convert your MPG file to QuickTime/Apple Intermediate Codec (AIC). In FCE, select one of the setups that uses AIC that best matches your clip (say, 1920x1080i60). Create a new sequence, then import the converted file.
Note that if your MPG file is actually MPEG2 you will also need the QuickTime MPEG2 Component in addition to MPEG Streamclip.
What was the source of the MPG file? How about if you open it in QuickTime, then do Window > Show Movie Inspector. Tell us what it says for codec/compression, frame size & frame rate.

Mkv with multiple video tracks

Hi. I have a load of Matroska files which contain a few (about 5) short video clips and an audio track. The video clips in each file are of the same event from different angles, so I want to watch all clips simultaneously. I have installed Perian and while the files open, I can only see one track, and I don't hear any audio. (MKVinfo tells me there are definitely multiple tracks.) Is it possible to use Perian/QuickTime to watch all video tracks simultaneously? If so, I can't figure out how, so I'd appreciate any pointers.
I've tried VLC, and while this also opens the files (and shows all tracks), it invariably crashes soon after opening.
If anyone has any other suggestions how I might solve this, that would be great too.
Thanks in advance,
wrathkeg

It could be a 'difficult' form of Matroska file. FYI Matroska is just a container like MOV or AVI, and some mkv have the video encoded with Real Video Codec (RV9 RV10). Perian+QT can't decode this, but VLC will play .mkv files just fine on OS X, as long as they don't use H.264!
It's a bit of a lottery until Matroska decide to support the Apple platform. I have found this:
http://mkv4mac.free.fr/index.php?lang=en&p=lec
which may help.
But there may be another workaround: 1. Get Info the mkv file
2. Change to extension to wmv. Save as wmv and that could work better.
Or this link may be helpful:
http://www.squidoo.com/mkv-converter-mac
Recently, a poster (ZachP14) suggested this:
"There's a program called Plex that runs .mkv files awesome on my 2.0 ghz macbook."
http://www.plexapp.com/
Maybe worth a try?

[Solved] Minimalist setup with no video tearing

Similar Messages

Maybe you are looking for