Re: No networking on 4.9-PRERELEASE

chael_at_southgate.ph.inter.net
Date: 09/15/03

  • Next message: Dan Strick: "Re: WINE"
    To: <questions@freebsd.org>, "Mike Meyer" <mwm-dated-1063996861.6ee0e3@mired.org>
    Date: Mon, 15 Sep 2003 08:12:26 +0800
    
    

    Dude, same here! Although mine's not an xl but an rl.

    I have posted it under subject "sendto: buffer space not available". I tried
    several times with that 4.9-PRERELEASE. But after every 12hrs, I get the
    buffer space error.

    Now I brought it back to 4.8-RELEASE-p4 via cvsup and everything seems to be
    running fine and it's been 13+hrs already non-stop (crossing fingers)

    ----- Original Message -----
    From: "Mike Meyer" <mwm-dated-1063996861.6ee0e3@mired.org>
    To: <questions@freebsd.org>
    Sent: Monday, September 15, 2003 2:40 AM
    Subject: No networking on 4.9-PRERELEASE

    > I updated (via source) to 4.9-prerelease. No, I *tried* to update to
    > 4.9-prerelease as of Sep 13th. The problem is that networking seems to
    > be failing in the 4.9-prerelease kernel. I build on one system and
    > test on a second system, installing via nfs. Following the nsame steps
    > I always follow to install a new kernel and world fails when I try and
    > install the world running the new kernel, as the nfs mount never
    > happens. Trying to ping the build system results in "Host is down"
    > messages. I can ping localhost and the ip address of the test machine
    > with no problems; those both use the loopback network. The interface
    > that's failing is xl0.
    >
    > Does anyone have an xl that's working with 4.9-prerelease? How about
    > anyone else having network problems with 4.9-prelease. A solution
    > would be best of all, of course.
    >
    > Thanks,
    > <mike
    > --
    > Mike Meyer <mwm@mired.org> http://www.mired.org/consulting.html
    > Independent Network/Unix/Perforce consultant, email for more information.
    > _______________________________________________
    > freebsd-questions@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    > To unsubscribe, send any mail to
    "freebsd-questions-unsubscribe@freebsd.org"
    >
    >

    _______________________________________________
    freebsd-questions@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-questions
    To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"


  • Next message: Dan Strick: "Re: WINE"

    Relevant Pages

    • Re: Fedora and PCMCIA support - upgrade kernel?
      ... Rebooted and no second kernel listed. ... > not then install it. ... on the network card... ... first no network support. ...
      (comp.os.linux.setup)
    • Re: Virtual Managers
      ... I was unable to get any repair done. ... The breakage was cause by doing some update swith the kernel stuff. ... network, which I don't have. ... you should have a working install by now. ...
      (alt.os.linux.suse)
    • Re: [opensuse] Support for Intel Centrino2 wireless chipset in openSUSE 11.00 ?
      ... 0c:00.0 Network controller: Intel Corp. ... SUSEs 2.6.25 kernel is too old to support Intels new 5xxx wifi series. ... You will have to update to kernel with current iwlagn driver and also install the matching firmware for that device. ... Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipientis prohibited. ...
      (SuSE)
    • RE: No Buffer Space Available
      ... Tweaking the kernel is not going to help you. ... Better to only run single network monitoring application at a time. ... Subject: No Buffer Space Available ... I noticed while I'm trying to monitor my network from my laptop ...
      (freebsd-questions)
    • Getting d-link DFE-530TX NIC working
      ... install of woody. ... configure the network on the grounds that it didn't find any network ... So I built myself a 2.4.21 kernel ... Ping to addresses on my LAN including the router itself returns: ...
      (Debian-User)