Wifi Qualcom Atheros is not working in Manjaro KDE

[megavolt]

Here is the problem:

@Justin47

[   13.111054] ath10k_pci 0000:02:00.0: failed to iomap BAR0
[   13.111133] ath10k_pci 0000:02:00.0: failed to claim device: -5
[   13.111240] ath10k_pci: probe of 0000:02:00.0 failed with error -5

Error No 5:

$ LANG=C errno 5
EIO 5 Input/output error

Anything blocked it or it is not properly initialized… Maybe FastBoot is enabled on the UEFI?

[Justin47]

@megavolt

Maybe FastBoot is enabled on the UEFI?

I disabled fast Boot in Windows 10 few days ago. But, there is no fast boot option in the bios menu when uefi is selected.
I selected legacy in bios and I disabled it there.

But, Now I face a even bigger problem manjaro boot menu doesn’t appear and Pc boots straight to Windows. This problem persists even after selecting the usual uefi in bios.

I’ve had manjaro installed in before too, but this problem happened to me before and I had to format and reinstall this version wel, that’s scary
I tried restoring previous Snapshot using timeshift, but it still would not load boot menu.

[Fabby]

@Justin47

I selected legacy in bios and I disabled it there

Revert that change: changing to legacy means reinstalling…

By now I’m thinking a partly working WiFi card (half of a hardware failure) and it’ll break down in Windows soon too…

[Justin47]

@Fabby

Revert that change: changing to legacy means reinstalling…

I reverted back to uefi already and did os-prober and update-grub. But still there is no way of booting onto manjaro. I faced a similair problem before formatting the disk will be somewhat depressing

@Fabby

By now I’m thinking a partly working WiFi card (half of a hardware failure) and it’ll break down in Windows soon too…

Then getting a network adapter would be a good move right? I’ll do that.
But I am more afraid of being unable to boot manjaro. What should I do now?

[Fabby]

@Justin47

But I am more afraid of being unable to boot manjaro. What should I do now?

That’s a completely different topic, and there are a few tutorials:

[Fix] Can’t login - black screen & chroot guide

Original author on old forum @AlManja If you are stuck and you can’t log into your system, use one of these steps below. They are sorted from easiest at the top. Start with the first step and if it doesn’t work, try with the next one and so on… Once you get access to the system, then proceed with updating the system or installing/removing packages, checking log files… Steps (you only need one) are: 1 - log to tty terminal 2 - boot without X 3 - chroot auto (with manjaro-chroot) 4 - chroot …

[How To] Save your Manjaro installation when it breaks

Difficulty: ★☆☆☆☆ Post original authored by Heart-Of-A-Lion Some of you might have had it happen, a Linux installation on your computer that breaks after installing certain software, after installing updates or after editing a configuration file. Sometimes you mess up so bad, that the entire system doesn’t boot past Grub or doesn’t even boot Grub itself if you messed around with its configuration files. So what can you do when you really messed up big time? What if you didn’t make that Clon…

[megavolt]

Maybe this works for you:

Its bit silly but it works follow me.
Please Install your Linux OS in EFI Mode otherwise this will not work.

1. Go to the UEFI Settings and navigate to BOOT Menu
2. Set the boot mode to Legacy Support and boot priority as UEFI first
3. Things to ENABLE:

• Fast boot → enable
• PXE boot to LAN → enable
• IPV4 PXE LAN first → enable

4. In EFI priority Setting,use F6 or f5 to make it
   move EFI PXE Network (xx-xx-xx-xx-xx-xx) to first
   move your to second
5. Don’t forget to save changes: Press F10 and select Yes

Source: Lenovo E41-25 Wifi not working only in any Linux-English Community

[Justin47]

@Fabby

That’s a completely different topic, and there are a few tutorials:

saw your guides, they were useful. At first, I literally thought that i am going to loose all data in this installation. This problem happened to me before ( 3 weeks ago), I asked a repairshop person and he said formatting is the way to go. But now , after some googlig, I learned to use efibootmgr. Each and everytime I switch uefi and legacy , the boot order gets reset and Any non-windows installation gets no priority in the boot list.
Assigning higher priority to manjaro and updating did the trick.

While googling , I happned to stumble upon one of your articles:

[HowTo] become a Manjaro power user when you're a wizard at Windows but a N00b at Manjaro / Linux

Difficulty: ☆☆☆☆☆ Remember when you installed your very first Windows, added bells and whistles and then couldn’t see the wood for the trees any more and had to re-install? Well, you’re in the same situation now: You’re a N00b again! Embrace it! I know right now you’re thinking:

Why is this so much more difficult than Windows?

[image]

Whereas in 6 months time, you’ll be like:

Why can't I make Windows jump through fiery hoops like I do with Linux???

<a class="lightbox&qu…

It was useful and I like how your writing style was fun and interactive

[Justin47]

@megavolt

Maybe this works for you:

I did just as you said. On booting I got checking (media > fail) two times.

And then… HOLY LOGOS!!! I was perplexed to see the network icon change to wifi. It is working really great.
Infact, I am writing this post using that connection.
Thanks a million, @megavolt
I really really appreciate your help

I am curious, why did the wifi not work before? Did it not work because of being on bottom of boot priority?

[Justin47]

@megavolt
@Fabby
@Yochanan

Thank you everyone for helping me . You guys are so smart and kind . I learned lots of new things through this thread and I Hope to repay the community by helping other users after I gain more experience in linux.

[megavolt]

@Justin47

I am curious, why did the wifi not work before? Did it not work because of being on bottom of boot priority?

No idea why. But the kernel messages said, as quoted above, that the driver has no access to the wireless card (I/O Error). And since that worked, I would rather think that the UEFI is buggy and does not initialize it unless it is triggered on boot time first by “PXE Network”. I believe there is a workaround for windows implemented on the UEFI, but since Linux is not officially supported, it runs into the bug and have had no access to it.