Opened 16 months ago

Last modified 2 months ago

#13694 new bug

[intel_extreme] Boot failure on Dual Core Pentium 2GHz

Reported by: Sabex Owned by: kallisti5
Priority: high Milestone: R1/beta2
Component: Drivers/Graphics/intel_extreme Version: R1/Development
Keywords: boot-failure, has-workaround Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description (last modified by diver)

hrev51399.

Machine boots using intel_extreme driver only rarely.

Selecting VESA mode always allows booting.

Machine Spec: Acer Extensa 5630 4GB RAM Intel Mobile series 4 integrated graphics

PCI Information:

Device/type	0x3
device/subtype	0x80
device/interface	0x0
device/vendor	0x8086
device/id	0x2a43

device/type	0x3
device/subtype	0x0
device/interface	0x0
device/vendor	0x8086
device/id	0x2a42

intel_extreme specific entries to syslog:

KERN: intel_extreme: CALLED status_t init_hardware()
KERN: intel_extreme: CALLED status_t init_driver()
KERN: intel_extreme: detect_intel_pch: No PCH detected.
KERN: intel_extreme: (0) GM45, revision = 0x7
KERN: intel_extreme: CALLED const char ** publish_devices()
KERN: intel_extreme: CALLED struct device_hooks * find_device(const char *)
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/intel_extreme
KERN: devfs: "intel_810" api_version missing

Attachments (4)

syslog (179.6 KB) - added by Sabex 16 months ago.
Syslog
syslog.2 (363.7 KB) - added by Sabex 14 months ago.
Latest syslog.
syslog.3 (36.6 KB) - added by Sabex 14 months ago.
Syslog after failed boot and reboot
syslog.old (512.0 KB) - added by Sabex 14 months ago.
Syslog after failed reboot (and then cold boot with safe mode VESA driver)

Download all attachments as: .zip

Change History (15)

comment:1 Changed 16 months ago by pulkomandy

There should be a lot more logs from the intel_extreme driver (setting up PLLs, etc). Ideally, include complete syslogs from both when it boots, and when it doesn't, so we can see if anything looks different in each case.

comment:2 Changed 16 months ago by Sabex

I can't seem to upload the files to Trac with either Qupzilla or WebPositive, so the first syslog is here:

https://pastebin.com/v92WuK1Y

Changed 16 months ago by Sabex

Attachment: syslog added

Syslog

comment:3 Changed 16 months ago by Sabex

Has a Patch: set

comment:4 Changed 16 months ago by korli

Has a Patch: unset

comment:5 Changed 14 months ago by Sabex

I can confirm this bug still exists in 32 bit Nightly 51507 gcc2 hybrid.

Please advise as to how I can help you obtain any more information.

Changed 14 months ago by Sabex

Attachment: syslog.2 added

Latest syslog.

Changed 14 months ago by Sabex

Attachment: syslog.3 added

Syslog after failed boot and reboot

Changed 14 months ago by Sabex

Attachment: syslog.old added

Syslog after failed reboot (and then cold boot with safe mode VESA driver)

comment:6 Changed 14 months ago by diver

Component: Audio & VideoDrivers/Graphics/intel_extreme
Description: modified (diff)
Owner: changed from nobody to kallisti5
Summary: [hrev51399 32-bit hybrid] Boot failure on Dual Core Pentium 2GHz[intel_extreme] Boot failure on Dual Core Pentium 2GHz

comment:7 Changed 14 months ago by Sabex

I tried to blacklist the driver by making a file:

/boot/system/settings/packages

Which I populated with this text:

Package haiku {
        EntryBlacklist {
                add-ons/accelerants/intel_extreme.accelerant
                add-ons/kernel/drivers/graphics/intel_extreme
        }
}

but I still need to boot in VESA safe graphics mode. Does that mean it isn't the intel xtreme driver that's causing the issue?

comment:8 Changed 14 months ago by pulkomandy

There is a simpler way to force VESA mode (not sure why everyone went with the blacklist for that).

Edit /home/config/settings/kernel/drivers/kernel

Uncomment the "fail_safe_video_mode true" line (at the end).

comment:9 Changed 14 months ago by Sabex

I'll do that, thanks.

Also, I booted with the kernel messages, and it seems that the intel xtreme driver is loading correctly, but then outputs "Could not intitialize graphics output. Exiting."

Just for fun I then tried forcing different screen resolutions, but it didn't help.

comment:10 Changed 5 months ago by waddlesplash

Keywords: boot-failure has-workaround added

comment:11 Changed 2 months ago by pulkomandy

Milestone: UnscheduledR1/beta2
Note: See TracTickets for help on using tickets.