I think I found my issue (BTW I'm 4.2 beta 1).
I have leading whitespace for many of my /etc/modules entries, so those
weren't being loaded via the modutils script because it filters for only
lines whose first char is alphanum:
> grep ^[a-z0-9A-Z] /etc/modules |
presumably to omit comment lines ... but it's a tad too restrictive for
me so I used instead:
> grep -vE "^[[:space:]]*(#|$)" /etc/modules |
to omit both comment lines and empty lines. (FWIW there's a second
instance of the problematic-for-me grep filter in that modutils file.)
In my case the netcard drivers were being loaded by the auto-loader
portion of modutils, and in the same order as I had in my modules file
so I hadn't noticed.
I also discovered that I had a typo in my modutils file for one of my
drivers. In light of this I'd put in an RFE for:
- when parsing of the /etc/modules file and an module file cannot be
found (or gives an error), it puts out an error msg to the console
(I know that if an entry in /etc/modules does not exist as a file that
no err msg is output.)
(I'd also put in an RFE for more output from the modutils file as it
does its work - could it indicate when it's doing each of the 3 internal
steps of module loading:
- parsing /etc/modules,
- walking /etc/modules.d,
- finally, autoloading
so the user can see when exactly modules are being loaded? That would
probably help tremendously with diagnosing module-loading issues.)
Myself, I have the section messages (within modutils) output at all
times since diag output is pretty 'cheap' to implement, but it could
instead be set to only show this info if $VERBOSE is true.
Cheers & thanks for LEAF!
On 12/03/31 05:41, Andrew wrote:
> 31.03.2012 00:27, groups, freeman написал:
>> On 12/03/26 05:11, Andrew wrote:
>>> 26.03.2012 07:03, ads...@genis-x.com написал:
>>>> How do I change the order of NIC detection? or how can I force the system
>>>> to
>>>> load e1000e BEFORE the igb driver?
>>>>
>>>> Bering-uClibc_4.2_i686_syslinux_vga
>>>>
>>>> {{ snip }}
>>>>
>>> Hi.
>>> Just add e1000e in /etc/modules - it is processed before hardware detection.
>> Hmmmm. I seem to be suffering the same issue but I'm using 4.2 *beta 1*.
>>
>> In my case I'm using the tg3 module, and when that file merely exists in
>> /lib/modules mdev (I believe) finds it and loads it before the modules
>> listed in my /etc/modules get loaded.
>>
>> So my question would be: do I need to upgrade to 4.2 *release*, to have
>> my /etc/modules file 'respected' (i.e. to not have tg3.ko auto-loaded),
>> or is something else afoot in my case?
>>
>> Cheers& thanks for LEAF!
>> scott
>>
> As I remember, nothing changed in module-related logic for a long time
> (except switching to more easy hardware detection using hotplug script).
> /etc/modules is parsed before modules probing for long time.
> Can you do lsmod and look, when actually tg3 was loaded (on top there
> are freshest modules)?
> Try to remove modules.lrp from list of packages (to avoid module
> loading), and try to load tg3 manually - will it loaded successfully?
> Maybe it depends from some other driver (some bridge or so on, that is
> supported as module).
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> ------------------------------------------------------------------------
> leaf-user mailing list: leaf-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/leaf-user
> Support Request -- http://leaf-project.org/
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
