Bug 37236 - [i965g] failed to create pipe_screen
Summary: [i965g] failed to create pipe_screen
Status: RESOLVED WONTFIX
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-15 13:30 UTC by Blaž Tomažič
Modified: 2011-05-16 08:40 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg log (29.34 KB, application/x-trash)
2011-05-15 13:30 UTC, Blaž Tomažič
Details

Description Blaž Tomažič 2011-05-15 13:30:53 UTC
Created attachment 46747 [details]
xorg log

i965g driver fails to create pipe_screen and falls back to software rendering. It tries to create it with radeon chip id instead of intel chip id. 'startx' outputs the following errors:

i965_drm_winsys_screen_create
brw_screen_create: unknown pci id 0x68e0, cannot create screen
dri_init_screen_helper: failed to create pipe_screen


Intel graphic controller is on cpu, core i5-460M arrandale, PCI:0:2:0, 0x0046.
radeon graphic controller is Mobility Radeon HD 5000 Series, PCI:1:0:0, 0x68e0.
Mesa and DRI drivers were built from git bd5b7a6f7113da38a2c1f07a4a71e9993666a567 (master from today).


- startx output:

X.Org X Server 1.10.1
Release Date: 2011-04-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.38-ARCH x86_64 
Current Operating System: Linux laptop-blazt 2.6.38-ARCH #1 SMP PREEMPT Fri May 13 09:24:47 CEST 2011 x86_64
Kernel command line: root=/dev/disk/by-uuid/a1b0c143-ebaa-4441-8902-682eee8bc5bc resume=/dev/disk/by-uuid/ff87644d-e6ee-489f-a7af-62b4559fe5a6 init=/bin/systemd ro
Build Date: 16 April 2011  12:02:01PM
 
Current version of pixman: 0.20.2
	Before reporting problems, check http://wiki.x.org
	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/Xorg.0.log", Time: Sun May 15 20:44:12 2011
(==) Using config directory: "/etc/X11/xorg.conf.d"
(EE) Failed to load module "fbdev" (module does not exist, 0)
i965_drm_winsys_screen_create
brw_screen_create: unknown pci id 0x68e0, cannot create screen
dri_init_screen_helper: failed to create pipe_screen
(EE) AIGLX error: Calling driver entry point failed
(EE) AIGLX: reverting to software rendering


- lspci -nn output:

00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 02)
00:01.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express x16 Root Port [8086:0045] (rev 02)
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02)
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 05)
00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller [8086:3b09] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller [8086:3b29] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 05)
00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 05)
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Manhattan [Mobility Radeon HD 5000 Series] [1002:68e0]
01:00.1 Audio device [0403]: ATI Technologies Inc Manhattan HDMI Audio [Mobility Radeon HD 5000 Series] [1002:aa68]
02:00.0 Network controller [0280]: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 03)
7f:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 02)
7f:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 02)
7f:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 02)
7f:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 02)
7f:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 02)
7f:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 02)
Comment 1 Tobias Jakobi 2011-05-16 05:56:03 UTC
AFAIK the i965 gallium driver is completly unsupported.
Comment 2 Jose Fonseca 2011-05-16 08:31:01 UTC
(In reply to comment #1)
> AFAIK the i965 gallium driver is completly unsupported.

That's right.

I'm not sure if we should make this more explicit or simply disable/remove the driver. The latest person to do a i965g specific change was Dave Airlie on Jan.
Comment 3 Tobias Jakobi 2011-05-16 08:40:34 UTC
I would vote at least for a big warning when enabling i965g in configure.

Removing the complete driver probably isn't a good idea. IIRC the i915 gallium driver was also unmaintained a long time and now someone (I think it was Daniel Vetter) is doing a lot of work on that one. Maybe something like that will happen for i965g too.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.