ath10k_pci failed the read device register, device is gone

Installation
1

Hello everyone. This is my first post to this server. Firstly I want to take a minute to thank all of you for your dedication to the project and time that you spend helping others. Especially in a wold here time seems to be short. I have home assistant installed on an old DELL laptop I have kicking around. I have made some bios changes ad version 17.1 “latest at this time” seemed to have some issues loading bluetooth. So I disabled that and it seems to be fine. The problem I have is with WIFI. The error in the title seems to present after, Lets ball park 6 hours. This kills the network and the only fix is to reboot the HAOS.

If I look in
/usr/lib/firmware/ath10_k/QCA6174
I see 2 directories HW2.1 Feb 10 137k and hw3.0 Feb 10 279kb

I managed to find a full driver set at Debian -- Details of package firmware-atheros in forky
The drivers I downloaded are from this DELL KB article How to Update Killer Wireless Firmware on Ubuntu Systems | Dell Australia

I have FTP the dirve set to the OS in /mnt/data/supervisor/addons/local/temp/QAC6174

I want to try a different firmware than what is installed on HAOS but the problem is that the file system is read only. I have tried to boot with a ubuntu USB and force mount the file system on nvme0n1p7. I can only mount the file system in Read only mode. It willl not mount as RW.

As this HAOS is on a laptop. I have keyboard, Screen and can login directly as the root user.
Does anyone have any ideas on how I might complete this task?
The above is a repost that I posted on Discord Hardware. Sinse then I have disabled power management on the WIFI adaptor in NetworManager. Currently testing to see if it fails again.

2

Well logging into root in HAOS is not a simple thing, so I bet you are not at root.

What install method did you use for installing HAOS? Can you return this? Link to System info – My Home Assistant

Also, HAOS is closed and is designed to be as lightweight as possible to be able to run on minimal hardware configurations. Since in HAOS you have no control over the OS itself, you cannot install extra things.
When you update HA any changes you managed to make will be gone.
If you really need to install drivers and hardware, consider using the Container install method or a VM where you retain control of your OS.

3

The recommended way to connect HAOS is via a wired Ethernet and I suspect most here including me will tell you that is the best way. If you do want to go down the unsupported Wi-Fi route I’d suggest getting a natively supported USB Wi-Fi adapter and disable the built in, you may also be able to swap the internal card.

Personally I’d move the laptop and hard wire. Not sure you will get very far trying to change the driver and if you did it may break again next update.