Discussion, talk and tips
https://forum.puppylinux.com/
After installing F96CE4 and using it for a while, the notification about "192.168.1.102 acquire on wlan0" appears about 3-5 minutes. How to turn off it permanently?
Thanks.
I don't know if it works in f96ce, but I turned them off with a right click on the task bar icon and choosing dissable notifications.
Hope it works.-
Have a nice day.
nfkhanh wrote: Thu Oct 17, 2024 7:39 pmAfter installing F96CE4 and using it for a while, the notification about "192.168.1.102 acquire on wlan0" appears about 3-5 minutes. How to turn off it permanently?
Thanks.
What about your other thread about rtl8821cu? A lot of effort went into that discussion.
I tried so much many times. I found out in github about the way to compile this rtl8811cu/rtl8821cu. It's from the Dongle company, maybe a Chinese's.
I compiled and used it on my debian successfully. But on F96CE4 the compilation stucked, so I didn't see rtl8821cu.ko in whole of puppy.
Following Sofiya, althought rtl8821cu.ko is in it folder, the wireless connection isn't succeed.
I copied rtl8821cu.ko which is compiled on the debian. It's the same, the puppy tells that the module of AC600 is not available.
I think the error is from the compilation on own puppy. If the puppy can compile itself, the AC600 is possible.
About the compilation, my knownledge is nothing.
Did you follow the instructions I posted in the other thread? What happened?
Thank you. I followed your instruction.
1. depmod -a ----> ok
2. modinfo rtl8821cu ----> the interface is number 1. Try other interface number 0 ----> so that I don't understand.
3. modprobe rtl8821cu ----> the module is unavailable.
i think that some Puppy community member with expertise in compiling wifi drivers needs to build the rtl8821cu.
rcrsn51 wrote: Thu Oct 17, 2024 8:52 pmi think that some Puppy community member with expertise in compiling wifi drivers needs to build the rtl8821cu.
@ozsouth made 64bit rtl8811cu/8821cu v2 wireless drivers for fossapup64-9.5 (kernel 5.4.53) & my kernel 5.10.153-64oz-ao (which is in forum Kernels section).
Use at own risk. To install, download .pet & click on it in ROX-Filer, then after a few seconds, try to connect.
@nfkhanh - I made an rtl8821cu driver for Fossa64-9.6-CE4 (kernel 6.0.12-FP). Use at own risk.
see: https://www.mediafire.com/file/gf5qaw8t ... P.pet/file
After download, with the matching wifi adaptor (0bda:1a2b) plugged in, click on .pet in filemanager & wait about 5 sec after install finishes, then try to connect.
Thank @ozsouth so much.
It runs but it's probably unstable.
How is it unstable?
1. I withdrawed the rtl8192 (supporting my F96CE4) and inserted rtl8811/rtl8821 (AC600), puppy connects to internet. It runs and interdits to be down around every 10 seconds and then it connects again. Again and again. The firefox surfing shows that. And the notification appears with "wlan0 down".
2. I inserted both adaptors, internet amanager shows puppy can connect 2 ssids with wlan0 (rtl8192) and wlan1 (rtl8821). wlan1 was down with the same way.
3. I changed the slut for the adaptor. wlan0 (rtl8821) was down after around 10 seconds and then it connects to internet again. The notification "wlan0 down" repeats interditly.
Is your router ac-mode?
My router is TPLINK TL-WR940N.
But after compiling rtl8821cu on my debian yesterday, it runs perfectly.
Of cource, the same in Windows.
I think the driver has some points not capatible with F96CE4 this time.
I cannot duplicate your problem with dropouts. I own three 8821cu adapters - two name-brand and one no-name. The third one requires the usb-modeswitch procedure. I have tested them on several platforms, including F96CE4 with ozsouth's driver. They all work OK.
[Update] I made another test with F96CE4 where the client was a long distance from the router. There were no dropouts.
@nfkhanh - seems to be some issue other than drivers, but let's try your other wifi adaptor (rtl8192cu). There is already a kernel driver for that. However, I made another, with newer source. The .pet attached below will unload & delete earlier driver, then load newer one. Use at own risk. Do not plug both adaptors in at same time. To retain it (if it works), must save upon exiting puppy, or run .pet each time.
If that also fails or is flaky, could be firmware missing. To test, with adaptor plugged in, in a maximised terminal, run:
dmesg | grep irmware
Thank you for your support, @ozsouth.