|Ok, so far we've seen a number of folks who got their hands on the V4SA at the A34 show, some of whom are having issues. This thread is to help bring together information to help those users get things up and running. Note that I don't have a V4SA yet, but I spend a lot of time in the IRC chat and here on the forums and have tried to compile what I have seen so far. |
PLEASE add to this any information you find or learn from the team as they help you so it can help others!!!
Currently the USB ports are only designated for mouse and keyboard use. The mouse MUST be plugged into the front port (near the joystick ports), keyboard in the rear (near the ethernet). Please try to use the provided ones from the A34 package FIRST as those have been tested to work. Others may or may not work (USB compatibility expansion is being worked on). Try with the provided first to ensure the system is working right before trying others. If you find ones that work, please post to this thread with the specific model numbers so the Wiki can be updated.
Note, currently DB9 Amiga mice do NOT work (although this might be reenabled in the future). For now, leave your old tank mice hooked to your classic hardware and stick with the USB mouse provided.
Video problems -
Some folks are experiencing problems getting anything to display on their device. This is typically because your display can't deal with the resolution/frequency that the system is trying to push out.
Some things to try:
1) with only the keyboard, mouse, power and DIGITAL-VIDEO hooked up. Try turning on the unit and going into the early boot menu - Power on while holding both mouse buttons. Hold them for 4 seconds and then release.
This should get you into the early boot menu which is a pretty low-resolution/standard res display. If you're getting this, then video works, but the system is trying to go into a display mode your display can't handle.
2) If that doesn't work, try changing to a different DIGITAL-VIDEO cable and/or a different monitor. Computer monitors tend to allow for many more resolution modes than consumer TV's, so if possible try on them.
3) see below about updating the core and SAGA drivers.
Updated Core -
The devices were sold with a core that is slightly out of date. There is a newer version that you can try which might fix some issues (it has for some). If anyone has the link to where you can get the new core, please post below as I don't have that information.
Updated SAGA drivers
There is a newer version of the SAGA drivers that have been published to the wiki. You should install them in whatever OS image you're using. See: EXTERNAL LINK
If you can't seem to get the system to boot up at all, you might need to install these drivers via plugging your CF card into a UAE system and then installing the drivers onto it from there.
Currently the Ethernet port does not work. This is known - the team decided this was not a critical feature to have working prior to release. It is being worked on though. Wifi should be possible in the future via interfacing something like an ESP32 board to the V4SA's expansion ports, but a driver will need to be written that doesn't currently exist.
Changing the Kickstart
The units ship with AROS' kickstart. It is possible to change this to 3.1 or 3.1.4 or some other version, just like it's possible to do on the V2 boards. A new MapRom tool is coming that will work with the V4SA to do this. But for now you'll need to stay on AROS.
As stated above, hope this helps clear up confusion and gives some help on how to get things started. If anyone has additional information, please include it below to help others.