Vortex86 DX PC104 computer boot issues

[Demolishun]

Hello,
I have a TC install using the latest iso on an 8GB Sandisk Cruser USB drive.  I am able to boot up on a Atom based car computer and everything works just fine.  However, on my target machine which is a Vortex86DX PC104 it boots up, but the /dev/sda is not detected and is never mounted.  I set the waitusb=10, but that did not help.  It is the same USB stick in both machines. 

I thought I had this working before, but I think I was only testing on the Atom.  I do have the options in the bios to select booting from USB.  It sees the device in the bios as a Cruzer USB stick of 8GB.  It does boot to a prompt, but it never sees the rest of the disk.  I can tell I am not seeing it as files are missing in opt.

Are there additional boot options I need for the Vortex86DX?  I did see in the forum there may be issues with memory mapping, but would that cause this issue?

[gerald_clark]

It may using a USB controller that has no driver in the TC kernel.
My VortexDX ( eBox2300 ) is supported for everything but the wifi.
Some models use a non standard CF interface.

[Demolishun]

I have been testing and it does pick up the USB sometimes.  I did go and set the usbwait=20 just to give it more time, but when it does detect the disk it does it within 1 to 2 seconds.  I also set the bios to wait for usb disk detection of 10 seconds.

So right now it periodically boots and sees the disk, but most of the time not.  So I think it has a driver for it, but it just is flaky.

[gerald_clark]

Try a different thumb drive.

[Demolishun]

I tried a different 8GB Sandisk with a unetbootin install of the CorePlus iso and it has the same result.

I also tried a 4GB Sandisk with a default install of the CorePlus iso using the TC_Install app and it has the same result.

Neither of these configs would detect the drive other than the initial boot disk boot.

[Demolishun]

I have been choosing ext4 in all configs.  Do I need to try ext2?  Should that even make a difference?

[tinypoodle]

No, difference not expectable.

Does your USB storage medium have a partition table? (Asking because you mention /dev/sda)

[curaga]

Please post dmesg from both cases (boot where it's not seen, and a boot where it is seen).

[Demolishun]

@tinypoodle,
Yes.  It is installed on /dev/sda1.

@curaga,
Okay, I have no way of getting the dmesg output off the machine for when it fails.  But I noticed at the start that it shows ehci failure -110.  Then I looked at the dmesg | grep ehci and it showed that one of the controllers is failing.  The other controller is working.  So I am going to switch the USB connector to use the other controller.  If it causes it to fail then it is a wiring issue.  If not then it is probably a controller is having issues.  I will get back to you on this really quick to let you know what it was.  I don't know if it uses 2 different USB controllers or not.  It could be the board is damaged. 

[Demolishun]

@curaga,
I just tried the other usb controller and it just hangs after the message of being a non recognized CPU type.  So it is working even less well than the other controller that sometimes works.  I just don't know what to make of that.  Evidently there are some usb issues with this board.

The board is from here:
http://www.advantech.com/products/PCM-3343/mod_645A1E17-167A-4476-B253-CA4CF2E19428.aspx

It is this model: PCM-3343F-256A1E

The usb looks built in to the processor: DM&P Vortex86DX

[gerald_clark]

Reset your BIOS to safe settings and try again.

[Demolishun]

I tried resetting the bios to no avail.

I just ordered a Atom based PC104 board.  I will revisit this later as I have a deadline. 

Thanks for your help!

[Demolishun]

Got a Atom based PC104 card from the same vendor (Advantech) and put the same USB drive in.  Everything booted up and worked properly.  I don't know if this is a hardware (damaged) issue or a driver issue or some combination with the Vortex board.  However, I did not have time to figure this out right now.  Using an Atom based board solved the issue.