Created attachment 54462 [details] dmesg output and Xorg.0.log Hi. Alexdeucher advised me to file a bug on my problem. Excuse me for for my bad English, but I'm using the Google Transaltor! So.....: Video card ATI Radeon 9200 AGP RV280 8x 128Mb DDR SDRAM. xserver-xorg-video-ati/radeon ver. 1:6.14.0-0ubuntu4.1 Ubuntu Natty 11.04 Motherboard ASUS A7V400-MX The 3D effects work, even if the windows "tear" at the top when you move. The DVI output does not work well. When you open, move the windows, the monitor turns off and on again. Same thing when you move the deskptop with the cube rotating. Even without using Gnome what actually happens is the same, but only on the DVI. With the VGA everything works, but with worse resolution of the monitor. I installed (for testing) Oneiric 11.10 but the problem remains. Can you help me? Tanks Valter
Created attachment 54463 [details] dmsg output
Created attachment 54464 [details] [review] Xorg.0.log
Oooooooooops! I forgot to specify something! The Monitor is a Samsung SyncMasterT24A350 16 / 9 native 1920x1080 60Hz. When you start the computer, the mouse cursor becomes a shadowy figure. This is also using the VGA. If you continue to access, the screenlets are corrupted by blue lines. Just restart your PC and everything goes back to regular.
According to your xorg log, you are trying to drive two 1920x1080 monitors. That is a lot of bandwidth for an r2xx GPU to drive. Try only attaching one monitor. I suspect the memory controller cannot keep up with the requests for two large monitors and the 3D engine, and when you get underflow, you get the blinking. Does it work ok with only one monitor (xrandr --output VGA-0 --off)? How about a different mode? Try 1024x768 or 1280x800, etc. You can also try a different modeline for 1920x1080. try: Modeline "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync for example.
No, no! I have a single monitor! If I use the VGA output is okay. If I use the DVI output of the monitor flashes. Should I disable the VGA output? How can I?
You must excuse me, but (maybe I did not say) are new to Linux, so some acronyms do not know them! And often I do not know how to give some commands that I suggest! : ((( I'm learning. Thank you!
In fact, the monitor is connected with both cables, both VGA and DVI. Select the input of the monitor depending on the OS I use (DVI or VGA with WindowsXP with Ubuntu). Of course the intention is to only use the DVI output and disconnect the VGA cable for ever! If I can make it work!
Does the problem also occur with only the DVI cable connected?
Well, you appear to have both the DVI and VGA ports attached: [ 18.191] (II) RADEON(0): Output VGA-0 connected [ 18.191] (II) RADEON(0): Output DVI-0 connected [ 18.191] (II) RADEON(0): Output S-video disconnected [ 18.191] (II) RADEON(0): Using exact sizes for initial modes [ 18.191] (II) RADEON(0): Output VGA-0 using initial mode 1920x1080 [ 18.191] (II) RADEON(0): Output DVI-0 using initial mode 1920x1080 You can turn off the VGA port by disconnecting the monitor that's plugged into the VGA port or by issuing the following command: xrandr --output VGA-0 --off
Ok here I am! I came home from work and I turned on my computer now. For Michel Dänzer: My monitor has two inputs, one VGA and one HDMI. The DVI output is connected to the HDMI with an adapter cable. Although the VGA Out DVI output has the same problem. When you try to rotate the cube (desktop) or you open or move a window, or write (as now) the comment with the keyboard, the monitor turns off and on, as if the video signal disappear for a moment . I wish both of the cables attached to the monitor for convenience only. So after testing, I can test if it works or remained the same throughout. If it can create problems, I can detach easily. For Alex : 1)With the command Radeon.modeset=0 ,the screen is larger than the monitor. There are more than it will the lower bar! Switching to VGA input, everything returns to normal! 2) No I did not try to change other resolutions. 3) The command (xrandr - output VGA-0 - off) is given by the terminal, right? As for "Modeline" 1920x1080R "138.50 1920 1968 2000 2080 1080 1083 1088 1111 + hsync -vsync as I do, always terminal? Now reboot again and try to change the resolution to 16:9 with only one available that is 1360x768. Obviously not giving the command radeon.modeset = 0
Ok Except now that everything is bigger, the resolution is not that good (at least to manage the photos) and I have gone to the screenlets (perhaps lost in another location on the desktop is not visible?), Now no longer the problem!
Hmm so this works with Windows? IIRC there were some problems with 9250 dvi outputs when driven near their clock limits in linux, but that was so long ago I can't remember if they were ever fixed for good.
Per Roland Scheidegger: In Windows XP the output goes perfectly! The monitor works by god! I would like to make it work with Ubuntu, then (I do not know how to say in English, or if the Google translator translates it to me correctly!) "Fuck you Windows,go to hell!" What the hell is going on? I put everything back as before, that I put the resolution to 1920x1080 60 Hz, but DVI output, the dsktop goes off the screen, you lose the top and bottom bars and screenlets, like the other resolution! The monitor tells me that the resolution is 1920x1080 sull'HDMI 60 P! What is P? Now go out and restart Windows XP to see what the monitor tells me. It seems to me to tell me 1920x1080 60Hz, like VGA on. Mhhh Of course it's all on VGA as before, that is fine.
Ok, I drank the brain! Evidently I'm tired. Today it happened to work for everything! Even in Windows tells me 1920x1080 / 60p. I'm sorry
Hi Alex. I wrote the command: valter@valter-A7V400-MX:~$ xrandr --newmode "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync to test, I had suggested committee. At first I worked and the video card was fine, at last! After reboot I tried again, but this cluster gives me error: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 150 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 29 Current serial number in output stream: 29 valter@valter-A7V400-MX:~$ What is wrong? And then how do I make it permanent?
(In reply to comment #15) > X Error of failed request: BadName (named color or font does not exist) > Major opcode of failed request: 150 (RANDR) > Minor opcode of failed request: 16 (RRCreateMode) This means a mode of that name exists already.
Ok. I made the suggestion of Alex in this way: 1) I gave the following terminal commands: xrandr - newmode "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 1111 + hsync-vsync xrandr - DVI-0 addmode 1920x1080R xrandr - output DVI-0 - mode 1920x1080R The monitor works fine as well! 2) Then I wrote these commands: sudo nano / etc / gdm / Init / Default After the lines: PATH = / usr / bin: $ PATH IFS = $ OLD_IFS and then I saved. 3) After restarting the monitor does not work anymore, but if I run the commands from the terminal xrandr - DVI-0 addmode 1920x1080R xrandr - output DVI-0 - mode 1920x1080R Then everything works! What's wrong?
Hello to everybody, again. I stand corrected. After further tests, after rebooting, it is sufficient only to give the command: xrandr - output DVI-0 - mode 1920x1080R so that the monitor is fine. Why doesn't it execute the last command? Does it exist another way to make the setting permanent? And how?
Hello everyone. I think I have solved! Just simply unplug the VGA cable and now the monitor works perfectly with the settings suggested by Alex! Thank you all for your precious help! One last question (if si possible): When I start the computer and launch Ubuntu, the mouse pointer, at the login screen. is corrupt. If I access so, the desktop is corrupted by light blue lines. However, if all goes well, reboot. Everything is fine even if boot Windows first and then reboot and launch Ubuntu. In practice, when I turn on the PC, if I want to use Ubuntu I have to reboot to get everything in place. This happens even if I use VGA. You have an idea of why?
(In reply to comment #19) > Hello everyone. > I think I have solved! > Just simply unplug the VGA cable and now the monitor works perfectly with the > settings suggested by Alex! > > Thank you all for your precious help! > Great. With both monitors plugged in the driver is driving both of them which is probably more bandwidth then the card can handle. > One last question (if si possible): > When I start the computer and launch Ubuntu, the mouse pointer, at the login > screen. is corrupt. > If I access so, the desktop is corrupted by light blue lines. > However, if all goes well, reboot. > Everything is fine even if boot Windows first and then reboot and launch > Ubuntu. > In practice, when I turn on the PC, if I want to use Ubuntu I have to reboot to > get everything in place. > This happens even if I use VGA. > > You have an idea of why? Possibly some uninitialized register. Does running an application that uses Xv also fix the issue? This should probably be tracked as a separate bug.
" This should probably be tracked as a separate bug. " Also in this section? "Does running an application that uses Xv also fix the issue?" Ehhhhhhhhh? O.o I'm lost! Which applications use Xv? and more importantly: What is Xv?
I came across this bug by an accident when searching for something else, however when reading through there seems to be some misunderstanding. If I understand correctly, Valter have (according to comment 5 and comment 7) _one_ monitor with two input cables both attached to the same card. While everyone else thinks he has two different monitors... Is this right? And of course the problem is solved when one cable is disconnected (comment 19).
(In reply to comment #21) > Which applications use Xv? movie players mostly (totem, mplayer, vlc, etc.) > > and more importantly: What is Xv? It's an X extension for accelerated colorspace conversion and scaling generally used for video display. Xv is short for Xvideo.
(In reply to comment #22) > I came across this bug by an accident when searching for something else, > however when reading through there seems to be some misunderstanding. > > If I understand correctly, Valter have (according to comment 5 and comment 7) > _one_ monitor with two input cables both attached to the same card. While > everyone else thinks he has two different monitors... Is this right? And of > course the problem is solved when one cable is disconnected (comment 19). I believe your assessment is correct. The driver sees two monitors attached, one on the DVI and one on the VGA connector. Whether or not they are the same monitor is irrelevant from the driver's perspective since the drier sees two monitors and lights them up. Two HD monitors is really pushing the bandwidth capabilities of this old card.
(In reply to comment #23) >movie players mostly (totem, mplayer, vlc, etc.) I have not tried. If I understand, within the monitor corrupted, then launch vlc to see if the problem is resolved. Tonight I run, then let you know. > >It's an X extension for accelerated colorspace conversion and scaling generally >used for video display. Xv is short for Xvideo. Ok, sorry for my ignorance! Often I do not understand the acronyms!
I tried. Opening VLC does not change anything. If I capture the screen, the performance is even worse than it actually is! On the white of the windows, the pointer disappears completely.
The DVI issue is fixed. Please open a new bug if you are still having gfx problems.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.