Kernel Update 3.11.6-200.fc19.x86_64 WIFI Issue

[Garry Kraemer]

I have successfully compiled the kernel source and the Realtek driver
for r8187se, which I need to get my Toshiba laptop WIFI working.

After compiling, I did the following as root:
# mkdir /lib/modules/$(uname -r)/kernel/drivers/staging/rtl8187se
# cp r8187se.ko /lib/modules/$(uname -r)/kernel/drivers/staging/rtl8187se/ 
# /sbin/depmod -a
# /sbin/modprobe r8187se

When I run /sbin/modprobe r8187se as root, I get a wifi connection.
If I reboot I have to become root and re-run the command.

What is the correct way to automate this process?
I would expect the driver to be linked in with the kernel code, but I
don't know enough about Linux builds to do it.

I have posted on the forum, but received no replies.

TIA

Garry

[Dexter L. Pearson]

Garry,

Have you checked your modprobe config file (usually 
*/etc/modprobe.conf*)? You might wanna see if your newly compiled and 
configured module is registered properly to this file. Another thing to 
do is to check the module's behavior by running *modprobe (-v 
*/or/*--verbose) (-n */or/*--dry-run)**r8187se*. That way, you can see a 
full report of what's happening when you manually load your module, 
especially if there's some side effects that weren't mentioned or known 
previously, or, and this could be possible, if there's a dependency 
that's either not present or not working/loading also. My first hunch, 
however, would be checking the .conf file; once a module's successfully 
loaded, it's there until you administrately issue the the *rmmod* 
(remove module) or *modprobe -r* /or/ *--remove* command.

Hope that helps,

Dexter

Garry Kraemer wrote:
> I have successfully compiled the kernel source and the Realtek driver
> for r8187se, which I need to get my Toshiba laptop WIFI working.
>
> After compiling, I did the following as root:
> # mkdir /lib/modules/$(uname -r)/kernel/drivers/staging/rtl8187se
> # cp r8187se.ko /lib/modules/$(uname -r)/kernel/drivers/staging/rtl8187se/
> # /sbin/depmod -a
> # /sbin/modprobe r8187se
>
> When I run /sbin/modprobe r8187se as root, I get a wifi connection.
> If I reboot I have to become root and re-run the command.
>
> What is the correct way to automate this process?
> I would expect the driver to be linked in with the kernel code, but I
> don't know enough about Linux builds to do it.
>
> I have posted on the forum, but received no replies.
>
> TIA
>
> Garry
> _______________________________________________
> laptop mailing list
> [e-mail]
> https://admin.fedoraproject.org/mailman/listinfo/laptop

[Brian Morrison]

On Sun, 27 Oct 2013 14:52:11 -0400
"Dexter L. Pearson"  wrote:
> Have you checked your modprobe config file (usually 
> */etc/modprobe.conf*)?

Fedora doesn't use this file any more, it uses a different method which
escapes me for the time being.

Might be worth searching Fedoraforum.org for some more information.