AROS ABIv0 20201110 Development

[ncafferkey]

@ncafferkey
Can you test with IntelGMA and nVidea the attached game ? basically on my Acer Z5 when you exit the game the computer restarts !

On Acer Z5 in Window Mode it is quite fast, in Fullscreen it is slow

http://aminet.net/package/game/misc/MunchDude

I tested it under 2019-04-16 under IntelGMA. It crashed on exit with a guru. I can post a stack trace if it's useful. However, did you want me to test with the new files or ISO that Deadwood posted?

[ncafferkey]

@ncafferkey

If you have time, can you try previous releases to see when things got broken:

https://axrt.org/download/aros/v0/AROS-20161228-1-pc-i386-boot-iso.zip
https://axrt.org/download/aros/v0/AROS-20170402-5-pc-i386-boot-iso.zip
https://axrt.org/download/aros/v0/AROS-20180415-2-pc-i386-boot-iso.zip
https://axrt.org/download/aros/v0/AROS-20180423-1-pc-i386-boot-iso.zip

The 2016 build is good and 2017 is bad. I didn't try the 2018 builds.

BTW the symptom of this nVidia bug is that booting hangs on "[I2C] Init".

[ncafferkey]

@ncafferkey

Please try -D3. Possibly solves problem with "crash at exit" in 3D applications in IntelGMA.

https://axrt.org/development/AROS-20190429-D3-pc-i386-boot-iso.zip

Yes, gears and MunchDude no longer crash at exit

[deadwood]

@ncafferkey

If you have time, can you try previous releases to see when things got broken:

https://axrt.org/download/aros/v0/AROS-20161228-1-pc-i386-boot-iso.zip
https://axrt.org/download/aros/v0/AROS-20170402-5-pc-i386-boot-iso.zip
https://axrt.org/download/aros/v0/AROS-20180415-2-pc-i386-boot-iso.zip
https://axrt.org/download/aros/v0/AROS-20180423-1-pc-i386-boot-iso.zip

The 2016 build is good and 2017 is bad. I didn't try the 2018 builds.

BTW the symptom of this nVidia bug is that booting hangs on "[I2C] Init".

Thanks. I see if I can locate the problem.

[deadwood]

The 2016 build is good and 2017 is bad. I didn't try the 2018 builds.

BTW the symptom of this nVidia bug is that booting hangs on "[I2C] Init".

@AMIGASYSTEM

Did you get any error reports about nVidia driver not working from people using your distribution?

[AMIGASYSTEM]

No no message received for my latest AROS One v1.9, but I think because NVIDEA works fine.

I did some tests with AROS One 1.9 (in the screenshot you can see the AROS version) with an old laptop (CDC) of mine which has 2 Video Cards "NVIDEA GeForce Go 6600" and one "GMA", these are the results:

- NVIDEA GeForce Go 6600 -> Works perfectly tested the game "MunchDude" no problem either in Windows Mode or FullScreen, no problma in game output

- GMA (don't know the exact model) -> "MunchDude" works fine in Windows Mode, in Fullscreen problems in game output.


On this PC I replaced IntelGMA Video Driver with the version you fixed, results:

- GMA -> Windows Mode "Black screen", Fullscreen "Black screen", basically only music can be heard.

Screenshots NVIDEA GeForce Go 6600 :

[AMIGASYSTEM]

Screenshot GMA:

[deadwood]

@AMIGASYSTEM

Today I tried D3 on my old nVidia development computer and I'm getting the same issues as @ncaffekey. Booting with "native" drivers stops at some point. There is definitely some issue there, though it might be related to card model.

@ncafferkey what card model were you testing with?

As for integrating just the driver with AROS One v1.9 that won't work - other internal elements have changed as well.

[AMIGASYSTEM]

I booted my old CDC laptop including the 2 Video Cards with your latest Build AROS-20190429-D3 (booted from PenDrive) !

- NVIDEA GeForce Go 6600 -> "MunchDude" window mode Guru in output, full screen mode system lock in game output
- GMA -> Window mode all OK, full screen mode system lock in game output

I add that "ScreenRecorder" with NVIDEA GeForce Go 6600 goes into Guru

[deadwood]

Ok, I did a series of tests on my hardware. Seems like 6xxx is the latest series that works. Computer with nVidia 8xxx series is already failing to boot using D3 and even previous release.

[deadwood]

@AMIGASYSTEM

The problem with "crash at exit" in Nouveau has been found and will be fixed in D4

[ncafferkey]

My 3D-supported nVidia card is reported by PCI Tool as “GT200GL [Quadro FX 3800]”. The numbering may be unusual as it’s a workstation card.

[AMIGASYSTEM]

I remember that there were a lot of variation even between Cards of fixed PCs and Laptop PCs, I had encountered this when I was i managed many PCs in my corporate network.

The other PCs I have at home do not have a supported video card:
AMD Radeon HD 5440
NVIDIA GeForce 8600M GT
Intel HD Graphics (card integrated into the motherboard)

[deadwood]

@ncafferkey

I looked into the freeze issues and it is quite strange. Seems like setting these attributes

Code: [Select]

            { aHidd_PCIDevice_isIO,     FALSE },    /* Don't listen IO transactions */
            { aHidd_PCIDevice_isMEM,    TRUE },     /* Listen to MEM transactions */
            { aHidd_PCIDevice_isMaster, TRUE },     /* Can work in BusMaster */

freezes the whole computer. I think this is somehow related to PCI-E devices. A lot of other drivers are setting them for PCI devices. Nouveau is also setting them for AGP cards and there is no problem. Problem seems to be only with PCI-E. There were changes on 2017-03-20 to pci/pcipc related to IRQ routing, which might be the problem. If you had similar issues in the past, let me know.


EDIT: Hmm, looks like adding noacpi boot option "solves" the problem for me. Can you try your hadrware?

[ncafferkey]

@ncafferkey

I looked into the freeze issues and it is quite strange. Seems like setting these attributes

Code: [Select]

            { aHidd_PCIDevice_isIO,     FALSE },    /* Don't listen IO transactions */
            { aHidd_PCIDevice_isMEM,    TRUE },     /* Listen to MEM transactions */
            { aHidd_PCIDevice_isMaster, TRUE },     /* Can work in BusMaster */

freezes the whole computer. I think this is somehow related to PCI-E devices. A lot of other drivers are setting them for PCI devices. Nouveau is also setting them for AGP cards and there is no problem. Problem seems to be only with PCI-E. There were changes on 2017-03-20 to pci/pcipc related to IRQ routing, which might be the problem. If you had similar issues in the past, let me know.


EDIT: Hmm, looks like adding noacpi boot option "solves" the problem for me. Can you try your hadrware?

"noacpi" works around the problem for me too. I did have some problems with PCI changes around that time. I think I fixed some of them on 2018-03-25, but IIRC it was related to problems I saw on my AspireOne.