Opened 14 months ago

Last modified 8 weeks ago

#14643 new bug

Black screen booting with Intel HD4600

Reported by: humdinger Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/intel_extreme/g45 Version: R1/beta1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

Used to work before that intel_extreme update some time ago. No syslog available.

It's a 4th generation Haswell CPU, i7-4712MQ:

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 8086: Intel Corporation
  device 0416: 4th Gen Core Processor Integrated Graphics Controller

Attachments (1)

syslog.txt (218.2 KB ) - added by humdinger 2 months ago.
syslog ​for Haswell CPU, ​i7-4712MQ

Download all attachments as: .zip

Change History (13)

comment:1 by humdinger, 14 months ago

Same for another Haswell CPU with similar Intel HD4600 chipset, i7-4770S:

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

comment:2 by waddlesplash, 8 months ago

Please retest after hrev53040.

comment:3 by humdinger, 8 months ago

No change with hrev53042.

comment:4 by pulkomandy, 2 months ago

A syslog would be nice.

comment:5 by humdinger, 2 months ago

Got a syslog now with hrev53523 for the Haswell CPU, ​i7-4712MQ. Attached.

by humdinger, 2 months ago

Attachment: syslog.txt added

syslog ​for Haswell CPU, ​i7-4712MQ

comment:6 by pulkomandy, 2 months ago

That syslog does not mention the intel_extreme driver at all. Did you blacklist it?

comment:7 by humdinger, 2 months ago

I deleted all files in system/var/logs/, rebooted, got a black screen, powered off, and booted into another Haiku installation to get to the syslog. I found it peculiar that there was only a "previous_syslog" there...
Maybe I messed it up and that wasn't the right syslog from the black-screen-boot... (could be there isn't one, as I wrote in the OT: "No syslog available.")

I'm out of time today, but I'll give it another try tomorrow. Thanks for looking into these intel_extreme issues!

comment:8 by pulkomandy, 2 months ago

It can be, indeed, that the driver somehow freezes the system completely before syslog is written to disk. In that case, we'll need serial debug, but I guess this is a laptop without serial or expresscard port?

comment:9 by humdinger, 2 months ago

Correct on all accounts. I tried to get a syslog once more (this time paying close attention at all times...), but it is indeed not written. No chance on serial debugging...

I'll check the i7-4770S from my 1st comment later.

comment:10 by humdinger, 2 months ago

The i7-4770S mentioned in the first comment is now using the intel_extreme driver. Yay!

On first boot, the bottom 120 pixels are a pixel chaos, because the resolution 1920x1080 was set, but the monitor is actually a 1920x1200 (nice!). That's fixed by setting the correct resolution. I suppose the monitor's EDID is slightly off.

comment:11 by pulkomandy, 2 months ago

It's actually because the intel_extreme driver does not know how to set a video mode. It works only with the mode already set by VESA.

I will look into actually doing modesetting for the modern intel videocards, but I would prefer to fix the regressions first and work from a sane base. There is some progress towards that, at least :)

comment:12 by pulkomandy, 8 weeks ago

Component: Drivers/Graphics/intel_extremeDrivers/Graphics/intel_extreme/g45
Owner: changed from kallisti5 to pulkomandy
Note: See TracTickets for help on using tickets.