1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Just starting to use Hardy. HELP!!!!!!!

Discussion in 'Tech Support' started by Neoki, 16 May 2008.

  1. Neoki

    Neoki Minimodder

    Joined:
    26 Oct 2004
    Posts:
    951
    Likes Received:
    2
    Never used linux ever ever before so I am completely new to this thing.

    So far impressed yet my broadcom 4311 does not work. Had a quick look around followed the guides on all these strange commands but no luck

    I have installed ubuntu-8.04-desktop and followed This


    So any ideas?
     
    Last edited: 16 May 2008
  2. steveo_mcg

    steveo_mcg What's a Dremel?

    Joined:
    26 May 2005
    Posts:
    5,841
    Likes Received:
    80
    how far do you get? Can you get to the end of the guide with an error?
     
  3. Neoki

    Neoki Minimodder

    Joined:
    26 Oct 2004
    Posts:
    951
    Likes Received:
    2
    well I manage to get to the end fine but it does not work. :(
     
  4. steveo_mcg

    steveo_mcg What's a Dremel?

    Joined:
    26 May 2005
    Posts:
    5,841
    Likes Received:
    80
    Do you have dhcp installed on a router? Whats comes up on the screen when you run
    Code:
    sudo dhclient
     
  5. Neoki

    Neoki Minimodder

    Joined:
    26 Oct 2004
    Posts:
    951
    Likes Received:
    2
    wmaster0: unknown hardware address type 801
    SIOCSIFFLAGS: No such file or directory
    SIOCSIFFLAGS: No such file or directory
    SIOCSIFFLAGS: Operation not supported
    SIOCSIFFLAGS: Operation not supported
    wmaster0: unknown hardware address type 801
    Listening on LPF/wlan0/00:14:a5:7e:d6:92
    Sending on LPF/wlan0/00:14:a5:7e:d6:92
    Listening on LPF/wmaster0/
    Sending on LPF/wmaster0/
    Listening on LPF/eth0/00:16:d4:00:bc:84
    Sending on LPF/eth0/00:16:d4:00:bc:84
    Sending on Socket/fallback
    receive_packet failed on wlan0: Network is down
    receive_packet failed on wmaster0: Network is down
    DHCPDISCOVER on wmaster0 to 255.255.255.255 port 67 interval 3
    send_packet: Network is down
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
    DHCPOFFER of 192.168.2.60 from 192.168.2.1
    DHCPREQUEST of 192.168.2.60 on eth0 to 255.255.255.255 port 67
    DHCPACK of 192.168.2.60 from 192.168.2.1
    bound to 192.168.2.60 -- renewal in 842 seconds.

    Connected to ethernet at the moment how ever the wireless does not work at all.
     
  6. steveo_mcg

    steveo_mcg What's a Dremel?

    Joined:
    26 May 2005
    Posts:
    5,841
    Likes Received:
    80
    Ah, ok try putting the eth0 down and bringing up wlan0
    Code:
     sudo ifdown eth0
    sudo ifup wlan0
    sudo dhclient 
    I must confess to not being fluent in wireless so i'm not sure if thats the problem but at least we can eliminate general network problems.
     
  7. Gareth Halfacree

    Gareth Halfacree WIIGII! Lover of bit-tech Administrator Super Moderator Moderator

    Joined:
    4 Dec 2007
    Posts:
    17,133
    Likes Received:
    6,728
    Paste the results of an sudo ifconfig and a sudo iwconfig, and we'll have a better idea of what's going on.
     
  8. Neoki

    Neoki Minimodder

    Joined:
    26 Oct 2004
    Posts:
    951
    Likes Received:
    2
    eth0 Link encap:Ethernet HWaddr 00:16:d4:00:bc:84
    inet addr:192.168.2.60 Bcast:192.168.2.255 Mask:255.255.255.0
    inet6 addr: fe80::216:d4ff:fe00:bc84/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1912 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1961 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:1673253 (1.5 MB) TX bytes:315984 (308.5 KB)
    Interrupt:21 Base address:0xa000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:2614 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2614 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:145020 (141.6 KB) TX bytes:145020 (141.6 KB)

    lo no wireless extensions.

    eth0 no wireless extensions.

    wmaster0 no wireless extensions.

    wlan0 IEEE 802.11g ESSID:""
    Mode:Managed Channel:0 Access Point: Not-Associated
    Tx-Power=0 dBm
    Retry min limit:7 RTS thr:eek:ff Fragment thr=2346 B
    Encryption key:eek:ff
    Link Quality:0 Signal level:0 Noise level:0
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
     
  9. Gareth Halfacree

    Gareth Halfacree WIIGII! Lover of bit-tech Administrator Super Moderator Moderator

    Joined:
    4 Dec 2007
    Posts:
    17,133
    Likes Received:
    6,728
    Okay, now try sudo iwlist wlan0 scanning and post the results.
     
  10. Max Spain

    Max Spain What's a Dremel?

    Joined:
    18 Jul 2007
    Posts:
    43
    Likes Received:
    0
    It would appear that your wireless card is being detected. Can you see any wireless networks with Network Manager (in the upper right of your screen aka nm-applet). Just click on it and it should show you your wired network connection and any wireless ones it can detect. Also, it always prefers wired connections to wireless ones, so you might have to unplug your wired connection.

    And for future reference, Intel wireless Cheesecake :clap:
     
  11. Fophillips

    Fophillips What's a Dremel?

    Joined:
    9 Oct 2006
    Posts:
    948
    Likes Received:
    1
    Just a note, sudo runs thing as superuser, giving you full access. I’m sure people here won’t tell you to do malicious things but you want to be careful around "sudo", "su", and "login as root".

    Also, could you try running dhclient again, and then posting the output of `dmesg | tail`. That command looks at system messages and prints the last few.
     
Tags:

Share This Page