ASUS ROG STRIX B860-G GAMING WIFI manjaro kde installation

Hi,

Bought a new pc with ASUS ROG STRIX B860-G GAMING WIFI.
Lots of startup messages regarding usb and wifi.

Any suggestions for the manjaro kde installation for adjusting bios or drivers ?

0.555128] RAS: Correctable Errors collector initialized.
[    7.147827] usb 3-14: device descriptor read/64, error -110
[   21.570059] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy component didn't bind within the expected timeout
[   21.570080] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC proxy handler failed to init
[   22.721128] usb 3-14: device descriptor read/64, error -110
[   28.481233] usb 3-14: device descriptor read/64, error -110
[   44.054451] usb 3-14: device descriptor read/64, error -110
[   55.234245] usb 3-14: device not accepting address 9, error -62
[   66.327589] usb 3-14: device not accepting address 10, error -62
[   68.412761] mt7925e 0000:85:00.0: probe with driver mt7925e failed with error -5
[   68.481320] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.RP01.PXSX._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184)
[   68.481324] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477)
[   68.481326] ACPI Error: Aborting method \_SB.PC00.RP01.PXSX._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529)
[   68.831592] ACPI BIOS Error (bug): Failure creating named object [\_SB.PC00.RP01.PXSX._DSM.USRG], AE_ALREADY_EXISTS (20240827/dsfield-184)
[   68.832021] ACPI Error: AE_ALREADY_EXISTS, CreateBufferField failure (20240827/dswload2-477)
[   68.832345] ACPI Error: Aborting method \_SB.PC00.RP01.PXSX._DSM due to previous error (AE_ALREADY_EXISTS) (20240827/psparse-529)

Before pulling up the big wallet - always research the linux support.

I just looked up the board - the wifi doesn’t have Windows 10 driver - only drivers for Windows 11 25H2 - so Linux support may be flaky - if existing at all…

thanks for your effort.
After the messages as described the system starts after a long time.

I am guessing this is the wifi ?

I found a lot of references - mt7925 seems to be a hit or miss - possibly depending on the vendor implementation.

It looks like you need Linux 6.18 to get it working

Based on this I’m thinking so.

Edit:

I don’t know if this is related, but see

https://www.reddit.com/r/ASUS/comments/1kbucgx/rog_strix_b860g_gaming_wifi_latest_bios_no/

:bangbang: Tip :bangbang:

When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:

```
pasted text
```

Or three (3) tilde signs, like this:

~~~
pasted text
~~~

This will just cause it to be rendered like this:

Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.

Instead of like this:

Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.

Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.

Thereby increasing legibility thus making it easier for those trying to provide assistance.

For more information, please see:

As I’m a moderator on the forum, I have taken the liberty of doing this for you, this time.


:bangbang::bangbang: Additionally

If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:

LC_ALL=C bluetoothctl

This will just cause the terminal output to be in English, making it easier to understand and debug.

Note that the above text is partially pre-prepared as a general introduction for new forum Users. Please take the time to to understand how it is done and encourage quality responses.

@stormschip! I’d expect you to know this already!

German source found: https://forums.linuxmint.com/viewtopic.php?t=365572

USB error -110 means “Timeout before the transfer was completed,” which can be caused
by a number of things. Most often, it’s due to power limitations;
the host couldn’t provide enough power to operate the USB connection.
Also, the USB device might not be able to send the device descriptor to the host
due to insufficient power, and therefore can’t be identified, and so on.
Perhaps your motherboard is overloaded with devices that are consuming all the available power.
.
Could it be a power-saving mechanism in the BIOS?

These warnings could be indicative of a mainboard that’s simply “too new” for general Linux compatibilty to be accounted for in kernel. Perhaps later iterations may be helpful, though one can only speculate without sufficient information provided.

No results here for the mainboard - perhaps there might be some better luck identifying compatibility of individual parts.

This can never be overstated.

Disable Secure Boot, Disable i-GPU if you have a dedicated one, disable TPM, disable Wifi if you can use a Lan-cable (RJ-45).

And use the latest ISO with the newest available Kernel.

2 Likes

Don’t forget about the Intel iGPU. I’ve never had unsupported wifi cause such trouble. And I get USB errors left and right with no issues with them (I have a lot of devices).

Might be worth trying:

/etc/modprobe.d/i915.conf


options i915 enable_guc=3

As you’re on the brand new gen Intel chipset, as people are saying, long shot maybe?

(And you can just blacklist the wifi module. Or am the only one that wires his desktop anymore!)

You are not alone - I am wiring everything that can be wired :slight_smile:

7 Likes

Hi,
The hardware:

ASUS ROG STRIX B860-G GAMING WIFI
Intel Core Ultra 7 265K - Processor
Corsair Vengeance - DDR5 - 64 GB: 2 x 32 GB
MSI GeForce RTX 5060 8G VENTUS 2X OC
CORSAIR RM650e
Arctic Freezer 36 
3 x Samsung 990 Pro 1TB
1 x Samsung 990 EVO Plus 4TB SSD

And you’re not the only one. Always wire if possible.

Then you can blacklist both i915 and mt7925e.

Hi did all the suggestions but the result was the same.
Systeem took a long time to boot, Udev starts immediately generating usb messages
Installed even the linux618.

And those modules you blacklisted still throw errors?

What’s taking the longest?

systemd-analyze blame

The whole journalctl -b --no-pager while it boots (with timestamps) may help; though it will be quite large. Just until you this slow boot more or less completes.

I don’t see any reason it shouldn’t work, but maybe that’s just my optimism today. (Maybe not working optimally, or taking full advantage of your new tech, but still better than your old one!) But I haven’t dealt with Arrow Lake yet, at least on this level. At least the kernel’s been dealing with P-cores and E-cores since 5.18.

I assume intel-ucode got installed?

That CPU should be supported as it’s over a year old. There’s a way to figure it out if you have the signature(sig) from the above journalctl logs. It should look something like:

kernel: microcode: sig=0x000806c1, pf=0x80, revision=0x2e

(But the logs should tell you if it is working anyway..)

intel-ucode is installed and the
systemd-analyze blame shows the fstrim.service takes up 5 seconds.
the systemd modules take up 2.4 so guess not that spectacular.

I contacted the vendor and hope they will react soon.
They advised me wrong. linux-aarhus already said no drivers for this motherboard.
The only thing it can store three nvme’s and i was hoping to use zfs for a mirrored home pool

If you come up with new suggestions (including hardware)much obliged and thanks for the input.
Which is for all forum members who reacted

https://linux-hardware.org/?view=search

Hi,

No hits

Use it for research to know what’s good and what’s not.

would you consider installing hw-probe

sudo pacman -S hw-probe

then run

 $ sudo hw-probe -all -upload
Probe for hardware ... Ok
Reading logs ... Ok
Uploaded to DB, Thank you!

Probe URL: https://linux-hardware.org/?probe=bc141820b2