Software Support > GroovyMAME
GroovyArcade live-CD 2022 (collaborative effort)
Banane:
Happy new year :cheers: . Really looking forward to your updates ;D
What "channel" is the best for giving testing feedback ? This thread here, your github-repo or the 'new' gitlab repo ? :)
Test-Setup (see attached picture)
* Board: Asrock a320m-hdv
* CPU: AMD Ryzen 5 2400G (integrated AMD Radeon Vega 11)
* Graphic: 1x 2GB Sapphire Radeon R5 230 PCIe, using VGA-Out, 1x HD6450 1GB PCIe, using DVI2VGA-Adapter
* HDD: 970 EVO Plus NVMe M.2 SSD, 250GB
* Monitors: Computer CRTs + several arcade monitors (Hantarex, WellsGardner etc.)
Test1 / Script Autoconfiguration: : Just used a SVGA-CRT on VGA of PCIe-R230, selected SVGA/LCD. Result see attached picture. (Connector war detected, video card doesnt support EDID, no monitor detected). The same with the HD6450 with DVI2VGA-Adapter.
Is there a shortcut I can use too see the output to tty1 'behind' the graphical menu ? Itīs not tty7 (Edited: Oh well, I can parse /var/log/groovy.log ::) )
Test2 / GA-Installer on NVMe SSD: : Autoformat /dev/nvme0n1 doesnīt work. Partitions are created but I guess the root partition (e.g /dev/ nvme0n1p3) is not formatted correctly. When I repeat the setup, use the auto applied partition layout from the last step and install to root partition (/dev/ nvme0n1p3) manually, arch is installating correctly and I can boot from HDD. What script is called here? In what logfile can I see the output (or again, is there a shortcut to see the output on tty1? ). The Installer says itīs copying the files to /dev/nvme0n13 instead of /dev/nvme0n1p3 - so I guess itīs just a parsing error of the script :applaud: )
-------------------------------------------------------------
(Edited: I'm no developer, but I got this far:
grep -rnw '/' -e 'Copying Groovy'
nano /opt/gasetup/core/procedures/interactive
--> worker_auto_partition()
--> line: mkfs.ext4 -F -O ^64bit -q ${DEVICE}${ROOTNUM}
which leads to /dev/nvme0n13
How about ?:
ROOTPART=$(fdisk -l ${DEVICE} | awk '{print $1}' | grep ${ROOTNUM})
mkfs.ext4 -F -O ^64bit -q ${ROOTPART}
which would lead to /dev/nvme0n1p3
-------------------------------------------------------------
Substring:
Hey Banane thank you for your feedback ! And Happy new year ;)
For test 1, there is a minor bug that has been solved since : the final result should have said "Connector VGA-1 was detected". I've fixed this bug a little while ago, haven't pushed yet the changes. What I'd like you to confirm is :
- have you heard the voice speaking ? You may not have turned your speakers on haha
- has your monitor been turned off, turned on and you could confirm it was your arcade monitor ?
For the "video card doesn't support EDID", it means you're not using a AMD/RADEON card, but this seems false. I think there was also a bug regarding this that I haven't pushed yet ... Now a small question : do you know if your GPU uses the amdgpu or radeon driver ? Don't rely on the lsmod result, I load nouveau i915 amdgpu and radeon from initramfs to get the splash logo. Have a look at dmesg.
Next thing I'd like you to test is starting the frontend right after the monitor setup.
Just for a general information : SVGA/LCD means a monitor tha has EDID (or DDC) capabilities ;)
Regarding test 2, I've already filled an issue on my side regarding the non detection ov NVMe SSD. I wouldn't mind you try the command listed there and give me the result. Regarding the partition name, it's just a display, so it's a minor bug ;) But your fix looks right. I haven't done much in gasetup for a while
Substring:
Happy News Year everyone :)
Been working hard on linux kernel patches during December, leaving GroovyArcade a little aside ... I'll go in a few technical details for people who are interested into that.
So, while testing this beta release, I was looking for a way to dynamically force an EDID. After some kernel code reading, a few commands here and there : bingo! This IS possible. But this wasn't possible everytime and got me quite confused, until I narrowed down to the precise case where forcing EDID doesn't exist : using the 15k modelines patched into kernel. It took me a few weeks of debugging + kernel compilation + patching to find the root cause of that. And the root is indeed the 15k patch. Despite it provides some 15kHz resolution, it has 2 major drawbacks : it blocked the EDID on-the-fly loading + the 15k modeline wasn't "advertised" by DRM. Although most people wouldn't care about EDID reloading, the second problem mislead everyone to believe that setting EDID at boot time was the way to go (see http://forum.arcadecontrols.com/index.php?topic=140215.0).
A little patching here and there in the kernel code confirmed that the 15k patch was a little too brutal and had to fit better how DRM processes resolutions. So I've rewritten the 15k patch and results are great : I have plug'n'play X when I use a switchres resolution at boot time! That's a major leap forward for 2 reasons. The 1st reason is that this new patch is much better integrated into the kernel, cleverly handles situations where the kernel fallbacks to old GTF resolutions when none was found. The second reason is that it respects modelines validation (at DRM level, and at driver level), so in the end, DRM advertises the 640x480i (or any other resolution the 15k patch handles) at sysfs level, making it available to any software including X. Xorg gets the 640x480i resolution from the kernel and natively uses it, no need to go anymore the EDID way!
But in Linux we're facing another major problem. Although Radeon GPUs (please note I'm not saynig AMD GPUs, we have no clue on them yet) have always been considered the best for 15k display (and this is true), Intel or NVIDIA are a much different story. 15k resolutions are rejected by the drivers. It's hard to tell if it's because Intel or NVIDIA decided 31.5kHz would be the minimum horizontal frequency, or if it's to avoid some hardware problems (like a DAC that can't handle such low resolutions, or refuses interlace), but I'm also digging on how to make them work. Looks like I could get this done for NVIDIA, gotta test in Intel too. Once again, when this seems like it can be tested, I'll publish a beta ISO :)
So, not much happened on GroovyArcade itself, but there are some major breakthroughs that GA will soon benefit hopefully :)
Banane:
--- Quote from: Substring on January 02, 2020, 03:49:33 am ---For test 1, there is a minor bug that has been solved since : the final result should have said "Connector VGA-1 was detected". I've fixed this bug a little while ago, haven't pushed yet the changes. What I'd like you to confirm is :
- have you heard the voice speaking ? You may not have turned your speakers on haha
- has your monitor been turned off, turned on and you could confirm it was your arcade monitor ?
For the "video card doesn't support EDID", it means you're not using a AMD/RADEON card, but this seems false. I think there was also a bug regarding this that I haven't pushed yet ... Now a small question : do you know if your GPU uses the amdgpu or radeon driver ? Don't rely on the lsmod result, I load nouveau i915 amdgpu and radeon from initramfs to get the splash logo. Have a look at dmesg.
Next thing I'd like you to test is starting the frontend right after the monitor setup.
--- End quote ---
Iīve tested it on a regular LCD monitor now, youīre right, itīs just the output which is not correct. The monitor itself is detected, the config is created. I will just wait for your update/pushes :)
* I can start the frontend afterwards with no problem.
* Monitor war turned on and off - with an arcade monitor I can test later
* There is no voice speaking, no. Speakers are turned on
* Radeon driver was used (lspci + dmesg)
--- Quote ---Regarding test 2, I've already filled an issue on my side regarding the non detection ov NVMe SSD.
--- End quote ---
I answered the issue in gitlab :). Thanks
Substring:
Wow, thank you for all that positive feedback. My kernel hacking is almost over, so I'll spend more time on groovyarcade now.
Thanks to your report on gitlab, I know that I can safely detect all hard drives. For the worker_auto_partition(), I'll see how to solve that part. Your code has a little problem with devices like mmcblk3 or nvme0n3 if such ever exist. And I wouldn't use fdisk for that, blkid is a much better tool in that case ;) Can you try as root (or just sudo blkid):
--- Code: ---DEVICE=/dev/sda
ROOTNUM=3
blkid | cut -d ":" -f1 | grep -oE "${DEVICE}[[:alnum:]]?${ROOTNUM}$"
--- End code ---
Looks fine on my side.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version