Re: please notice if any of your wsods gone with latest shr kernel upgrade [Was: QtMoko v25 - experimental with 2.6.34 kernel ]
On Thu, Aug 26, 2010 at 10:22:01PM +0200, Petr Vanek wrote: It was added to feed 2days ago together with 2.6.32.17-2.6.32.20 upgrade so if you have: SHR r...@gojama / $ opkg info kernel Package: kernel Version: 2.6.32.20-oe3.3+gitr6+a9254be10ac2294ea20165a87c09ea6afcf66d94-r0.5 or newer then you have this patch too FYI, here 2.6.32.20 was fetched but /boot/uImage symlink wasn't automatically updated from 2.6.32.16, not sure whether bug or intention... booting from uSD right? check cat /usr/lib/opkg/alternatives/uImage link to latest is managed by u-a and ie for mixed alternatives from 2.6.32 and 2.6.34 it doesn't work, because it's using last version part as priority on my install 2.6.32.21 wins (will be in feed today) even with 2.6.34.6 available SHR r...@gojama ~ $ cat /usr/lib/opkg/alternatives/uImage /boot/uImage uImage-2.6.32.17 17 uImage-2.6.32.20 20 uImage-2.6.32.21 21 uImage-2.6.34.5 5 uImage-2.6.34.6 6 i have switched now and rotate causes no wsod, which would typically appear... great! btw. how do you rotate the touchscreen (xrands rotates the display, but i cannot see xsetwacom to rotate the input...), thank you. Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
please notice if any of your wsods gone with latest shr kernel upgrade [Was: QtMoko v25 - experimental with 2.6.34 kernel ]
Hi, list btw, i would be very interesting to hear if after this patch (which came with latest kernel upgrade in shr) any kind of wsods disappeared on 4-4-4 (default) glamo settings too. please write down. thanks, Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: please notice if any of your wsods gone with latest shr kernel upgrade [Was: QtMoko v25 - experimental with 2.6.34 kernel ]
Is it in the feed right now ? I don't see anything 2010/8/26 Gennady Kupava g...@bsdmn.com Hi, list btw, i would be very interesting to hear if after this patch (which came with latest kernel upgrade in shr) any kind of wsods disappeared on 4-4-4 (default) glamo settings too. please write down. thanks, Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: please notice if any of your wsods gone with latest shr kernel upgrade [Was: QtMoko v25 - experimental with 2.6.34 kernel ]
Ah, i am a bit unclear. I am about 'patch which fixes WSOD for 2-4-2 timing', which were added few days ago. Please, write down here or somewhere (2 more reports will be enought of course) if it fixes some WSODs for you on usual timings too. I expected this, but were unable to check this. Gennady. В Чтв, 26/08/2010 в 13:20 +0200, Sylvain Paré пишет: Is it in the feed right now ? I don't see anything 2010/8/26 Gennady Kupava g...@bsdmn.com Hi, list btw, i would be very interesting to hear if after this patch (which came with latest kernel upgrade in shr) any kind of wsods disappeared on 4-4-4 (default) glamo settings too. please write down. thanks, Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: please notice if any of your wsods gone with latest shr kernel upgrade [Was: QtMoko v25 - experimental with 2.6.34 kernel ]
On Thu, Aug 26, 2010 at 02:25:45PM +0400, Gennady Kupava wrote: Ah, i am a bit unclear. I am about 'patch which fixes WSOD for 2-4-2 timing', which were added few days ago. It was added to feed 2days ago together with 2.6.32.17-2.6.32.20 upgrade so if you have: SHR r...@gojama / $ opkg info kernel Package: kernel Version: 2.6.32.20-oe3.3+gitr6+a9254be10ac2294ea20165a87c09ea6afcf66d94-r0.5 or newer then you have this patch too -- Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: please notice if any of your wsods gone with latest shr kernel upgrade [Was: QtMoko v25 - experimental with 2.6.34 kernel ]
It was added to feed 2days ago together with 2.6.32.17-2.6.32.20 upgrade so if you have: SHR r...@gojama / $ opkg info kernel Package: kernel Version: 2.6.32.20-oe3.3+gitr6+a9254be10ac2294ea20165a87c09ea6afcf66d94-r0.5 or newer then you have this patch too FYI, here 2.6.32.20 was fetched but /boot/uImage symlink wasn't automatically updated from 2.6.32.16, not sure whether bug or intention... i have switched now and rotate causes no wsod, which would typically appear... great! btw. how do you rotate the touchscreen (xrands rotates the display, but i cannot see xsetwacom to rotate the input...), thank you. Petr ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
mdbus2 to check GSM firmware version in latest SHR-u
Hi, in preparation for checking out android I wanted to see what my GSM firmware version is as described on this page: http://wiki.openmoko.org/wiki/GSM/Flashing Unfortunately I'm not familiar with mdbus2 and FSO and don't know what to do about this: r...@om-gta02 ~ # mdbus2 -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Device.GetInfo [ERR]: No method org.freesmartphone.GSM.Device.GetInfo found at /org/freesmartphone/GSM/Device for org.freesmartphone.ogsmd I guess it got restructured. But how do I find the new GetInfo equivalent? Thanks Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: mdbus2 to check GSM firmware version in latest SHR-u
Am Sonntag, den 09.05.2010, 19:46 +0200 schrieb Jan Girlich:
Hi,
in preparation for checking out android I wanted to see what my GSM
firmware version is as described on this page:
http://wiki.openmoko.org/wiki/GSM/Flashing
Unfortunately I'm not familiar with mdbus2 and FSO and don't know what
to do about this:
r...@om-gta02 ~ # mdbus2 -s
org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device
org.freesmartphone.GSM.Device.GetInfo
[ERR]: No method org.freesmartphone.GSM.Device.GetInfo found
at /org/freesmartphone/GSM/Device for org.freesmartphone.ogsmd
I guess it got restructured. But how do I find the new GetInfo
equivalent?
mic...@saphir:~$ mdbus2 -s
org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device
org.freesmartphone.Info.GetInfo
( { revision: GSM:
gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko11, imei:
354651011601806, model: Neo1973 GTA01/GTA02 Embedded GSM Modem,
manufacturer: FIC/OpenMoko } )
Hint: mdbus2 -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device
would have told you ;)
--
:M:
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: mdbus2 to check GSM firmware version in latest SHR-u
Am Sonntag, den 09.05.2010, 20:04 +0200 schrieb Michael 'Mickey' Lauer: mic...@saphir:~$ mdbus2 -s org.freesmartphone.ogsmd /org/freesmartphone/GSM/Device org.freesmartphone.Info.GetInfo Works fine, thanks! Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
On Wed, May 5, 2010 at 7:20 AM, Lars Hennig n...@el-hennig.de wrote: I am really looking forward to the upgrade of neo theme to illume2 ;-) And how you close an application in illume2?;-) For me the top shelf does not slide down anymore (dunno, what should be the method to close the applications) Best regards, Laszlo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
And how you close an application in illume2?;-) For me the top shelf does not slide down anymore (dunno, what should be the method to close the applications) For me it does not automatically, but as workaraound you can start shr_elm_softkey from the terminal and then it works fine. -- n...@el-hennig.de Lubarsky's Law of Cybernetic Entomology: There's always one more bug. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
Am Mittwoch, den 05.05.2010, 01:26 +0200 schrieb Bernd Prünster: Jan Girlich wrote: Wooha, after playing around too much with my installation today I broke it and reflashed my Freerunner with the lastest SHR unstable. And am stuck! Where do you guys keep up to date regarding the changes in the SHR apps? i don't... since the switch to fsogsmd+fsotld+etc... my neo is in a vegetative state I installed shr-theme-neo again and noticed that the background and symbol font on the starter are black and thus the app names are unreadable. (i'm the author of the neo theme ...at least illume and elm) i dont bother with illume2 for now ... i'm waiting till these issues are ironed out then i'll adapt the theme... what good does eye candy do when underlaying stuff is broken? :-P because of the current situation dont expect any theme updates until the current regressions are ironed out. you might want to try to switch to illume1 - window management and neo theme works there (go to illume settings - [i forgot the category] - profile and select illume-shr) I changed the theme under Look - Themes to illume-shr and go with this until the neo theme is fixed again. Thanks Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
Am Mittwoch, den 05.05.2010, 08:36 +0200 schrieb Laszlo KREKACS: On Wed, May 5, 2010 at 7:20 AM, Lars Hennig n...@el-hennig.de wrote: I am really looking forward to the upgrade of neo theme to illume2 ;-) And how you close an application in illume2?;-) For me the top shelf does not slide down anymore (dunno, what should be the method to close the applications) That's the same problem I tried to describe in my original post as well. I can't close any app anymore. Like the messages app. Open it once, not able to close, open something else so messages moves away from your current screen, then you don't have any means of switching to the currently running messages app anymore and can't open a new one because you can't start the app twice. Stuck. ssh into the phone/reboot. Cheers Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
Am Mittwoch, den 05.05.2010, 09:39 +0200 schrieb n...@el-hennig.de: And how you close an application in illume2?;-) For me the top shelf does not slide down anymore (dunno, what should be the method to close the applications) For me it does not automatically, but as workaraound you can start shr_elm_softkey from the terminal and then it works fine. Thanks! Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
For me it does not automatically, but as workaraound you can start shr_elm_softkey from the terminal and then it works fine. I found an even better way to workaraounf this problem automatically: I created a wrapper /usr/bin/shr_elm_softkey.sh that is called from /etc/X11/Xsession.d/89shr_elm_softkey and that waits some time until it starts shr_elm_softkey The wrapper loks like this: ---8- #!/bin/sh export DISPLAY=localhost:0 sleep 60 exec /usr/bin/shr_elm_softkey ---8- The Xsession-Skript is the following: ---8- #!/bin/sh -e DISPLAY=:0.0 /usr/bin/shr_elm_softkey.sh ---8- -- n...@el-hennig.de Lubarsky's Law of Cybernetic Entomology: There's always one more bug. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
On Wed, May 05, 2010 at 12:57:41PM +0200, n...@el-hennig.de wrote: For me it does not automatically, but as workaraound you can start shr_elm_softkey from the terminal and then it works fine. I found an even better way to workaraounf this problem automatically: I created a wrapper /usr/bin/shr_elm_softkey.sh that is called from /etc/X11/Xsession.d/89shr_elm_softkey and that waits some time until it starts shr_elm_softkey The wrapper loks like this: ---8- #!/bin/sh export DISPLAY=localhost:0 sleep 60 exec /usr/bin/shr_elm_softkey ---8- The Xsession-Skript is the following: ---8- #!/bin/sh -e DISPLAY=:0.0 /usr/bin/shr_elm_softkey.sh ---8- There is strace for not working http://build.shr-project.org/tests/jama/shr_elm.log.no and working start http://build.shr-project.org/tests/jama/shr_elm.log.yes As TAsn confirmed shr_elm_softkey needs illume module to be loaded before it's started. Your workaround works, but be aware that in that 60s you have to finish first run wizard (after reflash or .e removal). TAsn is checking possibilities for shr_elm_softkey autostarted by e17 itself. snip The best approach (imo), would be to make an app.desktop file, put it in /usr/share/applications (or standard place for your platform). Then in /etc/skel make a ./e/e/applications/startup/.order file with app.desktop listed in it. Then when new users get created, the ~/.e/e/applications/startup/.order file gets copied into users home dir and the QP app will get started every time they start E. /snip Shorter version of same workaround (not pushed because 20s is as bad as 60s for first start). sed -i 's#^DISPLAY=:0.0 /usr/bin/shr_elm_softkey#sh -c sleep 20 \\ /usr/bin/shr_elm_softkey#g' /etc/X11/Xsession.d/89shr_elm_softkey DISPLAY is also already set by /etc/profile.. -- uin:136542059jid:martin.ja...@gmail.com Jansa Martin sip:jama...@voip.wengo.fr JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Re: Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
TAsn is checking possibilities for shr_elm_softkey autostarted by e17 itself. That's probably the most elegant way. What I would like then, is to have the sliding shelf in the same style as the indicator, the capability of holding gadgets in the sliding shelf (like the IBar) and a possibility to configure the height of the shelf, if that is possible. -- n...@el-hennig.de Lubarsky's Law of Cybernetic Entomology: There's always one more bug. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
Wooha, after playing around too much with my installation today I broke it and reflashed my Freerunner with the lastest SHR unstable. And am stuck! Where do you guys keep up to date regarding the changes in the SHR apps? I installed shr-theme-neo again and noticed that the background and symbol font on the starter are black and thus the app names are unreadable. Changing the wallpaper does not change anything, the background stays plain black. The newly designed top bar does and power button-screen do not allow to close an application as they did before. So now when I open an app which has no quit button like tnagogps and then open another one, I'm stuck. I can't go back to the already opened instance because the left and right arrows to switch between apps are missing, and even if I could, I didn't know how to close it again. Tapping the tangopgs symbol again doesn't do anything: neither changing to the already opened instance out of sight nor opening a new one. How can I close apps? How can I switch between them? I really like the qwo keyboard, when I change the keyboard setting to qwo it permanently is overlayed on the screen, about middle of the screen, left side, and all app starter symbols are blanking out so I can't see any app anymore. qwo stays like this no matter what the topbars keyboard indicator status is and I have no clue how to make qwo go away and only appear when I tap the keyboard indicator icon like the default keyboard does. Any help appreciated Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
On Tue, May 4, 2010 at 4:15 PM, Jan Girlich vollk...@cryptobitch.de wrote: The newly designed top bar does and power button-screen do not allow to close an application as they did before. So now when I open an app which has no quit button like tnagogps and then open another one, I'm stuck. a few versions back there were back and close buttons on the bottom of the screen to handle switching and closing applications. in the latest versions those buttons were absent. so i have not opkg upgraded in some time because of it. something went down the tubes... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
Jan Girlich wrote: Wooha, after playing around too much with my installation today I broke it and reflashed my Freerunner with the lastest SHR unstable. And am stuck! Where do you guys keep up to date regarding the changes in the SHR apps? i don't... since the switch to fsogsmd+fsotld+etc... my neo is in a vegetative state I installed shr-theme-neo again and noticed that the background and symbol font on the starter are black and thus the app names are unreadable. (i'm the author of the neo theme ...at least illume and elm) i dont bother with illume2 for now ... i'm waiting till these issues are ironed out then i'll adapt the theme... what good does eye candy do when underlaying stuff is broken? :-P because of the current situation dont expect any theme updates until the current regressions are ironed out. you might want to try to switch to illume1 - window management and neo theme works there (go to illume settings - [i forgot the category] - profile and select illume-shr) br ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: latest SHR unstable: neo theme not working well, can't close apps anymore, qwo keyboard breaks starter
Am Mittwoch 05 Mai 2010 schrieb Bernd Prünster: because of the current situation dont expect any theme updates until the current regressions are ironed out. you might want to try to switch to illume1 - window management and neo theme works there (go to illume settings - [i forgot the category] - profile and select illume-shr) Once you tried illume2, you probably won't want to go back. At least in my case this was true. I am really looking forward to the upgrade of neo theme to illume2 ;-) -- Lars Lubarsky's Law of Cybernetic Entomology: There's always one more bug. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
'opkg list-upgradable' lists up-to-date packages on latest SHR unstable
Hi, just tried to update my phone because pretty much everything is broken (sms app dies right after opening, no contacts show up in contacts app, call screen dies after dialing so I can't hang up anymore, yadayada) But I discovered that when I execute 'opkg list-upgradable' or 'opkg upgrade' opkg tries upgrading programs which are already up-to-date. Is there any temp file or similar where the upgradable information is stored? Where does opkg get it's information from? How can I find out what's wrong here? Example: r...@om-gta02:~# opkg list-upgradable python-edbus - 0.3.1+svnr46504-ml0.4 - 0.3.1+svnr46510-ml0.4 [...] r...@om-gta02:~# opkg install python-edbus Package python-edbus (0.3.1+svnr46510-ml0.4) installed in root is up to date. Thanks Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'opkg list-upgradable' lists up-to-date packages on latest SHR unstable
On Sun, Mar 14, 2010 at 04:20:58PM +0100, Jan Girlich wrote: r...@om-gta02:~# opkg list-upgradable python-edbus - 0.3.1+svnr46504-ml0.4 - 0.3.1+svnr46510-ml0.4 [...] r...@om-gta02:~# opkg install python-edbus Package python-edbus (0.3.1+svnr46510-ml0.4) installed in root is up to date. Can you check your file /usr/lib/opkg/status? Does it mention python-edbus twice (or check the output of opkg list_installed)? If yes this is an old problem :-( I currently try to fix a broken /usr/lib/opkg/status as well. My file was truncated and I fixed it by reinstalling all packages found via ls /usr/lib/opkg/info/*.list but not available in status. Jens ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: 'opkg list-upgradable' lists up-to-date packages on latest SHR unstable
Am Sonntag, den 14.03.2010, 21:22 +0100 schrieb Jens Seidel: On Sun, Mar 14, 2010 at 04:20:58PM +0100, Jan Girlich wrote: r...@om-gta02:~# opkg list-upgradable python-edbus - 0.3.1+svnr46504-ml0.4 - 0.3.1+svnr46510-ml0.4 [...] r...@om-gta02:~# opkg install python-edbus Package python-edbus (0.3.1+svnr46510-ml0.4) installed in root is up to date. Can you check your file /usr/lib/opkg/status? Does it mention python-edbus twice (or check the output of opkg list_installed)? If yes this is an old problem :-( This solved my problem, thanks! Good luck with fixing your status file. Jan signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Latest SHR-?
I'm not using shr-t or any .29-rc3 kernel, so I cannot comment. But on shr ML and trac there was few reports about not getting GPS lock or GSM channel (even with debug kernel) and at least 3 people said that they are having this problem more often with nodebug kernel. I am one of those people ;-) the problem with registering GSM is not caused by the 'fast' kernel. However it occurs more often using the 'fast' kernel. Obviously there is something going wrong in FSO if the system responds much quicker than before with the debug kernel. I discussed that with Mickey last week during our regular munich openmoko meeting nd he is currently working on a solution for that problem, time permitting. So I asked spaetz (maintainer of shr-t) and he said that we should rather revert back to debug (as it's slower but as some say more stable). If we want to test nodebug kernel, we should do it rather in shr-u and *after* testing use it in shr-t too. With the new kernel I was able to register GSM only when I gave the system something to do (start navit for example). Then the modem registered correctly and the PIN dialogue popped up. Sounds strange, but it's just like that (a tribute to the mouse ;-) ). At the moment the debug kernel is better suited for every day use, but on the other hand the system speed the freerunner is capable of is amazing. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
On Friday 29 January 2010 09:15:07 n...@el-hennig.de wrote: With the new kernel I was able to register GSM only when I gave the system something to do (start navit for example). Then the modem registered correctly and the PIN dialogue popped up. Sounds strange, but it's just like that (a tribute to the mouse ;-) ). At the moment the debug kernel is better suited for every day use, but on the other hand the system speed the freerunner is capable of is amazing. I'm another one ;) Exactly the same symptoms here. signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
On Fri, Jan 29, 2010 at 10:33 AM, David Garabana Barro da...@garabana.com wrote: On Friday 29 January 2010 09:15:07 n...@el-hennig.de wrote: With the new kernel I was able to register GSM only when I gave the system something to do (start navit for example). Then the modem registered correctly and the PIN dialogue popped up. Sounds strange, but it's just like that (a tribute to the mouse ;-) ). At the moment the debug kernel is better suited for every day use, but on the other hand the system speed the freerunner is capable of is amazing. I'm another one ;) Exactly the same symptoms here. Which kernel are you guys using (on shr)? Andy-tracking? Cheers, Edwin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Latest SHR-?
Which kernel are you guys using (on shr)? Andy-tracking? I'm using this one: http://activationrecord.net/radekp/qtmoko/download/experimental/ Right now I switched back to the standard SHR-U kernel. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
On 29 January 2010 02:15, William Kenworthy bi...@iinet.net.au wrote: shr-testing is probably the most usable out-of-the-box at the moment. Only a few annoyances rather than show stoppers. I tried shr-t again a couple of days ago (after getting annoyed with the unreliability of my Debian...). I thought the integration of the phone apps, including the great today/locking screen, is now quite slick. And aesthetically it's now starting to look nice too. But - I found that I very quickly ran into system freezes, and/or weird graphical effects. E.g. after only a couple of minutes of panning and zooming the maps in tangogps. Am I the only one seeing this kind of problem? When that happens, the only remedy is to pull out the battery, and then I have no idea whether my rootfs is still OK. Is there a way of checking? (Maybe something similar to debsums in Debian.) Whenever I've had similar problems in the past (including on Debian), it's been when I've been running the glamo X server. So I would guess that that's the cause in shr-t too. Is it possible to run shr-t with the fbdev server? Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
On Friday 29 January 2010 10:51:46 Edder wrote: On Fri, Jan 29, 2010 at 10:33 AM, David Garabana Barro Which kernel are you guys using (on shr)? Andy-tracking? I'm using uImage-moredrivers-GTA02_oma-andy-a15608f241a40b41.bin, I'm getting similar errors with shr-u kernel, but less frequently. signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
Neil Jerram wrote: On 29 January 2010 02:15, William Kenworthy bi...@iinet.net.au wrote: shr-testing is probably the most usable out-of-the-box at the moment. Only a few annoyances rather than show stoppers. I tried shr-t again a couple of days ago (after getting annoyed with the unreliability of my Debian...). I thought the integration of the phone apps, including the great today/locking screen, is now quite slick. And aesthetically it's now starting to look nice too. But - I found that I very quickly ran into system freezes, and/or weird graphical effects. E.g. after only a couple of minutes of panning and zooming the maps in tangogps. Am I the only one seeing this kind of problem? You may want to run filesystem checks, a bad filesystem on flash or sdcard can cause all sorts of weird problems. I run shr-unstable. I upgrade often, get various improvements, and the occational breakage as well. But no freezes, just particular apps/functionality that fail Helge Hafting ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
Dnia 2010-01-28, czw o godzinie 19:22 -0500, Tony McKeehan pisze: I heard somewhere that there are some SHR-stable images on the way. Probably you could have read it on latest Community Updates page Have they been released? AFAIK no, they are still waiting for final bug reports for SHR-Testing. You could help with releasing SHR-Stable by filing bug reports to http://www.shr-project.org/trac . Until these bug reports are finished there will be no stable version. -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Email secured by Check Point ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
Dnia 2010-01-29, pią o godzinie 15:11 +0800, William Kenworthy pisze: Interesting - cant say Ive noticed anything bad - quite the reverse. Try image generated on 2010-01-15, it was totally unresponsive and slow. -- Patryk LeadMan Benderz Linux Registered User #377521 () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments Email secured by Check Point ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Re: Latest SHR-?
On Fri, 2010-01-29 at 09:15 +0100, n...@el-hennig.de wrote: I'm not using shr-t or any .29-rc3 kernel, so I cannot comment. But on shr ML and trac there was few reports about not getting GPS lock or GSM channel (even with debug kernel) and at least 3 people said that they are having this problem more often with nodebug kernel. I am one of those people ;-) the problem with registering GSM is not caused by the 'fast' kernel. However it occurs more often using the 'fast' kernel. Obviously there is something going wrong in FSO if the system responds much quicker than before with the debug kernel. I discussed that with Mickey last week during our regular munich openmoko meeting nd he is currently working on a solution for that problem, time permitting. So I asked spaetz (maintainer of shr-t) and he said that we should rather revert back to debug (as it's slower but as some say more stable). If we want to test nodebug kernel, we should do it rather in shr-u and *after* testing use it in shr-t too. With the new kernel I was able to register GSM only when I gave the system something to do (start navit for example). Then the modem registered correctly and the PIN dialogue popped up. Sounds strange, but it's just like that (a tribute to the mouse ;-) ). At the moment the debug kernel is better suited for every day use, but on the other hand the system speed the freerunner is capable of is amazing. The GSM chipset in my a5 FR worked ok on the 24 kernel, so-so on the .28 kernel - often took a number of reboots before the serial port would work to allow the OS to configure GSM. A *standard* unmodified .29 has never worked :( The fix for me was to make .29 behave like a .28 kernel and enable the GSM ... and leave it enabled. In .29 the kernel was changed to follow the specs and strobe the enable line (enable, wait 500ms, disable) which seems to work for everybody else but me (!) This current, modified kernel is perhaps the best behaved as far as GSM serial port goes that I have had up until now. And yes, there were a number of bug reports made and investigated with the consensus that my GSM chipset is faulty - however I am of the opinion that the kernel and framework handing of GSM is still not quite right and my chipset is just far enough out to cause problems. If you check the logs and it seems that the serial port is the problem, try the kernel and modules below. http://wdk.dyndns.org/freerunner/; unpack the modules to /lib/modules - it will be in 2.6.29-rc3-wdk so wont overwrite your current modules :) flash the kernel and boot. To return to your original, just reflash the old kernel and delete the new modules if finished with them. Use at own risk, yadda yadda ... This kernel been working very well for me for about a week, the gsm mod for about 6 months - have fun, Billk * Note that most of the fixes were from the mailing list, only the GSM one is mine. http://wdk.dyndns.org/freerunner/; Mods: * there are a couple of other msleeps in this file I set as well, but this was the critical fix for me! neo1973_pm_gsm.c neo1973_gpb_setpin(GTA01_GPIO_MODEM_ON, 1); msleep(500); /* neo1973_gpb_setpin(GTA01_GPIO_MODEM_ON, 0); leaves line high so serial stays working*/ Config was basic shr-t nodebug, with more debug items off, slub allocator and -O2 optimisation. It also has a 100ms delay for wifi as discussed on the list (where they recommended 10ms, neither value makes a difference to me, but I am not sure I suffer from the problem anyway - experimentation :) and a patch to wm8753.c to allow -O2 optimisation to compile. The .config (as config-wdk) is at the above address. All functions (wifi, usb, gsm, bluetooth, ...) seem to work well. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Latest SHR-?
I heard somewhere that there are some SHR-stable images on the way. Have they been released? If not, what image (lite) would you suggest I pick up for the time being that works best as an everyday phone (ie the most recent image)? Also, is there any specific kernel that has the logging disabled (like from the 'Significant speedups' thread) that work best with SHR? -Tonym ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
shr-testing is probably the most usable out-of-the-box at the moment. Only a few annoyances rather than show stoppers. The current kernel has most debugging disabled and though I used the default briefly (modified it for more speed soon after!), it seemed quite fast as is. BillK On Thu, 2010-01-28 at 19:22 -0500, Tony McKeehan wrote: I heard somewhere that there are some SHR-stable images on the way. Have they been released? If not, what image (lite) would you suggest I pick up for the time being that works best as an everyday phone (ie the most recent image)? Also, is there any specific kernel that has the logging disabled (like from the 'Significant speedups' thread) that work best with SHR? -Tonym ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- William Kenworthy bi...@iinet.net.au Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
On Fri, Jan 29, 2010 at 10:15:55AM +0800, William Kenworthy wrote: shr-testing is probably the most usable out-of-the-box at the moment. Only a few annoyances rather than show stoppers. IMHO best way is to install both shrs on different partitions and switch to 2nd if something goes wrong. The current kernel has most debugging disabled and though I used the default briefly (modified it for more speed soon after!), it seemed quite fast as is. No.. it's not disabled anymore (after few users reported that they see more issues with nodebug/nopreemt kernel). Cheers, -- uin:136542059jid:martin.ja...@gmail.com Jansa Martin sip:jama...@voip.wengo.fr JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
Interesting - cant say Ive noticed anything bad - quite the reverse. Everythings working and and some things like GSM serial port access are far better/more reliable than before. Then again, the extra changes I did involve patching a few things, turning off more debug, using the slub allocator instead of slab, and -02 instead of -Os. No benchmarks other than it seems justified as far as speed/reliability go compared to the old debug kernels and works well with shr-t :) BillK On Fri, 2010-01-29 at 07:26 +0100, Martin Jansa wrote: On Fri, Jan 29, 2010 at 10:15:55AM +0800, William Kenworthy wrote: shr-testing is probably the most usable out-of-the-box at the moment. Only a few annoyances rather than show stoppers. IMHO best way is to install both shrs on different partitions and switch to 2nd if something goes wrong. The current kernel has most debugging disabled and though I used the default briefly (modified it for more speed soon after!), it seemed quite fast as is. No.. it's not disabled anymore (after few users reported that they see more issues with nodebug/nopreemt kernel). Cheers, -- William Kenworthy bi...@iinet.net.au Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Latest SHR-?
On Fri, Jan 29, 2010 at 03:11:49PM +0800, William Kenworthy wrote: Interesting - cant say Ive noticed anything bad - quite the reverse. I'm not using shr-t or any .29-rc3 kernel, so I cannot comment. But on shr ML and trac there was few reports about not getting GPS lock or GSM channel (even with debug kernel) and at least 3 people said that they are having this problem more often with nodebug kernel. So I asked spaetz (maintainer of shr-t) and he said that we should rather revert back to debug (as it's slower but as some say more stable). If we want to test nodebug kernel, we should do it rather in shr-u and *after* testing use it in shr-t too. Regards, -- uin:136542059jid:martin.ja...@gmail.com Jansa Martin sip:jama...@voip.wengo.fr JaMa ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzz on GTA02v5 with latest SHR-Testing, do I need buzz fix ?
Hi Denis, A5 too, afected by buzzing here, now shr testing +Buzz fix+a7 alsa state file and no buzz at all. So seems is a hardware issue. I'm from Spain, but a buzz is buzz in any place it happens :) Regarsd 2009/4/29 Denis Johnson denis.john...@gmail.com: Currently running SHR Testing from around 22 April, on my GTA02V5 in Australia. While on a mobile to mobile call, the other party complained about buzzing. 1. Could someone please confirm that this is the hardware caused buzzing problem and not related to the distro or alsa state settings. 2. Are there any users in Australia with same batch (original group purchase via Perth/Brisbane) which also have the issue and have managed to get it corrected or have access to someone that can do the fix in Aus ? cheers Denis ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable embedded solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400, Arduino Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Buzz on GTA02v5 with latest SHR-Testing, do I need buzz fix ?
Denis Johnson wrote: Currently running SHR Testing from around 22 April, on my GTA02V5 in Australia. While on a mobile to mobile call, the other party complained about buzzing. 1. Could someone please confirm that this is the hardware caused buzzing problem and not related to the distro or alsa state settings. 2. Are there any users in Australia with same batch (original group purchase via Perth/Brisbane) which also have the issue and have managed to get it corrected or have access to someone that can do the fix in Aus ? I have about 8 sets of buzz fix parts from OpenMoko, and have previously (on the oz-moko list) said I'd send those parts to anyone who can fix devices in Australia. I haven't heard from anyone yet. -- Rod ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Buzz on GTA02v5 with latest SHR-Testing, do I need buzz fix ?
Currently running SHR Testing from around 22 April, on my GTA02V5 in Australia. While on a mobile to mobile call, the other party complained about buzzing. 1. Could someone please confirm that this is the hardware caused buzzing problem and not related to the distro or alsa state settings. 2. Are there any users in Australia with same batch (original group purchase via Perth/Brisbane) which also have the issue and have managed to get it corrected or have access to someone that can do the fix in Aus ? cheers Denis ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: rebooted the phone and the laptop, and still nothing dmesg gives this, which looks like it can see the phone, but not figure out what it is [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 . any ideas? I will try another usb cable or port ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/27 Jose Luis Perez Diez perezd...@gmail.com: El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: rebooted the phone and the laptop, and still nothing dmesg gives this, which looks like it can see the phone, but not figure out what it is [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 . any ideas? I will try another usb cable or port no, there was nothing wrong with the port or cable - someone at shr hadn't run depmod before creating the tarball, and the modules for communicating over usb weren't being loaded. if you run depmod on your phone, it should clear it up ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Mon, Apr 27, 2009 at 10:43 AM, Robin Paulson robin.paul...@gmail.com wrote: 2009/4/27 Jose Luis Perez Diez perezd...@gmail.com: El Saturday, 25 de April de 2009 01:30:45 Robin Paulson va escriure: rebooted the phone and the laptop, and still nothing dmesg gives this, which looks like it can see the phone, but not figure out what it is [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 . any ideas? I will try another usb cable or port no, there was nothing wrong with the port or cable - someone at shr hadn't run depmod before creating the tarball, and the modules for communicating over usb weren't being loaded. if you run depmod on your phone, it should clear it up It didn't when I tried this. I ended up flashing a newer version of SHR-testing (2009/04/22 if I remember corretly) and that one did work out of the box. That is untill I hit the suspend problem this morning... Regards Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Mon, Apr 27, 2009 at 6:43 PM, Robin Paulson robin.paul...@gmail.com wrote: no, there was nothing wrong with the port or cable - someone at shr hadn't run depmod before creating the tarball, and the modules for communicating over usb weren't being loaded. if you run depmod on your phone, it should clear it up I apologise for reporting this and then disappearing. Sometimes there are just not enough hours in the day. I just want to confirm that a combination of running 'depmod' in terminal on the phone and also using 'ifconfig -a' on my host (now upgraded to Ubuntu 9.04), I found that when the phone is plugged in that I got an 'eth1' listed so I changed my scripts accordingly and I can now SSH in. I have not rebooted the neo or my host yet but if anything changes I will report here. Thanks, to all for your replies and assist. cheers Denis ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Sat, Apr 25, 2009 at 08:37:50PM +1200, Robin Paulson wrote: i'm not entirely sure what it was, but i think it was related to some fiddling i did with depmod and modprobe on the phone. i'm guessing some usb modules weren't loaded by default The SHR packager forgot to run depmod before tarring up the rootfs. Alternatively, the initscripts should run depmod on startup. -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/25 Robin Paulson robin.paul...@gmail.com: 2009/4/24 Denis Johnson denis.john...@gmail.com: Flashing the latest SHR image and kernel from http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb on the host could see the neo but could not ifup usb0 Only after reflashing just the kernel back to Apr 9, could I again reconnect via SSH. I have not tried kernels posted between those dates to work out where the problem starts. Howver to confirm it, I have reflashed back to the latest 23rd April but could not connect, then reflashed back to 9th April and worked again. well, i fixed it - i can now ssh into my freerunner. i'm not entirely sure what it was, but i think it was related to some fiddling i did with depmod and modprobe on the phone. i'm guessing some usb modules weren't loaded by default ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Sat, 25 Apr 2009 22:05:35 +0200 Franky Van Liedekerke liede...@telenet.be wrote: ok, but how did you get to fiddle on the phone? Do you mean you actually used a terminal app, did some kind of modprobe on the phone and it started working? And now you don't remember what it was ... does this mean after the next reboot, you don't have ssh access anymore? Do the SHR people test these images? I've been told every time again it's the host (ethX instead of usb0), but I seriously believe something is wrong with the generated images ... my host fedora 10 system doesn't give any output in /var/log/messages when I plug in the phone with newer images (any old image reacts just fine), while it does give me info when I boot the phone in the NOR menu to flash it. To prove it myself, I will *again* flash my phone with the latest image/kernel found in http://build.shr-project.org/shr-unstable/images/ ok, I just tested this kernel and it seems to be ok now: it is eth1, and I've adapted my qtextended install script a bit, so it doesn't use the alias for the rm command. For the record, I tried from this url http://build.shr-project.org/shr-unstable/images/om-gta02/, the following rootfs and uImage: uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin openmoko-shr-lite-image-glibc-ipk--20090423-om-gta02.rootfs.jffs2 Although I don't like the following kernel messages, could somebody explain these? Apr 26 00:26:20 om-gta02 user.err kernel: [21474817.485000] HDQ error: 1 Apr 26 00:26:20 om-gta02 user.info kernel: [21474817.50] HDQ responds again Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/26 Franky Van Liedekerke liede...@telenet.be: ok, but how did you get to fiddle on the phone? Do you mean you actually used a terminal app, did some kind of modprobe on the phone yes. and it started working? And now you don't remember what it was ... does this mean after the next reboot, you don't have ssh access anymore? no, i can still ssh in after rebooting Do the SHR people test these images? I've been told every time again it's the host (ethX instead of usb0), but I seriously believe something yes, eth4 on my laptop is wrong with the generated images ... my host fedora 10 system doesn't give any output in /var/log/messages when I plug in the phone with newer images (any old image reacts just fine), while it does give me info when I boot the phone in the NOR menu to flash it. try dmesg, you'll see lots of errors from it trying to recognise the phone when you try to connect to the phone, my understanding is it's talking to a kernel module on the phone. the relevant module was not loaded afaics. i ran lsmod on the phone, and nothing was returned. i think i ran depmod, then modprobe ehci_usb (or maybe ehci_usb) and depmod again, then plugged it in, and lsusb (on the laptop) revealed it as being connected (it wasn't previously shown) i could always see the phone fine while it was booted to nor To prove it myself, I will *again* flash my phone with the latest image/kernel found in http://build.shr-project.org/shr-unstable/images/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
USB Kernel problem with latest SHR unstable
I'm not sure who or how to report this but since I have gone through the test and it has taken some time to resolve. Flashing the latest SHR image and kernel from http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb on the host could see the neo but could not ifup usb0 Only after reflashing just the kernel back to Apr 9, could I again reconnect via SSH. I have not tried kernels posted between those dates to work out where the problem starts. Howver to confirm it, I have reflashed back to the latest 23rd April but could not connect, then reflashed back to 9th April and worked again. Both report 2.6.29-rc3 via 'uname -r' cheers Denis ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Fri, 24 Apr 2009 16:38:59 +1000 Denis Johnson denis.john...@gmail.com wrote: I'm not sure who or how to report this but since I have gone through the test and it has taken some time to resolve. Flashing the latest SHR image and kernel from http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb on the host could see the neo but could not ifup usb0 Only after reflashing just the kernel back to Apr 9, could I again reconnect via SSH. I have not tried kernels posted between those dates to work out where the problem starts. Howver to confirm it, I have reflashed back to the latest 23rd April but could not connect, then reflashed back to 9th April and worked again. Both report 2.6.29-rc3 via 'uname -r' cheers Denis have you tried ifup ethx (with x the number of the new interface)? I've been told it is eth on the host now, but it doesn't work for me either ... Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Am Freitag 24 April 2009 08:57:48 schrieb Denis Johnson: Sorry to reply to my own post. Issue not quite as described. Between reflashing from 23rd April to 9th, one of the attempts at connecting also involved a reboot of my Ubuntu host. Which still failed to allow me to connect with the Kernel from the 2rd. Reflashing with the kernel from the 9th then worked. However, repeating the exercise as described bellow, also fails on the Kernel from the 9th. So something else is still at play here and it may be Ubuntu/host related. On Fri, Apr 24, 2009 at 4:38 PM, Denis Johnson denis.john...@gmail.com wrote: I'm not sure who or how to report this but since I have gone through the test and it has taken some time to resolve. Flashing the latest SHR image and kernel from http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3 .4-om-gta02.bin I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb on the host could see the neo but could not ifup usb0 Only after reflashing just the kernel back to Apr 9, could I again reconnect via SSH. I have not tried kernels posted between those dates to work out where the problem starts. Howver to confirm it, I have reflashed back to the latest 23rd April but could not connect, then reflashed back to 9th April and worked again. Both report 2.6.29-rc3 via 'uname -r' cheers Denis Did you try Franky's suggestion? It is indeed ethX now... Klaus 'mrmoku' Kurzmann ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 09:59:26PM +1200, Robin Paulson wrote: 2009/4/24 Klaus 'mrmoku' Kurzmann m...@mnet-online.de: Did you try Franky's suggestion? It is indeed ethX now... what number is 'x'? i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 gave 'unknown interface' Perhaps you could try looking in /var/log/syslog on Ubuntu? If unsure :- Unplug the USB, run 'tail -f /var/log/syslog' then plug it back in and post the output to the list. Cheers Ben ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/24 Ben Thompson b...@york.ac.uk: i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 gave 'unknown interface' Perhaps you could try looking in /var/log/syslog on Ubuntu? If unsure :- Unplug the USB, run 'tail -f /var/log/syslog' then plug it back in and post the output to the list. ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? anyway: Apr 24 22:20:01 inzy-laptop /USR/SBIN/CRON[16759]: (root) CMD ([ -x /usr/sbin/update-motd ] /usr/sbin/update-motd 2/dev/null) Apr 24 22:20:04 inzy-laptop kernel: [12898.209072] eth1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) Apr 24 22:20:34 inzy-laptop kernel: [12928.209045] eth1: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: 2009/4/24 Ben Thompson b...@york.ac.uk: ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. dmesg looks like this when i plug in my neo: usb 8-1: new full speed USB device using uhci_hcd and address 5 usb 8-1: New USB device found, idVendor=1457, idProduct=5122 usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 8-1: Product: RNDIS/Ethernet Gadget usb 8-1: Manufacturer: Linux 2.6.29-rc3 with s3c2410_udc usb 8-1: configuration #1 chosen from 2 choices eth1 (cdc_ether): not using net_device_ops yet eth1: register 'cdc_ether' at usb-:00:1d.3-1, CDC Ethernet Device, 00:1f:11:01:72:33 eth1: no IPv6 routers present so if u look at the beginning of the last three lines you see the interface name. greets Thomas ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/24 Klaus 'mrmoku' Kurzmann m...@mnet-online.de: Did you try Franky's suggestion? It is indeed ethX now... what number is 'x'? i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 gave 'unknown interface' ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
Robin Paulson wrote: 2009/4/24 Klaus 'mrmoku' Kurzmann m...@mnet-online.de: Did you try Franky's suggestion? It is indeed ethX now... what number is 'x'? i tried with 0, 1 and 2, and 0 and 1 gave a 'no such device' error, 2 gave 'unknown interface' Please post here output of /sbin/ip link show It would be much easier for everyone than just guessing the name of the network device. signature.asc Description: OpenPGP digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann zimmerm...@vdm-design.de wrote: Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: 2009/4/24 Ben Thompson b...@york.ac.uk: ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. Check: http://lists.openmoko.org/pipermail/devel/2009-April/005384.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
On Friday 24 April 2009 15:16:38 Nelson Castillo wrote: On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann zimmerm...@vdm-design.de wrote: Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: 2009/4/24 Ben Thompson b...@york.ac.uk: ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. Check: http://lists.openmoko.org/pipermail/devel/2009-April/005384.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community On my Ubuntu 8.10 the shr-unstable behaves exactly as described in the link. The X depends on your number of network cards. I use a notebook which has a cable and a Wifi ethernet adapter named eth0 and eth1. However the Neo becomes eth3 as it connects. I collected the information from the Wiki about USB Networking in a script, which i use until I managed to integrate the Neo better into Ubuntu and it's various network configuration mechanisms. The script has a variable for the interface as the first line. Adapt it to your needs and run it after you have connected your Neo to the USB port. I use ifconfig to check out the known network cards and their configuration. Regards thomas No Neo: eth1 Link encap:Ethernet HWaddr 00:15:00:22:c5:db inet6 addr: fe80::215:ff:fe22:c5db/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:117175 errors:141 dropped:141 overruns:0 frame:0 TX packets:9346 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3955 (3.9 KB) TX bytes:4599 (4.5 KB) Interrupt:21 Memory:c840-c8400fff loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2560 (2.5 KB) TX bytes:2560 (2.5 KB) Neo connected: eth1 Link encap:Ethernet HWaddr 00:15:00:22:c5:db inet6 addr: fe80::215:ff:fe22:c5db/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:131173 errors:141 dropped:141 overruns:0 frame:0 TX packets:10491 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3955 (3.9 KB) TX bytes:4599 (4.5 KB) Interrupt:21 Memory:c840-c8400fff eth3 Link encap:Ethernet HWaddr 00:1f:11:01:2e:ee inet6 addr: fe80::21f:11ff:fe01:2eee/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1564 (1.5 KB) TX bytes:580 (580.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2560 (2.5 KB) TX bytes:2560 (2.5 KB) Neo configured with frnet.sh eth1 Link encap:Ethernet HWaddr 00:15:00:22:c5:db inet6 addr: fe80::215:ff:fe22:c5db/64 Scope:Link UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:133181 errors:141 dropped:141 overruns:0 frame:0 TX packets:10667 errors:0 dropped:5 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3955 (3.9 KB) TX bytes:4599 (4.5 KB) Interrupt:21 Memory:c840-c8400fff eth3 Link encap:Ethernet HWaddr 00:1f:11:01:2e:ee inet addr:192.168.0.200 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::21f:11ff:fe01:2eee/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:46 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5546 (5.5 KB) TX bytes:10629 (10.6 KB) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:48 errors:0 dropped:0 overruns:0 frame:0 TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2560 (2.5 KB) TX bytes:2560 (2.5 KB) frnet.sh Description: application/shellscript ___ Openmoko community mailing list community@lists.openmoko.org
Re: USB Kernel problem with latest SHR unstable
On Fri, Apr 24, 2009 at 4:08 PM, Thomas Otterbein th.otterb...@gmx.net wrote: On Friday 24 April 2009 15:16:38 Nelson Castillo wrote: On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann zimmerm...@vdm-design.de wrote: Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: 2009/4/24 Ben Thompson b...@york.ac.uk: ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. Check: http://lists.openmoko.org/pipermail/devel/2009-April/005384.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community On my Ubuntu 8.10 the shr-unstable behaves exactly as described in the link. The X depends on your number of network cards. I use a notebook which has a cable and a Wifi ethernet adapter named eth0 and eth1. However the Neo becomes eth3 as it connects. I collected the information from the Wiki about USB Networking in a script, which i use until I managed to integrate the Neo better into Ubuntu and it's various network configuration mechanisms. The script has a variable for the interface as the first line. Adapt it to your needs and run it after you have connected your Neo to the USB port. I use ifconfig to check out the known network cards and their configuration. On my Fedora 10 laptop nothing appears to happen anymore when I plug in the Neo. No messages in /var/log/messages, nothing in dmesg. [m8...@fedora10 ~]$ sudo /sbin/ip link show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1c:23:01:c4:a0 brd ff:ff:ff:ff:ff:ff 3: wmaster0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ieee802.11 00:1b:77:60:df:64 brd ff:ff:ff:ff:ff:ff 4: wlan0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 00:1b:77:60:df:64 brd ff:ff:ff:ff:ff:ff 5: pan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN link/ether 52:6d:38:6a:32:49 brd ff:ff:ff:ff:ff:ff I am booting from U-Boot (in NAND) though, the post referenced above mentions SHR-testing (the distro on the SD I'm booting from) behaving differently when booted from QI. I get the same result on my Xubuntu laptop so I fear that something else got broken with the opkg update, opkg upgrade I performed. So far I haven't found a description of what is needed on the side of the FreeRunner itself. When I check ifconfig -a on the FreeRunner I see an eth0 interface with no IP address, eth0:avah alias with IP 169.254.7.134 and the loopback device. ip link show shows the loopback device and the eth0 interface. When I check the /etc/network/interfaces it contains a comment right before the auto usb0 section saying: # Ethernet/RNDIS gadget (g_ether) # ... or on host side, usbnet and random hwaddr ifup usb0 retruns: ifup: interface usb0 already configured but ifconfig usb0 returns: ifconfig usb0: error fetching interface information: Device not found modprobe g_ether on the FreeRunner fails to locate the module so maybe some modules are missing? Or is this module no longer needed? loading the usbnet module on either the Fedora or the Xubuntu laptop does not help. One final note: the hardware is fine, when I start FDOM from the device's main memory it is still recognized. Thanks in advance. Bram ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/25 Nelson Castillo arhu...@freaks-unidos.net: On Fri, Apr 24, 2009 at 5:42 AM, Thomas Zimmermann zimmerm...@vdm-design.de wrote: Am Freitag 24 April 2009 12:20:00 schrieb Robin Paulson: 2009/4/24 Ben Thompson b...@york.ac.uk: ok, i'm confused now. why do i want to run this on my host? the problem's with the phone, isn't it? I don't know why, but the interface name on my host changed. For me it's now eth1. Check: http://lists.openmoko.org/pipermail/devel/2009-April/005384.html well, this is interesting. lsusb no longer shows my neo as attached what gives? i rebooted the phone and the laptop, and still nothing dmesg gives this, which looks like it can see the phone, but not figure out what it is [ 1448.937469] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1451.316831] usb 1-1: new full speed USB device using uhci_hcd and address 18 [ 1466.428058] usb 1-1: device descriptor read/64, error -110 [ 1481.644065] usb 1-1: device descriptor read/64, error -110 [ 1481.863121] usb 1-1: new full speed USB device using uhci_hcd and address 19 [ 1482.092099] hub 1-0:1.0: unable to enumerate USB device on port 1 [ 1483.696065] usb 1-1: new full speed USB device using uhci_hcd and address 20 [ 1498.808067] usb 1-1: device descriptor read/64, error -110 [ 1514.032503] usb 1-1: device descriptor read/64, error -110 [ 1514.248047] usb 1-1: new full speed USB device using uhci_hcd and address 21 [ 1529.361074] usb 1-1: device descriptor read/64, error -110 [ 1544.581050] usb 1-1: device descriptor read/64, error -110 [ 1544.797061] usb 1-1: new full speed USB device using uhci_hcd and address 22 [ 1555.205040] usb 1-1: device not accepting address 22, error -110 [ 1555.319135] usb 1-1: new full speed USB device using uhci_hcd and address 23 [ 1565.728069] usb 1-1: device not accepting address 23, error -110 [ 1565.729365] hub 1-0:1.0: unable to enumerate USB device on port 1 any ideas? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: USB Kernel problem with latest SHR unstable
2009/4/24 Denis Johnson denis.john...@gmail.com: Flashing the latest SHR image and kernel from http://shr.bearstech.com/shr-unstable/images/om-gta02/ 23 April uImage-2.6.29-oe10+gitr119800+0b9d21bf5d05d5dd909425a67a8be2eb1c1fc579-r3.4-om-gta02.bin I could not connect via SSH over USB from my Ubuntu 8.10 host. lsusb on the host could see the neo but could not ifup usb0 Only after reflashing just the kernel back to Apr 9, could I again reconnect via SSH. I have not tried kernels posted between those dates to work out where the problem starts. Howver to confirm it, I have reflashed back to the latest 23rd April but could not connect, then reflashed back to 9th April and worked again. is this related to a discrepancy in the version of the modules? i.e. the modules not being the same as the version of the kernel? it's been pointed out to me that the kernel is version 2.6.29-rc3, while the modules are apparently version -rc2 where can i get an older version of the kernel - the only one on the shr site appears to be the latest, i.e. 22nd april? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
