Opened 3 years ago

Closed 3 years ago

#17307 closed bug (fixed)

Blank screen (on IvyBridge laptop)

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

Description

Since today upgrade, I have a black/blank screen (once all the boot icons have been successfully displayed/lit-up).

System description:

  • Dell Latitude e6430 (Intel x64 i5 quad core) using BIOS/Legacy boot.
  • Haiku hrev55207 x86_64

Booting using framebuffer does not generate any issue. The upgrade skipped several hrevs so not sure which one created the regression.

Attachments (3)

syslog (293.1 KB ) - added by yann64 3 years ago.
syslog.2 (259.0 KB ) - added by bruno 3 years ago.
syslog.3 (153.4 KB ) - added by yann64 3 years ago.

Download all attachments as: .zip

Change History (14)

by yann64, 3 years ago

Attachment: syslog added

by bruno, 3 years ago

Attachment: syslog.2 added

comment:1 by bruno, 3 years ago

I have same problem now with:

device Signal processing controller [11|80|0]

vendor 8086: Intel Corporation device 1903: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem

device Display controller (VGA compatible controller, VGA controller) [3|0|0]

vendor 8086: Intel Corporation device 1916: Skylake GT2 [HD Graphics 520]

device Bridge (Host bridge) [6|0|0]

vendor 8086: Intel Corporation device 1904: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers

If I start with haiku_loader.efi it works? Syslog attached. Haiku R1 Beta3 nightly hrev:: 55487

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

comment:2 by rudolfc, 3 years ago

Hi, I'd say these problems should not be connected to the latest updates as these updates did not change the card programming: it was merely the system interface that was updated.

One thing that comes to my mind is: do your CPU's have the SMAP thing? Since that would be a problem I'd guess as the intel driver, the nvidia driver, the via (probably only on older x64 if any) and neomagic (well neomagic should be 32bit target only) do not have the needed updates yet and might/will crash I guess because of that.

Is it possible for you to pinpoint better which hrev is the cause of the trouble? That would be super handy..

comment:3 by rudolfc, 3 years ago

Oh wait: ID 1916 (bruno) is skylake, that is generation 9 graphics: that is not really supported yet, though it's ID is in the driver. It might be wise to block driver use there for now (unless maybe you can pinpoint 'exactly' where it went wrong hrev wise)

ID 0166 (yann64) should have worked though (gen7 Ivy)...

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

comment:4 by bruno, 3 years ago

It is hrev. 55487 that makes problems.

If I use haiku_loader.efi it bootd to the desktop.

comment:5 by bruno, 3 years ago

This is the HP B&O Laptop I had ticket for 3 years. Teapot is spinning with 1000fps pn it...

comment:6 by yann64, 3 years ago

Hi rudolfc, I will try to find the faulty hrev during the week-end.

comment:7 by rudolfc, 3 years ago

Bruno, so all in all it seems your system only shows the nvidia gfx card, but not the intel one. So it looks like this bugreport is not the place to be for you ;-) If you really try to use the intel card (not the nvidia one) we should be able to see that in your log(s).

Do you need to enter the system BIOS to change active card?

comment:8 by korli, 3 years ago

yann64, any chance to test a recent nightly?

comment:9 by yann64, 3 years ago

driver working good on hrev56082 (was fixed way before that revision), no 3d acceleration as expected

I ended up re-installing the system as for some reason I ended up with a corrupted installation

Ticket can be closed

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

comment:10 by korli, 3 years ago

Please provide a syslog, thanks.

comment:11 by korli, 3 years ago

Milestone: UnscheduledR1/beta4
Resolution: fixed
Status: newclosed

by yann64, 3 years ago

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