OS/2, eCS & ArcaOS - Technical > Storage

oddities with OS2AHCI version 2.04

<< < (2/5) > >>

Dave Yeo:
You also might want to review your BIOS settings. Here, IIRC, I had to turn on the NX bit to get stable high memory usage (upper part of my 4GB). At least on my C2D, PAE seems to be tied to the NX bit.

Lars:
"memory check": I am using also Windows 10 64-bit on this very same HW. I have no apparent issues with it. At least not unexplicable crashes.

"setting NX" bit: I have no such option in my BIOS. I am not sure if my instability is limited to use of high memory. I had set VIRTUALADDRESSLIMIT to 512 MB and I still have these strange reboots etc.
I have the strong feeling that the amount of system memory matters. Unfortunately it is not all that easy to reduce it. And I bought it to be usable with a 64-bit OS like Windows 10 ...

Maybe there is an issue with AMD based systems ? You all seem to have Intel based systems.

What I also realised:
1) when I dump OS2AHCI$ to the console I have a lot of these entries:
port #0 interrupt error status: 0x40000001; restarting port

2) when I run "smartahci.exe -i hd1" and then dump OS2AHCI$ I get:
timeout for IORB da811ea (etc.)

I am beginning to believe that I cannot use OS2AHCI.ADD on this AMD based system.

ivan:
Lars,  while I don't have this latest OS2AHCI I have noticed that there is quite a number of things that are only just working on AMD processor systems.

It is almost as if testing on AMD systems is an afterthought or what units they use for testing are old ones (I would like to get ArcaOS working on my Ryzen 8 core system or even the A12 APU system but...) since it apparently works on Intel's latest and greatest.

David McKenna:
Lars,

  I have those port interrupt errors in OS2AHCI$ too, on all of my systems I've tried it on. At least here, it is always on the port where I have a DVD drive attached. I tried smartahci, then dumping OS2AHCI$ like you suggest, but I just see the interrupt errors along with the list of attached devices. You might try messing around with the switches on the driver. Here, I must use /!R or I can't boot. Maybe one of those will help. Also, I was able to eek out a little more physical memory (as seen at the top of a 'testlog generic') by lowering the video memory in BIOS. Maybe tweak on that (up or down) and see if there are any changes.

Neil Waldhauer:

--- Quote from: ivan on December 16, 2017, 10:58:42 pm ---Lars,  while I don't have this latest OS2AHCI I have noticed that there is quite a number of things that are only just working on AMD processor systems.

It is almost as if testing on AMD systems is an afterthought or what units they use for testing are old ones (I would like to get ArcaOS working on my Ryzen 8 core system or even the A12 APU system but...) since it apparently works on Intel's latest and greatest.

--- End quote ---

I'm one of ArcaOS tean of volunteer testers. I don't have any AMD systems. ArcaOS does not work at all on Intel's latest and greatest. I did provide Arca Noae with an Intel system that didn't work at all, and they made improvements to some of the IBM components that extended support. I don't have the resources to cover all systems, and neither does Arca Noae.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version