Y Axis missing steps on 300K+ line program

I tried the 4th axis again but with the Mesa card.
It appears everything is working and it even got me to figure out the 6i25. It's not that difficult but a basic set of steps would help as it's been years since I've done much with Linux.

I'd like to attribute it to either a slightly blown driver and/or 3.3v parallel port voltages coupled with step timing on the G540--which some people found to be of issue which I found through a few hours of research. I did attempt to increase step hold time.. I think it's QC of drivers couple with the lower yet still spec sheet voltage.

I do have a new complication which occurs after 30-45 minutes of use and everything works as I've memorized the keyboard shortcuts but this is less than ideal. I did read I shouldn't use more than a 1gb of ram (?) and I recently upped it to 4gb so perhaps I should swap it back to 2gb, should see if I can update drivers with the integrated drivers, and/or throw in a GT730 to see if that'll fix the issue.

Can't think that the integrated graphics would be going out and I do not within the GUI allow AXIS to draw everything as that slows the FPS/response time down.

image missing https://i.imgur.com/gYeQm5X.jpg

That looks like a syncing issue, so first check the cable and make sure it is working properly and properly inserted.
Had plenty of such issues with HDMI cables, never with DVI except when not properly seated.
And you can have as much memory as you can cram into it. Where did you get the 1Gb thingy ? That is not correct.

Thank you for clarifying my problem.
I'll try to get a DVI or SUB-D connected to it as I attempted to once there was a syncing issue but perhaps it needs this change to occur before boot.

I think I misinterpreted this "384 MB of RAM (512 MB up to 1 GB recommended)" from the minimum requirements page.

DVI or Display port if you have them, Sub-D is analogue so the picture is not as sharp as with the other connections.

I wanted to give you my final update on this issue.
Eventually I called Mesa Electronics and spoke to them about the G540.
They told me Geckodrive's minimum timing on their spec sheet doesn't work and it really should be more around 3000 or higher.

Basically it involves the fact that the optoisolators aren't individually binned and so they all act slightly differently--so that's why one axis may or may not trigger properly at the specified timing.

All considered he mentioned that you can easily turn the timing up to even 10000 and this wouldn't be an issue if one went overboard.

I think years back people were doing "sherline mode" and perhaps I got a unit that needed longer timing for it to work consistently.
Thus far I've got 3-4 hours of use at 3000 timing and no issues at all.
Machine sounds a little smoother and it's getting me through.