GMA Graphics on D945CLF2D board

CraigsBar · 3659

CraigsBar

  • Newbie
  • *
    • Posts: 7
    • Karma: +0/-0
on: December 02, 2018, 07:00:19 PM
Hi all,

I recently bought 2 D945GCLF2D boards to run Aros on (Always handy having a spare when using 10+ year old boards) however I cannot for the life of me get the Intel Accellerated video to work. VESA is fine but I need to get more flexible resolutions working that are simply not available in VESA modes (1440x900@60hz or 1366x768@60hz for example).

However as soon as I switch to one of these modes, or in fact something as simple as 1024x768@60hz using the Intel Driver then the screen corrupts on the next system boot (As a reboot is needed after saving the settings) These screen resolutions work fine on the monitor (and on the exact same boards using Windows 7) so I know that the issue is not with the hardware itself. Can anyone offer any advise on what I need ot do to get this working. I was originally planning on mounting one of these baords in the Checkmate A1500 plus case that I kickstarted, however this may now not happen and I end up with a A1222 board instead :( So far I have had a really frustrating weekend having achieved nothing other than several reinstalls and lots of disapointment with Aros in general.

Regards

Craig.



ncafferkey

  • Junior Member
  • **
    • Posts: 84
    • Karma: +34/-0
Reply #1 on: December 02, 2018, 07:38:48 PM
What AROS version are you using? Do any native (Intel Driver) modes work? I assume 640x480 works as this is the default mode you would have booted into before selecting a higher resolution.

Lastly, what monitor do you have? Any chance of trying a different monitor?



CraigsBar

  • Newbie
  • *
    • Posts: 7
    • Karma: +0/-0
Reply #2 on: December 02, 2018, 08:00:15 PM
What AROS version are you using? Do any native (Intel Driver) modes work? I assume 640x480 works as this is the default mode you would have booted into before selecting a higher resolution.

Lastly, what monitor do you have? Any chance of trying a different monitor?

Hi Neil, hope to catch up again at Amiga Ireland next month. OK...

I am using icaros desktop 2.2.4 (although the same thing happens with AspireOS and icaros desktop 2.2 beta (which I had kicking around on a disk) yes 640 x 480 works.

I have tried on 3 different monitors, an lg 19inch lcd 1366x768 native resolution, a Samsung Syncmaster lcd 1440x900 native resolution and finally an old miko crt that is good for up to 1280x1024. The all exhibit the same behaviour even at 1024x768@60hz. 😕

Kind regards

Craig



ncafferkey

  • Junior Member
  • **
    • Posts: 84
    • Karma: +34/-0
Reply #3 on: December 05, 2018, 06:41:12 PM
Oh, I didn't know it was you Craig :-) Yes, see you next month hopefully. I'll try to find time to check my machines that have Intel graphics with an external monitor, maybe this weekend. By the way, what kind of corruption are you getting?



paolone

  • Legendary Member
  • *****
    • Posts: 568
    • Karma: +90/-0
Reply #4 on: December 06, 2018, 09:08:55 AM
Craig, new user AndreaFK just wrote this in his presentation topic:
Quote
Only real glitch I'm getting is that the GMA driver doesn't seem to like 24 bit resolutions and corrupts the screen, it is wonderful at 16 bit
He's using a similar Atom board to yours. Would you please test if at least 16bit (65536 colors) resolutions work for you in native GMA mode?


CraigsBar

  • Newbie
  • *
    • Posts: 7
    • Karma: +0/-0
Reply #5 on: December 07, 2018, 05:31:56 PM
Craig, new user AndreaFK just wrote this in his presentation topic:
Quote
Only real glitch I'm getting is that the GMA driver doesn't seem to like 24 bit resolutions and corrupts the screen, it is wonderful at 16 bit
He's using a similar Atom board to yours. Would you please test if at least 16bit (65536 colors) resolutions work for you in native GMA mode?

Yes! That fixed it, damn awesome thank you so much.

😀



ncafferkey

  • Junior Member
  • **
    • Posts: 84
    • Karma: +34/-0
Reply #6 on: December 09, 2018, 11:24:45 AM
I tried the GMA driver with the VGA output of three of my netbooks/laptops. I didn't see any corruption at 1024x768@60 or any other resolution. I used Icaros 2.2.3 (confusingly, the About window still says 2.2).

What kind of corruption do you get? What's the PCI product ID of the graphics chip? Does the problem occur with older Icaros releases?



paolone

  • Legendary Member
  • *****
    • Posts: 568
    • Karma: +90/-0
Reply #7 on: December 10, 2018, 09:01:23 AM
I tried the GMA driver with the VGA output of three of my netbooks/laptops. I didn't see any corruption at 1024x768@60 or any other resolution. I used Icaros 2.2.3 (confusingly, the About window still says 2.2).

What kind of corruption do you get? What's the PCI product ID of the graphics chip? Does the problem occur with older Icaros releases?
Hi Neil, the problem occurs only at 24 bit resolutions, please try them with an external monitor.


ncafferkey

  • Junior Member
  • **
    • Posts: 84
    • Karma: +34/-0
Reply #8 on: December 10, 2018, 06:10:53 PM
Yes, I used 24-bit modes. Can you reproduce the problem Paolo?



nikos

  • Senior Member
  • ****
    • Posts: 374
    • Karma: +71/-3
    • aspireos
Reply #9 on: December 15, 2018, 04:00:36 AM
With IntelGMA and DELL D520 it is no problem with 24-bit screens using AspireOS.

Here is a video.

https://youtu.be/YZIemJ92kKg


paolone

  • Legendary Member
  • *****
    • Posts: 568
    • Karma: +90/-0
Reply #10 on: December 15, 2018, 10:48:14 AM
Yes, I used 24-bit modes. Can you reproduce the problem Paolo?
Sorry I don't own the same board where the GMA issue rised.

@NikosI'd refrain from advertising everywhere the fact that the IntelGMA driver works so well for the DELL D520: the complaining user does not own it and maybe it's not interested into purchasing one... 


nikos

  • Senior Member
  • ****
    • Posts: 374
    • Karma: +71/-3
    • aspireos
Reply #11 on: December 15, 2018, 10:54:09 AM
It is just a proof of concept.  Advertising?  I
Never earned a penny on aros and never will either. I like to help.  Now you know it is working on some hardware at least.  It is not a general problem.  That is what I wanted to show.