Acer 3400LMI manual Dynamic routine

Page 31

F8­x86_64 on the Acer Ferrari 3400LMi

#Bluetooth address of the phone device 00:0A:D9:E9:D8:4F;

#RFCOMM channel for the Dial Up Networking service channel 4;

#Description of the connection

comment "Modem on my phone";

}

13.2.4 Dynamic routine

If the method above works, you are all set and done. I started out that way and everything worked great for a while. Then all of a sudden I was unable to connect. It turned out that the DUN channel on my phone had changed!?! Instead of 4 as in the example above it showed up as channel 2, and later on as channel 3...

The statical configuration done by editing the rfcomm.conf file cannot handle this confusion. Instead I needed to dynamically decide which channel my phone used for the DUN service today and bind to it.

This is done in a simple shell script, that is called just before I intend to connect. Personally, I use Kppp and find it great for both modem­to­modem dial­ups and GPRS connections. So, I have configured KDE to call my script just before Kppp is opened.

First I was a bit suspicious about this method to work all the time, but I have not had any trouble this far and I have been using it for years now. You may find a printout of the script in Appendix C, or download it from http://ferrari.databa.se/3400/f8/dun­bind.sh. Obviously, you will need to change the name of the bluetooth device, BTNAME, and maybe the port to connect it to, RFPORT. Once that is done you may test run it:

#wget http://ferrari.databa.se/3400/f8/dun­bind.sh

#chmod +x dun­bind.sh

#./dun­bind.sh

Checking

for local Bluetooth device...

[

OK

]

Checking

that

/dev/rfcomm1 is free...

[

OK

]

Searching for

remote Bluetooth device S­Gs P900...

[

OK

]

Searching for

Dial Up Networking service...

[

OK

]

Binding /dev/rfcomm1 to DUN channel 3...

[

OK

]

# rfcomm

­a

 

 

 

 

rfcomm1:

00:0A:D9:E9:D8:4F channel 3 clean

 

 

 

Now all you need to do when you want to use your phone as a modem are the most basic steps:

Turn on bluetooth on your phone

Turn on the bluetooth hardware on your laptop Dial!

31

Image 31
Contents F8-x8664 on the Acer Ferrari 3400LMi Table of ContentsF8­x8664 on the Acer Ferrari 3400LMi Version IntroductionQuick reference guide Hardware Status Details Disk size InstallationGraphical installer Potential pitfallsHard drive Ieee 1394 FirewireUpgrading the drive # time cp ­rp /media/ieee1394disk/430MBfolder ~ Potential problemsComments Configuring FirewirePC-card In-1 Card readerSpecial keys & buttons Key-codes Configuration procedureScan-codes Button Key-code Default X key symbolsLinux key-codes WWW Key-codes revisited= XF86WWW CPU & Acpi support Configure actionsBasics GraphicsSuspend CPU frequency scalingDual-Head Simple configurationRadeon driver # xrandr ­q Screen 0 minimum Virtual screen sizeFn-F5 button Xrandr tool10.3 3D acceleration Optimization Simple benchmarkOther observations Initialization TV-outLoad detection Ntsc or PALTouch-pad Wireless NICWlan tools Installing WlanWlan firmware Manual way Get started with WlanEssid # iwconfig wlan0 essid Perspektiv Verify installation BluetoothGUI way UP Running Pscan Using a phone modemPrepare the laptop Prepare the phoneObex File Transfer 0x1106 Protocol Descriptor List Short explanation of the command above Static configurationDynamic routine AT+CGDATA=PPP,1 GprsMouse & keyboard KBluetoothInstallation Sending filesScan for devices Mouse & keyboardLock screen Infrared Configuring IrDATransfer files DMA IRQModem Testing IrDAInstalling daemon SLMODEMDDEVICE= SLMODEMDCOUNTRY=SWEDENConnecting Potential issueDisconnecting System hang ReferencesF8­x8664 on the Acer Ferrari 3400LMi Appendix a /etc/X11/xorg.conf XAA INTERNAL=LVDS Appendix B dual­head.shNtsc ACTION=$1­$DEFAULTACTION CURNDX=$CURNDX­$INTNDX CURRENT=$ALLOUT$CURNDX Lvds NEXT=$CURRENT LVDS+VGA­0Internal internal Tvout Usage Esac Appendix C dun­bind.sh F8­x8664 on the Acer Ferrari 3400LMi RETVAL=0 $CONFIGSLMODEMDOPTS=$SLMODEMDOPTS $SLMODEMDDEVICE RETVAL=$? F8­x8664 on the Acer Ferrari 3400LMi