Results 1 to 18 of 18
  1.    #1  
    I have Terminal and Terminus installed on my Verizon Pre Plus with webOS 1.4.5 - today I noticed this article On-device Command Line access returns to webOS 2.1, after a slight tweak | PreCentral.net | The #1 Palm Pre and Pixi Community talking about Terminus finally bringing command line access back to 2.x devices.

    This is great - but Terminus doesn't seem to work on my 1.4.5 device at all. What I get is a black screen with a block cursor and then nada. I can't type and I can do anything in that window. I can reduce it to a card and I don't lock my device up - but as far as what it is designed for - nada.

    Thoughts?

    If you have 1.4.5 and this is working (or not) for you would you let me know?
  2. #2  
    Did you try to get any error messages via "tail -f /var/log/messsages" (novaterm)?

    I never used Terminus on 1.4.5, only now because it's the only one working for 2.x
  3.    #3  
    I can try that. I setup Lumberjack to show the log in realtime for "everything" and when I launched Terminus all looked OK except for these errors but most seem unrelated to me. I colored in red the two that seem a little more confusing:

    [2011-03-15 19:08:31] (LunaSysMgr) user.crit: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file
    [2011-03-15 19:08:32] (LunaSysMgr) user.crit: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file
    [2011-03-15 19:08:33] (kernel) kern.err: [30238.020000] cy8mrln: Scan timed out
    [2011-03-15 19:08:34] (LunaSysMgr) user.crit: static gboolean PIpcChannel::nestedLoopTimeoutCallback(void*): Synchronous call timed out
    [2011-03-15 19:08:34] (LunaSysMgr) user.crit: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file
    [2011-03-15 19:08:46] (LunaSysMgr) user.crit: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file
    [2011-03-15 19:08:48] (LunaSysMgr) user.crit: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file
    [2011-03-15 19:08:48] (LunaSysMgr) user.crit: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file


    BTW - I'm running F102A but this problem predates my using anything but the default palm kernel.
  4. #4  
    Open Terminus again and look if the colored error messages come up again.
  5.    #5  
    Lucky me... the next two times I launched Terminus I got not ONE but TWO black screens and only one of these turned into the box with the block cursor. If I tossed away the first box the second went with it.

    Then fun fun fun... my system restarted (Luna) on the second one while I was using Lumberjack to view the logs.
  6.    #6  
    I am going to have to restart my device. Now every time I start Terminus it is crashing. Due to the speed of recovery (palm logo appears, less than a minute later I have a working launcher) I suspect it's just a luna restart and lumberjack seemed to confirm that.

    After restart I will try again... I don't think the phone liked what I was trying. I was trying to mark the log with "copy from here" in the follow log model and then I was going to mark with a "to here" to capture all that happened during the Terminus launch. I'm not sure that's Kosher with Lumberjack.
  7. #7  
    -> novaterm/SSH: tail -f /var/log/messages
  8.    #8  
    While I wait during the restart I had emailed a copy of the log from the crash to myself. I think this starts about the time I started Terminus as seen from the fact that Lumberjack was just brought up:

    2011-03-15 19:20:44] (upstart) daemon.info: (30848/947854913) org.webosinternals.lumberjack state changed from spawned to post-start
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/948251642) org.webosinternals.lumberjack state changed from post-start to running
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/948617853) Handling started event
    [2011-03-15 19:20:44] (upstart) daemon.warning: (30848/949289240) LunaSysMgr main process (1273) killed by SEGV signal
    [2011-03-15 19:20:44] (upstart) daemon.warning: (30848/951517023) LunaSysMgr main process ended, respawning
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/952096857) LunaSysMgr state changed from running to stopping
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/952920831) Handling stopping event
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/953470148) LunaSysMgr state changed from stopping to killed
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/956003107) LunaSysMgr state changed from killed to post-stop
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/956766046) LunaSysMgr state changed from post-stop to starting
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/957223810) Handling starting event
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/957651056) LunaSysMgr state changed from starting to pre-start
    [2011-03-15 19:20:44] (hidd) user.err: HiddEventIpc.c:440 : _SendEvent: Connection refused [Errors since last msg: 1]
    [2011-03-15 19:20:44] (pubsubservice) user.err: [cancelFunction: 306]: Headless app crashed?
    [2011-03-15 19:20:44] (upstart) daemon.info: (30848/992807306) Active LunaSysMgr pre-start process (6788)
    [2011-03-15 19:20:44] (audiod) user.warning: _keyServerStatus: lost connection to key server
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/26468195) LunaSysMgr pre-start process (6788) exited normally
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/27139581) LunaSysMgr state changed from pre-start to spawned
    [2011-03-15 19:20:44] (LibpurpleAdapter) user.info: Disabling server queue
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/59488214) Active LunaSysMgr main process (6791)
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/64920343) LunaSysMgr state changed from spawned to post-start
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/71329034) LunaSysMgr state changed from post-start to running
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/72702325) Handling started event
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/77157892) CustomizationService goal changed from stop to start
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/89029230) CustomizationService state changed from waiting to starting
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/89761652) firstuse-override goal changed from stop to start
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/90707697) firstuse-override state changed from waiting to starting
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/91104425) Handling starting event
    [2011-03-15 19:20:44] (upstart) daemon.info: (30849/91531671) Handling starting event
  9.    #9  
    Device Restart has not improved things. Each time I run Terminus (after having launched Lumberjack and stopped it this time BTW) it crashes LUNA.

    I'm not holding my mouth right am I?
  10.    #10  
    OK - no difference Still crashed even with use of novaterm rather than lumberjack.

    I'm restarting device again just in case lumberjack / terminus is fatal - this time I'll only use novaterm and not lumberjack before starting terminus.


    Oddly this app never crashed - just never did anything prior to trying to debug it.
  11.    #11  
    running novaterm I was able to tail the logs during the launch of Terminus. I did NOT run lumberjack at all after restarting my device. This time the app launched but did not proceed beyond the dead block cursor state mentioned before.

    I'm still looking at the logs trying to get something to post here but with certainty I can say this:

    1) Lumberjack before Terminus ON MY DEVICE (PrePlus with F102A at 500mhz due to battery charger attached) seems to cause an issue that crashes Terminus which then takes down LUNA.

    EDIT: Maybe not... See next message...

    2) Terminus will not start on my device to a condition that is useful. Even when it doesn't crash it doesn't do anything useful for me.
    Last edited by Unclevanya; 03/15/2011 at 03:33 PM.
  12.    #12  
    Restarted Device. Device still crashed on start of Terminus. I didn't think about it but when I used it earlier I was on a 1A charger and F102A was running at 500mhz. When I was on the USB side I actually slowed it down to 500 with Govnah and didn't think to do that this time.

    Now I'm wondering if this interacts with F102A - I'm going to revert to Palm default and retest after verifying this behavior a few more times.
  13.    #13  
    I'm still getting crashes so I'm posting this to see if anyone can help...

    App Startup:
    2011-03-15T20:46:09.580749Z [283] palm-webos-device user.debug jailer[2244]: findUser start
    2011-03-15T20:46:09.595520Z [283] palm-webos-device user.debug jailer[2244]: APPDIR: /media/cryptofs/apps/usr/palm/applications
    2011-03-15T20:46:09.596649Z [283] palm-webos-device user.debug jailer[2244]: JAILDIR: /var/palm/jail/us.ryanhope.terminus
    2011-03-15T20:46:09.605255Z [283] palm-webos-device user.info jailer[2244]: us.ryanhope.terminus entering game jail
    2011-03-15T20:46:09.605987Z [283] palm-webos-device user.info jailer[2244]: Enter jail us.ryanhope.terminus

    ...a bunch of normal jailer output with chmod's chown's chroot ...

    Three of these:
    2011-03-15T20:46:11.329711Z [285] palm-webos-device user.crit LunaSysMgr: {LunaSysMgr}: virtual void HostArmCastle::turboMode(bool): Failed to open cpu scaling sys file

    Then these:
    2011-03-15T20:46:21.317230Z [295] palm-webos-device kern.warning kernel: [ 295.080000] Alignment trap: LunaSysMgr (1618) PC=0x35de9104 Instr=0xe5034110 Address=0xbbadbeef FSR 0x801
    2011-03-15T20:46:21.388641Z [295] palm-webos-device user.crit LunaSysMgr: {LunaSysMgr}: retVal from message.c:Could not append paylod to reply message.
    2011-03-15T20:46:21.485046Z [295] palm-webos-device kern.warning kernel: [ 295.240000] Alignment trap: LunaSysMgr (1618) PC=0x35de9104 Instr=0xe5034110 Address=0xbbadbeef FSR 0x801

    And this:
    2011-03-15T20:46:21.537475Z [295] palm-webos-device user.err hidd: HiddEventIpc.c:440 : _SendEvent: Connection refused [Errors since last msg: 0]
    2011-03-15T20:46:21.555419Z [295] palm-webos-device user.err PmBtEngine: {PmBtEngine}: *****ERROR:[GAP-API]: SysMgrNotifnCallback: Error getting finished value
    2011-03-15T20:46:21.559631Z [295] palm-webos-device user.err pubsubservice: [bootStatusResponse: 935]: Couldnt find finished? {"serviceName":"com.palm.systemmanager","returnValue":false,"errorCode":-1,"errorText":"com.palm.systemmanager is not running."}


    Followed by all of this culminating in LUNA stopping:
    2011-03-15T20:46:21.560028Z [295] palm-webos-device user.err pubsubservice: [bootStatusResponse: 955]: bootStatusResponse failed. {"serviceName":"com.palm.systemmanager","returnValue":false,"errorCode":-1,"errorText":"com.palm.systemmanager is not running."}
    2011-03-15T20:46:21.593627Z [295] palm-webos-device daemon.warning upstart: (00295/354359130) LunaSysMgr main process (1269) killed by SEGV signal
    2011-03-15T20:46:21.594268Z [295] palm-webos-device daemon.warning upstart: (00295/354847412) LunaSysMgr main process ended, respawning
    2011-03-15T20:46:21.594573Z [295] palm-webos-device daemon.info upstart: (00295/355061035) LunaSysMgr state changed from running to stopping
    2011-03-15T20:46:21.594757Z [295] palm-webos-device daemon.info upstart: (00295/355518798) Handling stopping event
    2011-03-15T20:46:21.594970Z [295] palm-webos-device daemon.info upstart: (00295/355885009) LunaSysMgr state changed from stopping to killed
    2011-03-15T20:46:21.595153Z [295] palm-webos-device daemon.info upstart: (00295/356098632) LunaSysMgr state changed from killed to post-stop
  14.    #14  
    I removed F102A and retested using Palm Default. First run it ran normally (no I didn't have anything connected to look at logs) and then a few seconds after closing I ran again - only to crash LUNA.

    Restarting my device now to see if this "work once only" is repeatable with a longer delay between runs.
  15.    #15  
    No dice - reboot device - still crashes. This app seems to hate my device. This was at 500mhz on stock kernel.
  16.    #16  
    This program and my device seem to be really random with one another. I can get it to come up - to a "block cursor on a black screen" some of the time. Never any further. Any ideas on how to proceed with debugging would be welcomed.
  17. #17  
    Why not use the Terminal app on 1.4.5? I think it has more features and works better.
  18.    #18  
    Quote Originally Posted by pcworld View Post
    Why not use the Terminal app on 1.4.5? I think it has more features and works better.
    LOL - I do. And I will. I am just frustrated and wondering what the problem is and I like a good challenge.

Posting Permissions