Inability to start Network

Alright guys, I bet this will be an easy one, but I am all out of ideas and frustration has set in.  I've built up a new box, and while the entire thing works, boots and is running Arch Linux off my old hard drive, I just cannot seem to get the network to come up.
I bought a new Linksys LNE100TX.  I know that the module is tulip, hwd tells me that, searching the forums told me that... and so I have it loading.  I've tried building it into my costume kernel vs. modules.  No good...
I have come to the conclusion that I must be missing something simple.  Yes, the card is attach to the motherboard.  Yes it is recognized by hwd.  Yes my cable is plugged into the card. 
The funny thing is that when I run hwd it comes up under ethernet and then directly underneath is the network section.  This section is empty and says "No PCI card or onboard chip."  Seems strange, but then my old box has worked perfectly since long before hwd came out...
Any ideas?

Edit:  So it turns out all that was required was a resetting if the modem, called Comcast and it works.  Wow, what a nice waste of my day.
My ISP makes you register the MAC address of any network hardware you use before letting it access the net. Pissed me off once when the cable modem just blew up, was replaced by the ISP but wouldn't work because they didn't change the MAC address entry in the database.

Similar Messages

  • [Solved]Can't get past "Starting network" during installation from USB

    I'm trying to do a fresh install of Archlinux on my laptop, following the Beginners Guide. However, I never get to the shell prompt because the installation gets stuck at "Starting network [Busy]".
    These are steps I followed:
    - I downloaded the latest Arch ISO.
    - I wrote it to a usb stick ("Kingston Data Traveler") with "dd if=archlinux.iso of=/dev/sdb"
    - I put the usb stick into my laptop (HP Pavilion dm1-4139sd), and booted it. I chose "x86_64". Everything seems to go fine, the only warning I get is: "microcode: failed to load file amd-ucode/microcode_amd.bin".
    - I get the message "INIT: Entering runlevel: 3" and "Starting Syslog-NG [Done]", after that its endlessly (at least 20 minutes) stuck on "Starting network [Busy]".
    I tried the following variations on the above:
    - Wrote the ISO to a different USB, samen problem.
    - Tried it with a different Arch version (from August), same problem.
    - Turned kvm on and off, same problem.
    - Pressed TAB at the "x86_64" line and added "acpi=off" to the end of it. I then get:
        :: Triggering uevents....
        [ 19.697932 ] usb 1-1: device not accepting address 2, error -110
        :: Mounting '/dev/disk/by-label/ARCH_201209' to '/run/archiso/bootmnt'
        Waiting 30 seconds for device /dev/disk/by-label/ARCH_201209
        [ 35.312165 ] usb 1-1: device not accepting address 3, error -110
        [ 45.821422 ] usb 1-1: device not accepting address 4, error -110
        [ 56.330681 ] usb 1-1: device not accepting address 5, error -110
        [ 56.330681 ] hub 1-0:1.0: unable to enumerate USB devices on port 1
        ERROR: '/dev/disk/by-label/ARCH_201209' device did not show up after 30 seconds....
        Falling back to interactive prompt
        You can try to fix the problem manually, log out when you are finished
        sh: can't access tty; job control turned off
        [rootfs /]#
    I'm not sure what to do in this prompt. At least the network isn't working and none of the normal commands.
    - I reset the DHCP leases on my modem, same problem.
    - I turned off/on the hardware WLAN, same problem.
    - I tried it with or without the LAN cable plugged in, same problem.
    - I tried it with or without the battery plugged in, and with or without the power cable plugged in. Same problem.
    I also performed the Arch memory test, and the bios hard disk test. They both report no errors.
    I did an Arch installation a month ago on this laptop, and back then it didn't have this problem. I still have that arch installed from back then and it boots/works without problem (I have Starting NetworkingManager [Done]). I know I technically don't need to install arch again, as I still have the old one, but I wanted to clean the changes I made to some settings files and I if it turns out this is some kind of hardware problem I'd like to return it to the store.
    Please help! I'm not really that familiar with Linux in general, so it might have been a very basic mistake from me as well. I have no idea what to do next, except for formatting my harddisk (which I don't think should influence the installer?), or trying to install a different Linux distro.
    Edit: The solution that solved this problem for me in the end was resetting the BIOS to its defaults.
    Last edited by dbakker (2012-09-15 11:28:14)

    DSpider wrote:Did you check the MD5 checksum? If you downloaded it using a BitTorrent client, then you don't need to (its hash is checked during downloading).
    Yes, I downloaded it using BitTorrent and the MD5 matches.
    DSpider wrote:Try a different stick?
    Yes, I tried it with 2 different USB sticks. They are both from the same brand ("Kingston DataTraveler"), so I might try different brands as well, but I don't think it is the problem.
    DSpider wrote:Or at least a different method from that wiki page. For example, "dd"-ing it should work just fine.
    The methods for writing the ISO that I tried so far:
    The base method:
    dd if=archlinux.iso of=/dev/sdb
    (from an Arch install)
    The method without overwriting your USB drive (created a FAT32 drive with an VFAT filesystem, from an arch install)
    Using Imagewriter (from Windows)
    Each method gives the same result: the laptop gets stuck at "Starting network [Busy]" when booted from one of the USB sticks. My modem indicates that it "sees" the laptop, but that the laptop has no established connection. When the laptop is stuck at the "Starting network [Busy]", all the activity on the USB stick stops (the light stops flashing).
    The thing I find most strange is that the OS currently installed on the laptop has no problems booting or accessing the internet (both wired and wireless) at all.

  • Systemd doesnot start network/networkmanager automatically

    Systemd 44-5
    I have add network/networkmanager into the DAEMONS array of /etc/rc.conf
    DAEMONS=(syslog-ng dbus network crond sshd)
    But the network would not start automatically by systemd when arch boots.
    I must "sudo rc.d start network" maually when I login.

    What framas instructs _is_ doing it the native systemd way. The problem is that network.service doesn't start automatically. There's not even a single word about in the wiki - just about static network.
    Last edited by algorythm (2012-04-14 15:28:50)

  • Code 10: device cannot start Network Adapters

    Hello,
    I need help, my Media Player is not working right.  I keep getting this message; code 10:  device cannot start Network Adapters.  Please help, I tried to reinstall Windows Media Player 11, I even deleted the one on my laptop it kept saying it was still there.  I went in to the Device Managers and to Network Adapters, there is one that shows it is not working properly, Toredo tunneling.
    Please, Please help I need to download a document tonight.
    Terry789

    hey DTTODGG,
    since you have uninstalled the drivers under device manager, were you able to use the "update drivers" ?
    Anyway, is your system running on Win7 .. if it is, I believe that Win7 should have installed some generic drivers for you.
    Also could you check under the properties of your Network Adapter, is the device enabled ? If it isn't, enable it.
    WW Social Media
    Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
    Follow @LenovoForums on Twitter!
    Have you checked out the Community Knowledgebase yet?!
    How to send a private message? --> Check out this article.

  • EMac won't start up, only gets to "Starting Network File System"

    Would appreciate any help. I'm a novice. Have a 4-year-old eMac that offered updates for Quicktime and iTunes. I let it go ahead. Got to a point where it said to close iTunes before continuing update. I did close iTunes and OK'd to continue update. Right away the monitor became shaded it and said to restart. Now when I turn it off and try to restart, it makes the start-up sound and the circle clicks around and then suddenly stops. Then the blue line fills in until it gets to "Starting Network File System" and then becomes shaded again saying to restart. I did some research and tried holding down the option key while powering on. Now I have a Macintosh HD icon with a blue X, as well as a 3/4 circle w/arrow and a straight line arrow. Any help would be very, very much appreciated. Thank you. kcorbett

    bjadk,
    Welcome to the Apple Discussions!
    If Apple Hardware test is reporting RAM memory errors, no amount of reinstalling, or Disk Warrior, or anything else, will help. The install and repair attempts, sabotaged by bad RAM, would actually corrupt the hard drive worse on each attempt.
    Do you recall how much RAM was in the eMac? Did you get RAM size reports from AHT? Check the RAM slots on the eMac by opening the access door on the bottom (see eMac - Do-It-Yourself). If there are two DIMMS, pull the one in DIMM slot 1 (that'll be the one on the top if I recall correctly). Removing the bad RAM may leave you with too little RAM to actually run the eMac; you can check your eMac model and use that info to order good RAM from Crucial.
    Yet another potential problem comes to mind. If the Mac is three years old and hasn't been used much, has it been largely turned off and either unplugged, or plugged into a surge protector that was itself turned off? It the Mac hasn't been able to draw a trickle current while nominally turned off, the PRAM battery could be drained, which can also interfere with starting up and using the computer. You can use a voltmeter to check the battery while in the battery holder and replace it if it's more than 0.1v below the nominal 3.6v value.
    When AHT gives the RAM a clean bill, use your OS X Install disc to boot the computer and again try Repair Disk and/or use single-use rmode to run fsck (per Using Disk Utility and fsck). IF Repair Disk/fsck report making repairs, repeat that step until it either reports no problems found or unable to repair, since one directory error can mask other errors. As already mentioned, DiskWarrior has an excellent track record of making repairs where Disk Utility could not.
    If Disk Utility or Disk Warrior repair the disk, you can proceed to an Archive and Install (you'll need 5 GB or so free space on the hard drive to do an A&I; if space is tight, use the Installer options to select language support for only the language(s) you actually use).
    If no utility can repair the disk, an Erase & Install with the one-pass write zeros option selected could recover use of the drive, by forcing the drive to update it's record of bad disk sectors to avoid. This would lose any data and programs for which you don't have a backup or install discs, through.

  • Tomcat does not work when using only netcfg to start network

    hello!
    for myself i wrote a script to connect automatically to a wireless network using netcfg. i do not start my network via the daemon (/etc/rc.d/network).
    i have a project and so i want to use tomcat. but it does not work correct, i can start it, but i can't connect via "localhost:8080". when i start my network using the network daemon it works! apache runs fine, but i need tomcat!
    can someone help me please?
    thx, marv

    where is "lo" enabled in the network script? i did not found it and/or i have no idea which function enables it.
    can you help me please? can i just copy the lines of code to my own script and it will enable lo?
    mfg iggy

  • Starting Network...............[FAIL]

    I gotta problem with my network  on bootup, my network won't start. I think it is to do with the way my interfaces are configured in /etc/rc.conf (not sure though):
    lo="lo 127.0.0.1"
    eth0="eth0 192.168.2.5 netmask 255.255.255.0 broadcast 192.168.2.255"
    eth0="dhcp"
    INTERFACES=(lo eth0)
    The confusing thing for me is that I can start the network with /etc/rc.d/network start once I am logged in. Oh, and very rarely, my network DOES start on bootup, but 95 % of the time it does not.
    Thanks for any help and suggestions

    Right, I've finally got all the info I need to post.
    I'm not able to post my lsmod output, I don't have an internet browser configured in Arch yet, so I'm posting from FC3 on the same computer - jumping from one OS to the other, driving me nuts. Anyway, I wasn't sure how to save the output to a log file, so I'm going to post my /proc/modules instead (lsmod is just a different way to present this info, right?):
    ohci_hcd 23560 0 - Live 0xd0aa2000
    ehci_hcd 35332 0 - Live 0xd0a4c000
    parport_pc 28996 0 - Live 0xd0a43000
    parport 38600 1 parport_pc, Live 0xd0a1c000
    pcspkr 4044 0 - Live 0xd0996000
    tulip 51104 0 - Live 0xd0a94000
    snd_intel8x0 34336 0 - Live 0xd09c0000
    snd_ac97_codec 78176 1 snd_intel8x0, Live 0xd0a7f000
    snd_pcm_oss 56612 0 - Live 0xd0a70000
    snd_mixer_oss 21120 1 snd_pcm_oss, Live 0xd0a15000
    snd_pcm 101252 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss, Live 0xd0a56000
    snd_timer 27140 1 snd_pcm, Live 0xd09f8000
    snd 59108 6 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer, Live 0xd0a28000
    soundcore 10848 1 snd, Live 0xd09bc000
    snd_page_alloc 10244 2 snd_intel8x0,snd_pcm, Live 0xd09ad000
    joydev 10560 0 - Live 0xd0998000
    usbhid 45824 0 - Live 0xd09eb000
    i2c_i801 8972 0 - Live 0xd0980000
    i2c_core 23296 1 i2c_i801, Live 0xd09a6000
    usb_storage 71232 0 - Live 0xd0a02000
    uhci_hcd 34576 0 - Live 0xd09b2000
    usbcore 125560 6 ohci_hcd,ehci_hcd,usbhid,usb_storage,uhci_hcd, Live 0xd09cb000
    hw_random 5908 0 - Live 0xd0990000
    pci_hotplug 34748 0 - Live 0xd099c000
    tsdev 8128 0 - Live 0xd098d000
    evdev 9984 0 - Live 0xd0989000
    rtc 13128 0 - Live 0xd0984000
    OK, sorry it's not as visually nice as lsmod
    As for the Interfaces in /etc/rc.conf, I just got to what I did through trial and error. If I don't have both eth0= lines in there, I can't connect to the internet! (if I don't have the eth0="dhcp" line in there, the network daemon starts OK, but I don't have an internet connection, and if i don't have the other eth0 line in there, the network daemon won't start at all).
    You're right, I only have one network card, and I connect to the internet via a router which is connected to my network card and modem. I wasn't sure how to set this up in the interfaces section of /etc/rc.conf, basically I just gleaned the settings from my other OS's.
    Also, I know it's a basic question, but I'd like to shut hotplug daemon down and start up my modules manually. Is this just a case of manually commenting in the module names I want to start up into /etc/rc.conf?
    Thanks for all your help everyone

  • Weird issue starting network at boot [Solved]

    So, whenever i bootup, when it comes to starting the network, it hangs for a few seconds, then says 'fail', however, whenever i get gnome up and working, the connection is working just fine, so far, i have tried to increase the timeout though it doesn't really seem to make it wait any longer during boot...here is my rc.conf if it helps anyone, also, i am trying to connect to some NFS shares from my freeNAS box on boot, but since that fails, the network shares normally do to, but after booted, i can just do mount -a and they all connect just fine...its weird
    rc.conf:
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
    # in the hardware clock being left untouched (useful for virtualization)
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    HARDWARECLOCK="localtime"
    TIMEZONE="America/Chicago"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=(sky2 slhc snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore !usblp)
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="myhost"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    # - prefix an entry in INTERFACES with a ! to disable it
    # - no hyphens in your interface names - Bash doesn't like it
    # DHCP: Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="dhcp"
    eth0="dhcp"
    INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.2.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng dbus hal fam network rpcbind nfs-common netfs crond)
    also, i do have 'myhost' added to my hosts file as well, did so during setup...
    anyone got any ideas?
    Thanks
    Last edited by psilo357 (2009-12-21 00:02:46)

    alright, if just backgrounded 'network' it woudl cause rpcbind to start after it, but fail, so i backgrounded them all, and while network no longer says FAIL while booting, the network drives still don't mount, i still have to issue a mount -a after boot to get everything mounted...
    thanks for the tip though.  I don't mind it not running in background and waiting an extra few seconds to get everything setup as i want it to be as soon as i am logged in, just want it to all start correctly.
    EDIT:  alright, all network drives ARE mounting correctly on boot if nothing is in background, but i still don't like that network says FAIL when it is starting up, though it is apparently working...
    all help is appreciated.
    Last edited by psilo357 (2009-12-19 20:31:27)

  • Inability to See Network Computers with PPPoE

    I am using a MacBook, connected to a Linksys WRT150N wireless router. I am also using PPPoE to connect to the internet; the PPPoE settings are in the router, not in the computer.
    I would like to connect to computers in my LAN, but am not able to when PPPoE is turned on. (N.B. - I have this problem whether or not I connect to the network via the router or directly.) Turning PPPoE every time I want to connect to other computers in my network is obviously not an option. Are there any thoughts on my problem?
    (It is also important to note that I had the same problem with my iBook, running Tiger.)

    In both cases (cable directly attached or with a router), you have a firewall enabled between you and external network.
    I'm pretty sure that you also have DHCP going because if you didn't, you would be getting an 'auto-ip' address (something starting with 169). I suspect you're currently getting something like 192.168.1.x? DHCP doesn't cross router boundaries (unless configured - and a personal router wouldn't be configured to do that).
    If you want to make this work and keep your router in the mix, I suspect at the minimum you'll need to configure the router to consider your machine on the 'DMZ'. There should be a menu in there someplace that does this.
    When you setup an internal host as 'DMZ' on these routers, you're basically just thrown out on the external side of the router. So be sure to protect your system with a local firewall.
    As for when you're directly on the wire without the router, I'm not 100% certain how OS X handles its routing on PPPoE. Remember, with PPPoE, you're building a tunnel over a foreign network to a specific location, and then sending all traffic over the tunnel. The traffic wouldn't be able to break out of that tunnel to go to other network hosts by itself, so the OS would have to do what's called a 'split tunnel' and allow some traffic to stay out of the tunnel (the traffic that isn't working for you) while the rest travels in the tunnel (to the Internet).
    Hopefully with this information, you can re-arrange/re-configure things to get you going. Just be aware of your host security in doing this.
    Oh - and I'm heading out to work. Just a courtesy so you're not waiting for another reply this morning.
    Message was edited by: mreckhof

  • Have to manually start network . . .[solved]

    Hi,
    For some reason my network doesn't start when I boot, but works fine when I run dhcpcd after logging in.  I presume this is something simple, but would appreciate some help.
    The module I need is 8139too.  mkinticpio's autodetect gives 8139cp and 8139too for some reason, so I sorted that out in rc.conf.  (It didn't work when I left the modules alone, either).
    Here the relevant parts:
    MOD_BLACKLIST=(pcspkr 8139cp)
    MODULES=(8139too )
    lo="lo 127.0.0.1"
    eth0="DHCP"
    eth1="DHCP"
    INTERFACES=(lo eth0 eth1)
    #gateway="default gw 192.168.0.254"
    ROUTES=(!gateway)
    DAEMONS=(syslog-ng !hotplug !pcmcia hal network @fam @portmap @netfs @crond @alsa)
    I have network in the daemons array, but on startup it says 'cannot find device' (can't remember the exact wording) when trying to connect the network, as if the module isn't loaded yet, perhaps?  Should something be loaded before network in the daemons?
    The other thing is that I have eth0 and eth1 despite having only one network device (insofar as I'm aware) - ought this be the case?  I just stuck eth1 into rc.conf blindly since it existed.
    Any ideas on how to fix this?
    Thanks.
    Fishonadish

    Don't know wether it belongs to rc.conf, too.
    But UNIX is case-sensitive. Try to replace this line:
    eth0="DHCP"
    by
    erh0="dhcp"
    And all others that contain capitalized "DHCP".
    And why do you connect via dhcp through two network interfaces?

  • Cant see any airport option on mac mavericks..and cannot see wifi on my ipone wen i start network sharing

    cant see on available wifi networks on my iphone....when i start sharing wifi on network preferences..can anyone pls help

    sharing wifi network through macbook pro/mac mavericks

  • Start network connection during boot [KDE4]

    I want to able to connect to a network (with key) during boot.
    Right now, when my arch is booting, it is trying to connect to a dhcpcd during boot, but fails (after several seconds). Then knetworkmanager and even wicd doesn't seem to work correctly. Knetworkmanager (from KDEmod) seems like doesn't work at all.
    What can I do to make it connect during boot? (I usually connect only to one network).

    I got it working.. however, I am wondering if I have everything right in my rc.config file, in DAEMONS section (maybe I have there something extra, which I can turn off).
    #Static IP example
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    #eth0="dhcp"
    #INTERFACES=(eth0)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    # - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up. These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    NETWORKS=(wireless-wep)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng network netfs net-profiles hal !networkmanager crond alsa kdm)
    Which one do I need? network, netfs? net-profiles?
    Last edited by kdar (2009-12-16 02:17:01)

  • TC freezes while starting - Network adapter damaged?!

    Hello everyone,
    I have a TC 1TB, which worked fine a couple of month. Unfortunately, since yesterday, TC doesn't work at all, as it seems to be unable to start. From one minute to the other TC didn't appear in my Finder, TC showed a yellow light (not flashing). I tried to restart, since then, the following repeats after every restart (including those after resetting):
    TC shows a "yellow light" => shut down the TC, disconnected any cables and start again; then, shortly after showing a "green light", the light starts flashing and than continues in yellow. After a few seconds, yellow light starts flashing, TC seems to restart, ten seconds later the green light appears, followed by the same flashing and continuing in yellow.... All along, TC's drive is running.
    The Airport software recognizes my TC as soon as the green light appears, but cannot conntect because in the meantime, TC shows up with a yellow light and so on and on....
    I tried to restart several times, including different types of resetting the TC (pushing the button while TC is running as well as when connecting to power).
    Can anyone solve this?
    I do not think that my TC is dead (unlike many other postings....), because I still can start it. Anyway, I can't connect to it, neither wireless nor directly via ethernet cable....

    Hi!
    I already tried this - but it did not help. Right now I am writing this lines while looking a streamed video from my iMac. You may ask, why it works - it's easy: I plugged on my old AVM Fritzbox 3070.
    I will try this for another hour, but I guess that one thing is sure right now: the TimeCapsule is the problem, not any of my Macs or programs.
    Well - and I decided one more thing: my Fritzbox doesn't work "apple-like" using "Back to my Mac". Sometimes I need this feature. So I decided to order an AirportExtreme today. It will arrive here in the next 3 days, so I can try this next Monday.
    The TimeCapsule is very slow doing updates - so I never really liked it. Well - if the Fritzbox and the new Airport does a better job, the switch will be perfect.
    Anybody out there interested in a nice TimeCapsule 500 ?
    *EDIT - it does NOT work :,-(*
    Well - my Fritzbox worked for 15 Minutes and now the Videostreaming freezed. BUT - the network does not freeze like it does using the TimeCapsule. However - I am really interested in the AirPort Extreme and if it will make a better job.
    My "last idea": The TimeCapsule and the Fritzbox are both about 2 or 3 years old. Maybe the network-standard isn't fast enough for high quality video and causes a crash after a few minutes.
    Message was edited by: willObst

  • Starting network later

    Hello,
    Sometimes when I boot up my computer, there's no network. The solution then is to type "/etc/rc.d/network restart" as superuser.
    When I shut down my computer, I also shut down all the power, including the modem.
    When starting it up, I turn on the power, and then the computer. While the computer boots up, the modem is also starting up (it's an ADSL modem).
    Since sometimes I have network, sometimes not, I think it depends on how fast the modem started up that I have it or not. That's just my theory though. I think if ArchLinux would just init the network a little bit later, the problem would be gone.
    Is there any way to make it do the network only after initializing everything else?
    Or do you know any other (better) solution for this annoyance?
    Thanks!

    tomk wrote:
    You're talking about two completely independent unconnected power-ons - one for your computer, one for your modem. No matter how late Arch initialises the network,  there is always the chance that it will be too early for your modem.
    Solution: write a custom network init script that tests for connectivity, and loops over the required command(s) until the connection is established.
    The thing is, I never had this problem with my previous computer. My previous computer was 5 year old, and the Archlinux on it too (with 5 years of pacman -Syu history). So at least the two independent unconnected power-ons seem to be no problem for some Arch boxes. I've never created background daemons there either, or done any delay, it just never was a problem there.
    This new computer (well, half a year old in the meantime) has this problem.
    So maybe there was something better about how the old one was configured, but what could that be?
    Last edited by aardwolf (2012-09-19 19:54:44)

  • Problems starting network conection when installing Archlinux

    Hi,
    I have installed Arch, but can not install a desktop environment as my network is not up. I get the error messages 'failed to synchronize any databases' and 'transient resolver failure'. I tried different repository servers, but no luck, and then i tried ping google.com, and got 'unknown host'. I can ping 192.168.0.1. I have a broadband adsl router with an ethernet connection and a realtek ethernet card. I have never had any problems with any other distro, which all start the internet connection automatically (through DHCP i think).
    So far, i have looked at /etc/resolve.conf, which was empty. I added
    nameserver 192.168.0.1
    (which ubuntu uses) and rebooted. I tried again with 192.168.0.0 and 192.168.0.2 and a combination of the above but still could not ping google.com. I have also looked at /etc/modprobe.conf, which was empty, and added
    alias eth0 8139too
    but still nothing. Is there anything else i could try? Thanks.

    Arch does not automatically set everything up for you. Have you set up your networking in /etc/rc.conf?  Post the relevant section and we can help fix it if necessary.
    Here is the /etc/rc.conf section of the beginners guide: http://wiki.archlinux.org/index.php/Beg … .2Frc.conf
    Last edited by Allan (2008-02-02 11:40:22)

Maybe you are looking for