Results 1 to 4 of 4

Thread: No adapters recognized

  1. #1
    Just burned his ISO
    Join Date
    Jun 2009
    Posts
    5

    Default No adapters recognized

    Just booted up BT4 pre-final from USB drive and neither wireless nor wired adapters were present.

    Wired is Intel PRO/100/VE
    Wireless is Intel PRO/Wireless 3945ABG

    They were both recognized under BT3. The fact that not even the wired adapter is present makes me think there's something I've missed. Any ideas?

  2. #2
    Moderator KMDave's Avatar
    Join Date
    Jan 2010
    Posts
    2,281

    Default

    What does
    Code:
    ifconfig -a
    tell you?
    Tiocfaidh ár lá

  3. #3
    Just burned his ISO
    Join Date
    Jun 2009
    Posts
    5

    Default Now working - sorry

    I'll boot in again and try that. Main thing is it was just a false alarm. I read the review at Dedoimedo and it pinged when I read: "The network is not enabled by default and you'll have to fire it up manually.". So:

    /etc/init.d/networking start
    /etc/init.d/wicd start

    Success.

  4. #4
    Just burned his ISO
    Join Date
    Jun 2009
    Posts
    5

    Default ifconfig -a

    Result of ifconfig -a was:
    Code:
    eth0      Link encap:Ethernet  HWaddr 00:16:d4:0a:1a:31
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    wlan0     Link encap:Ethernet  HWaddr 00:13:02:57:25:6f
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    
    wmaster0  Link encap:UNSPEC  HWaddr 00-13-02-57-25-6F-00-00-00-00-00-00-00-00-00-00
              BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    By the way the 'networking start' command takes a long long time. Most of the time spent on DHCPDISCOVER requests. I shouldn't need to DHCP before I've selected a network - should I be doing something differently?

Posting Permissions

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