Open Ekiben542 opened 7 months ago
Opps... my guide did not show you how to edit ,config to turn on the RTW88 support for this adapter. My bad. Mine is compiling now which will probably take most of the night so let me check things and get a new guide to you.
By the way, the default .config was not compiling the support you need. RasPiOS devs generally only do with upgrades with LTS kernels and RTW88 came one kernel after the last LTS so the timing was not good.
I see. You don't have to rush.
I see. You don't have to rush.
What should have been easy is turning out not to be easy. The RasPi devs have made some changes. I keep telling them not to make changes without asking me first but that has not worked. Ha ha.
I need to start over.
I see. You don't have to rush.
What should have been easy is turning out not to be easy. The RasPi devs have made some changes. I keep telling them not to make changes without asking me first but that has not worked. Ha ha.
I need to start over.
I see. I'm sorry to hear that....
I'm sorry to hear that....
It is not a problem. I regularly do clean installs because of all of the work and testing that I do. It just slows things down.
I'm sorry to hear that....
It is not a problem. I regularly do clean installs because of all of the work and testing that I do. It just slows things down.
How are things so far?
@morrownr I ran the make command again and it worked fine with no errors.
dtb *dtb
test.
$ sudo cp arch/arm64/boot/dts/broadcom/.dtb /boot/ $ sudo cp arch/arm64/boot/dts/overlays/.dtb* /boot/overlays/ $ sudo cp arch/arm64/boot/dts/overlays/README /boot/overlays/
$ sudo cp arch/arm64/boot/Image.gz /boot/kernel8.img
Excuse me, is the above command really? (If you insert * or the like, the characters may be licked.) It's easy to understand if you wrap it in ```
@Ekiben542
Humble apologizes for taking so long. Let me finish testing this afternoon and get a new guide to you.
I was unaware that 2023-10-10 and later had made changes that required many changes in my guide. Other things have slowed me down. What you may want to do is burn a clean RasPiOS installation of the 64 bit version and get it updated and ready. The previous guide may have just messed things up.
@morrownr
/home/morrow/AppDev/Raspberry Pi/Upgrade_RasPiOS_Kernel/Compileand Install New_RasPiOS_Kernel.tar.gz
@Ekiben542
Here is the updated guide. Please let me know how well it works. If it works for you, I think I will add it to the Main Menu as others may want this guide.
@morrownr
Compileand Install New_RasPiOS_Kernel.tar.gz
Opps. here is the file.
I'll run it now.
@morrownr When checked with the uname -r command: Sometimes the USB flash drive is set to 6.1. 0 and sometimes to 6.6.7 (the USB flash drive is not recognized each time). What should I do?
Are you trying to boot a raspberry pi from usb? remove the SD card from the pi.
What should I do?
I am skeptical of booting with USB on the RasPi4B. I tried it at one time but was not happy with the results. The USB subsystem on the RasPi4B is problematic for a lot of reasons. The sd slot is fast enough for what the RasPi4B is capable of doing well and it is more stable. I recommend you grab a sd card and burn it.
Is it possible that I made a mistake on the guide? Yes. I did test it on a freshly burned sd and the results were good. Is it possible that my writing was not clear and you were unable to follow what I intended for you to do? This very well could be the case. It is a detailed process.
Let back up for a moment. I answer a lot of questions in different places on this site everyday that I am able so it can be hard for me to remember all of the details and this issue has drifted a lot since the beginning.
You have a RasPi4B running the 64 bit latest RasPiOS? Correct? You want to get a rtl8812bu based usb wifi adapter working with the in-kernel driver? Are you planning to use managed mode or master mode?
@morrownr
What should I do?
I am skeptical of booting with USB on the RasPi4B. I tried it at one time but was not happy with the results. The USB subsystem on the RasPi4B is problematic for a lot of reasons. The sd slot is fast enough for what the RasPi4B is capable of doing well and it is more stable. I recommend you grab a sd card and burn it.
Is it possible that I made a mistake on the guide? Yes. I did test it on a freshly burned sd and the results were good. Is it possible that my writing was not clear and you were unable to follow what I intended for you to do? This very well could be the case. It is a detailed process.
Let back up for a moment. I answer a lot of questions in different places on this site everyday that I am able so it can be hard for me to remember all of the details and this issue has drifted a lot since the beginning.
You have a RasPi4B running the 64 bit latest RasPiOS? Correct? You want to get a rtl8812bu based usb wifi adapter working with the in-kernel driver? Are you planning to use managed mode or master mode?
@morrownr
@morrownr
I will answer in order. RaspiOS (Lite) 64 bit is running. Yes. Trying to get it to work with AP (Could it work?)
Trying to get it to work with AP (Could it work?)
It should work. I am going to leave my PI4B as it is until you are ready to press on. Then we can set the AP up together
@morrownr Something strange is happening. I installed sl to test if it installed properly before installing, but it said that it had not install yet. In other words, the OS installation is not reflected for some reason?
Let's go over things:
I use:
https://www.raspberrypi.com/software/operating-systems/
Raspberry Pi OS (64-bit) Raspberry Pi OS with desktop Release date: December 5th 2023
I burn it to a 32 GB sd card with the Raspberry Pi Imager.
I use the version with the gui desktop because the gui desktop that RasPi uses is so light that it uses very little in terms of resources and some things are easier to do with gui apps and utilities.
I have updated and upgraded it and told it the WLAN country as well as some other things per the guide I posted. After running the guide, I see:
$ uname -r
6.6.11-v8+
phy#0
Interface wlan0
ifindex 3
wdev 0x1
addr 00:c0:ca:ad:de:9e
type managed
txpower 30.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcoltx-bytes tx-packets
0 0 0 0 0 0 0 0
That is from an 8812bu based adapter using the in-kernel 8822BU driver included in RTW88.
It is ready for me to start setting up AP mode for testing when you are ready.
Do you have any idea what is going on? Is this a clean installation? Are you using a sd card? Is the card or usb flash in good shape? Cards and drives go bad. I use really high quality cards to reduce problems.
@morrownr
では、詳しく見ていきましょう。
私は使用します:
https://www.raspberrypi.com/software/operating-systems/
Raspberry Pi OS(64ビット) Raspberry Pi OS(デスクトップ搭載) 発売日:2023年12月5日
Raspberry Pi Imagerで32GBのSDカードに書き込みました。
RasPiが使用するGUIデスクトップは非常に軽量であるため、リソースの点でほとんど使用せず、GUIアプリやユーティリティで簡単に実行できるものがあるため、GUIデスクトップのバージョンを使用します。
私はそれを更新してアップグレードし、私が投稿したガイドごとにWLANの国と他のいくつかのことを伝えました。ガイドを実行すると、次のように表示されます。
$ uname -r 6.6.11-v8+
phy#0 Interface wlan0 ifindex 3 wdev 0x1 addr 00:c0:ca:ad:de:9e type managed txpower 30.00 dBm multicast TXQ: qsz-byt qsz-pkt flows drops marks overlmt hashcoltx-bytes tx-packets 0 0 0 0 0 0 0 0
これは、RTW88 に含まれるカーネル内の 8822BU ドライバーを使用した 8812bu ベースのアダプターからのものです。
準備ができたら、テスト用のAPモードの設定を開始する準備が整いました。
何が起こっているのかわかりますか?これはクリーンインストールですか?SDカードを使用していますか?カードまたはUSBフラッシュは良好な状態ですか?カードやドライブが故障する。私は問題を減らすために本当に高品質のカードを使用しています。
@morrownr
I'm sorry to disturb you. I tried it a few times, and it took effect even after restarting. Thank you.
However, when I try to use the wifi signal, the message "Cannot connect to this network" appears.
I tried it a few times, and it took effect even after restarting.
I'll take this to mean that you are on kernel 6.6 and the adapter is showing a wifi interface?
However, when I try to use the wifi signal, the message "Cannot connect to this network" appears.
I need to know how you are setup. My Pi4B is headless. The only two wires going into my Pi is power and cat6 cable How about yours?
What are you trying to connect to? I assume you are using the Pi in client mode?
I tried it a few times, and it took effect even after restarting.
I'll take this to mean that you are on kernel 6.6 and the adapter is showing a wifi interface?
However, when I try to use the wifi signal, the message "Cannot connect to this network" appears.
I need to know how you are setup. My Pi4B is headless. The only two wires going into my Pi is power and cat6 cable How about yours?
What are you trying to connect to? I assume you are using the Pi in client mode?
From top to bottom: Yes. Only the cat6 cable, USB dongle, and power cable. Excuse me, what is client mode? (My understanding is that the Wifi function will be turned off and the Raspi side will receive the communication, which will be converted into a LAN and kept there.)
what is client mode?
Is your wifi adapter being used in managed mode to make a connection to an AP/wifi router?
My internet access comes in via cat6 cable so I was planning to take my wifi adapter directly into AP mode.
what is client mode?
Is your wifi adapter being used in managed mode to make a connection to an AP/wifi router?
My internet access comes in via cat6 cable so I was planning to take my wifi adapter directly into AP mode.
Is your wifi adapter being used in managed mode to make a connection to an AP/wifi router?
My internet access comes in via cat6 cable so I was planning to take my wifi adapter directly into AP mode.
The adapter is in AP mode. Communication is from the router. (So the situation should be similar.)
(So the situation should be similar.)
Okay. Then I will be using my AP guide located at:
https://github.com/morrownr/USB-WiFi/blob/main/home/AP_Mode/Bridged_Wireless_Access_Point.md
For now, I need to you hold off on following the guide as I need to do some modifications on the guide to differentiate between the in-kernel driver and the out-of-kernel driver. The part of the guide for rtl8812bu are currently only for the out-of-kernel driver and some things will change for the in-kernel driver.
As you can tell, I have not tested AP mode with the in-kernel driver. I will post when the changes have been made so for now, just read the guide and ask questions.
@morrownr
(So the situation should be similar.)
Okay. Then I will be using my AP guide located at:
https://github.com/morrownr/USB-WiFi/blob/main/home/AP_Mode/Bridged_Wireless_Access_Point.md
For now, I need to you hold off on following the guide as I need to do some modifications on the guide to differentiate between the in-kernel driver and the out-of-kernel driver. The part of the guide for rtl8812bu are currently only for the out-of-kernel driver and some things will change for the in-kernel driver.
As you can tell, I have not tested AP mode with the in-kernel driver. I will post when the changes have been made so for now, just read the guide and ask questions.
@morrownr
I see. I really appreciate your support. Thank you.
I really appreciate your support. Thank you.
You are welcome.
You are helping me also. You basically pushed me into updating my Guide for compiling a new kernel for the RasPiOS so now I need to find time to post it on the Main Menu. I'm also updating my AP guide so this is all good... but it goes slow as it takes a lot of work and I'm already busy on other issues.
We'll get it done.
@morrownr
@morrownr I've managed to get the AP up and running. However, it still says "Unable to connect to this network." Is there something wrong with the Archer T3U (the USB dongle I'm currently using)? (Maybe I'll switch to an Archer T4U Plus or something)
What is unable to connect, a phone? Try it without encryption (make the AP open).
What is unable to connect, a phone? Try it without encryption (make the AP open).
PC. I'll also try my smartphone. (I also try to open Wifi)
I can activate the AP and make the connection, Signal strength? I don't know what you call it (dbm). It doesn't change consistently, And after a few minutes, the SSID disappears... I checked hostapd and it doesn't seem to stop.
GNU nano 7.2 hostapd.log nl80211: Mode IEEE 802.11a: 5180 5200 5220 5240 5260[RADAR] 5280[RADAR] 5300[RADAR] 5320[RADAR] 5500[R>nl80211: Mode IEEE 802.11b: 2412 2417 2422 2427 2432 2437 2442 2447 2452 2457 2462 2467 2472 2484
hw vht capab: 0x3d071b2, conf vht capab: 0x3c001a2
wlan1: interface state COUNTRY_UPDATE->HT_SCAN
Scan for neighboring BSSes prior to enabling 40 MHz channel
40 MHz affected channel range: [5170,5210] MHz
wlan1: nl80211: scan request
nl80211: Passive scan requested
nl80211: Scan trigger failed: ret=-100 (Network is down)
nl80211: Set mode ifindex 5 iftype 2 (STATION)
nl80211: Failed to set interface 5 to mode 2: -16 (Device or resource busy)
nl80211: Try mode change after setting interface down
nl80211: Remove AP interface wlan1 temporarily from the bridge br0 to allow its mode to be set to STAT>nl80211: Set mode ifindex 5 iftype 2 (STATION)
nl80211: Mode change succeeded while interface is down
Could not set interface wlan1 flags (UP): Operation not possible due to RF-kill
nl80211: Failed to set interface up after switching mode
nl80211: Interface mode change to 2 from 2 failed
Failed to request a scan of neighboring BSSes ret=-100 (Network is down)
wlan1: interface state HT_SCAN->DISABLED
wlan1: AP-DISABLED
wlan1: Unable to setup interface.
hostapd_interface_deinit_free(0x55ac297630)
hostapd_interface_deinit_free: num_bss=1 conf->num_bss=1
hostapd_interface_deinit(0x55ac297630)
wlan1: interface state DISABLED->DISABLED
hostapd_bss_deinit: deinit bss wlan1
wlan1: Deauthenticate all stations
nl80211: send_mlme - da=ff:ff:ff:ff:ff:ff noack=0 freq=0 no_cck=0 offchanok=0 wait_time=0 no_encrypt=0>nl80211: send_mlme - Use bss->freq=0
nl80211: send_mlme -> send_frame_cmd
nl80211: Frame command failed: ret=-100 (Network is down) (freq=0 wait=0)
wlan1: AP-DISABLED
Excuse me for my long comment. It seems to have something to do with it, so I'll post it.
Post your hostapd.conf file.
Have you ever setup hostapd before? How are your networking skills?
FYI: The in-kernel driver and the out-of-kernel driver are not feature equal. Your ht capab and vht capab lines are likely wrong.
Did you follow my Bridged Wireless Access Point guide? I know it is a lot to take in if your experience level is low.
Post your hostapd.conf file.
Have you ever setup hostapd before? How are your networking skills?
FYI: The in-kernel driver and the out-of-kernel driver are not feature equal. Your ht capab and vht capab lines are likely wrong.
Did you follow my Bridged Wireless Access Point guide? I know it is a lot to take in if your experience level is low. OK.
# /etc/hostapd/Ohostapd-WiFi5.conf # Documentation: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf # 2022-09-25
ssid=myPI-WiFi5
wpa_passphrase=myPW1234
hw_mode=a
channel=36
vht_oper_chwidth=1
vht_oper_centr_freq_seg0_idx=42
country_code=JP
ieee80211d=1
ieee80211h=1
bridge=br0
interface=wlan1
driver=nl80211
beacon_int=100 dtim_period=2 max_num_sta=32 macaddr_acl=0 rts_threshold=2347 fragm_threshold=2346 send_probe_response=1
auth_algs=1 ignore_broadcast_ssid=0
wpa=2 rsn_pairwise=CCMP
wpa_key_mgmt=WPA-PSK
#
#
ieee80211n=1 wmm_enabled=1 #
#
#
ht_capab=[LDPC][HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
#
ieee80211ac=1 #
#
#
vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
#
I will also answer about the amount of knowledge. I have about 2~3 years of Linux experience, so much so that I consider myself to have little knowledge of networking (I'm a beginner). I have also configured hostapd. Well, I've only used it a little (I remember I didn't operate it by myself much because I do it with templates).
ht_capab=[LDPC][HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
Would you like for me to give you some homework? I can give you some files and enough info for you to work on the new versions of the above?
The issue at hand is that the capabilities depend on the driver. I did a quick look and the in-kernel driver has somewhat different capabilities than the out-of-kernel driver so those line need to be a little different. They are close or hostapd would throw a fit.
I am very busy today fixing an issue in my out-of-kernel scripts but will try to get back on this project later today or tomorrow as time permits.
hostapd is a very nice app but it takes time to learn and get it right.
Can I get your to post the results of:
$ lsusb -t
Let's see if the adapter is in USB3 mode. That is an issue that I'm working with a couple of others as I have time. The driver is not always going into USB3 mode when using a USB3 port.
@morrownr
Thanks (all I can say is thanks) for working with such a newbie. Here are the results of lsusb -t:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005 ID 2357:012d TP-Link Archer T3U [Realtek RTL8812BU]
Bus 001 Device 002 ID 2109:3431 VIA Labs, Inc. hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
For now, ht_capab=[HT40+] and vht_capab=[SHORT-GI-80] ht-capab and vht-capab, If it works, add something, If it doesn't work, it's a problem before that... Thank you. Japanese↓(Since my English is poor, I have prepared Japanese. If you can translate it, we will understand.)
とりあえず ht_capab=[HT40+] vht_capab=[SHORT-GI-80] の設定でやってみて、動きそうなら 追加して、動きそうならそれ以前の問題(ドライバーとかですかね?) という風にやっていこうと思います.
Here are the results of lsusb -t:
That does not look like lsusb -t. See below:
My dev box:
$ lsusb -t
/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtl8812au, 5000M
|__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M
/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 5: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 4, If 0, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 6: Dev 4, If 1, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 6: Dev 4, If 2, Class=Video, Driver=uvcvideo, 480M
|__ Port 6: Dev 4, If 3, Class=Video, Driver=uvcvideo, 480M
|__ Port 7: Dev 5, If 1, Class=Wireless, Driver=btusb, 480M
|__ Port 7: Dev 5, If 2, Class=Wireless, Driver=, 480M
|__ Port 7: Dev 5, If 0, Class=Wireless, Driver=btusb, 480M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M
|__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
My Pi4B:
$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtw_8822bu, 480M
f it works, add something,
Smart.
Something before I end this message: Remember that the in-kernel for the rtl8812bu is largely unproven in AP mode. I'm sure that somebody has tested it but they haven't showed up around here. Therefore, we really don't know what to expect. I hope it works but I do not know that it will. I hope to start setting up the AP here tomorrow but it will go slow as I have to rework my guide.
@morrownr
Sorry, here are the lsusb -t results ↓
/Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
|Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
|__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtw_8822bu, 480M
Here are the results of lsusb -t:
That does not look like lsusb -t. See below:
My dev box:
$ lsusb -t /: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtl8812au, 5000M |__ Port 4: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M |__ Port 5: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 5: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 5: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 4, If 0, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 6: Dev 4, If 1, Class=Audio, Driver=snd-usb-audio, 480M |__ Port 6: Dev 4, If 2, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 4, If 3, Class=Video, Driver=uvcvideo, 480M |__ Port 7: Dev 5, If 1, Class=Wireless, Driver=btusb, 480M |__ Port 7: Dev 5, If 2, Class=Wireless, Driver=, 480M |__ Port 7: Dev 5, If 0, Class=Wireless, Driver=btusb, 480M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 3: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
My Pi4B:
$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtw_8822bu, 480M
f it works, add something,
Smart.
Something before I end this message: Remember that the in-kernel for the rtl8812bu is largely unproven in AP mode. I'm sure that somebody has tested it but they haven't showed up around here. Therefore, we really don't know what to expect. I hope it works but I do not know that it will. I hope to start setting up the AP here tomorrow but it will go slow as I have to rework my guide.
@morrownr
Understood. I will test it as much as I can.
To smoothly proceed with this discussion, I'll list the current situation in bullet points:
Things to try next:
As a result of hostapd, dbm does not change as expected -> SSID disappears happens. I checked the logs and there were no errors. Also, I assume it is a spec, but is it a spec that the lamp does not light up? (Is the heat a little warm)
@Ekiben542
Update: I ran onto an issue at another site that seems to indicate the in-kernel 8822BU driver is not working well in AP mode. I still want to test it and hope to have time soon.
What you may want to do is install the 88x2bu driver here at this site. If using install-driver.sh
ro install it, it will automatically blacklist the in-kernel driver and reverse the blacklist if you use remove-driver.sh
to remove it. The link is:
https://github.com/morrownr/88x2bu-20210702
The info in the example hostapd.conf files in my guide is for this driver. On a RasPi4B, you may find that you need to keep it in USB2 mode. This will give you the chance to test to see if your setup is working well.
@morrownr
@Ekiben542
Update: I ran onto an issue at another site that seems to indicate the in-kernel 8822BU driver is not working well in AP mode. I still want to test it and hope to have time soon.
What you may want to do is install the 88x2bu driver here at this site. If using
install-driver.sh
ro install it, it will automatically blacklist the in-kernel driver and reverse the blacklist if you useremove-driver.sh
to remove it. The link is:https://github.com/morrownr/88x2bu-20210702
The info in the example hostapd.conf files in my guide is for this driver. On a RasPi4B, you may find that you need to keep it in USB2 mode. This will give you the chance to test to see if your setup is working well.
@morrownr
Understood, thank you.
@Ekiben542
I haven't given up on this project but there is a problem. I cannot tell if it is a hardward issue with my pi4b or is something in RasPi. I'm not currently setup to test AP mode on other systems so this could take some time.
@morrownr
I understand.
Hello. I purchased NETGEAR's A6210-100JPS to use the mt7612u in Japan (because it passed the technical standards and was sold in Japan). However, when I investigated, I found out that ・txpower has limitations ・openwrt is not supported I found something like. but, I think that txpower and openwrt are only restricted in the A6210-10000 series such as A6210-10000S, and it does not affect the A6210-100 series, but can it be used in this series? If I cannot use it, please let me know what technical compatible products I can purchase in Japan (available on Amazon) for mt7612u. thank you.