Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 03-03-2018, 08:40 PM   #31
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2
Posts: 387

Rep: Reputation: 81

The problem is, how do you select a kernel under RedHat that has the module that is needed (mwifiex).
Just any old upgrade is not going to suffice.
Old 03-03-2018, 09:14 PM   #32
Senior Member
Registered: Jan 2008
Location: Urbana IL
Distribution: Slackware, Slacko,
Posts: 3,716
Blog Entries: 3

Rep: Reputation: 480Reputation: 480Reputation: 480Reputation: 480Reputation: 480
Linux does not have drivers it has modules that are inserted and set in order to run.
Can we learn Linux here.
Old 03-06-2018, 09:45 AM   #33
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2
Posts: 387

Rep: Reputation: 81
Linux certainly does have drivers. It calls them drivers in the documentation, in the directory structure, and in the code itself. If the drivers are in the kernel they are still called drivers. The drivers may become modules, but only if they are built as kernel modules.
If the mwifiex driver is built-in to the kernel, you will not find a module for it.
For example, to boot your hard drive, the driver for the hard drive must be built-in the kernel, it cannot be a module. The filesystem for that hard drive must also be built-in. But the filesystems and drivers for secondary devices can be modules because they can be loaded after hard drive access to the modules is established.

A Linux kernel can be built having LAN access to its modules, and does not even need a local hard drive. In that case all the drivers for the LAN must be built-in to the kernel. In the kernel config they would be marked with "=y", and not the "=m" that builds modules. With the LAN drivers built-in, the LAN system can be used to access the network hard drives where there can be a path to kernel modules. Loading kernel modules would be done over the LAN drivers, which can then bring in drivers for other devices and optional kernel operations.

Not all modules are drivers, some are just kernel enhancements.

Some of the drivers won't let you build them as modules. Probably because writing them with the module hooks had some difficulty. Those drivers will only be present as built-in to the kernel.

Last edited by selfprogrammed; 03-06-2018 at 10:25 AM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Learn how to detect network equipment with Scientific Linux 7.1 and Python LXer Syndicated Linux News 0 09-10-2015 05:20 PM
Network communication issue with lotsa interfaces (Scientific Linux 6) watkinb Linux - Networking 13 01-22-2014 09:02 AM
Installed Scientific Linux 6.2 on a VM using KVM - no network access dralexpe Linux - Virtualization and Cloud 5 09-28-2012 09:09 PM
problem of network card with scientific linux wardani Red Hat 10 06-14-2011 11:05 AM
[SOLVED] How to configure network(internet) in scientific linux ? biplabbijay Linux - Newbie 7 04-06-2010 09:42 PM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 10:16 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration