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 suspe
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):
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 cac
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
> > T
> > 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 n
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 f
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]
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
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): I830CheckAvailableM
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 11
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 vers
11 matches
Mail list logo
