Since your wireless works prior to ethernet connection, let's see if it's an issue with the new NetworkManager (1.20.8) by installing 1.20.6: sudo eopkg install https://mirrors.rit.edu/solus/packages/shannon/n/network-manager/network-manager-1.20.6-49-1-x86_64.eopkg then rebooting.
I did that, and same issue persists. 'Device not ready, not managed' :-(
I am assuming that 'restart' is same as 'shutdown' and on again?
I had the exact same issue and what I did was change the wifi module but my laptop didn't accepted it and then I went back to my current wifi module and everything was working again. That was so weird, hope it can get fix it
Just saw this too.
ifconfig
eno1 Link encap:Ethernet HWaddr 94:C6:91:1A:66:53
inet addr:192.168.100.142 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6499 errors:0 dropped:0 overruns:0 frame:0
TX packets:1962 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1682888 TX bytes:220093
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:0.0.0.0 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:169 errors:0 dropped:0 overruns:0 frame:0
TX packets:169 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14766 TX bytes:14766
ifconfig: error: interface wlo2' does not exist
elfprince No bro, it was the hardware. I removed physically the wifi module card from motherboard and put it another one which the mother board didn't accept it so, I put back the old and current wifi module and it worked.
I was so pissed off because even restarting the machine didn't get it to work and I just did that. Don't know why that happened
JoshStrobl , does this link help at all?
https://unixblogger.com/how-to-get-your-realtek-rtl8111rtl8168-working-updated-guide/[](url)
It talks about installing R8168 driver. R8169 is installed.
elfprince $ uname -a
Linux solnux2 5.4.1-137.current #1 SMP PREEMPT Sat Dec 7 15:17:22 UTC 2019 x86_64 GNU/Linux
You may probably want to check if the problem also exists with an older kernel. For example with
sudo eopkg it https://mirrors.rit.edu/solus/packages/shannon/l/linux-current/linux-current-5.2.20-130-1-x86_64.eopkgThen reboot and see...
If you're on UEFI-boot: As Solus will keep the last kernel, you can easily reboot and check what happens with 5.4.1-137. If you haven't set a timeout used the "hit space-bar method" for enabling you to select the kernel.
You'll be notified that there is an update (current 5.4-kernel). Just update and the new 5.4 kernel will again be the default.
@JoshStrobl , I rolled back the kernel to linux-current-5.2.20 and now wifi is working again! Do I need to keep rolling back after each software update? Normally I use the terminal, `sudo eopkg up' . Thanks ! :-)
You should be reverting to our 5.3 series and not the EOL'ed 5.2 series (which we pushed back in October). @bolofar should've provided you with that kernel instead:
sudo eopkg install https://mirrors.rit.edu/solus/packages/shannon/l/linux-current/linux-current-5.3.13-135-1-x86_64.eopkg
I will be reverting us to 5.3 series again today (and updating it to latest in that series, 5.3.15), I'm just seeing way too many problems with various ethernet and wireless devices to warrant keeping us on 5.4. Unfortunately, as a result of some significant updates to xorgproto, libICE and xorg-server, unstable syncing to stable is blocked until Friday (Dec. 13th).
Great! Thanks. JoshStrobl ! Will do that.
@elfprince Just an update on this, 5.3.15 is now in the unstable repository. If you are feeling particularly adventurous, you can try:
sudo eopkg install https://mirrors.rit.edu/solus/packages/unstable/b/btrfs-progs/btrfs-progs-5.3.1-23-1-x86_64.eopkg https://mirrors.rit.edu/solus/packages/unstable/l/linux-current/linux-current-5.3.15-138-1-x86_64.eopkg
I'm not 100% sure you'll need all the xorgproto, xorg, and libICE updates but I can provide commands to those if need be.
@AlienTux since you had issues with your Elantech touchpad, you can see if the revert to 5.3.15 without some of the i2c changes resolves your non-functional touchpad. But before you do that I'd like to make sure I provide you with all the necessary eopkg URIs you need (in case say, you use specific drivers like broadcom).
Try running the following: eopkg li | grep 'current'
This is of course if you want to test it. Would be helpful to me so I can figure out early on in the week if there is more work I need to do on getting the touchpad in working order.
JoshStrobl , thanks, but I am not adventurous with my production system. 
Happy with previous rollback.
JoshStrobl @bolofar should've provided you with that kernel instead:
sudo eopkg install https://mirrors.rit.edu/solus/packages/shannon/l/linux-current/linux-current-5.3.13-135-1-x86_64.eopkg
Actually I intentionally proposed the 5.2 series and admit 
I should better have noted why. The reason is that on an Asus UX305 (which I maintain as well) kernels from the 5.3 series lead to frequent system freezes, while 5.2 does not. Thus, I thought 5.2 would be better for testing than 5.3.
Note: Interestingly 5.4 up to now seems to run stable on the UX305: no system freezes and not other problems.
bolofar I'm not one of the devs, but knowing that the 5.2 kernel has already reached it's EOL (end of life) means it's no longer being updated, which puts your system at risk and thus all users are urged to upgrade to the next kernel which is 5.3. Solus only maintains two kernels, current which is as of right now at 5.4 and the 4.9 LTS kernel. There is no support for the 5.2 kernel so I wouldn't advise using that. Try the 4.9 LTS kernel which is still supported instead of 5.2 if you can. Solus is meant primarily for modern desktops with modern hardware, so if you're having kernel issues and the Solus kernels aren't meeting your needs, not that it's an ideal option, but there are other distros worth checking out that backport changes to older kernels, like Ubuntu, Elementary, etc.
Scotty-Trees Try the 4.9 LTS kernel which is still supported instead of 5.2 if you can.
Thanks for your comment! 4.9 LTS did not work on the UX305 (no WIFI & no Sound). I tired that, before reverting to 5.2. So, the situation was: "Not use the system at all because of no WIFI with the LTS kernel and frequent freezes (every 10 to 15 minutes) with 5.3. Or use the 5.2 kernel.". This decision was easy
As mentioned 5.4.1 was working without problems, but now I installed 5.3.15 from the unstable repository to see if that works. The first test seems promising: WIFI working and 30 minutes without freezes.
JoshStrobl Sorry it took me a bit to answer this.
Absolutely, I'll give it a try. I ran the command you asked for, this is the result:
bash-5.0$ eopkg li | grep 'current'
linux-current - Linux kernel image and modules (current)
nvidia-glx-driver-current - NVIDIA Binary Driver (Current Kernel)
virtualbox-guest-current - VirtualBox guest additions for the linux-current kernel
bash-5.0$ I hope this helps!
JoshStrobl ok so I ran this command:
and even tho the boot manager said I was logging into the 5.4 kernel I believe I did end up loading into 5.3.13. I'm not sure how to check this, but I went into the software center, looked for "linux-current" and it does say 5.3.13. Also, it's telling me there's a kernel update (package "linux-current").
Touchpad still unresponsive.
JoshStrobl ok, now I ran this command:
Touchpad still unresponsive.
My bootmenu is a mess to be honest... When I run this:
bash-5.0$ sudo clr-boot-manager list-kernels
[FATAL] cbm (../src/bootloaders/systemd-class.c:L507): sd_class_get_default_kernel Unable to parse loader config
com.solus-project.current.5.4.1-137
bash-5.0$ But in my bootmenu there are 4 different options... I tried
sudo clr-boot-manager update and nothing changed... any ideas how to fix this?