Someone told me to run dhcpcd as root in order to get dhcp response for my eth0. There is no command dhcpcd, why not? I searched for this file in /sbin but found nothing. Anybody an idea whether there is a similar file on FC 3? On Tue, 2004-12-21 at 15:58 +0100, Maciek R. wrote: > Is there any other configuration file to check or tool to execute or > thing to do in order to get this card to work under the newest kernel? > > On Tue, 2004-12-21 at 10:55 +0100, Maciek R. wrote: > > Not even reinstalling the new kernel and removing the card from network > > configuration and adding it again helped. Someone experienced s.th. like > > this with his card too after updating the kernel? > > Maybe someone give me (one couple of days M$ free now) an advice? > > > > On Mon, 2004-12-20 at 23:44 +0100, Maciek R. wrote: > > > What I wanted to add: > > > Even under the old kernel, getting IP via DHCP on booting the system > > > became very slow. I have no idea why, because after installing a fresh > > > copy of Fedora Core 3 it was as fast as the wind behind my window ;-) > > > > > > On Mon, 2004-12-20 at 23:26 +0100, Maciek R. wrote: > > > > So I am posting my configuration now: > > > > > > > > The Card is -> > > > > Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet > > > > > > > > ifconfig command output: > > > > > > > > lo Link encap:Local Loopback > > > > inet addr:127.0.0.1 Mask:255.0.0.0 > > > > inet6 addr: ::1/128 Scope:Host > > > > UP LOOPBACK RUNNING MTU:16436 Metric:1 > > > > RX packets:3343 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:3343 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:0 > > > > RX bytes:4174142 (3.9 MiB) TX bytes:4174142 (3.9 MiB) > > > > > > > > route command output: > > > > > > > > Kernel IP routing table > > > > Destination Gateway Genmask Flags Metric Ref Use > > > > Iface > > > > 169.254.0.0 * 255.255.0.0 U 0 0 0 > > > > lo > > > > > > > > > > > > ifcfg-eth0 file output: > > > > > > > > # Please read /usr/share/doc/initscripts-*/sysconfig.txt > > > > # for the documentation of these parameters. > > > > IPV6INIT=no > > > > ONBOOT=yes > > > > USERCTL=no > > > > PEERDNS=yes > > > > TYPE=Ethernet > > > > DEVICE=eth0 > > > > HWADDR=00:c0:9f:42:33:e6 > > > > BOOTPROTO=dhcp > > > > > > > > On Mon, 2004-12-20 at 16:56 -0500, William Hooper wrote: > > > > > Maciek R. said: > > > > > > What I want to know either is: Is it important to keep your system up to > > > > > > date? > > > > > > > > > > It depends if the update is just a feature update or a security update. > > > > > > > > > > > Is it important to update my kernel - even if my hardware will not > > > > > > work after it? > > > > > > > > > > Kernel updates are generally to fix security issues (important to update) > > > > > or to fix specific problems (not as important if it doesn't effect you). > > > > > > > > > > Perhaps you can give us enough information on your issue that we can help. > > > > > Start with what kind of network card you have. Possibly the output of > > > > > some basic network commands: > > > > > > > > > > ifconfig > > > > > route > > > > > > > > > > The contents of /etc/sysconfig/networking/devices/ifcfg-eth0 would > > > > > probably help, too. > > > > > > > > > > -- > > > > > William Hooper > > > > > > > > > -- > > > > Maciek R. <m.mail@xxxxx> > > > > > > > -- > > > Maciek R. <m.mail@xxxxx> > > > > > -- > > Maciek R. <m.mail@xxxxx> > > > -- Maciek R. <m.mail@xxxxx>
