Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Announcements: #armbian-announcements | Developer talk: #armbian-devel | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
zeemate has quit [Ping timeout: 248 seconds]
jantones has quit [Remote host closed the connection]
axochitl has joined #armbian
axochitl has quit [Remote host closed the connection]
califax has quit [Read error: Connection reset by peer]
califax has joined #armbian
axochitl has joined #armbian
DC-IRC has quit [Remote host closed the connection]
DC-IRC has joined #armbian
nodelay has joined #armbian
nodelay has quit [Ping timeout: 248 seconds]
buzzmarshall has quit [Quit: Konversation terminated!]
nodelay has joined #armbian
nodelay has quit [Ping timeout: 248 seconds]
Mangix has quit [Read error: Connection reset by peer]
Mangix has joined #armbian
ikmaak has quit [Read error: Connection reset by peer]
marco44 has quit [Quit: ZNC 1.9.1+deb2+b3 - https://znc.in]
marco44 has joined #armbian
marco44 has quit [Client Quit]
marco44 has joined #armbian
Net147 has quit [Ping timeout: 248 seconds]
Net147 has joined #armbian
Hammdist80 has joined #armbian
<Hammdist80>
hey all. if you will remember I had various troubles trying to get USB WiFi adapters to work with my rpi5, and today I troubleshot it, so I will write the solution here for if others run into the same problem
<Hammdist80>
the adapter I have that is working now is tp-link archer t3u, plugged into a usb3 port (I haven't tested the now working solution with other configurations but I suspect it would work in usb2 port also)
<Hammdist80>
my problem was I was testing with iwconfig+dhclient -1 and the connection was unstable and eventually froze within a few minutes. when I switched to bringing up the wifi interface with nmtui, it started working. the reason for this discrepancy is unknown
agl has quit [Ping timeout: 252 seconds]
agl has joined #armbian
Hammdist80 has quit [Quit: Client closed]
<Hammdist>
maybe the underlying problem is that it's not supported to manually configure interfaces when also running networkmanager, unless they have been excluded from management somehow. but it's fine to use nmcli for me