I installed Haiku (the latest nightly build since the stable wouldn’t boot) and if I start it up normally, it loads the intel driver (Which is correct), but with 16 bit color depth. For whatever reason, only 8 bit color depth works with Haiku (Somehow after the install it got set to 8 bit depth and it worked). Otherwise I can only see about 1/4 of the screen and everything is distorted. Using that 1/4 of a screen I have tried to change the color depth, but every time it is changed, Haiku crashed (pressing power does nothing). I can boot using the failsafe graphics (vesa), but changing anything there won’t affect it when I boot back up using the intel accelerant.
So… 2 questions:
Is there a file that I can edit to change the color depth used with the intel driver?
If not, is there another way to change the color depth used with the intel driver while in vesa-mode?
Thanks for the response. I do not want to blacklist the Intel driver. I want to use the Intel accelerant, but change down the color depth so that there is no distortion. If you want to see what the commands do (When I am using the Intel Accelerant) I get something close to this:
You should file a bug report with the above info and the syslog at the bugtracker.
Until the issue is fixed (hopefully), there’s nothing really wrong with blacklisting and using VESA. Haiku doesn’t use 2d acceleration AFAIK, and overlay video with just a few graphics cards. So, if VESA is providing you with the correct resolution, that seems OK to me.
I can’t seem to get the package blacklist to work. Should it be this?: Package haiku {
EntryBlacklist {
add-ons/accelerants/intel_extreme.accelerant
}
}
And if I got the Intel accelerant to work, wouldn’t that take some stress off of the CPU? Or am I thinking of the wrong thing?
Then save it as “packages” in /boot/system/settings/.
That will disable the intel_extreme driver completely, leaving you with VESA. As I said, the accelerant won’t help much performancewise AFAIK, other than possibly overlay (if it supports that in the first place), and mode switching to get the right resolution (but that can work for VESA as wel…).
I have a Intel HD Graphics 4600 in my notebook and it works very well with VESA. I also have no problems with the included demos. What gives you grief?
Well, both GLTeapot and Haiku3D crash when executed. Patch Bay just gives a blank window. Is this since the laptop is too old, or is it VESA? And I’m not sure if its related, but Whenever I start up Arora, it says "Could not open “Arora” with application “Arora” (Not an executable).
VESA shouldn’t enter into it, I think. GLTeapot and Haiku3D work here with hrev47544 (gcc2hybrid). Maybe you’ll have to try a newer nightly. I don’t know how PatchPay is supposed to look, but it may be that you’ll have to have MIDI devices connected for it’s GUI to become alive.
No idea about Arora, there isn’t a package for it (yet).