Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem
On Monday 01 March 2010 04:16:22 Brolin Empey wrote: Does anyone use USB networking with their FreeRunner with Windows Vista or Windows 7? I had it working with XP. But now i switched all my machines (even at work) to linux. I think i left preinstalled win 7 on my notebook so i can try at home. that does not even matter any more until I fix the USB port hardware problem. You can try besides wifi also bluetooth networking. It should not be hard to set it up (but doing it all with onscreen keyboard could require some patience). But there can be problem that bluetooth is sometimes gone after suspend/resume. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problems with NWA
Ben Thompson b...@york.ac.uk writes: On Sun, Feb 28, 2010 at 01:52:01PM +0200, Timo Juhani Lindfors wrote: Ben Thompson b...@york.ac.uk writes: I will see if I can reliably reproduce the problem and submit a bug report if there isn't one (where should I do this?). http://bugs.openmoko.org is the place for kernel bugs. Set the component to System Software, an example bug: http://docs.openmoko.org/trac/ticket/2327 Thanks for that. The bug looks similar to :- http://docs.openmoko.org/trac/ticket/2267 I'm not sure how to read the dmesg stuff but it seems that the backtrace is very similar. Could someone take a look at the dmesg I provided earlier in this thread and comment? No, this backtrace of yours is entirely different. Please file a ticket preferrably with a way to reproduce it. Or at least be ready to test patches. I hope i can make the oops you report go away, but i need some way to test the possible solutions. Do not forget to specify kernel version you're using. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem
Hi Using qtmoko V16, I have found that suspending using the power button or waking by plugging in the charger guarantee that bluetooth is killed. If I allow the phone to suspend through timeout settings or wake the phone before attaching to a charge/usb source then bluetooth remains good for weeks. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v18 - based on 2.6.32
Hi, i have uploaded experimental QtMoko-v18 images. These images are based on 2.6.32 linux kernel. They can be downloaded from: http://sourceforge.net/projects/qtmoko/files/ The kernel was built from openmoko's git [1]. Kernel config and patches can be found here[2]. The images can be probably used as daily phone, but there some things that are still missing on not working correctly: - X server and X apps: the touchscreen generates bogus events. E.g. when typing on virtual keyboard it often presses wrong keys. If you use X applications often, then i dont recomend this image yet. - accelerometers: dont work - the driver has not been ported to 2.6.32 kernel yet. - bluetooth: after supend/resume you have to go to dev settings and use Power on bluetooth manually to bring it back. Otherwise the new kernel runs really nice. Bluetooth and accelerometers should be quite easy to fix. I dont know about the touchscreen in X. Any other distro that uses 2.6.32 kernel has X server all right? If there are no other regressions i am thinking about making 2.6.32 kernel default for QtMoko. Thanks to Lars and others on IRC for help! Cheers Radek [1] http://git.openmoko.org/?p=kernel.git;a=shortlog;h=refs/heads/om- gta02-2.6.32 [2] http://github.com/radekp/qtmoko/tree/lin2632/devices/neo/linux_kernel/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [QtMoko] intermittent USB networking + non-working WLAN = must use wired LAN = USB port hardware problem
Dave dave...@gmail.com writes: Using qtmoko V16, I have found that suspending using the power button or waking by plugging in the charger guarantee that bluetooth is killed. And what do you mean by killed? Does BT adapter disappear from lsusb list? Or does bluetoothd get confused by something? Or what? Please clarify, probably adding relevant dmesg and bluetoothd debug log lines, along with the information about the kernel version you use. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:fercer...@gmail.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v18 - based on 2.6.32
On Mon, Mar 01, 2010 at 01:09:24PM +0100, Radek Polak wrote: Otherwise the new kernel runs really nice. Bluetooth and accelerometers should be quite easy to fix. I dont know about the touchscreen in X. Any other distro that uses 2.6.32 kernel has X server all right? With 2.6.32 built with OE available here: http://build.shr-project.org/tests/mrmoku/kms/images/om-gta02/ defconfig http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux-openmoko-2.6.32/om-gta02/defconfig I don't see any strange touchscreen behavior in xserver-1.8 snapshot and I don't remember any ts issues with 1.7.* versions (except that I was missing ts filters in first defconfig and then ts calibration wasn't able to find sysfs nodes). http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/xserver-kdrive-common/xserver-kdrive-common/shr/89xTs_Calibrate If there are no other regressions i am thinking about making 2.6.32 kernel default for QtMoko. Great! Yesterday Thomas White pushed WSOD fix for his DRM driver, so I hope we could move to 2.6.32 with SHR soon too. 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: QtMoko v18 - based on 2.6.32
* Radek Polak wrote, Il 01/03/2010 13:09: Hi, i have uploaded experimental QtMoko-v18 images. These images are based on 2.6.32 linux kernel. They can be downloaded from: http://sourceforge.net/projects/qtmoko/files/ This a fantastic news! :-) Really thanks to all involved. -- Andrea ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v18 - based on 2.6.32
On Monday 01 March 2010 13:31:26 Martin Jansa wrote: On Mon, Mar 01, 2010 at 01:09:24PM +0100, Radek Polak wrote: Otherwise the new kernel runs really nice. Bluetooth and accelerometers should be quite easy to fix. I dont know about the touchscreen in X. Any other distro that uses 2.6.32 kernel has X server all right? With 2.6.32 built with OE available here: http://build.shr-project.org/tests/mrmoku/kms/images/om-gta02/ defconfig http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux -openmoko-2.6.32/om-gta02/defconfig I don't see any strange touchscreen behavior in xserver-1.8 snapshot and I don't remember any ts issues with 1.7.* versions (except that I was missing ts filters in first defconfig and then ts calibration wasn't able to find sysfs nodes). Hi Martin, thanks for pointers. I tried the latest 2.6.32 SHR kernel, but it does not work very good for me. Probably because of KSM. I am still using old Xglamo which segfaults with this kernel and fbdev xorg prints: (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (EE) FBDEV(0): mode initialization failed Fatal server error: AddScreen/ScreenInit failed for driver 0 I can try upgrade to debian testing so that i can try xf86-video-glamo (or is there package for lenny somewhere?). Anyway thanks! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v18 - based on 2.6.32
On Mon, Mar 01, 2010 at 03:58:26PM +0100, Radek Polak wrote: On Monday 01 March 2010 13:31:26 Martin Jansa wrote: On Mon, Mar 01, 2010 at 01:09:24PM +0100, Radek Polak wrote: Otherwise the new kernel runs really nice. Bluetooth and accelerometers should be quite easy to fix. I dont know about the touchscreen in X. Any other distro that uses 2.6.32 kernel has X server all right? With 2.6.32 built with OE available here: http://build.shr-project.org/tests/mrmoku/kms/images/om-gta02/ defconfig http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux -openmoko-2.6.32/om-gta02/defconfig I don't see any strange touchscreen behavior in xserver-1.8 snapshot and I don't remember any ts issues with 1.7.* versions (except that I was missing ts filters in first defconfig and then ts calibration wasn't able to find sysfs nodes). Hi Martin, thanks for pointers. I tried the latest 2.6.32 SHR kernel, but it does not work very good for me. Probably because of KSM. I am still using old Xglamo which segfaults with this kernel and fbdev xorg prints: (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (EE) FBDEV(0): mode initialization failed Fatal server error: AddScreen/ScreenInit failed for driver 0 I can try upgrade to debian testing so that i can try xf86-video-glamo (or is there package for lenny somewhere?). xglamo is deprecated a long time now. You should definitively switch to the xserver-xorg-video-glamo package from testing or unstable. We (pkg-fso) do not maintain any backports so far, so there probably won't be any lenny packages for this. Apart from this I don't think you want to use the xserver-xorg from lenny, because this one still depends on HAL ;) -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v18 - based on 2.6.32
On Mon, Mar 01, 2010 at 03:58:26PM +0100, Radek Polak wrote: On Monday 01 March 2010 13:31:26 Martin Jansa wrote: On Mon, Mar 01, 2010 at 01:09:24PM +0100, Radek Polak wrote: Otherwise the new kernel runs really nice. Bluetooth and accelerometers should be quite easy to fix. I dont know about the touchscreen in X. Any other distro that uses 2.6.32 kernel has X server all right? With 2.6.32 built with OE available here: http://build.shr-project.org/tests/mrmoku/kms/images/om-gta02/ defconfig http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/linux/linux -openmoko-2.6.32/om-gta02/defconfig I don't see any strange touchscreen behavior in xserver-1.8 snapshot and I don't remember any ts issues with 1.7.* versions (except that I was missing ts filters in first defconfig and then ts calibration wasn't able to find sysfs nodes). Hi Martin, thanks for pointers. I tried the latest 2.6.32 SHR kernel, but it does not work very good for me. Probably because of KSM. I am still using old Xglamo which segfaults with this kernel and fbdev xorg prints: (EE) FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (EE) FBDEV(0): mode initialization failed Fatal server error: AddScreen/ScreenInit failed for driver 0 Yes that's right, sorry I should warn you before trying, this kernel expects kms enabled xf86-video-glamo in userspace and disables old fbdev driver. Good thing is that kms enabled xf86-video-glamo in userspace is able to fallback to swrast when DRM kernel is not used. So in SHR we have the same userspace and used kernel decide how it will render. I can try upgrade to debian testing so that i can try xf86-video-glamo (or is there package for lenny somewhere?). No idea. Thomas White's kms branch is already merged to master, so package built from there with latest revision should be enough. http://git.openmoko.org/?p=xf86-video-glamo.git;a=summary You also need mesa and libdrm with Thomas's patches. http://git.bitwiz.org.uk/?p=libdrm.git;a=summary http://git.bitwiz.org.uk/?p=mesa.git;a=summary 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: elm_browser initial release
Hi, Thanks for the suggestion. I've applied. Interestingly, it seems like profusion/samsung are pushing their port of webkit to efl upstream. Hopefully, things should get a lot better soon. -- View this message in context: http://n2.nabble.com/Ventura-browser-NEW-release-15-Jan-tp4357081p4655147.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Help with buzz fix/SMD soldering in Hamburg, Germany
Am Freitag, den 26.02.2010, 20:33 +0100 schrieb Christian Weßel: Hi folks, I am living also near Hamburg and I am also looking for contacts and help. I found someone at the Chaos Computer Club chapter in Hamburg who has experience with SMD soldering and is willing to change the resistor for me. I also found a dealer in Hamburg selling the resistor I need. BUT, he never did this form factor 0402 before nor a buzz fix. And I'm only getting one of two parts needed. So if you, Christian, or anyone else in or around Hamburg wants some soldering done on his phone this is the time to speak up and I see what I can get organized. 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: Help with buzz fix/SMD soldering in Hamburg, Germany
Hello Jan, that sound good. Let's go on and see whats happen, I will partizipate. christian (wesse...@gmx.net) Am Montag, den 01.03.2010, 18:54 +0100 schrieb Jan Girlich: Am Freitag, den 26.02.2010, 20:33 +0100 schrieb Christian Weßel: Hi folks, I am living also near Hamburg and I am also looking for contacts and help. I found someone at the Chaos Computer Club chapter in Hamburg who has experience with SMD soldering and is willing to change the resistor for me. I also found a dealer in Hamburg selling the resistor I need. BUT, he never did this form factor 0402 before nor a buzz fix. And I'm only getting one of two parts needed. So if you, Christian, or anyone else in or around Hamburg wants some soldering done on his phone this is the time to speak up and I see what I can get organized. Cheers Jan ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Flurstraße 14 29640 Schneverdingen Tel.: +49 171 357 59 57 eMail: wesse...@gmx.net Web: http://wesselch.homelinux.org Skype: wesselch 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: Help with buzz fix/SMD soldering in Hamburg, Germany
So if you, Christian, or anyone else in or around Hamburg wants some soldering done on his phone this is the time to speak up and I see what I can get organized. here's one too! i am in hamburg and looking for the #1024 fix. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problems with NWA
On Mon, Mar 01, 2010 at 01:36:01PM +0300, Paul Fertser wrote: No, this backtrace of yours is entirely different. Please file a ticket preferrably with a way to reproduce it. Or at least be ready to test patches. I hope i can make the oops you report go away, but i need some way to test the possible solutions. Do not forget to specify kernel version you're using. Hi I can reproduce this problem using NWA but I am not sure what is going on at the D-Bus level. Maybe someone could help me (maybe Niko)? I have latest SHR-U with NWA installed from Niko's opkg repo and I made the oops happen like this :- 1. I create two profiles in NWA :- a) An WPA-Enterprise network with PEAP and RADIUS server cert defined and no MAC address defined b) An Open network with a MAC address defined 2. I then enabled these profiles (in NWA) and also enabled the profile called any_open. 3. Then sited the Freerunner in a location where non of the profiles specified in (1) above are withing range, but there is a third open network with a weak signal (Quality=4/94 Signal level=-91 dBm Noise level=-95 dBm). 4. Let NWA associate with the weak access point (I don't know what this AP is; its's just a signal I picked up from my house). I see this in dmesg :- [ 887.86] AR6000 connected event on freq 2437 with bssid 00:22:75:dd:76:51 listenInterval=100, beaconInterval = 100, beaconIeLen = 0 assocReqLen=41 assocRespLen =59 [ 887.86] Network: Infrastructure 5. The signal is weak and I do not recieve a DHCP lease (perhaps the UDP does not go well over weak wifi) but NWA says Connected. 6. I now disable the any_open profile in NWA and see this in dmesg :- [ 931.29] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 941.61] eth0: no IPv6 routers present 7. Now I quit NWA and although it appears to exit OK, this is when I see the Kernel Oops :- [ 961.89] Unable to handle kernel NULL pointer dereference at virtual address 002c [ 961.89] pgd = c6ae4000 [ 961.895000] [002c] *pgd=36a3a031, *pte=, *ppte= [ 961.90] Internal error: Oops: 17 [#1] PREEMPT [ 961.90] Modules linked in: ar6000 snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx_i2s snd_soc_s3c24xx s3cmci btusb rfcomm ppp_generic slhc ohci_hcd ipv6 hidp l2cap bluetooth g_ether snd_soc_wm8753 snd_soc_core snd_pcm snd_timer snd_page_alloc snd [ 961.90] CPU: 0Not tainted (2.6.29-rc3 #1) [ 961.90] PC is at wmi_cmd_send+0x98/0xc0 [ar6000] [ 961.90] LR is at wmi_cmd_send+0x60/0xc0 [ar6000] [ 961.90] pc : [bf159834]lr : [bf1597fc]psr: 8013 [ 961.90] sp : c7b73d28 ip : c7b73d28 fp : c7b73d44 [ 961.90] r10: c7b73d7c r9 : c6032e00 r8 : c686dcc0 [ 961.90] r7 : 0009 r6 : r5 : r4 : c686dcc0 [ 961.90] r3 : r2 : r1 : c686dcc0 r0 : c69fa682 [ 961.90] Flags: Nzcv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user [ 961.90] Control: c000717f Table: 36ae4000 DAC: 0015 [ 961.90] Process wpa_supplicant (pid: 1092, stack limit = 0xc7b72268) [ 961.90] Stack: (0xc7b73d28 to 0xc7b74000) [ 961.90] 3d20: c69fa684 c7b73d6c c7b73d48 [ 961.90] 3d40: bf15b9d8 bf1597ac c7bdc000 c7bdc460 c7b72000 c6032e00 [ 961.90] 3d60: c7b73db4 c7b73d70 bf1538ec bf15b960 0064 00cd 0001 [ 961.90] 3d80: c69b2a60 c005c744 c7b73d88 c7b73d88 bf1537c8 c7b73e78 c02e4138 8b18 [ 961.90] 3da0: c7bdc000 c7b73e1c c7b73db8 c02b7ea8 bf1537d8 c7b73e88 c7b73e2c [ 961.90] 3dc0: c03bfe70 [ 961.90] 3de0: c7b73e04 c7b73e78 bef23bd0 c7bdc000 c7b73e1c c7b73e78 bef23bd0 [ 961.90] 3e00: 8b18 c08c63e8 c7b72000 c08c63e8 c7b73e54 c7b73e20 c02b80ac c02b7c30 [ 961.90] 3e20: bf1537c8 000a 8b18 c7b73e74 bef23bd0 8b18 [ 961.90] 3e40: c002cfe4 c7b73ecc c7b73e58 c0247390 c02b8000 c7b73ef4 [ 961.90] 3e60: c7b73fa4 c7b73e70 c02364bc c0236244 c7b73e8c c7b73e80 30687465 [ 961.90] 3e80: c69b2a60 c69b2e98 [ 961.90] 3ea0: 6093 8b18 bef23bd0 bef23bd0 8b18 c002cfe4 c7b72000 40023000 [ 961.90] 3ec0: c7b73eec c7b73ed0 c023593c c0246cdc c699e140 c0235720 bef23bd0 8b18 [ 961.90] 3ee0: c7b73f0c c7b73ef0 c00ae894 c0235730 bef23bd0 c699e140 c39fe748 0005 [ 961.90] 3f00: c7b73f7c c7b73f10 c00aef14 c00ae86c c7b73e10 c7b73e14 c7b73f18 bef23ca8 [ 961.90] 3f20: 0003cd40 0008 0003ce50 c7b73f70 0003cdc8 c7b73f7c c7b73f48 [ 961.90] 3f40: c0030540 c003c158 c7b73f70 c03a4f40 c02bed70 c699e140 bef23bd0 8b18 [ 961.90] 3f60: 0005 c002cfe4 c7b72000 40023000 c7b73fa4 c7b73f80 c00aefc0 c00aea0c [ 961.90] 3f80: 4b8c283f
Re: Problems with NWA
On Mon, Mar 1, 2010 at 10:19 PM, Ben Thompson b...@york.ac.uk wrote: [...] I can reproduce this problem using NWA but I am not sure what is going on at the D-Bus level. Maybe someone could help me (maybe Niko)? You may try to produce a wpa_supplicant.conf with the exact parameters you see in nwa.conf, and start/stop wpa_suppliant to see if it reproduces the oops. The only think I guess *may* be different is that when NWA quits it does not kill wpa_supplicant, but simply remove all network definition and remove eth0 from managed interfaces. So it may trigger some actions that may reveal hidden kernel bugs not usual on other wifi managers? Anyway the problem should be fixed in kernel space ;) Paul, count me as a patch tester! Niko ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problems with NWA
On Mon, Mar 01, 2010 at 01:36:01PM +0300, Paul Fertser wrote: Ben Thompson b...@york.ac.uk writes: On Sun, Feb 28, 2010 at 01:52:01PM +0200, Timo Juhani Lindfors wrote: Ben Thompson b...@york.ac.uk writes: I will see if I can reliably reproduce the problem and submit a bug report if there isn't one (where should I do this?). http://bugs.openmoko.org is the place for kernel bugs. Set the component to System Software, an example bug: http://docs.openmoko.org/trac/ticket/2327 Thanks for that. The bug looks similar to :- http://docs.openmoko.org/trac/ticket/2267 I'm not sure how to read the dmesg stuff but it seems that the backtrace is very similar. Could someone take a look at the dmesg I provided earlier in this thread and comment? No, this backtrace of yours is entirely different. Please file a ticket preferrably with a way to reproduce it. Or at least be ready to test patches. I hope i can make the oops you report go away, but i need some way to test the possible solutions. Do not forget to specify kernel version you're using. Here is the ticket I have created: https://docs.openmoko.org/trac/ticket/2333 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Help with buzz fix/SMD soldering in Hamburg, Germany
Am Montag, den 01.03.2010, 21:47 +0100 schrieb arne anka: So if you, Christian, or anyone else in or around Hamburg wants some soldering done on his phone this is the time to speak up and I see what I can get organized. here's one too! i am in hamburg and looking for the #1024 fix. Okay, guys, I'm just asking my contact if he's okay with that right now. I'll keep you updated on this and the next steps in the next days. 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
