[ubuntu-uk] 10.04 Wireless Toshiba Portege PP041E

Tue Jun 29 20:06:03 BST 2010

> Message: 5
> Date: Tue, 29 Jun 2010 07:49:09 +0100
> From: daveg at boavon.plus.com
> Subject: Re: [ubuntu-uk] 10.04 Wireless Toshiba Portege PP041E
> To: ubuntu-uk at lists.ubuntu.com
> Message-ID:
> 	<1eb6b7d3bbe753c5f550abd7e9a619c8.squirrel at webmail.plus.net>
> Content-Type: text/plain;charset=iso-8859-1
>
>> Message: 5
>> Date: Mon, 28 Jun 2010 21:28:07 +0100
>> From: John Stevenson <john at jr0cket.com>
>> Subject: Re: [ubuntu-uk] 10.04 Wireless Toshiba Portege PP041E
>> To: UK Ubuntu Talk <ubuntu-uk at lists.ubuntu.com>
>> Message-ID:
>> 	<AANLkTinGTJ_zHlIarJlOtfCz6OXQJPOxx5B8uNB-VfbM at mail.gmail.com>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> 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
>>>
>>
>> Hello Dave,
>> The first thing you can check is System > Administration > Hardware
>> Drivers
>>
>> With luck it should have picked up your wireless hardware and it will
>> allow
>> you to activate the 3rd party driver that will make it work.  Please
>> note
>> that you will probably need to be connected to an Internet enabled
>> network,
>> so lets hope you have a wired connection spare.
>>
>> If there is nothing in the Hardware Drivers, then try issue the
>> following
>> command in a terminal window, it should tell you what your wireless
>> hardware
>> is
>>
>> lspci
>>
>> Try a google for: Ubuntu <your wireless make model here, copied from the
>> lspci output>
>>
>> Or post the output of lspci to the list if you dont get anywhere.
>>
>> Good luck.
>> --
>> John Stevenson
>> Lean Agile Consultant / Coach
>> jr0cket.com  |  leanagilemachine.com
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> URL:
>> https://lists.ubuntu.com/archives/ubuntu-uk/attachments/20100628/2bcf60cc/attachment-0001.htm
>
>
> Many thanks for your help.  Checking System > Administration > Hardware
>> Drivers only revealed a software modem that was not activated so have
> ignored that.
> lspci output as follows:-
>
> 00:00.0 Host bridge: ALi Corporation M1644/M1644T Northbridge+Trident (rev
> 01)
> 00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
> 00:02.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
> 00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
> 00:06.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link
> Controller Audio Device (rev 01)
> 00:07.0 ISA bridge: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge
> [Aladdin IV/V/V+]
> 00:08.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
> 00:0a.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
> 100 (rev 0d)
> 00:0c.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A
> IEEE-1394a-2000 Controller (PHY/Link)
> 00:10.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus
> Controller (rev 01)
> 00:11.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to
> Cardbus Bridge with ZV Support (rev 32)
> 00:11.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to
> Cardbus Bridge with ZV Support (rev 32)
> 00:12.0 System peripheral: Toshiba America Info Systems SD TypA Controller
> (rev 03)
> 01:00.0 VGA compatible controller: Trident Microsystems CyberBlade XPAi1
> (rev 82)
>
> The google search results look more promising than earlier - but will need
> to wait until I have finished some paid employment!  Many thanks - will
> come back if I need more help or simply to report solved - hopefully!
> DaveG

Not having much luck so far - but some sites suggest some other outputs
might help diagnosing the problem.  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