No video module?

/var/log/Xorg.0.log says, '[EE] Failed to load "fbdev" (module does not exist, 0)', and then on the next line, 'FATAL: Module i810 not found.' 'drm' also failed to open, and 'DRI' failed. 'startx' DOES open the basic X Window environment, although setting a terminal resolution in /boot/grub/menu.lst leads to screwed up terminal display after I exit X.
hwdetect doesn't list a video module.
I have Intel integrated graphics on this computer (an old Dell Dimension L733r), the hardware being a vga-compatible Intel 82810E DC-133 (CGC) chipset, according to lspci. I haved installed both available Intel drivers in the pacman database as well as vesa, and nothing changes.
Can someone at least point me in the right direction? I don't need a complete walkthrough - a few links to relevant info would be enough to give me an idea what to try next.
Thank you!

Xorg log:
[ 1084.614]
X.Org X Server 1.11.4
Release Date: 2012-01-27
[ 1084.614] X Protocol Version 11, Revision 0
[ 1084.615] Build Operating System: Linux 3.2.2-1-ARCH i686
[ 1084.615] Current Operating System: Linux Louise 3.2.7-1-ARCH #1 SMP PREEMPT Tue Feb 21 16:59:04 UTC 2012 i686
[ 1084.615] Kernel command line: root=/dev/disk/by-uuid/66114814-cb1f-4868-bc93-cfab0c21eb06 ro
[ 1084.615] Build Date: 29 January 2012 03:41:53PM
[ 1084.615]
[ 1084.615] Current version of pixman: 0.24.4
[ 1084.616] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 1084.616] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1084.617] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Mar 6 07:58:19 2012
[ 1084.654] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 1084.655] (==) No Layout section. Using the first Screen section.
[ 1084.655] (==) No screen section available. Using defaults.
[ 1084.655] (**) |-->Screen "Default Screen Section" (0)
[ 1084.655] (**) | |-->Monitor "<default monitor>"
[ 1084.672] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 1084.673] (==) Automatically adding devices
[ 1084.673] (==) Automatically enabling devices
[ 1084.716] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 1084.716] Entry deleted from font path.
[ 1084.716] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1084.716] Entry deleted from font path.
[ 1084.716] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 1084.716] Entry deleted from font path.
[ 1084.717] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1084.717] Entry deleted from font path.
[ 1084.717] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 1084.717] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1084.717] Entry deleted from font path.
[ 1084.717] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 1084.717] (==) FontPath set to:
/usr/share/fonts/misc/
[ 1084.717] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 1084.717] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 1084.735] (II) Loader magic: 0x8228580
[ 1084.735] (II) Module ABI versions:
[ 1084.735] X.Org ANSI C Emulation: 0.4
[ 1084.735] X.Org Video Driver: 11.0
[ 1084.735] X.Org XInput driver : 13.0
[ 1084.735] X.Org Server Extension : 6.0
[ 1084.737] (--) PCI:*(0:0:1:0) 8086:7125:8086:4332 rev 3, Mem @ 0xf8000000/67108864, 0xffa80000/524288
[ 1084.737] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 1084.738] (II) LoadModule: "extmod"
[ 1084.765] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[ 1084.793] (II) Module extmod: vendor="X.Org Foundation"
[ 1084.793] compiled for 1.11.4, module version = 1.0.0
[ 1084.793] Module class: X.Org Server Extension
[ 1084.793] ABI class: X.Org Server Extension, version 6.0
[ 1084.793] (II) Loading extension MIT-SCREEN-SAVER
[ 1084.794] (II) Loading extension XFree86-VidModeExtension
[ 1084.794] (II) Loading extension XFree86-DGA
[ 1084.794] (II) Loading extension DPMS
[ 1084.794] (II) Loading extension XVideo
[ 1084.794] (II) Loading extension XVideo-MotionCompensation
[ 1084.794] (II) Loading extension X-Resource
[ 1084.794] (II) LoadModule: "dbe"
[ 1084.794] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[ 1084.808] (II) Module dbe: vendor="X.Org Foundation"
[ 1084.808] compiled for 1.11.4, module version = 1.0.0
[ 1084.809] Module class: X.Org Server Extension
[ 1084.809] ABI class: X.Org Server Extension, version 6.0
[ 1084.809] (II) Loading extension DOUBLE-BUFFER
[ 1084.809] (II) LoadModule: "glx"
[ 1084.809] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 1084.874] (II) Module glx: vendor="X.Org Foundation"
[ 1084.874] compiled for 1.11.4, module version = 1.0.0
[ 1084.874] ABI class: X.Org Server Extension, version 6.0
[ 1084.874] (==) AIGLX enabled
[ 1084.874] (II) Loading extension GLX
[ 1084.874] (II) LoadModule: "record"
[ 1084.875] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
[ 1084.889] (II) Module record: vendor="X.Org Foundation"
[ 1084.889] compiled for 1.11.4, module version = 1.13.0
[ 1084.889] Module class: X.Org Server Extension
[ 1084.889] ABI class: X.Org Server Extension, version 6.0
[ 1084.889] (II) Loading extension RECORD
[ 1084.890] (II) LoadModule: "dri"
[ 1084.890] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[ 1084.909] (II) Module dri: vendor="X.Org Foundation"
[ 1084.909] compiled for 1.11.4, module version = 1.0.0
[ 1084.909] ABI class: X.Org Server Extension, version 6.0
[ 1084.909] (II) Loading extension XFree86-DRI
[ 1084.909] (II) LoadModule: "dri2"
[ 1084.910] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[ 1084.911] (II) Module dri2: vendor="X.Org Foundation"
[ 1084.911] compiled for 1.11.4, module version = 1.2.0
[ 1084.911] ABI class: X.Org Server Extension, version 6.0
[ 1084.911] (II) Loading extension DRI2
[ 1084.911] (==) Matched intel as autoconfigured driver 0
[ 1084.911] (==) Matched vesa as autoconfigured driver 1
[ 1084.912] (==) Matched fbdev as autoconfigured driver 2
[ 1084.912] (==) Assigned the driver to the xf86ConfigLayout
[ 1084.912] (II) LoadModule: "intel"
[ 1084.931] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 1085.012] (II) Module intel: vendor="X.Org Foundation"
[ 1085.012] compiled for 1.11.2, module version = 2.17.0
[ 1085.012] Module class: X.Org Video Driver
[ 1085.012] ABI class: X.Org Video Driver, version 11.0
[ 1085.012] (II) LoadModule: "vesa"
[ 1085.013] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 1085.025] (II) Module vesa: vendor="X.Org Foundation"
[ 1085.025] compiled for 1.11.1, module version = 2.3.0
[ 1085.025] Module class: X.Org Video Driver
[ 1085.025] ABI class: X.Org Video Driver, version 11.0
[ 1085.025] (II) LoadModule: "fbdev"
[ 1085.034] (WW) Warning, couldn't open module fbdev
[ 1085.034] (II) UnloadModule: "fbdev"
[ 1085.034] (II) Unloading fbdev
[ 1085.034] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 1085.034] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server
[ 1085.035] (II) VESA: driver for VESA chipsets: vesa
[ 1085.036] (--) using VT number 7
[ 1085.217] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[ 1085.218] (WW) Falling back to old probe method for vesa
[ 1085.240] (II) Loading sub module "vgahw"
[ 1085.240] (II) LoadModule: "vgahw"
[ 1085.241] (II) Loading /usr/lib/xorg/modules/libvgahw.so
[ 1085.242] (II) Module vgahw: vendor="X.Org Foundation"
[ 1085.242] compiled for 1.11.4, module version = 0.1.0
[ 1085.242] ABI class: X.Org Video Driver, version 11.0
[ 1085.243] (II) intel(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 16/16
[ 1085.243] (==) intel(0): Depth 16, (==) framebuffer bpp 16
[ 1085.243] (==) intel(0): RGB weight 565
[ 1085.243] (==) intel(0): Default visual is TrueColor
[ 1085.243] (II) Loading sub module "xaa"
[ 1085.243] (II) LoadModule: "xaa"
[ 1085.244] (II) Loading /usr/lib/xorg/modules/libxaa.so
[ 1085.281] (II) Module xaa: vendor="X.Org Foundation"
[ 1085.281] compiled for 1.11.4, module version = 1.2.1
[ 1085.281] ABI class: X.Org Video Driver, version 11.0
[ 1085.281] (II) Loading sub module "vbe"
[ 1085.281] (II) LoadModule: "vbe"
[ 1085.281] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 1085.295] (II) Module vbe: vendor="X.Org Foundation"
[ 1085.295] compiled for 1.11.4, module version = 1.1.0
[ 1085.295] ABI class: X.Org Video Driver, version 11.0
[ 1085.295] (II) Loading sub module "int10"
[ 1085.295] (II) LoadModule: "int10"
[ 1085.296] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 1085.309] (II) Module int10: vendor="X.Org Foundation"
[ 1085.310] compiled for 1.11.4, module version = 1.0.0
[ 1085.310] ABI class: X.Org Video Driver, version 11.0
[ 1085.310] (II) intel(0): initializing int10
[ 1085.312] (II) intel(0): Primary V_BIOS segment is: 0xc000
[ 1085.314] (II) intel(0): VESA BIOS detected
[ 1085.314] (II) intel(0): VESA VBE Version 2.0
[ 1085.314] (II) intel(0): VESA VBE Total Mem: 1024 kB
[ 1085.314] (II) intel(0): VESA VBE OEM: Intel810(TM) Graphics Chip Accelerated VGA BIOS
[ 1085.314] (II) intel(0): VESA VBE OEM Software Rev: 3.0
[ 1085.314] (II) intel(0): VESA VBE OEM Vendor: Intel Corporation
[ 1085.314] (II) intel(0): VESA VBE OEM Product: i810 Graphics Controller
[ 1085.314] (II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0
[ 1085.314] (II) Loading sub module "ddc"
[ 1085.314] (II) LoadModule: "ddc"
[ 1085.314] (II) Module "ddc" already built-in
[ 1085.340] (II) intel(0): VESA VBE DDC supported
[ 1085.340] (II) intel(0): VESA VBE DDC Level 2
[ 1085.340] (II) intel(0): VESA VBE DDC transfer in appr. 1 sec.
[ 1085.951] (II) intel(0): VESA VBE DDC read successfully
[ 1085.952] (II) intel(0): Manufacturer: DEL Model: a000 Serial#: 842089268
[ 1085.952] (II) intel(0): Year: 2000 Week: 30
[ 1085.952] (II) intel(0): EDID Version: 1.2
[ 1085.952] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
[ 1085.952] (II) intel(0): Sync: Separate
[ 1085.952] (II) intel(0): Max Image Size [cm]: horiz.: 27 vert.: 20
[ 1085.952] (II) intel(0): Gamma: 2.87
[ 1085.952] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[ 1085.952] (II) intel(0): First detailed timing is preferred mode
[ 1085.952] (II) intel(0): redX: 0.619 redY: 0.350 greenX: 0.305 greenY: 0.600
[ 1085.952] (II) intel(0): blueX: 0.154 blueY: 0.064 whiteX: 0.280 whiteY: 0.311
[ 1085.952] (II) intel(0): Supported established timings:
[ 1085.952] (II) intel(0): 720x400@70Hz
[ 1085.952] (II) intel(0): 640x480@60Hz
[ 1085.952] (II) intel(0): 640x480@75Hz
[ 1085.952] (II) intel(0): 800x600@60Hz
[ 1085.952] (II) intel(0): 800x600@75Hz
[ 1085.952] (II) intel(0): 1024x768@60Hz
[ 1085.952] (II) intel(0): Manufacturer's mask: 0
[ 1085.952] (II) intel(0): Supported standard timings:
[ 1085.953] (II) intel(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
[ 1085.953] (II) intel(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
[ 1085.953] (II) intel(0): Supported detailed timing:
[ 1085.953] (II) intel(0): clock: 49.5 MHz Image Size: 270 x 202 mm
[ 1085.953] (II) intel(0): h_active: 800 h_sync: 816 h_sync_end 896 h_blank_end 1056 h_border: 0
[ 1085.953] (II) intel(0): v_active: 600 v_sync: 601 v_sync_end 604 v_blanking: 625 v_border: 0
[ 1085.953] (II) intel(0): Serial No: 82CGN07J21C4
[ 1085.953] (II) intel(0): Monitor name: DELL E551
[ 1085.953] (II) intel(0): Ranges: V min: 50 V max: 120 Hz, H min: 30 H max: 54 kHz, PixClock max 75 MHz
[ 1085.953] (II) intel(0): EDID (in hex):
[ 1085.953] (II) intel(0): 00ffffffffffff0010ac00a034433132
[ 1085.953] (II) intel(0): 1e0a0102081b14bbeaa2ae9e594e9927
[ 1085.953] (II) intel(0): 10474fa5480031594559010101010101
[ 1085.953] (II) intel(0): 01010101010156132000315819201050
[ 1085.953] (II) intel(0): 13000eca1000001e000000ff00383243
[ 1085.953] (II) intel(0): 474e30374a323143340a000000fc0044
[ 1085.953] (II) intel(0): 454c4c20453535310a202020000000fd
[ 1085.953] (II) intel(0): 0032781e3607000a20202020202000c0
[ 1085.953] (II) intel(0): EDID vendor "DEL", prod id 40960
[ 1085.954] (II) intel(0): Using EDID range info for horizontal sync
[ 1085.954] (II) intel(0): Using EDID range info for vertical refresh
[ 1085.954] (II) intel(0): Printing DDC gathered Modelines:
[ 1085.954] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 1085.954] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 1085.954] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 1085.954] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 1085.954] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 1085.954] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 1085.954] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
[ 1085.954] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
[ 1085.955] (II) intel(0): Integrated Graphics Chipset: Intel(R) i810e
[ 1085.955] (--) intel(0): Chipset: "i810e"
[ 1085.955] (--) intel(0): Linear framebuffer at 0xF8000000
[ 1085.955] (--) intel(0): IO registers at addr 0xFFA80000
[ 1085.955] (II) intel(0): Kernel reported 109056 total, 0 used
[ 1085.955] (II) intel(0): I810CheckAvailableMemory: 436224k available
[ 1085.955] (==) intel(0): Will alloc AGP framebuffer: 24576 kByte
[ 1085.955] (==) intel(0): Using gamma correction (1.0, 1.0, 1.0)
[ 1085.955] (II) intel(0): <default monitor>: Using hsync range of 30.00-54.00 kHz
[ 1085.955] (II) intel(0): <default monitor>: Using vrefresh range of 50.00-120.00 Hz
[ 1085.955] (II) intel(0): <default monitor>: Using maximum pixel clock of 75.00 MHz
[ 1085.955] (II) intel(0): Estimated virtual size for aspect ratio 1.3500 is 1024x768
[ 1085.955] (II) intel(0): Clock range: 9.50 to 163.00 MHz
[ 1085.956] (II) intel(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768i" (unknown reason)
[ 1085.956] (II) intel(0): Not using default mode "512x384i" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768" (hsync out of range)
[ 1085.956] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768" (hsync out of range)
[ 1085.956] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.956] (II) intel(0): Not using default mode "1024x768" (hsync out of range)
[ 1085.957] (II) intel(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1152x864" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x960" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x960" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1280x1024" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.957] (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size)
[ 1085.957] (II) intel(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1792x1344" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1792x1344" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1856x1392" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1856x1392" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1920x1440" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1920x1440" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "416x312" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "1920x1440" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "2048x1536" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "2048x1536" (width too large for virtual size)
[ 1085.958] (II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 1085.958] (II) intel(0): Not using default mode "2048x1536" (width too large for virtual size)
[ 1085.959] (II) intel(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
[ 1085.959] (--) intel(0): Virtual size is 1024x768 (pitch 1024)
[ 1085.959] (**) intel(0): *Driver mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[ 1085.959] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 1085.959] (**) intel(0): *Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
[ 1085.959] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
[ 1085.959] (**) intel(0): *Default mode "832x624": 57.3 MHz, 49.7 kHz, 74.6 Hz
[ 1085.959] (II) intel(0): Modeline "832x624"x74.6 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz)
[ 1085.959] (**) intel(0): *Driver mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 1085.959] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 1085.959] (**) intel(0): *Driver mode "800x600": 56.2 MHz, 53.7 kHz, 85.1 Hz
[ 1085.959] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
[ 1085.959] (**) intel(0): *Driver mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 1085.959] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x85.1 56.30 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 50.0 MHz, 48.1 kHz, 72.2 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz)
[ 1085.960] (**) intel(0): *Default mode "800x600": 36.0 MHz, 35.2 kHz, 56.2 Hz
[ 1085.960] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz)
[ 1085.960] (**) intel(0): *Driver mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
[ 1085.960] (**) intel(0): *Driver mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 1085.960] (**) intel(0): *Driver mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 1085.960] (**) intel(0): *Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
[ 1085.960] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x480": 31.5 MHz, 37.5 kHz, 75.0 Hz
[ 1085.961] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x480": 31.5 MHz, 37.9 kHz, 72.8 Hz
[ 1085.961] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x480": 25.2 MHz, 31.5 kHz, 59.9 Hz
[ 1085.961] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz)
[ 1085.961] (**) intel(0): *Driver mode "720x400": 28.3 MHz, 31.5 kHz, 70.1 Hz
[ 1085.961] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz)
[ 1085.961] (**) intel(0): *Default mode "720x400": 35.5 MHz, 37.9 kHz, 85.0 Hz
[ 1085.961] (II) intel(0): Modeline "720x400"x85.0 35.50 720 756 828 936 400 401 404 446 -hsync +vsync (37.9 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x400": 31.5 MHz, 37.9 kHz, 85.1 Hz
[ 1085.961] (II) intel(0): Modeline "640x400"x85.1 31.50 640 672 736 832 400 401 404 445 -hsync +vsync (37.9 kHz)
[ 1085.961] (**) intel(0): *Default mode "640x350": 31.5 MHz, 37.9 kHz, 85.1 Hz
[ 1085.961] (II) intel(0): Modeline "640x350"x85.1 31.50 640 672 736 832 350 382 385 445 +hsync -vsync (37.9 kHz)
[ 1085.961] (**) intel(0): Display dimensions: (270, 200) mm
[ 1085.961] (**) intel(0): DPI set to (96, 97)
[ 1085.961] (II) Loading sub module "fb"
[ 1085.961] (II) LoadModule: "fb"
[ 1085.962] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 1085.972] (II) Module fb: vendor="X.Org Foundation"
[ 1085.972] compiled for 1.11.4, module version = 1.0.0
[ 1085.972] ABI class: X.Org ANSI C Emulation, version 0.4
[ 1085.972] (II) Loading sub module "ramdac"
[ 1085.972] (II) LoadModule: "ramdac"
[ 1085.972] (II) Module "ramdac" already built-in
[ 1085.972] (**) intel(0): page flipping disabled
[ 1085.972] (II) intel(0): XvMC is Disabled: use XvMCSurfaces config option to enable.
[ 1085.972] (II) UnloadModule: "vesa"
[ 1085.972] (II) Unloading vesa
[ 1085.988] drmOpenDevice: node name is /dev/dri/card0
[ 1085.993] drmOpenDevice: node name is /dev/dri/card0
[ 1086.005] [drm] failed to load kernel module "i810"
[ 1086.006] (EE) [drm] drmOpen failed.
[ 1086.006] (EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
[ 1086.024] (II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
[ 1086.088] (II) intel(0): Setting dot clock to 65.0 MHz [ 0x3f 0xa 0x30 ] [ 65 12 3 ]
[ 1086.089] (II) intel(0): chose watermark 0x2210e000: (tab.freq 65.0)
[ 1086.286] (II) intel(0): xf86BindGARTMemory: bind key 0 at 0x00000000 (pgoffset 0)
[ 1086.289] (II) intel(0): xf86BindGARTMemory: bind key 1 at 0x01800000 (pgoffset 6144)
[ 1086.289] (WW) intel(0): xf86BindGARTMemory: binding of gart memory with key 1
at offset 0x1800000 failed (Invalid argument)
[ 1086.289] (II) intel(0): Allocation of 4194304 bytes for DCACHE failed
[ 1086.289] (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x01800000 (pgoffset 6144)
[ 1086.290] (II) intel(0): Allocated of 4096 bytes for HW cursor
[ 1086.290] (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x01801000 (pgoffset 6145)
[ 1086.290] (II) intel(0): Allocated of 16384 bytes for ARGB HW cursor
[ 1086.290] (II) intel(0): Adding 768 scanlines for pixmap caching
[ 1086.290] (II) intel(0): Allocated Scratch Memory
[ 1086.291] (II) intel(0): Using XFree86 Acceleration Architecture (XAA)
[ 1086.291] Screen to screen bit blits
[ 1086.291] Solid filled rectangles
[ 1086.291] 8x8 mono pattern filled rectangles
[ 1086.291] Indirect CPU to Screen color expansion
[ 1086.291] Solid Horizontal and Vertical Lines
[ 1086.291] Setting up tile and stipple cache:
[ 1086.291] 24 128x128 slots
[ 1086.291] 6 256x256 slots
[ 1086.291] (==) intel(0): Backing store disabled
[ 1086.291] (==) intel(0): Silken mouse enabled
[ 1086.292] (==) intel(0): DPMS enabled
[ 1086.293] (WW) intel(0): Direct rendering disabled
[ 1086.293] (==) RandR enabled
[ 1086.293] (II) Initializing built-in extension Generic Event Extension
[ 1086.293] (II) Initializing built-in extension SHAPE
[ 1086.293] (II) Initializing built-in extension MIT-SHM
[ 1086.293] (II) Initializing built-in extension XInputExtension
[ 1086.293] (II) Initializing built-in extension XTEST
[ 1086.293] (II) Initializing built-in extension BIG-REQUESTS
[ 1086.293] (II) Initializing built-in extension SYNC
[ 1086.293] (II) Initializing built-in extension XKEYBOARD
[ 1086.293] (II) Initializing built-in extension XC-MISC
[ 1086.293] (II) Initializing built-in extension SECURITY
[ 1086.293] (II) Initializing built-in extension XINERAMA
[ 1086.293] (II) Initializing built-in extension XFIXES
[ 1086.293] (II) Initializing built-in extension RENDER
[ 1086.293] (II) Initializing built-in extension RANDR
[ 1086.293] (II) Initializing built-in extension COMPOSITE
[ 1086.294] (II) Initializing built-in extension DAMAGE
[ 1086.341] (II) AIGLX: Screen 0 is not DRI2 capable
[ 1086.341] (II) AIGLX: Screen 0 is not DRI capable
[ 1086.952] (II) AIGLX: Loaded and initialized swrast
[ 1086.952] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 1087.487] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 1087.487] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 1087.487] (II) LoadModule: "evdev"
[ 1087.488] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.503] (II) Module evdev: vendor="X.Org Foundation"
[ 1087.503] compiled for 1.10.99.902, module version = 2.6.0
[ 1087.503] Module class: X.Org XInput Driver
[ 1087.503] ABI class: X.Org XInput driver, version 13.0
[ 1087.503] (II) Using input driver 'evdev' for 'Power Button'
[ 1087.503] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.503] (**) Power Button: always reports core events
[ 1087.503] (**) Power Button: Device: "/dev/input/event1"
[ 1087.504] (--) Power Button: Found keys
[ 1087.504] (II) Power Button: Configuring as keyboard
[ 1087.504] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 1087.504] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 1087.504] (**) Option "xkb_rules" "evdev"
[ 1087.504] (**) Option "xkb_model" "evdev"
[ 1087.504] (**) Option "xkb_layout" "us"
[ 1087.646] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 1087.647] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 1087.647] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 1087.647] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.647] (**) AT Translated Set 2 keyboard: always reports core events
[ 1087.647] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 1087.647] (--) AT Translated Set 2 keyboard: Found keys
[ 1087.647] (II) AT Translated Set 2 keyboard: Configuring as keyboard
[ 1087.647] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 1087.647] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 7)
[ 1087.647] (**) Option "xkb_rules" "evdev"
[ 1087.647] (**) Option "xkb_model" "evdev"
[ 1087.647] (**) Option "xkb_layout" "us"
[ 1087.650] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/event3)
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: Applying InputClass "evdev pointer catchall"
[ 1087.650] (II) Using input driver 'evdev' for 'ImPS/2 Logitech Wheel Mouse'
[ 1087.650] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: always reports core events
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: Device: "/dev/input/event3"
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found 3 mouse buttons
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found scroll wheel(s)
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found relative axes
[ 1087.650] (--) ImPS/2 Logitech Wheel Mouse: Found x and y relative axes
[ 1087.650] (II) ImPS/2 Logitech Wheel Mouse: Configuring as mouse
[ 1087.650] (II) ImPS/2 Logitech Wheel Mouse: Adding scrollwheel support
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: YAxisMapping: buttons 4 and 5
[ 1087.650] (**) ImPS/2 Logitech Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 1087.651] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input3/event3"
[ 1087.651] (II) XINPUT: Adding extended input device "ImPS/2 Logitech Wheel Mouse" (type: MOUSE, id 8)
[ 1087.651] (II) ImPS/2 Logitech Wheel Mouse: initialized for relative axes.
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) keeping acceleration scheme 1
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration profile 0
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration factor: 2.000
[ 1087.651] (**) ImPS/2 Logitech Wheel Mouse: (accel) acceleration threshold: 4
[ 1087.652] (II) config/udev: Adding input device ImPS/2 Logitech Wheel Mouse (/dev/input/mouse0)
[ 1087.653] (II) No input driver specified, ignoring this device.
[ 1087.653] (II) This device may have been added with another device file.
[ 1087.654] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 1087.654] (II) No input driver specified, ignoring this device.
[ 1087.654] (II) This device may have been added with another device file.
[ 1094.003] (II) Power Button: Close
[ 1094.003] (II) UnloadModule: "evdev"
[ 1094.003] (II) Unloading evdev
[ 1094.016] (II) AT Translated Set 2 keyboard: Close
[ 1094.016] (II) UnloadModule: "evdev"
[ 1094.016] (II) Unloading evdev
[ 1094.029] (II) ImPS/2 Logitech Wheel Mouse: Close
[ 1094.030] (II) UnloadModule: "evdev"
[ 1094.030] (II) Unloading evdev
[ 1094.102] (II) intel(0): xf86UnbindGARTMemory: unbind key 0
[ 1094.102] (II) intel(0): xf86UnbindGARTMemory: unbind key 2
[ 1094.102] (II) intel(0): xf86UnbindGARTMemory: unbind key 3
[ 1094.208] Server terminated successfully (0). Closing log file.
For some reason I suddenly can't keep my computer logged on to the forums long enough to make a post (cookie issue?), so this is sent from a computer at the library. I failed to notice your asking for the dmesg output...so I'll go home tonight and get that, too.
Thanks for your help so far! I'm still trying things, but not getting anywhere yet.

Similar Messages

Premiere Pro CC could not find capable Video Module

Hello, I have looked all over for the answers to this problem and nothing I have found all over the forums is working. Here is what my system is:
CPU: Intel i7 960
24GB RAM
GPU: Quadro 4000
I have the latest drivers for the Quadro which I updated after I suddenly got this error I think after I did the latest CC Update.
The error is: Adobe Premiere Pro could not find any capable video play modules. Please update your video display drivers and start again.
I have only seen people that have AMD/ATI cards get this error or people that have the switching technology in laptops.
I have done the following:
Updated Video Card Drivers
Run As Administrator
Checked to Make Sure My Card Was In The Supported Cards List (I already knew it was because everything worked before.)
I don't know what my next options are. I have a lot of work to get done too so I need to get this working. Any help will be much appreciated. Thanks!

Hello, I had the same problem. Even after a new installation.
Solution: Media Player update as well as VLC Media Player from the original website installed. (Http://www.videolan.org/) then reboot. Now everything works. The problem was probably missing video codecs

CC 2014 on 2011 iMac - Video Module Problem

I just installed the 2014 CC version of Premiere Pro on my iMac and am now getting this message. Error "Premiere Pro could not find any capable video play modules"
The self-service support on the Adobe site is inadequate, fails to offer any valuable support.
Does anyone have the same issue with this version and, if so, any clues on fixing it, without buying a new Mac? And yes, I have 2Gb on the GPU, 32Gb RAM.

Hi NCMUK,
Try this:
Go to the following locations and rename the folders to "old_folder name" (like old_Adobe)
User/user library/Application Support and rename the Adobe folder.
User/user library/Preferences and rename the Adobe folder.
Then go to Documents folder and then to Adobe/Premiere pro/8.0 and rename the 8.0 folder.
Thanks,
Kevin

Third Party Video Modules

I have an MCU with EMP, and all works fine. I would like to have a "higher end" camera for conference rooms etc. Ideally, it would also be able to work with a projector on a laptop, incorporating IP Communicator. Any ideas? Thanks

I just got a resolution from TAC on this issue.
These settings fixed the issue for 8945 and Jabber clients.
Preferred video codecs:
Choice 1 : H.264
Video codec settings:
Video resolution: CIF (352x288)
Frame rate: 30fps
Video Bitrate: 384
Video packet size: 1400 Bytes
Advanced RTP settings
H.264 payload type (1): 103
H.264 payload type (1): 124
H.263+ payload type (1): 97
Polycomm Compatible; Yes

Crashing in video module in cc2014

Hello,
I'm finding that when editing video clips in the 2014 version of PS CC it crashes consistently so that I'm unable to edit multiple clips.
Thanks,
JoAnn Woods

What OS version are you using?
What does the detailed crash report say?

Hp hdx 16t laptop, hooked it philips 52 tv via hdmi cable and get video but no audio

Hp HDX 16t laptop Windows vista home prem, 64 bit, 4 gig ram, (512) 9600m gt nvidia geforce video card.
Hi I have a hp hdx 16t laptop, hooked it up to philips 52 inch LED tv via an hdmi cable and get video on tv but no audio. Only sound from laptop, My tv is set to computer hdmi 1 and all drivers up tp date. I have goolged numerous solutions and none have worked. If anybody has the time, a solution would be just great.. jd.

If you have the the video drivers installed for your notebook's chipset and the discrete video module then you should see something similar to the folowing image. This is on my loaner HP Pavilion dv7-4180ea. When I connect the notebook to my Philips HDTV the operating system switches to HDMI audio after I direct the video to the TV with the function keys on the notebook.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Front Row Video problem

For some reason whenever i go to Front Row and go to the video section, it goes directly back to the desktop. I have restarted my computer twice and the same thing happened. Does anybody know a fix?
P.S.
I have tiger so its not the most recent version of front row
Message was edited by: guitarfreak2013

If you use the Accounts System Preferences to create a new user, log out and log in as the new user, can they open the "Videos" module? If so, then Front Row is functioning normally but you may have a file in your original user's Movies folder that's causing the trouble. If the new user can't open the videos module, then there's some kind of system-wide Front Row or QuickTime problem.
-Doug

Default kernel config question: acpi video freezes my laptop

Hi,
I have a Samsung X60 laptop that freezes when the acpi video module is loaded. The default Arch kernel config (and the derived suspend2 one) includes as built-in some of the acpi code (including the video bit). I'm interested to learn why they are included as built in, and if there is a way to selectively skip the acpi video built-in bit of code? (more selectively than acpi=off as a kernel parameter). Would it be reasonable to request a change to the default kernel config?
cheers

bugs.archlinux.org to make sure its fixed.
the acpi video module is reasonably new and it can be compiled as a module iirc, so it shouldnt be any harm to have it compiled as such.
James

PProHeadless.exe, FileImporter.cpp-1132 errors exporting short video

Hi,
I'm getting an error when I try and export my 3 minute movie. The error goes as follows:
PProHeadless.exe
AppVer: 0.0.0.0
ModName: dvacore.dll
Mod Ver: 2.0.0.0
Offset: 002de00
Encoding Failed
Error compiling movie
Unknown Error
I tried removing the two clips from the timeline at which it always seemed to crash, and it did export but only as an mp4. I tried re-converting those clips thinking they were corrupted, and still get the error with the new clips. In this same area there are crossfading .jpgs, but they have been sized to 72dpi and are concurrent with the video size, so this shouldn't be the issue, correct?
It also has listed a FileImporter.cpp-1132 error.
I've never had this issue before. I'm running Premiere Pro CS4 on a windows xp machine. Should I be converting these videos to a specific format before using them in the timeline? Right now I'm importing them as mpeg2, after converting them in Media Encoder.
Thanks for your help!
-J

Everyone may have already got what they wanted from the answers given in the post but I thought I'd add my PAL experience of this.
I tried to media export a timeline to one large mixdown file. (blackmagic mjpeg) the timeline had simple premiere titles fading up and down to black before each video module. The media encoder worked fine but none of the dissolves from timeline to title worked - they translated as cuts in the mixdown. In the end I dropped premiere generated black video over the titles and used variable opacity to bring them in and out. This worked fine and proves that you can export with black at the front.
What it proves however is that CS4 really is working differently to CS3 in lots of ways.
As far as media encoder is concered, I'm sure this is a grandmother sucking eggs business but it's critical for performance that the USE PREVIEW FILES option in the settings box is selected. Otherwise CS4 starts to re-render everything and seems to be much slower at doing it than a basic timeline render. Including metadata files doesn't seem to offend too much but I only evr include this when I'm exporting final versions anyway.

Satellite 5200 - Video memory corruption

One month ago I encountered a problem with a slightly garbled screen
on the internal and external displays. More or less visible vertical
strips appear on the screen. They are mainly blue on dark background
(best visible) or yellow on white background (less visible) and have
approximately the same thickness of order 1-2 mm and length of order
1 cm. The locations of the strips depend on the positions of details
of the actual picture currently displayed on the screen.
The boot screen is also garbled but now by red vertical strips located on the left and on the right of the red logo "In Touch with Tomorrow Toshiba"
In the full screen text mode, odd characters appear in positions which correlate with positions of true characters.
The BurnIn Test V4.0 Pro indicated a video memory corruption (the adapter is NVIDIA GeForce4 460 Go, 64 MB, integrated RAMDAC). That is very interesting, yesterday
there was a short period of about 5 minutes when all the described above symptoms suddenly disappeared.
Even the BurnIn Test showed that everything is OK. But after this period, the symptoms recovered again. For this
reason I would like to ask how to solve the problem.
Is this indeed a bad video memory which can recover and then become bad again or other reasons, such as a bad connectivity, etc.?
Thanks.

hi, i had the same problem on a Satellite m70-159. With one diference- mine would start only in safe mode. But the same vertical strips, even in the ''in touch with tomorow'' screen. this was the good news. the bad news is that they had to replace both the motherboard and the video module.
sorry.. and it's not like anything had happened to my notebook..

Big color discrepancy when rendering video

I'm editing video on a Mac using PS CC. My Multisync PA242 monitor is calibrated. When I open the .MOV files for editing I select sRGB for color managing. I'm rendering out to a H.264 MP4 file and I've checked "color manage" in the export video dialogue. My rendered video is hugely undersaturated. My only "work around" is to OVER saturated before performing the export render. After much research, I can find no advice addressing this issue.

I am afraid this is not going to be a big help but you are not alone. I have just started shooting video after years of still photography. I have a full understanding of colour management and my still workflow is consistent from end to end. My impression of video is that most video editing applications do not colour manage at all. The professionals use expensive suites to edit in which separate calibrated monitors (to something called REC709 which is close to sRGB) are used to display the output but the User Interface display where all the work is done is not colour managed. This is probably all right if you do all your work on an sRGB monitor but if you have a calibrated wide gamut monitor like many stills photographers then you are in trouble. I was under the impression that the Video module in Photoshop CC (and CS6) is properly colour managed as we understand it and should assume sRGB for untagged video clips but I could be wrong.
The other big problem is that video "colourists" speak a different language from still photographers.

Compile radeonfb kernel module

what I want to do, is to compile just radeonfb as a module (so that I could use it), without rebuilding anything else because the entire kernel takes way too long (like an hour or so).
How about this possibility;
a pkgbuild that builds the module seperately off of cvs or whatever the kernel is hosted on, (so that the 40 MB tarball doesn't have to get downloaded?)
not sure exactly how that works out, but it's probably possible, or is it all just not worth the effort?

Do you have a /proc/config.gz that you could use? Otherwise I don't know. I mean, many modules should be compilable simply with the system-installed kernel headers, but not all native modules might follow that rule.
Unfortunatel most of what you find on the web talks about how to create new modules which can be compild against the installed kernel tree, not about how to compile one of the native kernel modules against it.
Actually, try what those links suggest.
Skip the configuration part, and just do:
make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video modules
(maybe `make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video clean` first )
EDIT: Meh, that uses your config and won't build that driver... there must be some way though
EDIT2: Try:
make -C /lib/modules/`uname -r`/build M=$(PWD)/drivers/video modules CONFIG_FB_VT8623=m CONFIG_FB_SVGALIB=m
The problem though is, that they might have removed some of the dependencies of the module, so if it doesn't compile, you'll have to recompile the kernel.
Good thing is though, you can use their .config as base (found in /usr/src/linux-..../.config)
You can also check if your config "supports" your module by putting it into the kernel source tree, running `make menuconfig` and typing /8623 and pressing enter.
The last line in that screen should read:
Selects: <list of options>
As long as all of those options are either =y or =m, you're good. SVGALIB can be =n because it's part of drivers/video/ and you can compile it together with your module.
Last edited by Blµb (2012-03-02 15:14:16)

Cannot load the "new" flash so I can play videos on Facebook via Firefox on OS 10.6.8. Have followed instuctions by after "save file" nothing happens, even after I trash the previous version of flash I have.

I am unable to play videos on Facebook unless I download a "new" flash, which I am unable to do -- following the instructions to trash the previous version included. I'm told to hit "save," but no downloading activity occurs at all. I'm using OS 10.6.8. Any clue what to do?

Hello, it seems that support is not aware of this blog post: http://blogs.adobe.com/crawlspace/2013/06/updatingupgrading-to-photoshop-cc-faq.html#video
Adobe decided to limit to Lion, each operating system they support means more quality assurance.
The APIs they used for video is not supported in Snow Leopard (I upgraded just for that)
Adding another one means more quality assurance, tests, detrimental to the new features.
If you are a creative cloud subscriber you can also install Photoshop CS6 that has a video module compatible with 10.6.8

Cant open Premier Pro-Asking for video driver update?

I have recently installed Adobe premier Pro and it comes up with the following message "Adobe Premier Pro could not find any capable play video modules.Please update your video display modules and start again"
I run Windows 7 and have a top of the range laptop which should easily be able to cope with the video output
Would really appreciate some help on this
Thank you
Andy

>top of the range laptop
Need exact brand and model... including the screen size in pixel X pixel dimensions
Also need exact brand and model of graphics adapter (ATI or nVidia or ???) and exact device driver number
To find the nVidia driver version
Right click in any open area of the Windows desktop
Select NVIDIA Control Panel from the popup window
Select SYSTEM INFORMATION at the lower left corner
Driver version should be the 1st line in Details
If your laptop has dual video (power saver and regular) read...
Dual video laptop problems
-http://helpx.adobe.com/premiere-pro/kb/error---preludevideo-play-modules.html
-http://forums.adobe.com/thread/1001579
-Use BIOS http://forums.adobe.com/thread/1019004?tstart=0
-link to why http://forums.adobe.com/message/4685328
-http://www.anandtech.com/show/4839/mobile-gpu-faceoff-amd-dynamic-switchable-graphics-vs-n vidia-optimus-technology/2
-HP Fingerprint/Password conflict http://forums.adobe.com/thread/911575
And, for the future, please remember that nobody here can look through the Internet to see what you have
More information needed for someone to help... please click these links and provide the requested information
-http://forums.adobe.com/message/4200840
-http://forums.adobe.com/thread/416679
-http://forums.adobe.com/thread/419406

Help me for Intel Video 3D Driver

Hi
I am a Chinese user,my video card is intel 82830M, I have installed the driver(pacman -S xf86-video-i810,i can't use xf86-video-intel)
glxinfo -- direct rendering: No
glxgears-- FPS only 300
and hard to play torcs
load "dri" is available in xorg.conf
how to open 3D support?

this is my old machine~
Kernel : 2.6.23-ARCH
CPU & Cache: Processor 0: Celeron (Coppermine) 863MHz, 128 KB Cache
Sound(m) : 82801CA/CAM AC'97 Audio Controller module: snd-intel-ich
Video : 82830 CGC [Chipset Graphics Controller] server: Xorg ( )
Driver : xf86-video- module: -
Monitor : Generic Monitor H: 28.0-96.0kHz V: 50.0-75.0Hz
Mouse : PS/2 Mouse xtype: PS2 device: /dev/psaux
HDD : 82801CAM IDE U100 Controller module: ata_piix
USB : 82801CA/CAM USB Controller #1 module: uhci_hcd
Ethernet : RTL-8139/8139C/8139C+ module: 8139too
Network : No wireless card
PCMCIA slot: OZ6933/711E1 CardBus/SmartCardBus Controller module: yenta_cardbus

No video module?

Similar Messages

Maybe you are looking for