I've taken some pictures of the boot, these is the cab with the ArcadeVGA 9250, right before mode switching:
1.- (using AVGA BIOS mode)
... and this is right after mode switching, sorry for the bad quality:
2.-
The one with HD4350, has split screen at point 1, and no video at all at point 2. It's connected via DVI-VGA (the 9250 is connected via VGA only). What makes me suspect of the EDID thing is that it seems this 4350 is really turning video off, no signal at all, it's not out of sync or anything. I'll try again with this one this evening, probably will plug the network cable to see if I can do ssh (no idea of what I should type however, I'll read the latests posts as it's probably been explained already).
Today I brought a mouse with me to test the first cab (9250) and finally was able to get into Wahcade. Video looks really nice inside X Windows. However, when I select a game, I expected some error message not finding the roms, but what happens is that X Windows exits to the console with an error message. By the way, during setup I mount /dev/sda1 as the roms drive but I can't figure out how to teach it to just point to C:\Roms\Mame.
I think this sequence will allow you to access it with ssh possibly and start X Windows to look at the 4350 remotely...
1. boot up (give it a while)
2. push enter
3. type eth0
4. push enter
5. At this point should be able to ssh into box, password for root is 'arcade'
6. push enter
7. push enter
8. type h9110
9. type 1
10 push enter
you will want to look at possibly the output of the 'dmesg' command when your ssh'd into it (ssh root@IPADDRESS to access it, password above). That's one issue but the other is concerning too with the video off center horizontally like that. Is it possibly a bad modeline, it should be this...
# 640x480@60.00 15.6300Khz
ModeLine "640x480x60.00" 13.004160 640 664 728 832 480 482 488 521 -HSync -VSync interlace
Although in theory it's the same as in X Windows so if that works then somehow the DRM layer is messing with the console video for the frame buffer I'm guessing. Possibly I need to use 320x240 I guess because it avoids interlace and maybe the frame buffer just isn't great at interlaced modelines, hopefully 320x240 is safe. Is there any better modeline resolution you think would be a good console one without any interlacing?
on the 9200 box, you can when in the console after it crashes, check /var/log/Xorg.0.log by running (less /var/log/Xorg.0.log) first of course choosing the menu option for the command prompt, and possibly see what is going on there. If you have network access possibly sending me that file, transfering it to another system with (ssh -rC /var/log/Xorg.0.log user@system:) first.
The rom directory probably doesn't have to be mounted/mapped for now to test because I have the default free roms from mamedev there right now to test with, but if you do map a drive it looks in the roms directory on that drive (so /data/roms/, where your drive is mapped to /data/). I have a new layout file showing the layout in the GIT repository I just uploaded and also am starting to get support for configuring links to where ever the actual roms/artwork is and lnking it properly. Here's the basic layout of /data/ right now that Wahcade looks at...
#
# Default directory layout for WahCade
#
## ROMS
/data/artwork_all
/data/samples
/data/roms
/data/biosroms
/data/Games/NES
/data/Games/SNES
/data/Games/Coleco
/data/Games/N64
/data/Games/C64
/data/Games/Atari2600
/data/Games/SegaGenesis
#
## Snap shots
/data/screen_shots/NES/snaps
/data/screen_shots/SNES/snaps
/data/screen_shots/Coleco/snaps
/data/screen_shots/N64/snaps
/data/screen_shots/C64/snaps
/data/screen_shots/Atari2600/snaps
/data/screen_shots/SegaGenesis/snaps
## Mame control/info files
/data/ctl
## Mame snapshots
/data/mrq
/data/cab
/data/fly
/data/cat
/data/pcb
/data/ttl
/data/prv
/data/ico
I do have the configuration menu able now to save all the information entered upon new boots and even auto find the home directory chosen after it's been setup, and since the config is saved there, then can read that and probably just boot into X Windows after 1 setup. I really would like to try and get away from using the console for anything but when your in console mode at first it's the root administrator user so it can do all the configuration from there, then I startup X Windows as the arcade user so it's non-privileged after that point. I might figure out a way to do it though so in X Windows the configuration can be done although that gets into the issue of needing to know the monitor type first
Definitely some tricky stuff to figure out with all that, but I am seeing it definitely harder to support card/arcade monitor/TV/monitor combinations than I had thought at first, and hopefully having a more basic generic console mode for at least Arcade monitors (and need ones for TV's in NTSC/PAL too) will make it work for both your cards (seems like that linux kernel change for interlacing might be to blame so getting away from interlaced consoles would be nice).