Software Support > GroovyMAME
GroovyArcade live-CD 2022 (collaborative effort)
Doozer:
--- Quote from: Substring on November 04, 2019, 04:51:11 pm ---Going the EDID way is just awesome, because you don't even need a xorg.conf ! X will detect the monitor EDID, and use the preferred resolution from it.
--- End quote ---
Xorg configuration might get a little tweak with the compositor layer being not used. This COULD lead to 1 frame lag gain (someone with high speed camera or lag tester must confirm this, some windows manager like openbox do not use composition). Page flipping and shadowing options might also give some boost when vblank is properly synced (internal buffer reduction to 1 page, drawing must be synced to vblank like GM does).
--- Code: ---Section "Extensions"
Option "Composite" "Disable"
EndSection
--- End code ---
The X layer over Mir has recently received massive updates and some reports claim that X over Mir has reached the same latency as standalone X. To be investigated ....
Doozer:
@substring, please consider adding "mitigations=off" to the kernel parameters, it will give a little non-negligible boost by not mitigating CPU vulnerabilities (spectre and other). I do not think that some has sensitive or confidential data to protect on their cabinet.
Substring:
--- Quote from: Doozer on November 06, 2019, 04:32:25 am ---
--- Quote from: Substring on November 04, 2019, 04:51:11 pm ---Going the EDID way is just awesome, because you don't even need a xorg.conf ! X will detect the monitor EDID, and use the preferred resolution from it.
--- End quote ---
Xorg configuration might get a little tweak with the compositor layer being not used. This COULD lead to 1 frame lag gain (someone with high speed camera or lag tester must confirm this, some windows manager like openbox do not use composition). Page flipping and shadowing options might also give some boost when vblank is properly synced (internal buffer reduction to 1 page, drawing must be synced to vblank like GM does).
--- Code: ---Section "Extensions"
Option "Composite" "Disable"
EndSection
--- End code ---
The X layer over Mir has recently received massive updates and some reports claim that X over Mir has reached the same latency as standalone X. To be investigated ....
--- End quote ---
Already added ;) Although i made a typo in the filename (which doesn't prevent X from loading the file). And Xorg.log reports fine that composition is disabled
--- Quote from: Doozer on November 06, 2019, 04:39:32 am ---
@substring, please consider adding "mitigations=off" to the kernel parameters, it will give a little non-negligible boost by not mitigating CPU vulnerabilities (spectre and other). I do not think that some has sensitive or confidential data to protect on their cabinet.
--- End quote ---
We share the same mind, I thought about adding this. Just wanted to refactor the syslinux.cfg file ... but sadly, syslinux globals just don't work the way I'd expect. So will have to add it to each entry ...
BTW, I sent you a PM for a kernel patch for Nvidia cards, please read and reply :) I tried the same for i915, but this isn't enough to get 640x480i working with EDID. I'm not sure it works with patched kernel resolutions, will try some day.
Doozer:
--- Quote from: Substring on November 06, 2019, 05:18:35 am ---BTW, I sent you a PM for a kernel patch for Nvidia cards, please read and reply :) I tried the same for i915, but this isn't enough to get 640x480i working with EDID. I'm not sure it works with patched kernel resolutions, will try some day.
--- End quote ---
I replied to it from the email. I assume my answer did not reach you.
To sum-up, I have an Intel and Nvidia patch sets but I am looking at making this more agnostic to the card drivers and just touching the drm helper or pruning function. Such patch must be tested against several chips and setup references to ensure that no collateral effects could arise from such modifications.
Stock kernel shows different behaviors with respect to EDID and the last kernel drm refactoring brought a lot to unify and normalize the calls. Nevertheless, ATI EDI do not check low dot clock the same way Nouveau does inside their respective driver branch.
Again, totally avoiding kernel patching might not be possible. E.g. without patching the ATI vblank interrupt, using any interlaced resolution under GM will be cap to 50% game speed.
It might be necessary to have a staging version which would have under development features. Personally, I do not own enough different configurations to confirm good working conditions in relation to non ATI hardware. Even for the ATI portion I am mostly using the 5000 generation chipset. I am also looking forward to getting in touch with the AMDGPU to see if newer generation can bring some good setup (i.e. Ryzen)
Substring:
--- Quote from: b4nd1t0 on November 06, 2019, 04:25:05 am ---the, gfx card to monitor is a simple vga connector to jamma (RGB+V and H sync) and jamma to monitor, nothing special, my video card is flashed with Atom-15, and the electronic is an Hantarex Polo28.
I think, to use edid i need to apply some resistances to the connector, i have read about this some years a go but never made it, if it works, is ok for me :D
I've tried the default EDID at boot menu, but i have black screen and no, i don't have edited the syslinux.cfg, you mean the one in \boot\syslinux\ ?
The problem in attract is strange, i have my usual hdd with groovy and it work fine, menu and games, with your iso only attract is out of sync
--- End quote ---
OK, reading your setup, your Polo 28 doesn't have an input impedance that allows the GFX card to detect if a monitor is connected. That's why the resistors trick could do the job. It has a small downsize though : birghtness is (a bit) lower. Just for info, Here is the EDID VGA dongle I bought and flashed with a switchres EDID. It does have the required resistors. They are 150 Ohms each. Here is a little article that describes the resistors hack.
Anyway, by tweaking your /boot/syslinux/syslinux.cfg file, you could use EDID by forcing the DVI-I to be enabled, as described earlier.
Now for the Attract problem, I need a little more details :
- do you have a nice splash boot screen with the progress bar before reaching attract ? (this means the resolution chosen works fine, X is not yet loaded)
- which monitor have you chosen in gasetup ? (to have a clue of X resolution)
- If you're OK with SSH and your cab has network, can you remotely login to your cab and give me the output of DISPLAY=:0 xrandr ? (to know which resolution was set)
- You mentionned LXDE : was it displaying fine even if menus are empty ? (to make sure that it's only an attract issue, LXDE and attract share the same X config)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version