No Wifi access on Jaunty with my Compaq Presario CQ50-100ED

Bug #356757 reported by hosoka
8
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

This is the same question found here but I'm working on Jaunty.
https://answers.launchpad.net/ubuntu/+question/50808

I did a clean install of Jaunty and updated with all the latest updates.

I notices through google that many users had problems with the wifi button on the keyboard. Seems not to be active on linux.
There is a built-in wifi card of Atheros. Can't tell which it is, you might check the specification for this model.
Tried with madwifi and without...
I noticed that anytime there is a new update on Jaunty, I need to configure everything again. Now after new updates, my wifi is totally gone.

Hope someone can help me out on this or it might be usefull to have it standard for all the Ubuntu users that are working with Atheros wifi built-in cards.

Tags: jaunty
Revision history for this message
hosoka (hosoka-deactivatedaccount-deactivatedaccount) wrote :
Download full text (20.9 KiB)

I've done some commands of what Mark Rijckenberg requested in previous #50808 for e.g. and getting these outcomes from the Terminal. Hope this will helps out:

          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

pan0 no wireless extensions.

hosoka@hosoka-laptop:~$ ping -c 4 google.com
PING google.com (74.125.67.100) 56(84) bytes of data.
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=1 ttl=243 time=132 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=2 ttl=243 time=131 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=3 ttl=243 time=132 ms
64 bytes from gw-in-f100.google.com (74.125.67.100): icmp_seq=4 ttl=243 time=133 ms

--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 131.109/132.352/133.753/1.006 ms
hosoka@hosoka-laptop:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:1d:72:65:dc:d8
          inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::21d:72ff:fe65:dcd8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:789 errors:0 dropped:0 overruns:0 frame:0
          TX packets:928 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:670539 (670.5 KB) TX bytes:155532 (155.5 KB)
          Interrupt:253 Base address:0x6000

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:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)

wlan0 Link encap:Ethernet HWaddr 00:1f:e2:b0:48:2e
          UP 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-1F-E2-B0-48-2E-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING 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)

hosoka@hosoka-laptop:~$ netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
link-local * 255.255.0.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
hosoka@hosoka-laptop:~$ sudo lshw -C network
[sudo] password for hosoka:
  *-network
       description: Ethernet interface
       product: MCP78S [GeForce 8200] Ethernet
       vendor: nV...

Monkey (monkey-libre)
tags: added: jaunty
Revision history for this message
David Tombs (dgtombs) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
hosoka (hosoka-deactivatedaccount-deactivatedaccount) wrote : RE: [Bug 356757] Re: No Wifi access on Jaunty with my Compaq Presario CQ50-100ED

Hello,
This case can be closed.

> Date: Sun, 9 May 2010 18:27:01 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 356757] Re: No Wifi access on Jaunty with my Compaq Presario CQ50-100ED
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. We are sorry that we do not always have the capacity to
> look at all reported bugs in a timely manner. There have been many
> changes in Ubuntu since that time you reported the bug and your problem
> may have been fixed with some of the updates. Can you try with the
> latest Ubuntu release? Thanks in advance.
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
> --
> No Wifi access on Jaunty with my Compaq Presario CQ50-100ED
> https://bugs.launchpad.net/bugs/356757
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
De Nieuwste Internet Explorer speciaal voor Hotmail, download nu gratis
http://www.microsoft.com/netherlands/ie8/hotmail.htm

Revision history for this message
David Tombs (dgtombs) wrote :

OK, thanks for the update.

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.