Ubuntu
xserver-xorg-video-intel package

Eschalon doesn't start on Intrepid with Intel graphics

Bug #321401 reported by Lele83x on 2009-01-26

4

Affects		Status	Importance	Assigned to	Milestone
	mesa (Ubuntu)	Fix Released	Undecided	Unassigned
	xserver-xorg-video-intel (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Eschalon Book I is a native Linux game with fairly low system requirements.
The game doesn't start on Intrepid with Intel graphics (945) giving this message:

USER@USER-laptop:~/eschalon_book_1$ ./eschalon_book_1
eschalon_book_1: ../common/dri_bufmgr_fake.c:576: dri_bufmgr_fake_contended_lock_take: Assertion `((&bufmgr_fake->on_hardware)->next == (&bufmgr_fake->on_hardware))' failed.
Aborted

This bug persists on every computer with similar intel graphic card, running Ubuntu 8.10.
With other video cards the game runs fine.
Specifically my laptop is a Thinkpad X60s with Intel 945 video card.

VARIOUS INFORMATIONS:

xserver-xorg-video-intel:
Installed: 2:2.4.1-1ubuntu10.3

*-display:0 UNCLAIMED
       description: VGA compatible controller
       product: Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 03
       width: 32 bits
       clock: 33MHz
       capabilities: msi pm bus_master cap_list
       configuration: latency=0
*-display:1 UNCLAIMED
       description: Display controller
       product: Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2.1
       bus info: pci@0000:00:02.1
       version: 03
       width: 32 bits
       clock: 33MHz
       capabilities: pm cap_list
       configuration: latency=0

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-01-29:

#1

Thank you for reporting this bug and helping making Ubuntu better. The Ubuntu developers are mainly concentrating on fixing bugs for the upcoming Jaunty release. We would therefore ask you test using a recent development of Jaunty. It seems to me that this bug is in mesa and similar to bug 296020. Mesa has had some significant upgrades since Intrepid, so there is a good chance it's already fixed. Could you test using a recent daily live from http://cdimage.ubuntu.com/daily-live/ ? (there is also alpha-3, and the bug may have been fixed already there, but there have been updates since then).

If the bug still exist in Jaunty, we will need the following information (preferably from Jaunty):
- the output `lspci -vvnn`
- /var/log/Xorg.0.log taken after you tried to run the program

Changed in mesa:
status:	New → Incomplete

Revision history for this message

Lele83x (lele83x) wrote on 2009-01-29:

#2

I've tried the daily build of Jaunty on a usb and the game actually runs.

I was running it live, not installed, and probably that's one of the reasons for the game to run so slow, it was unplayable and run only in windowed mode, if I selected fullscreen I just got a black screen.

I forgot to extract xorg log and I'll do it as soon as I can.

Thanks for the attention

Revision history for this message

Lele83x (lele83x) wrote on 2009-01-29:

#3

Xorg.0.log.1 Edit (23.9 KiB, text/plain)

I run the live of jaunty again and I extracted the logs: the .1 is the one right after I run the game in windowed mode the .2 is the one after I run the game in full screen and I had to killall again. the last file is the lspci log.

thanks again

Revision history for this message

Lele83x (lele83x) wrote on 2009-01-29:

#4

Xorg.0.log.2 Edit (29.7 KiB, text/plain)

Revision history for this message

Lele83x (lele83x) wrote on 2009-01-29:

#5

lspci Edit (14.2 KiB, text/plain)

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-02-02:

#6

Thank you for posting all the necessary information. To me it looks like the original bug has been solved in Jaunty. The performance problem and black fullscreen issue is quite different. My suggestion would be to close this bug, and possibly open a new one for the new issue(s). Then there would be a clean bug report for the issue with Jaunty, and hopefully get it solved before the Jaunty release. Alternatively, you may update the title and description, so that it describes the Jaunty problem.

I think this makes the probability higher to get this fixed in Jaunty.

Revision history for this message

Geir Ove Myhr (gomyhr) wrote on 2009-02-06:

#7

I'm closing this bug, since this particular mesa problem no longer exist in Jaunty. The performance problems for Jaunty are reported in bug 324292.

Changed in mesa:
status:	Incomplete → Fix Released
Changed in xserver-xorg-video-intel:
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.