Search results

  1. aTc

    (Re-)building firmare 1.60

    that's the easy bit, after that it starts to fail on m4, perl, intltool and a lot of fetches currently waitng for the dsp crap to download from ti, the recipe can't download them, and ti has them stored on the slowest server on the planet behind a big "im not a terrorist" form you have to fill...
  2. aTc

    (Re-)building firmare 1.60

    Actually, it's been quite a while since i even tried to build the old firmware, i'll see how far i'll get :)
  3. aTc

    (Re-)building firmare 1.60

    *sigh* indeed If you can't even get that part going, just give up. afaik there is currently only 1 place in the world where that firmware can be built, and that is on ED's server. This isn't your "normal" OE tree, this is a badly hacked up, barely working disaster. About the only way of...
  4. aTc

    (Re-)building firmare 1.60

    Trying to build the old firmware will give you even more problems. A lot of the recipes want to download sources from places that don't exist anymore, and some just fail to build completely because of some fun dependency problems that crept in. (i think it was something to do with recipes not...
  5. aTc

    .next 2013.06

    Yes. i pushed all the changes to the master branch, your patches are included
  6. aTc

    .next 2013.06

    screen going black is probably related to the  omapdss MANAGER error: dispc_ovl_setup failed for ovl 0 error message in dmesg trying to run the networkmanager gui from the tray seems to trigger it too
  7. aTc

    .next 2013.06

    Angstrom moved their master branch to 2013.06 a few days ago, and after some messing about I made a somewhat working image from it. http://next.openpandora.org/v2013.06/images/openpandora/Angstrom-OP-XFCE-NetworkManager-image-eglibc-ipk-v2013.06-openpandora.rootfs.tar.xz Installation is the...
  8. aTc

    .next alpha image

    I haven't really worked on it that much, so it's still at the stage where it really just needs one big final push and it's ready. The core of the image works, its just some final configuration changes to make everything work smoothly. Unfortunately there's quite a lot of those. and I don't...
  9. aTc

    .next alpha image

    you do it by rtfm
  10. aTc

    .next alpha image

    This only happens on mine very very rarely, and usually only when i was doing some serious messing about, so i didn't really bother to investigate deeper. Does this happen every time you reboot ? And does it also happen when you run "sudo systemctl poweroff" instead of going through the menu ...
  11. aTc

    .next alpha image

    It wasn't really a "big" update, it's just that the package manager doesn't really handle files that are set up by the first-run-wizard, or config files in the users home dir.
  12. aTc

    .next alpha image

    At least that confirms it really is the calibration, i have no idea why it would cause the rest of the script to fail when its run at the start. The older script used to run it at the end, and it didn't cause any visible problems there, not does it on the zaxxon firmware.
  13. aTc

    .next alpha image

    I think it has to do with the touchscreen calibration, if you skip that, it should be fine.
  14. aTc

    .next alpha image

    There's only one file in there that could really be the image, but i've changed the link in the first post to be the image itself instead of the dir that contains it. Other than that there aren't really much more details needed other than extracting it to sd, and booting it in the pandora...
  15. aTc

    .next alpha image

    sebt3 seems to have some problems with the gles stuff on his rebirth pandora. Can anyone confirm if gles works or not on pandoras with an /etc/powervr-esrev other than 2 ? (which should be the rebirth and 1ghz versions) Easiest way to test is probably...
  16. aTc

    .next alpha image

    the wifi led is set to blink on activity, i found that slightly more usefull than a static led that showed the same thing as the nm-applet.
  17. aTc

    .next alpha image

    No easy solution for that unfortunately. A lot of pnds segfault on .next. I think it's caused by the pnd having versions of libs in it that clash with the ones in .next itself. If you look through the logs even things like a "cp" that the pnd runs to copy some files around segfaults. But...
  18. aTc

    .next alpha image

    I don't have an otg adapter here, so I can't test it myself. Reading through the wiki and some forums posts, it's most likely because the g_cdc kernel module isn't loaded. You could try doing a "sudo modprobe g_cdc" , and then plugging in the otg stuff.
  19. aTc

    .next alpha image

    I've made some changes to the various recipes, and things now seem to work. At least good enough to run the Jedi Knight 3 demo. The pnd itself segfaults all over the place, probably because its including a lot of libs that already have versions in the firmware itself, but the thing works when...
  20. aTc

    .next alpha image

    all the different versions of libgles should already be on there. I did get it somewhat going by copying the pvr-init script and /etc/powervr.ini from the old firmware. One of the reasons it doesn't work is because in powervr.ini it tries to use X11 versions of the lib, and you need one of the...
Back
Top