Bug#421418: No XV here too
Does this also happen if you don't use Option SWcursor or enable the DRI? Disabling SWcursor partially fixes the problem : XV is enabled but I get the blue screen upon xv input. Upgrading to xserver-xorg-video-intel 2.0.0.0-2 fixes the problem. Thanks! I had SWCursor enabled because of suspend to RAM problems (cursor did not show upon resuming) but this is not an issue anymore with the -intel driver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
Please post a full log file from starting the X server without the VideoRam directive. Here it is (attached). An extract that I find relevant : (II) intel(0): I830CheckAvailableMemory: 440316 kB available (==) intel(0): VideoRam: 131072 KB (II) intel(0): Allocating 5472 scanlines for pixmap cache (II) intel(0): Memory allocation layout: (II) intel(0): 0x-0x0001: ring buffer (128 kB) (II) intel(0): 0x0002-0x00027fff: logical 3D context (32 kB) (II) intel(0): 0x0003-0x02127fff: front buffer (33760 kB) (II) intel(0): 0x007df000:end of stolen memory (II) intel(0): 0x02128000-0x02137fff: xaa scratch (64 kB) (II) intel(0): 0x0800:end of aperture (II) intel(0): front buffer is not tiled (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. Xorg.0.log.gz Description: GNU Zip compressed data
Bug#421418: No XV here too
On Fri, 2007-05-25 at 10:32 +0200, Alexandre Rossi wrote: Please post a full log file from starting the X server without the VideoRam directive. Here it is (attached). An extract that I find relevant : (II) intel(0): I830CheckAvailableMemory: 440316 kB available (==) intel(0): VideoRam: 131072 KB (II) intel(0): Allocating 5472 scanlines for pixmap cache (II) intel(0): Memory allocation layout: (II) intel(0): 0x-0x0001: ring buffer (128 kB) (II) intel(0): 0x0002-0x00027fff: logical 3D context (32 kB) (II) intel(0): 0x0003-0x02127fff: front buffer (33760 kB) (II) intel(0): 0x007df000:end of stolen memory (II) intel(0): 0x02128000-0x02137fff: xaa scratch (64 kB) (II) intel(0): 0x0800:end of aperture (II) intel(0): front buffer is not tiled (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. Does this also happen if you don't use Option SWcursor or enable the DRI? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#421418: No XV here too
On Wed, 2007-05-23 at 20:57 +0200, Alexandre Rossi wrote: Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? Nothing like that in the BIOS menus. Note that some BIOSes obfuscate it as DVMT (Dynamic Video Memory Technology) or some other fancy marketing term. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#421418: No XV here too
On Thu, 2007-05-24 at 10:07 +0200, Alexandre Rossi wrote: Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? Nothing like that in the BIOS menus. Note that some BIOSes obfuscate it as DVMT (Dynamic Video Memory Technology) or some other fancy marketing term. The BIOS of my VAIO VGN-B1VP does not have more than Date, Password, IDE devices and Boot device settings. Anyway this used to work perfectly with xserver-xorg-video-i810, so this seems to be a problem with the new driver. Please post a full log file from starting the X server without the VideoRam directive. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#421418: No XV here too
Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? Nothing like that in the BIOS menus. Note that some BIOSes obfuscate it as DVMT (Dynamic Video Memory Technology) or some other fancy marketing term. The BIOS of my VAIO VGN-B1VP does not have more than Date, Password, IDE devices and Boot device settings. Anyway this used to work perfectly with xserver-xorg-video-i810, so this seems to be a problem with the new driver. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? Nothing like that in the BIOS menus. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
On Sun, 2007-05-20 at 20:49 +0200, Alexandre Rossi wrote: (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. If I explicitely use VideoRam 32768 in xorg.conf, xorg does not start and fails with the following message : (II) intel(0): Kernel reported 110080 total, 1 used (II) intel(0): I830CheckAvailableMemory: 440316 kB available (**) intel(0): VideoRam: 32768 KB (II) intel(0): Allocating 5273 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? As indicated here, try commenting out the VideoRam directive in xorg.conf. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#421418: No XV here too
Hi, (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. If I explicitely use VideoRam 32768 in xorg.conf, xorg does not start and fails with the following message : (II) intel(0): Kernel reported 110080 total, 1 used (II) intel(0): I830CheckAvailableMemory: 440316 kB available (**) intel(0): VideoRam: 32768 KB (II) intel(0): Allocating 5273 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? As indicated here, try commenting out the VideoRam directive in xorg.conf. If I do, X.org starts but no XV, which is deactivated due to failing overlay register allocation . Alexandre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#421418: No XV here too
On Mon, 2007-05-21 at 09:18 +0200, Alexandre Rossi wrote: (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. If I explicitely use VideoRam 32768 in xorg.conf, xorg does not start and fails with the following message : (II) intel(0): Kernel reported 110080 total, 1 used (II) intel(0): I830CheckAvailableMemory: 440316 kB available (**) intel(0): VideoRam: 32768 KB (II) intel(0): Allocating 5273 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? As indicated here, try commenting out the VideoRam directive in xorg.conf. If I do, X.org starts but no XV, which is deactivated due to failing overlay register allocation . Does the BIOS setup allow changing the graphics aperture size? If yes, can you try increasing it? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#421418: No XV here too
Hi, Same behavior here. As this has not been said, I add my comments. It is in fact XV that does not work. I have no external screen connected. $ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) $ xvinfo X-Video Extension version 2.2 screen #0 no adaptors present $ grep -i xv /var/log/Xorg.0.log (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (WW) intel(0): Disabling Xv because the overlay register buffer allocation failed. If I explicitely use VideoRam 32768 in xorg.conf, xorg does not start and fails with the following message : (II) intel(0): Kernel reported 110080 total, 1 used (II) intel(0): I830CheckAvailableMemory: 440316 kB available (**) intel(0): VideoRam: 32768 KB (II) intel(0): Allocating 5273 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 Everything works well with the older i810 driver, Hoping to help, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
