O2 Joggler Forum

Posted: **Wed May 11, 2011 10:55 pm**

I have a joggler that I 'bricked' after doing some hacking on the efi. I was shooting for a new boot logo, but got it wrong, apparently.

Anyway, I decided to acquire another unit to un-brick my first. I also picked up a couple spare efi chips so that I could tinker with them safely. I received the new (used) joggler a couple days ago and I was able to successfully flash my corrupt efi chip and my spares.

Sounds good, right? Not quite.

The original unit now boots successfully, as I can hear the boot sound from the stock os and I can log in via telnet. However, the screen never turns on. Not even the backlight comes on at any point. My initial thought was that I broke the screen, somehow. But that was not the case, as I could hook up the screen from the original to the new one and it worked fine. Then I hooked up the screen from the new one to the original board and no dice. So, I have two working screens.

Is it possible that the lvds connector on the board is bad? I may have attempted to insert the cable backwards at one point, but it seemed harmless enough.

A software problem seems unlikely. I'm not sure what to check next. Any suggestions?

Posted: **Thu May 12, 2011 12:17 pm**

have you got xset installed?

if so, what does xset q show?

Posted: **Thu May 12, 2011 8:54 pm**

I was running stock os, which did not have xset installed. So I loaded Ubuntu Natty to try this out.

Code: Select all

joggler@joggler:~$ xset q
Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    off    02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  500    repeat rate:  30
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  0    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  600    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0    WhitePixel:  16777215
Font Path:
  /usr/share/fonts/X11/misc,/usr/share/fonts/X11/Type1,/var/lib/defoma/x-ttcidfo                                             nt-conf.d/dirs/TrueType,built-ins
DPMS (Energy Star):
  Standby: 0    Suspend: 0    Off: 0
  DPMS is Enabled
  Monitor is On

Display is, of course, still off.

Thanks for looking at this.

Posted: **Thu May 12, 2011 9:02 pm**

Also, the touchscreen is still responding, even though the screen is off.

Posted: **Thu May 12, 2011 9:59 pm**

buckle wrote:Also, the touchscreen is still responding, even though the screen is off.

please stick output from
xrandr --verbose
on pastebin or similar.

Posted: **Sat May 14, 2011 1:35 am**

results from xrandr --verbose

http://pastebin.com/7ppExD5d

Posted: **Sun May 15, 2011 5:40 pm**

I shined a flashlight towards the screen and I can see the image. So, I guess I have a backlight issue.

As I mentioned previously, the screen works on another joggler. So, the backlight itself is fine.

I guess maybe it is not getting power to the backlight?? What else could be going on here?

Posted: **Tue Jun 14, 2011 3:56 pm**

Any ideas?

Posted: **Tue Jun 14, 2011 4:30 pm**

sounds like the connector got damaged and as you say the light isn't working.

O2 Joggler Forum

Joggler running blind

Joggler running blind

Re: Joggler running blind

Re: Joggler running blind

Re: Joggler running blind

Re: Joggler running blind

Re: Joggler running blind

Re: Joggler running blind

Re: Joggler running blind

Re: Joggler running blind