Description of problem: If you try to use Vesa driver, the X will screw, lines to all places in the screen, this will make unusable your screen, and then if you change the driver, in my case to radeon, the X will screw... in this case, the computer will hang... don't know why it happens, my last Xorg.0.log Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
it's reproduce able always, Name : xorg-x11-drv-vesa Arch : x86_64 Version : 2.3.0 Release : 2.fc14 Size : 26 k Repositorio : installed From repo : updates-testing Summary : Xorg X11 vesa video driver URL : http://www.x.org License : MIT Descripción :X.Org X11 vesa video driver. Linux localhost.localdomain 2.6.35.6-48.fc14.x86_64 #1 SMP Fri Oct 22 15:36:08 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux My Video card it's a RAdeon HD 3200
[maximi89@localhost /]$ rpm -qls xorg-x11-drv-vesa normal /usr/lib64/xorg/modules/drivers/vesa_drv.so normal /usr/share/man/man4/vesa.4.gz
(In reply to comment #0) > my last Xorg.0.log Sorry, we haven't got it. Also, why do you need VESA driver at all? Wouldn't just removing your /etc/X11/xorg.conf altogher make system work? If not, please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Hi, when i have tried with VESA, i have used this conf: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib64/xorg/modules" FontPath "catalogue:/etc/X11/fontpath.d" FontPath "built-ins" EndSection Section "Module" Load "dri2" Load "glx" Load "extmod" Load "dri" Load "record" Load "dbe" 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" #DisplaySize 340 190 # mm Identifier "Monitor0" VendorName "AUO" ModelName "20ec" EndSection Section "Device" Option "RenderAccel" "true" Identifier "Card0" Driver "vesa" BusID "PCI:1:5: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 EndSubSection EndSection
If i remove the xorg.conf it works normally, probably using radeon driver...
well, the messages and Xorg.0.log don't provide any thing usefull... but all VT having the same problem... i will take a photo...
Created attachment 461124 [details] /var/log/messages when vesa driver is in use
Created attachment 461125 [details] /var/log/Xorg.0.log when vesa driver is in use
(In reply to comment #5) > If i remove the xorg.conf it works normally, probably using radeon driver... Sorry, could I still get the answer why you have to use VESA driver?
By the same reason why it exist... to be used when we require it... in my case it doesn't work at all...
Can you attach a picture of the broken display caused by the vesa driver? Note that a screenshot probably will not show anything wrong.