Software Support > GroovyMAME
GroovyArcade live-CD 2022 (collaborative effort)
Substring:
So, time for monthly news before kernel 5.4.1 and groovymame 0.216 are integrated.
Except unuseful things to mention, I've been working pretty hard on a script to "auto-detect" screen configuration. So this made me reduce the number of entries in the syslinux boot menu, as well as remove EDID menu options. So we're just left with 6 entries: 15kHz, 25 kHz, 31kHz, LCD, NTSC and PAL. Don't just shout yet with "Hey DVI-1/VGA-1/etc is now missing, my screen will never be detected!", and read till the end ;)
This script I told about will first turn on all video outputs (yeah mister sceptical, even the ones that are missing from the boot menu!), make sure you do see the very first message, then test outputs one by one in a clever way. If it detects an EDID, we know for sure a screen is connected and working. If you have a EDID dongle with a switchres edid in it, you shall be blessed! Every time a screen is turned on, a message is displayed for 5 seconds waiting for the user to confirm he sees the message. If no key was pressed, it means no message could be displayed, so no screen is connected. At the end, once all outputs have been tested, time to take decision on which screen seems the best, and what should be configured inside the OS to have it working. Icing on the cake: depending on your GFX card, the script will eventually recommend using EDID emulation.
The sad thing is that it won't hit the 2019.12 release, there is still much to be done. But once this is over, I can work on improving user experience (things like configuring wifi which is a total pain for now, add desktop UI where possible so people don't have to browse through some menus). And I'm still working on a desktop version of the gasetu script. Working rather fine I'd say, but having a tool that works the same on console or desktop implies some rewrites here and there, which takes time, as usual ...
If some people would like to test that auto-detect script, I can provide a link and instructions on how to use it. I did my best to test all possible cases, but I'm pretty sure I missed some.
Doozer:
Well done Substring, thank you for your time and efforts. Much appreciated :)
Calamity:
Hi Substring,
These days I've been experimenting with Ves around the EDID emulation option too, I still need to check whether forcing the EDID on all outputs (which works great on detectable monitors) actually works or not on non-detectable monitors. I'd like to test your auto-detect script too, I'm really interested.
Substring:
Regarding EDID emulation, here is my feedback:
- works fine with traditionnal radeon driver
- got no card to test amdgpu driver
- i915 seems not to work
- nouveau seems not to work unless patched (to remove the low dotclock limit warning). I asked Doozer his opinion on a patch I sent him, I'll let him tell his opinion about it. Even though I could get EDID emulation working, I had (much) tearing that I never had with radeon.
To be continued ...
I'll give the testing process once I get enuogh time to write a little tuto ! The script can even suggest kernel command line parameters to add ;)
On a side note, it's sad we're splitting our efforts each on our side regarding EDID emulation. I can tell you it works, that you don't even need to configure X after (at least on a TV that was seen by Linux, I don't have the case where the monitor is not detected by the OS). EDID emulation can be forced system wide, not just specific to a connector. We should really share our experiments and results in a more efficient way and not waste time this way ... Remember the name of the topic : "collaborative effort" ;)
Calamity:
--- Quote from: Substring on November 28, 2019, 06:26:03 am ---On a side note, it's sad we're splitting our efforts each on our side regarding EDID emulation.
--- End quote ---
I'm doing what's in my hand to avoid this splitting of efforts, trust me.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version