Opened 6 years ago

Closed 6 years ago

Last modified 5 years ago

#14338 closed bug (not reproducible)

Screen inop after desktop initialization

Reported by: cocobean Owned by: kallisti5
Priority: normal Milestone: R1/beta2
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

hrev52197 x86_64, Custom Desktop Machine, Intel i3-550 CPU with Intel IronLake IGP (8086:0042 - Intel HD Graphics, Y2010)

Graphic output: VGA and DVI-D port (connected to VGA port)

Issue: blue screen (screen inop) after Haiku splash screen red rocket is finished and main desktop is initializing.

Workaround: Use fail-safe graphics driver

Attachments (1)

intel_extreme_testing-hrev52197_x86_64.txt​ (18.4 KB ) - added by cocobean 6 years ago.
hrev52197 x86_64 Syslog info of intel_extreme driver output

Download all attachments as: .zip

Change History (9)

by cocobean, 6 years ago

Attachment: intel_extreme_testing-hrev52197_x86_64.txt​ added

hrev52197 x86_64 Syslog info of intel_extreme driver output

comment:1 by cocobean, 6 years ago

  1. Monitor EDID info is missing (not read from monitor).
  2. VMEM seems off(shows 256MB, usually sys memory/VRAM up to 1.7GB VRAM usually).
  3. Same monitor setup works on FreeBSD/Linux/Win distros.
  4. Fail-safe VESA driver works fine.
  5. Tested intel_extreme at various screen resolutions/Standard VGA. Same issue.
  6. Did the Screen->Preferences->Apply trick. Same issue.
  7. compute_dpll_g4x: offset by -0.311577 (108.883 versus 108.571)
Last edited 6 years ago by cocobean (previous) (diff)

comment:2 by waddlesplash, 6 years ago

Is this a new issue, or an old one?

comment:3 by cocobean, 6 years ago

New issue on this specific hardware.

Version 0, edited 6 years ago by cocobean (next)

comment:4 by cocobean, 6 years ago

NOTE: I can display both 1600x1200x32 and 1920x1440x32 screen resolutions with the VESA driver using my Intel IGP (PCI ID: 8086:0042) using screen preferences.

Last edited 6 years ago by cocobean (previous) (diff)

comment:5 by pulkomandy, 6 years ago

Milestone: Unscheduled → R1/beta2

comment:6 by cocobean, 6 years ago

Please close this ticket. I have a working driver solution.

comment:7 by waddlesplash, 6 years ago

Resolution: → not reproducible
Status: new → closed

comment:8 by nielx, 5 years ago

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.