lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 1 Mar 2019 22:52:41 -0500 From: "David R. Bergstein" <david.r.bergstein@...il.com> To: Larry Finger <Larry.Finger@...inger.net>, Tony Chuang <yhchuang@...ltek.com> Cc: Pkshih <pkshih@...ltek.com>, "linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Realtek r8822be kernel module does not negotiate 802.11ac connection Larry, Sorry about all these extra replies. Shortly after I sent my last message my access point started recognizing the connection as 802.11ac with PHY Rate / Modulation Rate of 866.6 Mbps. What is somewhat misleading is the information reported by iwconfig (see bit rate below). $ iwconfig wlo1 wlo1 IEEE 802.11 ESSID:"XXXXXXXXXX-5G" Mode:Managed Frequency:5.22 GHz Access Point: xx:xx:xx:xx:xx:xx Bit Rate=6.5 Mb/s Tx-Power=23 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:on Link Quality=70/70 Signal level=-40 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:11 Missed beacon:0 Sincerely, David R. Bergstein On 3/1/19 10:16 PM, David R. Bergstein wrote: > Larry, > > Please disregard my last message. The firmware is now installed and the > rtw88 module is working with my wireless router. The next hurdle > appears to be setting the speed to 802.11ac as it is currently > connecting as an 802.11n client. > > Sincerely, > > David R. Bergstein > > On 3/1/19 9:55 PM, David R. Bergstein wrote: >> Larry, >> >> Following up to your last reply, I blacklisted the r8822be module, >> rebooted and was unable to bring up the wireless interface via rtw88. >> Below are some errors recorded in my system log: >> >> >> [ 267.509818] rtw_pci 0000:3d:00.0: Direct firmware load for >> rtw88/rtw8822b_fw.bin failed with error -2 >> [ 267.509821] rtw_pci 0000:3d:00.0: failed to request firmware >> [ 267.511068] rtw_pci 0000:3d:00.0: mac power on failed >> [ 267.511072] rtw_pci 0000:3d:00.0: failed to power on mac >> [ 267.511073] rtw_pci 0000:3d:00.0: failed to setup chip efuse info >> [ 267.511075] rtw_pci 0000:3d:00.0: failed to setup chip information >> [ 267.512817] rtw_pci: probe of 0000:3d:00.0 failed with error -114 >> >> As directed, I used the rtwpci module to perform load/unload the rtw88 >> module before I saw the errors above. Do I still need to install firmware? >> >> Sincerely, >> >> David R. Bergstein >> >> On 3/1/19 8:46 PM, Larry Finger wrote: >>> On 3/1/19 4:26 PM, David R. Bergstein wrote: >>>> Larry, >>>> >>>> Thanks for the response and detailed instructions, which allowed me to >>>> build and install the rtw88 kernel module. I cannot however seem to get >>>> my system to actually use the module. Just to recap this is an HP Omen >>>> laptop with secure boot disabled. Upon boot-up both the new rtw88 and >>>> old r8822be modules are loaded. If I unload the r8822be module the wifi >>>> network connection gets terminated, even if I unload/reload the rtw88 >>>> module. >>>> >>>> Is there something else I should be doing prior to invoking rtw88, e.g., >>>> blacklisting the old module? >>> Yes, r8822be must be blacklisted. Use the lsmod command to see what >>> modules are actually loaded. You load/unload rtw88 using the rtwpci >>> module. >>> >>> Larry >>>
Powered by blists - more mailing lists