Opened 3 years ago

Closed 3 years ago

Last modified 3 years ago

#17046 closed bug (invalid)

IvyBridge on laptop: blank screen then KDL

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

Description (last modified by yann64)

Booting Haiku hrev55207 x86_64 on a Dell Latitude e6430 laptop using EFI results in a blank screen (once all the boot icons have been successfuly displayed/lit-up), then KDL after a few minutes. Booting using framebuffer does not generate any issue, so looks related to recent work on the Intel Extreme driver.

Attachments (5)

syslog.old (242.2 KB ) - added by yann64 3 years ago.
syslog
Devices.png (76.9 KB ) - added by yann64 3 years ago.
KDL.png (1.7 MB ) - added by yann64 3 years ago.
syslog (118.9 KB ) - added by yann64 3 years ago.
syslog for hrev55176
syslog.2 (369.5 KB ) - added by yann64 3 years ago.
syslog for hrev55214

Change History (12)

by yann64, 3 years ago

Attachment: syslog.old added

syslog

by yann64, 3 years ago

Attachment: Devices.png added

by yann64, 3 years ago

Attachment: KDL.png added

comment:1 by rudolfc, 3 years ago

Hi, Thank you. Can you please also upload a syslog from the last known to you working version of the driver for my reference if possible?

by yann64, 3 years ago

Attachment: syslog added

syslog for hrev55176

comment:2 by yann64, 3 years ago

Added syslog for hrev55176 (working driver). There are 6 hrevs in between this one and hrev55207 so it may not be the last working one.

comment:3 by yann64, 3 years ago

Description: modified (diff)

Booted latest nightly hrev55214 using BIOS and the driver worked fine. Tried again from USB this time using EFI and it also worked fine. I got a feeling my EFI install got somewhat corrupted between the aforementionned hrevs so I did a clean install (BIOS mode) with the latest nightly, and it works. The ticket can be close as invalid.

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

comment:4 by rudolfc, 3 years ago

Thank you. I expect it's the pipe assignment that's causing trouble for you (B=OK, A fails). I will look into it asap, but I can't update the driver until next week I'm afraid. I'll keep you posted!

comment:5 by rudolfc, 3 years ago

Resolution: invalid
Status: newclosed

Since yann64 wrote on discuss.haiku-os.org:

Ticket can be closed as invalid. Driver is working when booting from USB and from clean install. Somehow my install got corrupted. Sorry for the noise.

Closing ticket. Looks like pipe A does work.

If you could upload a new syslog that would be nice for confirmation!

Thanks!

by yann64, 3 years ago

Attachment: syslog.2 added

syslog for hrev55214

in reply to:  5 comment:6 by yann64, 3 years ago

Replying to rudolfc:

If you could upload a new syslog that would be nice for confirmation!

Thanks!

Added syslog from hrev55214 (working / clean install)

comment:7 by rudolfc, 3 years ago

Thank you. Pipe A is in use and looks OK indeed. It's preprogrammed by the BIOS to 18-bit colordepth for the panel as well. Which is an indicator the BIOS also uses this pipe.

Though FDI isn't actually used if all is right (panel on north/cpu side I assume). For your native mode two lanes would be needed while only 1 is operational from the looks of it.

Last edited 3 years ago by rudolfc (previous) (diff)
Note: See TracTickets for help on using tickets.