ThinkWiki - User contributions [en]

Category:Yoga

2013-12-23T15:44:43Z

Chrysn: update from referenced article

__NOTOC__

{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad Yoga ===
This page gives an overview of the ThinkPad Yoga.

(It is not to be confused with the IdeaPad series devices of the same name.)

=== Features ===

* 360° hinge for laptop and tablet operation
* One of the following processors:
** Intel Core i5-4200U Processor (3MB Cache, up to 2.60GHz)
** Intel Core i5-4300U Processor (3MB Cache, up to 2.90GHz)
** Intel Core i7-4500U Processor (4MB Cache, up to 3.00GHz)
** Intel Core i7-4600U Processor (4MB Cache, up to 3.30GHz)
* Full HD display with multitouch and wacom tablet
* Intel HD Graphics 4400
* 4-8GB [[PC3-12800]] DDR3L depending on CPU
* One of the following WiFi cards:
** Intel Wireless-N 7260 2X2 BGN+BT
** Intel Dual Band Wireless 7260AC with Bluetooth 4.0

|}

=== Resources ===

* [http://forum.ubuntuusers.de/topic/bluetooth-ethernet-ueber-dock-lenovo-thinkpad-/ Ubuntu 13.10 installation report] (german). bottom line: things work in general, Bluetooth is flaky (even under Windows), Ethernet (only available on OneLink dock anyway, rest of OneLink seems to work) does not work

Category:Yoga

2013-12-09T08:32:30Z

Chrysn: created page from lenovo website and linked installation report

__NOTOC__

{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad Yoga ===
This page gives an overview of the ThinkPad Yoga.

(It is not to be confused with the IdeaPad series devices of the same name.)

=== Features ===

* 360° hinge for laptop and tablet operation
* One of the following processors:
** Intel Core i5-4200U Processor (3MB Cache, up to 2.60GHz)
** Intel Core i5-4300U Processor (3MB Cache, up to 2.90GHz)
** Intel Core i7-4500U Processor (4MB Cache, up to 3.00GHz)
** Intel Core i7-4600U Processor (4MB Cache, up to 3.30GHz)
* Full HD display with multitouch and wacom tablet
* Intel HD Graphics 4400
* 4-8GB [[PC3-12800]] DDR3L depending on CPU
* One of the following WiFi cards:
** Intel Wireless-N 7260 2X2 BGN+BT
** Intel Dual Band Wireless 7260AC with Bluetooth 4.0

|}

=== Resources ===

* [http://forum.ubuntuusers.de/topic/bluetooth-ethernet-ueber-dock-lenovo-thinkpad-/ Ubuntu 13.10 installation report] (german)
bottom line: things work in general, WiFi works but is flaky, Ethernet (only available on OneLink dock) does not work

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2013-05-22T21:42:28Z

Chrysn: /* BIOS update */ how to see the bios version

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135. Please note that the E135 comes in subtle variations (eg. a BCM43142 wifi adapter instead of a BCM4313); if your experience differs from what is described here, please contribute your findings.

This description is sufficient to get the base system running; several subsystems have not yet been tested.

== BIOS update ==

If your BIOS version is smaller than 2.07 (eg. 1.05; versions between have not yet been tested; can be seen in the first screen of the BIOS setup tool or as -core / -firmware / version in `lshw` output), install [http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031728 the BIOS upgrade Lenovo provides]. The version linked is a ISO image that has to be burnt and booted from via an external CD drive; an [http://support.lenovo.com/en_US/downloads/detail.page?&DocID=DS031727 alternative version] can be installed from Windows.

A too old BIOS version will cause you trouble with suspending; in particular, a first suspend cycle will work but break wifi, and the machine won't come up from a second one again.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and (for BCM4313) wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well. For the BCM4313 modesl, if [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used.

=== Graphics ===

When the installer has completed and the system reboots, the graphical user interface will not come up. Press Ctrl-Alt-F1, log in, and execute the following lines to install the firmware the graphics card needs from Debian's non-free repositories:

<pre><nowiki>
# echo "deb http://cdn.debian.net/debian/ wheezy non-free" > /etc/apt/sources.list.d/nonfree.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get install firmware-linux-nonfree
# reboot
</nowiki></pre>

After rebooting, you should be able to log in graphically.

== WIFI ==

You can determine which wifi adapter is in use by issuing

<pre><nowiki>
$ lspci |grep BCM
</nowiki></pre>

=== BCM4313 models ===

There is a free driver for these cards called `brcmsmac` -- if things work for you out of the box, you are fine. Otherwise (eg. if you have signal strength issues), install the non-free `broadcom-sta-dkms` and `linux-headers-amd64` packages. The proprietary broadcom driver from the former package will be linked against the kernel in the latter, and wifi can be used regularly.

== BCM43142 models ==

The BCM43142 chip is [http://wireless.kernel.org/en/users/Drivers/b43 not supported] by the free drivers, and neither [http://bugs.debian.org/688823 by the nonfree drivers' version in wheezy].

A newer Ubuntu package can be used instead:

<pre><nowiki>
$ wget http://de.archive.ubuntu.com/ubuntu/pool/restricted/b/bcmwl/bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu6_amd64.deb
# apt-get install dkms libc6-dev linux-libc-dev
# dpkg -i bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu6_amd64.deb
</nowiki></pre>

(While it is not generally advisable to install packages from different distributions, "it is ok" here as there are no versioned dependencies, and it works.)

As with the BCM4313 approach, the proprietary broadcom driver will be linked against the kernel, and wifi can just be used.

== Hardware status ==

(none thereof tested in detail, eg if they operate at nominal speeds)

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: works
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth (might depend on wifi chip)

== Tweaks required ==

=== Volume keys ===

Multiple ALSA cards are detected, confusing xfce4-volumed. (In other words, volume buttons don't work). Can be fixed by installing gstreamer0.10-pulseaudio, and possibly setting the pulse audio sound card in the XFCE4 settings. [http://bugs.debian.org/694685 Reported.]

=== WiFi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

<tt>network-manager</tt> seems to be able to unlock cards too.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Category:E135

2013-05-22T21:40:16Z

Chrysn: note hardware variations

__NOTOC__
{| width="100%"
|style="vertical-align:top" |
<div style="margin: 0; margin-right:10px; border: 1px solid #dfdfdf; padding: 0em 1em 1em 1em; background-color:#F8F8FF; align:right;">
=== ThinkPad Edge E135 ===
This page gives an overview over of the ThinkPad Edge E135.

==== Features ====

{{Todo|Get an official list of variations}}

* AMD E2-1800 APU with Radeon(tm) Graphics
* Radeon HD 6250/6310 graphics card (1366x768 LCD display, VGA, HDMI)
* BCM4313 802.11b/g/n Wireless LAN Controller
** in later models: BCM43142
* RTL8111/816B PCI Express Gigabit Ethernet controller
* RTS5209 PCI Express Card Reader
* Hudson USB XHCI, OHCI and EHCI Controllers (USB 3.0)
* Hudson SATA Controller
* Hudson Azalia Controller (sound card)
* Seagate STL320LT007 320GB hard disk (7mm height)
* Lite-On integrated camera
* Broadcom BCM20702A0 bluetooth adapter
** replaced with BCM43142 chip in later models

[[Category:Edge]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2013-05-22T21:29:08Z

Chrysn: /* WiFi */ removed obsolete note (superseded by the comment about signal strength and nonfree drivers)

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135. Please note that the E135 comes in subtle variations (eg. a BCM43142 wifi adapter instead of a BCM4313); if your experience differs from what is described here, please contribute your findings.

This description is sufficient to get the base system running; several subsystems have not yet been tested.

== BIOS update ==

If your BIOS version is smaller than 2.07 (eg. 1.05; versions between have not yet been tested; can be seen in the first screen of the BIOS setup tool), install [http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031728 the BIOS upgrade Lenovo provides]. The version linked is a ISO image that has to be burnt and booted from via an external CD drive; an [http://support.lenovo.com/en_US/downloads/detail.page?&DocID=DS031727 alternative version] can be installed from Windows.

A too old BIOS version will cause you trouble with suspending; in particular, a first suspend cycle will work but break wifi, and the machine won't come up from a second one again.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and (for BCM4313) wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well. For the BCM4313 modesl, if [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used.

=== Graphics ===

When the installer has completed and the system reboots, the graphical user interface will not come up. Press Ctrl-Alt-F1, log in, and execute the following lines to install the firmware the graphics card needs from Debian's non-free repositories:

<pre><nowiki>
# echo "deb http://cdn.debian.net/debian/ wheezy non-free" > /etc/apt/sources.list.d/nonfree.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get install firmware-linux-nonfree
# reboot
</nowiki></pre>

After rebooting, you should be able to log in graphically.

== WIFI ==

You can determine which wifi adapter is in use by issuing

<pre><nowiki>
$ lspci |grep BCM
</nowiki></pre>

=== BCM4313 models ===

There is a free driver for these cards called `brcmsmac` -- if things work for you out of the box, you are fine. Otherwise (eg. if you have signal strength issues), install the non-free `broadcom-sta-dkms` and `linux-headers-amd64` packages. The proprietary broadcom driver from the former package will be linked against the kernel in the latter, and wifi can be used regularly.

== BCM43142 models ==

The BCM43142 chip is [http://wireless.kernel.org/en/users/Drivers/b43 not supported] by the free drivers, and neither [http://bugs.debian.org/688823 by the nonfree drivers' version in wheezy].

A newer Ubuntu package can be used instead:

<pre><nowiki>
$ wget http://de.archive.ubuntu.com/ubuntu/pool/restricted/b/bcmwl/bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu6_amd64.deb
# apt-get install dkms libc6-dev linux-libc-dev
# dpkg -i bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu6_amd64.deb
</nowiki></pre>

(While it is not generally advisable to install packages from different distributions, "it is ok" here as there are no versioned dependencies, and it works.)

As with the BCM4313 approach, the proprietary broadcom driver will be linked against the kernel, and wifi can just be used.

== Hardware status ==

(none thereof tested in detail, eg if they operate at nominal speeds)

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: works
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth (might depend on wifi chip)

== Tweaks required ==

=== Volume keys ===

Multiple ALSA cards are detected, confusing xfce4-volumed. (In other words, volume buttons don't work). Can be fixed by installing gstreamer0.10-pulseaudio, and possibly setting the pulse audio sound card in the XFCE4 settings. [http://bugs.debian.org/694685 Reported.]

=== WiFi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

<tt>network-manager</tt> seems to be able to unlock cards too.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2013-05-22T21:27:30Z

Chrysn: updated to latest status

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135. Please note that the E135 comes in subtle variations (eg. a BCM43142 wifi adapter instead of a BCM4313); if your experience differs from what is described here, please contribute your findings.

This description is sufficient to get the base system running; several subsystems have not yet been tested.

== BIOS update ==

If your BIOS version is smaller than 2.07 (eg. 1.05; versions between have not yet been tested; can be seen in the first screen of the BIOS setup tool), install [http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031728 the BIOS upgrade Lenovo provides]. The version linked is a ISO image that has to be burnt and booted from via an external CD drive; an [http://support.lenovo.com/en_US/downloads/detail.page?&DocID=DS031727 alternative version] can be installed from Windows.

A too old BIOS version will cause you trouble with suspending; in particular, a first suspend cycle will work but break wifi, and the machine won't come up from a second one again.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and (for BCM4313) wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well. For the BCM4313 modesl, if [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used.

=== Graphics ===

When the installer has completed and the system reboots, the graphical user interface will not come up. Press Ctrl-Alt-F1, log in, and execute the following lines to install the firmware the graphics card needs from Debian's non-free repositories:

<pre><nowiki>
# echo "deb http://cdn.debian.net/debian/ wheezy non-free" > /etc/apt/sources.list.d/nonfree.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get install firmware-linux-nonfree
# reboot
</nowiki></pre>

After rebooting, you should be able to log in graphically.

== WIFI ==

You can determine which wifi adapter is in use by issuing

<pre><nowiki>
$ lspci |grep BCM
</nowiki></pre>

=== BCM4313 models ===

There is a free driver for these cards called `brcmsmac` -- if things work for you out of the box, you are fine. Otherwise (eg. if you have signal strength issues), install the non-free `broadcom-sta-dkms` and `linux-headers-amd64` packages. The proprietary broadcom driver from the former package will be linked against the kernel in the latter, and wifi can be used regularly.

== BCM43142 models ==

The BCM43142 chip is [http://wireless.kernel.org/en/users/Drivers/b43 not supported] by the free drivers, and neither [http://bugs.debian.org/688823 by the nonfree drivers' version in wheezy].

A newer Ubuntu package can be used instead:

<pre><nowiki>
$ wget http://de.archive.ubuntu.com/ubuntu/pool/restricted/b/bcmwl/bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu6_amd64.deb
# apt-get install dkms libc6-dev linux-libc-dev
# dpkg -i bcmwl-kernel-source_6.20.155.1+bdcom-0ubuntu6_amd64.deb
</nowiki></pre>

(While it is not generally advisable to install packages from different distributions, "it is ok" here as there are no versioned dependencies, and it works.)

As with the BCM4313 approach, the proprietary broadcom driver will be linked against the kernel, and wifi can just be used.

== Hardware status ==

(none thereof tested in detail, eg if they operate at nominal speeds)

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: works
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth (might depend on wifi chip)

== Tweaks required ==

=== Volume keys ===

Multiple ALSA cards are detected, confusing xfce4-volumed. (In other words, volume buttons don't work). Can be fixed by installing gstreamer0.10-pulseaudio, and possibly setting the pulse audio sound card in the XFCE4 settings. [http://bugs.debian.org/694685 Reported.]

=== WiFi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

<tt>network-manager</tt> seems to be able to unlock cards too.

After the original installation, the WiFi only worked a few meters from the base station, as if a power saving mode that should be was active. That went away after some updates; a system from wheezy as of 2012-11-29 should work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2013-05-21T13:36:56Z

Chrysn: update: do a bios update

'''This report is outdated. Please leave it in place until it gets updated to the current state of Debian. If you experience any sort of trouble, install the BIOS / UEFI update described at http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS031728.'''

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used.

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the `linux` line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

== Open issues ==

* Starting Gnome makes the X server crash for yet-to-be-explored reasons.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.
* Device doesn't come up after suspend

== Hardware status ==

(none thereof tested in detail, eg if they operate at nominal speeds)

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: works
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth

== Tweaks required ==

=== Volume keys ===

Multiple ALSA cards are detected, confusing xfce4-volumed. (In other words, volume buttons don't work). Can be fixed by installing gstreamer0.10-pulseaudio, and possibly setting the pulse audio sound card in the XFCE4 settings. [http://bugs.debian.org/694685 Reported.]

=== WiFi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

<tt>network-manager</tt> seems to be able to unlock cards too.

After the original installation, the WiFi only worked a few meters from the base station, as if a power saving mode that should be was active. That went away after some updates; a system from wheezy as of 2012-11-29 should work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-29T02:09:07Z

Chrysn: wifi problem went away

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used.

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the `linux` line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

== Open issues ==

* Starting Gnome makes the X server crash for yet-to-be-explored reasons.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.
* Device doesn't come up after suspend

== Hardware status ==

(none thereof tested in detail, eg if they operate at nominal speeds)

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: works
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth

== Tweaks required ==

=== Volume keys ===

Multiple ALSA cards are detected, confusing xfce4-volumed. (In other words, volume buttons don't work). Can be fixed by installing gstreamer0.10-pulseaudio, and possibly setting the pulse audio sound card in the XFCE4 settings. [http://bugs.debian.org/694685 Reported.]

=== WiFi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

<tt>network-manager</tt> seems to be able to unlock cards too.

After the original installation, the WiFi only worked a few meters from the base station, as if a power saving mode that should be was active. That went away after some updates; a system from wheezy as of 2012-11-29 should work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-29T01:43:49Z

Chrysn: tweaks section

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

== Open issues ==

* Starting Gnome makes the X server crash for yet-to-be-explored reasons.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.
* Device doesn't come up after suspend

== Hardware status ==

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: extremely weak
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth

== Tweaks required ==

=== Volume keys ===

Multiple ALSA cards are detected, confusing xfce4-volumed. (In other words, volume buttons don't work). Can be fixed by installing gstreamer0.10-pulseaudio, and possibly setting the pulse audio sound card in the XFCE4 settings. [http://bugs.debian.org/694685 Reported.]

=== WiFi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

<tt>network-manager</tt> seems to be able to unlock cards too.

The card seems to be extremely weak in receiving signals, this is to be investigated further.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-29T01:34:42Z

Chrysn: /* Open issues */ added hardware section

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Starting Gnome makes the X server crash for yet-to-be-explored reasons.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.
* Device doesn't come up after suspend

== Hardware status ==

* Webcam: works
* Card reader: works with SD cards (no others tested)
* Touch pad, track point: work
* wifi: extremely weak
* Ethernet: works
* Regular USB: works

* Untested:
** USB 3
** Video connection
** Audio jack
** Bluetooth

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-22T11:43:24Z

Chrysn: /* Open issues */ gnome issue is back

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Starting Gnome makes the X server crash for yet-to-be-explored reasons.
* Check more hardware (webcam etc.).
* Find out if wifi is really that weak.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-22T04:21:43Z

Chrysn: /* Graphics */ missed an important parameter

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" -i /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Check more hardware (webcam etc.).
* Find out if wifi is really that weak.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-22T04:18:18Z

Chrysn: /* Graphics */ i should use preview more often

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<pre>
> insmod efi_gop
> insmod efi_uga
> insmod gfxterm
> set gfxmode=auto
> set gfxpayload=keep
> terminal_output gfxterm
</pre>

Then press Escape, `e` and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<pre><nowiki>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</nowiki></pre>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Check more hardware (webcam etc.).
* Find out if wifi is really that weak.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-22T04:15:44Z

Chrysn: make it work with encrypted disks

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing `c` and write the following commands:

<code>
insmod efi_gop
insmod efi_uga
insmod gfxterm
set gfxmode=auto
set gfxpayload=keep
terminal_output gfxterm
</code>

Then press Escape, `e` and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<code>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</code>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Check more hardware (webcam etc.).
* Find out if wifi is really that weak.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)
* The GRUB `insmod` lines are not necessary under all conditions. Especially, when an unencrypted disk is used, they seem to be optional; has to do with the early initial password prompt.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-22T04:02:49Z

Chrysn: /* Open issues */ gnome/gdm3 work, dunno what made them not work before; added missing issues

This is a short guide to installing Debian 7.0 (wheezy, currently testing, installer beta 4) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps). If [http://ftp.us.debian.org/debian/pool/non-free/f/firmware-nonfree/firmware-brcm80211_0.36_all.deb a firmware-brcm80211 package] is provided on an additional USB stick, the module can be loaded and wifi can be used. (Connecting required unusually good signal quality; whether the antenna is just weak or this is a configuration bug remains to be seen.)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing e and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<code>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</code>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Check more hardware (webcam etc.).
* Find out if wifi is really that weak.
* Try the whole setup process with more than an empty standard software selection. (Might interfere with display setup as long the drivers are not installed yet.)

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-22T03:29:04Z

Chrysn: about networking

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-21T17:05:33Z

Chrysn: more detailed instructions

This is a short guide to installing Debian 7.0 (wheezy, currently testing) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps).

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing e and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40). That can be accomplished by those commands, assuming you are connected to a typical wired network:

<code>
# dhclient eth0
# mkdir /lib/firmware/radeon
# cd !$
# wget -m -l1 http://people.freedesktop.org/~agd5f/radeon_ucode/
# mv people*/*/*/*.bin .
# echo "deb http://cdn.debian.net/debian/ experimental main" > /etc/apt/sources.list.d/experimental.list
# sed "s/^deb cdrom/# &/" /etc/apt/sources.list
# apt-get update
# apt-get -t experimental install libdrm2 libdrm-radeon1
# reboot
</code>

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Gnome and GDM don't work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-21T15:37:33Z

Chrysn: tried w/o ifrmware

This is a short guide to installing Debian 7.0 (wheezy, currently testing) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. Wired ethernet will work without the firmware as well (but seems limited to 100mbps).

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing e and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40).

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Gnome and GDM don't work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Category:E135

2012-11-20T02:22:56Z

Chrysn: /* Features */ more features from lsusb (last was from lshw)

Category:E135

2012-11-20T02:20:28Z

Chrysn: hardware summary

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-20T02:09:02Z

Chrysn: categorization for device number

This is a short guide to installing Debian 7.0 (wheezy, currently testing) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. (FIXME: ethernet had basic function w/o firmware, right?)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing e and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40).

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Gnome and GDM don't work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]
[[Category:E135]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-20T02:04:11Z

Chrysn: how to make wifi work

This is a short guide to installing Debian 7.0 (wheezy, currently testing) on a ThinkPad Edge E135.

It is sufficient to get the base system running; several subsystems have not yet been tested. As wheezy is not released yet, some steps might not be necessary in the future any more.

== Installation ==

Debian can be installed from a USB device (the E135 does not have an optical drive). The installer asks for firmware for the ethernet and wifi interfaces; those requests can safely be ignored. (FIXME: ethernet had basic function w/o firmware, right?)

=== Graphics ===

When the installer has completed and the system reboots, interrupt the bootloader by pressing e and add these parameters to the kernel line:

<code>radeon.modeset=0 1</code>

Log in using your root password, download all the <tt>.bin</tt> files from [http://people.freedesktop.org/~agd5f/radeon_ucode/] into <tt>/lib/firmware/radeon</tt>, and install libdrm2 and libdrm-radeon1 from the experimental repositories (>=2.4.40).

Since GDM and Gnome seem to have issues with the graphics system provided by this setup, that would also be a good time to install xdm and xfce4.

After rebooting, you should be able to log in graphically.

=== wifi ===

The wifi card is soft blocked at bootup (meaning that the OS thinks that something in the hardware is suggesting that wifi better be off). It can be explicitly unblocked with the <tt>rfkill</tt> utility, but in practice, installing the <tt>urfkill</tt> package is recommended, which makes the toggle-wifi (Fn-F9) hardware button work.

== Open issues ==

* Gnome and GDM don't work.

== Further references ==

* [http://bugs.debian.org/693756 installation report on the Debian bug tracking system]

[[Category:Debian 7.0 (Wheezy)]]

Installing Debian 7.0 (Wheezy) on a ThinkPad Edge E135

2012-11-20T00:52:42Z

Chrysn: how to get a basic running system

Xorg RandR 1.2

2008-03-17T02:24:03Z

Chrysn: added gui section

== Overview ==

'''X RandR '''is used to configure which display ports are enabled (e.g. LCD, VGA and DVI), and to configure display modes and properties such as orientation, reflection and DPI.

This is the simplest and most powerful way to get multi-monitor systems working using recent versions of Linux such as {{Ubuntu 7.10}} and {{Fedora 8}} with graphics chipsets such as the Intel 945GM/GMS and ATI Radeon found in Thinkpads.

'''xrandr''' is the command line interface to the RandR X extension. As usual with X, good documentation is hard to find; first try the following commands:

* {{cmduser|xrandr --help}}
* {{cmduser|man xrandr}}

* for Intel graphics: {{cmduser|man intel}}
* for ATI graphics: {{cmduser|man radeon}}

The rest of this page refers to a laptop with a built in 1024x768 pixel screen and an external 1600x1200 VGA monitor. Simply replace the relevant numbers with your own system specifications and all should work fine.

== Supported drivers ==
{{Ubuntu 7.10}} '''Gutsy Gibbon'''
* X.org [[intel]] driver, version ??? (included in Xorg ???) and later. Ubuntu version: [https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel/2:2.1.1-0ubuntu2 2:2.1.1-0ubuntu2] with [https://launchpad.net/ubuntu/gutsy/i386/xrandr/1:1.2.2-0ubuntu1 xrandr 1:1.2.2-0ubuntu1]

* X.org [[radeon]] driver, 6.7.192 and later (in ubuntu [http://packages.ubuntu.com/gutsy/x11/xserver-xorg-video-ati gutsy] and [http://packages.ubuntu.com/hardy/x11/xserver-xorg-video-ati hardy], but they still have [http://bugs.launchpad.net/bugs/148408 very serious issues] for some Thinkpads).

== xorg.conf ==
Recent versions of xorg.conf intended for use with xrandr 1.2 considerably simplify the video section of the configuration. If you upgrading from an earlier version you may find your existing xorg.conf works against the effective deployment of xrandr. So it is best to start with a new Xorg configuration.

'''an updated Xorg.conf should:'''
* omit dual Device/Screen/Monitor sections
* omit MonitorLayout option and Screen lines from the remaining Device section
* omit dual Screen lines from the ServerLayout section
* omit RightOf/LeftOf indication to the remaining Screen line in ServerLayout section
* add a "Virtual 2048 2048" line in SubSection "Display" to create a large virtual screen

To create a new xorg.conf or Ubuntu and other Debian based distributions connect the external display to the VGA port, turn on that display, and run
{{cmduser|sudo dpkg-reconfigure -phigh xserver-xorg}}

The resulting {{path|/etc/X11/xorg.conf}} should include something like

Section "Device"
Identifier "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
'''# ADD THIS IF YOUR LAPTOP DOES NOT HAVE A TV CONNECTOR or DOCKING STATION '''
'''Option "monitor-TV" "TV" '''
EndSection
Section "Monitor"
Identifier "Generic Monitor"
Option "DPMS"
EndSection
''' # ADD THIS IF YOUR LAPTOP DOES NOT HAVE A TV CONNECTOR or DOCKING STATION '''
'''Section "Monitor" '''
'''Identifier "TV" '''
'''Option "Ignore" "True" '''
EndSection '''
Section "Screen"
Identifier "Default Screen"
Device "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Monitor "Generic Monitor"
DefaultDepth 24
...
SubSection "Display"
Depth 24
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480"
'''# ADD A VIRTUAL LINE TO PROVIDE FOR THE LARGEST SCREENS YOU WILL HOTPLUG '''
'''Virtual 2048 2048 '''
EndSubSection
EndSection
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
InputDevice "stylus" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "Synaptics Touchpad"
EndSection

Just a hint:
If you want to use TV-out but not VGA for example, you should change these sections:
<pre>
Section "Device"
Identifier "Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller"
Driver "intel"
BusID "PCI:0:2:0"
Option "monitor-VGA" "VGA"
Option "monitor-TV" "TV"
Option "monitor-LVCD" "LVCD"
EndSection

Section "Monitor"
Identifier "VGA"
Option "Ignore" "true"
EndSection

Section "Monitor"
Identifier "LVCD"
Option "DPMS"
EndSection

Section "Monitor"
Identifier "TV"
Option "Ignore" "false"
EndSection
</pre>

after creating a clean Xorg.conf restart X and logon

You may find you have a display only on the external VGA screen at its default max resolution, do not worry xrandr can fix this.

== Using {{cmduser|xrandr}} ==

===First discover what we have ===
Open a terminal window to use the command line: 'Applications:Accessories:Terminal'

{{HINT|First look at the 'help' and 'man' pages. }}

{{cmduser|xrandr --help}}
{{cmduser|man xrandr}}

To find what version of xrandr is running, type the following command:
{{cmduser| xrandr -v}}
Server reports RandR version 1.2

To query what screens are connected, type the following: (The output shown indicates nothing is connected to the VGA port.)
{{cmduser| xrandr -q }}
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1920 x 1440
VGA disconnected (normal left inverted right)
LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 50.0
800x600 60.3
640x480 60.0 59.9
TV disconnected (normal left inverted right)

If you see the 'TV disconnected' line but have neither TV connector nor docking station (eg Thinkpad R60e) then add to the Monitor and Device sections of xorg.conf as noted above. This will prevent the external (VGA) flashing off for a few seconds every time xrandr is used. (Newer versions of the intel driver may fix this.)

The same command as above, but with the VGA monitor plugged in and powered off, should give something like the following output: (The VGA monitor is now shown as 'connected'.)
{{cmduser| xrandr -q }}
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1920 x 1440
VGA connected (normal left inverted right)
1920x1440@60 60.0
1920x1440 60.0
1600x1200@60 60.0
1600x1200 60.0
1280x960 60.0
640x480@60 60.0
LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 50.0
800x600 60.3
640x480 60.0 59.9
TV disconnected (normal left inverted right)

Powering on the VGA monitor and issuing the same command again will give the following output: (The size and position of the VGA output within the virtual screen is now shown.)
{{cmduser| xrandr -q }}
Screen 0: minimum 320 x 200, current 2624 x 1200, maximum 2624 x 2048
VGA connected 1600x1200+1024+0 (normal left inverted right) 367mm x 275mm
1600x1200 60.0*+
1920x1440@60 60.0
1600x1200@60 60.0
640x480@60 60.0
640x480 60.0
LVDS connected 1024x768+0+0 (normal left inverted right) 304mm x 228mm
1024x768 60.0*+ 50.0
800x600 60.3
640x480 60.0 59.9
TV disconnected (normal left inverted right)

For bug reporting and diagnosis use xrandr with the verbose option:
{{cmduser| xrandr --verbose}}

===Using xrandr to do useful things===
In general the commands will specify the output name and either --off or --auto. In the examples here the external screen is named ''VGA'', as used by the Intel driver, with an ATI card the name will probably be ''VGA-0''. In general use {{cmduser| xrandr -q}} to discover the appropriate output names for your configuration. The --auto option will select the preferred resolution for each output, this is starred(*) in the {{cmduser| xrandr -q}} listing and is normally the best resolution available. It is also possible to set a particular mode eg --mode 1024x768.

First clone the two screens, (the smaller screen will display the top left portion of the virtual screen)
{{cmduser| xrandr --output LVDS --auto --output VGA --auto --same-as LVDS}}

To turn off the VGA monitor.
{{cmduser| xrandr --output VGA --off }}

To turn the VGA monitor back on, with its viewport to the right of the laptop monitor:
{{cmduser| xrandr --output VGA --auto --right-of LVDS}}
This will probably give an error message similar to:
xrandr: screen cannot be larger than 1600x1600 (desired size 2624x1200)

This can be fixed by editing xorg.conf and changing the ''virtual'' line (see example above) to something like:
Virtual 2624 1200
Note that the maximum supported size of the virtual desktop for the Intel 945GM series of chipset with 3D acceleration enabled, is 2048x2048. The virtual screen can be larger but DRI will be disabled. This may matter if you like games and compiz desktop effects, or if you want Google Earth to display in better than geological time. Obviously the larger the virtual desktop, the more graphics memory is used. So for good performance with a shared graphics system such as Intel the Virtual should be no larger than necessary.

It is possible to set screen locations as ''--left-of'', ''--right-of'', ''--above'' and ''--below''. Assuming displays sizes of 1024x768 and 1200x1600:
{{cmduser| xrandr --output LVDS --auto --output VGA --auto --right-of LVDS}}
and
{{cmduser| xrandr --output LVDS --mode 1024x768 --pos 0x0 --output VGA --mode 1600x1200 --pos 1024x0}}
are equivalent. Both will place the external monitor to the right of the laptop display within the virtual screen.

If the Virtual size is only 2048 wide the above command will fail as the combined width of the two displays exceeds the maximum virtual size. However it is possible to have overlap the display viewports. So to fit within the 2048 limit:
{{cmduser| xrandr --output VGA --mode 1024x768 --pos 0x0 --output VGA --mode 1600x1200 --pos 448x0}}

===[[Sample Fn-F7 script]]===
For further examples of the use of xrandr commands and a script to switch the display using the Fuction key Fn7 see [[Sample Fn-F7 script]].

===GUIs===

Several graphical frontends are available for xrandr (all using GTK):

* [http://gitweb.freedesktop.org/?p=xorg/app/grandr.git Grandr]
* [http://www.albertomilone.com/urandr.html URandR]
* [http://christian.amsuess.com/tools/arandr/ ARandR]

== Summing up ==

'''xrandr''' enables dynamic resizing of screens, switching both external and laptop screens on and off, and the applications windows can be dragged from one screen to the other. None of this requires configuring anything special for {{path|/etc/X11/xorg.conf}}.

===the Virtual screen===
A Virtual line is needed in the 'Display' SubSection of the of xorg.conf; it determines the size of the frame buffer into which the displays must fit. Without it the maximum virtual size will be limited to the size of the largest display that was connected when X was started. The maximum virtual size cannot be changed once X starts so needs to be large enough to accommodate the largest combination of displays you want to hotplug without having to restart X. If it is greater than 2048x2048 and you are using an Intel 945 (or less) chip then DRI is not possible. Making the Virtual size square makes rotation easy. A bigger Virtual requires more memory.

[[Image:Intel-DualHead.png|monitor windows must fit within the virtual screen]]

=== Output port names ===

'''Intel driver'''
* '''VGA''' - Analog VGA output
* '''LVDS''' - Laptop panel
* '''TV''' - Integrated TV output
* '''TMDS-1''' - First DVI SDVO output
* '''TMDS-2''' - Second DVI SDVO output
The '''SDVO''' and '''DVO TV''' outputs are not supported by the driver at this time.

'''[[radeon]] driver '''
* '''VGA-0''' - Analog VGA output
* '''LVDS''' - Laptop panel
* '''S-video''' - Integrated TV output
* '''DVI-0''' - DVI output

===Note for Gnome users===
Gnome places the menu bar on screen 0 and thus with the Intel chip and driver Screen 0 (the external VGA monitor) will always be the default display if it is connected. This applies even if the external monitor is switched off but the cable connected: if you have a blank laptop monitor check if you have anything plugged in to the VGA port. Also beware that desktop icons and windows can disappear into the invisible parts of the virtual display. (see diagram below). If you want the panel(s) to appear by default on a different head, drag it to the head you want it on and GNOME will keep it there.

===Note for Ubuntu Gutsy users===
There is a Graphical Configuration Tool, ([https://launchpad.net/ubuntu/+source/displayconfig-gtk/0.2+20070731ubuntu1 displayconfig-gtk]) included with {{Ubuntu 7.10}}. At present [https://bugs.launchpad.net/ubuntu/+source/displayconfig-gtk it dosn't work too well].It is found in the menu: 'System: Administration: Screens and Graphics'. As using it will wreck your xorg.conf I recommend removing it.

== Gleanings ==
=== Notes from xserver-xorg-video-intel.readme ===
'''Known Limitations'''
- No support for "zaphod mode" dualhead. This is the mode in which two
Device sections are placed in the config file, and doesn't support DRI or
many other features. Instead, only "MergedFB-style" dualhead is supported.
- No support for X Screens larger than 2048 pixels in either direction
before the 965. This reflects hardware limitations in the x direction on
those older chips, and limits dualhead functionality. It may be possible to
extend the limit vertically on these older chips.
- i855 XV may cause hangs. This was present in the previous release, and no
workaround is known.
- SDVO TV-out cards not supported. This should be fixed in the next
release.
- Gray output with integrated TV-out and PAL TVs.
- EXA support unstable on i845.
- Some GM965 systems, such as the Thinkpad T61, probe the TV as being connected
even when no output connector is available.

'''Common issues not caused by the driver'''
- Font sizes (DPI) are wrong. Some displays incorrectly report their
physical size, which is harmless on most OSes that always assume 96dpi
displays. This can be fixed through quirks for specific monitors in the X
Server, and the output of xrandr --prop along with a physical measurement of
the screen size in a bug report against the server can help get that fixed.
- gnome-panel is located in the middle of the screen. gnome-panel places
itself within head #0's boundaries, which doesn't work well with a second
head covering the same area as head #0 but larger.
- Older resolution-changing applications have poor results in
multihead systems. Previous extensions such as RandR 1.1 exposed only a
single output to client programs, and those requests map poorly to multi-head
systems. Currently, those requests map to just one of the outputs in the
RandR 1.2 environment, and those applications need to be updated to RandR 1.2
API when available for better results.

=== Xorg mailing list ===
[http://lists.freedesktop.org/archives/xorg/2007-June/025469.html FreeDesktop.org 2007-June 025469]
[http://lists.freedesktop.org/archives/xorg/2007-June/025484.html FreeDesktop.org 2007-June 025484]
[http://lists.freedesktop.org/archives/xorg/2007-July/026340.html FreeDesktop.org 2007-July 026340]

the 3D engine has an 11 bit coordinate space at one point making it
impossible to draw to areas beyond 2048x2048. At another point, it has a
stride limit of 8192 bytes, so you can't even draw to a subset of a
larger frame buffer.

One more bit in both of these registers would have solved the problem
for pretty much any supportable monitor configuration (the chip can only
support two single-channel DVI outputs at the most; 1920 is the widest
size supported at single-channel speeds).

For multiple monitors, the driver could allocate multiple frame buffers
and step through them one at a time with appropriate clipping. It would
be icky, but could be made to work.

Of course, the latest hardware (965G/965GM) has plenty of coordinate
space, which does tend to reduce the odds that someone will get excited
enough to go fix the driver for older chips.

The Gnome menu bar lands on Xinerama Screen 0 at this
point, which isn't currently something that you can set through RandR. On Intel the allocation to Screen 0 is determined by CRTC order and LVDS only runs on screen 1.

[http://lists.freedesktop.org/archives/xorg/2007-June/026053.html FreeDesktop.org 2007-June 026053]

[http://lists.freedesktop.org/archives/xorg/2007-August/027616.html Blanking of external screen when using xrandr]

it's checking to see if you have anything connected to the TV output.
To do that, it needs to temporarily unplug the VGA.
You can avoid this by ignoring the TV output
Section "Monitor"
Identifier "TV"
Option "Ignore" "True"
EndSection
Section "Device"
Option "monitor-TV" "TV"
EndSection
If your machine cannot ever have a TV adapter (even with a docking station),
we can add a quirk to the driver to never look at the TV output. That requires
the pci subsystem values (from lspci -n -v) to plug into the quirk table.

[http://lists.freedesktop.org/archives/xorg/2007-August/027632.html default for 'Virtual']
> Version 2.1.1-0ubuntu2 seems to set the default Virtual size (maximum
> screen size) to 1920 x 1920, if there is no entry in xorg.conf. I take
> it the maximum screen size for the i915 chipset family is 2048 x 2048,
> so why not have it at that? This would make dualscreen setups a bit easier.
The default settings is found by taking the largest resolution in either
x or y dimension and making a square from that. This allows for easy
rotation should you want to do so.
I believe you should be able to do dual screen up to 8192x8192, though
only through two monitors (Only two pipes are available for output), but
that 3D acceleration is only supported up to 2048x2048. Thus as soon as
you set your virtual size above 2048x2048, you lose 3D acceleration.
The current driver cannot reallocate the frame buffer, so whatever size
you start with is the maximum the screen can ever become, and that this
amount of physical memory is tied down for the whole X server run.

[http://lists.freedesktop.org/archives/xorg/2007-August/027670.html Primary output for Laptop + external screen]
>the desired behavior of the video
> drivers in typical laptop situations with an internal display and an
> external screen attached (extending the desktop).
>
> Currently for example the intel driver uses the external screen as the
> primary output. It is listed first with xrandr. I'm not sure if this is
> intentional or just coincidence.
It's coincidence -- the laptop hardware has two crtcs, and the LVDS can
only be driven by the second.
Note that RandR doesn't really want the order to be significant; it
would be better if the desktop environment knew about outputs and could
refer to a specific output as 'primary' or 'holds toolbar' or whatever.

[mailto:gekkoman@illimitable.com  ] Uncovered a workaround for black and white TV-out "known limitation" listed above on a intel 945GM chipset running i810-2.1.1 driver and xrandr-1.2.2. Get TV running in black and white. Then run command.

xrandr --output TV --set TV_FORMAT PAL; xrandr --output TV --mode 1024x768

substitute TV_FORMAT and mode as required. Note that the command "xrandr --output TV --set TV_FORMAT PAL" gives an error but appears to work as the subsequent mode change converts screen to colour.

=== Notes for X31,T30 / Radeon 7000,Radeon 7500 users ===
My {{X31}} has an [[ATI Mobility Radeon 7000]] with only 16MB RAM. This is not enough for big screens and DRI. Neither with [[radeon]]-default virtual size of 2048x1200, nor with my customized virtual of 2304x1024 (for one 1024x768 and one 1280x1024 screen). But this only applies for 24-bit color depth. Now I'm using only 16-bit and DRI works fine with the big virtual screen.

If you really want 24-bit depth, and do not need a bigger screen as your LCD, try setting Virtual to "1024 768", this will enable DRI in 24-bit too, but you won't be able to extend your screen anymore (well, clone will still work though).

== References ==

* XRandR 1.2
** [http://gitweb.freedesktop.org/?p=xorg/proto/randrproto.git;f=randrproto.txt;a=blob RandR 1.2 protocol specifications] - this defines the model and terminology
** [http://wiki.x.org/wiki/XDC2007Notes#head-11895d48723a8d0308571bec8829b7cc3ef87d7b In Xorg Developer Conference 2007]
** [http://burtonini.com/blog/computers/randr-2007-02-06-17-50 tutorial blog post]

* Ubuntu
** Version 7.10 (Gutsy) of Ubuntu includes support for Xorg 7.3 with RandR 1.2 [https://wiki.ubuntu.com/Xorg7.3Integration Xorg 7.3]
** [[Installing Ubuntu on a ThinkPad R60e]] for a revised and more specific version of this page
** [https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel/ Ubuntu source for Intel]
** [https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/148408 gutsy version of xserver-xorg-ati has some major problems on ATI Radeon] for ([[:Category:X Series]]) and possibly others. The solution is to downgrade to the [https://launchpad.net/ubuntu/feisty/i386/xserver-xorg-video-ati/1:6.6.3-2ubuntu6 feisty version]

* X.org
** [http://lists.freedesktop.org/mailman/listinfo/xorg FreeDesktop.org mailing list]
** [http://lists.freedesktop.org/archives/xorg/ FreeDesktop.org Xorg archive]

* Useful page to supplement the minimal documentation [http://wiki.x.org/wiki/Development/Documentation/HowVideoCardsWork How video cards work]
* [http://wiki.debian.org/XStrikeForce/ReleaseNotes xserver-xorg-core and xserver-xorg-video-intel might cause some trouble but also brings nice features.]
* [http://andrew.mcmillan.net.nz/taxonomy/term/18 Seamless Monitor Hotplugging with X Windows]
* [http://www.intellinuxgraphics.org/ Linux Graphics Drivers from Intel]
* [http://zdzichubg.jogger.pl/2007/05/07/xrandr-1-2-sweetness/ blog post] with xrandr-1.2 commands and photos. Narrative is in polish.