Failed yum update -- WAS ( SLOW network on FC3 )

From: Jeff Vian (jvian10_at_charter.net)
Date: 12/19/04

  • Next message: antonio montagnani: "Re: CD burning problem" 
    To: For users of Fedora Core releases <fedora-list@redhat.com>
Date: Sun, 19 Dec 2004 00:59:39 -0600

    On Sat, 2004-12-18 at 12:15 -0500, Craig J Wright wrote:
    > When I used yum to update the kernel (to kernel-2.6.9-1.681_FC3.i686).
    > It failed with the following message:
    > /sbin/mkinitrd: line 776: /tmp/initrd.img.V21453: cannot
    > overwrite existing file mkinitrd failed
    >
    > This new kernel is not listed in the /boot/grub/grub.conf file either.
    > What do I do to fix this so the new kernel will be usable?
    > --Craig
    >

    1. Please do not post HTML to the list

    2. Please do not top post.

    3. Please do not hijack a thread. Your question had no relation to the
    subject line or to this thread. Please post a new message with a
    relevant subject line when you need assistance.

    Now for the answer: Delete the file that was a conflict, then do a "yum
    update kernel" and when it finishes all should be well.

    > On Fri, 2004-12-17 at 17:07 -0600, Bill Gradwohl wrote:
    > > JonVO wrote:
    > >
    > > > Thanks Bill for the tip. Unfortunately I succesfully implemented the
    > > > sysctl change to little effect. Download speed now a whopping 1KB/sec
    > > > on the Sun website, close to 196K on the Win2k box. ifconfig says my
    > > > eth0 is running multicast, no errors or collisions.
    > > > JonVO
    > > >
    > > If you have 2 or more machines handy, you might want to run some tests
    > > between machines ignoring your Internet connection for the moment. If
    > > machine to machine behind your router is also slow, then that would
    > > isolate the issue a bit more. If machine to machine is fast, then it has
    > > to do with your Internet connection.
    > >
    > > Try running some large ping packets between the FC3 and another box. Try
    > > running some regular ping packets too. I've seen packet size cause
    > > issues. For the moment, use only IP addresses not names to avoid name
    > > resolution issues, and also tell ping not to resolve names. You can run
    > > these ping tests against your Internet router also to see if packet size
    > > has any effect.
    > >
    > > You might try to use a cross over cable between 2 boxes to also
    > > eliminate any issues concerning a switch/hub.
    > >
    > > --
    > > Bill Gradwohl
    > > bill@ycc.com
    > > http://www.ycc.com
    > > spamSTOMPER Protected email
    > >
    > --
    > fedora-list mailing list
    > fedora-list@redhat.com
    > To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: antonio montagnani: "Re: CD burning problem"

    Relevant Pages

    • Re: Ping & Physics
      ... As I'm sure you know ping retuns the time taken for the packet ... be determined from ping latency values, ... considering only the bit rate is 1.5 ms for a round trip. ...
      (comp.unix.questions)
    • Re: failed shields up test
      ... Try to ping one - you'll probably get a response, ... Now, plug the cable back in, and fire up that packet sniffer on "this" ... protocols that can be found in an IP packet (see figure 3.1 in RFC0791 ...
      (alt.os.linux.suse)
    • Re: Connecting to Exchange...
      ... The truth is that ping packets are a basic troubleshooting tool and a router *shouldn't* be monkeying with them. ... And changing a packet intended to to troubleshoot a connectivity issue defeauts the purpose of sending the packet in the first place...as the destination suddenly becomes ambiguous. ... The ISP configured the original device and the device actually PROPERLY recreates NAT ping packets and passes them to the servers, but the SBS server was not part of that initial configuration. ...
      (microsoft.public.windows.server.sbs)
    • Re: failed shields up test
      ... Try to ping one - you'll probably get a response, ... Now, plug the cable back in, and fire up that packet sniffer on "this" ... protocols that can be found in an IP packet (see figure 3.1 in RFC0791 ...
      (alt.os.linux.suse)
    • Re: Intermittent problems with LAN transfer speeds
      ... run are to ping with a large packet size to emulate file transfers and not ... If you get 100% Packet Loss then your firewall is in the way. ... I've not found any solution other than rebooting the server. ...
      (freebsd-net)
    Loading