@ncafferkey

B&C - expected at this point. It's an Ivy Bridge chipset, so the ports were all switched to xHCI now and pcixhci.device is not functional on those boards yet

A - is this a regression then for WiFi dongle? I was under impression that it worked correctly with 0331 build.

@deadwood

A: Yes, I think it's a regression since then. Would it be useful if I test the other builds you released in between? Did you manage to get a WiFi dongle yet?

C: Shouldn't the USB2-only port still work with this mode? The laptop has an EHCI controller, which I presume is attached to this port.

A: Hmm, that's weird. The only thing that should impact pciusb.device was included in 0409 build and it should only trigger with 4GB RAM or more. WiFi dongle -> not yet, focusing on pen drives for now.

C: Boards with dual host controllers (EHCI/xHCI) starting from Ivy Bridge have the ports connected to both of them. The changes I added in 0411 build now correctly take over xHCI controller from BIOS and make the xHCI take over all the ports it can (same is happening in Linux codes). This now makes these ports "dead", but once pcixhci.device start working on those boards, all the ports will work with it.

@deadwood

A: I'll double check with the 0331 build. I have 8GB RAM FWIW.

C: You're probably right, but two ports on this laptop are labelled as SS (superspeed), while the last one is labelled with a lightning bolt (and no SS), so I thought that last one might not be under the control of xHCI.

@deadwood

A: I found the problem with WiFi. This GRUB entry has debug=serial set. When I change it to just "debug", the WiFi dongle works fine.

Also, when I remove "debug" completely, I can still boot normally, i.e. the problem I had with the 2026-03-31 build of getting stuck on the media screen unless I added "debug" is resolved.

BTW, Bifteck didn't work for me after I set debug=memory.

Ok, great to hear the problem was located

Hi All,

New build and some visible progress:

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

In TEST B (USB3) mode:
- pendrive partition is now visible in boot menu
- booting from pendrive starts
- booting from pendrive crashes with filesystem error

This has been confirmed on folowing hardware:
- GA-H81M-S2V
- DELL OPTIPLEX 9020
- DELL LATITUDE E6430
- MSI H81M-E34

If you experience blank screen after selecting TEST B in grub, reboot, go to bootmenu, check if the DU0 partition is visible and if so, "boot without startup sequence". This should show you then the filesystem error.

@ncafferkey
Turns out E6430 has the same chipset as your DELL. What I have on that machine is a single USB2 port on the left side and two USB3 ports (with SS icon) on the right side. If I plug pendrive into USB2 port and select TEST C, then it turns out on this hardware the USB2 port is not take over by xHCI so the booting finishes and then I can use both USB3 ports for USB3 data transfers.

Hi,

Thanks, is this for Intel only USB3?

No, fixes in this build are generic and should work on any xHCI host. It's possible they will fix GET_DESCRIPTOR error on your Lenovo V155.

Hi,

Thanks. Option B, now fixed GET_DESCRIPTOR error on Lenovo V155. Able to detect usb stick, format usb and install to it. DU0: present. But boot stops and blank screen after choosing option B from usb stick.

Ah, good to hear that detection is also fixed on your hardware.

@deadwood

Yes, my laptop seems to have a similar layout of USB ports. However, with the new build, I also get the filesystem error when I boot from the lefthand port (which has no SS but does have a lightning bolt symbol).

Coincidentally, the only other PC I have with USB 3 ports is a Dell desktop with the same chipset.

Booting from USB3 is now here!

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

Keep in mind that in order to use USB3 you need to select second option in grub - AROS TEST B. Also make sure you use InstallAROS to install from ISO to pendrive - other methods are not tested. Please post your test results along with hardware description in this thread.

Known issues:
- mouse attached to USB3 has slow movements

As a reminder, if you want to support Kalamatee's work you can:
- Send him a direct donation to: kalamatee@gmail.com
- Donate through Ko-Fi: https://ko-fi.com/kalamatee

If you want to support my work on hardware drivers (will be split 50:50 with Kalamatee), you can:
- Send donation to https://www.paypal.com/paypalme/4deadwood


Booting from pendrive on USB3 has been confirmed on following hardware:
VirtualBox 7.2
QEMU
DELL LATITUDE 7390
DELL LATITUDE E6430
DELL LATITUDE E6540
DELL LATITUDE E7440
DELL OPTIPLEX 9020
GA-H81M-S2V
ASUS P8Z68V LX
MSI H81M-E34
MSI H110M PRO-VD
DELL 3330

Booting from pendrive on USB3 has been reported to fail on following hardware:
Lenovo V155
DELL 7010

Hi,

Thanks, V155 performs as before but the usb drive has blank output and the led on the drive flashes on and off for a long time. Eventually, switched off.

What you can do is to remove vesagfx.hidd from the kernel modules list. This way the video mode should not kick in and you might catch on the screen the error that is happening.

Amazing! Kalamatee is doing and incredible job and he really needs your support. Donating!

Hi,

Removed vesagfx.hidd but not showing anything after choosing option B just a blank screen and flash drive led flashing.

Just remembered I have this so tried on a Dell 7010 thin client with AMD based usb2 and NEC based usb3. Able to choose option B but get the awaiting boot media screen when plugged into usb3 port. Removed vesa again and no change.

deadwood, on my HP ENVY 15-k112nl, the USB 3.0 flash drive booted up, and Windows started after GRUB.
My HP ENVY 15-k112n has 3 USB ports, but it only boots from one of them; the other two ports are probably not USB 3.0.

With VMware, the USB 3.0 flash drive initialised correctly and the build installation was successful.

Just a minor issue with VMware: the initialisation (Wipe) needs to be performed twice; if you only perform one Wipe, the filesystem becomes corrupted upon restart.

Wait. So after choosing option B you don't get any text on screen at all? Not even AROS kernel startup banner and listing of ACPI tables?

You Dell 7010 - does booting work with pendrive in USB2 slot and option A selected in grub?

@AMIGASYSTEM

I have you system noted down as "restarts right after grub with USB2". I expect the same is happening with USB3.