Opened 5 years ago

Last modified 3 years ago

#15241 closed bug

Intel HD Graphics Ironlake driver issue — at Version 8

Reported by: cocobean Owned by: kallisti5
Priority: normal Milestone: R1/beta3
Component: Drivers/Graphics/intel_extreme/ironlake Version: R1/Development
Keywords: Cc: ttcoder
Blocked By: Blocking:
Platform: All

Description (last modified by cocobean)

UPDATED: Ensure all IronLake GPUs fallback to VESA graphics driver.

Usually blacks out screen before Haiku logo boot splash screen appears or before the desktop appears. Normally, desktop screen won't appear unless we use the fail-safe (VESA) graphics driver.

NOTE: Can change screen resolutions under preflet up to 1920x1440 under VESA driver (mentioned in preflet)

Intel HD Graphics (Ironlake/Westmere: Clarkdale/Arrandale), 5th gen. Outputs: VGA, DVI Max res. 2560x1600 Monitor max res: 1280x1024 CPU: Intel i3 550

Change History (13)

by cocobean, 5 years ago

Attachment: listdev_cocobean_x86_64 added

listdev info for Intel HD Ironlake graphics

by cocobean, 5 years ago

Attachment: listimage_cocobean_x86_64 added

listimage info for Intel HD Ironlake graphics

by cocobean, 5 years ago

syslog intel_extreme driver info for Intel HD Ironlake graphics - hrev53353 x86_64

comment:1 by cocobean, 5 years ago

Intel Corporation Core Processor Integrated Graphics Controller (rev 18) 256M]
Outputs: VGA, DVI-D (dual link, digital)
Max. resolution output: 2560x1600x32 @ 60hz
Mesa DRI Intel(R) Ironlake Desktop x86/MMX/SSE2 (0x42)
Video memory: 1536MB
Unified memory: yes
 *-display                 
       description: VGA compatible controller
       product: Core Processor Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 18
       width: 64 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:26 memory:f7800000-f7bfffff memory:e0000000-efffffff ioport:dc00(size=8) memory:c0000-dffff

Comparing xf86-video-intel 2.99.917:

**Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192**
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 880mm x 490mm
   1920x1080     60.00*+
   1680x1050     59.95  
   1440x900      59.89  
   1360x768      60.02  
   1024x768      60.00  
   800x600       60.32  
   640x480       59.94  
   720x400       70.08  
HDMI-1 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)

Intel VGA output->VGA: works (retested with 1080p monitor)

Main issues: Either I can get past the Haiku logo boot splash screen and it fails to a black screen during screen init, or it just fails directly after I exit the Haiku boot loader menu. Sometimes, I don't get the Haiku logo splash screen at all until it fails to black screen.

With effort, I can get it to load with the VESA driver in which I can modify screen resolutions up to 1920x1440 (I also see this in the boot menu for modifying default screen mode settings).

NOTE: Setting fail-safe driver (true) and using 1024x768x32 @60hz default. Rebooted. This works as a workaround. Screen preflet shows monitor info, monitor dpi, and VESA driver (VESA) in left window pane. Resolutions changeable (when applied) from 640x480 to 1920x1400.

VESA driver/Intel IronLake Graphics reboot test: Rebooting at >1024x768 resolutions seems to crash during boot. Staying at <=1024x768 resolutions seems to boot reliably on Haiku.

Now that the output works reliably through the Intel video VGA output, we can isolate the intel_extreme driver issues better.

NOTE: The intel_extreme driver modeline PLL clock info seems off. See working modeline xrandr output for comparison.

intel_extreme:

KERN: intel_extreme: compute_dpll_g4x: best MHz: 109 (error: 0.116997)
KERN: intel_extreme: _IlkTrain: FDI train 1 failure!

xf86-video-intel:

1920x1080 (0x47) 148.500MHz +HSync +VSync *current +preferred
h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
Last edited 5 years ago by cocobean (previous) (diff)

by cocobean, 5 years ago

Intel IronLake Graphics - xrandr dump

by cocobean, 5 years ago

Haiku VESA driver screen preflet info - hrev53365 x86_64

comment:2 by pulkomandy, 5 years ago

Component: Drivers/Graphics/intel_extremeDrivers/Graphics/intel_extreme/ironlake

comment:3 by cocobean, 5 years ago

Tested hrev53556 x86_gcc2.

  1. Fail point right after:
    Intel extreme: Found EDID information!!
    (Detailed monitor info appears)
    Post-install script: sshd_keymaker.sh
    Size: 36 cm x 29 cm
    
  2. Then, display screen inits to black screen. Fails at point normally where Haiku logo splash screen would appear.

NOTE: I didn't get the crtc info. Also, I get the 'h:' info, but not the 'v:' info after the clock info. Normally, I get the 'h:', 'v:', Maximum pixel clock info, H/V Freq ranges, and crtc info. Also, the full serial number of the active monitor (last four digits appear here).

If the intel_extreme driver can mimic/baseline the VESA driver moreso, this may/should solve the problem as the VESA driver works as expected with this graphics chip.

comment:4 by pulkomandy, 5 years ago

Please include an updated syslog booting with the driver enabled.

comment:5 by cocobean, 5 years ago

LiveCD session: I only have recorded video session and screenshots from the online syslog debugger.

comment:6 by cocobean, 5 years ago

You can close this ticket. I remember seeing that this driver was not intended for the Intel HD series. Possible quick fix is to default all Intel HD graphic chips (Gen 5 and higher) to the VESA driver (i.e. removing them from the intel_extreme driver).

comment:7 by pulkomandy, 5 years ago

Then let's not close the ticket until that is done.

comment:8 by cocobean, 5 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.