Opened 17 months ago

Last modified 8 weeks ago

#14301 new bug

Intel HD Graphics 2000: black screen

Reported by: vidrep Owned by: pulkomandy
Priority: normal Milestone: R1/beta2
Component: Drivers/Graphics/intel_extreme/sandybridge Version: R1/Development
Keywords: Cc:
Blocked By: Blocking: #8952
Has a Patch: no Platform: All

Description

hrev52136 x86_gcc2h

Intel HD Graphics 2000

Sandy Bridge [HD Graphics GT1]

Device 8086:0102

Native resolution of monitor is 1680x1050

After rocket icon only a black screen.

Attachments (8)

listdev.txt (2.5 KB ) - added by vidrep 17 months ago.
syslog.txt (127.2 KB ) - added by vidrep 17 months ago.
dmidecode.txt (27.8 KB ) - added by vidrep 17 months ago.
VESA.png (23.2 KB ) - added by vidrep 17 months ago.
serial.txt (104.5 KB ) - added by vidrep 17 months ago.
Intel_8086:0102.txt (104.3 KB ) - added by vidrep 16 months ago.
intel_syslog.txt (14.7 KB ) - added by vidrep 2 months ago.
syslog (133.9 KB ) - added by vidrep 8 weeks ago.

Download all attachments as: .zip

Change History (22)

by vidrep, 17 months ago

Attachment: listdev.txt added

by vidrep, 17 months ago

Attachment: syslog.txt added

by vidrep, 17 months ago

Attachment: dmidecode.txt added

comment:1 by vidrep, 17 months ago

Native resolution of monitor (1680x1050) is not supported by VESA driver either.

by vidrep, 17 months ago

Attachment: VESA.png added

comment:2 by pulkomandy, 17 months ago

1898	intel_extreme: CALLED status_t init_hardware()
1899	package_daemon [15458676:   500] intel_extreme: CALLED status_t init_driver()
1900	active package: "cdrtools-3.02~a09-1-x86_64.hpkg"
1901	package_daemon [15474072:   500] active package: "tar-1.29-3-x86_64.hpkg"
1902	[36mAGP:[0m bus manager init
1903	package_daemon [15480564:   500] [36mAGP:[0m found 0 AGP devices
1904	active package: "openssl-1.0.2o-1-x86_64.hpkg"
1905	intel_extreme: detect_intel_pch: Found CougarPoint PCH
1906	package_daemon [15493386:   500] intel_extreme: (0) SandyBridge Desktop GT1, revision = 0x9
1907	active package: "mesa_swpipe-17.1.7-8-x86_64.hpkg"
1908	intel_extreme: CALLED const char** publish_devices()
1909	package_daemon [15510806:   500] intel_extreme: CALLED device_hooks* find_device(const char*)
1910	active package: "libtheora-1.1.1-7-x86_64.hpkg"
1911	loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/intel_extreme

These are the only references to the intel_extreme driver. It apparently found a PCH, but no device? How can we end up with a black screen because of it then?

comment:3 by vidrep, 17 months ago

I managed to grab a serial log, which I've attached. It may have the information you're looking for.

by vidrep, 17 months ago

Attachment: serial.txt added

comment:4 by pulkomandy, 16 months ago

The end of the serial log:

2114	intel_extreme: intel_set_display_mode(1680x1050)
2115	[33musb_asix:[0m00.17.251:init_driver::ver.0.10.1
2116	loaded driver /boot/system/add-ons/kernel/drivers/dev/net/usb_asix
2117	intel_extreme: IsConnected: Analog A PortRegister: 0x5001100
2118	intel_extreme: CALLED void Pipe::Enable(bool)
2119	[36mAGP:[0m create memory 0x82b6f420, base e0010000, size 6bb000, flags 0
2120	[36mAGP:[0m allocation is made of reserved memory
2121	[36mAGP:[0m reserved memory already bound
2122	intel_extreme: IsConnected: Analog A PortRegister: 0x5001100
2123	intel_extreme: SetDisplayMode: Analog A 1680x1050
2124	intel_extreme: CALLED status_t FDILink::Train(display_mode *)
2125	intel_extreme: Train: FDI Link Lanes: 2
2126	intel_extreme: CALLED void FDIReceiver::EnablePLL(long unsigned int)
2127	intel_extreme: EnablePLL: Already enabled.
2128	intel_extreme: CALLED void FDIReceiver::SwitchClock(bool)
2129	intel_extreme: CALLED void FDITransmitter::EnablePLL(long unsigned int)
2130	intel_extreme: EnablePLL: Already enabled.
2131	intel_extreme: CALLED status_t FDILink::_SnbTrain(long unsigned int)
2132	intel_extreme: CALLED void FDIReceiver::Enable()

This looks strange, we are trying to set a display mode so at this point we should be configuring the PLLs for the right mode. But instead it says "already enabled" and does nothing.

comment:5 by vidrep, 16 months ago

PulkoMandy, I updated both PC's to latest build (hrev52280), which now includes your changes to the Intel_extreme driver. I grabbed a serial debugging log of each PC. Attached is the log for this particular Intel graphics chipset (8086:0102.txt). What is odd is that the boot process appears to stall when initializing the graphics and does not go any further. Whereas, the other PC with chipset (8086:0152) will completely boot, although with a black screen. I will attach the log for that PC here: https://dev.haiku-os.org/ticket/13669

by vidrep, 16 months ago

Attachment: Intel_8086:0102.txt added

comment:6 by pulkomandy, 14 months ago

Milestone: UnscheduledR1/beta2

comment:7 by waddlesplash, 8 months ago

Blocking: 8952 added

comment:8 by waddlesplash, 8 months ago

Please retest after hrev53040.

comment:9 by vidrep, 8 months ago

I still have a black screen after updating to hrev53042.

comment:10 by pulkomandy, 2 months ago

Please try https://review.haiku-os.org/c/haiku/+/1899

I have prebuilt a (32bit) accelerant in case you don't want to build Haiku yourself: http://pulkomandy.tk/drop/intel_extreme_14301.accelerant

comment:11 by vidrep, 2 months ago

I've attached a summary of the syslog using the pre-build binary.

by vidrep, 2 months ago

Attachment: intel_syslog.txt added

comment:12 by pulkomandy, 2 months ago

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

comment:13 by waddlesplash, 8 weeks ago

Change was merged in hrev53551.

comment:14 by vidrep, 8 weeks ago

hrev53555 x86_64

Still black screen after update.

syslog attached

by vidrep, 8 weeks ago

Attachment: syslog added
Note: See TracTickets for help on using tickets.