intel_extreme driver - not working

[vercu]

Following the call for tester hrev 53787 was installed on my Lenovo Thinkpad X1 Carbon 1st generation.
This notebook is normally well supported.
Booting after the update to 53787 leads to a black screen.
Booting in fail safe mode with vesa driver works.

[pulkomandy]

It would be helpful if you could try some older versions and try to find the last working/first broken ones.

[vercu]

During boot I choose the previous state hrev53639 and it works. Screen preferences shows Intel HD/Iris (Ivy Bridge Mobile GT2). Trying to install a more recent rev failed. It seems the instructions are outdated. I use the commands at the bottom of the page ​https://www.haiku-os.org/guides/daily-tasks/updating-system.

[markh]

I have the same problem with an Ivy Bridge Mobile chipset. Do you need any additional information or is the information supplied by vercu enough?

[pulkomandy]

Hi, it would help to further narrow down the revision range in which this was broken. If you can try various nightly builds between hrev53639 and hrev53787 and finding the last working/first broken version would help, as I can then review a much smaller commit range and see which commit broke things.

[markh]

It was still working in hrev53759 and does not work in hrev53783. I saw on the website that I can download two revisions in between (hrev53776 and hrev53780). I am downloading those now and will test them tomorrow. Is there an easy way to try the other revisions that are not on the website?

[humdinger]

Is there an easy way to try the other revisions that are not on the website?

You'd have to build from source. Which I find is quite easily and relaatively quickly done Depending on your hardware of course, probably not recommended on 15+ years old laptops... :)

[markh]

Tested the two releases on the website: hrev53776: Fails to boot at all. Running into #15658, so no idea if the problem already existed or not. hrev53780: Got a black screen, so this revision definitely has the problem.

I will build from source to narrow down the problem further. My laptop is quite fast. :)

[markh]

Well, my laptop is plenty fast, but trying to get an image built to test is an exercise in frustration. Spent a few hours on this and got nothing to show for it. Got plenty of weird error messages during building and saw plenty of wrong documentation trying to get it fixed, though. Maybe I'll give it another go tomorrow.

[pulkomandy]

www.haiku-os.org/guides/building should be complete and up to date. If you found incorrect documentation/instructions somewhere, please link to them so we can update or remove them.

[markh]

Perhaps this ticket is not the right place to discuss this, but I still can't compile Haiku to determine the revision this issue started, so here goes:

ReadMe.Compiling.md included in the source states:

The tools to compile Haiku will vary, depending on the platform that you are using to build Haiku. When building from Haiku, all of the necessary development tools are included in official releases (e.g. R1/beta1) and in the nightly builds.

But at least xorriso and mtools are not included

​https://www.haiku-os.org/guides/building/pre-reqs states:

Currently, Haiku is arguably the most convenient development environment. A nightly image (or stable release) of Haiku should contain all of the software needed to build its sources for x86

But that same page then states that the following command should be executed:

pkgman install mtools python3 cmd:xorriso

However, I get the following error if I do that:

* Failed to find a match for "python3": Name not found

Excluding python3, installs the other packages, but that still gives me an error with compiling (something on there not being enough space on myfs).

​https://www.haiku-os.org/guides/building/compiling-x86 states:

This is the most basic build, it generally is good for quickly testing the OS after making modifications as it doesn't contain a lot of extra applications. Be sure to modify -j2 with the number of cpu cores on your build system to ensure the fastest build times. sh jam -q -j2 @image

However, trying to execute that in a shell gives me: /bin/jam: /bin/jam: cannot execute binary file

I know the sh should be left off, but it is frustrating running into all these things.

[pulkomandy]

• xorriso is needed only if you build an old-style iso image, which is not needed (you can build an anyboot or raw image instead). We have not built or shipped such images for a long time now.
• mtools is needed only to build a complete anyboot image for 64bit versions (to create the EFI partition), if you build only a filesystem image it is not needed.
• the python3 package can be installed using cmd:python3, I'll fix the instructions
• the "sh" is a markdown formatting problem, I'll fix it.

Thanks for reporting!

(something on there not being enough space on myfs).

More details about the important bit where you still have an error would be nice. Can you attach a buildlog or something?

[tqh]

Replying to markh:

Perhaps this ticket is not the right place to discuss this

It is not, either create a new ticket, or use the mailing lists.

[vercu]

I can at least confirm the markh report. hrev53759 works on my notebook. hrev53776 does not boot.

[pulkomandy]

Current status of investigations:

• hrev53759 working
• hrev53780 broken

In that range there were only two changes to the accelerant:

• ​https://git.haiku-os.org/haiku/commit/src/add-ons/accelerants/intel_extreme?id=03ee42a8eb8788177b7af67ca0f7284c98362811
• ​https://git.haiku-os.org/haiku/commit/src/add-ons/accelerants/intel_extreme?id=fadca4b173471fcb1ce40848dce4cc2adee4e681

I see that your hardware uses "Panther Point" platform control hub. I have adjuststed several things in the driver for "Cougar Point" which is the previous generation. Reviewing all places where we check for INTEL_PCH_CPT and adding INTEL_PCH_PPT where it makes sense to do the same thing is likely to help then. I think focusing on the places in Ports.cpp for this is a good start. So that would be lines 133, 385, 558 of the file.

[markh]

I have created #15694 for the build failure. If that gets fixed I can try your suggestions.

[pulkomandy]

Please test hrev53857, issue should be fixed.

[markh]

Just tried, but now I am getting "unable to find boot device" (or something to that effect) while starting up. That doesn't seem to have anything to do with your change, though. I will go back in the revisions to find one that still can boot on my machine and apply your change to see if that fixes it.

[vercu]

Installed hrev53864 and it works again! In detail: desktop ok GLTeapot: 59fps brightness: no effect external screen: does not work (mini dvi) videomodes works switching workspace works

Thank you very much for fixing this.