Software Support > GroovyMAME
GroovyMAME selecting modelines that my system doesn't like?
gabe:
--- Quote from: Calamity on July 06, 2011, 07:29:54 am ---I'd check if its only a problem with that exact modeline or rather it's a low dotclock issue. If you see the modeline generated for the cga monitor, it has a dotclock of 5.251606 MHz. I'd test games that have use a dotclock that's a little lower or higher, to see if they're affected too, i.e. argus (-monitor_orientation vertical) and toki.
--- End quote ---
Both games fail in a similar fashion to baddudes.
I gather that this post about Xorg ignoring dotclocks below 5mhz no longer applies?
Also - if it makes any difference, I'm launching from wah!cade.
Calamity:
--- Quote from: gabe on July 06, 2011, 01:34:33 pm ---Both games fail in a similar fashion to baddudes.
I gather that this post about Xorg ignoring dotclocks below 5mhz no longer applies?
Also - if it makes any difference, I'm launching from wah!cade.
--- End quote ---
Interesting, it would be good to see if there's a clear pattern, i.e. all modelines above a given dotclock work, and the ones below don't, etc.
All those dotclock issues were overcome by bitbytebit in the GroovyArcade build by means of different patches, which I can't remember right now, but lately I believe it was only necessary to patch the legacy Radeon driver, anyway if applying the same patches does not fix things in Arch Linux then maybe you should find all instances in the kernel where the dotclocks are checked.
gabe:
--- Quote from: bitbytebit on July 06, 2011, 06:52:13 pm ---
--- Quote from: Calamity on July 06, 2011, 04:28:24 pm ---
--- Quote from: gabe on July 06, 2011, 01:34:33 pm ---Both games fail in a similar fashion to baddudes.
I gather that this post about Xorg ignoring dotclocks below 5mhz no longer applies?
Also - if it makes any difference, I'm launching from wah!cade.
--- End quote ---
Interesting, it would be good to see if there's a clear pattern, i.e. all modelines above a given dotclock work, and the ones below don't, etc.
All those dotclock issues were overcome by bitbytebit in the GroovyArcade build by means of different patches, which I can't remember right now, but lately I believe it was only necessary to patch the legacy Radeon driver, anyway if applying the same patches does not fix things in Arch Linux then maybe you should find all instances in the kernel where the dotclocks are checked.
--- End quote ---
The newest versions of Xorg/ATI drivers with DRM enabled actually don't use that low dotclock value, since it's all built into the DRM layer of the kernel now instead of the xorg drivers. The kernel, if patched, should be the same as the ISO uses. Seems like something is not the same, but I'm not sure what it'd be. Actually odd certain games work and others don't. Yet if the kernel is right then that part shouldn't happen, since it's the central point all the modeline calculations are done.
--- End quote ---
6.162MHz seems to be the lowest dotclock my system will take. 5.911MHz and below results in a crash. I took the list of arcade modelines, and then searched MAWS for games by resolution. I then tested several games for each modeline in either direction of the 6.162MHz dotclock.
I'm using the same version of kernel, with the same patches applied as the ISO. I used a slightly different .config, so perhaps I should compare the two and take a closer look? If not, I suppose my next step will be to compare software versions on my Arch install to those on the ISO? ... Unless anyone has any better ideas?
Calamity:
--- Quote from: bitbytebit on July 06, 2011, 06:52:13 pm ---The newest versions of Xorg/ATI drivers with DRM enabled actually don't use that low dotclock value, since it's all built into the DRM layer of the kernel now instead of the xorg drivers. The kernel, if patched, should be the same as the ISO uses. Seems like something is not the same, but I'm not sure what it'd be. Actually odd certain games work and others don't. Yet if the kernel is right then that part shouldn't happen, since it's the central point all the modeline calculations are done.
--- End quote ---
However I remind the ATI drivers were picking those dotclock limits from the bios itself, at least for the legacy combios part that we had to patch. Could it be that the hd2600 bios template he's using in order to make the AVGA3000 work is different to the one you used?
gabe:
--- Quote from: Calamity on July 07, 2011, 03:48:26 am ---However I remind the ATI drivers were picking those dotclock limits from the bios itself, at least for the legacy combios part that we had to patch. Could it be that the hd2600 bios template he's using in order to make the AVGA3000 work is different to the one you used?
--- End quote ---
That shouldn't be the case, as I copied it directly from the Groovy ISO. The file in question should be hd2600.bin, correct?
If so, my hd2600.bin is the same exact size as the hd2600.bin found on the ISO. The only difference is permissions. Mine is:
--- Code: ----rw-r--r--
--- End code ---
While the ISO's is:
--- Code: ----rwxr-xr-x
--- End code ---
Am I wrong in assuming that this shouldn't make a difference? I can chmod and test when I get home.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version