Launchpad has imported 46 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=461829.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://hel
** Changed in: xserver-xorg-video-intel
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/304871
Title:
[i845G] Fatal server error: Couldn't bind memory for BO front b
** Changed in: xserver-xorg-video-intel
Importance: Critical => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/304871
Title:
[i845G] Fatal server error: Couldn't bind memory for BO front b
** Changed in: xserver-xorg-video-intel (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) => (unassigned)
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of
** Tags added: iso-testing
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
xserver-xorg-video-intel (2:2.6.3-0ubuntu9.3) for me is still reporting
this in Xorg.0.log:
(**) 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_disable_dri.patch.
My chipset is reported as "Inte
** Changed in: xserver-xorg-video-intel
Status: Confirmed => Fix Released
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
On my 82845G/GL[Brookdale-G]/GE chipset, with the latest Jaunty updates
as of April 20, I get the following error after I start X.
(EE) intel(0): Failed to init memory manager
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
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.
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification
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 fi
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.
Worked but get broken picture on some applications such as java applets
& firefox. See images attached.
-PCI Devices-
VGA compatible controller : Intel Corporation
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device
** Attachment added: "broken-image.png.tar.gz"
http
Hi,
I confirm the bug is fixed on MacBook White 4,1 (GMA 965)
Regards,
Étienne.
--
E Ultreïa !
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, whi
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?
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received thi
Well, after this update the scrolling and window management behavior
sucks.
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Thank you Bryce, et al.! Today's released fix worked perfectly. I can
finally empty my xorg.conf file :)
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bu
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
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 d
FYI adding DRI false seems to work
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
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
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You re
Alright, there are just wy 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
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://launchpadlibrarian.net/24434513/116_846g_865g_disable_dri.patch
https://bugs.launchpad.net/bugs/304871.
Another is
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" i
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 f
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
** Attachment added: "My xorg.conf... commented out sections were a fix which,
while working, wouldn't allow compiz to run. Remaining output fixes issue to my
satisfaction!"
http://launchpadlibrarian.net/24437003/xorg.conf
--
[i845G] Fatal server error: Couldn't bind memory for BO front buf
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.
** Attachment added: "Output of "lspci
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
PPA with this fix:
https://edge.launchpad.net/%7Ebryceharrington/+archive/ppa/+sourcepub/535882/+listing-archive-extra
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Status: Triaged => In Progress
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
ht
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 t
Using the 9.04 Beta Live CD it starts on my Intel 865GBF motherboard.
: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, laten
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"
Ide
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 :
Inc
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"int
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 "
@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
Controlle
On Sat, Mar 21, 2009 at 2:04 PM, jerrylamos
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 al
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/GL[Brookdale-G]/GE
Chipset Integrated Graphics Device (rev 01)
Linux version 2.6.2
Dell2400Dimension-Intel 82845G/GL/ICH4
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
--
[i845G] Fatal server error: Couldn't bind memory for BO front buff
I have no problem playing video
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
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
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://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
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 a
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 Graph
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"
BusI
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-xorg-video-intel
problems may be out of the way.
This log was generated when I tried EXA with NoLegacy3D:
X.
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 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
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"
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://bugs.launchpad.net/bugs/304871
You received this bug notification beca
O.K., downloaded
xf86-video-intel-2.6.3
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
--
[i845G] Fatal server error: Couldn't bind memory for BO f
You can test the latest intel (from git) driver and other stuff from the
"PPA for xorg crack pushers" https://launchpad.net/~xorg-
edgers/+archive/ppa and the latest kernel from
https://wiki.ubuntu.com/KernelTeam/KnowledgeBase
I'm using this right now with linux 2.6.29 rc7 and everything seems
sta
There is a fix for this issue in the newest driver-version :
http://cgit.freedesktop.org/xorg/driver/xf86-video-
intel/commit/?id=73db44e7ac524e84e5f0fda2d60069a9e954ad1b
"Drop Legacy3D option, only use fixed texture space with non-gem."
Together with two other git-commits (see Bug #316588) back
Marques: seems to work with both.
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
Nolari, with Legacy3d false, does it work in AccelMethod UXA, EXA, or
both?
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
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.
--
[i845G] Fatal s
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 !
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpa
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 accelmeth
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
wrote:
> I only get the message "Fatal server error: Couldn't bi
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,
espe
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
req
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 wrote:
> I can confirm my Intel i815 integrated graphics
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.0
On Fri, Jan 30, 2009 at 2:48 AM, Bryce Harrington
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-020629rc6-generic #020629rc6 SMP Mon F
> 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
upstr
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
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 eas
Bryce, I assume this model worked with XAA? Is it possible to switch
between XAA and EXA on a per-model basis?
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubu
> 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. ;-)
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because yo
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Assignee: (unassigned) => Bryce Harrington (bryceharrington)
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a me
** Tags added: uxa
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
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. An
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.
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/GL[Brookdale-G]/GE Chipset Integrated Graphics
Device (rev 01)
Jaunty uname -a
linux 2.6.28-7-gener
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 Integrate
Added dmesg and Xorg.0.log using UXA, and screenshots showing corruption
with EXA and UXA. Also added findings on the wiki.
** Attachment added: "screenshots, logs, exa, uxa on 865g"
http://launchpadlibrarian.net/22555943/screenshots_logs_865g_exa-uxa.tar.gz
--
[i845G] Fatal server error: Cou
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
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/22550116/Xorg.0.log
--
[i845G] Fatal server er
On Tue, Feb 10, 2009 at 10:20 PM, Bryce Harrington
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://wiki.ubuntu.com/X/UxaTesting
>
> The reason I ask is t
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.
--
[i845G] Fata
@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://wiki.ubuntu.com/X/Reporting . Thanks!
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/b
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://wiki.ubuntu.com/X/UxaTesting
The reason I ask is that there have been just two 8xx users reporting
there (both indicatin
I came here seeing a warning about Intel under
http://www.ubuntu.com/testing/jaunty/alpha4#Known%20Issues but I realise that
my problem (above) has little to do with this bug. (I do not get "Fatal server
error: Couldn't bind memory for BO front buffer".) Should I file this as
another bug?
I kee
Confirmed here on Dell Dimension 4500s
This xorg.conf, with 16 bit and no acel worked at a temp fix
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/304871/comments/27
put very poor refresh rate/fps
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (
and the Xorg log... sorry i couldn't tell how to attach two log files in
one post.
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/22444158/Xorg.0.log.old
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
Yo
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"
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-
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 di
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.
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https:/
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.
--
[i845G] Fatal server error: Couldn't bind memory
I have tested Kubuntu Jaunty amd64 Desktop from 03-feb-2009
http://cdimage.ubuntu.com/kubuntu/daily-live/20090203/jaunty-desktop-
amd64.iso with 82865G. Using the live CD I could start X and use KDE
with some graphics corruptions and Kwin compositor reported 100 FPS,
with Intrepid KDE 4.2 I get on
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- FastB
Using the following hardware:
00:02.0 VGA compatible controller: Intel Corporation
82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
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
rebo
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 workin
To confirm, Option "AccelMethod" "UXA" worked for me on a Intel
Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics
Controller.
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notificati
** Changed in: xserver-xorg-video-intel (Ubuntu Jaunty)
Status: Incomplete => Triaged
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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]
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notific
I have also tried Marques Johansson method and that works and seems
better than just disabling all acceleration.
--
[i845G] Fatal server error: Couldn't bind memory for BO front buffer (Jaunty)
https://bugs.launchpad.net/bugs/304871
You received this bug notification because you are a member of U
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
** Attachment added: "Xorg.0.log"
http://launc
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 wit
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"
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.
--
[i845G] Fatal server error: Couldn't
1 - 100 of 126 matches
Mail list logo
