[wplug] Fedora Core Network Bug

[Poyner, Brandon]

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.  This is an example of what you can do with the
eepro100 module.

# grep eepro /etc/modprobe.conf
alias eth0 eepro100
alias eth1 eepro100
options eepro100 full_duplex=1,1
# modinfo eepro100
...
parm:           debug:debug level (0-6)
parm:           options:Bits 0-3: transceiver type, bit 4: full duplex,
bit 5: 100Mbps
parm:           full_duplex:full duplex setting(s) (1)
parm:           congenb:Enable congestion control (1)
...

Brandon Poyner
Network Engineer III
CCAC - College Office
412-237-3086
 
 

> -----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
>