Puppy Linux Discussion Forum

I installed FossaPup64, using LICK, on the newly built system described below:
ASUS A320M-E mainboard
AMD Ryzen 3 1200 cpu
Biostar Radeon RX550 4GB graphics
Crucial Ballistix Sport LT 2x4GB RAM
USB2 M600 dual band WiFi dongle (uses RTL8812au drivers, provided on cd for Linux, Mac and Windows10).
[Actually uses RTL8821cu drivers as provided by ozsouth. Many thanks to ozsouth for the effort to provide drivers, and to bigpup for process recommendation.]
Seagate 500GB HDD
WD 500GB HDD.

WiFi is the only way to connect the PC to internet.

What is the necessary coding to install the drivers (currently copied to Home) so that the WiFi setup apps included with FossaPup64 can use them?

Thankyou in advance for the assistance!

SOLVED

@hotmud Welcome! Drivers are kernel-specific, so linux drivers would likely need compiling. RTL drivers go in /lib/modules under appropriate kernel folder (about 7 folders deep).

EDIT: link expired

I suggest after installing the pet.
Do a reboot, making sure to save.
That should make sure everything is seen and setup to use the driver.

Do you know how to make a WIFI connection, using one of the network connection programs?

You may also need to install firmware.

USB2 M600 dual band WiFi dongle (uses RTL8812au drivers, provided on cd for Linux, Mac and Windows10).

The firmware may be on the CD.
Under Linux stuff.
See if it has a file something like:
rtl8812aufw.bin
rtl8812aufw_wowlan.bin
Those go into /lib/firmware/rtlwifi

dup post

[textcolors]Do you know how to make a WIFI connection, using one of the network connection programs?[/textcolors]

none of them recognize the dongle! that is why i posted the request for assistance.

the linux files on the driver cd are for android and fedora only.

note:
1. mal...browser security reports filepup.net as a trojan.
2. installing from the link made no difference to gaining wifi access in fossapup.
3. my current internet access is in windows.

@hotmud - I've made another driver, with older source specific to rtl8812au, but I can't test, other than to say it loaded.

EDIT: link expired

Regardless, with dongle plugged in, the following commands will help diagnosis:

lsusb | grep -i rtl

and then

dmesg | grep irmware

@hotmud - this driver has worked for someone else - worth trying: viewtopic.php?p=16112#p16112

Have you tried installing PGPRS 3.0? This works for me in FossaPup64.

https://www.mediafire.com/file/da8nxc27 ... 0.pet/file

wlan.conf shows in geany:
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1
network={
ssid="Belong3613-5G"
scan_ssid=1
psk="ccfhkynhvxf"
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
}

geany shows:

for: [textcolors]wpa_supplicant.conf[/textcolors]
[textcolors]ctrl_interface=/var/run/wpa_supplicant
update_config=1[/textcolors]

for:[textcolors] pwf.conf[/textcolors]
[textcolors][textcolors]export INTERFACE=eth0
export DRIVER=RTL8812au-dkms
export PROFILEPATH=/etc/pwf/wifi
export TRIES=9
export STATIC="dkms"
export GATEWAY="on"
[/textcolors][/textcolors]

for:[textcolors] peasywifi_auto[/textcolors]
[textcolors]peasywifi wlan0
[/textcolors]

for: [textcolors]BelongAF36135G.conf[/textcolors]
[textcolors]ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1
network={
ssid="BelongAF3613-5G"
scan_ssid=1
psk="ccfhkynhvxfe"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
}[/textcolors]

for: [textcolors]Belong.conf[/textcolors]
[textcolors]ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1
network={
ssid="BelongAF3613-5G"
scan_ssid=1
psk="ccfhkynhvxfe"
proto=WPA2
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
}[/textcolors]

@hotmud - did you try the latest rtl88XXau driver I made at link above? After trying several sources code sets, it worked for the person asking there who has rtl8812au dongle. Link at that post now takes you to archive.org, not filepup.net. Connection wizard can not only set up wpasupplicant, but also resolv.conf & dhcp, so is recommended in puppy.

yes, i did. still can not get it online.
thankyou for all your work.

ozsouth

would it help if i allowed you remote access to my system? if so, how do i do that in fossapup64?

the driver cd contents:
/mnt/sr0 (Thumbs)
LINUX (folder)
8811AUlinux (folder)
RTL8821AU_Linux_v5.2.6_21981_COEX20170206-6720.20170407.zip (installed by 'Extract files' to root folder - selected from limited menu)
RTL81888192EUS_linux_v4.3.0.4_11485.20140519 (folder containing Android drivers etc)

root# lsusb | grep -i rtl
root# dmsg | grep irmware
bash: dmsg: command not found
root# dmesg | grep irmware
[ 0.706106] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.714784] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.839886] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[ 0.839960] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[ 0.840023] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[ 0.840094] [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
[ 17.206834] [drm] Found UVD firmware Version: 1.130 Family ID: 16
[ 17.223772] [drm] Found VCE firmware Version: 53.26 Binary ID: 3
root#

@hotmud - wow, I haven't had this much trouble finding the right driver since the Broadcom chip saga in 2017. It seems different systems are reacting to different drivers for the same wireless chip. Can you please run (with the dongle plugged in) lsusb & post output.
I've attached the only other driver which showed any response to rtl8812au on the other person's system for you to try (at own risk). To install, download .pet & click on it in ROXFiler, wait a few seconds, then plug in dongle & try to connect.

Interested in the topic and so using BionicPup did a search for rtl8812 in Bionic and Xubuntu and only found three hits in Xubuntu. See attached. I did wonder if that device worked in other Distros.

@peterw - first file you displayed is bluetooth firmware; last 2 are for rtl8812au & both are in fossapup64's fdrv. The reason for getting folk to run
dmesg | grep irmware
is to show missing firmware, which apparently isn't the case here. Don't be discouraged from making suggestions tho. This is tricky.

ozsouth wrote: ↑Fri Jan 29, 2021 8:42 am

@hotmud - wow, I haven't had this much trouble finding the right driver since the Broadcom chip saga in 2017. It seems different systems are reacting to different drivers for the same wireless chip. Can you please run (with the dongle plugged in) lsusb & post output.
I've attached the only other driver which showed any response to rtl8812au on the other person's system for you to try (at own risk). To install, download .pet & click on it in ROXFiler, wait a few seconds, then plug in dongle & try to connect.

requested output is immediately above your post.

peterw wrote: ↑Fri Jan 29, 2021 9:04 am

Interested in the topic and so using BionicPup did a search for rtl8812 in Bionic and Xubuntu and only found three hits in Xubuntu. See attached. I did wonder if that device worked in other Distros.

thankyou. i already have those from a different source.

I know this is a lot of steps to follow, but it provides us exact information on where your problem is.

Do the connection setup using the Network Wizard.

menu->Setup->Internet Connection Wizard->Wired or wireless LAN->Network Wizard

Network Wizard wireless connection steps.

1. Select Network Wizard
2. Select wlan0 (your network card may have a different description)
3. Select Wireless in the Configure wireless network box.
4. Select Scan and your ESSID (WIFI router) should come up.
5. Select your ESSID and OK
6. Give a name to your profile. It should already be what you selected in step 5.
7. Encryption. Most people use WPA/TKIP - select it or WPA2.
8. A box will open for you to write the WPA password. It is called a Shared Key. Enter the password.
9. Leave the other boxes as they are. Rarely do these need adjustment.
9. Select Save
10. Select Use This Profile
11. A box will appear showing Puppy trying to connect
12. A box will come up “REPORT ON TEST 0f wlan0CONNECTION”
13. Select Auto DHCP in the Configure interface box and it will go through a handshake routine. and declare itself successful
14. Select done

Select to use this setup on boot up.
Select to use this as default.

If something does not work.
What step?
You do what?
You see what?

Also make sure your system's time zone setting is correct - if not, many website's certificates then act as if they are expired, and the webpage won't display.

@hotmud - Command you ran before was just looking for rtl output.

I need to see ALL usb output by running JUST lsusb with dongle plugged in,
but if you don't want to display everything here, this should suffice (unless it shows a blank): lsusb | grep etwork

ozsouth wrote: ↑Fri Jan 29, 2021 12:06 pm

@hotmud - Command you ran before was just looking for rtl output.

I need to see ALL usb output by running JUST lsusb with dongle plugged in.

ok, i will attempt that tomorrow.

bigpup wrote: ↑Fri Jan 29, 2021 12:02 pm

I know this is a lot of steps to follow, but it provides us exact information on where your problem is.

Do the connection setup using the Network Wizard.

ok, i will attempt that tomorrow

ozsouth wrote: ↑Fri Jan 29, 2021 12:06 pm

@hotmud - Command you ran before was just looking for rtl output.

I need to see ALL usb output by running JUST lsusb with dongle plugged in,
but if you don't want to display everything here, this should suffice (unless it shows a blank): lsusb | grep etwork

"root# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 2a7a:8a47 CASUE USB KB
Bus 003 Device 003: ID 275d:0ba6 USB OPTICAL MOUSE
Bus 003 Device 002: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root# "

"root# lsusb | grep etwork
root# "

also i found this one in Geany on friday:
"PROBE
=====
Date: Fri Jan 29 16:39:01 2021 (1611902341)
Probe URL: https://linux-hardware.org/?probe=f654ae8b0e"

lsusb after moving usb wifi to the next usb port:
root# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 2a7a:8a47 CASUE USB KB
Bus 003 Device 003: ID 275d:0ba6 USB OPTICAL MOUSE
Bus 003 Device 013: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root#

now to try bigpup's last request

bigpup wrote: ↑Fri Jan 29, 2021 12:02 pm

I know this is a lot of steps to follow, but it provides us exact information on where your problem is.

Do the connection setup using the Network Wizard.

menu->Setup->Internet Connection Wizard->Wired or wireless LAN->Network Wizard

Network Wizard wireless connection steps.

1. Select Network Wizard
2. Select wlan0 (your network card may have a different description)
3. Select Wireless in the Configure wireless network box.

Puppy Network Wizard shows ONLY eth0.
step 2, unplug wifi dongle and network cable, try again from beginning
same result, plug in network cable to send this message

@hotmud - aha! the lsusb identifies your chip as rtl8821cu, as does the 'probe' you found.
I've made a driver for that chip, which compiled with warnings so use at own risk.
To install, download & click on .pet in ROXFILER. Is here: LINK EXPIRED

ozsouth wrote: ↑Mon Feb 01, 2021 2:33 am

@hotmud - aha! the lsusb identifies your chip as rtl8821cu, as does the 'probe' you found.
I've made a driver for that chip, which compiled with warnings so use at own risk.
To install, download & click on .pet in ROXFILER. Is here: http://www.filepup.net/files/deaa6cf61612146248.html

SOLVED after restart and completing the procedure detailed by bigpup. thankyou guys!!!!!

ozsouth I bow at your feet for your ability to always come up with the needed WIFI firmware and drivers!!

Thanks for your WIFI support in Puppy!!!