Groovy Arcade never completes loading from USB?

[Spicules]

Loaded 64-bit vers onto a 16gb USB stick earlier today.  Seems to go without a hitch, except for that it took like 40 minutes to install.

Loaded it up - the logo comes up, the progress bar starts to move, and then it goes REALLY slow.  It took about 10 minutes for it to travel across the screen from left to right and then it seems to sit.  The planet in the back ground is still moving, but it doesn't seem to load. 

This rig that I have plays stuff fine in windows without any excessive load times or anything...  Not sure what to do.  Any help greatly appreciated as I have not been able to use the Arcade VGA fully, yet. 

I have the following specs:

AMD 64 3000+
1GB Ram
AGP Arcade VGA
MSI K8MM   
NEC xm29 multi-sync monitor

[Calamity]

Hi Spicules,

This is a known bug related to the splash screen. As soon as the logo appears, press Escape to exit to text mode. Then it will load fine.

Once loaded, get into gasetup, Video Setup/Video Grub to disable the splash screen permanently.

[Spicules]

Hitting Esc worked - I can get everything working... EXCEPT...

I get the following error:

USB 1-1 Device not accepting address #, error -110
ERROR: UNABLE TO FIND ROOT DEVICE ...  you are being dropped to a recovery shell.
Type 'exit' to try and continue booting
sh: Cannot access tty; job control turned off

[26.. (bunch of numbers)] usb 1-1: device descriptor read/64, error -110


I can type exit, and it looks like it tries to read another usb device.  If I keep doing this, it eventually clicks and loads GA. 

I know nothing about linux (hence why I got GA!) but is there a way to tell it the correct address of GA or whatever it needs to stop the searching?

[Calamity]

Hi Spicules,

Well, I don't know if BIOS boot sequence order could influence on the install process and later use. In case it does, I always set is in this oder: 1-USB, 2-CD, 3-HDD

Anyway, it could be simply that your USB has become corrupt when turning your computer off when it crashed after splash, and you need to reinstall the system. This has happened to me on the past, although my error messages were different.

[Spicules]

Thank you for your response. 

I have reinstalled the system and I am still getting the same error:

"usb 2-4 device descriptor read/64, error -110"

This error popped up at the bottom of the screen when I was using GRUB to reinstall the system to the usb.  It will repeat, and I can type "exit" to attempt to boot.  After a couple tries, sometimes it works, othertimes it does not. 

[Calamity]

Could it be the same problem?

http://ubuntuforums.org/showthread.php?t=1610142

[Spicules]

Could it be the same problem?

http://ubuntuforums.org/showthread.php?t=1610142

Tried unplugging like it said - still get the same problem.  I was going to reinstall, but when I started, I was getting the same error in the installer, so I don't think that will help. 

[Calamity]

Anyway, for what you can find on google, that error seems to be related to the usb power. Won't you have another pendrive to test with?

[Spicules]

This is the second pen drive.  The first stopped being recognized by windows and GRUB after I tried a few re-installs to it. 

I am thinking maybe it is this motherboard?  I also tried using a USB pci card, but my bios does not recognize it as a bootable device if plugged in there.  I will if plugged into the motherboard's usb slots though.