Bug 107452 - New intel driver does not support i810/i815 GPU Full HD
Summary: New intel driver does not support i810/i815 GPU Full HD
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Chris Wilson
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2018-08-02 08:16 UTC by pablocool
Modified: 2019-11-27 13:49 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Gentoo and Ubuntu9.10 Xorg.0.log (13.34 KB, application/zip)
2018-08-02 08:16 UTC, pablocool
no flags Details
Gentoo Xorg.0.log (42.30 KB, text/plain)
2018-08-03 09:19 UTC, pablocool
no flags Details

Description pablocool 2018-08-02 08:16:08 UTC
Created attachment 140933 [details]
Gentoo and Ubuntu9.10 Xorg.0.log


I decided to run gentoo on my old Pentium III based HP IPAQ Desktop. It has xf86-video-intel ver. 2.99.917_p20180214. There is no possibility to run X in 1920x1080. Maximum is what I gained with tweaks of xorg.conf is 1600x900.

I recall I was using this machine with Ubuntu 9.10 with 1920x1080 just after install without xorg.conf. 

What is important to mention this new intel driver tries to load wrong module i915 instead i810. When I manually load i810 then i915 is not loaded. But this has no impact on resolution.

Using or not i810fb also does not change anything. But what is important I was able to setup 1920x1080 on console using this FB module.

I also manually copied all xorg related/intel binaries and libraries from Ubuntu 9.10 to gentoo and was able to run 1920x1080. Mouse and keyboard was not working because Ubuntu uses depreciated HAL. Anyway it confirms newer intel driver has broken support for old i810/i815 GPUs.

Newer Ubuntu > 10 does not support this GPU anymore. Screen becomes black.

Is it possible to run this GPU on new intel driver with 1920x1080 resolution with some kind of configuration tweak?

See attached Xorg.0.log from both systems.
Comment 1 Chris Wilson 2018-08-02 08:26:37 UTC
Not the ddx but the underlying infrastructure.

It failed to read the EDID, hence not showing the correct modes:
[   415.988] (II) intel(0): VESA VBE DDC read failed 

Memory allocation failed:
[   416.116] (II) intel(0): xf86BindGARTMemory: bind key 2 at 0x00000000 (pgoffset 0) 
[   416.118] (WW) intel(0): xf86AllocateGARTMemory: allocation of 1024 pages failed 
   (Cannot allocate memory) 
[   416.118] (II) intel(0): No physical memory available for 4194304 bytes of DCACHE 
[   416.118] (II) intel(0): xf86BindGARTMemory: bind key 3 at 0x01800000 (pgoffset 6144) 
[   416.119] (II) intel(0): Allocated of 4096 bytes for HW cursor 
[   416.119] (II) intel(0): xf86BindGARTMemory: bind key 4 at 0x01801000 (pgoffset 6145) 
[   416.119] (II) intel(0): Allocated of 16384 bytes for ARGB HW cursor 
[   416.119] (II) intel(0): Adding 768 scanlines for pixmap caching 
[   416.119] (II) intel(0): Allocated Scratch Memory 
[   416.389] (WW) intel(0): Direct rendering disabled 

And no xaa:
[   415.932] (EE) Failed to load /usr/lib/xorg/modules/libxaa.so: /usr/lib/xorg/modules/libxaa.so: undefined symbol: miZeroLineScreenKey
Comment 2 pablocool 2018-08-02 08:40:16 UTC
Sorry for libxaa.so error on gentoo
[   415.932] (EE) Failed to load /usr/lib/xorg/modules/libxaa.so: /usr/lib/xorg/modules/libxaa.so: undefined symbol: miZeroLineScreenKey

I forgot I copied it from ubuntu to gentoo. It was also missing natively on gentoo aS I get to know intel driver stopped support for XAA some day. I even found commit somewhere on internet. 

I will try with other monitor and back with clean Xorg.0.log from gentoo system. Thanks for help
Comment 3 pablocool 2018-08-03 09:19:21 UTC
Created attachment 140949 [details]
Gentoo Xorg.0.log

Hello Please check this new Xorg.0.log from gentoo. No bin/libs from ubuntu, no xorg.conf.
Comment 4 Martin Peres 2019-11-27 13:49:53 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-intel/issues/157.

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.