Author Topic: AirCable Bluetooth  (Read 4160 times)

yodabob

  • Jr. Member
  • **
  • Posts: 87
    • View Profile
    • http://
AirCable Bluetooth
« on: February 09, 2004, 08:30:11 pm »
I\'m new to Linux (Ok, so shoot me :-))  I\'ve gotten an AirCable bluetooth adaptor for my SL-5600 and was finally able to \"pair\" it with my Motorola 270C Bluetooth cell phone.  Now I\'m supposed to make a modification to a file in  /etc/ppp/peers .  Basically this is a IRDA dial-up profile file which I now need to \"fool\" into thinking the serial port is the IRDA port.  I\'m supposed to do this by adding /dev/ttyS0 as the first line in this \"script\".  I\'ve used File Manager, but can\'t get to it.  I\'ve Terminal, but am told that access ist verboten.  I know next to (I mean really next to) nothing about VI, but I\'m determined not to be beat by this.  Anybody lend a poor novice a hand ?  Since I\'ll never use the IRDA, does anybody have an idea about how I might be able to \"permanently\" make it point to the serial port ?

Thanks !

nilch

  • Hero Member
  • *****
  • Posts: 668
    • View Profile
    • http://
AirCable Bluetooth
« Reply #1 on: February 09, 2004, 10:03:11 pm »
Try downloading QZed from killefiz. It is a great (graphical) editor as a  replacement for those afraid of vi.
and unlike the notepad application, this does now append line breaks unneccesarily.

One you have that (or have the courage to try vi, it is not that hard really, once you remember the key sequences), then just add the line /dev/ttyS0 at the begining of the file (/dev/etc/peers/dialupxxxxxx).

But be warned, whenever you go into the network setting and change anything thuu the interface, the /etc/ppp/peers file will automatically convert back to the IrDA standard and the serial mod line will be erased again.

But once changed and if you dont toucvh the network interface for settings, it will work fine for each connection session.

Note : also pinclude the line \'idle 100\' so connection does not break while the connection is on idle time. 100 maybe modified to suitable value. Add this line at bottom of the same file.

If using vi do the following
vi <filename>
press \"i\" to go into insert mode
type in \'/dev/ttyS0\'     [without quotes]
press \'cancel\' button to give an escape key press
then type   :wq   to save the file and exit from vi


hope that helps
New no more-C1000 / 5000D (sold my 6000 and 750) | Cacko ROM 1.23 on C1000 | 256 MB CF | 2GB PNY SD card | Socket Networker WiFi CF Card | USB Host cable from StreamlineCPUS | Mini Microphone (for voice recording) |

n8a

  • Full Member
  • ***
  • Posts: 235
    • View Profile
    • http://
AirCable Bluetooth
« Reply #2 on: February 09, 2004, 10:05:42 pm »
i dont have the aircable card, but as for modifying the file, id search these forums for some info on vi.  i wrote a little primer a while back, and it is pretty necessary for you to learn the rudimentary commands for vi to truly get the most out of your zaurus.
also, try typing \'su\' and your pword to gain root privs at the cmd line to resolve the \'ist verboten\' issue-- i think thats what you are referring to.
good luck!

n8a

  • Full Member
  • ***
  • Posts: 235
    • View Profile
    • http://
AirCable Bluetooth
« Reply #3 on: February 09, 2004, 10:17:38 pm »
this thread has my comments regarding vi:

http://www.zaurususergroup.com/index.php?n...1158&highlight=

i would have referenced it before, but i was out getting food and didn\'t want to search for it while in line.  it\'s just a little summary of the main commands that you would use in vi.  it\'s handy to know, as it\'s nice to just type $ vi <file> when perusing through the file system.

Just remember, when in doubt: <ESC>:q! to exit without saving!

yodabob

  • Jr. Member
  • **
  • Posts: 87
    • View Profile
    • http://
AirCable Bluetooth
« Reply #4 on: February 10, 2004, 01:48:45 pm »
Thanks folks !  That worked like a charm, vi isn\'t half as bad as I thought.  I edited the file appropriately and added in the required text.  It did have a tendency to time-out, so I went back in and added that last idle parameter and that fixed the problem.  Also, the su (which I presume stands for super user) worked like a charm.

I appreciate the help, thanks again !

zmike

  • Jr. Member
  • **
  • Posts: 77
    • View Profile
    • http://
AirCable Bluetooth
« Reply #5 on: February 10, 2004, 02:30:44 pm »
What is the idle parameter you added? A friend of mine has the same card for his SLC860 and has timeout problems. He resorted to running a background \"ping\" session.
SLC860, Zubuntu, Symbol Spectrum24 Wireless CF, 4GB SD Card

edl867

  • Newbie
  • *
  • Posts: 28
    • View Profile
    • http://
AirCable Bluetooth
« Reply #6 on: February 10, 2004, 05:22:29 pm »
su is \"substitute user\"
it defaults to root unless you tell it another user login.

yodabob

  • Jr. Member
  • **
  • Posts: 87
    • View Profile
    • http://
AirCable Bluetooth
« Reply #7 on: February 12, 2004, 06:08:01 pm »
I used idle 500 which seems to work just fine.  As far as what that actually means, I have no idea, it was suggested to me in the thread above to use idle 100 \"or a suitable value\".