WebOS Internals - User contributions [en]

Patch webOS CPU Frequency or Voltage Scaling

2009-09-05T03:46:40Z

Howard: fix typo

{{template:patch}}
= Overview=
There are currently 2 methods to enable further power saving - neither is perfect. Note that '''these 2 methods CANNOT be used together''' so make sure you try only one solution at a time. Using both has been reported to brick your Pre, requiring a visit to the WebOS Doctor. Patches for these are now available in the gitorious repo. See [[Applying Patches]]

1 CPU Scaling
* This allows the Pre to scale the CPU clock speed up and down in response to changes in CPU utilization. Some people have reported glitching when using scaling when the CPU is under heavy load (lots of multitasking, playing video, etc).
2 SmartReflex
* This allows the Pre to vary the voltage inside the core in response to silicon characteristics, temperature, voltage, etc. This does not save that much power because it is supposed to be used along with CPU scaling to reduce voltage when the CPU is running slower, but the Pre's kernel is missing the modules to do this. This is why using both together will '''freeze''' the Palm Pre. (Remove the battery, restart with the USB plugged into your computer with NovaCom installed, During the phones boot procedure simply telnet to the phone through NovaCom's Proxy port 8023, remove the smartreflex files you installed in the events folder in /etc/ before WebOS panics)

= CPU Scaling=
== Default Setting==
Frequency scaling does not appear to be active by default on the Pre by default. The directory /sys/devices/system/cpu/cpu0/cpufreq contains information on the current state. The clock seems to be fixed at 500mHz for normal operation (according to cpuinfo_cur_freq), however several other frequencies exist:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# cat ./scaling_available_frequencies
600000 550000 500000 250000 125000
</nowiki></pre>
The file /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state shows that at some point (probably during startup) the frequency is raised to 550mHz for a short period of time.

== Enabling Scaling==
It is possible to enable frequency scaling using the 'ondemand' governor:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo ondemand > ./scaling_governor
</nowiki></pre>
this will cause the frequency to be reduced automatically while idle, and increased as needed during operation, potentially increasing battery life. Because higher frequencies may cause overheating, and TI has noted a significant decrease in the life of the processor when running above 500mHz, you should also restrict the frequency scaling to 500mHz and below by doing the following:
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 500000 > ./scaling_max_freq
</nowiki></pre>
If your Pre seems sluggish after enabling scaling, you can try changing the values in /sys/devices/system/cpu/cpu0/cpufreq/ondemand as detailed below.

== 'ondemand' Configuration==
Increasing the value of 'scaling_min_freq' will prevent the CPU from going into extremely low speed configurations, which will significantly improve the responsiveness of the device when it first detects increased CPU usage, at the cost of a little bit of battery life.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq# echo 250000 > ./scaling_min_freq
</nowiki></pre>
Setting the value of 'up_threshold' lower will cause the frequency to be increased at lower levels of activity.
<pre><nowiki>
root@castle:/sys/devices/system/cpu/cpu0/cpufreq/ondemand# echo 30 > ./up_threshold
</nowiki></pre>
Note: The default setting for 'up_threshold' is 80.

== Checking Performance and Stats==
To check how long your Pre has been running and at what frequency, do this:

<pre><nowiki>cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state</nowiki></pre>

You will see something like this:
<pre><nowiki>600000 906
550000 768
500000 380
250000 0
125000 180505</nowiki></pre>

The first number is the CPU frequency, the second is a time interval. In this example, my Pre has spent the most time @ 125mHz, but you can see it shoots up when needed. Note that if you are overclocking, it really doesn't spend much time at 600mHz, so overheating shouldn't be a problem, but you will definitely notice an improvement. These stats are reset after a reboot.

== Overclocking==
Overclocking is not recommended, as TI has reported a significant decrease in the life of the CPU at frequencies about 500mHz. However some users have reported better responsiveness, in addition to running cooler and using less battery while overclocking.

To overclock to the CPU's maximum speed, do:
<pre><nowiki>echo "600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

To put it back, do:
<pre><nowiki>echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq</nowiki></pre>

== Making your changes stick after a reboot==
Create a file called '''cpu-scaling''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# Enables cpu scaling

start on stopped finish
stop on runlevel [!2]

console none

script
echo "500000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "30" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
end script
</nowiki></pre>

== Return to Stock Fixed Frequency==
The simple way is just to remove the '''cpu-scaling''' script from /etc/event.d (if you created it) and reboot. None of these changes are persistent without the "sticky" script shown above.

If you switch back to the 'userspace' governor without rebooting, your frequency could get stuck at a lower setting and the whole system get really bogged down. Here is a quick shell script to help you revert to userspace with the original frequency:

Copy/paste this whole line as one command:
<pre><nowiki>echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ; echo 500000 >/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed </nowiki></pre>
Then confirm the frequency/governor are back the way you want.

== Comments and Caveats==
* "I tried this out but video playback was flickery and horrible. The up_threshold tweak setting to 30 seems to improve it a lot , but it's still flickery a bit. Some people may not be happy."

* "I found that setting the max freq to 600000 with the threshold helps this problem. See relevant warnings above first! I don't really watch video on my Pre, so it's not so big of a deal." -pEEf

* "A lot of people on the Precentral forums (myself included) are experiencing the phone locking up after a while of using this, and need to pull the battery to reset. (On webOS 1.0.3 at least.)"

* "I've been running my phone with scaling for nearly a week now without problems, but I'm not 'overlcocking' so to speak. Any specifics on what might cause the locks? (ok had my first locks tonight while attached to the touchstone, weird it never happened before now (and annoying))" -retry

= SmartReflex=
== Enable SmartReflex==
SmartReflex can be enabled in the VDD1 and VDD2 areas of the OMAP processor by setting two flags under /sys/power
<pre><nowiki>
root@castle:/sys/power# echo -n 1 > ./sr_vdd1_autocomp
root@castle:/sys/power# echo -n 1 > ./sr_vdd2_autocomp
</nowiki></pre>
[http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt This slide deck] has much of the pertinent information about SmartReflex and other power-saving technologies on the OMAP processor. Unfortunately the kernel modules that provide many of the features mentioned in the slide deck are not present on the Pre. This is the main reason that SmartReflex may not save a terribly large amount of power.

== Making your changes stick after a reboot==
To enable SmartReflex, create a file called '''smartreflex''' in /etc/event.d and put this code in it, then reboot.
<pre><nowiki>
# -*- mode: shell-script; -*-
description "SmartReflex"
author "Alex Markson"
version 1.0

start on stopped finish
stop on runlevel [!2]

console none

script

# SmartReflex
# "SmartReflex™ driver allows for auto-compensation of VDD1 and
# VDD2 voltages (around the voltages specified by current OPP)
# by analyzing the silicon characteristics, temperature, voltage etc"
#
# Enable SmartReflex
echo -n 1 > /sys/power/sr_vdd1_autocomp
echo -n 1 > /sys/power/sr_vdd2_autocomp

end script
</nowiki></pre>

If you want to enable overclocking in addition to SmartReflex, add the following JUST BEFORE the '''end script''' line:
<pre><nowiki>
# according to the OEM shell script in /etc/miniboot.sh
# this seems like it needs to be set twice to make sure ?
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
echo 600000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
</nowiki></pre>

== Comments and Caveats==
* "After updating to 1.0.4 my pre would lock up and get really hot using the ONDEMAND cpu scaling method and with smartflex everything running great and battery seems even better than ondemand." -seekis
* "AFter using this for about a week, I find that using SmartReflex causes the Pre to stutter every so often"

= Credits=
* Alex Markson for the SmartReflex find and the script.
* pEEf for numerous discoveries related to cpu scaling.
* sidamos for the info about 'up_threshold'
* garrettwp for the cpu scaling event.d script.
* Jauder Ho for gitorious patches

= Hacking=
There is still a lot of work to be done in making this work optimally. The following are some resources and thoughts.
* A paper about the ondemand governor http://www.linuxinsight.com/ols2006_the_ondemand_governor.html
* webOS 1.0.4 has CONFIG_PREEMPT set along with CONFIG_HZ=100. CONFIG_NO_HZ aka tickless is not set.
* Possible patch for NOHZ / ondemand governor http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-05/msg10436.html
* Use PowerTop to observe what is going on inside the Pre
* http://www.lesswatts.org/
* http://wiki.davincidsp.com/index.php/Running_PowerTOP_on_OMAP35x_platform
* TI 3430 PM presentation http://www.celinux.org/elc08_presentations/TI_OMAP3430_Linux_PM_reference.ppt

USBnet networking setup

2009-09-04T10:46:38Z

Howard: /* On Windows XP */

USBnet allows you to create an IP network over the USB cable. This will allow you to talk to your Pre without WiFi or Bluetooth, and it keeps the battery charged.

This page is a duplicate of [[USBnet Setup]]

== On your rooted Pre==

run

<pre><nowiki>
usbnet enable
</nowiki></pre>

as root and then restart the device as instructed. When it comes back up, run 'ifconfig' and verify you now have a usb0 interface. Mine had the IP of 192.168.0.202. The IP can be changed in /etc/network/interfaces. After a change, bounce the usb0 interface: ifdown usb0; ifup usb0

== Optional Setup to enable DHCP (so you don't have to set the IP address below)==
# Edit /etc/dnsmasq.palm.conf
# Add interface=usb0 below the existing interface line
# Add dhcp-range=192.168.0.11,192.168.0.12,12h below the existing dhcp-range
# Restart the dnsmasq process: stop dnsmasq; start dnsmasq

== On Windows XP==
# Download the driver here: [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre.inf usbnet-pre windows driver(32 bit)] or [http://gitorious.org/webos-internals/usbnet-pre/blobs/raw/master/windows/usbnet-pre-64.inf usbnet-pre windows driver(64 bit)] and save the file to disk as usbnet-pre.inf
# Plug the Pre into your computer. The Add New Hardware Wizard should come up, asking to install an ethernet gadget.
# Follow detailed instructions (screenshots and all) here if you are unfamiliar with installing drivers: [http://docwiki.gumstix.org/index.php/Windows_XP_usbnet Windows XP USBnet install]
# When you finish, you should have a network setup. Goto "Network Connections" via Network Places or the Control Panel
# If you have previously installed Novacom on this machine, bring up Windows Task Manager before proceeding. You may discover a conflict between USBnet and novacomd where the novacomd process will consume lots of CPU and your machine will become very unresponsive. Since you have Task Manager up already, you can easily use it to kill novacomd if this occurs.
# Right-click on the new network, which probably be named Local Area Connection 2
# Select Properties
# Double click on Internet Protocol (TCP/IP)
# Click Advanced
# UNCheck Automatic metric, put 100 in its place. This will keep Windows from attempting to [http://support.microsoft.com/default.aspx/kb/299540 route] traffic over the Pre (it won't work anyway)
# Click OK
# If you did not enable DHCP, you will need to set an IP address manually:
# Set your IP address as 192.168.0.203 ( could be anything except 192.168.0.202, assuming this is the Pre's address)
# Subnet mask: 255.255.255.0
# Default Gateway: 192.168.0.202 (your Pre's address for the usb0 interface)
# Set DNS to your preferred servers. Addresses are not currently resolving for me, regardless of the server I use
# Hit OK

The network should now be setup. To verify, ssh to 192.168.0.202, and you should be prompted for a login.

=== Notes:===
* This has only been tested on Windows XP 32 bit. For Windows 2000, you will need an additional download from Microsoft. The link is in the header of the INF file.
- From zinge: I have several confirmations via the precentral forums that this only works on XP sp3. Sp2 gives "error code 10, the device cannot start". Has anyone followed this process and had it work on XP sp2? Update: Upgraded to SP3 on my laptop, and it immediately started working.
* The 64 bit driver is unverified at this point, but I think it works.
* wayne47: I was having all kinds of issues with this on my WinXP notebook. Clicking on the //safely remove hardware// icon in the tray indicated two devices associated with the Pre: Novacom and a USB drive. Stopping the Novacom service resolved the issues. Note that I need to do this each time that I attach the Pre via USB.

== On Mac OS X==
mdklein notes that as of 1.0.4 the g_composite driver appears to only operate usbnet in rndis mode which is not the method OS-X includes. He has made a version that implements CDC-ECM, but it breaks a few other things. Working on this.

Allegedly, Mac OS X 10.4 should create a usb0 interface after you plug in a usbnet enabled pre. 10.5 needs a modified driver, which is not working for me (and carazy) yet.
See http://bugcommunity.com/wiki/index.php/Start_Guide_Mac_OS_X_10.5 for more details.

== Windows Vista (64-bit)==
* If driver/device fails to come online in network sharing center, simply click start->right click computer-> properties ... Click Device manager and look for the device "Linux USB Ethernet/RNDIS Gadget" you can then right click disable/enable the device. That's all.
* This device/driver can also be cycled with MS Windows own [http://support.microsoft.com/kb/311272 DevCon] application.

== Windows 7 RC Build 7100 (64-bit)==
* User lars47 confirms this is working on Windows 7 x64. Wrestled with the driver installation at first, it would not install, Windows complained of a file in use. I rebooted, and the next time I plugged in the Pre via USB, it "just worked". Unsure if I caused the problem, or if a reboot is required/recommended.

== Linux Support==
Once usbnet was enabled on the Pre, my Ubuntu 9.04 (64 bit) immediately identified the Pre in the NetworkManager and worked without modification to the OS. It seems to already have a driver that works.

== Return to the next steps page: [[Next_steps | Next Steps ]].==

Next steps

2009-09-03T14:44:56Z

Howard: /* Finishing */

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes a SSH program (''Dropbear'') and SFTP program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

===Installing Optware in the Emulator?===
If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
#Alternately you can use this tiny url http://tinyurl.com/n8q2vy
sh optware-bootstrap.sh
source /etc/profile.d/optware
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your Pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, you are in a local network, but checkmyip.com gives you the WAN addess. Install whatismyip from the homebrew catalog to get your pre's ip address within the local network and use that
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Only the default shell (/bin/ash) will work for ssh. To change your shell to bash (located in /opt/bin/bash after the install), you will have to create an /etc/shells file, and add the following lines:

/bin/ash
/bin/sh
/opt/bin/bash

Then you will be able to edit /etc/passwd and change the shell parameter for the user you created. Note that if you try to change your shell without adding an /etc/shells the SSH server (Dropbear) will look like it is rejecting your password on subsequent connections.

Next steps

2009-09-03T10:27:46Z

Howard: /* Finishing */

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes a SSH program (''Dropbear'') and SFTP program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

===Installing Optware in the Emulator?===
If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
#Alternately you can use this tiny url http://tinyurl.com/n8q2vy
sh optware-bootstrap.sh
source /etc/profile.d/optware
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, you are in a local network, but checkmyip.com gives you the WAN addessInstall whatismyip from the homebrew catalog to get your pre's ip address within the local network and use that
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Only the default shell (/bin/ash) will work for ssh. To change your shell to bash (located in /opt/bin/bash after the install), you will have to create an /etc/shells file, and add the following lines:

/bin/ash
/bin/sh
/opt/bin/bash

Then you will be able to edit /etc/passwd and change the shell parameter for the user you created. Note that if you try to change your shell without adding an /etc/shells the SSH server (Dropbear) will look like it is rejecting your password on subsequent connections.

Next steps

2009-09-03T10:26:44Z

Howard: /* Finishing */

''The old, manual setup of Optware and users can be found [[Setting_up_optware_feed | here]].''

=Automated Setup of Optware, Users and Access=
The webOS community asks that users who have obtained access to the Linux subsystem install a standard set of software to ensure everyone has the necessary tools in place to use the resources the community is providing.

In particular, this includes the Optware package manager. Palm's webOS uses the ''ipkg'' package manager internally. The community has a version of ''ipkg'' called ''ipkg-opt'' which accesses the Optware library of over 1300 Linux programs available for installation on the Pre.

Palm has indicated that they have no intention of using the /opt directory, so we direct our installs to /opt/bin rather than /bin to avoid being overwritten by future Palm software upgrades.

In addition, the standard package creates a non-root user, installs ''sudo'', and includes a SSH program (''Dropbear'') and SFTP program.

For your convenience, we've packaged all this up into a simple script.

==Optware Setup==

===Installing Optware in the Emulator?===
If you're attempting to install these packages to your emulator, you must first add sufficient space by [[Adding_Disks_to_the_Emulator|enabling a virtual disk]].

After completing the process of obtaining access to your Pre, do the following:

'''Type each line exactly as it appears. Copying and pasting is probably a good idea.'''

''Note to Windows Putty users: To paste in putty, simply right-click and the program pastes into the terminal whatever you have copied to the clipboard.''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/optware-bootstrap.sh
#Alternately you can use this tiny url http://tinyurl.com/n8q2vy
sh optware-bootstrap.sh
source /etc/profile.d/optware
</source></div>

Follow the on-screen instructions.

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/optware-bootstrap.sh]

==Quilt setup==

Optionally, you can then install the ''quilt'' patch manager which allows multiple-file patches. (Yes, the pun was intentional. Quilt manages multiple patches.) This installation process has also been packaged into a simple script. It will install quilt, and all of its dependencies, and create a local clone of the WebOS-Internals patch repository. [[Applying_Patches | Applying Patches]] provides a more thorough guide on the use of quilt.

'''Again, type each line exactly as it appears. Copying and pasting is probably a good idea.'''

<div style="font-size:100%;">
<source lang=bash>
cd /tmp
wget http://gitorious.org/webos-internals/bootstrap/blobs/raw/master/quilt-bootstrap.sh
sh quilt-bootstrap.sh
</source></div>

If you want to review the script before you run it, you can look here:

[http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh http://gitorious.org/webos-internals/bootstrap/blobs/master/quilt-bootstrap.sh]

==Finishing==

To finish off, turn Developer Mode back to "Off" (which will reboot your Pre).

Once you are finished, you may SSH into your Pre with an SSH client like [http://www.chiark.greenend.org.uk/~sgtatham/putty/ Putty]:
*Find your IP address on your pre with [http://checkmyip.com/ CheckMyIP.com]
**In many cases, checkmyip.com will give you the wan addess, but you would be within a local network. Install whatismyip from the homebrew catalog to get your pre's ip address within the local network
*SSH to that IP address on port 222
**If you're doing this over EVDO, there may be a lot of latency. Be patient.
**You can optionally install [[Avahi]] and SSH to <tt>castle.local.</tt>
*Log in with the username and password you created during the Optware installation
**Many operations cannot be carried out with the permissions of that username. You'll need to [[Basic_Linux_Use#sudo|sudo]] those operations with the new username's password

Only the default shell (/bin/ash) will work for ssh. To change your shell to bash (located in /opt/bin/bash after the install), you will have to create an /etc/shells file, and add the following lines:

/bin/ash
/bin/sh
/opt/bin/bash

Then you will be able to edit /etc/passwd and change the shell parameter for the user you created. Note that if you try to change your shell without adding an /etc/shells the SSH server (Dropbear) will look like it is rejecting your password on subsequent connections.