PDA

View Full Version : [ubuntu] Activing my VGA, Ubuntu goes "Out Of Range"



StormWalker
December 6th, 2008, 11:23 PM
Hi, I'm a new linux\Ubuntu User, this have being my first shots,
My computer is new and I was trying to install Ubuntu on it, I had few problems installing...every time that I tried I got this mensage in the monitor "Out Of Range"
but after a while studying I installed in safe graphics mode
But it only uses 800x600 of resolution, I tried to put in on 1024x768 and I can't.

I went to Hardware and tried to activate my graphic card that apparently wasn't active.
after it said to restart the computer to finish activing my graphic card, after that again I get the "Out Of Range"
Ican hear the sound when is Starts the OS is Working but no image just the big "Out Of Range"
the 800x600 resolution is way to big, I realy want to put it on 1024x768, but I dont know how.
I tried the xorg.conf and some sudo commands that I get in here like.
$ sudo dpkg-reconfigure -phigh xserver-xorg
$ sudo /etc/init.d/gdm restart

but it just wont work.

I realy dont know what to do.

StormWalker
December 6th, 2008, 11:37 PM
I'm Using Ubuntu 8.10 64bit

and my graphic card is
MSI R4850-512M Radeon HD 4850 512MB 256-bit GDDR3 PCI Express 2.0 x16



MohtherBoard: DFI LP JR 790GX-M2RS AM2+/AM2 AMD 790GX HDMI AMD
Processor: AMD Phenom 9850 BLACK EDITION 2.5GHz Socket AM2+ 125W Quad-Core
Memory: (2x) mushkin 2GB 240-Pin DDR2 SDRAM DDR2 800

ahood
December 7th, 2008, 01:44 AM
Maybe after activating the 3d graphics driver, the resolution defaults to something greater than 1024x768, which in turn is too high for the monitor?

After activating the graphics driver, do not restart. Rather, check the resolution. If it is high, lower it to 1024x768. Then restart.

If it happens again, repeat but select 800x600 and see if 3d graphics driver stays enabled. If it does, then do the 'sudo dpkg-reconfigure xserver-org' and be sure to select the appropriate driver, and as importantly, the desired resolution (assuming the monitor supports 1024x768).

I hope this helps. Not exactly sure though, but maybe worth a try.

StormWalker
December 12th, 2008, 06:54 AM
when I activate it stills dont working... when I try to change on the Resolution the only Options are 800x600 and 600x240....
I try Ilot thing... tried to change the xorg.conf.....with no sucsses, I try to change but it still uses the .failsafe.....
I tried to fixed with no sucsses as well.....
I install the least driver for my card but when I try to enter the catalyst appears,
"There was a problem initializing Catalyst Control center Linux Edition. It Could be ..........I use a ATI HD 4850

StormWalker
December 12th, 2008, 07:25 AM
this files are appearing every time that The failsafe comes.
all in the \etc\X11
xorg.conf.20081207230917
xorg.conf.20081207234547
xorg.conf.failsafe
xorg.conf.failsafe.back

and all with the same content.....


# xorg.conf.failsafe (X.Org X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the xorg.conf manual page.
# (Type "man xorg.conf" at the shell prompt.)
#
# This file is automatically updated on xserver-xorg package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xorg
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command:
# sudo dpkg-reconfigure -phigh xserver-xorg

Section "Device"
Identifier "Configured Video Device"
Driver "vesa"
EndSection

Section "Monitor"
Identifier "Configured Monitor"
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection

StormWalker
December 12th, 2008, 07:44 AM
this is my Xorg.0.log =)

II) VESA(0): Total Memory: 256 64KB banks (16384kB)
(II) VESA(0): Configured Monitor: Using default hsync range of 31.50-37.90 kHz
(II) VESA(0): Configured Monitor: Using default vrefresh range of 50.00-70.00 Hz
(WW) VESA(0): Unable to estimate virtual size
(II) VESA(0): Not using built-in mode "1920x1440" (no mode of this name)
(II) VESA(0): Not using built-in mode "1856x1392" (no mode of this name)
(II) VESA(0): Not using built-in mode "1792x1344" (no mode of this name)
(II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
(II) VESA(0): Not using built-in mode "1400x1050" (no mode of this name)
(II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
(II) VESA(0): Not using built-in mode "1280x960" (no mode of this name)
(II) VESA(0): Not using built-in mode "1152x864" (no mode of this name)
(II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
(II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
(II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
(II) VESA(0): Not using built-in mode "720x400" (no mode of this name)
(II) VESA(0): Not using built-in mode "640x350" (no mode of this name)
(II) VESA(0): Not using built-in mode "512x384" (no mode of this name)
(II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
(II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
(WW) VESA(0): No valid modes left. Trying less strict filter...
(II) VESA(0): Configured Monitor: Using hsync range of 31.50-37.90 kHz
(II) VESA(0): Configured Monitor: Using vrefresh range of 50.00-70.00 Hz
(WW) VESA(0): Unable to estimate virtual size
(II) VESA(0): Not using built-in mode "1920x1440" (hsync out of range)
(II) VESA(0): Not using built-in mode "1856x1392" (hsync out of range)
(II) VESA(0): Not using built-in mode "1792x1344" (hsync out of range)
(II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
(II) VESA(0): Not using built-in mode "1400x1050" (hsync out of range)
(II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
(II) VESA(0): Not using built-in mode "1280x960" (hsync out of range)
(II) VESA(0): Not using built-in mode "1152x864" (hsync out of range)
(II) VESA(0): Not using built-in mode "1024x768" (hsync out of range)
(II) VESA(0): Not using built-in mode "720x400" (hsync out of range)
(II) VESA(0): Not using built-in mode "640x350" (hsync out of range)
(II) VESA(0): Not using built-in mode "512x384" (hsync out of range)
(II) VESA(0): Not using built-in mode "320x240" (illegal horizontal timings)
(II) VESA(0): Not using built-in mode "320x200" (illegal horizontal timings)
(--) VESA(0): Virtual size is 800x600 (pitch 800)
(**) VESA(0): *Built-in mode "800x600"
(**) VESA(0): *Built-in mode "640x480"
(==) VESA(0): DPI set to (96, 96)
(II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (122)
(II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (121)
(**) VESA(0): Using "Shadow Framebuffer"
(II) Loading sub module "shadow"
(II) LoadModule: "shadow"

(II) Loading /usr/lib/xorg/modules//libshadow.so
(II) Module shadow: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.1.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "fb"
(II) LoadModule: "fb"

(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(==) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? No, I don't.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[4] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[5] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[6] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[7] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[8] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[9] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[10] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[11] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[12] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[13] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[14] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[15] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[16] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[17] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[18] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[19] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[20] -1 0 0xffffffff - 0xffffffff (0x1) MX[B]
[21] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B]
[22] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B]
[23] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B]
[24] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[25] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[26] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[27] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[28] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[29] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[30] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[31] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[32] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[33] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
[34] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B]
[35] -1 0 0x00000000 - 0x00000000 (0x1) IX[B]
(II) Loading sub module "int10"
(II) LoadModule: "int10"

(II) Reloading /usr/lib/xorg/modules//libint10.so
(II) VESA(0): initializing int10
(II) VESA(0): Primary V_BIOS segment is: 0xc000
(II) VESA(0): VESA BIOS detected
(II) VESA(0): VESA VBE Version 3.0
(II) VESA(0): VESA VBE Total Mem: 16384 kB
(II) VESA(0): VESA VBE OEM: ATI ATOMBIOS
(II) VESA(0): VESA VBE OEM Software Rev: 11.6
(II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2005, ATI Technologies Inc.
(II) VESA(0): VESA VBE OEM Product: RV770
(II) VESA(0): VESA VBE OEM Product Rev: 01.00
(II) VESA(0): virtual address = 0x7f8c4d1c7000,
physical address = 0xd0000000, size = 16777216
(II) VESA(0): VBESetVBEMode failed...Tried again without customized values.
(==) VESA(0): Default visual is TrueColor
(==) VESA(0): Backing store disabled
(II) VESA(0): DPMS enabled
(==) RandR enabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) AIGLX: Screen 0 is not DRI capable
(II) config/hal: Adding input device Macintosh mouse button emulation
(II) LoadModule: "evdev"

(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.5.2, module version = 2.0.99
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 2.1
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Configuring as mouse
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) config/hal: Adding input device AT Translated Set 2 keyboard
(**) AT Translated Set 2 keyboard: always reports core events
(**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
(II) AT Translated Set 2 keyboard: Found keys
(II) AT Translated Set 2 keyboard: Configuring as keyboard
(II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) AT Translated Set 2 keyboard: xkb_rules: "evdev"
(**) Option "xkb_model" "pc105"
(**) AT Translated Set 2 keyboard: xkb_model: "pc105"
(**) Option "xkb_layout" "us"
(**) AT Translated Set 2 keyboard: xkb_layout: "us"
(II) config/hal: Adding input device HID 04b4:0033
(**) HID 04b4:0033: always reports core events
(**) HID 04b4:0033: Device: "/dev/input/event2"
(II) HID 04b4:0033: Found x and y relative axes
(II) HID 04b4:0033: Found 5 mouse buttons
(II) HID 04b4:0033: Configuring as mouse
(II) XINPUT: Adding extended input device "HID 04b4:0033" (type: MOUSE)
(**) HID 04b4:0033: YAxisMapping: buttons 4 and 5
(**) HID 04b4:0033: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
AUDIT: Thu Dec 11 22:13:47 2008: 6081 X: client 4 rejected from local host ( uid=0 gid=0 pid=6293 )
AUDIT: Thu Dec 11 22:13:37 2008: 6081 X: client 4 rejected from local host ( uid=0 gid=0 pid=6542 )
AUDIT: Thu Dec 11 22:13:45 2008: 6081 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=6664 )
Auth name: MIT-MAGIC-COOKIE-1 ID: -1
AUDIT: Thu Dec 11 22:13:45 2008: 6081 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=6665 )
Auth name: MIT-MAGIC-COOKIE-1 ID: -1
AUDIT: Thu Dec 11 22:13:45 2008: 6081 X: client 4 rejected from local host ( uid=1000 gid=1000 pid=6666 )
Auth name: MIT-MAGIC-COOKIE-1 ID: -1

StormWalker
December 12th, 2008, 07:58 AM
everytime that I try to fix I get the "Out Of Range"....
If I got to the "HArdware Drivers" and Activate I got the "Out Of Range"
.........I tried to edit the xorg... the failsafe...de xorg.0.conf.... and when I reiniciate it comes to the screem....Working on Low-graphic mode... so I got to the XFix...and Againg all the same.. 800x600 ...




I don't know what to do... because when I had Windows I was using 1024x768 and was working fine........

I'm Reading some Ubuntu Books ... but I still can't fix that.... =)

StormWalker
December 15th, 2008, 09:16 AM
Anybody ??

Larrxi
January 11th, 2009, 02:46 PM
I'll get the same motherboard tomorrow because my old could not handle the Phenom 9950.

Maybe it is wrong with the monitor? Do you got a CRT? I had a Radeon 4850 a month ago got a out of range with a CRT.

melojo
January 11th, 2009, 03:14 PM
Boot into recovery and type this below.



sudo dpkg-reconfigure xserver-xorg