On Wed, Apr 12, 2017 at 2:11 PM, Jerry Snitselaar <
dev@snitselaar.org>
wrote:
>
> Stephen M @ 2017-04-09 00:35 GMT:
>
> > When I go into the zip file itself, the driver is 8188eu and that's what
> I
> > copied over to /lib/modules but still getting the same message. I can
> do a
> > lsmod and it can see the module but it's not active.
> >
>
> What is the output of the following:
>
> uname -r
> find /lib/modules -type f -name 8188eu.ko
> grep 8188eu.ko /lib/modules/`uname -r`/modules.dep
> lsmod | grep 8188eu
>
> > On Sat, Apr 8, 2017 at 12:18 PM, Jerry Snitselaar <dev@snitselaar.org>
> > wrote:
> >
> >>
> >> Stephen M @ 2017-04-08 18:58 GMT:
> >>
> >> > I get this message when trying,
> >> >
> >> > stephend@stephend-desktop:~/Downloads/rtl8188eu$ sudo modprobe
> 8188eu.ko
> >> > [sudo] password for stephend:
> >> > modprobe: FATAL: Module 8188eu.ko not found.
> >> > stephend@stephend-desktop:~/Downloads/rtl8188eu$
> >> >
> >> > Now I'm assuming I need to move the driver but do a move the entire
> >> folder
> >> > or just the script itself to the usr/lib folder?
> >> >
> >> > On Sat, Apr 8, 2017 at 11:40 AM, Jerry Snitselaar <dev@snitselaar.org
> >
> >> > wrote:
> >> >
> >>
> >> When using modprobe drop the .ko off the name. Is it named 8188eu.ko or
> >> r8188eu.ko ? Whichever it is, copy it to /lib/modules/`uname -r`/extra
> >> and then run 'depmod -a'. once that is done you should be able to do
> >> 'modprobe r8188eu' or whatever the name is, and have it load.
> >>
> >> >>
> >> >> Stephen M @ 2017-04-08 15:56 GMT:
> >> >>
> >> >> > The driver is rtl8188eu for a TL-WN725N wifi adapter
> >> >> >
> >> >>
> >> >> Ah, that has been sitting in drivers/staging for a long time.
> >> >>
> >> >> Does your modprobe work now?
> >> >>
> >> >> An example on Fedora 25 with a test module:
> >> >>
> >> >> ~/mymod> sudo modprobe mymod
> >> >> modprobe: FATAL: Module mymod not found in directory
> >> >> /lib/modules/4.10.5-200.fc25.x86_64
> >> >> ~/mymod> make
> >> >> make -C /lib/modules/4.10.5-200.fc25.x86_64/build
> >> M=/home/jsnitsel/mymod
> >> >> modules
> >> >> make[1]: Entering directory '/usr/src/kernels/4.10.5-200.
> fc25.x86_64'
> >> >> CC [M] /home/jsnitsel/mymod/mymod.o
> >> >> Building modules, stage 2.
> >> >> MODPOST 1 modules
> >> >> CC /home/jsnitsel/mymod/mymod.mod.o
> >> >> LD [M] /home/jsnitsel/mymod/mymod.ko
> >> >> make[1]: Leaving directory '/usr/src/kernels/4.10.5-200.
> fc25.x86_64'
> >> >> xz --check=crc32 --lzma2=dict=512KiB mymod.ko
> >> >> ~/mymod> ls
> >> >> Makefile modules.order Module.symvers mymod.c mymod.ko.xz
> >> >> mymod.mod.c mymod.mod.o mymod.o
> >> >> ~/mymod> sudo cp mymod.ko.xz /lib/modules/`uname -r`/extra/
> >> >> ~/mymod> sudo depmod -a
> >> >> ~/mymod> sudo modprobe mymod
> >> >> ~/mymod> lsmod | grep mymod
> >> >> mymod 16384 0
> >> >> ~/mymod> dmesg | tail -1
> >> >> [344910.989060] loading mymod
> >> >>
> >> >>
> >> >> > On Fri, Apr 7, 2017 at 10:32 PM, Jerry Snitselaar <
> dev@snitselaar.org
> >> >
> >> >> > wrote:
> >> >> >
> >> >> >>
> >> >> >> Stephen M @ 2017-04-08 00:55 GMT:
> >> >> >>
> >> >> >> > Hi everyone,
> >> >> >> >
> >> >> >> > This seems really dumb but I have a wifi adapter from TP-Link
> on a
> >> >> Ubuntu
> >> >> >> > 14.04 machine that disconnects after reboot or a system
> update. I
> >> >> keep
> >> >> >> > typing insmod to get it to turn back on. I know I need to do
> >> modprobe
> >> >> >> but
> >> >> >> > it can't find the file.
> >> >> >> >
> >> >> >> > I downloaded the driver from their site, unzipped it in my
> download
> >> >> >> folder
> >> >> >> > though I think I need to move it. Any help would be grateful.
> >> >> >>
> >> >> >> modprobe can't load it because it knows nothing about the driver.
> >> >> >>
> >> >> >> Try:
> >> >> >>
> >> >> >> sudo cp *downloaded-module* /lib/modules/`uname -r`/extra/
> >> >> >> sudo depmod -a
> >> >> >>
> >> >> >> You will still run into the issue each time a new kernel is
> >> installed,
> >> >> >> and since the driver isn't tied to the kernel you are running
> there
> >> can
> >> >> >> be incompatibilities that cause issues. if you do run into issues
> >> with
> >> >> >> it, you can blacklist it on the kernel parameters line when
> booting.
> >> >> >> 'module_blacklist=module_name' should work.
> >> >> >>
> >> >> >> What driver is it using?
> >> >> >> ---------------------------------------------------
> >> >> >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> >> >> >> To subscribe, unsubscribe, or to change your mail settings:
> >> >> >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
> >> >>
> >> >> ---------------------------------------------------
> >> >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> >> >> To subscribe, unsubscribe, or to change your mail settings:
> >> >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
> >> >>
> >>
> >> ---------------------------------------------------
> >> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> >> To subscribe, unsubscribe, or to change your mail settings:
> >> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
> >>
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
--
Stephen Melheim
602-400-7707
SMelheim85@gmail.com
---------------------------------------------------
PLUG-discuss mailing list -
PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
(text/plain)
