F5F Stay Refreshed Software Operating Systems Unable to generate a hotspot with Nobara using the Archer T6E AC1300.

Unable to generate a hotspot with Nobara using the Archer T6E AC1300.

Unable to generate a hotspot with Nobara using the Archer T6E AC1300.

C
CarmellaYT
Junior Member
Find
13
03-18-2021, 10:25 AM
#1
Hi everyone, I'm using Nobara 38 with KDE and have a Broadcom Wi-Fi card installed. I'm running Windows 10 alongside Nobara on separate drives with no shared partitions. The distribution didn't include drivers for the card, so I looked through forum discussions and installed the broadcom-wl drivers via dnf. When I checked the device list with lspci -nn -d 14e4: I saw a matching adapter (Broadcom 802.11ac). My card connects to my router and phones but can't create a hotspot from the PC. I don’t use terminal commands for hotspots—I just click the Hotspot option in the Network system tray. Whenever it fails, notifications appear. I also tried setting up a shared Wi-Fi network through KDE Settings’ Connectivity page, which gave the same message.

PC Specs:
- CPU: AMD Ryzen 5 3600
- GPU: AMD Radeon RX 6600
- RAM: 2x8 GB at 3600 MHz
- Storage: 1 TB NVMe M.2, 1 TB SATA 3 x 6 GB/s
- Power: Corsair RM650 80+ Gold

Could someone help resolve this issue or explain why it’s happening? Thanks.
Reply
Reply
C
CarmellaYT
03-18-2021, 10:25 AM #1

Hi everyone, I'm using Nobara 38 with KDE and have a Broadcom Wi-Fi card installed. I'm running Windows 10 alongside Nobara on separate drives with no shared partitions. The distribution didn't include drivers for the card, so I looked through forum discussions and installed the broadcom-wl drivers via dnf. When I checked the device list with lspci -nn -d 14e4: I saw a matching adapter (Broadcom 802.11ac). My card connects to my router and phones but can't create a hotspot from the PC. I don’t use terminal commands for hotspots—I just click the Hotspot option in the Network system tray. Whenever it fails, notifications appear. I also tried setting up a shared Wi-Fi network through KDE Settings’ Connectivity page, which gave the same message.

PC Specs:
- CPU: AMD Ryzen 5 3600
- GPU: AMD Radeon RX 6600
- RAM: 2x8 GB at 3600 MHz
- Storage: 1 TB NVMe M.2, 1 TB SATA 3 x 6 GB/s
- Power: Corsair RM650 80+ Gold

Could someone help resolve this issue or explain why it’s happening? Thanks.

Reply
Reply
F
flyer78
Senior Member
Find
425
03-18-2021, 10:33 AM
#2
Consider exploring alternative tools like the one shared here.
Reply
Reply
F
flyer78
03-18-2021, 10:33 AM #2

Consider exploring alternative tools like the one shared here.

Reply
Reply
L
Lebko
Junior Member
Find
12
03-25-2021, 11:38 PM
#3
Check the official Fedora documentation for installation details. Since it’s not listed there, look for Fedora-specific guides or community resources. You might need to use a different package manager like yum or dnf if available.
Reply
Reply
L
Lebko
03-25-2021, 11:38 PM #3

Check the official Fedora documentation for installation details. Since it’s not listed there, look for Fedora-specific guides or community resources. You might need to use a different package manager like yum or dnf if available.

Reply
Reply
M
Mr_Floobiful
Posting Freak
Find
890
03-26-2021, 04:14 AM
#4
The Fedora setup guide is correct. The DNF information seems uncertain, but a quick search confirms it should already be included in the system.
Reply
Reply
M
Mr_Floobiful
03-26-2021, 04:14 AM #4

The Fedora setup guide is correct. The DNF information seems uncertain, but a quick search confirms it should already be included in the system.

Reply
Reply
C
Cupcake_Rose
Posting Freak
Find
844
03-30-2021, 11:21 AM
#5
I assembled the entire device and installed it on Fedora. Then I executed the wihotspot command through the GUI. Initially, I encountered an error indicating failure and recommended trying the no-virt mode. I reviewed the No Virt section in the UI and noticed a message appearing in the terminal after running pkexec. If you see a similar warning like 'n80211: Could not configure driver mode', please run the following steps before launching create_ap: nmcli r wifi off rfkill unblock wlan.
Reply
Reply
C
Cupcake_Rose
03-30-2021, 11:21 AM #5

I assembled the entire device and installed it on Fedora. Then I executed the wihotspot command through the GUI. Initially, I encountered an error indicating failure and recommended trying the no-virt mode. I reviewed the No Virt section in the UI and noticed a message appearing in the terminal after running pkexec. If you see a similar warning like 'n80211: Could not configure driver mode', please run the following steps before launching create_ap: nmcli r wifi off rfkill unblock wlan.

Reply
Reply