[ubuntu-uk] Lucid Lynx wifi not working

Thu Jul 1 19:12:40 BST 2010

> Message: 7
> Date: Wed, 30 Jun 2010 23:20:16 +0100
> From: Daniel Case <danielcase10 at googlemail.com>
> Subject: Re: [ubuntu-uk] 10.04 Wireless Toshiba Portege PP041E
> To: UK Ubuntu Talk <ubuntu-uk at lists.ubuntu.com>
> Message-ID:
> 	<AANLkTiluOL4BfKZN2hGlIP5B1j9-ln3FBj8lvK5jXTMN at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hiya Dave
> Have you checked the restricted drivers? You can also use lspci and
repost
> to let us know what wifi card you have in there.
>
> You may also want to re-title this, as google has declared it "spam" for
me...and not many people check there spam boxes
>
> Dan
>
> On 28 June 2010 20:20, <daveg at boavon.plus.com> wrote:
>
>> Completed fresh 10.04 install on this little laptop, after some
months(years?) successful running of 8.04.  Managed to overcome the
display problem with a little edit of xorg.conf but cannot get wireless
running.
>> It worked fine on 8.04 and still manages ok on on the XP partition.  I
have a very vague memory that I had to overcome display probs and
wireless
>> probs on 8.04
>> My memory was just ok for the display issues - but for the life of me I
cannot recall what I did (if anything) to get wireless going.  I have done
>> the usual searches but frankly there is more garbage and red herrings
each
>> and every day.
>> I would welcome some help or pointing in the right direction.  I can
supply some outputs if reqd, but you will need to lead me gently. Many thanks
>> DaveG

Hiya Dan and others

Message header changed following advice re potential spam.

Dont know what is meant by restricted drivers.  My other post provided
lspci output revealing I think a
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
100 (rev 0d)
Google search results for this looked promising initially but have proved
to be many red herrings or unintelligible to me.

Here is output from ifconfig -a

Ignore the wlan0 entry - that refers to a USB wireless stick I had
knocking around - but needed elsewhere.  I think its the eth1 I need to
work.  The MAC address certainly matches the router and my expectations.

eth0      Link encap:Ethernet  HWaddr 00:00:39:3f:46:a5
          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)

eth1      Link encap:Ethernet  HWaddr 00:02:2d:6a:a2:d1
          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)
          Interrupt:11 Base address:0x100

irda0     Link encap:IrLAP  HWaddr 00:00:00:00
          NOARP  MTU:2048  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:8
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:7 Base address:0x2f8

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

pan0      Link encap:Ethernet  HWaddr 66:8a:46:1b:42:0f
          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:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:0f:cb:c0:fe:cd
          inet addr:192.168.0.8  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::20f:cbff:fec0:fecd/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:5132 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3659 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2746797 (2.7 MB)  TX bytes:675609 (675.6 KB)

My /etc/network/interfaces looks like this
auto lo
iface lo inet loopback

My output from sudo lshw -C Network is as follows:-
 *-network
       description: Ethernet interface
       product: 82557/8/9/0/1 Ethernet Pro 100
       vendor: Intel Corporation
       physical id: a
       bus info: pci at 0000:00:0a.0
       logical name: eth0
       version: 0d
       serial: 00:00:39:3f:46:a5
       size: 10MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt
10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e100
driverversion=3.5.24-k2-NAPI duplex=half firmware=N/A latency=64
link=no maxlatency=56 mingnt=8 multicast=yes port=MII speed=10MB/s
       resources: irq:11 memory:f7efe000-f7efefff ioport:eec0(size=64)
memory:f7ec0000-f7edffff
  *-network
       description: Wireless LAN Card
       product: Version 01.01
       vendor: TOSHIBA
       physical id: 0
       slot: Socket 0
       resources: irq:11
  *-network:0
       description: Wireless interface
       physical id: 2
       logical name: wlan0
       serial: 00:0f:cb:c0:fe:cd
       capabilities: ethernet physical wireless
       configuration: broadcast=yes ip=192.168.0.8 multicast=yes
wireless=IEEE 802.11bg
  *-network:1
       description: Wireless interface
       physical id: 3
       logical name: eth1
       serial: 00:02:2d:6a:a2:d1
       capabilities: ethernet physical wireless
       configuration: broadcast=yes driver=orinoco driverversion=0.15
firmware=Lucent/Agere 9.48 link=no multicast=yes wireless=IEEE
802.11b

Anybody think that there may be some clues in here:-
http://web.archiveorange.com/archive/v/AGd2Zjs1ZyTJ8iqq5U6S
or is yet just another red herring?

Something in dmesg suggests that Lucent/Agere firmware doesn't support
manual roaming
Whats that about?

Finally, some extractions from dmesg about orinoco
[   22.948499] orinoco 0.15 (David Gibson <hermes at gibson.dropbear.id.au>,
Pavel Roskin <proski at gnu.org>, et al)
[   22.996141] orinoco_cs 0.15 (David Gibson
<hermes at gibson.dropbear.id.au>, Pavel Roskin <proski at gnu.org>, et al)
[   23.078063] orinoco_cs 0.0: Hardware identity 0005:0004:0005:0000
[   23.078187] orinoco_cs 0.0: Station identity  001f:0001:0008:000a
[   23.078197] orinoco_cs 0.0: Firmware determined as Lucent/Agere 8.10
[   23.350876] orinoco_cs 0.0: firmware: requesting agere_sta_fw.bin
[   23.508133] orinoco_cs 0.0: Hardware identity 0005:0004:0005:0000
[   23.508266] orinoco_cs 0.0: Station identity  001f:0002:0009:0030
[   23.508276] orinoco_cs 0.0: Firmware determined as Lucent/Agere 9.48
[   23.508284] orinoco_cs 0.0: Ad-hoc demo mode supported
[   23.508290] orinoco_cs 0.0: IEEE standard IBSS ad-hoc mode supported
[   23.508296] orinoco_cs 0.0: WEP supported, 104-bit key
[   23.508302] orinoco_cs 0.0: WPA-PSK supported
[   23.519319] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   24.122076] ADDRCONF(NETDEV_UP): eth1: link is not ready

Haven't a clue about these but thought they may be relevant.
I think I now need help :(
DaveG