[wplug] Fedora Core Network Bug

[Vanco, Don]

>-----Original Message-----
>From: wplug-bounces+don.vanco=agilysys.com at wplug.org 
>[mailto:wplug-bounces+don.vanco=agilysys.com at wplug.org] On 
>Behalf Of Poyner, Brandon
>Sent: Tuesday, June 07, 2005 1:39 PM
>To: General user list
>Subject: RE: [wplug] Fedora Core Network Bug
>
>
>What type of network card is it?  Some kernel ethernet modules will let
>you set the duplex and other options when the module is loaded.  You
>make the change in modprobe.conf and then you have to rebuild your
>initrd with mkinitrd.  

Sure you don't mean /etc/modinfo.conf?  I know that the network widget
uses the file /etc/log.d/conf/services/modprobe.conf - but there's no
"user land" edited file of this name that I know of.

FYI, you can also get the module options (for entry into
/etc/modules.conf) using the modinfo command:
e.g.:
[root at rh3u3 root]# modinfo
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/net/e1000/e1000.o
filename:
/lib/modules/2.4.21-32.0.1.ELsmp/kernel/drivers/net/e1000/e1000.o
description: "Intel(R) PRO/1000 Network Driver"
author:      "Intel Corporation, <linux.nics at intel.com>"
license:     "GPL"
parm:        debug int, description "Debug level (0=none,...,16=all)"
parm:        TxDescriptors int array (min = 1, max = 32), description
"Number of transmit descriptors"
parm:        RxDescriptors int array (min = 1, max = 32), description
"Number of receive descriptors"
parm:        Speed int array (min = 1, max = 32), description "Speed
setting"
parm:        Duplex int array (min = 1, max = 32), description "Duplex
setting"
parm:        AutoNeg int array (min = 1, max = 32), description
"Advertised auto-negotiation setting"
parm:        FlowControl int array (min = 1, max = 32), description
"Flow Control setting"
parm:        XsumRX int array (min = 1, max = 32), description "Disable
or enable Receive Checksum offload"
parm:        TxIntDelay int array (min = 1, max = 32), description
"Transmit Interrupt Delay"
parm:        TxAbsIntDelay int array (min = 1, max = 32), description
"Transmit Absolute Interrupt Delay"
parm:        RxIntDelay int array (min = 1, max = 32), description
"Receive Interrupt Delay"
parm:        RxAbsIntDelay int array (min = 1, max = 32), description
"Receive Absolute Interrupt Delay"
parm:        InterruptThrottleRate int array (min = 1, max = 32),
description "Interrupt Throttling Rate"

..sadly, I have found that some MFGRs do a poor job of listing what
params are required to make other params work, especially when trying to
use bonding/teaming drivers.

JMO, but in most cases Ethernet drivers are not required in the initrd,
but sure can't hurt

Don
 
>
>> -----Original Message-----
>> From: wplug-bounces+bpoyner=ccac.edu at wplug.org 
>> [mailto:wplug-bounces+bpoyner=ccac.edu at wplug.org] On Behalf 
>> Of Weber, Larry A
>> Sent: Tuesday, June 07, 2005 12:51 PM
>> To: 'wplug at wplug.org'
>> Subject: [wplug] Fedora Core Network Bug
>> 
>> Every time I boot my Fedora Core 2 system, eth0 fails to 
>> start.  I get a
>> "......check cable" message.  After the system starts I can 
>> manually start
>> the network as root with:  ifconfig eth0 up
>> and then activating it with:  system-config-network
>> 
>> This works but is a real pain to remember every time the 
>> system restarts.
>> Is there a file that runs at startup that would be the 
>> correct place to
>> config and activate the network?
>> 
>> -laweber
>> 
>> _______________________________________________
>> wplug mailing list
>> wplug at wplug.org
>> http://www.wplug.org/mailman/listinfo/wplug
>> 
>
>_______________________________________________
>wplug mailing list
>wplug at wplug.org
>http://www.wplug.org/mailman/listinfo/wplug
>