Hi,

I take it this is only for VirtualBox testing only as native AMD no other devices other than hubs detected?

No, it's mean to work on all hardware. It is simply that it is being developed first on VMs, because that's easier than developing on real hardware, however we would like to get reports how each version works on real hardware too and if there is a regression or improvement.

Hi,

Thanks

Finally has a few minutes to burn the CD and try this. First test is on my i5 lapttop, which does work with 'normal' AROS via USB2 but does have USB3 ports.

Booting from CD is fine and the xHCI system is seem both in Trident and PCITool (please see attached). In trident a new hub is shown which is labelled as 'superspeed'.

I attached a wireless dongle for a mouse and keyboard combo: all fine, both recognised and useable

Tried SFS formatted USB sticks: all fine, sticks are recognised, windows opeend and files accssed

Tried FAT formatted USB stick: stick is recognised but on trying to open there's a warning that the file system is corrupted. For one stick, the files could be seen but filenames were corrupted (seemingly random characters). On another, no files were displayed. Both sticks are fine under 'nromal' AROS.

Next attempt will be on a machine which has no USB access wih the normal system.

Cheers,
Nigel.

Which FAT did you use? The ideal one is the standard FAT32, which works perfectly on native PCs. I don't know if the problem is the USB3 port!

All ports were giving the same effect and with 'normal' 64 bit AROS they work fine with the USB2 driver. The format is FAT32. As mentioned, USB sticks formatted using SFS work with no issues, so that may imply it's something to do with how the USB3 driver invokes the FAT handler rather than a hardware or stack problem, although this is a pure guess.

Cheers,
Nigel.

Just tried my Acer Aspire. This machine will boot normal 64 bit with all working aside from the USB ports. With this experimental distibution the boot stalls at:

ehciHandleFinishedTDs/309: NAK timeout

Tried all booy options, same result, booting from CD.

Cheers,
Nigel.

A new ISO containing all the chages from last ISO till now:

https://build.axrt.org/download/builds/Experimental/exp-usb3-pc-x86_64-20260125-123947.tar.gz

@ntromans

Thanks for testing prevoius ISO on your hardware.

Hi,

Thanks, just tried and booted burnt CD on Native AMD Ryzen but the devices section in Trident only shows the hub (one entry) but no other devices detected when inserted.

I tested the experimental build with my notebook, but after Grub, the PC restarts and boots up with Windows.

These are the specifications of my PC:
- HP ENVY 15-k112nl
- Intel Core i7 i7-4510U
- 16 GB DDR3L-SDRAM
- NVIDIA® GeForce® GTX 850M

Test with new build:

i5 laptop (USB2 works with 'normal' 64 bit) - no change from previous release in that USB3 is recognised, SFS memery stick works fine but FAT32 is still corrupted (please see attached images).

Acer Aspire laptop (USB2 does not work with 'normal' 64 bit) - it now boots to Wanderer and USB3 hub is recognised (please see attached for PCITool output) and information on it can be opened in Trident. This is progress on the 'normal' distibution in that if you open Trident from that the machine quickly locks up. However, attached devices are not recognised i.e. do appear in Trident or work (HID or memory stick).

Cheers,
Nigel.

@ntromans
Could you make an image of your USB stick (what size is it?) I would like to burn it onto my USB stick and then try it on AROS!

Next time I boot up my Linux hard-drive I'll see if it has an imaging tool. In any case it's not specific to that memory stick - other FAT32 ones give the same issue.

Cheers,
Nigel.

@ntromans

One request for futures cases: please export all PCI device information, not just for the single USB device. How other devices are recognized in system may have an effect on USB.

Please see attached for full PCI dumps for i5 and Acer laptops.

Cheers,
Nigel.

I tried to boot on an HP EliteBook 830, but it didn't work in either UEFI or legacy mode. Perhaps it's too recent

What do you mean by 'it didn't work'. Please be more specific how (from CD, from pendrive, which grub option selected) you were booting it and what was the result (black screen, insert media screen (cat's eyes), crash requester visible, etc)

I tried with the USB key in legacy mode and grub is visible. I select the first option and then a black screen appears. With the DVD in legacy mode, it starts up and then a colour artefact appears on the screen and it does not work.

Ok, for DVD select either second or third option and see if that gets you further

For USB, select second option and then add debug=serial to grub command line and capture what is on screen.

ok