(old)Puppy Linux Discussion Forum

This is the first time I have ever tried to compile a driver.

This is the line in the install script...

make ARCH=i386 CROSS_COMPILE= -C /lib/modules/3.14.55/build M=/root/my-documents/RTL8188 8192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519 modules

...and this is the error message that I get

make: *** /lib/modules/3.14.55/build: No such file or directory. Stop.

Running on Slacko 6.3.2

Creating a driver for Hornettek HT-WN300A.

I checked the Hornettek website, but it is currently down.

Heya dfw55, is Slackos`devx and kernel src loaded?

The "build" directory you've got to create.

Use PupScan in the system menu to tell us the "Vendor:Product" ID of your card.

devx_slacko_6.3.2.sfs is loaded

"build" directory has been created

Manufacturer=Realtek
Product=802.11n NIC
SerialNumber=000F002C0C45
VendorID=0bda ProductID=818b KERNEL-DRIVER(builtin)=(none)

You need the kernel source any time you're compiling a driver. Is that loaded?

Where do I get the kernel source?

If there's no SFS_Manager in the menu, get the correct src here.

If you're noPAE, this one.

https://wikidevi.com/wiki/Realtek says you need the RTL8192EU driver.

As it has the latest commit, I think you need this rtl8192eu-linux-driver package.

Green bar on the right, you want the zip.

Ah, I think drivers are compiled for a specific kernel. That is, drivers compiled for one kernel (probably) won't work with a different kernel.

OK.

I've made it past the previous error at the "make ARCH..." line.

Here's the new error message:


make ARCH=i386 CROSS_COMPILE= -C /lib/modules/3.14.55/build M=/initrd/mnt/dev_save/wifi_adapter/RTL8188 8192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519 modules
make[1]: Entering directory `/usr/src/linux'
make[1]: *** No rule to make target `8192EUS_linux_v4.3.0.4_11485.20140519/driver/rtl8188EUS_linux_v4.3.0.4_11485.20140519'. Stop.
make[1]: Leaving directory `/usr/src/linux'
make: *** [modules] Error 2

This fdrv sfs package has more firmware for Slacko 6.3.2

It may have what is needed already compiled and ready to use.

This is the fdrv sfs file.
Download this:
http://distro.ibiblio.org/puppylinux/pe ... ko_PAE.sfs

This is for Slacko 6.3.2 using Linux kernel 4.1.11
Check in menu>System>Pup-Sysinfo>Sys-specs>kernel to see if that is the kernel you are using.

I hope you have Slacko 6.3.2 as a frugal install with all the files in a directory(folder) usually named slacko632uefi.
Place the fdrv sfs in this directory with the other Slacko sfs files.
Reboot to get it loaded.

I checked, and my kernel is 3.14.55.

I just downloaded and created my frugal Slacko 6.3.2 a few days ago, so I assumed it had all of the latest stuff.

Looking around for how to update the kernel, and it doesn't look easy.

Since I'm just trying to create a new system, and I am more than willing to start again from scratch, where would I find the newest Slacko that already has kernel 4.1.11 (or newer)?

Sorry for the misinformation.

Found this info for the Realtek RTL8192EU chipset
http://www.murga-linux.com/puppy/viewtopic.php?t=110812
Seems by this info you need the 4.9.13 kernel.
It tells you how to change the kernel and where to get a new one to use.
I assume you are using the 32bit version of Slacko 6.3.2. Make sure you get the 32bit kernel.
Slacko may already have change_kernels program. So, try entering it in a console to see what happens.

rcrsn51 actually made some pet packages to install the needed module/driver to different Puppies. however, the download seems to be dead.
That would be the easy fix.

Wifi just seems to be a constant moving target providing the needed support.

Unless you are stuck on using Slacko.
Xenialpup 7.5 is a good option to try.

There is this info on compiling the driver.
http://www.murga-linux.com/puppy/viewtopic.php?t=110162

My problem was resolved by perdido providing me an alternate site to download the pet that was recommended by bigpup. See the following post for the download site:

http://www.murga-linux.com/puppy/viewtopic.php?t=110812

This was the easy fix, because it did not require me to compile the driver, and I did not have to change the kernel.

So, while my problem with compiling the driver has still not been resolved, I now no longer need to compile this driver.

My thanks to all of you who responded to this thread.