Quantcast

WiFi problems

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

WiFi problems

joncoops
I am trying to get the WiFi working on my Overo Fire follwoing the instructions posted at http://wiki.gumstix.org/index.php?title=Overo_Wifi and I am getting problems at boot. Once I remove networkmanager the wlan0 interface does not seem to come up until some time after the boot sequence has completed and as a result several of the boot steps fail. I can get the WiFi to work if I restart the network after boot /etc/init.d/networking restart although it sometimes takes a couple of attempts. I am assuming the hardware is good, but that there is something flaky with the kernel or driver, any pointers on debuging or fixing the problem would be much appreciated.

Below are the boot errors I am seeing.


[snip]
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
lib80211: common routines for IEEE802.11 drivers
cfg80211: Calling CRDA to update world regulatory domain
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman
Remounting root file system...

udevadm settle - timeout of 8 seconds reached, the event queue contains:
  /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0 (639)
  /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p1 (640)
  /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p2 (641)
  /sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1 (644)
Caching udev devnodes
Populating dev cache
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
Cleaning: /etc/network/run/ifstate.
Configuring network interfaces... Error for wireless request "Set Encode" (8B2A) :
    SET failed on device wlan0 ; No such device.
Failed to bring up wlan0.
done.
Starting portmap daemon: portmap.
[snip]
...
[snip]
Starting GPE display manager: gpe-dm

.---O---.
|       |                  .-.           o o
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                -'  |
                '---'

The Angstrom Distribution overo ttyO2

Angstrom 2011.03 overo ttyO2

overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
libertas_sdio mmc1:0001:1: wlan0: Features changed: 0x00004800 -> 0x00004000
libertas: wlan0: Marvell WLAN 802.11 adapter
libertas: assoc: bss   (null) not in scan results
ADDRCONF(NETDEV_UP): wlan0: link is not ready
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Brett Hemes-2

I had some similar issues and was able to work through them.  What does your /etc/network/interfaces file look like (any uncommented wlan0 entries)?

Brett
On Sep 19, 2011 5:58 PM, "joncoops" <[hidden email]> wrote:
>
>
> I am trying to get the WiFi working on my Overo Fire follwoing the
> instructions posted at http://wiki.gumstix.org/index.php?title=Overo_Wifi
> and I am getting problems at boot. Once I remove networkmanager the wlan0
> interface does not seem to come up until some time after the boot sequence
> has completed and as a result several of the boot steps fail. I can get the
> WiFi to work if I restart the network after boot /etc/init.d/networking
> restart although it sometimes takes a couple of attempts. I am assuming the
> hardware is good, but that there is something flaky with the kernel or
> driver, any pointers on debuging or fixing the problem would be much
> appreciated.
>
> Below are the boot errors I am seeing.
>
>
> [snip]
> usbcore: registered new interface driver option
> option: v0.7.2:USB Driver for GSM modems
> lib80211: common routines for IEEE802.11 drivers
> cfg80211: Calling CRDA to update world regulatory domain
> libertas_sdio: Libertas SDIO driver
> libertas_sdio: Copyright Pierre Ossman
> Remounting root file system...
>
> udevadm settle - timeout of 8 seconds reached, the event queue contains:
>
> /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0
> (639)
>
> /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p1
> (640)
>
> /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p2
> (641)
>
> /sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1
> (644)
> Caching udev devnodes
> Populating dev cache
> NET: Registered protocol family 10
> ALSA: Restoring mixer settings...
> Cleaning: /etc/network/run/ifstate.
> Configuring network interfaces... Error for wireless request "Set Encode"
> (8B2A) :
>    SET failed on device wlan0 ; No such device.
> Failed to bring up wlan0.
> done.
> Starting portmap daemon: portmap.
> [snip]
> ...
> [snip]
> Starting GPE display manager: gpe-dm
>
> .---O---.
> |       |                  .-.           o o
> |   |   |-----.-----.-----.| |   .----..-----.-----.
> |       |     | __  |  ---'| '--.|  .-'|     |     |
> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>                -'  |
>                '---'
>
> The Angstrom Distribution overo ttyO2
>
> Angstrom 2011.03 overo ttyO2
>
> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
> libertas_sdio mmc1:0001:1: wlan0: Features changed: 0x00004800 -> 0x00004000
> libertas: wlan0: Marvell WLAN 802.11 adapter
> libertas: assoc: bss   (null) not in scan results
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> --
> View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32473984.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> gumstix-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gumstix-users


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Nick Starzicki
Hi
I am pasting the whole process I documented that worked for me:

For testing:

root@overo:~# iwconfig wlan0 essid any

root@overo:~# ifconfig wlan0 up

root@overo:~# iwlist wlan0 scan

 

Now configuration:

root@overo:~# cat >> /etc/network/interfaces

allow-hotplug wlan0

auto wlan0

iface wlan0 inet dhcp

        pre-up /sbin/iwconfig wlan0 essid any

        wireless_mode managed

(pressed ctrl C to exit this mode)

Remove networkmanager: (I had to remove it for wifi to work)

root@overo:~# opkg remove networkmanager --force-depends

root@overo:~# ifdown wlan0

root@overo:~# ifup wlan0

 

I entered: ping google.com to check if you have a connection.

root@overo:~# ping google.com

If there is no connection you can try bringing network down and up again.

This will give you information regarding your connections:

root@overo:~# ifconfig –a

For more information:

http://wiki.gumstix.org/index.php?title=Overo_Wifi

The problem for me is that this way wifi does not start by itself on boot, so I tried the following:

1)

Creating the file : "/etc/modprobe.conf" with the content:

options libertas_sdio helper_name="sd8686_helper.bin"

options libertas_sdio fw_name="sd8686.bin"

 

This only works if I connect through serial as usual, and then type "boot", and then it works automatically.

 

2)

Add a script into /etc/init.d/, but first change directory:

cd /etc/init.d/

 

I added a file using "nano myInit.sh"

Then added the following text to the file:

#!/bin/sh

Ifdown wlan0

Ifup wlan0

 

This script should be marked as executable:

chmod +x myInit.sh

 

Your next step is to add a symlink to this script from /etc/rc5.d/

First change directory "cd /etc/rc5.d/"

Then type: "ln -s ../init.d/myInit.sh S96myInit"

 

S: basically says to run a script on startup,

96: is for the ordering of when the scripts are run.

myInit: is a name for our own reference.

 

In order to check that you don't use the same ordering number twice, check using this command:

"ls –la" while in the /etc/rc5.d/ directory

The highest number script which is generally pre-installed on a basic Gumstix Buildroot or OE system is S90, but better check!

 

To check that it works beforehand, type:

/etc/rc5.d/S96myInit

 

For more information:

http://www.iualdii.net/articles/gumstix-boot-scripts



On 20 September 2011 03:08, Brett Hemes <[hidden email]> wrote:

I had some similar issues and was able to work through them.  What does your /etc/network/interfaces file look like (any uncommented wlan0 entries)?

Brett


On Sep 19, 2011 5:58 PM, "joncoops" <[hidden email]> wrote:
>
>
> I am trying to get the WiFi working on my Overo Fire follwoing the
> instructions posted at http://wiki.gumstix.org/index.php?title=Overo_Wifi
> and I am getting problems at boot. Once I remove networkmanager the wlan0
> interface does not seem to come up until some time after the boot sequence
> has completed and as a result several of the boot steps fail. I can get the
> WiFi to work if I restart the network after boot /etc/init.d/networking
> restart although it sometimes takes a couple of attempts. I am assuming the
> hardware is good, but that there is something flaky with the kernel or
> driver, any pointers on debuging or fixing the problem would be much
> appreciated.
>
> Below are the boot errors I am seeing.
>
>
> [snip]
> usbcore: registered new interface driver option
> option: v0.7.2:USB Driver for GSM modems
> lib80211: common routines for IEEE802.11 drivers
> cfg80211: Calling CRDA to update world regulatory domain
> libertas_sdio: Libertas SDIO driver
> libertas_sdio: Copyright Pierre Ossman
> Remounting root file system...
>
> udevadm settle - timeout of 8 seconds reached, the event queue contains:
>
> /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0
> (639)
>
> /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p1
> (640)
>
> /sys/devices/platform/omap/omap_hsmmc.0/mmc_host/mmc0/mmc0:b368/block/mmcblk0/mmcblk0p2
> (641)
>
> /sys/devices/platform/omap/omap_hsmmc.1/mmc_host/mmc1/mmc1:0001/mmc1:0001:1
> (644)
> Caching udev devnodes
> Populating dev cache
> NET: Registered protocol family 10
> ALSA: Restoring mixer settings...
> Cleaning: /etc/network/run/ifstate.
> Configuring network interfaces... Error for wireless request "Set Encode"
> (8B2A) :
>    SET failed on device wlan0 ; No such device.
> Failed to bring up wlan0.
> done.
> Starting portmap daemon: portmap.
> [snip]
> ...
> [snip]
> Starting GPE display manager: gpe-dm
>
> .---O---.
> |       |                  .-.           o o
> |   |   |-----.-----.-----.| |   .----..-----.-----.
> |       |     | __  |  ---'| '--.|  .-'|     |     |
> |   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
> '---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
>                -'  |
>                '---'
>
> The Angstrom Distribution overo ttyO2
>
> Angstrom 2011.03 overo ttyO2
>
> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
> libertas_sdio mmc1:0001:1: wlan0: Features changed: 0x00004800 -> 0x00004000
> libertas: wlan0: Marvell WLAN 802.11 adapter
> libertas: assoc: bss   (null) not in scan results
> ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> --
> View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32473984.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> gumstix-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users



------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Gerhard H.
In reply to this post by joncoops

Hello,

I guess I have the same problem on the latest console Image from
http://cumulus.gumstix.org/images/angstrom/developer/2011-08-30-1058/

Sometimes during startup it lasts around 2 Minutes till the line
[snip]
libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
[snip]

is printed to the console and
sometimes the startup runs through quite fluently and after some time I get
the output as Jon was pasting it. After that it is possible to start the
wlan using iwconfig, but not before (see snip from Jon below).

joncoops wrote:
>
> [snip]
> libertas_sdio: Copyright Pierre Ossman
> ....
> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>

Jon, do you have also sometimes the situation, that "libertas:
00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303" is already printed during
startup after around 2 Minutes?

@Nick and Eric:
Either "Ifdown wlan0..." nor adjustments in "/etc/.../Interfaces" will work
as long as this "libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303"
output was not printed to the console

Gerhard
--
View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32503864.html
Sent from the Gumstix mailing list archive at Nabble.com.


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Eric Diethorn

Gerhard,

Nice information.

I must correct my first post. Adding "iwlist..." to /etc/network/interfaces
alone does not solve the problem I experienced wherein DHCP is not assigned.
I used Nick Starzicki's method, in his post in this thread, and now I see
100% success on power-up boot. That is, just add a boot process (mine in
/etc/rc5.d) that is second to last just behind the final login process and
have it perform "ifdown -a" followed by "ifup -a". I still find the need for
"iwlist..." in interfaces, however.

Eric


Gerhard H. wrote:

>
> Hello,
>
> I guess I have the same problem on the latest console Image from
> http://cumulus.gumstix.org/images/angstrom/developer/2011-08-30-1058/
>
> Sometimes during startup it lasts around 2 Minutes till the line
> [snip]
> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
> [snip]
>
> is printed to the console and
> sometimes the startup runs through quite fluently and after some time I
> get the output as Jon was pasting it. After that it is possible to start
> the wlan using iwconfig, but not before (see snip from Jon below).
>
> joncoops wrote:
>>
>> [snip]
>> libertas_sdio: Copyright Pierre Ossman
>> ....
>> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>>
>
> Jon, do you have also sometimes the situation, that "libertas:
> 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303" is already printed during
> startup after around 2 Minutes?
>
> @Nick and Eric:
> Either "Ifdown wlan0..." nor adjustments in "/etc/.../Interfaces" will
> work as long as this "libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap
> 0x00000303" output was not printed to the console
>
> Gerhard
>

--
View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32503899.html
Sent from the Gumstix mailing list archive at Nabble.com.


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Gerhard H.
In reply to this post by joncoops

Hello,

I guess I have the same problem on the latest console Image from
http://cumulus.gumstix.org/images/angstrom/developer/2011-08-30-1058/

Sometimes during startup it lasts around 2 Minutes till the line
[snip]
libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
[snip]

is printed to the console and
sometimes the startup runs through quite fluently and after some time I get
the output as Jon was pasting it. After that it is possible to start the
wlan using iwconfig, but not before (see snip from Jon below).

joncoops wrote:
>
> [snip]
> libertas_sdio: Copyright Pierre Ossman
> ....
> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>

Jon, do you have also sometimes the situation, that "libertas:
00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303" is already printed during
startup after around 2 Minutes?

@Nick and Eric:
Either "Ifdown wlan0..." nor adjustments in "/etc/.../Interfaces" will work
as long as this "libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303"
output was not printed to the console

Gerhard

FYI: sent again because I had problems that the post was accepted by the
mailing list
--
View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32503929.html
Sent from the Gumstix mailing list archive at Nabble.com.


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

joncoops
In reply to this post by Gerhard H.
Gerhard,

As you observe it seems to take a while and then I get the
[snip]
libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
[snip]
message after that I can start the interface. Before this when typing ifconfig the interface for the WiFi does not show up.

I have added a deamon process to check periodicallty for connectivity and restart the network interface if it cannot reach the internet. This seems like using a sledge hammer to crack a walnut, but it works. I am really curious why the WiFi hardware does not seem to come up on boot.

Jon


Gerhard H. wrote
Hello,

I guess I have the same problem on the latest console Image from
http://cumulus.gumstix.org/images/angstrom/developer/2011-08-30-1058/

Sometimes during startup it lasts around 2 Minutes till the line
[snip]
libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
[snip]

is printed to the console and
sometimes the startup runs through quite fluently and after some time I get
the output as Jon was pasting it. After that it is possible to start the
wlan using iwconfig, but not before (see snip from Jon below).

joncoops wrote:
>
> [snip]
> libertas_sdio: Copyright Pierre Ossman
> ....
> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>

Jon, do you have also sometimes the situation, that "libertas:
00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303" is already printed during
startup after around 2 Minutes?

@Nick and Eric:
Either "Ifdown wlan0..." nor adjustments in "/etc/.../Interfaces" will work
as long as this "libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303"
output was not printed to the console

Gerhard
--
View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32503864.html
Sent from the Gumstix mailing list archive at Nabble.com.


------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
gumstix-users mailing list
gumstix-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Replic8tor
I just wanted to note that I am experiencing a delay in wlan0
appearing. It takes several minutes, 2-5, for the messages like

libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303

to show up. After it does everything works great. I don't know if
Nick's method was attempting to solve this but it did not work for me.

I am compiled from openembedded using the over-2011.03 branch, current
as of today.

On 27 September 2011 10:56, joncoops <[hidden email]> wrote:

>
> Gerhard,
>
> As you observe it seems to take a while and then I get the
> [snip]
> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
> [snip]
> message after that I can start the interface. Before this when typing
> ifconfig the interface for the WiFi does not show up.
>
> I have added a deamon process to check periodicallty for connectivity and
> restart the network interface if it cannot reach the internet. This seems
> like using a sledge hammer to crack a walnut, but it works. I am really
> curious why the WiFi hardware does not seem to come up on boot.
>
> Jon
>
>
>
> Gerhard H. wrote:
>>
>>
>> Hello,
>>
>> I guess I have the same problem on the latest console Image from
>> http://cumulus.gumstix.org/images/angstrom/developer/2011-08-30-1058/
>>
>> Sometimes during startup it lasts around 2 Minutes till the line
>> [snip]
>> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>> [snip]
>>
>> is printed to the console and
>> sometimes the startup runs through quite fluently and after some time I
>> get
>> the output as Jon was pasting it. After that it is possible to start the
>> wlan using iwconfig, but not before (see snip from Jon below).
>>
>> joncoops wrote:
>>>
>>> [snip]
>>> libertas_sdio: Copyright Pierre Ossman
>>> ....
>>> overo login: libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>>>
>>
>> Jon, do you have also sometimes the situation, that "libertas:
>> 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303" is already printed during
>> startup after around 2 Minutes?
>>
>> @Nick and Eric:
>> Either "Ifdown wlan0..." nor adjustments in "/etc/.../Interfaces" will
>> work
>> as long as this "libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303"
>> output was not printed to the console
>>
>> Gerhard
>> --
>> View this message in context:
>> http://old.nabble.com/WiFi-problems-tp32473984p32503864.html
>> Sent from the Gumstix mailing list archive at Nabble.com.
>>
>>
>> ------------------------------------------------------------------------------
>> All of the data generated in your IT infrastructure is seriously valuable.
>> Why? It contains a definitive record of application performance, security
>> threats, fraudulent activity, and more. Splunk takes this data and makes
>> sense of it. IT sense. And common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy2
>> _______________________________________________
>> gumstix-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>>
>>
>
> --
> View this message in context: http://old.nabble.com/WiFi-problems-tp32473984p32537024.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> gumstix-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

victoraa
Hello,
any solution for this? I have a similar situation. Sometimes the Overo COM starts but it doesn't detect the wifi until some minutes, and other times it hangs the booting some minutes until it detects the wireless interface.
When the booting is stoping I get these messages:

....
Starting udev
udevd (74): /proc/74/oom_adj is deprecated, please use /proc/74/oom_score_adj instead.
lib80211: common routines for IEEE802.11 drivers
cfg80211: Calling CRDA to update world regulatory domain
libertas_sdio: Libertas SDIO driver
libertas_sdio: Copyright Pierre Ossman

(... wait some minutes ..)

libertas_sdio mmc1:0001:1: (unregistered net_device): 00:19:88:3a:af:63, fw 9.70.7p0, cap 0x00000303
libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter
...

I am compiled from openembedded using the over-2011.03 branch, too.

root@overo:~# uname -a
Linux overo 3.0.0 #1 Tue Nov 8 17:52:03 CET 2011 armv7l GNU/Linux

Thanks.

Replic8tor wrote
I just wanted to note that I am experiencing a delay in wlan0
appearing. It takes several minutes, 2-5, for the messages like

libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303

to show up. After it does everything works great. I don't know if
Nick's method was attempting to solve this but it did not work for me.

I am compiled from openembedded using the over-2011.03 branch, current
as of today.

On 27 September 2011 10:56, joncoops <joncoops@yahoo.com> wrote:
>
> Gerhard,
>
> As you observe it seems to take a while and then I get the
> [snip]
> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
> [snip]
> message after that I can start the interface. Before this when typing
> ifconfig the interface for the WiFi does not show up.
>
> I have added a deamon process to check periodicallty for connectivity and
> restart the network interface if it cannot reach the internet. This seems
> like using a sledge hammer to crack a walnut, but it works. I am really
> curious why the WiFi hardware does not seem to come up on boot.
>
> Jon
>
>
>
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

victoraa
Hello everybody,

The same for the last prebuild image from the Gumstix repository (for
omap3-console-image), that use the kernel 3.0 too.
How can I stabilize this situation?
I boot and I don't have wifi until 1-5 minutes later.

Thanks a lot.


----- Original Message -----
From: "Víctor Andrés" <[hidden email]>
To: <[hidden email]>
Sent: Wednesday, November 09, 2011 12:45 PM
Subject: Re: [Gumstix-users] WiFi problems


>
> Hello,
> any solution for this? I have a similar situation. Sometimes the Overo COM
> starts but it doesn't detect the wifi until some minutes, and other times
> it
> hangs the booting some minutes until it detects the wireless interface.
> When the booting is stoping I get these messages:
>
> ....
> Starting udev
> udevd (74): /proc/74/oom_adj is deprecated, please use
> /proc/74/oom_score_adj instead.
> lib80211: common routines for IEEE802.11 drivers
> cfg80211: Calling CRDA to update world regulatory domain
> libertas_sdio: Libertas SDIO driver
> libertas_sdio: Copyright Pierre Ossman
>
> (... wait some minutes ..)
>
> libertas_sdio mmc1:0001:1: (unregistered net_device): 00:19:88:3a:af:63,
> fw
> 9.70.7p0, cap 0x00000303
> libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter
> ...
>
> I am compiled from openembedded using the over-2011.03 branch, too.
>
> root@overo:~# uname -a
> Linux overo 3.0.0 #1 Tue Nov 8 17:52:03 CET 2011 armv7l GNU/Linux
>
> Thanks.
>
>
> Replic8tor wrote:
>>
>> I just wanted to note that I am experiencing a delay in wlan0
>> appearing. It takes several minutes, 2-5, for the messages like
>>
>> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>>
>> to show up. After it does everything works great. I don't know if
>> Nick's method was attempting to solve this but it did not work for me.
>>
>> I am compiled from openembedded using the over-2011.03 branch, current
>> as of today.
>>
>> On 27 September 2011 10:56, joncoops <[hidden email]> wrote:
>>>
>>> Gerhard,
>>>
>>> As you observe it seems to take a while and then I get the
>>> [snip]
>>> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>>> [snip]
>>> message after that I can start the interface. Before this when typing
>>> ifconfig the interface for the WiFi does not show up.
>>>
>>> I have added a deamon process to check periodicallty for connectivity
>>> and
>>> restart the network interface if it cannot reach the internet. This
>>> seems
>>> like using a sledge hammer to crack a walnut, but it works. I am really
>>> curious why the WiFi hardware does not seem to come up on boot.
>>>
>>> Jon
>>>
>>>
>>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/WiFi-problems-tp32473984p32810337.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> gumstix-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/gumstix-users 


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

victoraa
Nobody have this situation? (hung startup until wifi is detected )

libertas_sdio mmc1:0001:1: (unregistered net_device): 00:19:88:3a:af:63, fw
9.70.7p0, cap 0x00000303
libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter

I have updated the MLO of the Overo but it continues. It's a Overo COM Air.
I'm trying to build a kernel image with the last kernel avaliable (3.0 from
the Sakoman repository, following the oficial Gumstix building steps), but I
have this strange situation.

I want to know if anyone else have this or this is anything for my
situation.

Thanks a lot.


----- Original Message -----
From: "Víctor Andrés" <[hidden email]>
To: <[hidden email]>
Sent: Wednesday, November 09, 2011 12:45 PM
Subject: Re: [Gumstix-users] WiFi problems


>
> Hello,
> any solution for this? I have a similar situation. Sometimes the Overo COM
> starts but it doesn't detect the wifi until some minutes, and other times
> it
> hangs the booting some minutes until it detects the wireless interface.
> When the booting is stoping I get these messages:
>
> ....
> Starting udev
> udevd (74): /proc/74/oom_adj is deprecated, please use
> /proc/74/oom_score_adj instead.
> lib80211: common routines for IEEE802.11 drivers
> cfg80211: Calling CRDA to update world regulatory domain
> libertas_sdio: Libertas SDIO driver
> libertas_sdio: Copyright Pierre Ossman
>
> (... wait some minutes ..)
>
> libertas_sdio mmc1:0001:1: (unregistered net_device): 00:19:88:3a:af:63,
> fw
> 9.70.7p0, cap 0x00000303
> libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter
> ...
>
> I am compiled from openembedded using the over-2011.03 branch, too.
>
> root@overo:~# uname -a
> Linux overo 3.0.0 #1 Tue Nov 8 17:52:03 CET 2011 armv7l GNU/Linux
>
> Thanks.
>
>
> Replic8tor wrote:
>>
>> I just wanted to note that I am experiencing a delay in wlan0
>> appearing. It takes several minutes, 2-5, for the messages like
>>
>> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>>
>> to show up. After it does everything works great. I don't know if
>> Nick's method was attempting to solve this but it did not work for me.
>>
>> I am compiled from openembedded using the over-2011.03 branch, current
>> as of today.
>>
>> On 27 September 2011 10:56, joncoops <[hidden email]> wrote:
>>>
>>> Gerhard,
>>>
>>> As you observe it seems to take a while and then I get the
>>> [snip]
>>> libertas: 00:19:88:3e:7e:d2, fw 9.70.7p0, cap 0x00000303
>>> [snip]
>>> message after that I can start the interface. Before this when typing
>>> ifconfig the interface for the WiFi does not show up.
>>>
>>> I have added a deamon process to check periodicallty for connectivity
>>> and
>>> restart the network interface if it cannot reach the internet. This
>>> seems
>>> like using a sledge hammer to crack a walnut, but it works. I am really
>>> curious why the WiFi hardware does not seem to come up on boot.
>>>
>>> Jon
>>>
>>>
>>>
>>
>
> --
> View this message in context:
> http://old.nabble.com/WiFi-problems-tp32473984p32810337.html
> Sent from the Gumstix mailing list archive at Nabble.com.
>
>

------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users 


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Nader Rahimizad
I have the same issue with two brand new Overo AirStorm Com's i got yesterday (Angstrom 2.6.39) running from the built-in flash...

Does anyone have a suggestion on what to try to remedy this issue?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

gumsticker
This post has NOT been accepted by the mailing list yet.
I have the problem too with my new Firestorms shipped mid of December when I use a SD image from 2011-03 and 2011-10. Seems all images from 2011-03 and newer using the libertas driver are affected.

I forgot if the issue appears on the 2010-10 NAND factory image, too... will check it.

However I will investigate further on this problem to find solutions to two problems:
- Load delay of the libertas_sdio driver (which causes the wlan0 interface to appear delayed)
- Disable the CRDA lookup, which hangs the boot procedure for ~5 min.

I also tried the new firmware  fw 9.70.20p0, which I got from http://dev.laptop.org/pub/firmware/libertas/, but no change.

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

gumsticker
This post has NOT been accepted by the mailing list yet.
In reply to this post by Nick Starzicki
Hello again,

The conf options from Nick Starzicki did the trick for me! Now the libertas_sdio (and wlan0) comes up immediately. I still have to enforce a connection by calling ifdown / ifup in a late init.d script, e.g. at time S98 (choose a non-duplicate), but now it seems to work everytime. Thanks alot!

Regards, Johannes

PS: It really seems to be an issue with the libertas_sdio module. When you have wlan0 up then "modprobe libertas_sdio" returns immediately. Directly after boot the same command returns delayed, not until the ADDRCONF messages appear.

Nick Starzicki wrote
1)
Creating the file : "/etc/modprobe.conf" with the content:
options libertas_sdio helper_name="sd8686_helper.bin"
options libertas_sdio fw_name="sd8686.bin"

This only works if I connect through serial as usual, and then type "boot",
and then it works automatically.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: WiFi problems

Petar Durdevic
This post has NOT been accepted by the mailing list yet.
I have tried all of these solutions and with the newest stable image at http://cumulus.gumstix.org/images/angstrom/factory/2011-08-30-1058/. And i am now running the preflashed nand image which is a 2.6.34 kernel and still i get the following result..

Ps. i am running a overo ironStorm mounted on a robovero.


------------------------------

OMAP36XX/37XX-GP ES2.1
Board revision: 1
Loading u-boot.bin from nand


U-Boot 2010.09 (Oct 20 2010 - 10:11:49)

OMAP36XX/37XX-GP ES2.1, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
Gumstix Overo board + LPDDR/NAND
I2C:   ready
DRAM:  512 MiB
NAND:  512 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Board revision: 1
Tranceiver detected on mmc2
No EEPROM on expansion board
Die ID #187800029ff80000016830c40a027016
Net:   No ethernet found.
Hit any key to stop autoboot:  0
No MMC card found
Booting from nand ...

NAND read: device 0 offset 0x280000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Angstrom/2.6.34/overo
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3160068 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.34 (steve@www.sakoman.com) (gcc version 4.3.3 (GCC) ) #1 Wed Oct 20 10:22:48 PD0
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Gumstix Overo
Memory policy: ECC disabled, Data cache writeback
OMAP3630 ES1.0 (l2cache iva sgx neon isp 192mhz_clk )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 12582912 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttyS2,115200n8 mpurate=500 vram=12M omapfb.mode=dvi:1024x768MR-16@602
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 256MB 256MB = 512MB total
Memory: 500816k/500816k available, 23472k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xe0800000 - 0xf8000000   ( 376 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .init : 0xc0008000 - 0xc00f2000   ( 936 kB)
      .text : 0xc00f2000 - 0xc05f6000   (5136 kB)
      .data : 0xc061a000 - 0xc0659400   ( 253 kB)
Hierarchical RCU implementation.
NR_IRQS:402
Clocking rate (Crystal/Core/MPU): 26.0/332/600 MHz
 (null): no physical address for uart#3, so skipping early_init...
Reprogramming SDRC clock to 332000000 Hz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 597.64 BogoMIPS (lpj=2334720)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
regulator: core version 0.5
NET: Registered protocol family 16
------------[ cut here ]------------
WARNING: at arch/arm/mach-omap2/serial.c:727 omap_serial_init_port+0x60/0x480()
(null): can't init uart3, no clocks available
Modules linked in:
[<c00f75c8>] (unwind_backtrace+0x0/0xec) from [<c0119b50>] (warn_slowpath_common+0x4c/0x80)
[<c0119b50>] (warn_slowpath_common+0x4c/0x80) from [<c0119bc0>] (warn_slowpath_fmt+0x28/0x38)
[<c0119bc0>] (warn_slowpath_fmt+0x28/0x38) from [<c000e98c>] (omap_serial_init_port+0x60/0x480)
[<c000e98c>] (omap_serial_init_port+0x60/0x480) from [<c000edd8>] (omap_serial_init+0x2c/0x3c)
[<c000edd8>] (omap_serial_init+0x2c/0x3c) from [<c0010680>] (overo_init+0x4c/0x4a0)
[<c0010680>] (overo_init+0x4c/0x4a0) from [<c000b7e4>] (customize_machine+0x1c/0x2c)
[<c000b7e4>] (customize_machine+0x1c/0x2c) from [<c00f234c>] (do_one_initcall+0x5c/0x1bc)
[<c00f234c>] (do_one_initcall+0x5c/0x1bc) from [<c0008404>] (kernel_init+0x94/0x148)
[<c0008404>] (kernel_init+0x94/0x148) from [<c00f38c0>] (kernel_thread_exit+0x0/0x8)
---[ end trace 1b75b31a2719ed1c ]---
Found NAND on CS0
hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
Switched to new clocking rate (Crystal/Core/MPU): 26.0/500/332 MHz
OMAP DMA hardware revision 5.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev4.0 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
regulator: VUSB1V5: 1500 mV normal standby
regulator: VUSB1V8: 1800 mV normal standby
regulator: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
regulator: VMMC1: 1850 <--> 3150 mV at 3000 mV normal standby
regulator: VDAC: 1800 mV normal standby
regulator: VDVI: 1800 mV normal standby
i2c_omap i2c_omap.3: bus 3 rev4.0 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.22.1.
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, musb-dma, host, debug=0
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.34 musb-hcd
usb usb1: SerialNumber: musb_hdrc
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb_hdrc musb_hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) (SUMMARY)  �© 2001-2006 Red Hat, Inc.
msgmni has been set to 978
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
OMAP DSI rev 1.0
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit)
cmdlinepart partition parsing not available
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000020000000 : "rootfs"
smsc911x: Driver version 2008-10-21.
smsc911x: Driver version 2008-10-21.
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OMAP-EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.34 ehci_hcd
usb usb2: SerialNumber: ehci-omap.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: OMAP UDC driver, version: 4 October 2004 (iso) (dma)
mice: PS/2 mouse device common for all mice
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
i2c /dev entries driver
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
twl4030_wdt twl4030_wdt: Failed to register misc device
twl4030_wdt: probe of twl4030_wdt failed with error -16
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
overo SoC init
asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
ALSA device list:
  #0: overo (twl4030)
oprofile: using arm/armv7
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
fbcvt: 1024x768@60: CVT Name - .786M3-R
Console: switching to colour frame buffer device 128x48
regulator_init_complete: incomplete constraints, leaving VDAC on
twl_rtc twl_rtc: setting system clock to 2010-10-20 12:10:14 UTC (1287576614)
Empty flash at 0x09a5016c ends at 0x09a50800
JFFS2 notice: (1) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 .
VFS: Mounted root (jffs2 filesystem) on device 31:4.
devtmpfs: mounted
Freeing init memory: 936K
INIT: version 2.86 booting
Please wait: booting...
Starting udev
udev: starting version 151
Remounting root file system...
Caching udev devnodes
Populating dev cachetar: dev/.udev/db: file changed as we read it
ads7846 spi1.0: touchscreen, irq 274
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
ads7846 spi1.0: no device detected, test read result was 0x00000FFF
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems

NET: Registered protocol family 10
ALSA: Restoring mixer settings...
Configuring network interfaces... ioctl[SIOCGIFFLAGS]: No such device
Could not get interface 'wlan0' flags
ioctl[SIOCSIWPMKSA]: No such device
ioctl[SIOCSIWMODE]: No such device
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: No such device
ioctl[SIOCGIFINDEX]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
JFFS2 notice: (528) check_node_data: wrong data CRC in data node at 0x1b2301c4: read 0x2c60b2a5, .
ioctl[SIOCSIWENCODE]: No such device
ioctl[SIOCSIWENCODEEXT]: No such device
ioctl[SIOCSIWENCODE]: No such device
Failed to disable WPA in the driver.
ioctl[SIOCSIWAP]: No such device
ioctl[SIOCGIFFLAGS]: No such device
Failed to bring up wlan0.
done.
Starting portmap daemon: portmap.
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
Turning echo off on /dev/ttyS1
INIT: Entering runlevel: 5
Starting system message bus: dbus.
Starting Hardware abstraction layer hald
Starting syslog-ng:.
Starting OpenBSD Secure Shell server: sshd
done.
/etc/rc5.d/S100myInit: line 3: Ifdown: not found
/etc/rc5.d/S100myInit: line 5: Ifup: not found
Starting advanced power management daemon: No APM support in kernel
(failed.)
Starting ntpd: done
Starting syslogd/klogd: done
[ ok ]rting Avahi mDNS/DNS-SD Daemon: avahi-daemon
Starting Bluetooth subsystem:
CSR build ID 0x0C-0x5C
Device setup complete
 ttyS1 bluetoothd hid2hci rfcomm.
Waiting for connection on channel 1
No SGX hardware, not starting PVR
Starting GPE display manager: gpe-dm

.-------.                                          
|       |                  .-.                      
|   |   |-----.-----.-----.| |   .----..-----.-----.
|       |     | __  |  ---'| '--.|  .-'|     |     |
|   |   |  |  |     |---  ||  --'|  |  |  '  | | | |
'---'---'--'--'--.  |-----''----''--'  '-----'-'-'-'
                -'  |
                '---'

The Angstrom Distribution overo ttyS2

Angstrom 2010.7-test-20100909 overo ttyS2

overo login: root
root@overo:~# iwconfig wlan0
wlan0     No such device

Greetings

Petar Durdevic
Loading...