ThinkWiki - User contributions [en]

Installing Ubuntu on a ThinkPad T20

2007-02-01T02:18:24Z

Kenguest: fixed link

== Ubuntu 6.10, Edgy Eft ==

=== Blank Screen when booting Live CD ===
As described in [[Installing Ubuntu on a Thinkpad T21]], there is an issue with the Savage driver which makes the initial boot into X hit and miss.

You can avoid this problem by using the alternate install CD. However, that doesn't allow you to
do any pre-installation evaluation of the GUI that the Live/Install CD provides.

=== Using APM to Suspend ===

To enable APM when booting the Live/Install CD, add these boot options:

`noacpi acpi=off apm=on`

After booting, `Fn-F4` will still only put the command in a standby state, but
using `apm --suspend` on the command line will successfully suspend machine, and it resumes as well.

=== Trying to Suspend with ACPI ===

A alternative to APM is ACPI. It is newer and more advanced, and preferred when it works. However, even with the newest BIOS (1.22) isntalled in the T20, Linux will still recognize the BIOS as "too old" and will disable ACPI. You can override this by adding this boot option: `acpi=force`.

Assuming you actually have Ubuntu installed (i.e., not running from Live CD) To add this boot option, open /boot/grub/menu.lst and look for the line(s) (there will be one for each boot menu choice) similar to:

kernel /boot/vmlinuz-2.6.17-10-386 root=UUID=1a2b3c4d-5e6f-1234-7a8b-1a2b3c4d5e6f ro

(n.b., I've obscured the UUID hex string above).

and add acpi=force to the lines you wish to change (i.e., the choices you want ACPI enabled for, though you probably only want to add to the line corresponding to the option for normal boot, not the recovery boot options).

N.B. *** READ THIS ***. Before running the grub-install line *at your own risk* below, make sure you know what you're doing (i.e., have read the grub documentation) and that /dev/hda *is* your boot drive otherwise you may render your system unbootable. Obviously if you're not using grub then this won't work.

Now run: grub-install /dev/hda

With this enabled suspend and resume works OK with the following caveats:

1. Weird errors seem to get output on resume.
2. Sometimes the machine will randomly enter suspend mode. This may be a setting in power manager that I've got set wrong or due to LCD screen wobble (suspend activates on lid close, resumes on lid open). The power manager help indicates how to set advanced gconf settings. There are also files in /etc/modprobe.d and /etc/acpi for further machine-specific configuration (TODO: investigate and post results here).

Even this option, once booted into the LiveCD, suspend still does not work. `gnome-power-manager` logs
to `/var/log/messages` that is beginning to suspend, but nothing happens. This looks like it might
be a [https://launchpad.net/distros/ubuntu/+source/linux-source-2.6.15/+bug/50031 known bug] in Ubuntu.

=== Special Key Support ===

The light and brightness keys work as expected. The volume keys have some on-screen visuals that automatically
appear to illustrate them, using graphics that match the curren theme. Rather nice!

=== Video ===

Direct rendering / GL acceleration works. Use "PCI" in BIOS rather than AGP. I removed all modes apart from 1024x768. ppracer plays well at c. 10fps with all the eye candy on.

Driver "savage"
BusID "PCI:1:0:0"
Option "SWCursor" "on"
Option "ShadowStatus" "on"
Option "DMAMode" "Vertex"
Option "DmaType" "PCI"
Option "BusType" "PCI"

HorizSync 28-51
VertRefresh 43-60

=== Confirmed compatible wireless cards ===

Belkin f5d7050 Wireless 802.11g USB adaptor (version 3) works (plugged into dock's lower USB port). The procedure is essentially install the ndiswrapper-1.8 and work through https://help.ubuntu.com/community/WifiDocs/WirelessTroubleShootingGuide.=

=== DVDs ===

DVDs play great once you've installed all the missing multimedia plugins. (work through https://help.ubuntu.com/community/MultimediaApplications and the linked to freeformats and restrictedformats pages).

=== Working software (or not) ===

One thing I find frustrating is that often it's difficult to know in advance which software requires too much memory / cpu or has GL problems (e.g., the infamous visual 0x42 error). At the risk of this lengthening this page somewhat here's a small list to start with.

==== With 128Mb ====

OpenOffice OK
Eclipse needs more RAM

==== With 384Mb ====

Eclipse OK

== Ubuntu 6.06 LTS, Dapper Drake ==

When booting the Live/Install CD, adjust the boot options to add the following:

`noacpi acpi=off apm=on`

Sometimes the CD may stall on boot with a blank black screen. Trying again with "Safe Graphics"
mode may help. (Or prehaps this is the same X issue with the Edgy Live CD, and it is simply trying again that helps).

Once booted, suspend and resume using Fn-F4 was successfully tested running from the LiveCD.
However, in at least a couple of cases, the Live CD froze at seemingly random points shortly
after resuming.

''Results from a complete install still need to be documented.''

== See Also ==

Because the models are very similar, [[Installing Ubuntu on a ThinkPad T21]] may also be helpful.

== External Resources ==

*[http://del.icio.us/tags/ubuntu+t20 Bookmarks tagged with Ubuntu and T20] on del.icio.us
*[http://ubuntuforums.org/tags/index.php/t20/ Forum posts tagged with T20] on ubuntuforums.org

{{Ubuntu}} {{T20}}

User:Kenguest

2007-02-01T02:11:51Z

Kenguest:

Running Ubuntu Dapper on a T22 and Breezy on a 390x.

Blog is at [[http://blogs.linux.ie/kenguest/]]

How to setup Bluetooth

2006-05-31T14:15:34Z

Kenguest: /* External Links */

{| width="100%"
|style="vertical-align:top;padding-right:20px;width:10px;white-space:nowrap;" | __TOC__
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#efefef; align:right;">
This HOWTO tells you how to install and configure Bluetooth on your Linux driven ThinkPad and how to make the most common Bluetooth applications (like connecting your mobile phone etc.) work.
</div>
|}

==BlueZ Installation==
===Building from source===
Get the source packages from [http://www.bluez.org www.bluez.org].

Build each of them with the usual steps:
:{{cmduser|./configure && make}}
:{{cmdroot|make install}}

===Gentoo ebuilds===
Under {{Gentoo}}, install the following ebuilds:
*net-wireless/bluez-bluefw
*net-wireless/bluez-firmware
*net-wireless/bluez-hcidump
*net-wireless/bluez-hciemu
*net-wireless/bluez-libs
*net-wireless/bluez-utils

{{NOTE|net-wireless/bluez-kernel is not needed, since the current version is included in your kernel.}}

===Other distributions===
You will find packages for {{Debian}}, {{Redhat}} and {{Slackware}} on the [http://www.bluez.org/packages.html packages page] of the BlueZ project.

==Configuring the kernel==
Since the Bluetooth card is connected to the USB subsystem, you will need to enable USB support in your kernel:
:{{kernelconf|CONFIG_USB|<M>|Support for Host-side USB|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_DEVICEFS|[*]|USB device file system|USB support|Device Drivers||}}

Choose an appropriate USB host driver, one of:
:{{kernelconf|CONFIG_USB_EHCI_HCD|<M>|EHCI HCD (USB 2.0) support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_UHCI|<M>|UHCI HCD support|USB support|Device Drivers||}}
:{{kernelconf|CONFIG_USB_OHCI|<M>|OHCI HCD support|USB support|Device Drivers||}}

Enable Bluetooth subsystem and drivers:
:{{kernelconf|CONFIG_BT|<*>|Bluetooth subsystem support|Networking|||}}
:{{kernelconf|CONFIG_BT_L2CAP|<*>|L2CAP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_SCO|<*>|SCO links support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM|<*>|RFCOMM protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_RFCOMM_TTY|[*]|RFCOMM TTY support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_BNEP|<*>|BNEP protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HID|<*>|HID protocol support|Bluetooth subsystem support|Networking||}}
:{{kernelconf|CONFIG_BT_HCIUSB|<M>|HCI USB driver|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}
:{{kernelconf|CONFIG_BT_HCIUSB_SCO|[*]|SCO (voice) support|Bluetooth device drivers|Bluetooth subsystem support|Networking|}}

Make sure that the according modules are loaded:
:{{cmdroot|modprobe uhci_hcd ; modprobe ehci_hcd ; modprobe hci_usb}}

==Serial connection over Bluetooth==
One common application is to connect your mobile phone and use it as a modem to connect to the internet via GPRS or 3G (UMTS). A lot of phones do this through using AT-commands on a serial over Bluetooth connection.

By configuring {{path|/etc/bluetooth/rfcomm.conf}} correctly, you'll get a device {{path|/dev/rfcomm0}}.

Eventually one could use the command:
:{{cmdroot|rfcomm bind 0 00:15:A0:7A:90:F2 3}}

The hardware address should be replaced with that of your phone. If you don't know the hardware address of your phone yet, you can get it by running:
:{{cmdroot|hcitool scan}}

The last parameter ('3') is the channel to use. I spent quite some time fighting before I found out of that one; I didn't find it documented anywhere, but by running
:{{cmdroot|sdptool records 00:15:A0:7A:90:F2}}
I found channel 3 to be the right one for my phone. You will have to experiment to find the right one for your phone setup; for T-Mobile GSM/GPRS carrier in USA this is channel 1.
{{NOTE|By experimenting, the bluetooth stack on the cellphone may crash. Reboot it if that happens.}}

Alternativly one could use the following to find the right channel:
:{{cmdroot|sdptool search DUN}}

Inquiring ...
Searching for DUN on 00:11:22:33:44:55 ...
Service Name: Dial-up Networking
Service RecHandle: 0x10001
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4

Now {{path|/dev/rfcomm0}} exists.

At this point you can use an automatic dialing utility such as wvdial, editing the config file to point to the modem at {{path|/dev/rfcomm0}}, and everything should work just like a land line!

{{NOTE|If you experience strange disconnects while using wvdial, disable "Carrier Check" in your wvdial configuration.}}

You may directly access the modem (i.e. by using minicom:)
:{{cmduser|minicom -s}}
set the serial device to be {{path|/dev/rfcomm0}}, choose 'exit' and then the AT-commands can be typed in.
With my operator (Telenor, Norway) it seemed simple enough, I just entered
:ATDT *99#
and lots of cryptic letters started dancing across the screen, indicating a ppp session startup.

To configure pppd create {{path|/etc/ppp/peers/nokia}} with particularly those lines:
/dev/rfcomm0
connect '/usr/sbin/chat -v -f /etc/ppp/chat-nokia'
debug
10.0.1.3
crtscts
noipdefault
ipcp-accept-local
defaultroute
novj
nobsdcomp
novjccomp
nopcomp
noaccomp
usepeerdns

Furthermore, you need a simple chat script. Create {{path|/etc/ppp/chat-nokia}}:
'TIMEOUT' '5'
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO ANSWER'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDT*99#'
'~--' ''

Run pppd with:
:{{cmduser|pppd call nokia}}
This should establish the internet connection.

{{NOTE|Different network operators may require different call strings. For many carriers (including T-Mobile USA) "*99#" works without additional parameters.}}

For editing phonebook / ringtones / etc., the gammu utils (http://www.gamu.net) has been reported to work well, but this appears to be primarily for Nokia phones.

==File Transfer==
File transfers are accomplished through OBEX transfer, which I believe is basically an FTP over bluetooth connection. Once you have bonded with your phone (yes, I know you love your sexy RAZR, but here I mean paired it with your laptop via bluetooth), you can easily use "obexftp" to transfer files. As an example,

:obexftp -b 00:01:02:03:04:05 -l

will list the root directory of the phone with bluetooth address 00:01:02:03:04:05. Refer to the man page for more of the unique commands. What a wonderful interface! Unfortunately there doesn't seem to be a way to get a standard 'ftp' session using familiar commands (e.g. 'mget').

For a more user-friendly experience, you can use the kde tools, just launch
:kbtobexclient

for a file browser. In the Location: option put
:obex://[00:01:02:03:04:05]

to list the files. Note that the brackets *are* necessary. From there, you can list directories easily and batch download files.

==External Links==
*http://gagravarr.org/series-60/
*http://www.polycon.fi/~laa/biblo/linux_gprs.html
*[http://www.gentoo.org/doc/en/bluetooth-guide.xml Guide on how to set up Bluetooth in Gentoo]
*[http://www.linux.ie/articles/bluetoothheadset.php www.linux.ie:Linux and Bluetooth Headset howto (AKA: Fedora, BTSCO, Bluez, Jabra and Skype)]

[[Category:A30]] [[Category:A30p]] [[Category:A31]] [[Category:A31p]] [[Category:R40]] [[Category:R40e]] [[Category:R50]] [[Category:R50p]] [[Category:R51]] [[Category:R52]] [[Category:T30]] [[Category:T40]] [[Category:T40p]] [[Category:T41]] [[Category:T41p]] [[Category:T42]] [[Category:T42p]] [[Category:T43]] [[Category:T43p]] [[Category:T60]] [[Category:X23]] [[Category:X24]] [[Category:X30]] [[Category:X31]] [[Category:X32]] [[Category:X40]] [[Category:X41]] [[Category:X41 Tablet]] [[Category:X60]] [[Category:X60s]] [[Category:Z60m]] [[Category:Z60t]]