Opened 4 years ago

Last modified 2 years ago

#16806 new bug

Black screen with Intel Graphics HD 4000

Reported by: alscaldas Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/intel_extreme/ivybridge Version: R1/beta2
Keywords: Cc:
Blocked By: Blocking:
Platform: x86-64

Description

Hello,

I have a Intel Graphics HD 4000 and I can boot only if I use VESA. Otherwise I get a black screen. Not sure if it's relevant but I connect my monitor via HDMI or DVI, and with both I get the same result.

That's the output of a listdev:

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
  vendor 8086: Intel Corporation
  device 0162: Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller

And also I'm attaching my syslog in case it's necessary.

Attachments (4)

syslog (263.5 KB ) - added by alscaldas 4 years ago.
Syslog
listdev.txt (5.2 KB ) - added by scottmc 2 years ago.
previous_syslog-scottmc (142.6 KB ) - added by scottmc 2 years ago.
syslog-scottmc.txt (348.4 KB ) - added by scottmc 2 years ago.

Download all attachments as: .zip

Change History (8)

by alscaldas, 4 years ago

Attachment: syslog added

Syslog

comment:1 by korli, 3 years ago

Please check with a current nightly, and provide a syslog.

by scottmc, 2 years ago

Attachment: listdev.txt added

by scottmc, 2 years ago

Attachment: previous_syslog-scottmc added

comment:2 by scottmc, 2 years ago

I'm having a similar issue. I can get to Haiku only if I pick fail safe video mode. I'd like to be able to use my monitors native resolution, but may not be possible? 3440 x 1440

hrev 56506 x86_64

Last edited 2 years ago by scottmc (previous) (diff)

comment:3 by korli, 2 years ago

The syslog only shows that the intel_extreme driver was bypassed. You should boot without fail-safe mode, and provide a new syslog.

by scottmc, 2 years ago

Attachment: syslog-scottmc.txt added

comment:4 by korli, 2 years ago

the app_server tries 3440x1440@49Hz. Is it what it is supposed to ask the driver?

Note: See TracTickets for help on using tickets.