Re: Serious problems after failed upgrade
Brian-32 wrote: > >> > On Wed, 2010-03-17 at 08:28 -0800, vancel35 wrote: >> > > Unfortunately I cannot get into the boot menu, and my desktop >> > > computers don't see the FR. Not only that, but last night I tried >> > > the 1 amp wall charger to see if the higher output would get it to >> > > recognize the USB/power cable, and it didn't. >> > > > > This is probably a stupid question but have you tried removing the > battery and leaving the FR unplugged for ~15 minutes and then see if > you can get the NOR boot menu? I only ask because I've had a similar > issue and this solved my problem. > Further update this morning, since letting the FR "rest" worked, I re-flashed the kernel with the SHR kernel from March 4th (I think it's the 4th... it's the most recent kernel flash image on the site). To see if the kernel modules were what were preventing the USB from being recognized, and the USB is still unrecognized. My last backup was done a week or two ago. I think I've only added a couple of appointments since then (gpe-calendar). Brian-32 wrote: > > As far as the desktops not seeing the device via USB do you get any > useful info from doing an lsusb or lsusb -vv as superuser ? What does > ifconfig say ? I recommend trying this on both the FR and your > desktop. Perhaps the device name is different from what it normally is. > I use the following on my desktop to get networking up: > > ip addr add 192.168.0.200/24 dev eth4;iptables -A POSTROUTING -t nat -j > MASQUERADE -s 192.168.0.0/24;sysctl -w net.ipv4.ip_forward=1 > > Your device may vary in the above example the FR is eth4. > >> > > The interesting thing about the USB port is that if I plug the >> > > adapter into the FR while it's turned off, it recognizes the >> > > connection and boots (as expected) but somewhere along the way the >> > > USB port is completely disabled. I don't know if it's a mokonnect >> > > failure or what, but something is completely hosed. So much that >> > > I used to be able to take the battery out as long as it was >> > > connected to the charger, but now it turns off as if it wasn't. >> > > > > It sounds like the USB port is okay but since Qi doesn't initialize > USB you have to rely on the kernel to do it and it sounds like your > install isn't. > The DFU works now, but once it's booted, it's as if a disconnected cable is plugged into my desktop. Brian-32 wrote: > >> > > I also need the buzz fix done on my phone, so if there were a US >> > > company that I could send the phone to that would do that work, >> > > maybe they could reinstall the bootloader so that I could at least >> > > get to the boot menu. That's really all I need is to get to the >> > > boot menu and I can do the rest from there. >> > > > > I hope you get the issue resolved I have an A5 without the buzzfix and > so far I haven't had any buzzfix related issues. Just some minor tweaks > to the mic volume have sorted out the noise issues on SHR for me. > > Good luck Laura ;-) > > Brian > My buzz may be software related too, because I first started getting complaints about buzz after I upgraded in February. I had never had any complaints before that, so I may just be able to alter a configuration and get it fixed. I have the skills to do the buzz fix on my own (experience with circuit board soldering and modification), but I'm not sure my current soldering gun has a fine enough point (Cold Heat). I was considering doing mine anyway and then offering up a buzz-fix party or maybe do it for those that can't. I was hoping to be able to take the lazy way out. ;) -Laura -- View this message in context: http://n2.nabble.com/Serious-problems-after-failed-upgrade-tp4747627p4757652.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: Serious problems after failed upgrade
> > I hope you get the issue resolved I have an A5 without the buzzfix and > so far I haven't had any buzzfix related issues. Just some minor tweaks > to the mic volume have sorted out the noise issues on SHR for me. > Hi Neil, Sorry to hijack the thread, but could you post your tweaked soundconfig on the Wiki? http://wiki.openmoko.org/wiki/Neo_Freerunner_audio_subsystem#Empirical_Data_for_Mic_Settings This could help others to find more useable settings for their phone. Thanks, Niels. _ Surf veilig : download Internet Explorer 8 http://www.microsoft.com/belux/nl/windows/internet-explorer/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Serious problems after failed upgrade
Brian-32 wrote: > > This is probably a stupid question but have you tried removing the > battery and leaving the FR unplugged for ~15 minutes and then see if > you can get the NOR boot menu? I only ask because I've had a similar > issue and this solved my problem. > > As far as the desktops not seeing the device via USB do you get any > useful info from doing an lsusb or lsusb -vv as superuser ? What does > ifconfig say ? I recommend trying this on both the FR and your > desktop. Perhaps the device name is different from what it normally is. > I use the following on my desktop to get networking up: > > ip addr add 192.168.0.200/24 dev eth4;iptables -A POSTROUTING -t nat -j > MASQUERADE -s 192.168.0.0/24;sysctl -w net.ipv4.ip_forward=1 > > Your device may vary in the above example the FR is eth4. > >> > > The interesting thing about the USB port is that if I plug the >> > > adapter into the FR while it's turned off, it recognizes the >> > > connection and boots (as expected) but somewhere along the way the >> > > USB port is completely disabled. I don't know if it's a mokonnect >> > > failure or what, but something is completely hosed. So much that >> > > I used to be able to take the battery out as long as it was >> > > connected to the charger, but now it turns off as if it wasn't. >> > > > > It sounds like the USB port is okay but since Qi doesn't initialize > USB you have to rely on the kernel to do it and it sounds like your > install isn't. > >> > > Would I be able to fix it if I had a debug board? >> > > > > I don't see how NOR could be broken since this is an FR we're talking > about. > >> > > I also need the buzz fix done on my phone, so if there were a US >> > > company that I could send the phone to that would do that work, >> > > maybe they could reinstall the bootloader so that I could at least >> > > get to the boot menu. That's really all I need is to get to the >> > > boot menu and I can do the rest from there. >> > > > > I hope you get the issue resolved I have an A5 without the buzzfix and > so far I haven't had any buzzfix related issues. Just some minor tweaks > to the mic volume have sorted out the noise issues on SHR for me. > >> > > The FreeRunner was my first smart phone, and I've gotten used to >> > > it. I don't want to tether myself to either Apple or Google, and >> > > I definitely don't want a Microsoft smart phone, so that leaves >> > > the FR, or some other smart phone that I haven't found yet. > > There's always the Nokia N900 which is really pricey but a very nice toy > indeed. I'm a cheapskate but the friends I know that own the N900 are > pretty happy with it so far. > > Good luck Laura ;-) > > Brian > My FR has been sitting all day turned off, and I just went upstairs to prep it for an overnight without the battery, but I decided to see if I could get to the NOR boot menu one more time before I let it sit overnight, and whadayaknow... it came up to the boot menu. :D The USB port still isn't recognized, so I can't charge it yet, but I can at least reflash now. :) Thanks Brian! -Laura -- View this message in context: http://n2.nabble.com/Serious-problems-after-failed-upgrade-tp4747627p4755140.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: Serious problems after failed upgrade
W.Kenworthy wrote: > > Why dont you reflash? (you do know that the FR has two boot options for > flashing - one being read only so it cant be easily trashed? - see the > wiki) > > Your description implies that the upgrade left you with a missmatched > kernel and modules, or no modules - can you flash your original kernel > back (you do keep backups/versions? :) > > Put a distro on an SD card, boot and install the matching modules > package. > > Just depends how much you lose with whats on the phone - easier just to > reflash and start again if nothing valuable. > > BillK > How do I reflash when I can't get to the boot menu? The boot menu I'm talking about is the one when you hold the aux button and press the power button. If that's the NOR boot menu, then I can't get to the NOR boot menu. I'll try what Brian suggested in his email and leave it with no power (battery or charger) for a while... I'll do overnight, because I can't remember if I left the battery out for any length of time after this has happened. I'll let everyone know if this works. Thanks! :) -Laura -- View this message in context: http://n2.nabble.com/Serious-problems-after-failed-upgrade-tp4747627p4755122.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: Serious problems after failed upgrade
> > On Wed, 2010-03-17 at 08:28 -0800, vancel35 wrote: > > > Unfortunately I cannot get into the boot menu, and my desktop > > > computers don't see the FR. Not only that, but last night I tried > > > the 1 amp wall charger to see if the higher output would get it to > > > recognize the USB/power cable, and it didn't. > > > This is probably a stupid question but have you tried removing the battery and leaving the FR unplugged for ~15 minutes and then see if you can get the NOR boot menu? I only ask because I've had a similar issue and this solved my problem. As far as the desktops not seeing the device via USB do you get any useful info from doing an lsusb or lsusb -vv as superuser ? What does ifconfig say ? I recommend trying this on both the FR and your desktop. Perhaps the device name is different from what it normally is. I use the following on my desktop to get networking up: ip addr add 192.168.0.200/24 dev eth4;iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24;sysctl -w net.ipv4.ip_forward=1 Your device may vary in the above example the FR is eth4. > > > The interesting thing about the USB port is that if I plug the > > > adapter into the FR while it's turned off, it recognizes the > > > connection and boots (as expected) but somewhere along the way the > > > USB port is completely disabled. I don't know if it's a mokonnect > > > failure or what, but something is completely hosed. So much that > > > I used to be able to take the battery out as long as it was > > > connected to the charger, but now it turns off as if it wasn't. > > > It sounds like the USB port is okay but since Qi doesn't initialize USB you have to rely on the kernel to do it and it sounds like your install isn't. > > > Would I be able to fix it if I had a debug board? > > > I don't see how NOR could be broken since this is an FR we're talking about. > > > I also need the buzz fix done on my phone, so if there were a US > > > company that I could send the phone to that would do that work, > > > maybe they could reinstall the bootloader so that I could at least > > > get to the boot menu. That's really all I need is to get to the > > > boot menu and I can do the rest from there. > > > I hope you get the issue resolved I have an A5 without the buzzfix and so far I haven't had any buzzfix related issues. Just some minor tweaks to the mic volume have sorted out the noise issues on SHR for me. > > > The FreeRunner was my first smart phone, and I've gotten used to > > > it. I don't want to tether myself to either Apple or Google, and > > > I definitely don't want a Microsoft smart phone, so that leaves > > > the FR, or some other smart phone that I haven't found yet. There's always the Nokia N900 which is really pricey but a very nice toy indeed. I'm a cheapskate but the friends I know that own the N900 are pretty happy with it so far. Good luck Laura ;-) Brian On Thu, 18 Mar 2010 07:55:34 +0800 William Kenworthy wrote: > Why dont you reflash? (you do know that the FR has two boot options > for flashing - one being read only so it cant be easily trashed? - > see the wiki) > She can't reflash according to the original post. She hasn't been able to get the NOR boot menu to come up while pressing AUX. > Your description implies that the upgrade left you with a missmatched > kernel and modules, or no modules - can you flash your original kernel > back (you do keep backups/versions? :) > She apparently can boot into SHR but the only app that works is the terminal app. Since the USB device doesn't see either a charger or a USB cable connected to it she doesn't have too many options. > Put a distro on an SD card, boot and install the matching modules > package. > Trying an SD card install probably isn't a bad idea. I haven't successfully tried an SD card install myself but from what I've read Qi polls the SD card for a kernel first and this kernel can be skipped by holding AUX in to boot from the NAND install correct? > Just depends how much you lose with whats on the phone - easier just > to reflash and start again if nothing valuable. > > BillK > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Serious problems after failed upgrade
Why dont you reflash? (you do know that the FR has two boot options for flashing - one being read only so it cant be easily trashed? - see the wiki) Your description implies that the upgrade left you with a missmatched kernel and modules, or no modules - can you flash your original kernel back (you do keep backups/versions? :) Put a distro on an SD card, boot and install the matching modules package. Just depends how much you lose with whats on the phone - easier just to reflash and start again if nothing valuable. BillK On Wed, 2010-03-17 at 08:28 -0800, vancel35 wrote: > Unfortunately I cannot get into the boot menu, and my desktop computers don't > see the FR. Not only that, but last night I tried the 1 amp wall charger to > see if the higher output would get it to recognize the USB/power cable, and > it didn't. > > The interesting thing about the USB port is that if I plug the adapter into > the FR while it's turned off, it recognizes the connection and boots (as > expected) but somewhere along the way the USB port is completely disabled. > I don't know if it's a mokonnect failure or what, but something is > completely hosed. So much that I used to be able to take the battery out as > long as it was connected to the charger, but now it turns off as if it > wasn't. > > Would I be able to fix it if I had a debug board? > > I also need the buzz fix done on my phone, so if there were a US company > that I could send the phone to that would do that work, maybe they could > reinstall the bootloader so that I could at least get to the boot menu. > That's really all I need is to get to the boot menu and I can do the rest > from there. > > The FreeRunner was my first smart phone, and I've gotten used to it. I > don't want to tether myself to either Apple or Google, and I definitely > don't want a Microsoft smart phone, so that leaves the FR, or some other > smart phone that I haven't found yet. -- William Kenworthy Home in Perth! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Serious problems after failed upgrade
Unfortunately I cannot get into the boot menu, and my desktop computers don't see the FR. Not only that, but last night I tried the 1 amp wall charger to see if the higher output would get it to recognize the USB/power cable, and it didn't. The interesting thing about the USB port is that if I plug the adapter into the FR while it's turned off, it recognizes the connection and boots (as expected) but somewhere along the way the USB port is completely disabled. I don't know if it's a mokonnect failure or what, but something is completely hosed. So much that I used to be able to take the battery out as long as it was connected to the charger, but now it turns off as if it wasn't. Would I be able to fix it if I had a debug board? I also need the buzz fix done on my phone, so if there were a US company that I could send the phone to that would do that work, maybe they could reinstall the bootloader so that I could at least get to the boot menu. That's really all I need is to get to the boot menu and I can do the rest from there. The FreeRunner was my first smart phone, and I've gotten used to it. I don't want to tether myself to either Apple or Google, and I definitely don't want a Microsoft smart phone, so that leaves the FR, or some other smart phone that I haven't found yet. -- View this message in context: http://n2.nabble.com/Serious-problems-after-failed-upgrade-tp4747627p4751376.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: Serious problems after failed upgrade
On Tue, 16 Mar 2010, vancel35 wrote: > After the reboot, I have a few problems, and I'm not sure how to fix it. > > 1) the boot menu doesn't come up (aux-power) > 2) when booted normally, it doesn't recognize the USB connected, and the > battery doesn't charge. > 3) I can't start any programs except the terminal. (this means I can't dim > the backlight to make the battery last longer and gain more time to solve > this problem) > > I have an A6 FreeRunner, and since the "brick" problems were fixed by the > boot menu, I didn't buy the debug board. > > Is there any way to recover my phone? If I need to buy a debug board, > hopefully I'll be able to find one. If there's something I can do to > get it to even get to the boot menu, I'd be happy. assuming i understand your situation correctly (which i may well not) i have done the same thing a few times recently (as a result of update-alternatives linking init to busybox) and thanks to the dual-boot-environment nature of the freerunner you definitely haven't bricked it. you will need the dfu-util tool to upload a new kernel and rootfs, but i assume you have this already; you can get it via the wiki if not. 1) get a new flashable kernel (uImage*.bin) and root fs (shr-*-rootfs.jffs2) from http://build.shr-project.org/shr-unstable/images/om-gta02/ 2) disconnect USB cable. 3) boot into NOR flash (power off, hold down AUX, hold down POWER until you see the NOR boot screen, release AUX and power). 4) connect USB cable directly between PC and phone; do NOT use a hub. use dfu-util to upload the new root fs and kernel images; precise incantations can be found at http://www.teaparty.net/technotes/openmoko-3.html#Upgrading-the-OS , though the filenames are old Om2008 ones, and you will need to substitute your new rootfs and uImage files. if the phone powers off, which it will do after about 30s of indolence, repeat step 3. 5) power off, reboot. note: THIS WILL WIPE OUT ANY CUSTOMISATION YOU HAVE MADE TO YOUR PHONE. it will be blank but properly-installed and ready for you to re-customise. i hope this is of some use, and that i have not misunderstood the problem completely. -- Tom Yates - http://www.teaparty.net ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Serious problems after failed upgrade
On Tue, Mar 16, 2010 at 7:06 PM, vancel35 wrote: > The only problem is that I can't even get into the phone. The boot menu > doesn't come up, and it doesn't recognize the USB connection. ah sorry, i miss read. i thought you said you CAN get those... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Serious problems after failed upgrade
jeremy jozwik wrote: > > had that problem a few moths ago on shr. i was able to ssh into the > phone and re-start the upgrade but the phone never really became > operational. > > ended up copying whatever files i needed to my desktop, and did a reflash. > lesson of the ordeal... dont bother with opkg upgrade. > The only problem is that I can't even get into the phone. The boot menu doesn't come up, and it doesn't recognize the USB connection. Worst case is I'll get into the phone, copy everything that I want to the microSD in the terminal, and just be done with it. The reason I tried for the upgrade was that on top of being my daily phone, I've recently been using it as a mobile data connection for my netbook, but after what seems like a specific amount of data is transferred, the GPRS connection and mdbus locks (have to reboot the phone to recover). I hoped that there was an upgraded driver, because I remember someone talking about dropped connections after data transfer. -- View this message in context: http://n2.nabble.com/Serious-problems-after-failed-upgrade-tp4747627p4747769.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: Serious problems after failed upgrade
On Tue, Mar 16, 2010 at 6:19 PM, vancel35 wrote: > I tried to upgrade last night (Mar 15th), and it didn't complete, but the > display got messed up enough that I couldn't continue the process. I > thought the upgrade was complete since the command prompt was back, so I > rebooted. had that problem a few moths ago on shr. i was able to ssh into the phone and re-start the upgrade but the phone never really became operational. ended up copying whatever files i needed to my desktop, and did a reflash. lesson of the ordeal... dont bother with opkg upgrade. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Serious problems after failed upgrade
I tried to upgrade last night (Mar 15th), and it didn't complete, but the display got messed up enough that I couldn't continue the process. I thought the upgrade was complete since the command prompt was back, so I rebooted. After the reboot, I have a few problems, and I'm not sure how to fix it. 1) the boot menu doesn't come up (aux-power) 2) when booted normally, it doesn't recognize the USB connected, and the battery doesn't charge. 3) I can't start any programs except the terminal. (this means I can't dim the backlight to make the battery last longer and gain more time to solve this problem) I have an A6 FreeRunner, and since the "brick" problems were fixed by the boot menu, I didn't buy the debug board. Is there any way to recover my phone? If I need to buy a debug board, hopefully I'll be able to find one. If there's something I can do to get it to even get to the boot menu, I'd be happy. In hindsight I should have left it turned on, connected via SSH and finished the upgrade without a reboot, but unfortunately I didn't. :( I've never lost the boot menu. I'm on SHR-unstable, and my bootloader is Qi. I appreciate any help offered. -Laura -- View this message in context: http://n2.nabble.com/Serious-problems-after-failed-upgrade-tp4747627p4747627.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
