Hi all,
I recently purchased a new ASUS Z370-G motherboard after my old board fried. I have installed 42.3 (kernel 4.4.114-42) and everything works except the wifi which is mounted on the motherboard.
That has worked (almost) brilliantly. Wifi is now working but it has killed my ASUS GeForce GTX1050ti card’s resolution. Can only get 1024x768 whereas I had full 1920x1080.
chris@linux-vdis:~> uname -a
Linux linux-vdis 4.15.9-1.g2c1b8ee-default #1 SMP PREEMPT Sun Mar 11 22:31:16 UTC 2018 (2c1b8ee) x86_64 x86_64 x86_64 GNU/Linux
chris@linux-vdis:~>
I assume that you were using the proprietary nvidia driver (installed via nvidia packages for the Leap 42.3 kernel). Since you’re no longer using the standard kernel, you’ll will have to install the driver as explained here…
The ‘hard way’ scares me a bit but I will play with kernel work a little later. I think it will be easier to buy a USB dual band 2.4/5 GHz wifi dongle.
However that leads to a question or two - how did you the identify the firmware needed for the device? Also how did you know that particular kernel version works?
Is there a wiki or database I can search to identify firmware/drivers/kernels etc BEFORE I rush out and buy hardware? That would make me a bit more self reliant in linux.
Whatever works best for you. Some online retailers provide explicit information with respect to Linux support for a given device. Most leave you to research such things for yourself
However that leads to a question or two - how did you the identify the firmware needed for the device? Also how did you know that particular kernel version works?
Once one knows more about the device concerned, github can be also be one’s friend
If a kernel includes a particular driver module eg foo, then the pertinent firmware details for various supported chipsets can be found using
modinfo foo|grep firmware
Is there a wiki or database I can search to identify firmware/drivers/kernels etc BEFORE I rush out and buy hardware? That would make me a bit more self reliant in linux.
Thanks,
Chris.
Not a centralised one if that’s what you mean. Hardware compatibility lists are often out of date - a constantly moving target, so careful research is needed. From a Linux perspective, chipset details are what counts, but these are not always published with the reseller specs. Bleeding edge hardware can be risky, as kernel support takes time to be implemented.
That’s a good option Sauerland. I wasn’t ware of your repo for this. This would allow the OP to keep the standard Leap 42.3 kernel (and nvidia drivers). Thanks for sharing.
Thank you sauerland, I nearly missed your reply as I hadn’t set my email subscription properly.
So as I understand it from Deano, if I load your modules for k4.4.114 and assuming it works, then if and when the kernel gets updated from the repo it will pick up these modules as well?
Sounds easy
Still reading the notes from deano and ravas but that may end up as an experiment for me in a Virtualbox environment first.
If you have updated to Kernel 4.4.114, you should add my Update Repo and install rtlwifi_new-extended.
If the Kernel in the OSS-Update Repo gets an Update, my rtlwifi_new-extended will automatically build against the new Kernel and published as an Update in my Update Repo.
You get only the last build Package, so the now actual kmp for kernel 4.4.114 will be deleted and replaced by the new one.
Thanks for the procedure deano_ferrari, I had the same issue with openSUSE Leap 15 on my ThinkPad A475. Installing the new kernel and copying the new firmware did the trick to get my Wi-Fi card detected.