Haiku / Intel HD Graphics 4000 / i7-3770

[oxoocoffee]

I just tried latest nightly hrev53935-x86_64-anyboot today and I am seeing black screen. I also see similar ticket https://dev.haiku-os.org/ticket/11180

​https://ark.intel.com/content/www/us/en/ark/products/65719/intel-core-i7-3770-processor-8m-cache-up-to-3-90-ghz.html

My system is: Asus P8H77-I motherboard with i7-3770 CPU, 16G RAM and 256G SSD

Here is what I did try and what I did see.

1. Boot from USB (hrev53935-x86_64-anyboot)
2. All icons do light up
3. Now I should see blue desktop but instead I see black screen. Looks like my 24in Samsung screen stays black and it does not say lost signal or anything like that. I did gave about 2-3 min and nothing changed.
4. Next I did try fail safe VESA and this time everything looks fine.

I did try above with VGA, HDMI and DVI cables. Also I did try removing cable, wait 5 sec and inset cable back while I did see black screen. There was not change. I did read someone had tried this on his system (not sure what was his detail configuration) and that did bring full desktop. Not for me.

I am attaching syslog and sysinfo. Please let me know which next version I should try when it will become available. Also if there is any additional tests or files I will be glad to provide. Please include detail commands and file locations.

[oxoocoffee]

sysinfo dump

[oxoocoffee]

syslog dump

[cocobean]

For test, first try the VGA option:

1. Disconnect monitor cable. Leave it disconnected.
2. Boot or reboot computer. Let computer boot until disk activity stops entirely.
3. Reconnect monitor cable.

If successful: You should see the blue desktop (or installation GUI, if Live CD, so pick 'boot to Desktop'). Post the syslog data to bug report. Snapshot the desktop's screen preferences GUI.

[vidrep]

Can you provide a listdev ? The device ID may be helpful.

[oxoocoffee]

syslog and screenshot after connecting VGA after boot finished

[oxoocoffee]

I followed your directions and repeated it 3 times for different connections

1. VGA (attached file vga.tar.gz)
2. HDMI (blank screen)
3. DVI (blank screen)

I could not get 2. and 3. working. Please let me know if you have any additional questions

EDIT: I forgot to mention that I grabbed syslog after the first screen. 2nd and 3rd screenshots were captured after HDMI and DVI test failed and I did go back to VGA. If you want syslog for the other two screens (resize) let me know.

[cocobean]

Intel Gen 7 GPU - Intel HD Graphics 4000

IvyBridge Desktop GT2, revision = 0x9
PCI ID: 0162

[pulkomandy]

What is the last haiku revision known to work on this machine? This is the main and most helpful information I need to investigate. The smaller range of last working/first broken revision you can provide, the better. This will allow me to analyze only a few commits for regressions, instead of trying to guess what could be wrong.

[oxoocoffee]

Do yoU have any idea when it was working last time? I should be able to go back and search backward tonight.

[oxoocoffee]

Ok I was able to narrow down where things worked and when it stopped

haiku-master-hrev50544-x86_64-anyboot - Not workig (VGA or HDMI) haiku-master-hrev50357-x86_64-anyboot - Working

haiku-master-hrev50544-x86_64-anyboot

Cold boot with plugged in VGA or HDMI not working Cold boot without the cable plugged int

After USB stops blinking I plugged in HDMI and no video at all After USB stops blinking I plugged in VGA and there is video but not sized properly (I will attach the screens soon)

haiku-master-hrev50357-x86_64-anyboot

Cold boot with plugged in VGA or HDMI video is working. No need to go to safe mode

I sampled 10? nightly above haiku-master-hrev50544-x86_64-anyboot and none worked

Let me know if you need anything else

[pulkomandy]

I checked the syslog for these old revisions and I found that the Intel driver didn't handle this device at all in hrev50357. The PCI IDs had been disabled. So I think the driver never worked properly with your hardware, and was just not used before that. We should probably disable it again.

For the beta 2 we will probably do that, and work later on on a proper fix (if I or some other developer gets their hand on an IvyBridge machine and can find the problem).

[modeenf]

has it bean disabled?

I have a intel nuc dc3217by with that card. It also are a HDMI only. ​https://ark.intel.com/content/www/us/en/ark/products/71274/intel-nuc-kit-dc3217by.html

Does VESA support HDMI? Perhaps I fund the answer to that :) ​https://discuss.haiku-os.org/t/does-haiku-support-hdmi-dvi-d-dual-link-video/2821

[modeenf]

tested to inactivate the driver and vesa did work :).. No sound but I can see :)

Now are there any way to get the previus syslog file some how? there are no serial connector only USB.

If I could boot with intel driver and then get that log when boot up with VESA driver that would help a lot :)

[pulkomandy]

The syslog is accessible in several ways:

• If the machine does not crash too badly, even if you get a black screen, it is still written to disk (the logs from the next boot are just appended to the syslog file)
• It is also persistant in RAM if the BIOS does not erase it, the bootloader allows to write it to a FAT32 USB drive from the boot menu, and it is also saved as /var/log/previous_syslog if you reboot into Haiku
• If the machine has a black screen but an ssh or telnet server is set up, you can get the syslog that way as well, by connecting from another machine.

[modeenf]

Nice thanks..

btw, minne are a IvyBridge Mobile GT2

[modeenf]

Found these. lines so it's found :). I copied inly those lines that had "intel_extreme:"

intel_extreme: CALLED status_t init_hardware()
intel_extreme: CALLED status_t init_driver()
[36mAGP:[0m bus manager init
[36mAGP:[0m found 0 AGP devices
intel_extreme: detect_intel_pch: Found PantherPoint PCH
intel_extreme: (0) IvyBridge Mobile GT2, revision = 0x9
intel_extreme: CALLED const char ** publish_devices()
intel_extreme: CALLED struct device_hooks * find_device(const char *)
loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/intel_extreme

Another question. should this work to blacklist it? Create a text file named 'packages' in /boot/home/config/settings/global, with this text?

Package haiku {

EntryBlacklist {

add-ons/kernel/drivers/bin/intel_extreme

}

}

[jharris]

Sysinfo (i3 with intel integrated)

[jharris]

I am having the same issue, although on an i3. I've attached the output of sysinfo, if this should be its own bug let me know.

[pulkomandy]

The sysinfo is useless to me, it only shows info about the CPU. Please include your syslog (from /var/log/syslog) from a boot to black screen. Please create a separate ticket for it, as yours is a SandyBridge and not IvyBridge system.

[jharris]

Sandybridge syslog

[jharris]

Does this help? This came from a VESA boot, but I assume that the info you need is in here somewhere, so I'm just going to upload the whole thing here, as the file described as "Sandybridge syslog."

[jharris]

(I'm not sure how to upload the boot from a blank screen boot, since the system crashed, but maybe it just appends after a successful boot instead of overwrites?)

[waddlesplash]

No, unfortunately this does not help, as the syslog apparently "wrapped". Just clear the contents of that directory and reboot, and then upload that syslog.

However, since you appear to have a different model of CPU, this probably deserves a separate ticket, so please just open a new one instead of adding to this one.

[oxoocoffee]

Haiku R1/beta2 Hardware Testing

Still both gcc and x64 require Video Safe Mode (VESA). By default it is black screen after all icons light up

[korli]

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

[korli]

No reply.