Opened 5 years ago

Closed 3 years ago

Last modified 3 years ago

#15350 closed bug (fixed)

Black screen and system freeze with 8086:0412 (Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller)

Reported by: X512 Owned by: pulkomandy
Priority: normal Milestone: R1/beta3
Component: Drivers/Graphics/intel_extreme/haswell Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by X512)

This is hrev53481, 32 bit, gcc2hybrid.

Display turns off when kernel finish loading. ACPI shutdown button has no effect and SSH client can't connect. VESA is working without any problems, native resolution is avalible.

listdev output:

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 8086: Intel Corporation
  device 0412: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller

Attachments (1)

previous_syslog (160.3 KB ) - added by X512 4 years ago.
syslog

Download all attachments as: .zip

Change History (15)

comment:1 by X512, 5 years ago

Description: modified (diff)

comment:2 by diver, 5 years ago

Component: Drivers/GraphicsDrivers/Graphics/intel_extreme
Owner: changed from nobody to kallisti5

comment:3 by pulkomandy, 4 years ago

Please include a syslog.

comment:4 by X512, 4 years ago

It is not possible to shutdown cleanly and syslog are not saved. I can take syslog only when failsafe video driver is enabled in boot settings.

Problem looks like similar to #14643. In comment https://dev.haiku-os.org/ticket/14643#comment:1 same hardware id is mentioned.

comment:5 by X512, 4 years ago

Display is now working in hrev53618.

comment:6 by X512, 4 years ago

Display is working, but display shut down after rocket icon fo about 5 seconds before desktop appear.

Version 0, edited 4 years ago by X512 (next)

by X512, 4 years ago

Attachment: previous_syslog added

syslog

comment:7 by pulkomandy, 4 years ago

This happens because the video timings between VESA and the intel driver can be different, so the videocard has to be reinitialized. But we can try to make it faster, maybe?

comment:8 by modeenf, 4 years ago

Component: Drivers/Graphics/intel_extremeDrivers/Graphics/intel_extreme/haswell
Owner: changed from kallisti5 to pulkomandy

comment:9 by modeenf, 4 years ago

Why did the owner changed to pulkomandy when I hanged the graphic card to the right sub type?

comment:10 by pulkomandy, 4 years ago

I am the default owner for the subcomponents that I created. I did not find how to change the default owner for the existing intel_extreme one in the current Trac adming interface so it's still kallisti5, but he has not done a lot of work on this driver for a while.

comment:11 by Coldfirex, 3 years ago

Any change with on Beta 3 that includes several fixes to the intel_extreme driver?

in reply to:  11 comment:12 by X512, 3 years ago

Replying to Coldfirex:

Any change with on Beta 3 that includes several fixes to the intel_extreme driver?

Works fine at least from beginning of this year.

comment:13 by diver, 3 years ago

Resolution: fixed
Status: newclosed

comment:14 by pulkomandy, 3 years ago

Milestone: UnscheduledR1/beta3
Note: See TracTickets for help on using tickets.