Opened 10 years ago

Closed 3 years ago

#11180 closed bug (fixed)

Intel i7-3770 (HD Graphics 4400) boots into black screen

Reported by: pistooli Owned by: nobody
Priority: normal Milestone: R1/beta4
Component: Drivers/Graphics/intel_extreme/ivybridge Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #11437, #17282
Platform: x86

Description

I have an Intel i7-3770 Gigabyte motherboard with integrated HD4000 (3rd Gen Core processor Graphics Controller) graphics and neither the intel, nor vesa driver works. It boots, then after the boot screen it goes out of sync and screen goes dark (hdmi and/or DVI).

it is in hrev47773 (but never worked so far)

Vendor: 0x8086, Device: 0x0166

Perhaps these IDs can be added to the intel_extreme driver...

Attachments (9)

listdev (2.4 KB ) - added by pistooli 10 years ago.
listdev
syslog (474.1 KB ) - added by danboid 10 years ago.
listdev-4700MQ (2.7 KB ) - added by danboid 10 years ago.
listdev.2 (32.3 KB ) - added by vidrep 9 years ago.
syslog.2 (138.1 KB ) - added by vidrep 9 years ago.
HD4000_hrev53047.jpg (97.4 KB ) - added by taos 6 years ago.
HD4000 under hrev53047.
syslog.txt (512.0 KB ) - added by taos 6 years ago.
Syslog booting HD4000 with hrev53047 anyboot iso.
DSCN5543.JPG (2.9 MB ) - added by aldor 3 years ago.
Log file in "Use fail-safe graphics driver" mode
syslog.3 (469.3 KB ) - added by aldor 3 years ago.

Change History (39)

comment:1 by jprostko, 10 years ago

Both the device bridge ID and device display ID are needed to patch the driver. If you can provide both (0x0166 is either the display ID or bridge ID only), then an attempt at patching the driver can be attempted.

I only know this by following the recent commits by Humdinger and Pulkomandy to add device support. I'll actually add support for the Iris Pro Graphics 5200 present on my laptop later today or tomorrow after I do more testing to make sure it is stable on my machine.

comment:2 by pistooli, 10 years ago

Thank you,

Vendor: 8086, Device: 0166, Sub Ven: 1458, Sub Dev: D000

Thats all I can get it seems. If that is sufficiant.

comment:3 by korli, 10 years ago

Please provide a listdev output and/or syslog.

by pistooli, 10 years ago

Attachment: listdev added

listdev

comment:4 by pistooli, 10 years ago

VESA mode works, sorry for the wrong information, listdev attached.

comment:5 by jprostko, 10 years ago

Well, it seems like it should already be supported from what I can tell.

See http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/busses/agp_gart/intel_gart.cpp#n98

which shows the device ID of 0162 and the bridge ID of 0150.

Also, http://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/drivers/graphics/intel_extreme/driver.cpp#n94

shows the device ID of 0162 as well.

I think that a syslog will be needed in this case to diagnose any further.

Last edited 10 years ago by jprostko (previous) (diff)

comment:6 by luroh, 10 years ago

Summary: Intel i7-3770 (HD Graphics 4400) does not boot (not even in VESA)Intel i7-3770 (HD Graphics 4400) boots into black screen

comment:7 by taos, 10 years ago

It seems I have the same (or at least very similar) problems with an i3-3225 (HD 4000) on DisplayPort (further details in 10978#comment:4), from 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
Last edited 10 years ago by taos (previous) (diff)

comment:8 by vidrep, 10 years ago

Ticket #11437 is related - Intel HD graphics boots into black screen.

comment:9 by pulkomandy, 10 years ago

Blocking: 11437 added

comment:10 by danboid, 10 years ago

I'm having the same problem under 49132 on my i7-4700MQ / HD 4600. Whether I boot using Intel Extreme or the VESA (fail-safe) drivers, I don't get an image on my HDMI TV.

Last edited 10 years ago by danboid (previous) (diff)

by danboid, 10 years ago

Attachment: syslog added

by danboid, 10 years ago

Attachment: listdev-4700MQ added

comment:11 by vidrep, 9 years ago

My Intel Core i5-660 integrated graphics has never worked with Haiku. Same symptoms as described above - driver loads, but only black screen. This is using the VGA output. I have attached a listdev and syslog.

by vidrep, 9 years ago

Attachment: listdev.2 added

comment:12 by vidrep, 9 years ago

Sorry, forgot to attach the syslog...

by vidrep, 9 years ago

Attachment: syslog.2 added

comment:13 by axeld, 8 years ago

Owner: changed from axeld to nobody
Status: newassigned

comment:14 by pulkomandy, 6 years ago

Milestone: R1R1/beta2

comment:15 by waddlesplash, 6 years ago

Please retest after hrev53040.

comment:16 by taos, 6 years ago

For my i3-3225 with HD 4000, it's definitely better than before. Instead of a black screen I'm now greeted by several (2.5 to be exact) desktops (see attached HD4000_hrev53047.jpg). I can't change the resolution in Screen preferences to the native 2560 x 1440 of my display, maximum is 1920 x 1200 which means a little less than 1.5 desktop tiles on the screen (it seems it can't stretch one desktop to fill the whole screen).

by taos, 6 years ago

Attachment: HD4000_hrev53047.jpg added

HD4000 under hrev53047.

by taos, 6 years ago

Attachment: syslog.txt added

Syslog booting HD4000 with hrev53047 anyboot iso.

comment:17 by pulkomandy, 5 years ago

Component: Drivers/Graphics/intel_extremeDrivers/Graphics/intel_extreme/ivybridge

comment:18 by pulkomandy, 5 years ago

Resolution: not reproducible
Status: assignedclosed

taos:

KERN: intel_extreme: Warning: zero active displays were found!

vidrep: using VGA

danboid: using Haswell which is a quite different hardware

pistooli: never attached a syslog so I don't know.

It is very difficult for me to track multiple different problems in a single ticket. So I will focus on taos' problem here.

What is your setup? How do you connect the display to the computer? DVI? HDMI?

in reply to:  18 comment:19 by taos, 5 years ago

Replying to pulkomandy:

taos:

KERN: intel_extreme: Warning: zero active displays were found!

...

It is very difficult for me to track multiple different problems in a single ticket. So I will focus on taos' problem here.

What is your setup? How do you connect the display to the computer? DVI? HDMI?

As mentioned in comment:7, my display is connected via DisplayPort.

comment:20 by nielx, 5 years ago

Milestone: R1/beta2

Remove milestone for tickets with status = closed and resolution != fixed

comment:21 by diver, 3 years ago

Blocking: 17282 added

comment:22 by diver, 3 years ago

Resolution: not reproducible
Status: closedreopened

Someone reported on Telegram that this is still an issue.

comment:23 by rudolfc, 3 years ago

Hi, what is 'this'? seems there were a few different problems in this ticket..

comment:24 by aldor, 3 years ago

Hey! HD Graphics 4400 boots into black screen. Before beta 3, the download went smoothly. Perhaps in the last nightly builds, before the release of beta 3, there were already problems. Now I don't remember exactly. It seems that after fixing the Intel (R) HD Graphics drivers, before beta 3, this problem appeared.

My laptop configuration

X64-based ACPI Computer (Mobile)

Motherboard: CPU Type Mobile DualCore Intel Core i5-4210U, 2400 MHz (24 x 100) Systemic pay Acer Aspire E5-573G

Chipset systemic fees Intel Lynx Point-LP, Intel Haswell Systemic memory

DIMM1: Samsung 4 GB DDR3-1600 DDR3 SDRAM (11-11-11-28 @ 800 MHz) (10-10-10-27 @ 761 MHz) (9-9-9-24 @ 685 MHz) (8-8 -8-22 @ 609 MHz) (7- M471B5173EB 0-YK0 7-7-19 @ 533 MHz) (6-6-6-16 @ 457 MHz) (5-5-5-14 @ 380 MHz) BIOS type Insyde (02/16/2016) Communication this port Standard serial port over Bluetooth connection (COM3)

Communication this port Standard serial port over Bluetooth connection (COM4)

Display: Intel (R) HD Graphics 4400 3D Accelerator: Intel HD Graphics 4400 3D AcceleratornVIDIA GeForce 920M Monitor CMN N156HGE- EAB [15.6 "LCD]

Multimedia:

Sound adapter Realtek ALC255 @ Intel Lynx Point-LP PCH - High Definition Audio Controller [B2] Data storage: IDE controller Intel (R) 8 Series Chipset Family SATA AHCI Controller

Keyboard Standard PS / 2 keyboard Mouse ELAN I2C Filter Driver Mouse HID Compliant Mouse

Network:

Network adapter Bluetooth Device (Personal Area Network) Network adapter Broadcom 802.11n Network Adapter Network adapter Microsoft Wi-Fi Direct Virtual Adapter # 2 Network adapter Microsoft Wi-Fi Direct Virtual Adapter Network adapter Realtek PCIe GbE Family Controller

Controller USB2 Intel Lynx Point-LP PCH - USB 2.0 EHCI Host Controller 1 [B2]

Controller USB3 Intel Lynx Point-LP PCH - USB 3.0 xHCI Host Controller [B2] USB Bluetooth USB module USB Generic USB Hub USB HD WebCam USB Device Realtek USB 2.0 Card Reader USB device USB input device USB device Composite USB device Microsoft Surface Battery ACPI- Compliant Control Method Battery

Last edited 3 years ago by aldor (previous) (diff)

comment:25 by rudolfc, 3 years ago

Hello Aldor, can you upload a syslog, preferably from a boot where the driver for intel tries to control the card? You can try previous syslog after a failed boot, when booting into vesa mode or so..

comment:26 by aldor, 3 years ago

Last edited 3 years ago by aldor (previous) (diff)

comment:27 by aldor, 3 years ago

Checked on nightly build 55449 64-bit.Using these modes "Enable serial debug output + Disable on screen paging" we managed to take a picture of the boot log. But there is a subtle point ... If the system is allowed to boot in normal mode, with "Enable serial debug output + Disable on screen paging", then after displaying the entire log on the screen, a black screen turns on. If you enable "Use fail-safe graphics driver" and "Enable serial debug output + Disable on screen paging" then the log reaches a certain place and hangs.

Last edited 3 years ago by aldor (previous) (diff)

comment:28 by aldor, 3 years ago

I don't understand how to attach a photo with a log here.

Last edited 3 years ago by aldor (previous) (diff)

by aldor, 3 years ago

Attachment: DSCN5543.JPG added

Log file in "Use fail-safe graphics driver" mode

by aldor, 3 years ago

Attachment: syslog.3 added

comment:29 by aldor, 3 years ago

In revision 55706, the problem is gone.

comment:30 by rudolfc, 3 years ago

Milestone: R1/beta4
Resolution: fixed
Status: reopenedclosed

Nice! Closing ticket then, assuming it was re-opened for your system. Thanks for the feedback!

Note: See TracTickets for help on using tickets.