Re: [SHR-u] Abyss or gsm0710muxd? (Was: Re: [SHR] opkg upgrade (10 Aug 2009))
I think it was added to the image at some point in time. Don't know why it wasn't installed automatically but it was mentioned on this (another?) mailing list at some time and I installed it manually. I always try to avoid to reflash. I've got SHR working to my liking, I've got a couple of custom apps and I have the stupid habit of not writing down what I changed. I even didn't reflash when it was announced that you had to (I think that was when unstable became testing). I usually fix problems by reinstalling or removing and reinstalling packages. Dirk On 13.08.2009, at 06:33, David Fokkema wrote: > On Wed, 2009-08-12 at 13:56 -0400, D. Gassen wrote: >> I had the same problem but I solved that (for me) by reinstalling a >> couple of packages: >> >> opkg install -force-reinstall libgsm0710mux0 libfsotransport0 \ >> libfsoframework0 libfsobasics0 fso-abyss fsousaged \ >> libgsm0710mux-config frameworkd frameworkd-config-shr \ >> libframeworkd-phonegui-efl0 \ >> shr-contacts shr-messages shr-dialer ophonekitd >> >> (I hope I got them all, I didn't use one command but several) >> >> After that the phone connected properly to the GSM network, was able >> to read all my contacts and I could make and receive calls again. > > That's funny. I don't have fso-abyss on my phone. Apparently, it is a > new GSM muxer implementation by Mickey to replace fso-gsm0710muxd, > which > _is_ installed on my phone. I'm running SHR-unstable from July 31st > (or > a few days before that). Did something change in the latest images? > Isn't SHR using nice metapackages to move people to the new daemon on > upgrade? Or did you just custom install fso-abyss? > > David > > > ___ > 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
[SHR-u] Abyss or gsm0710muxd? (Was: Re: [SHR] opkg upgrade (10 Aug 2009))
On Wed, 2009-08-12 at 13:56 -0400, D. Gassen wrote: > I had the same problem but I solved that (for me) by reinstalling a > couple of packages: > > opkg install -force-reinstall libgsm0710mux0 libfsotransport0 \ >libfsoframework0 libfsobasics0 fso-abyss fsousaged \ > libgsm0710mux-config frameworkd frameworkd-config-shr \ > libframeworkd-phonegui-efl0 \ > shr-contacts shr-messages shr-dialer ophonekitd > > (I hope I got them all, I didn't use one command but several) > > After that the phone connected properly to the GSM network, was able > to read all my contacts and I could make and receive calls again. That's funny. I don't have fso-abyss on my phone. Apparently, it is a new GSM muxer implementation by Mickey to replace fso-gsm0710muxd, which _is_ installed on my phone. I'm running SHR-unstable from July 31st (or a few days before that). Did something change in the latest images? Isn't SHR using nice metapackages to move people to the new daemon on upgrade? Or did you just custom install fso-abyss? David ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] opkg upgrade (10 Aug 2009)
D. Gassen wrote: > I had the same problem but I solved that (for me) by reinstalling a > couple of packages: > > opkg install -force-reinstall libgsm0710mux0 libfsotransport0 \ >libfsoframework0 libfsobasics0 fso-abyss fsousaged \ > libgsm0710mux-config frameworkd frameworkd-config-shr \ > libframeworkd-phonegui-efl0 \ > shr-contacts shr-messages shr-dialer ophonekitd > > (I hope I got them all, I didn't use one command but several) > > After that the phone connected properly to the GSM network, was able > to read all my contacts and I could make and receive calls again. > > Dirk That's exactly what I love about the openmoko community. Thank you very much, that did the trick for me, too! :) Regards, Konstantin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] opkg upgrade (10 Aug 2009)
I had the same problem but I solved that (for me) by reinstalling a couple of packages: opkg install -force-reinstall libgsm0710mux0 libfsotransport0 \ libfsoframework0 libfsobasics0 fso-abyss fsousaged \ libgsm0710mux-config frameworkd frameworkd-config-shr \ libframeworkd-phonegui-efl0 \ shr-contacts shr-messages shr-dialer ophonekitd (I hope I got them all, I didn't use one command but several) After that the phone connected properly to the GSM network, was able to read all my contacts and I could make and receive calls again. Dirk On 12.08.2009, at 13:28, Konstantin wrote: > Davide Scaini wrote: >> today upgrade fixed the thing for me... >> d >> > > Unfortuneately, GSM still doesn't work for me after the upgrade. > The alternate image (SHR stable) I am using via NAND works okay, > though. > /var/log/ophonekitd.log just says > "GSM not available, try again in 5s" > a few times, then a few > "idle notifier state handler called, id 1" > with verious ids, and the SIM entry dialog never pops up. :( > Anyone else with that problem? > > Regards, > Konstantin > > ___ > 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: [SHR] opkg upgrade (10 Aug 2009)
Davide Scaini wrote: > today upgrade fixed the thing for me... > d > Unfortuneately, GSM still doesn't work for me after the upgrade. The alternate image (SHR stable) I am using via NAND works okay, though. /var/log/ophonekitd.log just says "GSM not available, try again in 5s" a few times, then a few "idle notifier state handler called, id 1" with verious ids, and the SIM entry dialog never pops up. :( Anyone else with that problem? Regards, Konstantin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] opkg upgrade (10 Aug 2009)
today upgrade fixed the thing for me... d On 8/11/09, Adam Jimerson wrote: > On Tuesday 11 August 2009 06:29:49 am Sebastian Krzyszkowiak wrote: >> >> The answer is: read, before you do. It was said everywhere: don't opkg >> upgrade! Latest unstable image is the last good working ATM :P > > If by latest unstable image you mean the one released on the 8th of August > then that wasn't working for me as well GSM wouldn't come on, screen would > not > dim, and the phone didn't show that it was charting or not via the led light > on the power button or the battery icon on the top shelf. I hope that a > update to fix this problem will be released soon. > -- > "We must plan for freedom, and not only for security, if for no other reason > than only freedom can make security more secure." Karl Popper > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR] opkg upgrade (10 Aug 2009)
On Tuesday 11 August 2009 06:29:49 am Sebastian Krzyszkowiak wrote: > > The answer is: read, before you do. It was said everywhere: don't opkg > upgrade! Latest unstable image is the last good working ATM :P If by latest unstable image you mean the one released on the 8th of August then that wasn't working for me as well GSM wouldn't come on, screen would not dim, and the phone didn't show that it was charting or not via the led light on the power button or the battery icon on the top shelf. I hope that a update to fix this problem will be released soon. -- "We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure." Karl Popper 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: [SHR] opkg upgrade (10 Aug 2009)
Hi, Sebastian Krzyszkowiak wrote: > > The answer is: read, before you do. It was said everywhere: don't opkg > upgrade! Latest unstable image is the last good working ATM :P > Didn't see that myself. Not that it would have stopped me. I've been waiting for the FSO enhancements to show up in SHR-U. -- View this message in context: http://n2.nabble.com/-SHR--opkg-upgrade-%2810-Aug-2009%29-tp3420265p3423526.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: [SHR] opkg upgrade (10 Aug 2009)
On 8/11/09, Niall Haslam wrote: > Hi, > > opkg update and upgrade fail as of today for me, on SHR unstable. > > Error: > Upgrading fsousaged on root from > 0.0.0.0+gitr359+74528d0cdab7f7c193c9fd86e4432b57155c74b7-r5.0 to > 0.0.0.0+gitr368+e808af24134049c4f41e77f6e5de1c9144a7e7b1-r5.0... > Downloading > http://build.shr-project.org/shr-unstable/ipk/armv4t/fsousaged_0.0.0.0+gitr368+e808af24134049c4f41e77f6e5de1c9144a7e7b1-r5.0_armv4t.ipk > Collected errors: > * ERROR: Cannot satisfy the following dependencies for fsousaged: > * libfsoframework0 (>= > 0.1.0.0+gitr368+e808af24134049c4f41e77f6e5de1c9144a7e7b1) * > > The settings dialogues report the error that they cannot connect to > FSO. I've tried restarting it but to no avail. Any ideas? I have > libfsoframework0 gitr359 installed. But trying to update this alone > doesn't solve the problem. Does the repo need refreshed? > > Thanks. The answer is: read, before you do. It was said everywhere: don't opkg upgrade! Latest unstable image is the last good working ATM :P -- Sebastian Krzyszkowiak dos ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[SHR] opkg upgrade (10 Aug 2009)
Hi, opkg update and upgrade fail as of today for me, on SHR unstable. Error: Upgrading fsousaged on root from 0.0.0.0+gitr359+74528d0cdab7f7c193c9fd86e4432b57155c74b7-r5.0 to 0.0.0.0+gitr368+e808af24134049c4f41e77f6e5de1c9144a7e7b1-r5.0... Downloading http://build.shr-project.org/shr-unstable/ipk/armv4t/fsousaged_0.0.0.0+gitr368+e808af24134049c4f41e77f6e5de1c9144a7e7b1-r5.0_armv4t.ipk Collected errors: * ERROR: Cannot satisfy the following dependencies for fsousaged: * libfsoframework0 (>= 0.1.0.0+gitr368+e808af24134049c4f41e77f6e5de1c9144a7e7b1) * The settings dialogues report the error that they cannot connect to FSO. I've tried restarting it but to no avail. Any ideas? I have libfsoframework0 gitr359 installed. But trying to update this alone doesn't solve the problem. Does the repo need refreshed? Thanks. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
