640 x 480 resolution problem [solved]

I testing Arch. I've got it installed as a vbox guest. I plan (if things go well) to eventually turn it into a live CD, as I can't find one out there now that fully meets my needs.
So far, things have gone pretty smooth, but now I've hit a wall. I got lxde installed (live CD, so keep it light and lean) and it works. The problem is the resolution is stuck at 640 x 480. I can't increase it. xrandr says my max is 640 x 480, which I know isn't true. Obviously installing specific drivers isn't an option as I plan on doing the live CD. Quite a bit of searching turned up several solved, but most of those were physical hardware issues in the end (Puppy does 1600x1050 as a guest, so it's not hardware or vbox) and "it just fixed itself" isn't an answer for me. What am I doing wrong?
Xorg.0.log
[ 4.981]
X.Org X Server 1.15.0
Release Date: 2013-12-27
[ 4.981] X Protocol Version 11, Revision 0
[ 4.981] Build Operating System: Linux 3.12.5-1-ARCH i686
[ 4.981] Current Operating System: Linux AveA 3.12.9-1-ARCH #1 SMP PREEMPT Sun Jan 26 09:15:23 CET 2014 i686
[ 4.981] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=fbaafe30-b716-4dfa-b1b6-a1d8e054b5d1 rw quiet
[ 4.981] Build Date: 09 January 2014 09:32:33AM
[ 4.981]
[ 4.981] Current version of pixman: 0.32.4
[ 4.981] Before reporting problems, check [url]http://wiki.x.org[/url]
to make sure that you have the latest version.
[ 4.981] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 4.981] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Feb 15 22:46:13 2014
[ 5.028] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 5.028] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 5.072] (==) No Layout section. Using the first Screen section.
[ 5.072] (==) No screen section available. Using defaults.
[ 5.072] (**) |-->Screen "Default Screen Section" (0)
[ 5.072] (**) | |-->Monitor "<default monitor>"
[ 5.073] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 5.073] (==) Automatically adding devices
[ 5.073] (==) Automatically enabling devices
[ 5.073] (==) Automatically adding GPU devices
[ 5.090] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 5.090] Entry deleted from font path.
[ 5.115] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 5.115] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 5.115] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 5.115] (II) Loader magic: 0x8265660
[ 5.115] (II) Module ABI versions:
[ 5.115] X.Org ANSI C Emulation: 0.4
[ 5.115] X.Org Video Driver: 15.0
[ 5.115] X.Org XInput driver : 20.0
[ 5.115] X.Org Server Extension : 8.0
[ 5.116] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 5.130] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/33554432
[ 5.130] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 5.131] Initializing built-in extension Generic Event Extension
[ 5.131] Initializing built-in extension SHAPE
[ 5.131] Initializing built-in extension MIT-SHM
[ 5.131] Initializing built-in extension XInputExtension
[ 5.131] Initializing built-in extension XTEST
[ 5.131] Initializing built-in extension BIG-REQUESTS
[ 5.131] Initializing built-in extension SYNC
[ 5.131] Initializing built-in extension XKEYBOARD
[ 5.131] Initializing built-in extension XC-MISC
[ 5.131] Initializing built-in extension SECURITY
[ 5.132] Initializing built-in extension XINERAMA
[ 5.132] Initializing built-in extension XFIXES
[ 5.132] Initializing built-in extension RENDER
[ 5.132] Initializing built-in extension RANDR
[ 5.132] Initializing built-in extension COMPOSITE
[ 5.132] Initializing built-in extension DAMAGE
[ 5.132] Initializing built-in extension MIT-SCREEN-SAVER
[ 5.132] Initializing built-in extension DOUBLE-BUFFER
[ 5.132] Initializing built-in extension RECORD
[ 5.132] Initializing built-in extension DPMS
[ 5.132] Initializing built-in extension Present
[ 5.132] Initializing built-in extension DRI3
[ 5.132] Initializing built-in extension X-Resource
[ 5.132] Initializing built-in extension XVideo
[ 5.132] Initializing built-in extension XVideo-MotionCompensation
[ 5.132] Initializing built-in extension XFree86-VidModeExtension
[ 5.132] Initializing built-in extension XFree86-DGA
[ 5.132] Initializing built-in extension XFree86-DRI
[ 5.132] Initializing built-in extension DRI2
[ 5.132] (II) "glx" will be loaded by default.
[ 5.132] (II) LoadModule: "dri2"
[ 5.132] (II) Module "dri2" already built-in
[ 5.132] (II) LoadModule: "glamoregl"
[ 5.132] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
[ 5.323] (II) Module glamoregl: vendor="X.Org Foundation"
[ 5.323] compiled for 1.15.0, module version = 0.6.0
[ 5.323] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.323] (II) LoadModule: "glx"
[ 5.338] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 5.352] (II) Module glx: vendor="X.Org Foundation"
[ 5.352] compiled for 1.15.0, module version = 1.0.0
[ 5.352] ABI class: X.Org Server Extension, version 8.0
[ 5.352] (==) AIGLX enabled
[ 5.352] Loading extension GLX
[ 5.352] (==) Matched vboxvideo as autoconfigured driver 0
[ 5.352] (==) Matched vboxvideo as autoconfigured driver 1
[ 5.352] (==) Matched modesetting as autoconfigured driver 2
[ 5.352] (==) Matched fbdev as autoconfigured driver 3
[ 5.352] (==) Matched vesa as autoconfigured driver 4
[ 5.352] (==) Assigned the driver to the xf86ConfigLayout
[ 5.352] (II) LoadModule: "vboxvideo"
[ 5.371] (WW) Warning, couldn't open module vboxvideo
[ 5.371] (II) UnloadModule: "vboxvideo"
[ 5.371] (II) Unloading vboxvideo
[ 5.371] (EE) Failed to load module "vboxvideo" (module does not exist, 0)
[ 5.371] (II) LoadModule: "modesetting"
[ 5.371] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 5.388] (II) Module modesetting: vendor="X.Org Foundation"
[ 5.388] compiled for 1.15.0, module version = 0.8.1
[ 5.388] Module class: X.Org Video Driver
[ 5.389] ABI class: X.Org Video Driver, version 15.0
[ 5.389] (II) LoadModule: "fbdev"
[ 5.389] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 5.393] (II) Module fbdev: vendor="X.Org Foundation"
[ 5.393] compiled for 1.15.0, module version = 0.4.4
[ 5.393] Module class: X.Org Video Driver
[ 5.393] ABI class: X.Org Video Driver, version 15.0
[ 5.393] (II) LoadModule: "vesa"
[ 5.394] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 5.403] (II) Module vesa: vendor="X.Org Foundation"
[ 5.404] compiled for 1.15.0, module version = 2.3.2
[ 5.404] Module class: X.Org Video Driver
[ 5.404] ABI class: X.Org Video Driver, version 15.0
[ 5.404] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 5.404] (II) FBDEV: driver for framebuffer: fbdev
[ 5.404] (II) VESA: driver for VESA chipsets: vesa
[ 5.404] (++) using VT number 1
[ 5.404] (WW) Falling back to old probe method for modesetting
[ 5.404] (II) Loading sub module "fbdevhw"
[ 5.404] (II) LoadModule: "fbdevhw"
[ 5.404] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 5.415] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 5.415] compiled for 1.15.0, module version = 0.0.2
[ 5.415] ABI class: X.Org Video Driver, version 15.0
[ 5.415] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[ 5.415] (II) FBDEV(1): using default device
[ 5.415] (WW) Falling back to old probe method for vesa
[ 5.416] (EE) Screen 0 deleted because of no matching config section.
[ 5.416] (II) UnloadModule: "modesetting"
[ 5.416] (II) FBDEV(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 5.416] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[ 5.416] (==) FBDEV(0): RGB weight 888
[ 5.416] (==) FBDEV(0): Default visual is TrueColor
[ 5.416] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[ 5.416] (II) FBDEV(0): hardware: VESA VGA (video memory: 1216kB)
[ 5.416] (II) FBDEV(0): checking modes against framebuffer device...
[ 5.416] (II) FBDEV(0): checking modes against monitor...
[ 5.416] (--) FBDEV(0): Virtual size is 640x480 (pitch 640)
[ 5.416] (**) FBDEV(0): Built-in mode "current": 30.7 MHz, 36.9 kHz, 73.3 Hz
[ 5.416] (II) FBDEV(0): Modeline "current"x0.0 30.72 640 672 752 832 480 484 488 504 -hsync -vsync -csync (36.9 kHz b)
[ 5.416] (==) FBDEV(0): DPI set to (96, 96)
[ 5.416] (II) Loading sub module "fb"
[ 5.416] (II) LoadModule: "fb"
[ 5.416] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 5.422] (II) Module fb: vendor="X.Org Foundation"
[ 5.422] compiled for 1.15.0, module version = 1.0.0
[ 5.422] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.422] (**) FBDEV(0): using shadow framebuffer
[ 5.422] (II) Loading sub module "shadow"
[ 5.422] (II) LoadModule: "shadow"
[ 5.422] (II) Loading /usr/lib/xorg/modules/libshadow.so
[ 5.426] (II) Module shadow: vendor="X.Org Foundation"
[ 5.426] compiled for 1.15.0, module version = 1.1.0
[ 5.426] ABI class: X.Org ANSI C Emulation, version 0.4
[ 5.426] (II) UnloadModule: "vesa"
[ 5.426] (II) Unloading vesa
[ 5.426] (==) Depth 24 pixmap format is 32 bpp
[ 5.426] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 5.433] (==) FBDEV(0): Backing store enabled
[ 5.434] (==) FBDEV(0): DPMS enabled
[ 5.434] (==) RandR enabled
[ 5.451] (II) AIGLX: Screen 0 is not DRI2 capable
[ 5.451] (EE) AIGLX: reverting to software rendering
[ 5.993] (II) AIGLX: Loaded and initialized swrast
[ 5.993] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 6.318] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 6.318] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 6.318] (II) LoadModule: "evdev"
[ 6.318] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 6.331] (II) Module evdev: vendor="X.Org Foundation"
[ 6.331] compiled for 1.15.0, module version = 2.8.2
[ 6.331] Module class: X.Org XInput Driver
[ 6.331] ABI class: X.Org XInput driver, version 20.0
[ 6.331] (II) Using input driver 'evdev' for 'Power Button'
[ 6.331] (**) Power Button: always reports core events
[ 6.331] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 6.331] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 6.331] (--) evdev: Power Button: Found keys
[ 6.331] (II) evdev: Power Button: Configuring as keyboard
[ 6.331] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event1"
[ 6.331] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 6.331] (**) Option "xkb_rules" "evdev"
[ 6.331] (**) Option "xkb_model" "pc104"
[ 6.331] (**) Option "xkb_layout" "us"
[ 6.351] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
[ 6.351] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 6.351] (II) Using input driver 'evdev' for 'Sleep Button'
[ 6.351] (**) Sleep Button: always reports core events
[ 6.351] (**) evdev: Sleep Button: Device: "/dev/input/event2"
[ 6.351] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 6.351] (--) evdev: Sleep Button: Found keys
[ 6.351] (II) evdev: Sleep Button: Configuring as keyboard
[ 6.351] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input3/event2"
[ 6.351] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 6.351] (**) Option "xkb_rules" "evdev"
[ 6.351] (**) Option "xkb_model" "pc104"
[ 6.351] (**) Option "xkb_layout" "us"
[ 6.352] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 6.352] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event3)
[ 6.352] (**) VirtualBox mouse integration: Applying InputClass "evdev pointer catchall"
[ 6.352] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
[ 6.352] (**) VirtualBox mouse integration: always reports core events
[ 6.352] (**) evdev: VirtualBox mouse integration: Device: "/dev/input/event3"
[ 6.352] (--) evdev: VirtualBox mouse integration: Vendor 0x80ee Product 0xcafe
[ 6.352] (--) evdev: VirtualBox mouse integration: Found 1 mouse buttons
[ 6.352] (--) evdev: VirtualBox mouse integration: Found absolute axes
[ 6.352] (--) evdev: VirtualBox mouse integration: Found x and y absolute axes
[ 6.352] (--) evdev: VirtualBox mouse integration: Found absolute touchscreen
[ 6.352] (II) evdev: VirtualBox mouse integration: Configuring as touchscreen
[ 6.352] (**) evdev: VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
[ 6.352] (**) evdev: VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 6.352] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/input/input4/event3"
[ 6.352] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: TOUCHSCREEN, id 8)
[ 6.352] (II) evdev: VirtualBox mouse integration: initialized for absolute axes.
[ 6.352] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
[ 6.352] (**) VirtualBox mouse integration: (accel) acceleration profile 0
[ 6.352] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
[ 6.352] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
[ 6.352] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/js0)
[ 6.353] (II) No input driver specified, ignoring this device.
[ 6.353] (II) This device may have been added with another device file.
[ 6.353] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event5)
[ 6.353] (**) VirtualBox USB Tablet: Applying InputClass "evdev pointer catchall"
[ 6.353] (II) Using input driver 'evdev' for 'VirtualBox USB Tablet'
[ 6.353] (**) VirtualBox USB Tablet: always reports core events
[ 6.353] (**) evdev: VirtualBox USB Tablet: Device: "/dev/input/event5"
[ 6.353] (--) evdev: VirtualBox USB Tablet: Vendor 0x80ee Product 0x21
[ 6.353] (--) evdev: VirtualBox USB Tablet: Found 9 mouse buttons
[ 6.353] (--) evdev: VirtualBox USB Tablet: Found scroll wheel(s)
[ 6.353] (--) evdev: VirtualBox USB Tablet: Found relative axes
[ 6.353] (--) evdev: VirtualBox USB Tablet: Found absolute axes
[ 6.353] (--) evdev: VirtualBox USB Tablet: Found x and y absolute axes
[ 6.353] (--) evdev: VirtualBox USB Tablet: Found absolute touchscreen
[ 6.353] (II) evdev: VirtualBox USB Tablet: Configuring as touchscreen
[ 6.353] (II) evdev: VirtualBox USB Tablet: Adding scrollwheel support
[ 6.353] (**) evdev: VirtualBox USB Tablet: YAxisMapping: buttons 4 and 5
[ 6.353] (**) evdev: VirtualBox USB Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 6.353] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb2/2-1/2-1:1.0/input/input6/event5"
[ 6.354] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: TOUCHSCREEN, id 9)
[ 6.354] (WW) evdev: VirtualBox USB Tablet: touchpads, tablets and touchscreens ignore relative axes.
[ 6.354] (II) evdev: VirtualBox USB Tablet: initialized for absolute axes.
[ 6.354] (**) VirtualBox USB Tablet: (accel) keeping acceleration scheme 1
[ 6.354] (**) VirtualBox USB Tablet: (accel) acceleration profile 0
[ 6.354] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
[ 6.354] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
[ 6.354] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/js1)
[ 6.354] (II) No input driver specified, ignoring this device.
[ 6.354] (II) This device may have been added with another device file.
[ 6.354] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse0)
[ 6.354] (II) No input driver specified, ignoring this device.
[ 6.354] (II) This device may have been added with another device file.
[ 6.354] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 6.355] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 6.355] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 6.355] (**) AT Translated Set 2 keyboard: always reports core events
[ 6.355] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 6.355] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 6.355] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 6.355] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 6.355] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 6.355] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 10)
[ 6.355] (**) Option "xkb_rules" "evdev"
[ 6.355] (**) Option "xkb_model" "pc104"
[ 6.355] (**) Option "xkb_layout" "us"
[ 6.355] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event6)
[ 6.355] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
[ 6.355] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
[ 6.355] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
[ 6.355] (**) evdev: ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event6"
[ 6.355] (--) evdev: ImExPS/2 Generic Explorer Mouse: Vendor 0x2 Product 0x6
[ 6.355] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
[ 6.355] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
[ 6.355] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found relative axes
[ 6.355] (--) evdev: ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
[ 6.355] (II) evdev: ImExPS/2 Generic Explorer Mouse: Configuring as mouse
[ 6.355] (II) evdev: ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
[ 6.355] (**) evdev: ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
[ 6.355] (**) evdev: ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 6.355] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input7/event6"
[ 6.355] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 11)
[ 6.355] (II) evdev: ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
[ 6.355] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
[ 6.355] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
[ 6.355] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
[ 6.355] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
[ 6.355] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse1)
[ 6.355] (II) No input driver specified, ignoring this device.
[ 6.355] (II) This device may have been added with another device file.
[ 6.356] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
[ 6.356] (II) No input driver specified, ignoring this device.
[ 6.356] (II) This device may have been added with another device file.
[ 6.358] (EE) FBDEV(0): FBIOBLANK: Invalid argument
Last edited by rsberzerker (2014-02-16 23:30:00)

Vesa drivers are normally used as a fallback as it is very generic. Use the free or proprietary drivers for your intel/ati/nvidia instead.
Here is a quote from the beginner's guide:
"The vesa driver is a generic mode-setting driver that will work with almost every GPU, but will not provide any 2D or 3D acceleration. If a better driver cannot be found or fails to load, Xorg will fall back to vesa. To install it:"
https://wiki.archlinux.org/index.php/Beginners'_Guide/Post-installation#Install_a_video_driver

Similar Messages

Suddenly LED 24" Arrangement broken, only get 640 x 480 resolution

Yesterday, did a SuperDuper backup instructing "when finished shut down." This morning I fired up my MacBook Pro and the LED 24" and the latter will only display 640 X 480 resolution (very big with jaggies). Also the prior arrangement setting is gone and cannot be reset. I've tried unplugging the LED and restarting the MacBook Pro. Neither changes the situation.
Incidentally, in the Display window of System Preferences the MacBook Pro shows everything as normal. The Display window of the LED shows the ONLY resolution available is 640 X 280. In other words, it is not as though other options are presented to select. Toggling mirroring doesn't seem to do anything either.
Please help. In this condition the LED is useless.

Well, I seemed to have fixed the problem by unplugging the LED from both the MacBook Pro and the wall outlet. After counting to 10 I plugged it all back together and the LED is showing the proper resolution, arrangement and resolution options.
Of course, I'm still interested in trying to figure out what happened in the first place. If any of you have ideas, I'd like to hear them. The LED is plugged into a surge strip, so I'm discounting that. Perhaps while I was away last night, there was a power failure. Anyway, I've had this display for 8 months, love it and it has never behaved this way before.

Screen stuck on 640 x 480 resolution

I have a B & W g3 and about two months ago my screen resolution changed from 1280 x 960 to 640 x 480 making it preety difficult to do some simple tasks such as surfing the internet. If anyone has any clue as to how to solve this problem please help!!!

What kind of video connector is on your graphics board and monitor? Can you describe it? Does it have three rows of pins or two? I am trying to remember, but I believe a B&W G3 may date back to Apple's old monitor detection scheme of using jumpers and diodes across certain pins on the video connector. If a monitor wasn't read correctly or no monitor detected, it reverted to 640 x 480 at 67Hz, which is a legacy Apple timing associated with their very first Mac color monitor, a 14" that shipped with the Mac II. I think that is what is happening here. For some reason the graphics card isn't recognizing the display. The problem could be on either end. It's hard to say. Is there any way for you to get your hands on a second monitor to try? That would help determine where the problem lies.

Xfce Resolution Problems [SOLVED]

I installed Arch on my old box. Xfce won't display 1024x768.
I set GRUB with vga=773 and the console displays in 1024x768, but when I startxfce4 the GUI is in 640x480. I'm tired as hell, so I'll try out suggestions in the morning. Thanks for any help in advance!
EDIT: BTW, I tried setting xorg.conf already and it didn't work.
Last edited by Superjoshi (2009-10-30 18:32:38)

Superjoshi wrote:
Thanks boss, that did the trick. I totally forgot about those packages...
Linux always makes me feel like a dumbass because it's always my fault. Only advantage to Windows is blaming it instead of yourself! LOL
No problem. And don't be too hard on yourself. Just mark the thread as [SOLVED].

Mac Mini defaults to 640 by 480 and can't be reset?

Hello fellow macfolks...
I have a Mac Mini that I use only on an occasional basis. Tonight I connected it to my trusty, known-good NEC 20 inch monitor, and lo and behold, the mini boots up at 640 by 480 resolution with NO other choices in teh display panel.
I tried resetting the NV RAM, no good.
I tried to do a software update, and believe it or not, YOU CAN'T CLICK ON THE AGREED BUTTON ON THE SOFTWARE LICENSE TO UPDATE THE SYSTEM SOFTWARE!!!! And return, or enter don't work either.
Any suggestions as to what I should do? I looked around for a display preferences file that I might trash, but none are obvious. I tried a different (known good) monitor with a different cable, SAME THING.
I then took the thing to Frys and tried it with an HDMI monitor... it came up at a higher resolution, but still only one setting...
Is this a hardware problem?
Any help any of you geniuses at large can provide would be appreciated...
And Apple... you need to make sure that system updates can be performed at any resolution, or make your base default something higher please!
Regards
Groovology
Macs to the Max!

If you did a clean install of the system then it is likely a hardware issue. Someone here more knowledeable than myself may know something more to help you, but after exhausting all other options I would lean towards a hardware problem.
You never said if when you started from the system disk if it also ran in 640x480. While I know you cannot change resolutions from the startup CD, it would be readily apparent if it too was running in 640x480 or if the other issue you had appeared. That would certainly indicate a hardware issue since the install disk should be a "clean" version of the system. You also never answered the question about safe boot, but after a clean install I would think that point is moot anyway.
I am assuming you did a clean install of the system, which if software was an issue it should have resolved it. I am unaware of any firmware or other updates that may have caused (or coulkd fix) this problem, but again I have not had any issues with any of the minis I own so I have not done any amount of troubleshooting.
Sorry I could not be of more help.

MulitScan 15 not doing 640 X 480 anymore

My Apple Multiple Scan 15 monitor is having trouble with 640 X 480 resolution. Left and right sides curve inwards and the menu bar is way past the top of the screen. This just happened the last time I turned it on, no obvious damage or settings changes. 800 X 600 works as does 832 X 764. Is this a sign of impending monitor failure? It is currently being used with a Performa 6300CD, and I use the lower resolution for watching TV.

A further curious fact to add to the mystery; the resolution 640 X 480 @ 67Hz is the one that I am having the problem with, but when I chose “all” instead of “Recommended” resolutions from the OS 8.1 Monitors & Sound control panel, a resolution of 640 X 480 appeared with no refresh rate given, and that one works fine!?! And of course I erred when I said that there is a resolution of 832 X 764, it is actually 832 X 624 @ 75Hz.
I basically got this Monitor for free louie, I was just wondering if anyone else had experienced this problem and knew of a quick, inexpensive fix, or if I should start the search for another MultiSync monitor.
Apropos of nothing, I do have another monitor waiting in the wings, a beautiful Apple 16” Color Display with a Trinitron screen, but unfortunately it only has one resolution; 832 X 624, which is a setting that the standard digitizer of the Apple Video Player won’t work with. Hence my need for a working MultiSync monitor.

Screen resolution stuck at 640 x 480

Hi folks,
I'm using OS 10.4.9 on a Power Mac G4 with one of those grey eggshell-like Apple displays. A week or so ago, I lost all resolution options (I always had it at 1024 x 768) and I'm stuck at 640 x 480. Nothing else appears in System Preferences besides this option.
In the past a simple restart solved the problem; not this time. I already zapped the NVRAM to no avail.
Any suggestions?

I searched the forums with no satisfactory solution to the problem.
Anyone have suggestions?

Xserve screen resolution stuck at 640 x 480

I'm troubleshooting a Xserve for a friend's company. After a restart a few days ago, their Xserve will only display at 640 x 480. They have it connected to a standard VGA monitor, which did display higher resolutions before. I know some of the basic troubleshooting methods like reseting the PRAM and trashing the display prefs, but I'd like to try fixing it without rebooting the server or knocking people off. Any ideas on how to correct this issue without rebooting?

beavis51-
Greetings and welcome to the Apple boards.
Did you check your cable and connections? I am not positive but it seems to me that the video card may have to sense the ability of the monitor to display the proper resolution.
Have you tried connecting the monitor to another device to make sure it is not the monitor?
Luck-
-DaddyPaycheck

HP Envy Game resolution problem

Hi
I am having trouble with my Envy 17 after installing BlazBlue, I am having trouble with games resolution all games run perfectly fine but in a 640*480 resolution. Games that used to run perfectly in a full screen reso now only run in 640*480. Not long ago that I discovered if I connect the laptop to the HDTV Bravia I have all games run in full reso again. I tried uninstalling the drivers and restarting the laptop and reinstall the original drivers it didn't work. I tried installing the newest drivers in hope it will get fixed but it didn't. I am out of options ..... the only that I have in mind is to factory reset the laptop and im not even sure that will solve the problem... can someone help me please with a solution that might work?? thanks in advance.
I have these photos which I took that might help you recognize the problem better thanks again.
(without the HD cable being connected)
http://imageshack.us/photo/my-images/43/20110630214956.jpg/
http://imageshack.us/photo/my-images/820/20110630220234.jpg/
(with The HD cable being connected)
http://imageshack.us/photo/my-images/804/20110630215032.jpg/
http://imageshack.us/photo/my-images/707/20110630215253.jpg/

I just wanted to add that scaling options in the graphics properties can't be modified. I was messing around a bit with the options and I lowered my laptop's resolution to 800*600.
right click on desktop -->Screen Resolution --> Resolution 800*600
anyhow after doing that I went back to the scaling option in the graphic properties
right click on desktop --> "1st choice" graphics properties --> My Built-in Displays "you have to be in advance mode"
then I saw that the scaling options were changeable so I changed it from Preserve Aspect Ratio to Full Screen.
Apply the changes and got the problem fixed for some of the games. So its half fixed some games started running on full screen and some didn't... please any help? i've been suffering from this annoying problem for a month now.. thanks again people.

640 x 480

I need to have my mini/display set at 640 x 480. So, after I change the resolution to 640 x 480 then restart the computer, the resolution automatically switches back to 1024 x 786. I've tried this on numerous displays all with the same outcome. This is the only resolution in the list of options given in the preferences that this happens to. All others resstart just as I set them in the preferences...any clue as to what is going on? Any help would be appreciated!

That's a really interesting problem. 640x480 is the lowest resolution "console" mode that a Mac puts out. I never noticed before that you can't leave a Mac set at that resolution through a restart, but I have honestly never tried.
Does the bad behavior change if you select different refresh rates? Maybe that would trigger the Mac to think "you really mean it" that you want 640x480 if you set a high refresh rate, like 85Hz or more. Alternately, if you are really desperate for a solution, it might work to use a product like SwitchRes X to build a custom 640x480 resolution. I would think that it would stick in that case and not change on you during restarts.

24' cinema display stuck in 640 X 480 - unless used in Apple Store!

I really need some help with my new MBP and 24" LED cinema display that is driving me crazy. The first part of the problem is that when I bring my MBP out of sleep and attach the monitor, or if I simply disconnect the monitor and reconnect it without sleeping, it only shows 640X480 and no options for other display settings.
I have tried a great many things and suggestions, including deleting the com.apple.windowserver.plist files (system and byhost versions), repairing the permissions, resetting the pram. Nothing makes any difference to this behaviour.
The second part of the problem is that having decided it was the monitor itself I took both the display and the MBP back to the apple store today where it worked faultlessly - no amount of rebooting, sleeping and attaching/detaching would make the error occur. Once we gave and I got them both home again - it reverted to the previous, faulty behaviour! We wondered in the store if it was a faulty cable - but no amount of wriggling of the cable makes any difference.
When The display is correct, the system profiler shows:
LED Cinema Display:
Resolution: 1920 x 1200
Depth: 32-bit Color
Core Image: Software
Mirror: Off
Online: Yes
Quartz Extreme: Not Supported
Connection Type: DisplayPort
When the display goes to its 640 X 480 mode, the system profiler shows:
Display:
Resolution: 640 x 480
Depth: 32-bit Color
Core Image: Hardware Accelerated
Mirror: Off
Online: Yes
Quartz Extreme: Supported
Rotation: Supported
Connection Type: DisplayPort
I found a few things relating to issues with recognition of monitors when coming out of sleep - but this monitor was made specifically for this MBP, and others don't seem to be having this problem. My MBP also works fine with my DELL flatscreen display at a high resolution.
Anyone got any idea what else I can change before I have to completely rebuild my MBP. I am really confused by this - why would it insist on working in the Apple Store and refuse to work correctly at home?

First off, the power cable is not permanently attached to the monitor. It is a 3-pronged, grounded connector at the monitor end. I know because I just disconnected mine and freed up the entire cable. Since I'm one of those who just does stuff even when it may not always be well-advised, I can report on an experience that could bear on your situation.
I had my Mac Pro running when I reached around the back of my 24" LED display and pulled the plug from the monitor. Of course, the monitor instantly went "black". I quickly replugged it back in (no, I didn't shut anything down and risked frying the monitor). When the monitor returned to life it was "stuck" in 640 x 480 mode and I could only "restart" or "shut down" to get it restored to the 1920 x 1200 mode I keep it in.
This suggests to me that the problem lies in your cabling and power delivery system. Perhaps you are getting power surges or power spikes that have the equivalent effect of taking your monitor "off" and then returning the monitor to a 640 x 480 condition after restoring power.
If it were me, I'd try with a new monitor cable to power. I'm betting your problem doesn't have anything to do with the monitor to computer cable, but it isn't the only cable here. Something is disrupting the constant power feed and I'm betting the problem is amplified by faulty power cord. Since I just replicated your situation by literally pulling the plug and replugging it in, it seems to me that this would be a fruitful area of investigation.
Hope this leads you somewhere positive.

Running OS X Lion at 640 x 480

How do I run Lion at 640 x 480, I have an old CRT projector and this is the maximum resolution it will handle. Snow Leopard on my old MBP managed it but the minimum I can see on Lion is 800 x 600.. There must be some third party software or a work around?
Cheers,
Chris

I know this is an old post, but for everyone which has the same problem:
Try to use:
https://github.com/jhford/screenresolution
This is a command line utility. You can install it and run from Terminal.app.

When I open icloud, desktop is opened with a pixel size of 640 x 480

When I open icloud, desktop is opened with a pixel size of 640 x 480
The normal pixel size is 1680 x 1050 on my desk.
This means that I can not turn the button so all the settings are installed.
How to solve this problem?
I use Internet Explore as your browser.
Operating system is windoes 7 ultimate.

Move the cursor to the very top of the screen, maybe push up a bit. The main menubar should then appear. All the way to the right should be a bright blue icon - click it, and the Safari window should revert to 'normal' size.
Pressing Command-Control-F should accomplish the same thing.
Once it is back to normal size, click and hold on the top portion of the Safari window and drag to left or right to place it where you want it to be. Once you leave it there, the next time you open Safari it should open its window in normal size at that place.
If you need to re-size the window a bit, you can click-and-hold on the bottom-right corner of the window and drag to resize it.

6220c pseudo 640 x 480 video

pseudo in terms of true resolution, I would love to read comments from users about the 6220c 640 x 480 video resolution, my feeling is this was misrepresented in advertising it is so obviously not a true 640 x 480 I mean you can create a 640 x 480 frame size from 176 x 144 if you really want to, in the case of 6220c it seems to me this is a 320 x 240 video interpolated by some proprietary manner to 640 x 480 frame size and passed off as such for what purpose that serves I have no idea- I would like to get the observations of others who have used it what do you think

I assume you are using the main camera (5 MP) to take the video.
I don't know what to say. Surely the sensor is more than capable of recording video at 640 x 480. And since the videos you are taking are 640x480 my guess is that the problem is the video image quality.
Maybe someone else that has this model can comment.
640K Should be enough for everybody
El_Loco Nokia Video Blog

42 Inch Philips Plasma Resolution Problem

I have tried hooking up my Mini to my 42 inch Philips plasma TV and I am having a problem getting the resolution issues solved. I have after market software that allows me to make resolutions available after configuring them and restarting the computer. Does anyone have the same TV and know what the setup should be? I am currently at 1280x720 and it seems to be ok for vertical, but horizontally things are cutoff the screen. Any help would be much appreciated since this problems seems to have started with the update to 10.5.7.
Message was edited by: hatesand

Hi Hatesand, what settings did you change to make this work? On the mini or on the plasma?
I'm still plodding along with 1920x1080 as nothing seems to make the monitor stay in 1920x1200
Syed

640 x 480 resolution problem [solved]

Similar Messages

Maybe you are looking for