OP
avanturismo
Member
Im confused, when Im trying to reinstall it says its already there.. but cant find wifi...
Very new to Linux
- Thread starter avanturismo
- Start date
OP
avanturismo
Member
unfortunately does not work like that...
OP
avanturismo
Member
not sure how this should help. I tried restart router it didnt help. funny but even ChatGPT wont give me the right answers...
Condobloke
Well-Known Member
Did you really expect it to know ?
D
Deleted member 108694
Guest
Did your kernel get an upgrade? if so your - make dkms_install - may no longer be there since it was installed to that specific kernel because inxi -N is not showing your rtl8812au - dkms usually generate Linux kernel modules whose sources generally reside outside the kernel source tree. The concept is to have DKMS modules automatically rebuilt when a new kernel is installed.
But sometimes this does not happen - why - there is probably a thousand different reasons as to why
If that is the case you will just have to rebuild it again
Also on your image it is showing - that your Ethernet is connected
from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
Routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap. This may be why your WiFi is not working - The solution I know is having more than one interface connected to the same network is to aggregate them together in a bridge interface
But sometimes this does not happen - why - there is probably a thousand different reasons as to why
If that is the case you will just have to rebuild it again
Also on your image it is showing - that your Ethernet is connected
from the routing perspective, while possible, it is not ideal to have addresses from the same network in different interfaces.
Routing expects a different network per interface, and ultimately one of them will take precedence over the other in routing, since they overlap. This may be why your WiFi is not working - The solution I know is having more than one interface connected to the same network is to aggregate them together in a bridge interface
OP
avanturismo
Member
sure, why not? uninstalling, reinstalling, troubleshooting... You should try it Bruh
Condobloke
Well-Known Member
OP
avanturismo
Member
tbh I dont know about kernel upgrade. but I have this error message when I hit dkms_install.
so how may I rebuild dkms module?
Regarding "Ethernet is connected" I connected my OnePlus to share internet via USB.)))
OP
avanturismo
Member
so in the end ChatGPT heled me to solve
Condobloke
Well-Known Member
Has this worked for you as expected?
OP
avanturismo
Member
it fixed the problem which I tried to fix all day
Condobloke
Well-Known Member
I will have to give a try.
OP
avanturismo
Member
do not underestimate, it is truly amazing instrument.
OP
avanturismo
Member
after few years of using ubuntu I can definitely shout out - Thanks to ChatGPT for helping me out otherwise sometimes thats just to much when the machine is not working as expected!
OP
avanturismo
Member
so hello my Linux friends again! After few years of comfortable use of linux I face a new problem which apparently I can not fix with ChatGPT. So I am here seeking help with the following problem. My usb wifi adapter drivers got broken and I could not fix it. So I was using PC with mobile usb tethering and few weeks ago it started to malfunction, at first when I was restarting pc everytime I had to use comand:
ip addr
sudo ip link set "deviceID" up
dhclient "deviceID"
then few days ago it just got broken and I can not use wifi or even mobile tethering.
I tried several methods with chatgpt but still could not fix it. I see now that chatgpt hardly can fix everything without a proper, juicy human brain.
I thank you in advance for your answers.
ip addr
sudo ip link set "deviceID" up
dhclient "deviceID"
then few days ago it just got broken and I can not use wifi or even mobile tethering.
I tried several methods with chatgpt but still could not fix it. I see now that chatgpt hardly can fix everything without a proper, juicy human brain.
I thank you in advance for your answers.
Brickwizard
Well-Known Member
how did it get broken?
Yes, that would indeed help!
@avanturismo Am I understanding that your WiFi adaptor (not only your mobile phone) is USB? If so, check the output of
lsusb and there should be a vendor : product code, example: Bus 001 Device 001: ID xxxx:xxxx Nuclear Warhead Controller where xxxx is a hex number. Also, the output of ip -a would help regarding your mobile phone (after connecting it and ensuring USB tether is on).On the USB WiFi dongle side, typically, most distros will have a wifi driver package for each of the common series of chipsets. It's possible an upgrade messed with this. You can always purge the package, then reinstall it. Sounds obvious, but 9/10 times it's that simple... But more details will help narrow it down. For example, did you try the USB WiFi dongle in another PC to see if it works, etc.
Brickwizard
Well-Known Member
Right now I am fully awake and had my Brekki,
Provided you have not physically damaged the Wi-Fi dongle
1] have you tried it in a different socket?
2] tethering a mobile uses different controllers, have you tried using it in a different port to the non-working dongle?
3] have you checked it hasn't gone into hard-block [flight mode]? this sometimes occurs on doing upgrades
4 if all above fail, and you have INXI installed please run inxi -Nnz and copy/paste back the resultant report.
IF damage to the wi-fi is the result of the machine being dropped whilst the dongle was still in the port, then you may have damaged either the dongle or the port.
another thing could be wi-fi drivers not being present, if you are not using drivers supplied by the distribution [you install them yourself from another source] then you will probably need to re-install them
Provided you have not physically damaged the Wi-Fi dongle
1] have you tried it in a different socket?
2] tethering a mobile uses different controllers, have you tried using it in a different port to the non-working dongle?
3] have you checked it hasn't gone into hard-block [flight mode]? this sometimes occurs on doing upgrades
4 if all above fail, and you have INXI installed please run inxi -Nnz and copy/paste back the resultant report.
IF damage to the wi-fi is the result of the machine being dropped whilst the dongle was still in the port, then you may have damaged either the dongle or the port.
another thing could be wi-fi drivers not being present, if you are not using drivers supplied by the distribution [you install them yourself from another source] then you will probably need to re-install them
This is of course one of the few downsides with Linux; every time you get a kernel upgrade, any driver you're using that's not IN the kernel has to be re-built again.
Which is why I don't use proprietary driver packages.....and tend to stick with LTS kernels anyway. Kernel upgrading in Puppy is a manual procedure; many of us take the view that "if it ain't broken.....why bother trying to 'fix' it?" We'll find an up-to-date kernel that works for everything we happen to use, and stick with it for a while.
I'll keep an up-to-date LTS kernel for 6 months or so, then upgrade to the next newest LTS kernel. Some of you may think "That's crazy. You're not getting all the latest updates and security patches".....but with the way Puppy works, continuous, never-ending updates for the sake of it are nowhere NEAR as critical.
Yes, some of our members like to always have the most bang-up-to-date kernel. For these, a few of our senior members regularly compile the newest versions and make them available.....or else, you can always run the "kernel-kit" package over in Woof-CE at Github & build your own. The whole thing's automated, runs in a chrooted container on GitHub's servers, and only takes a few minutes to complete.
Mike.
Which is why I don't use proprietary driver packages.....and tend to stick with LTS kernels anyway. Kernel upgrading in Puppy is a manual procedure; many of us take the view that "if it ain't broken.....why bother trying to 'fix' it?" We'll find an up-to-date kernel that works for everything we happen to use, and stick with it for a while.
I'll keep an up-to-date LTS kernel for 6 months or so, then upgrade to the next newest LTS kernel. Some of you may think "That's crazy. You're not getting all the latest updates and security patches".....but with the way Puppy works, continuous, never-ending updates for the sake of it are nowhere NEAR as critical.
Yes, some of our members like to always have the most bang-up-to-date kernel. For these, a few of our senior members regularly compile the newest versions and make them available.....or else, you can always run the "kernel-kit" package over in Woof-CE at Github & build your own. The whole thing's automated, runs in a chrooted container on GitHub's servers, and only takes a few minutes to complete.
Mike.
Last edited:
