Re: Neo due-2 - NG - last chance
Robin Paulson wrote: > > 2008/12/12 GreyCardinal : >> How? >> Please write steps >> >> r...@om-gta02:~# ls /sys/class/backlight/pcf50633-bl/brightness * >> /sys/class/backlight/pcf50633-bl/brightness > > it's a text file; try: > > vi /sys/class/backlight/pcf50633-bl/brightness > > assuming you have vi installed > > if you don't know already how to use vi, you might want a vi manual to > hand before starting > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > r...@om-gta02:~# cat /sys/class/backlight/pcf50633-bl/brightness 63 -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1644925.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
2008/12/12 GreyCardinal : > How? > Please write steps > > r...@om-gta02:~# ls /sys/class/backlight/pcf50633-bl/brightness * > /sys/class/backlight/pcf50633-bl/brightness it's a text file; try: vi /sys/class/backlight/pcf50633-bl/brightness assuming you have vi installed if you don't know already how to use vi, you might want a vi manual to hand before starting ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
j newkirk wrote: > > > How? Please write steps r...@om-gta02:~# ls /sys/class/backlight/pcf50633-bl/brightness * /sys/class/backlight/pcf50633-bl/brightness Applications: AlarmServer Qtopia qtmail Settings: PluginManager.conf.lock packages: picssounds r...@om-gta02:~# -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1644575.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
On Tue, 9 Dec 2008 11:31:51 -0800 (PST), GreyCardinal <[EMAIL PROTECTED]> wrote: > > No more ideas? > -- > View this message in context: > http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1635415.html > Sent from the Openmoko Support mailing list archive at Nabble.com. While SSH'd into the blank FR, take a look in /sys/class/backlight/ and see what brightness is set to, and try to echo a different value to it. If it shows brightness already set to 100 or something and your display is unlighted I'd say it's likely your backlight is done, talk to OM or distributor about warranty. If you have no backlight when you boot up to NOR bootrom I'd say it's pretty certain already, but if you can SSH in and poke at the settings you can more readily assure yourself of that. Sorry I don't have more or better to offer, but I honestly think you're hit with a backlight failure at the hardware level. j -- Joel Newkirk http://jthinks.com (blog) http://newkirk.us/om (FR stuff) ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
No more ideas? -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1635415.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | How about the NOR U-Boot, this has been quite reliable in bringing up | backlight in my experience? What happens with backlight if you hold | down AUX during powerup to get into NOR U-Boot? | When I'm booting to NOR U-Boot my FreeRunner is available with | USB(dfu-util), but the screen is black — no backlight and not text (i am use | paltop with damage backlight - know ). I blew up the backlight regulator on a GTA02 A5 here by hotplugging the LCM connector... the flat cable has a 2 layer set of terminating pads on it and it trashed the LED regulator on the PMU. But if you didn't even open the case I dunno what makes the problem, I never saw the regulator have trouble without me causing it. The LCD flex cable is held in place by some sticky EMI tape so I doubt it moved. NOR flash code should definitely start the LED regulator up without any question. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk9dPoACgkQOjLpvpq7dMoRxACfSARykgE2OhlPIbqYDcazdvjl STUAn0lpVCzNKSizhmER6kD0/29yh7bi =B1f6 -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
Andy Green wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > > | Then I've tried with Om 2008.9. After flashing it to FreeRunner I've > got it > | working by SSH. But the display was still empty (black and no light, I > | mean). > | > | What can I do to understand where's the problem? Maybe, the reason is in > | some contacts? I've not unsealed the device. No accidents with > FreeRunner > | happened either. > > How about the NOR U-Boot, this has been quite reliable in bringing up > backlight in my experience? What happens with backlight if you hold > down AUX during powerup to get into NOR U-Boot? > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAkk9cBYACgkQOjLpvpq7dMpL7gCeKvl0LEl/+cyLlusfbbK/x6eZ > Yc8Ani8i+dntk1f6CIg15IwYeqK2QUK3 > =HYs5 > -END PGP SIGNATURE- > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > When I'm booting to NOR U-Boot my FreeRunner is available with USB(dfu-util), but the screen is black — no backlight and not text (i am use paltop with damage backlight - know ). -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1630462.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Then I've tried with Om 2008.9. After flashing it to FreeRunner I've got it | working by SSH. But the display was still empty (black and no light, I | mean). | | What can I do to understand where's the problem? Maybe, the reason is in | some contacts? I've not unsealed the device. No accidents with FreeRunner | happened either. How about the NOR U-Boot, this has been quite reliable in bringing up backlight in my experience? What happens with backlight if you hold down AUX during powerup to get into NOR U-Boot? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkk9cBYACgkQOjLpvpq7dMpL7gCeKvl0LEl/+cyLlusfbbK/x6eZ Yc8Ani8i+dntk1f6CIg15IwYeqK2QUK3 =HYs5 -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Neo due-2 - NG - last chance
Sorry for my English. Now, I'm trying to repeat my problem in a more appropriate manner. My device is Neo FreeRunner GTA02v5 (DateCode: 20080618). I've got it in August and have been playing with it for a few months. I've tested a lot of distributions (from Om 2008 to FDOM, Qt Extended and Debian). Also, I've flashed the boot loader (uboot) many times -- I was trying to get my 8 Gb card working (this card was okay but slow when I was booting from the internal flash). So, after yet another loading the FDOM distribution to the internal flash my FreeRunner seemed to be okay but became unreachable by SSH. After that, I left my device and the battery discharged. The next booting showed me a black screen. I thought the reason was in discharged battery and changed it to the additional one. That didn't seem to help. Okay, I've started making some experiments: I've flashed the special uboot patched for a discharged battery -- FreeRunner blinked with its light. After that, my device could be connected by USB but there was nothing on its screen. No light, no image. Then I've tried with Om 2008.9. After flashing it to FreeRunner I've got it working by SSH. But the display was still empty (black and no light, I mean). What can I do to understand where's the problem? Maybe, the reason is in some contacts? I've not unsealed the device. No accidents with FreeRunner happened either. -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1630257.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
