Find the answer to your Linux question:
Results 1 to 5 of 5
Hi guys. After recompiling 2.6.18 kernel, now each time i reboot i have to type "# dhclient ath0" to receive IP. I have no problems when i boot original 2.6.18 ...
  1. #1
    Just Joined! polyunix's Avatar
    Join Date
    Jul 2007
    Posts
    5

    DHCP problems.



    Hi guys.

    After recompiling 2.6.18 kernel, now each time i reboot i have to type
    "# dhclient ath0" to receive IP.
    I have no problems when i boot original 2.6.18 kernel. the difference between these two is the only proper type of processor i changed and that's it.
    i use madwifi 0.9.3 drv + wep key
    # /etc/networks/interfaces
    # The loopback network interface
    auto lo
    iface lo inet loopback

    # The primary network interface
    #allow-hotplug eth1
    #iface eth1 inet dhcp

    # The secondary network interface
    allow-hotplug ath0
    iface ath0 inet dhcp
    wireless-essid my-essid
    wireless-key MY-KEY


    auto ath0

    Any ideas?
    Thanks

  2. #2
    Linux Newbie
    Join Date
    Feb 2006
    Location
    Dover, DE
    Posts
    112
    Make sure the module is being loaded at boot.
    Code:
    lsmod | grep ath
    My madwifi module is ath_pci but yours may be ath_somethingelse (you can find out by running lsmod while your card is working). If lsmod doesn't return anything try adding ath_pci (or whatever yours is) to the file /etc/modules

  3. #3
    Just Joined! polyunix's Avatar
    Join Date
    Jul 2007
    Posts
    5
    Hi jonantice. Thanks for reply.

    This is my lsmod.

    # lsmod | grep ath
    ath_rate_sample 10720 1
    ath_pci 80192 0
    wlan 174468 5 wlan_wep,wlan_scan_sta,ath_rate_sample,ath_pci
    ath_hal 191088 3 ath_rate_sample,ath_pci

    It looks ok.

    I think if it was about ath_.... module it wouldn't load the wireless device altogether. Although in my case, it loads wireless, but it cant obtain IP from DHCP, but it can get IP when i choose another kernel at boot.

  4. #4
    Just Joined! polyunix's Avatar
    Join Date
    Jul 2007
    Posts
    5
    New discovery.

    It loads the network eventually but in 5 min after i login. it's weird. when i boot the other kernel it receives IP on boot process.

  5. #5
    Just Joined! polyunix's Avatar
    Join Date
    Jul 2007
    Posts
    5
    Ok.
    I found what caused the problem. At one of those updates Debian installed its own madwifi modules and they interact with madwifi modules that i compiled from the source. I opened synaptic and removed Debian's madwifi source, madwifi-tools and madwifi-module.
    The problem is solved!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •