#11254 closed bug (invalid)
Intel graphics randomly boots with black screen
Reported by: | edglex | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Drivers/Graphics/intel_extreme/ivybridge | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
This is hrev 47865 on a thinkpad x230 with intel HD 4000 graphics.
Two thirds or three quarters of the time this machine has a black screen on boot (with the intel driver). The rest of the time it boots normally and has the correct resolution etc.
The attached syslog is from 2 boots - the first exhibited the problem while the second was a successful boot.
More info: Changing display settings once booted can also cause the same issue (screen goes black to change modes and the image doesn't come back). This is mostly a problem with software that changes the screen mode itself (like SDL apps), since they change without a "return to previous settings" timeout. Actually, SDL apps seem to change the mode to the same as it already is for some reason, but I know the mode has changed because of the flash to a black screen and then back again, and afterwards switching desktops will cause the screen to turn briefly black then come back, unless I use screen preferences and apply to all desktops.
Attachments (3)
Change History (13)
by , 10 years ago
comment:1 by , 10 years ago
Another couple of notes:
I am sure this is an intel driver problem because booting with vesa does not exhibit the issue. Also, the system still responds - if I press (not hold) the power button I see disk activity and the machine powers off.
The problem has been around since at least hrev 46596 (the first haiku version I installed on here).
by , 10 years ago
Attachment: | syslog_diff added |
---|
diff -Naur syslog\ success syslog\ fail > syslog_diff
comment:3 by , 10 years ago
Can't really see any difference here really except the address the RAM is mapped to by the MMU, if I follow correctly?
Is there a way to enable more logging for the intel_extreme driver?
comment:4 by , 10 years ago
Alignment issue? The difference I mentioned was:
-KERN: intel_extreme: mapping VBIOS: 0xc0000 -> 0x81be9000 +KERN: intel_extreme: mapping VBIOS: 0xc0000 -> 0x8060d000
-KERN: [[36mAGP:[[0m create memory 0x82a90440, base e0000000, size 10000, flags 0 -KERN: add_memory_type_range(4464, 0xf252b000, 0x20000, 0) +KERN: [[36mAGP:[[0m create memory 0x82b8bd40, base e0000000, size 10000, flags 0 +KERN: add_memory_type_range(4465, 0xf252b000, 0x20000, 0)
-KERN: [[36mAGP:[[0m create memory 0x82a90800, base e00ff000, size 1000, flags 2 +KERN: [[36mAGP:[[0m create memory 0x82ab5a60, base e00ff000, size 1000, flags 2
-KERN: [[36mAGP:[[0m create memory 0x82a90e80, base e0100000, size 408000, flags 0 +KERN: [[36mAGP:[[0m create memory 0x82b9a3a0, base e0100000, size 408000, flags 0
comment:5 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 6 years ago
Milestone: | R1 → R1/beta2 |
---|
comment:8 by , 5 years ago
Component: | Drivers/Graphics/intel_extreme → Drivers/Graphics/intel_extreme/ivybridge |
---|
comment:10 by , 5 years ago
Milestone: | R1/beta2 |
---|
Remove milestone for tickets with status = closed and resolution != fixed
syslog of failed and successful boot