View Single Post
tzsm98's Avatar
Posts: 500 | Thanked: 437 times | Joined on Nov 2009 @ Oklahoma
#17
Originally Posted by RockCreek1 View Post
Hi
I have a similar problem. Joikuspot worked fine prior to the recent n900 update. It also seemed to work fine, though took a few tries to connect, during the interlude between my downloading the recent N900 update and the most recent Joiku update. I am just a regular N900 user and I do not want to mess around with root, etc. Nor do I think I should be required to do so for something I paid for. So I wonder if there is another way to deal with this problem. My compter indicates that I am connected to Joiku with an excellent signal. Thanks in advance for your help.
I've suggested to JoikuShop that they add a subroutine that detects which kernel is active and to have the code lines as part of the startup-shut down routines of the application. I also tried using QueenBee to handle the code but that didn't work.

Until JoikuShop takes my advice messing around in root to the extent this fix requires means having to be extra careful about typing and reviewing what you've typed before hitting the 'enter' key. You:
  • open xterm
  • type sudo gainroot 'enter'
  • type modprobe JoikuSpot_Bouncer 'enter'
  • close x-term
Case sensitive so be sure to watch for the capital letters. After you are done with JS:
  • open xterm
  • type sudo gainroot 'enter'
  • type modprobe -r JoikuSpot_Bouncer 'enter'
  • close x-term


Practice typing it in a note program or Conboy to build your confidence. I wish I could cut and paste from my note program to x-term but that doesn't seem to be possible. I'm kinda, sorta fearless when it comes to entering short pieces of code. The longer scripts are what scare me off. I'm too awful of a typist.
__________________
A Thing of Beauty Is a Joy Forever
 

The Following User Says Thank You to tzsm98 For This Useful Post: