Re: [2008.9] Suspending questions
Thomas White rašė: > On Tue, 23 Sep 2008 11:50:04 +0200 > "Christoph Siegenthaler"<[EMAIL PROTECTED]> wrote: > > >> I've got the following problem: suspending the FR works (by pressing >> on/off and automatically) but every time I wake it up (by pressing >> on/off) the device wakes up for about 2s and returns straight back to >> its suspended state - until I press on/off again. The second time, >> resuming works ok. Any hints on how to fix this? >> > > I have problems that sound a lot like this if I have automatic suspend > enabled. With it turned off, the problems go away but obviously > there's a danger of flattening the battery if (say) the Neo gets woken > up by a missed call and you don't notice for a number of hours. > Same here, but even with automatic blanking switched off. Had this problem ever since installed Om2008.8 on August 31st. Keep up the good work, fellows! -- sledge ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Video on Freerunner?
Mikko Rauhala rašė: > Quoting Tim Dobson<[EMAIL PROTECTED]>: > >> you tube video are possible on the free runner. though not instantly... >> > > See my earlier mail on Youtube offering mp4 versions of their videos. > I still don't know if anyone's verified how balrog-kun's referenced > glamo-accelerated mplayer plays them (or if the glamo output has received > further finetuning). I am trying to play a 20 min short movie. Transcoding it from 640x352 WMA 170MB video according to http://wiki.openmoko.org/wiki/Video_Player#Playback_using_480x640_.2F_640x480 Resulting one I tried many sizes, ranging 50-150 in MegaBytes. But running with mplayer output.avi -sws 0 -nodouble -vo sdl -fs -framedrop [ -autosync 30 -vf scale -zoom -xy 640 -vf rotate=1 ] mplayer crashes Running with glamo mplayer (http://downloads.tuxfamily.org/3v1deb/openmoko/mplayer-glamo.tar.bz2) with `-vo glamo' it writes out Badly interleaved AVI file detected - switching to -ni mode... And then I can see the video only after seeking, but it is incredibly slow. Strange, why is it badly interleaved, I have transcoded it with wiki's mencoder -o -ofps 13 -vf scale -zoom -xy 640 -af channels=1:0:0:1:0 -oac lavc -ovc lavc -lavcopts acodec=libmp3lame:vcodec=h263p:autoaspect=1:vbitrate=300:abitrate=32 The best performance (~4 fps) I have achieved was with transcoding into the ~210x100 final video and running opkg installed non-glamo mplayer. Tried -vo fbdev (-vo sdl does not work), too. Also mplayer crashes were also occasional. I am launching a movie from an SD card. Maybe it may slow some things down, too. Has anyone gone any better than this, please share. -- sledge ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Problem with usb cable: device descriptor read/64, error -110
Yhaw! It was enough today just to flash this: http://downloads.openmoko.org/releases/Om2008.8-update/Om2008.8-gta02-20080903.uImage.bin and cdc_ether immediately gave out usb0 (before to even get the usb `new full speed USB device using uhci_h' line, I had to suspend and then wake up. So, it was the kernel's problem (and for some reason the 20080826 did not work (bad image) on my FR DateCode: 20080725). Case close, into the new explorations! ;) and thanks for everyone's care, -- sledge Sarton O'Brien rašė: > On Wednesday 03 September 2008 10:32:17 sledgeas wrote: > >> Please, refer to this >> http://n2.nabble.com/Can-bad-NAND-blocks-cause-USB%27s-%22device-descriptor >> -read-64%2C-error--110%22---tp835094p835094.html for more full info. >> A guy in #openmoko suggested my flash blocks might be bad and fs not >> really dealing with them ok. - could this be causign the usb problem (or >> even 20080826 kernel's wrong image error for some reason) ? >> > > Well the next thing I was going to say was, I can imagine only a few > scenarios: > > - Bad flash procedure > - Bad image > - Bad hardware > > If you are doing everything by the book and your images aren't corrupt, it > does sound like your flash is fubar. You haven't showed any commands or output > during your flashing procedures so it is still really hard to tell. > > Sarton > > ___ > 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: Problem with usb cable: device descriptor read/64, error -110
Please, refer to this http://n2.nabble.com/Can-bad-NAND-blocks-cause-USB%27s-%22device-descriptor-read-64%2C-error--110%22---tp835094p835094.html for more full info. A guy in #openmoko suggested my flash blocks might be bad and fs not really dealing with them ok. - could this be causign the usb problem (or even 20080826 kernel's wrong image error for some reason) ? -- sledge Sarton O'Brien rašė: > On Wednesday 03 September 2008 02:49:58 sledgeas wrote: > >> I am having the same problem as Kevin once had, now. I have immed >> reflashed my FR's om2007 with 2008 and kernel: >> tried these: >> from openmoko2008 update site: >> Om2008.8-gta02-20080826.uImage.bin - this one says bad kernel image >> these combinations work, (but the usb error is still there, error -110): >> Om2008.8-gta02-20080831.rootfs.jffs2 >> testing-om-gta02-20080831.uImage.bin >> testing-om-gta02-20080902.uImage.bin >> gta02v5_and_up-u-boot.bin (Aug 26th) >> > > OK, so it looks like you've tried a few combinations. It's still really hard > to tell if you have used the right combination though and where the images > actually came from. > > You should be using images from here: > > http://downloads.openmoko.org/releases/Om2008.8-update/ > > And from nowhere else (at least until you have something working). > > If using those images doesn't work then it's sounding like some kinda hardware > fault. > > Good luck! > > Sarton > > ___ > 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: Problem with usb cable: device descriptor read/64, error -110
> > If using those images doesn't work then it's sounding like some kinda hardware > fault. > > Good luck! > 8( -- sledge Sarton O'Brien rašė: > On Wednesday 03 September 2008 02:49:58 sledgeas wrote: > >> I am having the same problem as Kevin once had, now. I have immed >> reflashed my FR's om2007 with 2008 and kernel: >> tried these: >> from openmoko2008 update site: >> Om2008.8-gta02-20080826.uImage.bin - this one says bad kernel image >> these combinations work, (but the usb error is still there, error -110): >> Om2008.8-gta02-20080831.rootfs.jffs2 >> testing-om-gta02-20080831.uImage.bin >> testing-om-gta02-20080902.uImage.bin >> gta02v5_and_up-u-boot.bin (Aug 26th) >> > > OK, so it looks like you've tried a few combinations. It's still really hard > to tell if you have used the right combination though and where the images > actually came from. > > You should be using images from here: > > http://downloads.openmoko.org/releases/Om2008.8-update/ > > And from nowhere else (at least until you have something working). > > Sarton > > ___ > 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: Problem with usb cable: device descriptor read/64, error -110
Thanks for the answer, but referring to my next email (yes, I have tried to use the correct kernel): > from openmoko2008 update site: > Om2008.8-gta02-20080826.uImage.bin - this one says bad kernel image The exact error of NOR and NAND (when using 20080826 kernel and 20080831 or 20080901-2 rootfs) is: 2097152 bytes read:OK Wrong image format for bootm command ERROR: can't get kernel image! That's what's my situation is about. -- sledge Sarton O'Brien rašė: > On Wednesday 03 September 2008 01:35:50 sledgeas wrote: > >> Hello, >> >> I am getting same error. I got my FR last week. I reflashed om2007 with >> 2008.8 using: >> >> Om2008.8-gta02-20080831.rootfs.jffs2 >> gta02v5_and_up-u-boot.bin >> testing-om-gta02-20080831.uImage.bin >> > > You're using a testing kernel. You can't ever expect the test kernel and > stable userland to match. They _may_ match but it's up to you to find out the > hard way :) > > Try flashing the correct kernel/uImage. > > Sarton > > ___ > 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: Problem with usb cable: device descriptor read/64, error -110
Hi everyone, I am having the same problem as Kevin once had, now. I have immed reflashed my FR's om2007 with 2008 and kernel: tried these: from openmoko2008 update site: Om2008.8-gta02-20080826.uImage.bin - this one says bad kernel image these combinations work, (but the usb error is still there, error -110): Om2008.8-gta02-20080831.rootfs.jffs2 testing-om-gta02-20080831.uImage.bin testing-om-gta02-20080902.uImage.bin gta02v5_and_up-u-boot.bin (Aug 26th) Tried various ways (booting with/without usb cable, plugging it later etc.), re-inserting uhci_hcd etc. cdc_ether and usbnet compiled as modules too. inserted (maually). this comes up though only when i keep pressing power button in ASU (not too long thouth, of course :)) usb 6-1: new full speed USB device using uhci_hcd and address 21 usb 6-1: device descriptor read/64, error -110 though with the newest (today's) kernel it appears: usb 6-1: device descriptor read/64, error -84 Thanks huge! Keep up the great work! -- sledge Kevin Zuber rašė: > Hi Community, > > After a few days not using the usb cable and an opkg update and an > system update (Ubuntu with Kernel 2.6.24-20), the cable doesn't work > anymore. > > Dmesg says: > > [ 211.983257] usb 1-1: new full speed USB device using uhci_hcd and > address 2 > [ 227.081309] usb 1-1: device descriptor read/64, error -110 > [ 242.288201] usb 1-1: device descriptor read/64, error -110 > [ 242.502543] usb 1-1: new full speed USB device using uhci_hcd and > address 3 > [ 257.600058] usb 1-1: device descriptor read/64, error -110 > [ 272.800497] usb 1-1: device descriptor read/64, error -110 > [ 273.016294] usb 1-1: new full speed USB device using uhci_hcd and > address 4 > > I double checked it with another computer with an older system (Ubuntu > 7.10 and 8.04 without updates), but the same again. > > So it should be the cable (hardware defect?) oder the neo update (using > 2007.2 with latest updates). > Did I miss something, any other ideas? Has someone this problems, too? > > It also seems, that the neo isn't charging anymore when it is connected > to the cable. The usb power supply is still working fine and can charge > the neo. > > Thanks a lot for your answer! > > Kevin > > > ___ > 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: Problem with usb cable: device descriptor read/64, error -110
Hello, I am getting same error. I got my FR last week. I reflashed om2007 with 2008.8 using: Om2008.8-gta02-20080831.rootfs.jffs2 gta02v5_and_up-u-boot.bin testing-om-gta02-20080831.uImage.bin Ask me for further details. thanks huge! S. Kevin Zuber rašė: > Hi Community, > > After a few days not using the usb cable and an opkg update and an > system update (Ubuntu with Kernel 2.6.24-20), the cable doesn't work > anymore. > > Dmesg says: > > [ 211.983257] usb 1-1: new full speed USB device using uhci_hcd and > address 2 > [ 227.081309] usb 1-1: device descriptor read/64, error -110 > [ 242.288201] usb 1-1: device descriptor read/64, error -110 > [ 242.502543] usb 1-1: new full speed USB device using uhci_hcd and > address 3 > [ 257.600058] usb 1-1: device descriptor read/64, error -110 > [ 272.800497] usb 1-1: device descriptor read/64, error -110 > [ 273.016294] usb 1-1: new full speed USB device using uhci_hcd and > address 4 > > I double checked it with another computer with an older system (Ubuntu > 7.10 and 8.04 without updates), but the same again. > > So it should be the cable (hardware defect?) oder the neo update (using > 2007.2 with latest updates). > Did I miss something, any other ideas? Has someone this problems, too? > > It also seems, that the neo isn't charging anymore when it is connected > to the cable. The usb power supply is still working fine and can charge > the neo. > > Thanks a lot for your answer! > > Kevin > > > ___ > 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
