[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xf86-video-intel |
Fix Released
|
Critical
|
|||
xserver-xorg-video-intel (Fedora) |
Fix Released
|
High
|
|||
xserver-xorg-video-intel (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Jaunty |
Fix Released
|
High
|
Bryce Harrington |
Bug Description
Since the change from the 2.4.1 driver to 2.5.1, Jaunty now hangs during boot, with "Fatal server error: Couldn't bind memory for BO front buffer" shown in the log.
This bug is ONLY for the issue on i845 graphics. While the same symptom can be seen with 855 and 865, the workaround and solution is different.
Also discussed at this forum: https:/
[Original Report]
Binary package hint: xserver-
Hi all,
This is in jaunty, I get no screens.
[lspci]
00:00.0 Host bridge [0600]: Intel Corporation 82845G/
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/
Subsystem: Intel Corporation 82845G/
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #164 |
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #165 |
Created attachment 316357
Xorg.0.log with 2.4.2-7 and EXA
I am also attaching the Xorg.0.log from xorg-x11-
In Red Hat Bugzilla #461829, Matěj (matj-redhat-bugs) wrote : | #166 |
Isn't this the same bug as bug 461171, or are we talking about different machine here?
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #167 |
I could be mistaken, but I believe it to be a different issue. In this case, I cannot ever get X to start, and there are errors that appear in the Xorg.0.log and in dmesg. With 2.4.2-1, X usually worked, but I haven't been able to get it to start with 2.4.2-2 and later. In contrast, bug 461171 is an occasional problem (20% of the time) that I noticed with 2.4.2-1, and it doesn't put any errors in the log.
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #168 |
I was just curious if there's any other information I should provide. By the way, I've tried as recent rpms as xorg-x11-
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #169 |
I noticed that there's an upstream commit which looks like it might be a fix:
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #170 |
I am suffering from the very same problem. The upstream git commit seems to be already present in the latest xorg (xorg-x11-
X startup fails all the time. 100% reliable.
(intel 82865G controller)
Just went from F8 (X OK) to todays Rawhide, fully uptodate.
Surviving with fbdev for now...
Greetings, Konrad
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #171 |
Created attachment 319473
Xorg startop log
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #172 |
comment #7 with todays rawhide xorg-x11-
fbdev :-(
system-
what can I do to track this down?
Konrad
In Red Hat Bugzilla #461829, Joachim (joachim-redhat-bugs) wrote : | #173 |
X still does not start with the message "Fatal server error: Couldn't bind memory for BO front buffer" for a current Koji development system, featuring:
kernel-
libdrm-
xorg-
xorg-
for an integrated graphics chipset Intel Corporation 82845G/
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #174 |
I have a hobbled-together system using xorg-x11-
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #175 |
ditto here: today's xorg-x11-
NoAccel (BO front buffer) on intel 82865G.
I have another wierdness on this machine when logging in to the console
(run level 3): my user id is not being echoed the first time. after a
logout and again login it is echoed properly.
In Red Hat Bugzilla #461829, Dave (dave-redhat-bugs) wrote : | #176 |
can one of the 865G people try adding
Option "Legacy3D" "false"
to the xorg.conf device section?
In Red Hat Bugzilla #461829, Michael (michael-redhat-bugs) wrote : | #177 |
Created attachment 320413
X org log file
With
Option "Legacy3D" "false"
it gets further, displaying the splash login screen, sometoimes with corrupted text, and quickly freezes up. I am attaching the Xorg.0.log file just in case it is useful, but I don't think it is.
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #178 |
Created attachment 320483
Xorg.0.log
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #179 |
argh, forgot to type this comment into the attachments comment field...
Gets past the BO pin message but does not become useable.
The kde konsole background looked like a chess board (white/light grey)
My Xorg.0.log seems to be more complete, I was able to reboot the
machine via ssh.
In the kernel log I found the following lines:
Oct 15 21:25:04 f9beta1 kernel: [drm] Initialized drm 1.1.0 20060810
Oct 15 21:25:04 f9beta1 kernel: pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
Oct 15 21:25:04 f9beta1 kernel: [drm:i915_
Oct 15 21:25:04 f9beta1 kernel: [drm] Initialized i915 1.6.0 20080730 on minor 0
Oct 15 21:25:19 f9beta1 acpid: client connected from 2814[0:500]
Oct 15 21:52:46 f9beta1 kernel: konsole[3147]: segfault at 84 ip 0065057f sp bf81b120 error 4 in libkdeui.
Oct 15 21:52:47 f9beta1 kernel: [drm:i915_gem_idle] *ERROR* hardware wedged
what to try next? All help very much appreciated, no_accel is dog slow,
unfortunately.
Greetings,
Konrad
In Red Hat Bugzilla #461829, Robert (robert-redhat-bugs-1) wrote : | #180 |
*** Bug 467554 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Matěj (matj-redhat-bugs) wrote : | #181 |
*** Bug 465844 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Matthias (matthias-redhat-bugs) wrote : | #182 |
Ajax, is this a blocker ?
If it only affects intel kms and we are not enabling that by default, it might not be...
In Red Hat Bugzilla #461829, Joachim (joachim-redhat-bugs) wrote : | #183 |
(In reply to comment #18)
> If it only affects intel kms and we are not enabling that by default, it might
> not be...
Installing F10-Snap1-i686 on Intel 82845G/
It does not seem to be a matter of kernel mode setting anyway which appears to be currently disabled for Intel graphics.
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #184 |
Matthias, I agree with Joachim that this seems unrelated to kernel mode setting. It's a very serious problem that makes it completely impossible to start X. Not that my vote counts for anything, but I think this should be a blocker. Thanks!
In Red Hat Bugzilla #461829, Bob (bob-redhat-bugs) wrote : | #185 |
Still breaks on F10-Snap3-i686. Booted to runlevel 3 and tried to start with:
startx /usr/bin/xterm -- -logverbose 7
(I yum installed xterm on to a live-usb stick)
The herringbone Xserver crosshatch came up, but no xterm and no mouse.
In another network login:
xterm -display :0
and then the Xserver logs a
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
and a backtrace. I've attached Xorg.0.log file, and tacked in the lines
from /var/log/messages.
In Red Hat Bugzilla #461829, Bob (bob-redhat-bugs) wrote : | #186 |
Created attachment 321531
Xorg.0.log from Fedora-
This is a Dell inspiron 7500 laptop.
Fedora-
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #187 |
Bob, yours looks like a separate bug. You should probably open up a new bug report.
In Red Hat Bugzilla #461829, Gerwin (gerwin-redhat-bugs) wrote : | #188 |
This nasty problem doesn't happen only with the i810 driver but also with the "intel" driver. First of all it's not only annoying you don't get a login manager but 2nd, there should be an error telling that X can't be started. So probably 2 bugs.
rawhide version: 29-10-2008
gpu: Intel Corporation 82865G Integrated Graphics Controller
In Red Hat Bugzilla #461829, Matěj (matj-redhat-bugs) wrote : | #189 |
(In reply to comment #24)
> This nasty problem doesn't happen only with the i810 driver but also with the
> "intel" driver. First of all it's not only annoying you don't get a login
> manager but 2nd, there should be an error telling that X can't be started. So
> probably 2 bugs.
Just for the record, at least since F9 i810 driver is just an alias for intel driver.
In Red Hat Bugzilla #461829, Bob (bob-redhat-bugs) wrote : | #190 |
(In reply to comment #23)
> Bob, yours looks like a separate bug. You should probably open up a new bug
> report.
Thanks Andrew - I've created Bug 469292 , and added more detail for my case.
In Red Hat Bugzilla #461829, stefan (stefan-redhat-bugs-1) wrote : | #191 |
Hello,
i do not know if this helps at all but I have a HP Compaq d330 with a intel 82865G Integrated Graphics controller an I too have the same issue described in this thread.
I have tried running F10 snapshot3 i686 KDE4 live cd. The booting of the live cd fails when starting X, nor do i get a nice graphical plymouth boot.
extract from my xorg.0.log:
X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.18-92.1.10.el5 i686
Current Operating System: Linux localhost.
21 01:39:53 EDT 2008 i686
Build Date: 20 October 2008 10:41:26AM
Build ID: xorg-x11-server 1.5.2-8.fc10
Before reporting problems, check http://
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/
(EE) Unable to locate/open config file
(II) Loader magic: 0x81f3400
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 4.1
X.Org XInput driver : 2.1
X.Org Server Extension : 1.1
X.Org Font Renderer : 0.6
(II) Loader running on linux
(++) using VT number 7
......
drmGetBusid returned ''
(II) [drm] loaded kernel module for "i915" driver.
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(**) intel(0): Framebuffer compression disabled
(**) intel(0): Tiling enabled
(==) intel(0): VideoRam: 131072 KB
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Tiled allocation successful.
(II) intel(0): [drm] Registers = 0xfc400000
(II) intel(0): [drm] Initialized kernel agp heap manager, 33554432
(II) intel(0): [dri] visual configs initialized
(II) intel(0): Page Flipping disabled
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 34406400 bytes
(II) EXA(0): Driver registered support for the following operations:
(II) Solid
(II) Copy
(II) Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): [DRI] installation complete
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x03f2f000 (pgoffset 16175)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x03f30000 (pgoffset 16176)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x06000000 (pgoffset 24576)
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffe...
In Red Hat Bugzilla #461829, Andrew (andrew-redhat-bugs) wrote : | #192 |
Do we have any hope for this working in Fedora 10? Just hoping...
Thanks.
In Red Hat Bugzilla #461829, Matěj (matj-redhat-bugs) wrote : | #193 |
*** Bug 469115 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Jaroslav (jaroslav-redhat-bugs) wrote : | #194 |
*** Bug 466801 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Matěj (matj-redhat-bugs) wrote : | #195 |
*** Bug 460776 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Matěj (matj-redhat-bugs) wrote : | #196 |
*** Bug 449491 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Jesse (jesse-redhat-bugs) wrote : | #197 |
An attempt to solve this by reverting the driver to not use the GEM system is in the works. Please stay tuned for test packages.
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #198 |
feel free to throw test packages at us :-). very much appreciated!
(hardware is 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) BTW)
Side note: with Option "Legacy3D" "no" the KDE splash screen is
being displayed properly but the X server is soon getting stuck in some
DRI ioctl .
Just launching X and starting an xterm and twm goes OK, however when
moving around the xterm there is graphics garbage left behind
(mostly thin horizontal and vertical lines). The xterm (maximized)
survives a find / -print and runs at a fine speed. Then I got
adventurous and started firefox on www.orf.at. The page got mostly
displayed but then the X server hung like above.
During boot I only get something like a progress bar in text mode
at the bottom of the screen, no nice splash image at all.
Greetings,
Konrad
In Red Hat Bugzilla #461829, Will (will-redhat-bugs) wrote : | #199 |
The fix Jesse mentioned in comment #33 is in kernel-
(In reply to comment #34)
> During boot I only get something like a progress bar in text mode
> at the bottom of the screen, no nice splash image at all.
That's expected. Graphical boot requires kernel modesetting. Intel modesetting drivers should appear sometime before F11.
In Red Hat Bugzilla #461829, Pieter (pieter-redhat-bugs) wrote : | #200 |
This is on a Dell Inspiron 510M with Intel Corporation 82852/855GM Integrated Graphics Device.
Experienced same error messages as in comment #27 with kernel-
In Red Hat Bugzilla #461829, Pieter (pieter-redhat-bugs) wrote : | #201 |
In comment #36, it should read "same error messages with kernel-
In Red Hat Bugzilla #461829, Mace (mace-redhat-bugs) wrote : | #202 |
With the new kernel, I still get a black screen and hang using XAA. While EXA doesn't hang and I can login, I get screen corruption if using Compiz (or any 3D app).
Supermicro C2SEA with G45 X4500HD:
kernel-
xorg-x11-
xorg-x11-
xorg-x11-
In Red Hat Bugzilla #461829, Will (will-redhat-bugs) wrote : | #203 |
EXA is the default, as far as I can tell. So if the default case works now, we can at least move this off the blocker list.
What error messages appear in Xorg.0.log if you're using XAA?
Screen corruption using Compiz/GL stuff is a separate bug - if it's font corruption, perhaps it's bug 471537?
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #204 |
xorg-x11-
kernel-
Intel Corporation 82865G
Server starts now even w/o xorg.conf but text display is heavily
corrupted. (KDE konsole, Firefox, etc)
With no_accel there is no text corruption.
glxgears
[intel_
668 frames in 5.0 seconds = 133.492 FPS
The corruption looks funny while typing: while typing the "The" at beginning
of this line the "Th" was cut about half vertically(only upper part shown) and
when I typed the "e" then the missing parts appeared.
will attach an image combined from three screen shots (KDE konqueror on www.heise.de)
Thanks for your efforts,
Konrad
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #205 |
Created attachment 323654
graphic glitches, see comment #40
In Red Hat Bugzilla #461829, Konrad (konrad-redhat-bugs) wrote : | #206 |
Created attachment 323659
Xorg.0.log - comment #40
it is almost impossible to view this file in less or vi. about one third of the lines is invisible and gets visible when you move the cursor around vertically.
In Red Hat Bugzilla #461829, Will (will-redhat-bugs) wrote : | #207 |
(In reply to comment #40)
> The corruption looks funny while typing: while typing the "The" at beginning
> of this line the "Th" was cut about half vertically(only upper part shown) and
> when I typed the "e" then the missing parts appeared.
Yes, that looks just like bug 471537. Follow up there for the graphical corruption problems.
Seems like X is starting up successfully now, and there's no mention of the original error message. Closing this bug.
Reopen *only* if X fails to start and the message "Couldn't bind memory for BO front buffer" appears in Xorg.0.log.
In Red Hat Bugzilla #461829, Will (will-redhat-bugs) wrote : | #208 |
*** Bug 471973 has been marked as a duplicate of this bug. ***
In Red Hat Bugzilla #461829, Hollis (hollis-redhat-bugs) wrote : | #209 |
I see this same problem with F10 release, on a Thinkpad T61 with Intel Mobile GM965/GL960 (PCI vendor/ID 8086:2a03).
EXA vs XAA doesn't matter, and neither does the suggested Legacy3D; the only workaround I've found is Option "NoAccel" "yes" in xorg.conf. Same error from dmesg:
...
[drm:
...
Same error from Xorg.0.log:
...
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
kernel-
xorg-x11-
(Additionally there's a failure when the X server crashes that seems to disable all input, so X never exits cleanly and I can't switch to another virtual terminal. All I can do is hit the power button to cleanly reboot [i.e. the ACPI event seems to be handled properly].)
Shirish Agarwal (shirishag75) wrote : | #1 |
Shirish Agarwal (shirishag75) wrote : | #2 |
Shirish Agarwal (shirishag75) wrote : | #3 |
Shirish Agarwal (shirishag75) wrote : | #4 |
Geir Ove Myhr (gomyhr) wrote : Re: [Jaunty,845G] Fatal server error: Couldn't bind memory for BO front buffer | #5 |
Thank you for reporting this bug. Could you please also attche the following:
- /etc/X11/xorg.conf
- output of `lspci -vvnn`
Also, have you installed the libdrm-intel1 package? (see bug 303177)
Shirish Agarwal (shirishag75) wrote : | #6 |
Shirish Agarwal (shirishag75) wrote : | #7 |
Shirish Agarwal (shirishag75) wrote : | #8 |
Changed in xserver-xorg-video-intel: | |
status: | New → Confirmed |
In freedesktop.org Bugzilla #18974, Bryce Harrington (bryce) wrote : | #9 |
Created an attachment (id=20941)
Xorg.0.log
Forwarding this bug report from a Ubuntu reporter:
https:/
Also seen on Fedora:
http://
[Problem]
X hangs during boot with error "Couldn't bind memory for BO front buffer"
[lspci]
00:02.0 VGA compatible controller [0300]: Intel Corporation 82845G/
Subsystem: Intel Corporation 82845G/
[Report]
Regression since 2.4.1 driver seen in 2.5.1 driver on 82845G/
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
Two other users indicated having a matching issue; one user was also on 845, the other on undeclared hardware. http://
Changed in xserver-xorg-video-intel: | |
importance: | Undecided → High |
Bryce Harrington (bryce) wrote : Re: [Jaunty,845G] Fatal server error: Couldn't bind memory for BO front buffer | #10 |
Could be a 845-specific issue (in the forums link, one user saying he had the same issue also saw it on 845; the other user didn't indicate his hardware so who knows.) Anyone on hardware other than 845 able to reproduce it?
Anyway, I've forwarded it upstream here; please subscribe, etc.:
https:/
Changed in xserver-xorg-video-intel: | |
status: | Unknown → Confirmed |
description: | updated |
Jynx97 (jynx97) wrote : | #11 |
Changed in xserver-xorg-video-intel: | |
status: | Unknown → Fix Released |
DougieFresh4U (butcheeyboy) wrote : | #12 |
Bryce Harrington (bryce) wrote : | #13 |
Thanks, so 865 is affected as well apparently. Anyone else seeing this same exact error?
description: | updated |
In freedesktop.org Bugzilla #18974, Gordon Jin (gordon-jin) wrote : | #14 |
Eric says this error appears if you've got a memory allocation setup that doesn't fit in your apperture, and DRI2 will likely fix it.
Twig (pfirth) wrote : Re: [Jaunty,845G] Fatal server error: Couldn't bind memory for BO front buffer | #15 |
I am seeing exactly this behaviour with Jaunty and 845 chipset on an IBM machine.
In freedesktop.org Bugzilla #18974, DougieFresh4U (butcheeyboy) wrote : | #16 |
This is happening with the Intel 865G chipset as well
Marques Johansson (marques) wrote : Re: [Jaunty,845G] Fatal server error: Couldn't bind memory for BO front buffer | #17 |
On a Dell OptiPlex GX270 (bios A07), with a current Jaunty (including libdrm-intel1 2.4.1-0ubuntu5), I have the same problems here:
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA])
Subsystem: Dell Device [1028:0151]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
Region 2: I/O ports at ed98 [size=8]
Capabilities: [d0] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel modules: intelfb
Anand Kumria (wildfire) wrote : | #18 |
I was having this problem too.
I downgraded my kernel to 2.6.27 and things are working perfectly fine.
I suspect the problem is that libdrm is not correctly detecting that the kernel is not doing mode setting.
Twig (pfirth) wrote : | #19 |
I confirm that downgrading to 2.6.27-8 also works for me. The desktop takes forever to load but I suspect that that is another issue.
In freedesktop.org Bugzilla #18974, Marques Johansson (marques) wrote : | #20 |
Since I can't run X with the intel driver in its current state, I have been using the fbdev driver. Here are some details and (attached) log entries. I hope it can be of use:
sudo lspci -nnvv :
00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA])
Subsystem: Dell Device [1028:0151]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx+
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f0000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
Region 2: I/O ports at ed98 [size=8]
Capabilities: [d0] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel driver in use: intelfb
Kernel modules: intelfb
Some lines from dmesg | grep -i -e intel -e drm -e agp:
[ 21.064321] Linux agpgart interface v0.103
[ 21.160181] agpgart-intel 0000:00:00.0: Intel 865 Chipset
[ 21.160644] agpgart-intel 0000:00:00.0: detected 8060K stolen memory
[ 21.162745] agpgart-intel 0000:00:00.0: AGP aperture is 128M @ 0xf0000000
[ 74.884390] intelfb: Framebuffer driver for Intel(R) 830M/845G/
[ 74.884403] intelfb: Version 0.9.6
[ 74.884493] intelfb 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 74.884509] intelfb: 00:02.0: Intel(R) 865G, aperture size 128MB, stolen memory 8060kB
[ 74.888847] intelfb: Initial video mode is 1024x768-32@70.
[ 466.161347] [drm] Initialized drm 1.1.0 20060810
[ 466.201873] intelfb 0000:00:02.0: setting latency timer to 64
[ 466.210603] [drm] Initialized i915 1.6.0 20080730 on minor 0
[ 822.739357] [drm:i915_
[ 822.739365] [drm:i915_
[ 827.341749] [drm:i915_
[ 831.945566] [drm:i915_
[ 1117.105987] [drm:i915_
[ 1827.914660] [drm:i915_
In freedesktop.org Bugzilla #18974, Marques Johansson (marques) wrote : | #21 |
Created an attachment (id=21237)
intel driver failing to load on :1 while :0 is occupied with intelfb/fbdev driver
Changed in xserver-xorg-video-intel: | |
status: | Confirmed → Triaged |
DeJe (djenett) wrote : | #22 |
I can confirm this bug with 855GM chipset.
For me, kernel 2.6.27 was working also. I cannot attach any logs cause I allready reformatted and removed Jaunty. I saw that this error still is in Alpha2 (https:/
Jynx97 (jynx97) wrote : | #23 |
Mahesh Asolkar (asolkar) wrote : | #24 |
Mahesh Asolkar (asolkar) wrote : | #25 |
manzur (sl-solaris) wrote : | #26 |
I can confirm this bug with i845 chipset
trshemanske (thomas-r-shemanske) wrote : | #27 |
I was experiencing this problem with an old uniwell laptop (intel graphics), and have a partial resolution by changing the color depth from 24 to 16 bit, i.e. add
DefaultDepth 16
to the screen section of /etc/X11/xorg.conf
Partial resolution means I can achieve default resolution 1280x800 at 16 bit color using the intel driver
In freedesktop.org Bugzilla #18974, Maxi-daemonizer (maxi-daemonizer) wrote : | #28 |
Created an attachment (id=21481)
Xorg.0.log
same problem here:
(EE) intel(0): Failed to pin back buffer: Cannot allocate memory
(Xorg.0.log ist attached)
lspci:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
kernel: 2.6.28
using 'Option "Legacy3D" "false"' I get working 2D but no 3D:
[intel_
X Error of failed request: BadAlloc (insufficient resources for operation)
Major opcode of failed request: 154 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateCon
Serial number of failed request: 24
Current serial number in output stream: 27
This bug is also present in xf86-video-
In freedesktop.org Bugzilla #18974, Yu Yuwei (acevery) wrote : | #29 |
Created an attachment (id=21482)
Failure log
The same on intel 855GME here,
x11-base/
x11-drivers/
x11-libs/
media-libs/mesa-7.2
sys-kernels/
Gentoo Linux
cat ~/Xorg.0.log | grep -C3 "(EE)"
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/
(==) Using config file: "/etc/X11/
(==) ServerLayout "Simple Layout"
--
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x03bfe000 (pgoffset 15358)
(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x03bff000 (pgoffset 15359)
(II) intel(0): xf86BindGARTMemory: bind key 6 at 0x059ff000 (pgoffset 23039)
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
Marques Johansson (marques) wrote : | #30 |
- NoAccel - working at 1920x1200 Edit (73.5 KiB, text/plain)
I tried setting the DefaultDepth to 16, but that caused X to lock up (mouse worked, could not type in the log in prompt) after a few seconds (less than 15).
I tried adding NoAccel and that is allowing me to use X at 1920x1200, without compiz.
Both logs are attached.
Marques Johansson (marques) wrote : | #31 |
Marques Johansson (marques) wrote : | #32 |
The errors and warnings in the NoAccel log I attached are:
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000207 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(EE) intel(0): Failed to init memory manager
That first error message yields some google matches. I thought EE was a dead end for X, but this log is from the active session.
Shirish Agarwal (shirishag75) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #33 |
Marques Johansso, can you put up your xorg.conf ?
--
Regards,
Shirish Agarwal
This email is licensed under http://
http://
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17
Marques Johansson (marques) wrote : | #34 |
It's the vanilla xorg.conf with 'Option "NoAccel" "true"' added. I have some other junk in there, but that's all it is.
Section "Device"
Identifier "Configured Video Device"
# when intel doesn't work, modprobe intelfb and use these instead of 'driver "intel"'
# Driver "fbdev"
# Option "UseFBDev" "true"
Driver "intel"
Option "NoAccel" "true" # works around LPB 304871 - probably disables the next two
Option "XvMC" "true" # Enabled for no particular reason
Option "TripleBuffer" "true" # Enabled for no particular reason
Option "ModeDebug" "true" # More Verbose logging
Option "FallbackDebug" "true" # More Verbose logging
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
# 16BPP is a possible work around for LPB 304871 that only locks me up at
# 2.6.28-3-generic, xserver-
# DefaultDepth 16
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
Marques Johansson (marques) wrote : | #35 |
I've also used a daily Jaunty live CD while this bug has existed, and strangely enough, the CD which uses the latest xorg and 2.6.28 kernel doesn't give me this problem. Maybe it disables acceleration also - I didn't check.
Marques Johansson (marques) wrote : | #36 |
The log shows that my XvMC is disabled, but if you are going to copy my config line per line, you may also want to make sure the file "/etc/X11/
libIntelXvMC.so.1
Shirish Agarwal (shirishag75) wrote : | #37 |
- Xorg.0.log Edit (87.3 KiB, text/plain)
I also get few warnings
(WW) The directory "/usr/share/
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(WW) intel(0): Register 0x70024 (PIPEASTAT) changed from 0x80000207 to 0x00000000
(WW) intel(0): PIPEASTAT before: status: FIFO_UNDERRUN VSYNC_INT_STATUS SVBLANK_INT_STATUS VBLANK_INT_STATUS OREG_UPDATE_STATUS
(WW) intel(0): PIPEASTAT after: status:
(WW) config/hal: device AT Translated Set 2 keyboard already added. Ignoring.
description: | updated |
Gavin Tweedie (gav-narx) wrote : | #38 |
Pretty sure I'm hitting this too with an Intel 915GM/GMS/910GML chipset. Can supply logs if useful in addition to what is already attached.
Temp workaround for me was to switch to Vesa driver.
In freedesktop.org Bugzilla #18974, Andres-becerra (andres-becerra) wrote : | #39 |
I have the same setup than Yu Yuwei, and I want to add that if I boot a 2.6.27 kernel, xorg starts without problems.
It is only with the 2.6.28 kernel that I can reproduce the failure.
manzur (sl-solaris) wrote : | #40 |
i confirm this too, i can not use jaunty jackalope because of this bug, i am using:
Intel(r) 82845G/GL/GE/PE/GV Graphic Controller
Vikrant (vikrant82) wrote : | #42 |
Sure, intel 915GM is affected too. Also on vesa/fbdev.
jsarman (johnsarman) wrote : | #43 |
I added the Option "NoAccel"
to Section "Device"
worked for me too (I even forgot to put "true" so that must be default)
Robin Becker (robin-reportlab) wrote : | #44 |
I have a DELL 2400 that ran fine with 8.10, but failed after upgrade to Jaunty. lspci reveals
00:00.0 Host bridge: Intel Corporation 82845G/
00:02.0 VGA compatible controller: Intel Corporation 82845G/
00:1d.0 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
00:1d.1 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
00:1d.2 USB Controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
00:1d.7 USB Controller: Intel Corporation 82801DB/DBM (ICH4/ICH4-M) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corporation 82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801DB (ICH4) IDE Controller (rev 01)
00:1f.3 SMBus: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-
01:09.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01)
and the simple fix works ie adding
option "NoAccel" "true"
to Section "Device" in the stock xorg.conf seems to work well for me.
In freedesktop.org Bugzilla #18974, Karsten Heiken (karsten-disposed) wrote : | #45 |
Created an attachment (id=22281)
"*ERROR* GTT full, but LRU list empty" in kernel.log
Same bug here.
It's actually pretty annoying...
No xf86-video-intel 2.5.0+ works for me.
I've got a Sony VAIO SR19XN with the 4500MHD (GM45, right?).
In freedesktop.org Bugzilla #18974, Karsten Heiken (karsten-disposed) wrote : | #46 |
(In reply to comment #8)
> Created an attachment (id=22281) [details]
> "*ERROR* GTT full, but LRU list empty" in kernel.log
>
> Same bug here.
> It's actually pretty annoying...
>
> No xf86-video-intel 2.5.0+ works for me.
> I've got a Sony VAIO SR19XN with the 4500MHD (GM45, right?).
>
Geez, hit the "Commit"-button too fast. Sorry guys.
It's a 2.6.28 kernel using (read: trying to use) xf86-video-intel 2.5.0, Xorg 1.5.3, libdrm 2.4.4.
In freedesktop.org Bugzilla #18974, Lefty (lefty) wrote : | #47 |
i am using intel X3100 (G965 i guess) and having the same error. The configuration:
dri2proto 1.99.3
xf86-dri-proto 2.0.4
mesa 7.3
xorg-server 1.5.99.901
xf86-video-intel 2.6.1
gentoo kernel 2.6.28-r1
it works with NoAccel with cca 150-200 FPS.
I use fbsplash on console (intelfb module). Tried unloading this module and starting X with no success.
the system is unusable after this error, no mouse/keyboard input response (sysrq and power button work i guess).
just tell me if you need more info/debugging. this bug is quite critical (not just) for me.
Bryce Harrington (bryce) wrote : | #48 |
Upstream said that DRI2 will fix this bug.
When someone is able to boot with DRI2 on jaunty, please let us know if this is the case or not.
Changed in xserver-xorg-video-intel: | |
status: | Triaged → Incomplete |
Rick Gabriel (klaxian1) wrote : | #49 |
I tested Jaunty Daily Build 1/27/2009 and the bug still occurs. Is DRI2 live yet? If not, do we have an ETA? I am happy to re-test when it makes sense.
Bryce Harrington (bryce) wrote : | #50 |
klaxian, why didn't you attach your Xorg.0.log?
Robin Becker (robin-reportlab) wrote : | #51 |
- C:\tmp\Xorg.0.log Edit (15.3 KiB, text/plain)
I can confirm the problem is still there as of my latest updates 30/jan/2009 15:gmt.
uname -a ==>
Linux everest 2.6.28-6-generic #16-Ubuntu SMP Mon Jan 26 20:16:00 UTC 2009 i686 GNU/Linux
My Xorg.0.log is attached (there is also an Xorg.failsafe.log as the system tries to start in low res mode).
Rick Gabriel (klaxian1) wrote : | #52 |
Sorry Bryce. I figured there were already enough logs attached, but I would be happy to include mine as well. Since I'm only testing with a LiveCD and it won't boot into X, how do you suggest I go about getting this log? Is there an easy method? Thanks.
Marques Johansson (marques) wrote : | #53 |
I was also able to get the driver working by adding 'Option "DRI" "false"' instead of 'Option "NoAccel" "true"'. It sounds like a more favorable work-around for the time being.
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "XvMC" "true" # /etc/X11/XvMCConfig should contain "libIntelXvMC.so.1"
Option "DRI" "false"
Option "ModeDebug" "true"
Option "FallbackDebug" "true"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
EndSection
In freedesktop.org Bugzilla #18974, Lefty (lefty) wrote : | #54 |
I'm afraid DRI2 doesn't fix that as it was reported with 1.5.99 (and kernel 2.6.29) by several people. You can find one experimenting with several versions here: https:/
Bryce Harrington (bryce) wrote : | #55 |
In Jaunty, it is now possible to use DRI2 by using UXA. This can be done by specifying Option "AccelMethod" "UXA" in your xorg.conf.
Note that it will *probably* break your xorg very badly, however I don't know anyone who has tested it on 8xx chips, so who knows. A few people have found that with UXA it resolves all performance issues and works great. Other people have found it freezes on displaying the login screen, and other problems, so please be forewarned.
Once we have someone's testing of UXA on 8xx, we can re-ping upstream about this issue.
Robin Becker (robin-reportlab) wrote : | #56 |
- Xorg.0.log Edit (20.6 KiB, text/plain)
OK I have the 82845G chipset and UXA works up to a point in that I see the GDM splash screen and the mouse works, but I find my keyboard locked whilst trying to login (User name appeared after a pause, but could not enter). I attach the Xorg.0.conf
Robin Becker (robin-reportlab) wrote : | #57 |
I have also tried Marques Johansson method and that works and seems better than just disabling all acceleration.
trylik (marek-nasionka) wrote : | #58 |
i can confirm, that on my laptop it is fixed on latest jaunty updates
i have:
Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582]
Changed in xserver-xorg-video-intel: | |
status: | Incomplete → Triaged |
Kieran Hogg (xerosis) wrote : | #59 |
To confirm, Option "AccelMethod" "UXA" worked for me on a Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller.
jsarman (johnsarman) wrote : | #60 |
Option "AccelMethod" "UXA" did not work for
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
The video did come up and immediately had no keyboard. Restarted GDM with no effect. Tried to reboot computer, it just ignored me, ssh was still working so I umounted my raid and did a hard reboot. It booted again and now I had keyboard and mouse. I logged in but before gnome fully came up, it locked up again. I tried all the above steps nothing, so i changed back to NoAccel and reboot the hard way and bqack to normal.
In freedesktop.org Bugzilla #18974, Gordon Jin (gordon-jin) wrote : | #61 |
(In reply to comment #11)
> I'm afraid DRI2 doesn't fix that as it was reported with 1.5.99 (and kernel
> 2.6.29) by several people. You can find one experimenting with several versions
> here: https:/
Is UXA used? (DRI2 takes effect only when UXA enabled)
Twig (pfirth) wrote : | #62 |
Using the following hardware:
00:02.0 VGA compatible controller: Intel Corporation 82845G/
Option "AccelMethod" "UXA" will boot to graphical login prompt but is incredibly slow and not usable. Had to kill -9 X from ssh session and reboot.
Option "DRI" "false" and option "Noaccel" "true" are equally usable.
Marques Johansson (marques) wrote : | #63 |
UXA also locks my X up after a few seconds.
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) (prog-if 00 [VGA])
Subsystem: Dell Device 0151
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
Region 1: Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
Region 2: I/O ports at ed98 [size=8]
Capabilities: [d0] Power Management version 1
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Kernel modules: intelfb
Götz Christ (g-christ) wrote : | #64 |
I have tested Kubuntu Jaunty amd64 Desktop from 03-feb-2009 http://
Also bug 295934 get fixed in Jaunty.
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
redada (infos-redada) wrote : | #65 |
UXA locks my laptop with i830m graphics:
00:02.0 VGA compatible controller: Intel Corporation 82830 CGC [Chipset Graphics Controller] (rev 04)
With Option ""NoAccel" "true" i get a usable (but sluggish) desktop, with just ~50 FPS in glxgears.
Mirko Pace (mirkop82) wrote : | #66 |
With following hardware:
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
and UXA method works but with aprox 300FPS in glxgear.
In freedesktop.org Bugzilla #18974, Lefty (lefty) wrote : | #67 |
UXA hangs as well. see https:/
Dominique Meeùs (dominiquem) wrote : | #68 |
- Archive generated by failsave Edit (50.0 KiB, application/x-tar)
After upgrading from Ubuntu 8.10, upon restart I got after the progression bar with Ubuntu logo a black (blueish) screen for gdm (with usual sound). Ctrl+Alt+F1 seemed to do something, but with the same screen. At least Ctrl+Alt+Del would restart the system. Choosing 2.6.27 in grub didn't make a difference. After some more restarts, I was proposed failsafe on server 1 (0 beeing busy. Failsave proposed to archive the logs, which I did (attachment). This failsafe is in 1280*1024 (the screen's best)which allows me to write this normally.
Dominique Meeùs (dominiquem) wrote : | #69 |
- lspcivvnn.txt Edit (9.4 KiB, text/plain)
Video is Intel 945G. (Full lspci -vvnn attached)
00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02)
Subsystem: ASUSTeK Computer Inc. Device [1043:817a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 0: Memory at dfe00000 (32-bit, non-prefetchable) [size=512K]
Region 1: I/O ports at 8800 [size=8]
Region 2: Memory at e0000000 (32-bit, prefetchable) [size=256M]
Region 3: Memory at dfe80000 (32-bit, non-prefetchable) [size=256K]
Capabilities: <access denied>
Kernel modules: intelfb
Aram Yegenian (aramyegenian) wrote : | #70 |
UXA locks up my pc, im running latest packages
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "ModeDebug" "true"
Option "FallbackDebug" "true"
Option "AccelMethod" "UXA"
Option "XvMC" "true"
Option "DRI" "false"
EndSection
Aram Yegenian (aramyegenian) wrote : | #71 |
- Xorg.0.log Edit (73.8 KiB, application/x-trash)
and the Xorg log... sorry i couldn't tell how to attach two log files in one post.
nblracer (nblracer) wrote : | #72 |
Confirmed here on Dell Dimension 4500s
This xorg.conf, with 16 bit and no acel worked at a temp fix
https:/
put very poor refresh rate/fps
Dominique Meeùs (dominiquem) wrote : | #73 |
I came here seeing a warning about Intel under http://
I keep getting things like
[ 0.148993] (II) intel(0): Output VGA using monitor section Monitor0
[ 0.149006] (**) intel(0): Option "PreferredMode" "1280x1024"
[ 1.201850] (II) intel(0): Output VGA disconnected
[ 1.201890] (WW) intel(0): No outputs definitely connected, trying again...
[ 1.201901] (II) intel(0): Output VGA disconnected
[ 1.201912] (WW) intel(0): Unable to find initial modes
[ 1.201923] (EE) intel(0): No valid modes.
[ 1.499698] (II) UnloadModule: "intel"
[ 1.499738] (II) UnloadModule: "vgahw"
[ 1.499749] (II) Unloading /usr/lib/
[ 1.499768] (EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
After some restarts, I once got a regular mode. Most of the time nothing. Sometimes failsafe.
Bryce Harrington (bryce) wrote : | #74 |
I would like to ask that all subscribers to this bug with i8xx hardware please test activating UXA. Directions and a place to record your findings are at this page:
https:/
The reason I ask is that there have been just two 8xx users reporting there (both indicating very positive findings), and I'd like to obtain broader test coverage, particularly so we will know about problems.
Steve Beattie (sbeattie) wrote : | #75 |
@Dominique: yes, your issue is probably a separate bug, please open a new bug report, preferably by using the ubuntu-bug tool as described in https:/
Khashayar Naderehvandi (khashayar) wrote : | #76 |
Bryce, I had a minute to try out the latest alpha live CD on my 855 with UXA. It was a big improvement for me. I've updated the matrix. It wasn't extensive testing. I had compiz and UXA running for as long as it takes to install Jaunty + an additional 20 minutes or so. No lockups.
Anand Kumria (wildfire) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #77 |
On Tue, Feb 10, 2009 at 10:20 PM, Bryce Harrington
<email address hidden> wrote:
> I would like to ask that all subscribers to this bug with i8xx hardware
> please test activating UXA. Directions and a place to record your
> findings are at this page:
>
> https:/
>
> The reason I ask is that there have been just two 8xx users reporting
> there (both indicating very positive findings), and I'd like to obtain
> broader test coverage, particularly so we will know about problems.
Done.
On a 82852/855GM is is nice to see native resolution again.
Unfortunately the blue squares replacing various text pixmaps maps the
system unusable within 30 minutes.
I also see some icon corruption as well.
I have not taken into account any kind of performance and in order to
avoid a lock-up you must disable visual effects as well.
Thanks,
Anand
Aram Yegenian (aramyegenian) wrote : | #78 |
- Xorg.0.log Edit (36.2 KiB, text/plain)
Bryce,
I have added my findings on the wiki. I'm also attaching the latest Xorg.0.log. I want to reaffirm that only the vesa driver doesn't cause my system to lock up.
Thanks,
Aram
Götz Christ (g-christ) wrote : | #79 |
- screenshots, logs, exa, uxa on 865g Edit (161.4 KiB, application/x-tar)
Added dmesg and Xorg.0.log using UXA, and screenshots showing corruption with EXA and UXA. Also added findings on the wiki.
Manuel Siggen (manuel-siggen) wrote : | #80 |
On my system (Thinkpad X40), UXA works nicely and gives the best performance when desktop effects are activated, but it shows some random screen corruption (blanked characters, red-filled icons, horizontal lines...).
lspci:
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
$ apt-cache show xserver-
Version: 2:2.6.1-1ubuntu2
$ uname -a
Linux x40 2.6.28-5-generic #15-Ubuntu SMP Thu Jan 22 21:21:04 UTC 2009 i686 GNU/Linux
(I cannot use the latest kernel because usplash doesn't ask for crypt-setup password)
jerrylamos (jerrylamos) wrote : | #81 |
uxa gives a blue screen with white top and bottom borders, then no response to any keyboard action. Mouse pointer moves however no response to clicks.
IBM ThinkCentre A30
Intel Corporation 82845G/
Jaunty uname -a
linux 2.6.28-7-generic #20-Ubuntu SMP Mon Feb 9 15:43:21 UTC 2009 i686 GNU/Linux
Since the system is dead altogether no logs or dmesg. Only thing that works is Option "NoAccel" which is pretty slow.
Jerry
Bryce Harrington (bryce) wrote : | #82 |
Thanks everyone, this fleshes in the table a lot better. It confirms what I suspected at the beginning - it's a mixed bag, great for some, poor for others, and unfortunately there's not a strong correlation between success and chip family, so black/whitelisting doesn't seem to be an option for us.
From what I gather, upstream is going to be sticking with UXA. Earlier on it sounded like they would backport stuff to EXA once it was ready, but recent comments make it sound like that is no longer the plan. So going forward I anticipate that Intel will be prioritizing support for UXA issues over EXA, which means we are going to be faced with the situation of a) user for whom UXA is better than EXA will be pushing us to move to UXA by default, and b) people for whom EXA has been working ok but UXA brings problems will be upset to see the regressions.
In my ideal world, what I would like to see is for us the distro to hold off on moving to UXA until it is more stable, and have technically able users such as yourselves take the initiative of working with upstream directly at getting the issues you've found investigated and solved. This would help Ubuntu out a lot in paving a path of stability with UXA that we can follow for Jaunty+1 (and maybe even Jaunty if enough work gets done in the next few weeks).
So I would like to encourage each of you to forward the issues you find upstream. Here is a link to use in filing your bugs:
https:/
When filing your bugs upstream, please always include your Xorg.0.log (and/or Xorg.0.log.old) after reproducing the issue with Option "ModeDebug" "true" in your xorg.conf. Also include your PCI IDs, which you can get by running the command `lspci -vvnn | grep -A2 "VGA compat"`.
Additional guidelines on filing bugs upstream to Intel are at http://
Once you've filed your bug, it would be wonderful if you could also include a link to the bug in your comments on the UxaTesting wiki page - https:/
In freedesktop.org Bugzilla #18974, Lefty (lefty) wrote : | #83 |
Hangs even with:
kernel-
xorg-x11-
xorg-x11-
libdrm-
mesa-libGL-
mesa-libGLU-
mesa-dri-
... and UXA enabled
logs can be found here: https:/
original comment at RH bugzilla: https:/
DRI2 really doesn't fix that ...
Khashayar Naderehvandi (khashayar) wrote : | #84 |
Perhaps it would make sense to track version 2.7 of the intel driver for jaunty (which would in effect mean the master branch for now, I guess). After all, intel releases on a quarterly basis. Last release was in q4 2008, so 2.7 should be released in q1 2009, i.e. in time for the jaunty release. And I'm sure it'll have a lot of UXA stabilization going in. In either event, it's hard to imagine 2.7 being less stable and less performant than 2.6.x :-p
In freedesktop.org Bugzilla #18974, Lefty (lefty) wrote : | #85 |
Next try:
kernel-
xorg-x11-
xorg-x11-
xorg-x11-
libdrm-
mesa-libGL-
mesa-libGLU-
mesa-dri-
"The keyboard does not hang. chvt works. I can use
ctrl-alt-F2 to change to a vt and blindly log in (verified that mingetty
changes to bash using ps in a ssh session). Despite changing vt's and back to
vt7, the backlight remains off. However "xdpyinfo -display :0" hangs when
ssh'ing into the laptop. Though the mouse is not visible, moving the mouse in
the direction of the xterm and typing commands doesn't produce any results
(example: "ls > /tmp/x" doesn't create file /tmp/x)."
messages:
Feb 14 21:36:19 blu kernel: [drm] Initialized drm 1.1.0 20060810
Feb 14 21:36:19 blu kernel: pci 0000:00:02.0: PCI INT A -> Link[LNKA] -> GSI 11
(level, low) -> IRQ 11
Feb 14 21:36:19 blu kernel: [drm] Initialized i915 1.6.0 20080730 on minor 0
Feb 14 21:36:19 blu kernel: [drm:i915_irq_emit] *ERROR* i915_irq_emit called
without lock held, held 0 owner (null) dce600f0
end of xorg log:
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007df000 (pgoffset 2015)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x00800000 (pgoffset 2048)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-
(II) intel(0): 0x00020000-
(II) intel(0): 0x00025000-
(II) intel(0): 0x007df000: end of stolen memory
(II) intel(0): 0x007df000-
)
(II) intel(0): 0x00800000-
(II) intel(0): 0x08000000: end of aperture
_fence_
original: https:/
In freedesktop.org Bugzilla #18974, Zdenek Kabelac (zdenek-kabelac) wrote : | #86 |
I think I'm seeing now the same bug:
Even shortly after boot:
[ 223.795729] gnome-screensav used greatest stack depth: 3288 bytes left
[ 563.731434] [drm:i915_
[ 563.731441] [drm:i915_
My machine is T61, C2D, 4GB RAM.
I'm running 2.6.29-rc5, x86_64, UXA acceleration
Xorg server from Fedora Rawhide:
drm library commit: eb78c53aa1a980e
xf86-video-intel: 3012d85cc5eb58c
(both relatively recent I guess)
I only see this dmesg error message - there is no error message in Xorg.0.log yet
Changed in xserver-xorg-video-intel: | |
assignee: | nobody → bryceharrington |
In freedesktop.org Bugzilla #18974, Opensource-andmarios (opensource-andmarios) wrote : | #87 |
I confirm this bug. I think it is related to kernel version 2.6.28 or higher since it does not happen with kernel 2.6.27.
It happens with every combination I have tried: xf86-video-intel (2.5.0, 2.5.1, 2.6.1), xorg-server (1.5.3, 1.5.99.902), dri2proto (1.1, 1.99.3), mesa (7.2, 7.3), libdrm (2.4.3, 2.4.4).
lspci:
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Fujitsu Siemens Computers Device 1108
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at fc000000 (64-bit, non-prefetchable) [size=1M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 1800 [size=8]
Expansion ROM at <unassigned> [disabled]
Sorry but I do not know which info would help, if there is something you need please ask.
Bryce Harrington (bryce) wrote : | #88 |
> In either event, it's hard to imagine 2.7 being less stable and less performant than 2.6.x :-p
You're new here, aren't you. ;-)
Martin Pitt (pitti) wrote : | #89 |
Bryce, I assume this model worked with XAA? Is it possible to switch between XAA and EXA on a per-model basis?
Bryce Harrington (bryce) wrote : | #90 |
Martin, yes it is possible to switch between XAA and EXA on a per-model basis. The trade-off is that Intel will *only* support EXA, so we would not be able to upstream bugs for any chips that use XAA. They asked us last year to stop using XAA and move to EXA for all chips, in order to make it easier for them to provide support.
We've actually had a series of problems with 8xx chips ever since moving from -i810 to -intel in the Hardy timeframe. There have been a series of performance and stabilization regressions on these old chips as upstream has moved forward, that seem to not be getting attention. Indeed, they have completely dropped support on i815 and some of the other very early 8xx chips.
So, if XAA makes things better on i845, we can consider moving to it, but understand that once we do so we probably won't be able to get any other bugs fixed on this chipset.
jerrylamos (jerrylamos) wrote : | #91 |
XAA not much luck on this i845. Sometimes it will run for a minute or two, today it wouldn't even complete booting complaining about low graphics mode with 2.6.28-8.8. Neither is UXA or EXA I could generate Xorg.0.logs if they are of interest.
Presently for jaunty I'm using Driver "vesa" which has much much better scroll than Driver "Intel" Option "NoAccel".
By far the best is intrepid ibex with acpid=noirq.
Ubuntu seems to be well on the path of "latest, high end equipment only" which is the way Microsoft goes. If it weren't for the jaunty video the performance of this 2 gHz Celeron is just fine for internet news, flash videos, Office Write & spreadsheet, mail, ... No I don't do games.
So I may well be stuck on Intrepid for IBM Think Centre A30 2 gHz Celeron and IBM Thinkpad R31 1 gHz Celeron. The IBM Thinkpad T40 and Compaq Presario 3.3 gHz Celeron are O.K. with jaunty, who knows about Koala....
Thanks for your efforts on this. Jerry
In freedesktop.org Bugzilla #18974, Opensource-andmarios (opensource-andmarios) wrote : | #92 |
An update over my previous comment.
I edited xorg.conf and set explicitly for the intel driver to use UXA acceleration (it doesn't use it automatically). That way I am able to boot to a 2.6.28 kernel and use my desktop. There are some problems but X is up and running and this is generally considered as a good thing!
Sorry I hadn't tried this earlier since it is mentioned in the comments above, but I was somewhat confused by the intel driver's documentation as the man page (up to version 2.6.1) doesn't include UXA as a possible option to AccelMethod.
Bryce Harrington (bryce) wrote : | #93 |
> Ubuntu seems to be well on the path of "latest, high end equipment only" which is the way Microsoft goes.
Please, that is hardly a fair statement to make.
The purpose for putting out new Ubuntu releases is *primarily* to provide users with easy access to the latest code from upstream. If upstream chooses to drop support for some old piece of hardware, there is often little we can do about it at the distro level; if it's something our OEMs care about or that has a ton of users, Canonical may be able to justify investing resources there, but that is rarely the case with legacy graphics hardware. If an older release works, stick with it.
Ultimately, part of the reason we all want to see hardware vendors putting out their drivers as open source instead of proprietary, is so that when the company decides to cut off support for a chip, at least the community has the option to provide support for it themselves. We're in that situation now for i815 and i825; it stands to reason eventually we'll be there with i845 too.
I don't like seeing support for old Intel chips deteriorate any more than owners of the chip do, but I think at some point the only way we're going to keep up support on the old chips is if some community heroes step up to the plate and take a swing at it themselves. The good news is that with -intel, most of the code is already there, and experts are easily at hand for advice and guidance; if you have the hardware, ample free time, and know a little C coding, you can do it.
In freedesktop.org Bugzilla #18974, Lefty (lefty) wrote : | #94 |
i upgraded kernel to vanilla 2.6.29-r6 and UXA relatively works.
dmesg:
[drm:i915_
[drm:i915_
empty 1
-↑- several times
[drm:i915_
FPS cca 600 in glxgears with vblank_mode=0.
Anand Kumria (wildfire) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #95 |
On Fri, Jan 30, 2009 at 2:48 AM, Bryce Harrington
<email address hidden> wrote:
> Upstream said that DRI2 will fix this bug.
>
> When someone is able to boot with DRI2 on jaunty, please let us know if
> this is the case or not.
Hi,
I am running:
eve[~]% uname -a
Linux eve 2.6.29-
UTC 2009 i686 GNU/Linux
And everything is now working as expected.
So it seems:
2.6.27 (via linux-ports) works but does not have audio modules
2.6.28 (9.04 kernel) does not work (glyph corruption, eventual machine hang)
2.6.29-rc6 (and later, presumably) will work
What is the process from here? As 2.6.28 will be the shipping kernel
anyone upgrading with i845 / i855 hardware is going to experience an
issue.
Cheers,
Anand
Edmond Thiebaud (thiebaude) wrote : | #96 |
I can confirm my Intel i815 integrated graphics has this problem, x starts then its says something about Intel freezing and I never can get to a log-in screen, so then I can't use Ubuntu 9.04.I hope this is fixed so I can upgrade to 9.04.and I also have to say since I've been using Ubuntu since 6.06 I have never had a problem with any alpha's or beta with the i815 graphics driver.email me ,please when there is a workaround this.
thanks
keep up the good work.
Anand Kumria (wildfire) wrote : | #97 |
Hi Edmond,
If you have had a chance to read the various things stated, there are
three workarounds:
- use the 2.6.27 kernel
- use the 2.6.28 kernel
- skip the upgrade to 9.04
Cheers,
Anand
On Sat, Feb 28, 2009 at 5:27 AM, Edmond Thiebaud <email address hidden> wrote:
> I can confirm my Intel i815 integrated graphics has this problem, x
> starts then its says something about Intel freezing and I never can get
> to a log-in screen, so then I can't use Ubuntu 9.04.I hope this is fixed
> so I can upgrade to 9.04.and I also have to say since I've been using
> Ubuntu since 6.06 I have never had a problem with any alpha's or beta
> with the i815 graphics driver.email me ,please when there is a
> workaround this.
>
> thanks
>
> keep up the good work.
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>
In freedesktop.org Bugzilla #18974, Yu Yuwei (acevery) wrote : | #98 |
I test xf86-video-
Xorg.0.log:
(II) intel(0): [DRI] installation complete
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x02ff4000 (pgoffset 12276)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x02ff5000 (pgoffset 12277)
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x02ff9000 (pgoffset 12281)
(II) intel(0): xf86BindGARTMemory: bind key 3 at 0x02ffa000 (pgoffset 12282)
(II) intel(0): xf86BindGARTMemory: bind key 4 at 0x02ffe000 (pgoffset 12286)
(II) intel(0): xf86BindGARTMemory: bind key 5 at 0x02fff000 (pgoffset 12287)
(II) intel(0): xf86BindGARTMemory: bind key 6 at 0x059ff000 (pgoffset 23039)
(EE) intel(0): Failed to pin back buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO back buffer
(II) intel(0): xf86UnbindGARTM
(II) intel(0): xf86UnbindGARTM
(II) intel(0): xf86UnbindGARTM
(II) intel(0): xf86UnbindGARTM
(II) intel(0): xf86UnbindGARTM
(II) intel(0): xf86UnbindGARTM
(II) intel(0): xf86UnbindGARTM
dmesg | grep drm:
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized i915 1.6.0 20080730 on minor 0
[drm:i915_setparam] *ERROR* unknown parameter 4
[drm:i915_getparam] *ERROR* Unknown parameter 6
[drm:i915_
[drm:i915_
[drm:i915_getparam] *ERROR* Unknown parameter 6
[drm:i915_
[drm:i915_
[drm:i915_getparam] *ERROR* Unknown parameter 6
[drm:i915_
[drm:i915_
seems the drm(20060810) is not compatible with new i915(20080730).
Bryce Harrington (bryce) wrote : | #99 |
Status update:
I've seen there are a bunch of BO fixes included in the 2.6.3 version of the driver, however that version has new dependencies. I've done the merge of the 2.6.3 -intel, however it won't build until the dependencies are satisfied. I've packaged and uploaded libdrm 2.4.5 that it requires, and this is included in Alpha6. It also requires a small kernel change, which I've spoken to the kernel team about but that won't go in until after Alpha6 at the earliest.
Also, the vast bulk of the 2.6.3 changes are for features we do not enable by default yet, so I'm not certain if the benefit is going to outweigh the risk. We'll want to make sure ample testing is done on it before we make the decision.
Götz Christ (g-christ) wrote : | #100 |
I only get the message "Fatal server error: Couldn't bind memory for BO front buffer" when trying to use XAA in a i865G, but not with EXA nor with UXA.
Using Intel 2.7 RC1, Kernel 2.6.29 RC7, and the Xserver + Mesa from the repository I don't get so many corruptions on screen, but still some, especially with wine, virtualbox and flash videos. Using composition those corruptions go away, but scrolling text e.g. with Firefox is slower.
Also UXA is more stable, it doesn't crash any more with opengl apps like glxgears, but it is not possible to distinguish the gears, it is like blur.
With my little experience, I think that we should try intel 2.6.3.
Edmond Thiebaud (thiebaude) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #101 |
I have good news and bad news, before i wasn't able to get into 9.04, but
just a few hours ago i upgraded to 9.04 again and was not able to login to
9.04, but i was able to log in fluxbox.
On Wed, Mar 11, 2009 at 4:30 PM, G. Christ <email address hidden> wrote:
> I only get the message "Fatal server error: Couldn't bind memory for BO
> front buffer" when trying to use XAA in a i865G, but not with EXA nor
> with UXA.
>
> Using Intel 2.7 RC1, Kernel 2.6.29 RC7, and the Xserver + Mesa from the
> repository I don't get so many corruptions on screen, but still some,
> especially with wine, virtualbox and flash videos. Using composition
> those corruptions go away, but scrolling text e.g. with Firefox is
> slower.
>
> Also UXA is more stable, it doesn't crash any more with opengl apps like
> glxgears, but it is not possible to distinguish the gears, it is like
> blur.
>
> With my little experience, I think that we should try intel 2.6.3.
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
> (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Khashayar Naderehvandi (khashayar) wrote : | #102 |
Since I'm the guy who suggested we track 2.7, obviously I think 2.6.3 is a good idea :-p
Seriously, the fixes that have gone into 2.6.3 might not be relevant for what's gonna be enabled by default in Jaunty, but if things don't improve, 855GM users are gonna see forum posts that say "add accelmethod UXA to xorg.conf and you'll be fine." Which brings me to my point: with 2.6.3 I have had no server crash on my 855GM with UXA enabled, whereas on 2.6.1 I had a couple of hard xserver hangs.
So +1 for trying out 2.6.3 :-)
Étienne BERSAC (bersace) wrote : | #103 |
Hi,
> So +1 for trying out 2.6.3 :-)
Me too. I also hits freeze on GMA965 on last intel-GPU MacBook. Looks
like the problem does not touch only old hardwares.
Regards,
Étienne
--
E Ultreïa !
Dirk Gerrits (dirk-gerrits) wrote : | #104 |
I've been getting the "Fatal server error: Couldn't bind memory for BO front buffer" error as well on Jaunty with my old laptop's "Intel Corporation 82852/855GM Integrated Graphics Device". The error goes away for me by adding
Option "Legacy3D" "false"
to the Device section.
Marques Johansson (marques) wrote : | #105 |
Nolari, with Legacy3d false, does it work in AccelMethod UXA, EXA, or both?
Dirk Gerrits (dirk-gerrits) wrote : | #106 |
Marques: seems to work with both.
Stefan Glasenhardt (glasen) wrote : | #107 |
There is a fix for this issue in the newest driver-version :
"Drop Legacy3D option, only use fixed texture space with non-gem."
Together with two other git-commits (see Bug #316588) backported to the driver version 2.6.1, the driver now works perfectly on my 855-chipset.
jerrylamos (jerrylamos) wrote : | #108 |
O.K., downloaded
xf86-video-
any hints on how to use this directory?
There seems to be a Makefile.am in it and an autogen.sh however I don't know the command line commands to do anything with them.
Thanks for hints,
Jerry
Götz Christ (g-christ) wrote : | #109 |
You can test the latest intel (from git) driver and other stuff from the "PPA for xorg crack pushers" https:/
I'm using this right now with linux 2.6.29 rc7 and everything seems stable and with less problems.
In freedesktop.org Bugzilla #18974, Bryce Harrington (bryce) wrote : | #110 |
Gordon, please would you mind giving us an update on the status of this bug?
Bryce Harrington (bryce) wrote : | #111 |
I've uploaded 2.6.3 a couple days ago, which in theory should fix this problem.
@Shirish, mind updating to latest jaunty and re-testing?
wilbur (wilburgr) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #112 |
I have updated to 2.6.3 but it has made no difference at all to the
reported problem.
Thanks for the update.
If any one or combination of these lines is remarked in the xorg.conf file
the system throws the error or fails to boot.
Option "DRI" "False"
Option "NoAccel" "True"
Option "AccelMethod" "UXA"
2009/3/18 Bryce Harrington <email address hidden>
> I've uploaded 2.6.3 a couple days ago, which in theory should fix this
> problem.
>
> @Shirish, mind updating to latest jaunty and re-testing?
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
> (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “xserver-
> Status in xserver-
> Status in “xserver-
>
> Bug description:
> Since the change from the 2.4.1 driver to 2.5.1, Jaunty now hangs during
> boot, with "Fatal server error: Couldn't bind memory for BO front buffer"
> shown in the log. So far, this has been seen by two people with i845
> graphics and two with i865.
>
> Also discussed at this forum:
> https:/
>
> [Original Report]
> Binary package hint: xserver-
>
> Hi all,
> This is in jaunty, I get no screens.
>
>
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation 82845G/
> DRAM Controller/Host-Hub Interface [8086:2560] (rev 03)
> 00:02.0 VGA compatible controller [0300]: Intel Corporation
> 82845G/
> (rev 03)
> Subsystem: Intel Corporation 82845G/
> Integrated Graphics Device [8086:2562]
>
>
In freedesktop.org Bugzilla #18974, Karsten Heiken (karsten-disposed) wrote : | #113 |
I also suffered from this bug.
But recently I found out, that it only happened, when there is a "Virtual"-option in my Xorg.conf:
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "LVDS"
DefaultDepth 24
SubSection "Display"
Modes "1280x800_60"
Virtual 2960 1056
EndSubSection
EndSection
When I removed the Virtual-option, everything went fine.
The other day i reinstalled my system (Arch Linux) and installed the newest packages from the testing-repository.
Namely those packages are:
xf86-video-intel 2.6.99.902-1
libdrm 2.4.5-2
mesa 7.3-2
xorg-server 1.6.0-1
After a few changes in my Xorg.conf I came to these settings:
Section "Device"
Identifier "Device0"
Driver "intel"
Option "Legacy3D" "true"
Option "DRI" "true"
Option "AccelMethod" "uxa"
Option "ExaNoComposite" "true"
EndSection
I put the Virtual-section back in - I need my 22" lcd ;)
And what do my eyes see?
Everything works!
I also tried the latest xf86-video-intel via GIT. Same thing there.
I installed ioquake3 - and woohoo! 90fps.
Everything's great right now.
Maybe someone could try those Xorg.conf-settings and the latest git-version.
Regards,
karsten
Anand Kumria (wildfire) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #114 |
Hi,
I've also upgraded, done the same tests and experienced the same failures.
Anand
On Thu, Mar 19, 2009 at 3:00 AM, wilbur <email address hidden> wrote:
> I have updated to 2.6.3 but it has made no difference at all to the
> reported problem.
>
> Thanks for the update.
>
> If any one or combination of these lines is remarked in the xorg.conf file
> the system throws the error or fails to boot.
>
> Option "DRI" "False"
> Option "NoAccel" "True"
> Option "AccelMethod" "UXA"
>
>
> 2009/3/18 Bryce Harrington <email address hidden>
>
>> I've uploaded 2.6.3 a couple days ago, which in theory should fix this
>> problem.
>>
>> @Shirish, mind updating to latest jaunty and re-testing?
>>
>> --
>> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
>> (Jaunty)
>> https:/
>> You received this bug notification because you are a direct subscriber
>> of a duplicate bug.
>>
>> Status in X.org xf86-video-intel: Confirmed
>> Status in “xserver-
>> Status in xserver-
>> Status in “xserver-
>>
>> Bug description:
>> Since the change from the 2.4.1 driver to 2.5.1, Jaunty now hangs during
>> boot, with "Fatal server error: Couldn't bind memory for BO front buffer"
>> shown in the log. So far, this has been seen by two people with i845
>> graphics and two with i865.
>>
>> Also discussed at this forum:
>> https:/
>>
>> [Original Report]
>> Binary package hint: xserver-
>>
>> Hi all,
>> This is in jaunty, I get no screens.
>>
>>
>>
>> [lspci]
>> 00:00.0 Host bridge [0600]: Intel Corporation 82845G/
>> DRAM Controller/Host-Hub Interface [8086:2560] (rev 03)
>> 00:02.0 VGA compatible controller [0300]: Intel Corporation
>> 82845G/
>> (rev 03)
>> Subsystem: Intel Corporation 82845G/
>> Integrated Graphics Device [8086:2562]
>>
>>
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>
Marques Johansson (marques) wrote : | #115 |
2.6.3 isn't a solution for me either. UXA locks X (the keyboard and display locks during the gnome-session startup - the mouse cursor works however). I think the BO aspect of the xserver-
This log was generated when I tried EXA with NoLegacy3D:
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux bang 2.6.28-10-generic #33-Ubuntu SMP Tue Mar 17 12:27:50 UTC 2009 i686
Build Date: 07 March 2009 02:18:57AM
xorg-server 2:1.6.0-0ubuntu1 (<email address hidden>)
Before reporting problems, check http://
to make sure that you have the latest version.
Markers: [ 0.011339] (--) probed, [ 0.011360] (**) from config file, [ 0.011375] (==) default setting,
[ 0.011390] (++) from command line, [ 0.011404] (!!) notice, [ 0.011418] (II) informational,
[ 0.011433] (WW) warning, [ 0.011447] (EE) error, [ 0.011461] (NI) not implemented, [ 0.011476] (??) unknown.
[ 0.011590] (==) Log file: "/var/log/
[ 0.028686] (==) Using config file: "/etc/X11/
exaCopyDirty: Pending damage region empty!
error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid argument (22)
ddxSigGiveUp: Closing log
This is what I got from UXA without default options. (I can't use UXA with DRI off. X still locks with Legacy3D)
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
Current Operating System: Linux bang 2.6.28-10-generic #33-Ubuntu SMP Tue Mar 17 12:27:50 UTC 2009 i686
Build Date: 07 March 2009 02:18:57AM
xorg-server 2:1.6.0-0ubuntu1 (<email address hidden>)
Before reporting problems, check http://
to make sure that you have the latest version.
Markers: [ 0.017446] (--) probed, [ 0.017469] (**) from config file, [ 0.017484] (==) default setting,
[ 0.017498] (++) from command line, [ 0.017513] (!!) notice, [ 0.017527] (II) informational,
[ 0.017541] (WW) warning, [ 0.017556] (EE) error, [ 0.017570] (NI) not implemented, [ 0.017584] (??) unknown.
[ 0.017701] (==) Log file: "/var/log/
[ 0.034666] (==) Using config file: "/etc/X11/
get fences failed: -1
param: 6, val: 0
get fences failed: -1
param: 6, val: 0
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Backtrace:
0: /usr/X11R6/
1: /usr/X11R6/
2: /usr/X11R6/
3: /usr/lib/
4: /usr/X11R6/bin/X [0x80c7dc7]
5: /usr/X11R6/bin/X [0x80b82ec]
6: [0xb7eef400]
7: /usr/lib/
8: /usr/lib/
9: /usr/lib/
10: /usr/lib/
11: /u...
wilbur (wilburgr) wrote : | #116 |
Friday March 20th 2009 with latest updates.
With the following entry in the xorg.conf file Ubuntu now boots and runs
normally. It hangs with "DRI" "True".
Section "Device"
VendorName "Intel Corporation"
Identifier "82865G Integrated Graphics Controller"
Driver "Intel"
BusID "PCI:0:2:0"
Option "DRI" "False"
EndSection
2009/3/19 Marques Johansson <email address hidden>
> 2.6.3 isn't a solution for me either. UXA locks X (the keyboard and
> display locks during the gnome-session startup - the mouse cursor works
> however). I think the BO aspect of the xserver-
> problems may be out of the way.
>
> This log was generated when I tried EXA with NoLegacy3D:
>
> X.Org X Server 1.6.0
> Release Date: 2009-2-25
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
> Current Operating System: Linux bang 2.6.28-10-generic #33-Ubuntu SMP Tue
> Mar 17 12:27:50 UTC 2009 i686
> Build Date: 07 March 2009 02:18:57AM
> xorg-server 2:1.6.0-0ubuntu1 (<email address hidden>)
> Before reporting problems, check http://
> to make sure that you have the latest version.
> Markers: [ 0.011339] (--) probed, [ 0.011360] (**) from config file,
> [ 0.011375] (==) default setting,
> [ 0.011390] (++) from command line, [ 0.011404] (!!) notice, [
> 0.011418] (II) informational,
> [ 0.011433] (WW) warning, [ 0.011447] (EE) error, [
> 0.011461] (NI) not implemented, [ 0.011476] (??) unknown.
>
> [ 0.011590] (==) Log file: "/var/log/
> 08:37:21 2009
> [ 0.028686] (==) Using config file: "/etc/X11/
> exaCopyDirty: Pending damage region empty!
> error setting MTRR (base = 0xe8000000, size = 0x08000000, type = 1) Invalid
> argument (22)
> ddxSigGiveUp: Closing log
>
>
> This is what I got from UXA without default options. (I can't use UXA with
> DRI off. X still locks with Legacy3D)
>
> X.Org X Server 1.6.0
> Release Date: 2009-2-25
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.24-19-server i686 Ubuntu
> Current Operating System: Linux bang 2.6.28-10-generic #33-Ubuntu SMP Tue
> Mar 17 12:27:50 UTC 2009 i686
> Build Date: 07 March 2009 02:18:57AM
> xorg-server 2:1.6.0-0ubuntu1 (<email address hidden>)
> Before reporting problems, check http://
> to make sure that you have the latest version.
> Markers: [ 0.017446] (--) probed, [ 0.017469] (**) from config file,
> [ 0.017484] (==) default setting,
> [ 0.017498] (++) from command line, [ 0.017513] (!!) notice, [
> 0.017527] (II) informational,
> [ 0.017541] (WW) warning, [ 0.017556] (EE) error, [
> 0.017570] (NI) not implemented, [ 0.017584] (??) unknown.
> [ 0.017701] (==) Log file: "/var/log/
> 08:28:57 2009
> [ 0.034666] (==) Using config file: "/etc/X11/
> get fences failed: -1
> param: 6, val: 0
> get fences failed: -1
> param: 6, val: 0
> [mi] EQ overflowing. The server is probably stuck in an infinite loop.
>
> Backtrace:
> 0: /usr/X11R6/
> 1: ...
wilbur (wilburgr) wrote : | #117 |
Friday March 20th 2009 with latest updates.
With the following entry in the xorg.conf file Ubuntu now boots and runs
normally. It hangs with "DRI" "True" and *Running a video causes a reboot or
kills X*.
Section "Device"
VendorName "Intel Corporation"
Identifier "82865G Integrated Graphics Controller"
Driver "Intel"
BusID "PCI:0:2:0"
Option "DRI" "False"
EndSection
jerrylamos (jerrylamos) wrote : | #118 |
Score! kernel 2.6.28-11-generic with xorg.......intel updates works on i830 on IBM Thinkpad R31. No changes to xorg.conf, just as is upgraded today.
First jaunty that's run without "NoAccel" on the R31!
Kudo's to whoever fixed it!l Hope it stays fixed, I'll use dual boot to keep this jaunty around.
Thanks much, Jerry
p.s. I'll try my i845 next when I swap a display onto it. It was too sluggish with jaunty before.
wilbur (wilburgr) wrote : | #119 |
Try running a video which takes down my i865. Much better screen scrolling
as long as I don't run a video.
Edmond Thiebaud (thiebaude) wrote : | #120 |
wilbur told me to change the option section in xorg.conf to "DRI" "False"
and then i saved it, upgraded to 9.04 and eveything boots just perfect, the
only thing is for some reason i cant uninstall Ubuntu Studio, but thats not
big deal, and also the fonts are too small in ubuntu, but i use xrandr to
set my correct resolution, its only a temp fix, everytime i log in to
ubuntu to use 800x600 i have to do xrandr -s 800x600 -r 85, but thats also
not big problem because i always had to do that in fluxbox.Thanks Wilbur for
that fix for me, i'am not going to touch anything on this system.
On Fri, Mar 20, 2009 at 9:05 PM, wilbur <wilburgr@gI follmail.com> wrote:
> Try running a video which takes down my i865. Much better screen scrolling
> as long as I don't run a video.
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
> (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Edmond Thiebaud (thiebaude) wrote : | #121 |
I have no problem playing video
Rebug (j-de-cuba) wrote : | #122 |
Dell2400Dimensi
Have today march 21 2009 successfully installed Ubuntu Jaunty 9.04 daily build live-cd. Perfect audio/video.
I have missed Ubuntu since 11 September 2008 due to i8xx chipset issue.
Thanks
jerrylamos (jerrylamos) wrote : | #123 |
Video YouTube Leona Lewis "Run" and scrolled while the video was going.
No problem. Video, audio, & scroll all at the same time. Must be time for a new update!
VGA compatible controller: Intel Corporation 82845G/
Linux version 2.6.28-11-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009
Jerry
In freedesktop.org Bugzilla #18974, Gordon Jin (gordon-jin) wrote : | #124 |
(In reply to comment #21)
> Gordon, please would you mind giving us an update on the status of this bug?
I don't have more update. Eric owns this bug.
Edmond Thiebaud (thiebaude) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #125 |
On Sat, Mar 21, 2009 at 2:04 PM, jerrylamos <email address hidden> wrote:
> Video YouTube Leona Lewis "Run" and scrolled while the video was going.
> The only problem besides the small fonts is now i cant log-in with the
> newest kernal, but the older kernal i'am able to log-in.
> No problem. Video, audio, & scroll all at the same time. Must be time
> for a new update!
>
> VGA compatible controller: Intel Corporation 82845G/
> Chipset Integrated Graphics Device (rev 01)
>
> Linux version 2.6.28-11-generic (buildd@rothera) (gcc version 4.3.3
> (Ubuntu 4.3.3-5ubuntu4) ) #36-Ubuntu SMP Fri Mar 20 19:40:40 UTC 2009
>
> Jerry
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
> (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
In freedesktop.org Bugzilla #18974, Yu Yuwei (acevery) wrote : | #126 |
(In reply to comment #22)
> I also suffered from this bug.
> But recently I found out, that it only happened, when there is a
> "Virtual"-option in my Xorg.conf:
> Section "Screen"
> Identifier "Screen0"
> Device "Device0"
> Monitor "LVDS"
> DefaultDepth 24
> SubSection "Display"
> Modes "1280x800_60"
> Virtual 2960 1056
> EndSubSection
> EndSection
>
> When I removed the Virtual-option, everything went fine.
>
> The other day i reinstalled my system (Arch Linux) and installed the newest
> packages from the testing-repository.
> Namely those packages are:
> xf86-video-intel 2.6.99.902-1
> libdrm 2.4.5-2
> mesa 7.3-2
> xorg-server 1.6.0-1
>
> After a few changes in my Xorg.conf I came to these settings:
> Section "Device"
> Identifier "Device0"
> Driver "intel"
> Option "Legacy3D" "true"
> Option "DRI" "true"
> Option "AccelMethod" "uxa"
> Option "ExaNoComposite" "true"
> EndSection
>
> I put the Virtual-section back in - I need my 22" lcd ;)
>
> And what do my eyes see?
> Everything works!
>
> I also tried the latest xf86-video-intel via GIT. Same thing there.
> I installed ioquake3 - and woohoo! 90fps.
>
> Everything's great right now.
>
> Maybe someone could try those Xorg.conf-settings and the latest git-version.
>
> Regards,
> karsten
>
This solution is not workable for me with xf86-video-
javajazz (randister) wrote : | #127 |
- Xorg.0.log.old Edit (46.0 KiB, application/x-trash)
@ubuntu:~$ lspci
00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller
as others above i could only get into kde by setting DRI to false within the device section of xorg.conf.
I boot into the cli and then startx. No kdm. before the DRI fix, it would typically freeze during the splash sequence, though sometimes it would make it to the desktop with mouse moving but otherwise not functioning. No keyboard either.
it is 3/22/09 and i am updated to all the latest jaunty versions of kernel and intel and xorg and libdrm; and still not working for the 865g without a hack.
Anyway! Yes running a video will crash the desktop. Most of the time i end up at the cli (no kdm) with xorg messages there in print to read. the xorg.0.log message says "could not pin xv". so i startx into kde and open mplayer and and go to preferences to set video from xv to gl. then to real player to turn xv off. then to electricsheep screensaver to set it from xv to gl. I control alt backspace and then startx again and yes i can do the electricsheep without crashing the desktop. Oh, by the way, electricsheep uses mplayer to run the sheep.
Those interested, please note: in systemsettings within the desktop icon/desktop effects/advanced tab; I have compositing type set to "xrender". I had to change it from the default "opengl" to get transparent effects in the panel and for konsole and some plasmoids.
Those still interested please also note: I have been running jaunty for months. I have been using the xorg packages from intrepid. Everything on my system is the latest jaunty versions, except xorg. everything has worked "fine" "slow but functional" for months. if interested and AT YOUR OWN risk, just go to packages.ubuntu.com and download the xorgs you need from intrepid. then do "apt-get --purge remove xserver-xorg". now go to directory containg all those xserver-xorg packages and do a "dpkg -i xserver*". i must have gone back and forth with this a number of times. every time the repositories show a new version of xorg-intel i do a full upgrade and crash the desktop. lukily i got my little stash of intrepid xorg to get me back in.
THANKS guys for showing me the way with DRI false. Thanks.
Ivan A. Flores Correa (ifloresenator) wrote : | #128 |
Hello
for Device :
00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02)
bug fixed with next xorg.conf config Video Device:
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "XvMC" "true"
Option "AccelMethod" "UXA"
EndSection
I have acceleration and not have problem with video ... ;-)
THANKS
wilbur (wilburgr) wrote : Re: [Bug 304871] Re: [i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty) | #129 |
Thanks for the input.
With an Intel 82865G my system locks up tight using UXA.
The following works except for some video:
Section "Device"
VendorName "Intel Corporation"
BoardName "Intel 82865G"
Identifier "82865G Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
Option "DRI" "False"
# Option "NoAccel" "True"
EndSection
To run some video the 'NoAccel' line has to be:
Option "NoAccel" "True"
We have to hope that this does get fixed at some point.
2009/3/25 segato <email address hidden>
> Hello
>
> for Device :
>
> 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM
> Integrated Graphics Device (rev 02)
>
> bug fixed with next xorg.conf config Video Device:
>
> Section "Device"
> Identifier "Configured Video Device"
> Driver "intel"
> Option "XvMC" "true"
> Option "AccelMethod" "UXA"
> EndSection
>
> I have acceleration and not have problem with video ... ;-)
>
> THANKS
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
> (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “xserver-
> Status in xserver-
> Status in “xserver-
>
> Bug description:
> Since the change from the 2.4.1 driver to 2.5.1, Jaunty now hangs during
> boot, with "Fatal server error: Couldn't bind memory for BO front buffer"
> shown in the log. So far, this has been seen by two people with i845
> graphics and two with i865.
>
> Also discussed at this forum:
> https:/
>
> [Original Report]
> Binary package hint: xserver-
>
> Hi all,
> This is in jaunty, I get no screens.
>
>
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation 82845G/
> DRAM Controller/Host-Hub Interface [8086:2560] (rev 03)
> 00:02.0 VGA compatible controller [0300]: Intel Corporation
> 82845G/
> (rev 03)
> Subsystem: Intel Corporation 82845G/
> Integrated Graphics Device [8086:2562]
>
>
Stefan Glasenhardt (glasen) wrote : | #130 |
- git-commit : Drop Legacy3D option, only use fixed texture space with non-gem. Edit (3.3 KiB, text/plain)
Hi,
There are two possible solutions for this bug (at least for all 855GM-based hardware owners) :
Add the following line to your Device-Section in the "xorg.conf"-file :
Option "Legacy3d" "false"
With this option i can use EXA an 3D-acceleration an my DELL Latitude D505.
Second option :
Include the following git-commit into the driver version 2.6.3 :
"Drop Legacy3D option, only use fixed texture space with non-gem."
This patch works perfectly with driver version 2.6.3 on my notebook and the "Legacy3D" option is no longer needed.
Ivan A. Flores Correa (ifloresenator) wrote : | #131 |
Hello
with this xorg.conf :
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "XvMC" "true"
Option "AccelMethod" "UXA"
EndSection
I have problem with de VGA output, and this VGA config found use this config :
Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "DRI" "false"
EndSection
I do change this config to use the VGA in my notebook ...
VGA output BUG NOT CLOSED
:'(
Saludos from Chile
Scott Kitterman (kitterman) wrote : | #132 |
Using the 9.04 Beta Live CD it starts on my Intel 865GBF motherboard.
0000:00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) (prog-if 00 [VGA])
Subsystem: Intel Corporation: Unknown device 4246
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Memory at ffa00000 (32-bit, non-prefetchable) [size=512K]
I/O ports at ec00 [size=8]
Bryce Harrington (bryce) wrote : | #133 |
- 116_846g_865g_disable_dri.patch Edit (702 bytes, text/plain)
Hrmph, no word from upstream, no word from the original reporter.
Of the other commenters, some say the issue is fixed. Others (mostly 845G and 865G users) say it's still there but goes away once DRI is disabled.
It is easy enough to force DRI off for all 845G and 865G chips. I've put a patch to do this into my ppa. I would ask that 845 and 865 users please test it and verify it fixes the issue, without requiring setting anything in your xorg.conf. If it does, I can upload it.
If anyone does not think we should do this change, now's the time to speak up, but provide an explanation why.
Bryce Harrington (bryce) wrote : | #134 |
Changed in xserver-xorg-video-intel (Ubuntu Jaunty): | |
status: | Triaged → In Progress |
wilbur (wilburgr) wrote : | #135 |
Intel 82865G user.
Before doing the patch I would like to know what the DRI actually does and
what will be lost by patching it out. I am one of those for whom the problem
is definitely not resolved. Things like flash and video are not working
correctly or not working at all to the point where I am off looking at other
distos.
Option "XvMC" "true" does not seem to help
Option "DRI" "False" has to be false or lockup
Option "NoAccel" "True" has to be true to play videos
makes the system unpleasant to use for other things.
Option "AccelMethod" "UXA" causes lockup EXA seems OK
Option "DPMS" "false" no change noted
Option "Legacy3d" "false" no change noted
So most of the time I run with the 'NoAccel' option commented out but
activate it and restart X if I want to run a video. Some flash will not run,
for example the Dow Jones chart at
http://
in 8.10 and seems to work well in a number of other distros I have tried.
At the moment 9.04 is a crippled OS with the Intel 82865G. I hope it gets
fixed and that we are not left stranded.
Many thanks for the DRI patch I will give it a try and report back.
Julian Lam (julian-lam) wrote : | #136 |
- Output of "lspci -vvnn" Edit (12.0 KiB, text/plain)
Here to report that Stefan Glasenhardt's workaround works perfectly.
I added the line:
Option "Legacy3d" "false"
to xorg.conf, which enabled hardware acceleration, allowing me to get to the desktop WITH compiz. Perfect!
I've attached the requested outputs.
Julian Lam (julian-lam) wrote : | #137 |
javajazz (randister) wrote : | #138 |
VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
am running the latest from the jaunty repositories and still no satisfaction with electricsheep screensaver, that uses mplayer to run an avi. It will only show up in a window and not full screen as it used to do with xorg from intrepid repositories. will not work when running a 2.6.29 kernel either.
but the good news is that all flash and other videos work, I only miss my full screen electricsheep.
I do have to set DRI to false within xorg.conf because otherwise i will never make it to the kde4 desktop. AND I have to set all video apps to not use "xv" because otherwise it will crash the desktop when i run a video. i currently have mplayer set to use "x11". "gl" is too slow.
do i need to buy an nvidea card!!!!!? I will not leave ubuntu!!
wilbur (wilburgr) wrote : | #139 |
March 12, 11:37pm
I installed the update with an interesting result. Now when I run a video it
is exactly the same result as pressing Ctl-Alt-Bksp. Without any warning X
is gone and after a black screen the login screen comes up and then X. So
now running a video is a software X restart. If I can figure out what is the
trigger then it will be posted. Tomorrow I will try changing some of the
Options in xorg.conf.
2009/3/27 Bryce Harrington <email address hidden>
> PPA with this fix:
>
> https:/
>
> ** Changed in: xserver-
> Status: Triaged => In Progress
>
> --
> [i845G] Fatal server error: Couldn't bind memory for BO front buffer
> (Jaunty)
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in X.org xf86-video-intel: Confirmed
> Status in “xserver-
> Status in xserver-
> Status in “xserver-
>
> Bug description:
> Since the change from the 2.4.1 driver to 2.5.1, Jaunty now hangs during
> boot, with "Fatal server error: Couldn't bind memory for BO front buffer"
> shown in the log. So far, this has been seen by two people with i845
> graphics and two with i865.
>
> Also discussed at this forum:
> https:/
>
> [Original Report]
> Binary package hint: xserver-
>
> Hi all,
> This is in jaunty, I get no screens.
>
>
>
> [lspci]
> 00:00.0 Host bridge [0600]: Intel Corporation 82845G/
> DRAM Controller/Host-Hub Interface [8086:2560] (rev 03)
> 00:02.0 VGA compatible controller [0300]: Intel Corporation
> 82845G/
> (rev 03)
> Subsystem: Intel Corporation 82845G/
> Integrated Graphics Device [8086:2562]
>
>
javajazz (randister) wrote : | #140 |
Intel Corporation 82865G Integrated Graphics Controller (rev 02)
the latest xorg upgrade from the jaunty repository now allows me to get into the kde4 desktop without having to set DRI to false. Yipee!
BUT, running mplayer with the "xv" driver, still, will knock me right out of kde4. and "xv" is the only way i can get electricsheep to run full screen. I have to set the driver to "x11" for videos to work. But as stated in previous posts, my electricsheep will only run in a window, not fullscreen, if set to "x11". It will run in fullscreen if I set mplayer to use "xv" driver and i revert to xorg from the intrepid repository.
anyway. congrads. you are half way there.
fix the "xv". please. I want my eye candy fullscreen.
and why is electricshhep not a default option for kde4? I had to hack it in with trial and error making a electricsheep.
wilbur (wilburgr) wrote : | #141 |
There seem to be different problems with Intel 865G video.
One is that DRI has to be disabled with
Option "DRI" "False" in /etc/xorg.conf
or with the patch from Bryce (Thanks)
http://
https:/
Another is the acceleration. To play video (badly)
Option "NoAccel" "True" has to be set.
This setting is not practical for other use and not much good for video
other than it does not crash the system.
There are problems with all sorts of video, flash, mplayer, slide shows to
name three. Some lead to an instant restart of X, a software Ctl-Alt-Bksp,
while others simply do not play at all, cause lock up or display badly.
The system boots to lockup with UXA enabled.
Nothing additional in the logs.
If anyone has any ideas to try or tests to run please post them.
Bryce Harrington (bryce) wrote : | #142 |
Alright, there are just waaaay too many different things going on with this bug.
The original problem which is targeted for jaunty is the fatal server error on 845.
The problem people are having with video, requiring NoAccel to be used is a separate bug. File a new report on that; don't comment further about it here.
From the comments, there are reporters for 845, 855, 865, and other chips, and the symptoms/fixes for each seem to be different.
845: From the last couple comments from 845 users jerrylamos and j-de-cuba it seems the issue on 845 is solved with the latest updates. Other 845 users including the original reporter have not commented further; I guess we have to assume they're not commenting because the issue is gone. So 845 is solved. Great.
855: This chip seems to be in much better shape. Many users find UXA solves the issue. Others not so much. The Legacy3D patch seems necessary for this. However I think we need to handle the 855 bugs separately from the 845 ones. So this needs to go to a different bug report.
865: From comments from randister and kitterman this may now be fixed with latest updates. Otherwise, disabling DRI solves the problem. Video is still broken but as I mentioned, that should be a separate bug.
Fernando Miguel (fernandomiguel) wrote : | #143 |
bryce i just tested todays daily jaunty 32bits on an Dell GX270 with Intel 865 and it failed to boot the installer.
Only using Safe Graphics and having VESA on xorg.cong
Fernando Miguel (fernandomiguel) wrote : | #144 |
FYI adding DRI false seems to work
Bryce Harrington (bryce) wrote : | #145 |
I've unduped the non-845 bugs from this one. Non-845 users should unsub from this one and sub to the appropriate one:
bug 304871 - [i845] couldn't bind memory for BO backbuffer on 845
bug 322646 - [i855] couldn't bind memory for BO backbuffer on 855
bug 317457 - [i865] freeze, works only with dri false
bug 328528 - [i865] UXA locks up system (UXA bug)
If your issue doesn't fit into one of the above bugs, file a NEW one.
description: | updated |
Bryce Harrington (bryce) wrote : | #146 |
As per the last two comments from the two most recent 845 reporters, the issue on i845G chips has been resolved with latest updates as of 2009-03-21.
Please do not reopen this bug unless you have i845 graphics and see the exact error message "Couldn't bind memory for BO front buffer".
Changed in xserver-xorg-video-intel (Ubuntu Jaunty): | |
status: | In Progress → Fix Released |
Julian Lam (julian-lam) wrote : | #147 |
Thank you Bryce, et al.! Today's released fix worked perfectly. I can finally empty my xorg.conf file :)
Daniël H. (daan-is-here) wrote : | #148 |
Well, after this update the scrolling and window management behavior sucks.
Daniël H. (daan-is-here) wrote : | #149 |
I'm sorry, after resetting xorg.conf this problem was resolved. Strange, because I didn't ever changed it manually. Maybe because I did a upgrade from Intrepid?
Étienne BERSAC (bersace) wrote : | #150 |
Hi,
I confirm the bug is fixed on MacBook White 4,1 (GMA 965)
Regards,
Étienne.
--
E Ultreïa !
Feistybird (bryanjen-tw) wrote : | #151 |
- broken-image.png.tar.gz Edit (348.3 KiB, application/x-tar)
Worked but get broken picture on some applications such as java applets & firefox. See images attached.
-PCI Devices-
VGA compatible controller : Intel Corporation 82845G/
jerrylamos (jerrylamos) wrote : | #152 |
On Release Candidate, launchpad bug #304871 is back in spades. Integrated Intel graphics i845 boots to black screen on CD Live and install on Ubuntu and Xubuntu.
I had to boot CD Live, edit command line, remove quiet splash, add single to get recovery mode. Then in root prompt nano /etc/X11/xorg.conf to add Option "NoAccel" just after "Configured Video Device".
Same thing on install.
Update Manager lists 49 updates already, NONE of them in xorg to fix this bug again.
Performance is sluggish on scroll etc to say the least.
What happened? It was fine on Beta?
Jerry
jerrylamos (jerrylamos) wrote : | #153 |
Today's updates, April 17, did fix the problem for the installed Xubuntu. Will try Ubuntu next. There weren't any xorg updates but there was a kernel update.
The release candidate (as in Daily Build 20090414) boots to black screen unless I do "NoAccel".
Thanks, someone, hope the CD Live gets fixed too.
Jerry
Edmond Thiebaud (thiebaude) wrote : | #154 |
in 9.04 after login x freezes and then the OS is unusable on the Intel i815 graphics chip,so went back to 8.10 for now, until a fix is found.
HeWhoE (hewhoe) wrote : | #155 |
On my 82845G/
(EE) intel(0): Failed to init memory manager
In freedesktop.org Bugzilla #18974, Carl Worth (cworth) wrote : | #156 |
(In reply to comment #15)
> _fence_
I just replicated this part of the bug at least, (with all the latest userspace, such as xf86-video-intel 2.7.99 from git), and a non-GEM Debian kernel (2.6.26-2-686).
Eric suggests that when the userspace opens the drm and finds that it's non-GEM it should just close it. I'll attempt that here and report back.
-Carl
In freedesktop.org Bugzilla #18974, Carl Worth (cworth) wrote : | #157 |
(In reply to comment #25)
> (In reply to comment #15)
>
> > _fence_
>
> I just replicated this part of the bug at least, (with all the latest
> userspace, such as xf86-video-intel 2.7.99 from git), and a non-GEM Debian
> kernel (2.6.26-2-686).
>
> Eric suggests that when the userspace opens the drm and finds that it's non-GEM
> it should just close it. I'll attempt that here and report back.
Eric had some half-finished patches for this which I finished and pushed (see below).
With these patches applied, the latest driver from git now runs just fine on the non-GEM Debian kernel (2.6.26-2-686). I'd be very interested if other people that have experienced the bugs reported here could try using the latest driver and report back whether the bug is fixed.
I'll also consider cherry-picking the relevant commits here to the 2.7 branch for an upcoming 2.7.2 release.
-Carl
In freedesktop.org Bugzilla #18974, Carl Worth (cworth) wrote : | #158 |
(In reply to comment #26)
> Eric had some half-finished patches for this which I finished and pushed (see
> below).
Here's the "see below" part I forgot to add with the last comment.
-Carl
commit 8e942b70cb9a784
Author: Carl Worth <email address hidden>
Date: Thu May 21 13:12:52 2009 -0700
Revert "Rely on BO pixmaps being present in acceleration paths."
This reverts commit 4653a7db622ad54
Eric was getting a little too ambitious about our brave, new world.
We do still want the driver to work with old, non-GEM kernels
after all.
commit 1a039f4371bec45
Author: Eric Anholt <email address hidden>
Date: Mon Apr 27 17:45:02 2009 -0700
Fold GEM detection into DRM master open.
We don't have anything to do with the DRM unless it's GEM-enabled, unless
we were to support GEM-but-not-DRI2, which doesn't seem useful.
Compilation fixes by Carl Worth <email address hidden>
commit a04a51c9bb60664
Author: Eric Anholt <email address hidden>
Date: Mon Apr 27 17:29:36 2009 -0700
Open the DRM and keep the handle throughout server startup to finish.
This will let us configure the server from start to finish with the
most pertinent information available (KMS vs UMS, DRI2 vs non-DRI). Also,
we now close the DRI2 fd at terminate, which we didn't before.
This duplicates some code from DRI1 for getting a master FD like I'd done in
DRI2, but given that we weren't loading DRI1 ourselves, this is also a
bogosity cleanup, and avoids allocating the extra DRI1 private.
In freedesktop.org Bugzilla #18974, Gordon Jin (gordon-jin) wrote : | #159 |
Could any of the reporters confirm this problem still exists with the latest xf86-video-intel driver and a KMS kernel? If so, I'll increase the priority and target for Q2 release (2.8).
In freedesktop.org Bugzilla #18974, Bugzilla-dolphinling (bugzilla-dolphinling) wrote : | #160 |
I used to see this with a 2.5-era xf86-video-intel and now I do not with current git stuff and KMS.
In fact, I get an explicit success message:
(II) intel(0): BO memory allocation layout:
(II) intel(0): 0x00000000: start of memory manager
(II) intel(0): 0x03800000-
(II) intel(0): 0x03000000-
(II) intel(0): 0x07fff000: end of memory manager
This is on 845.
In freedesktop.org Bugzilla #18974, Gordon Jin (gordon-jin) wrote : | #161 |
So I assume it has been fixed.
If anyone still see this with a new driver (>=2.6.99.901) and KMS kernel, please reopen.
In freedesktop.org Bugzilla #18974, Gordon Jin (gordon-jin) wrote : | #162 |
(In reply to comment #30)
> So I assume it has been fixed.
> If anyone still see this with a new driver (>=2.6.99.901)
typo. I meant 2.7.99.901.
Changed in xserver-xorg-video-intel: | |
status: | Confirmed → Fix Released |
Dan Astoorian (djast-ecf) wrote : | #163 |
xserver-
(**) intel(0): DRI is disabled because it fails to run without freezing on i810 and i865G chips. (See LP 304871)
i.e., the package still includes 116_8xx_
My chipset is reported as "Intel Corporation 82865G Integrated Graphics Controller rev 2".
If the problem has been fixed, the patch should presumably be removed; if there are still problems not related to the fix associated with this bug, the message produced by the patch should be updated to refer to a more appropriate bug number.
tags: | added: iso-testing |
Changed in xserver-xorg-video-intel (Ubuntu): | |
assignee: | Bryce Harrington (bryceharrington) → nobody |
Changed in xserver-xorg-video-intel: | |
importance: | Unknown → Critical |
Changed in xserver-xorg-video-intel: | |
importance: | Critical → Unknown |
Changed in xserver-xorg-video-intel: | |
importance: | Unknown → Critical |
Changed in xserver-xorg-video-intel (Fedora): | |
importance: | Unknown → High |
Created attachment 316355
Xorg.0.log with 2.4.2-7 and XAA
Description of problem:
X fails to start and the Xorg.0.log shows:
(EE) intel(0): Failed to pin front buffer: Cannot allocate memory
Fatal server error:
Couldn't bind memory for BO front buffer
Note that my xorg.conf is set to use XAA instead of EXA because the latter causes the computer to completely hang when X tries to start. In dmesg, the following error appears repeatedly:
mtrr: type mismatch for d0000000,10000000 old: write-back new: write-combining gem_object_ bind_to_ gtt] *ERROR* GTT full, but LRU list empty gem_object_ pin] *ERROR* Failure to bind: -12<4
[drm:i915_
[drm:i915_
Version-Release number of selected component (if applicable):
xorg-x11- drv-i810- 2.4.2-7
I was able to successfully use XAA with xorg-x11- drv-i810- 2.4.2-1, but I have not been able to use either XAA or EXA in any version since.
Please let me know if any other output would be helpful.