Opened 6 weeks ago

Last modified 5 weeks ago

#15448 assigned bug

Synchronization with flat-panel display after live-USB boot is broken

Reported by: Evgen Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description (last modified by Evgen)

hrev53561 does not sync with monitor

Display: LG FULL HD 21.7 1920 x 1080 32 bit/pixel 102 dpi 60Hz, plugged to machine via VGA port. Chip: Intel GMA (i915 GM)

Booting with live-USB passes through whole set of icons of splash-screen, but when it comes to welcome to install, synchronization is broken. I have tried to set different video modes (standard VGA, 640 x 480 ...). Does not help. Latest revision that worked with no issues was hrev53543

Update: was actually able to boot with VESA mode with hrev53556, sorry. The last build that works normally was hrev53546. I wonder whether support for videochip on my machine is dropped?

Attachments (3)

syslog_hrev53546 (215.7 KB ) - added by Evgen 6 weeks ago.
hrev53546 syslog
previous_syslog (90.0 KB ) - added by Evgen 5 weeks ago.
intel videochip
syslog (497.7 KB ) - added by Evgen 5 weeks ago.
VESA video

Download all attachments as: .zip

Change History (16)

comment:1 by Evgen, 6 weeks ago

Description: modified (diff)

comment:2 by diver, 6 weeks ago

Component: Audio & VideoDrivers/Graphics/intel_extreme
Owner: changed from nobody to pulkomandy
Status: newassigned

comment:3 by Evgen, 6 weeks ago

Description: modified (diff)

comment:4 by pulkomandy, 6 weeks ago

No, we don't drop support for hardware, but testing depends on our access to relevant machines.

There is probably a problem in https://git.haiku-os.org/haiku/commit/?id=b8f6e4813d2befd024b556e6dec98398489b69b5

But it's possible the issue is fixed by https://review.haiku-os.org/c/haiku/+/1898 , if you could build Haiku with that change applied and test that, it would be great to confirm that this works.

Otherwise, I would need a syslog, ideally from both the latest working revision and a current (broken) one.

comment:5 by Evgen, 6 weeks ago

OK, will provide syslogs for both cases. Actually, there seems another problem: when I asked bootloader to show debug info, it shows several pages (that I can continue listing by pressing 'space'), and then machine totally hangs. But if in debugging options I disable page listing, everything is fine and machine proceeds to the desktop.

comment:6 by pulkomandy, 6 weeks ago

Possibly similar to #15457 ?

by Evgen, 6 weeks ago

Attachment: syslog_hrev53546 added

hrev53546 syslog

comment:7 by Evgen, 6 weeks ago

Please see hrev53546 (boots normally) syslog attached

in reply to:  6 comment:8 by Evgen, 6 weeks ago

Replying to pulkomandy:

Possibly similar to #15457 ?

Yes. In my case it's 32 bit and BIOS.

comment:9 by Evgen, 5 weeks ago

hrev53567 bootlog (9 shots). Sorry, mistakenly uploaded them for ticket 14368 too.

comment:10 by pulkomandy, 5 weeks ago

These screenshots do not include any information from the intel driver (the log stops before that). You should be able to access the syslog this way:

  • Boot the machine normally (to a black screen) from a writable device (USB stick or hard disk)
  • Reboot (use KDL shortcut and type "reboot", for example) and select VESA from the boot menu
  • Get the syslogs from /var/log (previous boot syslogs are stored there as well)

comment:11 by Evgen, 5 weeks ago

Ok, if I got it right:

  • Live-USB boot with intel videodriver active. Syslog will be saved.
  • Live-USB boot with VESA videodriver active. Previous syslog will be saved in /var/log.

You want this file. All correct?

comment:12 by pulkomandy, 5 weeks ago

Yes. Get all 3 syslogs from /var/log (syslog, syslog.1 and previous_syslog) just to be sure. I'll find what I need there.

by Evgen, 5 weeks ago

Attachment: previous_syslog added

intel videochip

by Evgen, 5 weeks ago

Attachment: syslog added

VESA video

comment:13 by Evgen, 5 weeks ago

Please see, attached. There were no syslog.1

Note: See TracTickets for help on using tickets.