From: Al V. <alv...@gm...> - 2010-09-21 03:07:23
|
Hi Paul, I just saw your post that those wi-fi timeout errors are no longer there with the latest pre-built images. On the older images, I noticed that wi-fi disconnects if I don't continuously ping. If you leave your gumstix on and do not do the constant pinging, does the wi-fi connection stay up/connected? |
From: Paul N. <pa...@id...> - 2010-09-21 05:00:28
|
> Hi Paul, I just saw your post that those wi-fi timeout errors are no > longer there with the latest pre-built images. On the older images, I > noticed that wi-fi disconnects if I don't continuously ping. If you > leave your gumstix on and do not do the constant pinging, does the wi-fi > connection stay up/connected? It seemed to, it definitely wasn't disconnecting all the time like before where the LED would just go off, then start blinking again. Can't test more at the moment as I`m testing ad-hoc mode now. Apart from the WiFi module being scorching hot, this seems to be working OK so far too. Paul Nolan, CEO Idruna Software Inc. |
From: J. L. <vwy...@gm...> - 2010-09-21 18:50:17
|
On Mon, Sep 20, 2010 at 10:00 PM, Paul Nolan <pa...@id...> wrote: > >> Hi Paul, I just saw your post that those wi-fi timeout errors are no >> longer there with the latest pre-built images. On the older images, I >> noticed that wi-fi disconnects if I don't continuously ping. If you >> leave your gumstix on and do not do the constant pinging, does the wi-fi >> connection stay up/connected? > > It seemed to, it definitely wasn't disconnecting all the time like > before where the LED would just go off, then start blinking again. Can't > test more at the moment as I`m testing ad-hoc mode now. Apart from the > WiFi module being scorching hot, this seems to be working OK so far too. > > Paul Nolan, CEO Idruna Software Inc. > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > No luck with the latest image for me same results with the on board wifi. The light blinks insanely fast, same time out errors and still wont even allow me to bring down the interface. All other wifi adapters work perfectly still, its just the on board wifi thats not useless. So it must not be the kernel since that was my only difference. So what is going on with the on board adapter? What is there left to look at to try and make it useable again. Doesnt even need to work perfect just needs to useable again. Should this be something that gets posted to the libertas-dev mailing list? |
From: Dr. J. <j...@hu...> - 2010-09-22 18:57:20
|
On Tue, Sep 21, 2010 at 11:50 AM, J. L. <vwy...@gm...> wrote: > No luck with the latest image for me same results with the on board > wifi. The light blinks insanely fast, same time out errors and still > wont even allow me to bring down the interface. All other wifi > adapters work perfectly still, its just the on board wifi thats not > useless. So it must not be the kernel since that was my only > difference. > > So what is going on with the on board adapter? What is there left to > look at to try and make it useable again. Doesnt even need to work > perfect just needs to useable again. Should this be something that > gets posted to the libertas-dev mailing list? In the Overo signals document, GPIO16 is listed as being connected to GPIO16_W2W_nRESET. Bouncing this pin might allow the wireless device to be reset without having to power cycle the whole module. Here's what I really want to know from Gumstix: does the Wi2wi device include any kind of mechanism to signal thermal problems? Is there a watchdog or debug UART exposed from the 88W8686 core in the Wi2wi package which could be used to differentiate a driver problem from a bona fide hardware problem? It pains me to think of a patch to the libertas driver that blindly bounces a platform GPIO every time something -- possibly caused by the driver itself -- goes wrong. It would also be nice to know which LDO and clocks from the TPS65950 are hooked up to the Wi2wi too. |
From: J. L. <vwy...@gm...> - 2010-09-28 07:44:17
|
On Wed, Sep 22, 2010 at 11:57 AM, Dr. Jesus <j...@hu...> wrote: > On Tue, Sep 21, 2010 at 11:50 AM, J. L. <vwy...@gm...> wrote: >> No luck with the latest image for me same results with the on board >> wifi. The light blinks insanely fast, same time out errors and still >> wont even allow me to bring down the interface. All other wifi >> adapters work perfectly still, its just the on board wifi thats not >> useless. So it must not be the kernel since that was my only >> difference. >> >> So what is going on with the on board adapter? What is there left to >> look at to try and make it useable again. Doesnt even need to work >> perfect just needs to useable again. Should this be something that >> gets posted to the libertas-dev mailing list? > > In the Overo signals document, GPIO16 is listed as being connected to > GPIO16_W2W_nRESET. Bouncing this pin might allow the wireless device > to be reset without having to power cycle the whole module. > > Here's what I really want to know from Gumstix: does the Wi2wi device > include any kind of mechanism to signal thermal problems? Is there a > watchdog or debug UART exposed from the 88W8686 core in the Wi2wi > package which could be used to differentiate a driver problem from a > bona fide hardware problem? It pains me to think of a patch to the > libertas driver that blindly bounces a platform GPIO every time > something -- possibly caused by the driver itself -- goes wrong. > > It would also be nice to know which LDO and clocks from the TPS65950 > are hooked up to the Wi2wi too. > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > Wish I knew where to find the info your asking but I have no clue. If you post specific things I can do on the overo to bring up any info you need I would happily do so just let me know. I am still seeing this issue where I can not get the on board wifi to work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as well as the gnome image that sakoman has but with added packages.. I am getting the following error below: libertas: requeueing command 0x0006 due to timeout (#1) libertas: Received result 0 to command 6 after 1 retries libertas: command 0x0006 timed out libertas: requeueing command 0x0006 due to timeout (#1) libertas: command 0x0006 timed out libertas: requeueing command 0x0006 due to timeout (#2) libertas: command 0x0006 timed out libertas: requeueing command 0x0006 due to timeout (#3) libertas: command 0x0006 timed out libertas: Excessive timeouts submitting command 0x0006 libertas: PREP_CMD: command 0x0006 failed: -110 libertas: SCAN_CMD failed libertas: command 0x0013 timed out libertas: requeueing command 0x0013 due to timeout (#1) libertas: command 0x0013 timed out libertas: requeueing command 0x0013 due to timeout (#2) libertas: command 0x0013 timed out libertas: requeueing command 0x0013 due to timeout (#3) libertas: command 0x0013 timed out libertas: Excessive timeouts submitting command 0x0013 libertas: PREP_CMD: command 0x0013 failed: -110 libertas: command 0x0006 timed out libertas: requeueing command 0x0006 due to timeout (#1) Same as I reported before... I do not have this issue when running the standard omap3 kernel. What is the difference between the two to make the on board wifi become unreliable? Stopping networkmanager makes no difference, when you run iwconfig it shows lo and wlan0 which is my plugged in USB adapter which works fine, udev seems to switch the on board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just hangs there like its trying to get info from the on board. Now when I boot it with no USB adapter I have the same issue with the on board but I see no udev action in the boot and when I run iwconfig I see lo and then just hangs there like it does mentioned above. Thanks for anymore help or info on this, I really need to get this kernel going for my project. JL I attached my defconfig and both recipes I built with the psp kernel in case something that gives some clue as to whats going on for me. |
From: Alex G. <al...@al...> - 2010-09-28 08:30:08
|
On 28/09/2010 5:44 PM, J. L. wrote: > On Wed, Sep 22, 2010 at 11:57 AM, Dr. Jesus<j...@hu...> wrote: >> On Tue, Sep 21, 2010 at 11:50 AM, J. L.<vwy...@gm...> wrote: >>> No luck with the latest image for me same results with the on board >>> wifi. The light blinks insanely fast, same time out errors and still >>> wont even allow me to bring down the interface. All other wifi >>> adapters work perfectly still, its just the on board wifi thats not >>> useless. So it must not be the kernel since that was my only >>> difference. >>> >>> So what is going on with the on board adapter? What is there left to >>> look at to try and make it useable again. Doesnt even need to work >>> perfect just needs to useable again. Should this be something that >>> gets posted to the libertas-dev mailing list? >> In the Overo signals document, GPIO16 is listed as being connected to >> GPIO16_W2W_nRESET. Bouncing this pin might allow the wireless device >> to be reset without having to power cycle the whole module. >> >> Here's what I really want to know from Gumstix: does the Wi2wi device >> include any kind of mechanism to signal thermal problems? Is there a >> watchdog or debug UART exposed from the 88W8686 core in the Wi2wi >> package which could be used to differentiate a driver problem from a >> bona fide hardware problem? It pains me to think of a patch to the >> libertas driver that blindly bounces a platform GPIO every time >> something -- possibly caused by the driver itself -- goes wrong. >> >> It would also be nice to know which LDO and clocks from the TPS65950 >> are hooked up to the Wi2wi too. >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > Wish I knew where to find the info your asking but I have no clue. If > you post specific things I can do on the overo to bring up any info > you need I would happily do so just let me know. > > I am still seeing this issue where I can not get the on board wifi to > work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as > well as the gnome image that sakoman has but with added packages.. I > am getting the following error below: > > libertas: requeueing command 0x0006 due to timeout (#1) > libertas: Received result 0 to command 6 after 1 retries > libertas: command 0x0006 timed out > libertas: requeueing command 0x0006 due to timeout (#1) > libertas: command 0x0006 timed out > libertas: requeueing command 0x0006 due to timeout (#2) > libertas: command 0x0006 timed out > libertas: requeueing command 0x0006 due to timeout (#3) > libertas: command 0x0006 timed out > libertas: Excessive timeouts submitting command 0x0006 > libertas: PREP_CMD: command 0x0006 failed: -110 > libertas: SCAN_CMD failed > libertas: command 0x0013 timed out > libertas: requeueing command 0x0013 due to timeout (#1) > libertas: command 0x0013 timed out > libertas: requeueing command 0x0013 due to timeout (#2) > libertas: command 0x0013 timed out > libertas: requeueing command 0x0013 due to timeout (#3) > libertas: command 0x0013 timed out > libertas: Excessive timeouts submitting command 0x0013 > libertas: PREP_CMD: command 0x0013 failed: -110 > libertas: command 0x0006 timed out > libertas: requeueing command 0x0006 due to timeout (#1) > > Same as I reported before... I do not have this issue when running the > standard omap3 kernel. What is the difference between the two to make > the on board wifi become unreliable? Stopping networkmanager makes no > difference, when you run iwconfig it shows lo and wlan0 which is my > plugged in USB adapter which works fine, udev seems to switch the on > board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just > hangs there like its trying to get info from the on board. Now when I > boot it with no USB adapter I have the same issue with the on board > but I see no udev action in the boot and when I run iwconfig I see lo > and then just hangs there like it does mentioned above. > > Thanks for anymore help or info on this, I really need to get this > kernel going for my project. > > JL > > I attached my defconfig and both recipes I built with the psp kernel > in case something that gives some clue as to whats going on for me. Problem is all the marvell docs are under a full NDA. I did have access to the docs for the wifi chipset for the orginal olpc but not any more. And we weren't allowed to keep copies. Took us nearly six months to get the access. Unfortunately more manufacturers are requiring full NDA which makes it hard to get the proper documentation. Alex -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology, Sydney. Before opening any attachments, please check them for viruses and defects. |
From: Dr. J. <j...@hu...> - 2010-09-28 14:19:50
|
On Tue, Sep 28, 2010 at 1:29 AM, Alex Gibson <al...@al...> wrote: > Problem is all the marvell docs are under a full NDA. > > I did have access to the docs for the wifi chipset for the orginal olpc > but not any more. > And we weren't allowed to keep copies. Took us nearly six months to get > the access. > > Unfortunately more manufacturers are requiring full NDA which makes it > hard to get the proper documentation. My question was for a Gumstix engineer, because (in theory) they're responsible for providing the first tier of support for wi2wi's products. I assume someone over there has access to the pinouts of the wireless chip because someone had to route the signals on the Overo COM when it was designed. They certainly know which LDO and clock pins from the power management chip are connected. |
From: Dr. J. <j...@hu...> - 2010-09-28 14:26:34
|
On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: > Wish I knew where to find the info your asking but I have no clue. If > you post specific things I can do on the overo to bring up any info > you need I would happily do so just let me know. > > I am still seeing this issue where I can not get the on board wifi to > work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as > well as the gnome image that sakoman has but with added packages.. I > am getting the following error below: > > [snip] > > Same as I reported before... I do not have this issue when running the > standard omap3 kernel. What is the difference between the two to make > the on board wifi become unreliable? Stopping networkmanager makes no > difference, when you run iwconfig it shows lo and wlan0 which is my > plugged in USB adapter which works fine, udev seems to switch the on > board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just > hangs there like its trying to get info from the on board. Now when I > boot it with no USB adapter I have the same issue with the on board > but I see no udev action in the boot and when I run iwconfig I see lo > and then just hangs there like it does mentioned above. > > Thanks for anymore help or info on this, I really need to get this > kernel going for my project. I'm not an expert, but it sounds like the problem is the PSP kernel :) When you say "USB adapter which works fine" and then "just hangs there like its trying to get info", are you talking about with the PSP kernel? Does it eventually work at all? When you say "do not have this issue when running the standard omap3 kernel," could you provide a boot log? I'm suspecting it's the firmware version or the driver version. |
From: J. L. <vwy...@gm...> - 2010-09-28 17:34:31
|
On Tue, Sep 28, 2010 at 7:26 AM, Dr. Jesus <j...@hu...> wrote: > On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: >> Wish I knew where to find the info your asking but I have no clue. If >> you post specific things I can do on the overo to bring up any info >> you need I would happily do so just let me know. >> >> I am still seeing this issue where I can not get the on board wifi to >> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >> well as the gnome image that sakoman has but with added packages.. I >> am getting the following error below: >> >> [snip] >> >> Same as I reported before... I do not have this issue when running the >> standard omap3 kernel. What is the difference between the two to make >> the on board wifi become unreliable? Stopping networkmanager makes no >> difference, when you run iwconfig it shows lo and wlan0 which is my >> plugged in USB adapter which works fine, udev seems to switch the on >> board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just >> hangs there like its trying to get info from the on board. Now when I >> boot it with no USB adapter I have the same issue with the on board >> but I see no udev action in the boot and when I run iwconfig I see lo >> and then just hangs there like it does mentioned above. >> >> Thanks for anymore help or info on this, I really need to get this >> kernel going for my project. > > I'm not an expert, but it sounds like the problem is the PSP kernel :) > > When you say "USB adapter which works fine" and then "just hangs there > like its trying to get info", are you talking about with the PSP > kernel? Does it eventually work at all? No what I was trying to get across there was that when I run the command iwconfig it shows the WIFI adapter I have plugged in to the hub and the lo, when it trys to show the interface that is the on boards it just hangs there like its trying to figure it out the adapters info, I honestly have never seen an adapter do this when you give iwconfig. > > When you say "do not have this issue when running the standard omap3 > kernel," could you provide a boot log? I'm suspecting it's the > firmware version or the driver version. I will post the boot logs very shortly I have to put the images back onto my cards with the psp kernel, though I do know they are pulling the same firmware version as I did verify that. they are both building the libertas-sd-firmware_9.70.7, if there is other things that I can post that you want to see please let me know as I will post everything I can for you. Also I posted the defconfig of the psp kernel in case there was something in that, that messed things up for me with the psp. > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: J. L. <vwy...@gm...> - 2010-09-28 18:46:45
|
On Tue, Sep 28, 2010 at 6:34 PM, J. L. <vwy...@gm...> wrote: > On Tue, Sep 28, 2010 at 7:26 AM, Dr. Jesus <j...@hu...> wrote: >> On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: >>> Wish I knew where to find the info your asking but I have no clue. If >>> you post specific things I can do on the overo to bring up any info >>> you need I would happily do so just let me know. >>> >>> I am still seeing this issue where I can not get the on board wifi to >>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>> well as the gnome image that sakoman has but with added packages.. I >>> am getting the following error below: >>> >>> [snip] >>> >>> Same as I reported before... I do not have this issue when running the >>> standard omap3 kernel. What is the difference between the two to make >>> the on board wifi become unreliable? Stopping networkmanager makes no >>> difference, when you run iwconfig it shows lo and wlan0 which is my >>> plugged in USB adapter which works fine, udev seems to switch the on >>> board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just >>> hangs there like its trying to get info from the on board. Now when I >>> boot it with no USB adapter I have the same issue with the on board >>> but I see no udev action in the boot and when I run iwconfig I see lo >>> and then just hangs there like it does mentioned above. >>> >>> Thanks for anymore help or info on this, I really need to get this >>> kernel going for my project. >> >> I'm not an expert, but it sounds like the problem is the PSP kernel :) >> >> When you say "USB adapter which works fine" and then "just hangs there >> like its trying to get info", are you talking about with the PSP >> kernel? Does it eventually work at all? > > No what I was trying to get across there was that when I run the > command iwconfig it shows the WIFI adapter I have plugged in to the > hub and the lo, when it trys to show the interface that is the on > boards it just hangs there like its trying to figure it out the > adapters info, I honestly have never seen an adapter do this when you > give iwconfig. > >> >> When you say "do not have this issue when running the standard omap3 >> kernel," could you provide a boot log? I'm suspecting it's the >> firmware version or the driver version. > > I will post the boot logs very shortly I have to put the images back > onto my cards with the psp kernel, though I do know they are pulling > the same firmware version as I did verify that. they are both building > the libertas-sd-firmware_9.70.7, if there is other things that I can > post that you want to see please let me know as I will post everything > I can for you. > > Also I posted the defconfig of the psp kernel in case there was > something in that, that messed things up for me with the psp. > > >> >> ------------------------------------------------------------------------------ >> Start uncovering the many advantages of virtual appliances >> and start using them to simplify application deployment and >> accelerate your shift to cloud computing. >> http://p.sf.net/sfu/novell-sfdev2dev >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > Here is the log for you, as well as the kernel log. Hope this helps some. This is the omap3-desktop-image running the psp kernel. Please let me know if there is more I can post |
From: J. L. <vwy...@gm...> - 2010-09-29 07:00:40
|
On Tue, Sep 28, 2010 at 11:46 AM, J. L. <vwy...@gm...> wrote: > On Tue, Sep 28, 2010 at 6:34 PM, J. L. <vwy...@gm...> wrote: >> On Tue, Sep 28, 2010 at 7:26 AM, Dr. Jesus <j...@hu...> wrote: >>> On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: >>>> Wish I knew where to find the info your asking but I have no clue. If >>>> you post specific things I can do on the overo to bring up any info >>>> you need I would happily do so just let me know. >>>> >>>> I am still seeing this issue where I can not get the on board wifi to >>>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>>> well as the gnome image that sakoman has but with added packages.. I >>>> am getting the following error below: >>>> >>>> [snip] >>>> >>>> Same as I reported before... I do not have this issue when running the >>>> standard omap3 kernel. What is the difference between the two to make >>>> the on board wifi become unreliable? Stopping networkmanager makes no >>>> difference, when you run iwconfig it shows lo and wlan0 which is my >>>> plugged in USB adapter which works fine, udev seems to switch the on >>>> board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just >>>> hangs there like its trying to get info from the on board. Now when I >>>> boot it with no USB adapter I have the same issue with the on board >>>> but I see no udev action in the boot and when I run iwconfig I see lo >>>> and then just hangs there like it does mentioned above. >>>> >>>> Thanks for anymore help or info on this, I really need to get this >>>> kernel going for my project. >>> >>> I'm not an expert, but it sounds like the problem is the PSP kernel :) >>> >>> When you say "USB adapter which works fine" and then "just hangs there >>> like its trying to get info", are you talking about with the PSP >>> kernel? Does it eventually work at all? >> >> No what I was trying to get across there was that when I run the >> command iwconfig it shows the WIFI adapter I have plugged in to the >> hub and the lo, when it trys to show the interface that is the on >> boards it just hangs there like its trying to figure it out the >> adapters info, I honestly have never seen an adapter do this when you >> give iwconfig. >> >>> >>> When you say "do not have this issue when running the standard omap3 >>> kernel," could you provide a boot log? I'm suspecting it's the >>> firmware version or the driver version. >> >> I will post the boot logs very shortly I have to put the images back >> onto my cards with the psp kernel, though I do know they are pulling >> the same firmware version as I did verify that. they are both building >> the libertas-sd-firmware_9.70.7, if there is other things that I can >> post that you want to see please let me know as I will post everything >> I can for you. >> >> Also I posted the defconfig of the psp kernel in case there was >> something in that, that messed things up for me with the psp. >> >> >>> >>> ------------------------------------------------------------------------------ >>> Start uncovering the many advantages of virtual appliances >>> and start using them to simplify application deployment and >>> accelerate your shift to cloud computing. >>> http://p.sf.net/sfu/novell-sfdev2dev >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>> >> > > Here is the log for you, as well as the kernel log. Hope this helps > some. This is the omap3-desktop-image running the psp kernel. > > Please let me know if there is more I can post > Though it is working with the standard kernel I just noticed that its showing up as what my USB wifi adapter is and not the on board. Though it appears to be working? Seems weird to me. |
From: J. L. <vwy...@gm...> - 2010-09-30 06:06:46
|
On Wed, Sep 29, 2010 at 12:00 AM, J. L. <vwy...@gm...> wrote: > On Tue, Sep 28, 2010 at 11:46 AM, J. L. <vwy...@gm...> wrote: >> On Tue, Sep 28, 2010 at 6:34 PM, J. L. <vwy...@gm...> wrote: >>> On Tue, Sep 28, 2010 at 7:26 AM, Dr. Jesus <j...@hu...> wrote: >>>> On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: >>>>> Wish I knew where to find the info your asking but I have no clue. If >>>>> you post specific things I can do on the overo to bring up any info >>>>> you need I would happily do so just let me know. >>>>> >>>>> I am still seeing this issue where I can not get the on board wifi to >>>>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>>>> well as the gnome image that sakoman has but with added packages.. I >>>>> am getting the following error below: >>>>> >>>>> [snip] >>>>> >>>>> Same as I reported before... I do not have this issue when running the >>>>> standard omap3 kernel. What is the difference between the two to make >>>>> the on board wifi become unreliable? Stopping networkmanager makes no >>>>> difference, when you run iwconfig it shows lo and wlan0 which is my >>>>> plugged in USB adapter which works fine, udev seems to switch the on >>>>> board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just >>>>> hangs there like its trying to get info from the on board. Now when I >>>>> boot it with no USB adapter I have the same issue with the on board >>>>> but I see no udev action in the boot and when I run iwconfig I see lo >>>>> and then just hangs there like it does mentioned above. >>>>> >>>>> Thanks for anymore help or info on this, I really need to get this >>>>> kernel going for my project. >>>> >>>> I'm not an expert, but it sounds like the problem is the PSP kernel :) >>>> >>>> When you say "USB adapter which works fine" and then "just hangs there >>>> like its trying to get info", are you talking about with the PSP >>>> kernel? Does it eventually work at all? >>> >>> No what I was trying to get across there was that when I run the >>> command iwconfig it shows the WIFI adapter I have plugged in to the >>> hub and the lo, when it trys to show the interface that is the on >>> boards it just hangs there like its trying to figure it out the >>> adapters info, I honestly have never seen an adapter do this when you >>> give iwconfig. >>> >>>> >>>> When you say "do not have this issue when running the standard omap3 >>>> kernel," could you provide a boot log? I'm suspecting it's the >>>> firmware version or the driver version. >>> >>> I will post the boot logs very shortly I have to put the images back >>> onto my cards with the psp kernel, though I do know they are pulling >>> the same firmware version as I did verify that. they are both building >>> the libertas-sd-firmware_9.70.7, if there is other things that I can >>> post that you want to see please let me know as I will post everything >>> I can for you. >>> >>> Also I posted the defconfig of the psp kernel in case there was >>> something in that, that messed things up for me with the psp. >>> >>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Start uncovering the many advantages of virtual appliances >>>> and start using them to simplify application deployment and >>>> accelerate your shift to cloud computing. >>>> http://p.sf.net/sfu/novell-sfdev2dev >>>> _______________________________________________ >>>> gumstix-users mailing list >>>> gum...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>> >>> >> >> Here is the log for you, as well as the kernel log. Hope this helps >> some. This is the omap3-desktop-image running the psp kernel. >> >> Please let me know if there is more I can post >> > > Though it is working with the standard kernel I just noticed that its > showing up as what my USB wifi adapter is and not the on board. Though > it appears to be working? Seems weird to me. > Here is some of the watchdog errors that I get when I am able to get the on board wifi working.. wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready cfg80211: Calling CRDA for country: US wlan0: no IPv6 routers present ------------[ cut here ]------------ WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x140/0x220() NETDEV WATCHDOG: wlan1 (libertas_sdio): transmit queue 0 timed out Modules linked in: ipv6 libertas_sdio libertas lib80211 rtl8187 option eeprom_93cx6 usbserial ads7846 [<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 [<c03de5a0>] (dev_watchdog+0x140/0x220) [<c03de5a0>] (dev_watchdog+0x140/0x220) from [<c01228b4>] (run_timer_softirq+0x188/0x204) [<c01228b4>] (run_timer_softirq+0x188/0x204) from [<c011ea98>] (__do_softirq+0x78/0x100) [<c011ea98>] (__do_softirq+0x78/0x100) from [<c011eb60>] (irq_exit+0x40/0x94) [<c011eb60>] (irq_exit+0x40/0x94) from [<c00f2078>] (asm_do_IRQ+0x78/0x98) [<c00f2078>] (asm_do_IRQ+0x78/0x98) from [<c00f2ab4>] (__irq_svc+0x34/0x80) Exception stack(0xc061bf78 to 0xc061bfc0) bf60: 00000000 40000013 bf80: 40000013 00000000 c061a000 c061df54 c061dd88 c065968c 8002a5c0 411fc083 bfa0: 0000001f 00000000 c062bca8 c061bfc0 c0101e60 c00f3ea4 60000013 ffffffff [<c00f2ab4>] (__irq_svc+0x34/0x80) from [<c00f3ea4>] (cpu_idle+0x78/0xa8) [<c00f3ea4>] (cpu_idle+0x78/0xa8) from [<c000898c>] (start_kernel+0x254/0x2b8) [<c000898c>] (start_kernel+0x254/0x2b8) from [<80008034>] (0x80008034) ---[ end trace e368611c371552a4 ]--- libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout libertas: tx watch dog timeout |
From: J. L. <vwy...@gm...> - 2010-10-02 05:01:47
|
On Wed, Sep 29, 2010 at 11:06 PM, J. L. <vwy...@gm...> wrote: > On Wed, Sep 29, 2010 at 12:00 AM, J. L. <vwy...@gm...> wrote: >> On Tue, Sep 28, 2010 at 11:46 AM, J. L. <vwy...@gm...> wrote: >>> On Tue, Sep 28, 2010 at 6:34 PM, J. L. <vwy...@gm...> wrote: >>>> On Tue, Sep 28, 2010 at 7:26 AM, Dr. Jesus <j...@hu...> wrote: >>>>> On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: >>>>>> Wish I knew where to find the info your asking but I have no clue. If >>>>>> you post specific things I can do on the overo to bring up any info >>>>>> you need I would happily do so just let me know. >>>>>> >>>>>> I am still seeing this issue where I can not get the on board wifi to >>>>>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>>>>> well as the gnome image that sakoman has but with added packages.. I >>>>>> am getting the following error below: >>>>>> >>>>>> [snip] >>>>>> >>>>>> Same as I reported before... I do not have this issue when running the >>>>>> standard omap3 kernel. What is the difference between the two to make >>>>>> the on board wifi become unreliable? Stopping networkmanager makes no >>>>>> difference, when you run iwconfig it shows lo and wlan0 which is my >>>>>> plugged in USB adapter which works fine, udev seems to switch the on >>>>>> board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just >>>>>> hangs there like its trying to get info from the on board. Now when I >>>>>> boot it with no USB adapter I have the same issue with the on board >>>>>> but I see no udev action in the boot and when I run iwconfig I see lo >>>>>> and then just hangs there like it does mentioned above. >>>>>> >>>>>> Thanks for anymore help or info on this, I really need to get this >>>>>> kernel going for my project. >>>>> >>>>> I'm not an expert, but it sounds like the problem is the PSP kernel :) >>>>> >>>>> When you say "USB adapter which works fine" and then "just hangs there >>>>> like its trying to get info", are you talking about with the PSP >>>>> kernel? Does it eventually work at all? >>>> >>>> No what I was trying to get across there was that when I run the >>>> command iwconfig it shows the WIFI adapter I have plugged in to the >>>> hub and the lo, when it trys to show the interface that is the on >>>> boards it just hangs there like its trying to figure it out the >>>> adapters info, I honestly have never seen an adapter do this when you >>>> give iwconfig. >>>> >>>>> >>>>> When you say "do not have this issue when running the standard omap3 >>>>> kernel," could you provide a boot log? I'm suspecting it's the >>>>> firmware version or the driver version. >>>> >>>> I will post the boot logs very shortly I have to put the images back >>>> onto my cards with the psp kernel, though I do know they are pulling >>>> the same firmware version as I did verify that. they are both building >>>> the libertas-sd-firmware_9.70.7, if there is other things that I can >>>> post that you want to see please let me know as I will post everything >>>> I can for you. >>>> >>>> Also I posted the defconfig of the psp kernel in case there was >>>> something in that, that messed things up for me with the psp. >>>> >>>> >>>>> >>>>> ------------------------------------------------------------------------------ >>>>> Start uncovering the many advantages of virtual appliances >>>>> and start using them to simplify application deployment and >>>>> accelerate your shift to cloud computing. >>>>> http://p.sf.net/sfu/novell-sfdev2dev >>>>> _______________________________________________ >>>>> gumstix-users mailing list >>>>> gum...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>> >>>> >>> >>> Here is the log for you, as well as the kernel log. Hope this helps >>> some. This is the omap3-desktop-image running the psp kernel. >>> >>> Please let me know if there is more I can post >>> >> >> Though it is working with the standard kernel I just noticed that its >> showing up as what my USB wifi adapter is and not the on board. Though >> it appears to be working? Seems weird to me. >> > > Here is some of the watchdog errors that I get when I am able to get > the on board wifi working.. > > wlan0: associated > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > cfg80211: Calling CRDA for country: US > wlan0: no IPv6 routers present > ------------[ cut here ]------------ > WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x140/0x220() > NETDEV WATCHDOG: wlan1 (libertas_sdio): transmit queue 0 timed out > Modules linked in: ipv6 libertas_sdio libertas lib80211 rtl8187 option > eeprom_93cx6 usbserial ads7846 > [<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 [<c03de5a0>] > (dev_watchdog+0x140/0x220) > [<c03de5a0>] (dev_watchdog+0x140/0x220) from [<c01228b4>] > (run_timer_softirq+0x188/0x204) > [<c01228b4>] (run_timer_softirq+0x188/0x204) from [<c011ea98>] > (__do_softirq+0x78/0x100) > [<c011ea98>] (__do_softirq+0x78/0x100) from [<c011eb60>] (irq_exit+0x40/0x94) > [<c011eb60>] (irq_exit+0x40/0x94) from [<c00f2078>] (asm_do_IRQ+0x78/0x98) > [<c00f2078>] (asm_do_IRQ+0x78/0x98) from [<c00f2ab4>] (__irq_svc+0x34/0x80) > Exception stack(0xc061bf78 to 0xc061bfc0) > bf60: 00000000 40000013 > bf80: 40000013 00000000 c061a000 c061df54 c061dd88 c065968c 8002a5c0 411fc083 > bfa0: 0000001f 00000000 c062bca8 c061bfc0 c0101e60 c00f3ea4 60000013 ffffffff > [<c00f2ab4>] (__irq_svc+0x34/0x80) from [<c00f3ea4>] (cpu_idle+0x78/0xa8) > [<c00f3ea4>] (cpu_idle+0x78/0xa8) from [<c000898c>] (start_kernel+0x254/0x2b8) > [<c000898c>] (start_kernel+0x254/0x2b8) from [<80008034>] (0x80008034) > ---[ end trace e368611c371552a4 ]--- > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > libertas: tx watch dog timeout > Here are the errors from a fresh first boot with kernel omap3 .34 lib80211: common routines for IEEE802.11 drivers libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin libertas: 00:50:43:02:fe:01, fw 9.70.7p0, cap 0x0000030b libertas: wlan0: Marvell WLAN 802.11 adapter udevd[78]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/60-gpsd.rules:43 udevd[78]: SYSFS{}= will be removed in a future udev version, please use ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in /etc/udev/rules.d/60-gpsd.rules:43 Remounting root file system... |
From: J. L. <vwy...@gm...> - 2010-10-02 06:59:06
|
On Fri, Oct 1, 2010 at 10:01 PM, J. L. <vwy...@gm...> wrote: > On Wed, Sep 29, 2010 at 11:06 PM, J. L. <vwy...@gm...> wrote: >> On Wed, Sep 29, 2010 at 12:00 AM, J. L. <vwy...@gm...> wrote: >>> On Tue, Sep 28, 2010 at 11:46 AM, J. L. <vwy...@gm...> wrote: >>>> On Tue, Sep 28, 2010 at 6:34 PM, J. L. <vwy...@gm...> wrote: >>>>> On Tue, Sep 28, 2010 at 7:26 AM, Dr. Jesus <j...@hu...> wrote: >>>>>> On Tue, Sep 28, 2010 at 12:44 AM, J. L. <vwy...@gm...> wrote: >>>>>>> Wish I knew where to find the info your asking but I have no clue. If >>>>>>> you post specific things I can do on the overo to bring up any info >>>>>>> you need I would happily do so just let me know. >>>>>>> >>>>>>> I am still seeing this issue where I can not get the on board wifi to >>>>>>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>>>>>> well as the gnome image that sakoman has but with added packages.. I >>>>>>> am getting the following error below: >>>>>>> >>>>>>> [snip] >>>>>>> >>>>>>> Same as I reported before... I do not have this issue when running the >>>>>>> standard omap3 kernel. What is the difference between the two to make >>>>>>> the on board wifi become unreliable? Stopping networkmanager makes no >>>>>>> difference, when you run iwconfig it shows lo and wlan0 which is my >>>>>>> plugged in USB adapter which works fine, udev seems to switch the on >>>>>>> board my wlan0 to wlan1 and the USB from wlan1 to wlan0, and the just >>>>>>> hangs there like its trying to get info from the on board. Now when I >>>>>>> boot it with no USB adapter I have the same issue with the on board >>>>>>> but I see no udev action in the boot and when I run iwconfig I see lo >>>>>>> and then just hangs there like it does mentioned above. >>>>>>> >>>>>>> Thanks for anymore help or info on this, I really need to get this >>>>>>> kernel going for my project. >>>>>> >>>>>> I'm not an expert, but it sounds like the problem is the PSP kernel :) >>>>>> >>>>>> When you say "USB adapter which works fine" and then "just hangs there >>>>>> like its trying to get info", are you talking about with the PSP >>>>>> kernel? Does it eventually work at all? >>>>> >>>>> No what I was trying to get across there was that when I run the >>>>> command iwconfig it shows the WIFI adapter I have plugged in to the >>>>> hub and the lo, when it trys to show the interface that is the on >>>>> boards it just hangs there like its trying to figure it out the >>>>> adapters info, I honestly have never seen an adapter do this when you >>>>> give iwconfig. >>>>> >>>>>> >>>>>> When you say "do not have this issue when running the standard omap3 >>>>>> kernel," could you provide a boot log? I'm suspecting it's the >>>>>> firmware version or the driver version. >>>>> >>>>> I will post the boot logs very shortly I have to put the images back >>>>> onto my cards with the psp kernel, though I do know they are pulling >>>>> the same firmware version as I did verify that. they are both building >>>>> the libertas-sd-firmware_9.70.7, if there is other things that I can >>>>> post that you want to see please let me know as I will post everything >>>>> I can for you. >>>>> >>>>> Also I posted the defconfig of the psp kernel in case there was >>>>> something in that, that messed things up for me with the psp. >>>>> >>>>> >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Start uncovering the many advantages of virtual appliances >>>>>> and start using them to simplify application deployment and >>>>>> accelerate your shift to cloud computing. >>>>>> http://p.sf.net/sfu/novell-sfdev2dev >>>>>> _______________________________________________ >>>>>> gumstix-users mailing list >>>>>> gum...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >>>>>> >>>>> >>>> >>>> Here is the log for you, as well as the kernel log. Hope this helps >>>> some. This is the omap3-desktop-image running the psp kernel. >>>> >>>> Please let me know if there is more I can post >>>> >>> >>> Though it is working with the standard kernel I just noticed that its >>> showing up as what my USB wifi adapter is and not the on board. Though >>> it appears to be working? Seems weird to me. >>> >> >> Here is some of the watchdog errors that I get when I am able to get >> the on board wifi working.. >> >> wlan0: associated >> ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready >> cfg80211: Calling CRDA for country: US >> wlan0: no IPv6 routers present >> ------------[ cut here ]------------ >> WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x140/0x220() >> NETDEV WATCHDOG: wlan1 (libertas_sdio): transmit queue 0 timed out >> Modules linked in: ipv6 libertas_sdio libertas lib80211 rtl8187 option >> eeprom_93cx6 usbserial ads7846 >> [<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 [<c03de5a0>] >> (dev_watchdog+0x140/0x220) >> [<c03de5a0>] (dev_watchdog+0x140/0x220) from [<c01228b4>] >> (run_timer_softirq+0x188/0x204) >> [<c01228b4>] (run_timer_softirq+0x188/0x204) from [<c011ea98>] >> (__do_softirq+0x78/0x100) >> [<c011ea98>] (__do_softirq+0x78/0x100) from [<c011eb60>] (irq_exit+0x40/0x94) >> [<c011eb60>] (irq_exit+0x40/0x94) from [<c00f2078>] (asm_do_IRQ+0x78/0x98) >> [<c00f2078>] (asm_do_IRQ+0x78/0x98) from [<c00f2ab4>] (__irq_svc+0x34/0x80) >> Exception stack(0xc061bf78 to 0xc061bfc0) >> bf60: 00000000 40000013 >> bf80: 40000013 00000000 c061a000 c061df54 c061dd88 c065968c 8002a5c0 411fc083 >> bfa0: 0000001f 00000000 c062bca8 c061bfc0 c0101e60 c00f3ea4 60000013 ffffffff >> [<c00f2ab4>] (__irq_svc+0x34/0x80) from [<c00f3ea4>] (cpu_idle+0x78/0xa8) >> [<c00f3ea4>] (cpu_idle+0x78/0xa8) from [<c000898c>] (start_kernel+0x254/0x2b8) >> [<c000898c>] (start_kernel+0x254/0x2b8) from [<80008034>] (0x80008034) >> ---[ end trace e368611c371552a4 ]--- >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> libertas: tx watch dog timeout >> > > Here are the errors from a fresh first boot with kernel omap3 .34 > > lib80211: common routines for IEEE802.11 drivers > libertas_sdio: Libertas SDIO driver > libertas_sdio: Copyright Pierre Ossman > libertas_sdio mmc1:0001:1: firmware: requesting sd8686_helper.bin > libertas_sdio mmc1:0001:1: firmware: requesting sd8686.bin > libertas: 00:50:43:02:fe:01, fw 9.70.7p0, cap 0x0000030b > libertas: wlan0: Marvell WLAN 802.11 adapter > udevd[78]: SYSFS{}= will be removed in a future udev version, please > use ATTR{}= to match the event device, or ATTRS{}= to match a parent > device, in /etc/udev/rules.d/60-gpsd.rules:43 > > udevd[78]: SYSFS{}= will be removed in a future udev version, please > use ATTR{}= to match the event device, or ATTRS{}= to match a parent > device, in /etc/udev/rules.d/60-gpsd.rules:43 > > Remounting root file system... > Only able to get 2.3MBs and here is still the watchdog issues: ------------[ cut here ]------------ WARNING: at net/sched/sch_generic.c:256 dev_watchdog+0x140/0x220() NETDEV WATCHDOG: wlan0 (libertas_sdio): transmit queue 0 timed out Modules linked in: ipv6 libertas_sdio libertas lib80211 option ftdi_sio usbserial ads7846 [<c00f75c8>] (unwind_backtrace+0x0/0xec) from [<c011a048>] (warn_slowpath_common+0x4c/0x80) [<c011a048>] (warn_slowpath_common+0x4c/0x80) from [<c011a0b8>] (warn_slowpath_fmt+0x28/0x38) [<c011a0b8>] (warn_slowpath_fmt+0x28/0x38) from [<c03d8760>] (dev_watchdog+0x140/0x220) [<c03d8760>] (dev_watchdog+0x140/0x220) from [<c0122dac>] (run_timer_softirq+0x188/0x204) [<c0122dac>] (run_timer_softirq+0x188/0x204) from [<c011ef90>] (__do_softirq+0x78/0x100) [<c011ef90>] (__do_softirq+0x78/0x100) from [<c011f058>] (irq_exit+0x40/0x94) [<c011f058>] (irq_exit+0x40/0x94) from [<c00f2078>] (asm_do_IRQ+0x78/0x98) [<c00f2078>] (asm_do_IRQ+0x78/0x98) from [<c00f2ab4>] (__irq_svc+0x34/0x80) Exception stack(0xc0611f30 to 0xc0611f78) 1f20: 03a3c480 00000000 03a3c480 00000000 1f40: 00000003 00000003 c0650254 c0650334 c0650338 411fc083 0000001f 00000000 1f60: 3b9ac9ff c0611f78 c01027b4 c01027c0 60000053 ffffffff [<c00f2ab4>] (__irq_svc+0x34/0x80) from [<c01027c0>] (omap3_enter_idle+0x108/0x140) [<c01027c0>] (omap3_enter_idle+0x108/0x140) from [<c0367f18>] (cpuidle_idle_call+0xa0/0x100) [<c0367f18>] (cpuidle_idle_call+0xa0/0x100) from [<c00f3e84>] (cpu_idle+0x58/0xa8) [<c00f3e84>] (cpu_idle+0x58/0xa8) from [<c000898c>] (start_kernel+0x254/0x2b8) [<c000898c>] (start_kernel+0x254/0x2b8) from [<80008034>] (0x80008034) ---[ end trace 752aa605aac2c5df ]--- libertas: tx watch dog timeout Hope maybe some of this will help someone figure something out..... Still have expected performance with any other plugged in USB WIFI adapter I have tried so far and no issues I have run across. |
From: Steve d. <st...@co...> - 2010-10-11 18:21:38
|
>>>>>>>> I am still seeing this issue where I can not get the on board wifi to >>>>>>>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>>>>>>> well as the gnome image that sakoman has but with added packages.. I >>>>>>>> am getting the following error below: I highly recommend you try with a much more current kernel, even go as far as building from the wireless-testing head kernel. Lots of changes between .32 and now on libertas. - Steve |
From: J. L. <vwy...@gm...> - 2010-10-11 18:59:11
|
On Mon, Oct 11, 2010 at 11:19 AM, Steve deRosier <st...@co...> wrote: >>>>>>>>> I am still seeing this issue where I can not get the on board wifi to >>>>>>>>> work with the omap3-desktop-image running the linux-omap-psp_2.6.32 as >>>>>>>>> well as the gnome image that sakoman has but with added packages.. I >>>>>>>>> am getting the following error below: > > I highly recommend you try with a much more current kernel, even go as > far as building from the wireless-testing head kernel. Lots of > changes between .32 and now on libertas. > > - Steve > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today. > http://p.sf.net/sfu/beautyoftheweb > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > I have been trying with the omap3-.34 the last few days with same results and more frequent time outs .. Its not the kernel I dont think. JL |