install debian on eee pc

8/9/2019 Install debian on eee pc

1/96

debianwikieeepc.TOTAL

10 FEV 2015

+++ installer sur eeepc 701/901 debian +++26/02/2014qd meme ntéressant le site wikiD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC ||| CL DebianEeePCD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ M _ o _ d _ e _ l _ / _ 7 _ 0 _ 1 __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/Model/701D _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ F _ A _ Q __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/FAQ ||| CL FAQ-f33

D _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ H _ o _ w _ T _ o _ / _ I _ n _ s _ t _ a _ l _ l __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/HowTo/Insta

D _

e _

b _

i _

a _

n _

E _

e _

e _

P _

C _

/ _

H _

o _

w _

T _

o _

/ _

I _

n _

s _

t _

a _

l _

l _

U _

s _

i _

n _

g _

S _

t _

a _

n _

d _

a _

r _

d _

I _

n _

s _

t _

a _

l _

l _

e _

r __

- __

D _

e _

b _

i _

a _

n __

W _

i _

k _

i _

https://wiki.debian.orgD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ H _ o _ w _ T _ o _ / _ I _ n _ s _ t _ a _ l _ l _ O _ n _ S _ D _ c _ a _ r _ d _ O _ r _ U _ s _ b _ S _ t _ i _ c _ k __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.orgD _ e _ b _ i _ a _ n __ - _ - __ P _ a _ c _ k _ a _ g _ e __ S _ e _ a _ r _ c _ h __ R _ e _ s _ u _ l _ t _ s __ - _ - __ e _ e _ e _ p _ c _ - _ a _ c _ p _ i _ - _ s _ c _ r _ i _ p _ t _ s _ https://packages.debian.org/seaD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ H _ o _ w _ T _ o _ / _ C _ o _ n _ f _ i _ g _ u _ r _ e __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/HowD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ H _ o _ w _ T _ o _ / _ S _ o _ u _ n _ d __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/HowTo/SoundD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ T _ i _ p _ s _ A _ n _ d _ T _ r _ i _ c _ k _ s __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/TipsAndTricD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ S _ o _ f _ t _ w _ a _ r _ e __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/Software |D _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ S _ o _ f _ t _ w _ a _ r _ e _ / _ D _ e _ s _ k _ t _ o _ p _ E _ n _ v _ i _ r _ o _ n _ m _ e _ n _ t __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianED _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ S _ o _ f _ t _ w _ a _ r _ e _ / _ P _ r _ o _ d _ u _ c _ t _ i _ v _ i _ t _ y __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/SofD _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ S _ o _ f _ t _ w _ a _ r _ e _ / _ M _ u _ l _ t _ i _ m _ e _ d _ i _ a __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/Sof

F _ r _ e _ e _ S _ p _ a _ c _ e __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/FreeSpace ||| CL FreeSpace-2687bf497b3D _

e _

b _

i _

a _

n _

E _

e _

e _

P _

C _

/ _

B _

o _

o _

t __

- __

D _

e _

b _

i _

a _

n __

W _

i _

k _

i _

https://wiki.debian.org/DebianEeePC/Boot#head-d706b8e22B _ o _ o _ t _ P _ r _ o _ c _ e _ s _ s _ S _ p _ e _ e _ d _ u _ p __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/BootProcessSpeedup |||F _ r _ o _ m _ _ _ N _ a _ u _ g _ h _ t _ _ _ t _ o _ _ _ S _ i _ x _ t _ y _ _ _ i _ n _ _ _ 5 _ _ _ S _ e _ c _ o _ n _ d _ s __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/From_Naught_to_

D _ e _ b _ i _ a _ n _ E _ e _ e _ P _ C _ / _ B _ u _ g _ s __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/DebianEeePC/Bugs?action=show&reS _ y _ n _ a _ p _ t _ i _ c _ s _ T _ o _ u _ c _ h _ p _ a _ d __ - __ D _ e _ b _ i _ a _ n __ W _ i _ k _ i _ https://wiki.debian.org/SynapticsTouchpad


2/96

DebianEeePC-feb70179d6d9517881c6d94742117ae2.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

DebianEeePC•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

Brasileiro - ?Česky - Deutsch - English - Español - Français - ?Magyar - Italiano - Nederlands - ?Norsk - Polski - Português - Русский (Russkij) -?Svenska - ?Türkçe - Chinese - ? ( (Farsi) - ? (Tamilسر

The Debian Eee PC project's goal is full support for the ASUS Eee PC in

Debian.

We make Debian itself run on your Eee. See this summary about what has been

achieved so far and where we are heading.

Download, installation, configuration

See /HowTo/Install. For upgrades, check out the /HowTo/Upgrade page.

News

See the Project blog.

1/3

10 FEV 2015


3/96

Contact us

Discussion takes place on the IRC channel #debian-eeepc and the mailing list.

User

Supported

The following pages document the supported way to install, configure and use Debian on your Eee.

/FAQ•

/FreeYourEee•

/HowTo/Install•

/HowTo/InstallUsingStandardInstaller•

/HowTo/Configure•/HowTo/Wifi•

/HowTo/Sound•

/HowTo/Troubleshooting•

/HowTo/Upgrade•

/HowTo/UpgradeBIOS•

/HowTo/InstallOnSDcardOrUsbStick•

/Models•

/Repository•

/Software•

Contributed

Not all of the things documented by contributors below are supported by this project, though that does not

make them any less interesting or worth doing.

/HowTo/SplashyWithDmcryptAndStandardGrub•

/TipsAndTricks•

/Boot•

/HowTo/GetNativeConsoleResolution•

/HowTo/UseUpstreamAtherosModules•

/HowTo/ElantechTouchpad•

Developer

/Todo•

/Bugs•

/Source•

/Source/CustomInstaller•

Project

Teams/DebianEeePC•

/Status•

/Accessibility•

Alioth project site: http://alioth.debian.org/projects/debian-eeepc•

2/3


4/96

Translations

See the translations links at the top of each page. Please make sure if you add a translation that you or anyone

is also willing to update and maintain it.

Related

Related projects including Eee PC news, documentation, user support and development.

http://eeeuser.com/ (Eee-related news blog)•

http://wiki.eeeuser.com/

http://wiki.eeeuser.com/tuep:debianbase?s=debian (Etch-based base Debian install)♦

http://wiki.eeeuser.com/irc-channels♦

•

http://forum.eeeuser.com/ (A wide variety of Eee-related topics including original OS, other distros)

http://forum.eeeuser.com/search.php (for Debian-related threads: Keyword search: debian,

Search in: Topic subject only)

♦

•

http://eeebuntu.org/ (despite the name, versions >= 4.0 to be directly Debian based)•

CategoryLaptopComputer•

DebianEeePC (last edited 2013-07-11 10:33:24 by BenArmstrong)

MoinMoin Powered•

Python Powered•

Valid HTML 4.01•

Debian Wiki team, bugs and config available.•

Hosting provided by Dembach Goo Informatik GmbH & Co KG•

3/3


5/96

701-906d1bd36d3e3b76396008ee2cbd2f91.html.tgz.pdf

10 FEV 2015

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

DebianEeePC/Model/701•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

Model•

701•

The model 701 (listed in Asus literature as the model 4G) and related models (2G surf, 4G surf, and 8G) are

the oldest models, and therefore most of this wiki was written with them in mind. Exceptions for newer

models are noted in each page where appropriate.

When Lenny released, the Atheros AR2425 wifi b/g chipset in these machines was only supported by the

non-free madwifi driver. The good news is that now you can ../../FreeYourEee by upgrading your kernel to

2.6.30 as per ../../HowTo/Upgrade, as the free ath5k driver in recent kernels supports the AR2425.

The 701 is sometimes confused with the DebianEeePC/Model/701SD which has a different wireless chipset.

If the installer freezes while trying to install Wheezy onto a model 701, press the tab button beside the

"install" option. Then edit the "vga=#" to "vga=769"

DebianEeePC/Model/701 (last edited 2014-07-06 04:34:44 by ?AaronBecker)

MoinMoin Powered•

Python Powered•

Valid HTML 4.01•



1/1


6/96

FAQ-f33747e34c1228c686d44d1aca659387.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

DebianEeePC/FAQ•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

FAQ•

Translations: German, French, Italiano, Portuguese, Spanish

Contents

Links to basic knowledge1.

Frequently Asked Questions

Why do you make another fork of Debian to adapt it to the Asus Eee PC?1.

Do you provide a custom kernel specially adapted to the Eee PC hardware?2.

Do I need a swap partition?3.What about hibernate if I have no swap?4.

How much RAM do I need?5.

How much disk space does the installation take?6.

Do I need the EFI partition or is it safe to delete?7.

Can I make a test install on removable media without changing the existing OS?8.

Can I install *to* a USB harddrive in an external case?9.

Can I put the *installer* on an external harddrive and start installation *from there*?10.

Can I install from an external CDROM drive?11.

Can I mount an SD card at boot time?12.

My system takes too much space on the flash drive. How can I make it smaller?13.

Suspend won't work. How do I fix it?14. How do I listen to music with the lid closed?15.

How do I get wicd to automagically show me the networks available when my lxde desktop

starts?

16.

2.

1/4

10 FEV 2015


7/96

My fan won't start. How do I fix it?17.

Where can I get help?18.

Where is the latest version of this FAQ?19.

Links to basic knowledge

See ../HowTo/Install to learn how to install Debian on your Asus Eee PC.•

See ../HowTo/Troubleshooting for answers to problems arising from the initial install & configuration

of Debian on the Eee.

•

See ../HowTo/Upgrade after an upgrade.•

See ../TipsAndTricks to have many questions answered, before you even ask them.•

Frequently Asked Questions

Why do you make another fork of Debian to adapt it to the Asus Eee PC?

We don't. DebianEeePC is pure Debian. It's a DebianPureBlends project to make Debian work

optimally on the Eee. Our repository keeps just a few packages which cannot (yet) be in mainstream

Debian for some reason.

•

Do you provide a custom kernel specially adapted to the Eee PC

hardware?

Maintaining a custom kernel for special hardware is much more work then just finding the right

configuration and compiling kernels. Think of backporting all mainstream and Debian patches and all

the related testing needed to really support such a kernel over some time. As we aim to fully supportthe Eee in Debian itself and not a fork of Debian, we cannot depend on a custom kernel. Such a kernel

would never be a part of Debian.

•

Do I need a swap partition?

No, not really. The system works well without. The installer will try to convince you, that you do

need one, but it's up to you to decide. Putting more RAM into your Eee is often a better choice than

using swap.

•

What about hibernate if I have no swap?

Hibernate will not work without a swap space. However, it is possible to use a swap file created in the

following way:

dd if=/dev/zero of=/tmp/deletami bs=1024k count=512♦

•

This command creates a 512 MB swap file that can be used to hibernate the system. (Note that you'll

need a bigger swap file if you have more RAM).

•

How much RAM do I need?

Try it out. You will be surprised how much you can do even with 512 MB. But then, RAM is cheap

and does not drain too much battery power. So if you can upgrade to 1 G or 2 G it is certainly worth

it.

•

2/4


8/96

How much disk space does the installation take?

The aim is to provide a simple basic installation and let the user decide what he wants to add. A test

on 2008 April 10 with a base install, then package files cleaned and treated with localepurge needed

401 MB of disk space.

•

Do I need the EFI partition or is it safe to delete?

When Boot Booster is enabled in the BIOS data gets saved in the small EFI partition to speed up next

boot process. (See also http://en.wikipedia.org/wiki/EFI_System_Partition). It’s safe to delete that,

Debian won’t need it. Leave it in place if a short boot time is important to you.

•

Can I make a test install on removable media without changing the

existing OS?

Yes. See ../HowTo/InstallOnSDcardOrUsbStick.•

Can I install *to* a USB harddrive in an external case?

Yes. There are the same confusing device name changes as outlined in installing to USB flash media.

You will have to fix the installation before booting as outlined there. Booting with grub, you can press

'e' and change the disk where the kernel is loaded from.

•

Can I put the *installer* on an external harddrive and start installation

*from there*?

If you want to use your drive in “superflopp” mode (i.e. without partition table etc.) it should work.

But who would like to? Press on bootup and select your external drive to boot from, if you

want to do it.

•

Can I install from an external CDROM drive?

Yes. Press on bootup and select your cdrom drive.•

Can I mount an SD card at boot time?

Yes. However, due to the order in which rc scripts are executed during the boot process, automatically

mounting file systems on an SD card cannot be done as part of a mount -a invocation. You should

add noauto to the options, and explicitly mount the file system later on in the boot process, e.g. from

the /etc/rc.local file.

•

My system takes too much space on the flash drive. How can I make it

smaller?

The Debian eeepc system leaves you all the freedom to install/uninstall the software packages you

want. Use Aptitude or apt-get to do that. For suggestions of lightweight packages see ../Software.

../TipsAndTricks gives instructions how to make your system's footprint smaller, like deletingobsolete package files and localepurge.

•

3/4


9/96

Suspend won't work. How do I fix it?

The eee will not suspend unless your user is in the powerdev group. This affects users of power

managers (e.g. gnome-power-manager) as otherwise suspend is handled by acpid which runs as root.

•

How do I listen to music with the lid closed?

This is configurable in /etc/default/eeepc-acpi-scripts. Look for LID_CLOSE_ACTION and set it to

'nothing'. See /usr/share/doc/eeepc-acpi-scripts/examples for more information.

•

How do I get wicd to automagically show me the networks available

when my lxde desktop starts?

Add a desktop to your ~/.config directory with 3 lines saying

[Desktop Entry]

Type=Application

Exec=wicd-client -n

•

My fan won't start. How do I fix it?

It's probably a hardware fault. Disassemble your system, (caution, this may void your warranty,)

check if the fan is stuck, clean it and verify it spins easily again, reassemble your system. If that

doesn't work, see this post.

•

Where can I get help?

Your questions are welcome on our IRC channel #debian-eeepc at oftc

(irc://irc.oftc.net/#debian-eeepc ) or the mailing list. Please do read the information given in our wiki

pages first. Feel free to come back later and edit the wiki, if your question was not answered here.

•

Where is the latest version of this FAQ?

This FAQ is at kept up to date in our wiki due to the joint efforts of our developers and users like you:

http://wiki.debian.org/DebianEeePC/FAQ

•

DebianEeePC/FAQ (last edited 2010-05-11 23:42:46 by ?JoshDrizin)

MoinMoin Powered•

Python Powered•

Valid HTML 4.01•



4/4


10/96

Install-c1b91851e6c1e474d29597918abcabf7.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

DebianEeePC/HowTo/Install•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•HowTo•

Install•

Translations: French German Portuguese Italian Nederlands

Make a system backup.

Methods to backup and restore the Eee PC are found on the Tips And Tricks page.♦

1.

Determine your model.

Please find the Model page for your exact model number and read it first. Asus releases newmodels at a dizzying pace, often with deceptively similar-looking model numbers that have

entirely different hardware in them, so it is important to know what you have to choose an

appropriate install method.

♦

2.

Select an appropriate install method.

If you want to install Debian Wheezy (recommended), Use the Standard Installer HowTo.

This should cover most users, as you can install from the network or without, as well as

special needs like pppoe, lvm or crypto.

♦

If you want to install to a USB key or SD/SDHC card, follow SD Card or USB HowTo.♦

If you have no USB key, external hard drive, SD/SDHC card or CD/DVD-ROM , for

some models it’s possible to boot the standard installer over the network (though youcurrently need a USB ethernet adaptor). See Netboot HowTo.

♦

3.

DebianEeePC/HowTo/Install (last edited 2013-08-06 18:12:46 by GeoffSimmons)

1/2

10 FEV 2015


11/96

MoinMoin Powered•

Python Powered•

Valid HTML 4.01•



2/2


12/96

InstallUsingStandardInstaller-e4692af177b34e19305c0fa12cbb221d.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

InstallUsin...rdInstaller•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

HowTo•

InstallUsingStandardInstaller•

Translations: French, German, Portuguese, Italiano, Polish

Contents

Select Stable "Wheezy" installer or Oldstable "Squeeze"1.

Preparation2.

Installation3.

Configuration4.

Select Stable "Wheezy" installer or Oldstable "Squeeze"

Newer models are supported by Wheezy and older by both Wheezy and Squeeze. For more details, see the

wiki page for your ../../Model. If your model isn't listed, Debian may still work on it. Check the pages for

models with similar specifications and/or contact us.

Note: even if you do have an older model that works with Squeeze, there are many advantages to using

Wheezy, which was released May 4th, 2013.

1/3

10 FEV 2015


13/96

Preparation

Stable "Wheezy" system using the standard installer:

Download the Wheezy netinst ISO image from http://www.debian.org/CD/netinst/ . Choose either

i386 or amd64, depending on your model.

1.

Using an empty USB device, copy the image to the raw device (the ISO hybrid images can be copied

directly to the device; don't use unetbootin):

# cp debian-7.*-netinst.iso /dev/sdX # where sdX is the device your USB media is using

2.

Reboot and boot the netbook from the USB drive.3.

If your installer freezes after hitting "install", just hit "help" in the main installer menu, hit enter, wait

30 seconds and then enter again... this should work.

4.

Oldstable "Squeeze" system using the standard installer:

Download the Squeeze netinst ISO image from

http://www.debian.org/releases/squeeze/debian-installer/ . Choose either i386 or amd64, depending on

your model.

1.

Using an empty USB device, copy the image to the raw device (the ISO hybrid images can be copied

directly to the device; don't use unetbootin):

# cp debian-6.*-netinst.iso /dev/sdX # where sdX is the device your USB media is using

2.

Reboot and boot the netbook from the USB drive.3.

If your installer freezes after hitting "install", just hit "help" in the main installer menu, hit enter, wait

30 seconds and then enter again... this should work.

4.

Installation

Boot the Eee PC using the USB device (press ESC during boot; if this fails to bring up a device menu,

press F2 during boot, disable "Boot Booster" in the BIOS and retry).

1.

Follow the installer instructions.2.

Install the eeepc-acpi-scripts package for best results (additional hotkey support, etc. not provided out

of the box with base Debian install).

3.

Wifi drivers status

The kernel in Wheezy and Squeeze should already include a wifi driver for your model, except as indicated in

../../Models where no driver is yet available in Debian, so our repository is no longer needed.

Configuration

After installing the base system and wifi drivers, you may need to configure the system for wifi, webcam,

hotkeys, etc. to work. On Wheezy and Squeeze, some of these steps may no longer be necessary.

DebianEeePC/HowTo/InstallUsingStandardInstaller (last edited 2014-06-17 03:10:50 by ?StuartPrescott)

MoinMoin Powered•

Python Powered•

Valid HTML 4.01•

2/3


14/96



3/3


15/96

InstallOnSDcardOrUsbStick-7d7a863d214deba1b57ba07320758a45.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

InstallOnSDcardOrUsbStick•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

HowTo•

InstallOnSDcardOrUsbStick•

Translations: French German Russian

Contents

Introduction1.

Drawbacks2.

Installation on external flash drive: overview3.

Installing on SD cards or external flash drivesStarting installation1.

Partitioning a SD card or USB stick and mounting it2.

Installing the GRUB bootloader on an SD card or an USB stick3.

Fixing GRUB configuration and /etc/fstab4.

Fixing uswusp configuration5.

Inhibiting suspend6.

4.

Booting external media

Common case1.

Booting from SDHC card2.

5.

Introduction

1/7

10 FEV 2015


16/96

The limited storage capability of the Asus Eee PC is not adequate to keep multiple operating systems on the

internal flash drive. An SD or SDHC card (which can always stay in the built in card reader) or a USB stick

can be a very convenient medium to install another system and extended storage. This wiki page gives you

instructions how to do that.

This version of the page depends very much on the current versions of kernel, installer and the like; details

could change in the future. Please edit as needed.

?RobertEpprecht - This versions is based on Eee 701 models. Newer models have another disk layout.

Please give details if you try with other models. The page was written for 2.6.24 kernels and tested

succsessfully with the new 2.6.26 kernel version.

•

Tim_Auton - The default IO scheduler is cfq. There seems to be pathological behaviour on USB flash

and SD cards with this scheduler - it's slow and far from fair. Till this is fixed, use another scheduler.

Deadline appears to be the most effective. Add the kernel parameter "elevator=deadline" to the kernel

line in grub/menu.conf to use deadline as the default. Setting the fifo_batch parameter also helps

interactive response - batching reads or writes is good for minimising seeks, but is irrelevant for flashwith its constant access time. "echo 1 > /sys/block/sdX/queue/scheduler/iosched/fifo_batch".

•

ManfredWassmann - CHECK THIS: from what I googled you should use the noop scheduler with

SSD's (flash, SD cards etc.)

•

Drawbacks

A system on an external flash medium can be convenient and very usable. There are some drawbacks, of

course:

A system on a USB stick or SDHC card will be slower than on internal flash. Speed depends on

internal Eee hardware and the type of medium you use.

•

Never take out the card or stick before shutdown is complete; with a stick this could happen

unintentionally. Do not ask for a reboot (instead of shutdown) and remove the media between

shutdown and automatic reboot.

•

Some people had problems with the internal card reader. It is possible that newer models do not have

this problem any more or that it was caused by (non Debian) software or BIOS. Please report your

experience. (I am using a system on a SDHC card very intensively and did not see any problems so

far.)

•

Installation is not difficult, but device names keep changing in a very confusing way. (See 389881). If

you are doing it for the first time, the following step by step recipe tries to avoid this confusion.

•

For lvm or crypto, you may need to add rootdelay=10 to the kernel command line; see 366175 for

details.

•

Installation on external flash drive: overview

The installation process is pretty much straightforward. Read ../Install before proceeding. The main

difference to a normal installation is that you need to manually fix the bootloader configuration and

/etc/fstab. Device names do move around in a very confusing way. So here is a very detailed recipe to

avoid confusion and to show how to fix the faulty bits after running the installer. Sorry if it sounds

overly complicated.

•

Precautions should be taken that you will not suspend such a system.•

2/7


17/96

Installing on SD cards or external flash drives

Starting installation

Put the stick with the installer in the USB port on the left side.1.

Press to enter in the bios and disable bootboster, to save and exit - DavideCalcagnile.2.

Press while booting and select the stick to boot from.3.

Now put the SD or SDHC card into the built in reader. If you want to install to a USB stick put that

one in the second USB port on the right side, the first is closest to the plug ac.

4.

Start installation until partitioning. Select manual partitioning.5.

?RobertSchuettler] On our Eee-PC 701 there was a problem recognizing the SD card during

installation (16GB Transcend if that matters). The only available disks showing up for partitioning

were the internal one and the USB device that the installer itself bootet from. My (easy enough)

solution was to take the SD card out of the internal reader and stick it into the USB-reader that came

with the card, then re-detect disks and voila. Maybe this helps someone. Remember to check (and

probably edit) /etc/fstab if you do this though.

•

•

?Alexandru] It seems that if one puts first the root device (SDHC or USB) and after that the

installation media, the root device problem does not appear at all (no need to modify /etc/fstab). All

one needs is to change grub's menu.lst to point (hd0,0) for the SDHC / USB device with root

filesystem and (hd1,0) for internal SSD.

•

When I tried, I first enter in BIOS boot settings and changed devices settings (2-nd item) to show

SDHC card at the first line and the internal SSD at the second line. After that, I changed the boot

devices priority (1-st item) to boot from the installation USB-flash.

•

•

?RalfEngels] There are several people reporting problems with the internal SD card reader. The

symptoms are: stopping of the installation two thirds through. IO errors reported for the drive. The

partition is mounted read-only and remounting does not help. File system corruption.

•

These problems are caused partly by the SD-card reader, temperature, core voltage and an old bios.•

This post goes into details: http://forum.eeeuser.com/viewtopic.php?id=19216•

Also the Bios 0802 is reported to solve the problem.•

•

XTaran - Other SD card reader problems (throwing I/O errors, access is hanging) or hanging fdisk or

hanging grub os-detect can be caused by the BIOS setting "OS Installation". It seems as if must be set

to "finished" to make the SD card reader behave properly. See also

https://bugs.launchpad.net/ubuntu-eeepc-kernel/+bug/301932/comments/12

•

Partitioning a SD card or USB stick and mounting it

Spot the device you want to install to: the internal card reader is easy to find, the stick might show a

brand label, size or something else from which you can tell which stick is which. If you have no clue,

then assume the installer stick is on /dev/sdb1 and the target stick on /dev/sdc1 (if you did put it intothe USB ports I told you to).

1.

Write the name of the device down (It's very likely /dev/sdc1 with the current installer on a Eee 701).

You will need that device name later to know where to install the bootloader.

2.

3/7


18/96

On a pristine stick or card you will see one fat partition, select and delete it.3.

DavideCalcagnile - This step is not present in the installation with the image ...eeepc.img (16MB

network-based installer image)

•

select the ext2 file system because the ext3 file system with journalling is not working properly in

some cases

•

bootable flag does not exist as an option•

noted that to proceed with the partitioning•

•

Rudy X. Desjardins - Note, if you follow the preceding suggestion of using ext2 (vs. ext3), you must•

ommit the commit=120 option when editing fstab later, as the commit option is specific to ext3

filesystems and if left in, will

•

cause the system to fail remounting your final root fs as read-write. If you see a lot of failed startup

scripts for your default

•

runlevel (probably 2), and/or an error from the 'final' mount command, this is likely the culprit.•

Now you will see free space. Select that, and create a new primary partition. Accept the default size

to use the whole medium. You could leave space for a swap partition, but on a flash device it might

be quite reasonable not to have a swap partition. The installer will protest, but you can safely proceed

without. (If your machine allows it, you should consider adding more RAM instead.)

4.

Filesystem default ext3 is fine. Select mount option noatime (relatime does not work yet).5.

I would set a volume label like eeeSDcard or eeeStick.6.

Set the bootable flag.7.

Select 'Done setting up partition' and 'Finish partitioning and write changes to disk'.8.The installer starts to protest that you should have a swap partition, but you can safely continue

without. There will be more warnings about missing swap later on, so just keep your own opinion.

9.

Installing the GRUB bootloader on an SD card or an USB stick

Now let the installer do its thing until it wants to write the GRUB bootloader. Stop now. Do not

install the GRUB bootloader in the MBR.

1.

To install the bootloader on your external media you have to give the name of the device as the

installer sees it during installation. So install it to the device (without partition number) you wrote

down in the partitioner. On a 701 Eee model it will probably be /dev/sdc (*NOT* /dev/sdc1).

You can double check this by switching to console 2 (press + + and then

) and use the 'mount' command. It's the device where /target is mounted (without

partition number). Switch back to the installer by pressing + + .

♦

You install GRUB on a device like /dev/sdc but this will show up as /dev/sdb when the

system gets booted. Don't get confused, it is confusing.

♦

2.

Fixing GRUB configuration and /etc/fstab

Continue until the installer wants to reboot, but don't do that yet. We must correct the faulty disk

and device names in /boot/grub/menu.lst and /etc/fstab first. You can do that inside the installer

now, or you can decide to let the installer finish and mount the media somewhere else to fix thingsthere before rebooting the Eee. Next steps show how to do it in the installer.

1.

Switch to console 2 ( + + ).2.

4/7


19/96

The root of the installed system is mounted under /target during the instal. So if you edit the

files during installation make sure to edit the copy in the /target/ hierarchy! The other files in the

root filesystem are in the ramdisk and will be gone when you´ll reboot. Make a security copy,

something like

3.

cp -a /target/boot/grub/menu.lst /target/boot/grub/menu.lst.INSTALLER.back cp -a /target/etc/fstab /target/etc/fstab.INSTALLER.back4.

Check and edit the drive letter in /target/etc/fstab. / should be mounted on /dev/sdb1 (not /dev/sdc1)

nano /target/etc/fstab

it should look like this:

/dev/sdb1 / ext3 noatime,errors=remount-ro 0 1

Or even better, see http://www.cyrius.com/debian/nslu2/linux-on-flash.html

/dev/sdb1 / ext3 noatime,commit=120,errors=remount-ro 0 1

5.

Edit /target/boot/grub/menu.lst. The external media root should be on (hd0,0). Scroll down until

you see the entries for the installed system, it looks similar to this:

## ## End Default Options ##

title Debian GNU/Linux, kernel 2.6.26-1-686

root (hd2,0)

kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/sdc1 ro quiet

initrd /boot/initrd.img-2.6.26-1-686

...

### END DEBIAN AUTOMAGIC KERNELS LIST

Now change to 'root (hd0,0)' and '/dev/sdb1'. On a EeePC 701 it looks like:

title Debian GNU/Linux, kernel 2.6.26-1-686

root (hd0,0)

kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/sdb1 ro quiet


title Debian GNU/Linux, kernel 2.6.26-1-686 (single-user mode)

root (hd0,0)

kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/sdb1 ro single


The internal flash drive should be on (hd1,0) and /dev/sda(x). So for default xandros on the internal

drive you would edit the entries (farther down) to look something like this:

# This entry automatically added by the Debian installer for an existing

# linux installation on /dev/sda1.

title Normal Boot (on /dev/sda1)

root (hd1,0)

kernel /boot/vmlinuz-2.6.21.4-eeepc quiet rw vga=785 irqpoll root=/dev/sda1

initrd /boot/initramfs-eeepc.img

...

Now we must correct the entries for update-grub. They look like comments in the first part of the

same file. Edit the device in the kernel options to /dev/sdb1.

# kopt=root=/dev/sdb1 ro

and GRUBs root to (hd0,0)

# groot=(hd0,0)

6.

5/7


20/96

Now change back to console 1 ( + + ) and let the installer reboot.7.

See Booting external media for methods how to boot later.

Note by Kai Martens: On Eee PC 900 /dev/sdb will be the internal solid state harddrive. While all the (hd2,0)instances mentioned above must still be altered to (hd0,0), the /dev/sdc1 instances should not be altered to

/dev/sdb1 (neither in fstab, nor in menu.lst). If it is rebooted with /dev/sdb1 after loading the kernel there will

be three messages that mount failed and then the message that there is no file /sbin/init - your cue that you got

the (hdx,y) stuff right (found the kernel and ram image), but the /dev/sdxy stuff wrong...

Note by RGM: if your primary partition is Windows XP then you may need to add a map (hd1) (hd0)

command in addition to modifying the root entry.

map (hd1) (hd0)

rootnoverify (hd1,0)

savedefault

chainloader +1

•

Note by Marcos Talau: I had problems with the device names on 701. I recommend the use of labels for

GRUB and fstab.

Fixing uswusp configuration

If you have made a swap partition on your medium, you will probably see:

resume: libcrypt version: 1.4.0

resume: Could not stat the resume file: '/dev/sdc2'

...

That's uswusp configured on a wrong device name asking for the right one. Just ignore the question

and boot. Then do as root:

aptitude purge uswusp

aptitude install uswusp

On next boot you won´t be asked again.

•

Inhibiting suspend

Change the scripts under /etc/acpi so that they never do suspend. Otherwise you do risk integrity ofyour filesystem, and you will see damage on files opened to write. If you're like me and have the habit

of saving your work very often or let your applications do that for you, you can use the following

hack for this which just does shutdown instead of suspend. It dosn't even ask, who would answer the

question when you just closed the lid anyway? Edit /etc/acpi/actions/suspend.sh

#!/bin/sh

# do nothing if package is removed

[ -d /usr/share/doc/eeepc-acpi-scripts ] || exit 0

if (runlevel | grep -q [06]) || (pidof '/sbin/shutdown' > /dev/null); then

exit 0

fi

shutdown -h now

•

Probably we will have a better method of avoiding suspend, see 474531.

6/7


21/96

Booting external media

First you have to set the Boot Device Priority in the BIOS. Press after power on to set BIOS

parameters. The following settings seem appropriate:

1st Boot Device [Removable Dev.]

2nd Boot Device [HDD:SM-SILICONMOTI]

3rd Boot Device [ATAPI CD-ROM]

•

Common case

By pressing the key after power on, you can select the device to boot from.•

Booting from SDHC card

If you have your system on an SD card that you always leave in the slot, you might want to boot fromit directly. The card must be in the slot for the BIOS to show this option. Press after powering

on to see the BIOS. Go to the boot tab. If the card is in the slot, you will find the option > Hard Disk

Drives. Change the card reader to be the first drive. (Leave Boot Device Priority as shown above.)

From now on the Eee will boot from your card without having to press .

•

Attention: If you ever boot without the card the BIOS will silently revert this setting.•

CategoryFrGame

DebianEeePC/HowTo/InstallOnSDcardOrUsbStick (last edited 2011-08-07 11:45:41 by BenArmstrong)

MoinMoin Powered•Python Powered•

Valid HTML 4.01•



7/7


22/96

Configure-1ef2e37f19834dfd12d9ec8996a560d4.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

Configure•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

HowTo•

Configure•

Translations: French, German, ?Portuguese

Contents

Repository1.

Model specific issues2.

Additional modules not yet in Debian kernels

Introduction to building out-of-kernel modules1.Ethernet (atl2)2.

Bluetooth3.

Wireless (madwifi)4.

Webcam (uvcvideo)5.

Board, BIOS, ACPI (eeepc_laptop)6.

3.

Power management & hotkeys

Scripts (eeepc-acpi-scripts)1.

Hotkeys

Notes1.

2.

Power management

Super Hybrid Engine1. Notes2.

3.

4.

Xorg

Fonts1.

5.

1/12

10 FEV 2015


23/96

DRI2.

Touchpad Scrolling3.

Display resolution and desktop size4.

Display panning5.

Multiple displays6.AIGLX support for compiz7.

Hibernate (suspend-to-disk)6.

Graphical boot

Grub1.

Lilo2.

7.

Troubleshooting8.

Repository

The new installer adds our ../../Repository to your /etc/apt/sources.list automatically. This includes some

packages required to take full advantage of hardware in the Eee PC which not yet suitable for inclusion in theofficial Debian archives.

(The repository doesn't support squeeze, so I guess squeeze users don't need to add it?)

Model specific issues

Please go to ../../Models to find out about model-specific configurations.

Additional modules not yet in Debian kernels

Introduction to building out-of-kernel modules

The instructions below require you to install and compile module source packages using module-assistant.

This can be done on your Eee PC, but will result in the installation of a lot of development tools that you

might not otherwise need.

An alternative method is to do the installation and compilation of the modules on another Debian machine

(one that is faster and has more disk space), and then install the resulting module packages on the Eee PC.

If you decide to go this route, refer to the manpage for module-assistant. You will need to run

“m-a build …” instead of “m-a auto-install …”. Note that if your Eee PC is running a different kernelversion than your build machine, you will need to install the linux-headers and linux-kbuild packages

corresponding to the Eee PC's kernel, and use the -l option to specify that version when you invoke

module-assistant.

Note: m-a is an abbreviation for module-assistant which can be used as a command too. You can even

use “m-a a-i …” for “module-assistant auto-install …” on the command line.

Once you have successfully built a module, copy the resulting .deb to the Eee PC and install it there with

“dpkg -i …”.

2/12


24/96

Ethernet (atl2)

This just works now. The old version of our installer had a bug which required a manual install of atl2 after

installation – this is now no longer required.

Bluetooth

This uses the eeepc_laptop module, which is included with the latest debian kernels (Squeeze, for example,

includes it). You can toggle it manually by setting the value of /sys/class/rfkill/rfkill1/state, or

you can use eee-control. See http://hughperkins.com/techblog/?p=167 for details of installing and using

eee-control, or merge with this article.

Wireless (madwifi)

This is installed automatically by the new installer. See ../../HowTo/Wifi to set up wifi with or without

encryption.

If you have problems when trying to reactivate your Wireless connection with the hotkey, you may have to

ensure the module pciehp is loaded with the right options. See Power management & hotkeys

Webcam (uvcvideo)

Ever since kernel version 2.6.26 there is no need to build uvc module which is now included in.

Become root and type the following commands to enable camera in the BIOS:

echo "1" > /sys/devices/platform/eeepc/camera

The "uvcvideo" module should be loaded automatically.

You should see messages about the camera being detected:

dmesg | tail

Next, install some software to test it works. Become root and invoke the following command:

aptitude install luvcview mplayer

As normal user you can now make use of your web cam tool:

luvcview -f yuv

or, using mplayer:

mplayer -vf screenshot -fps 30 tv://

You can use 's' to take a single screenshot and 'S' to toggle on/off a series of screenshots (as fast as the system

can keep up). Use this to play back that sequence:

mplayer -fps 30 mf://shot*.png

If you broke your webcam settings, use mplayer -fps 30 tv:// once to restore them.

3/12


25/96

Board, BIOS, ACPI (eeepc_laptop)

This kernel module is present in 2.6.26 and later.

Power management & hotkeys

Scripts (eeepc-acpi-scripts)

This package requires the eeepc_laptop kernel module and is installed automatically by the installer.

Debian 6.0 "Squeeze" users: the eeepc-acpi-scripts package conflicts with acpi-support; as root, you must

apt-get purge acpi-support: this removes all of the acpi-support scripts that would remain in /etc. If

you do not follow this step, you will cause conflicts.

Since eeepc-acpi-scripts 1.1.11 (Debian 7 "Wheezy" and later releases), this no longer conflicts withacpi-support and now depends on it.

Enabling & disabling the wifi works like plugging & unplugging the PCI Express wifi card. If you have a

fresh install, this should just work. However, if you have an older install, ensure eeepc-acpi-scripts 1.1.0 or

newer is installed and 'pciehp' is not in /etc/modules (it'll be loaded automatically if needed).

If you're sticking with an older eeepc-acpi-scripts, then make sure that pciehp is mentioned in /etc/modules`. If

it isn't, run echo pciehp >>/etc/modules as root.

Read the doc in /usr/share/doc/eeepc-acpi-scripts/README.Debian and configure

/etc/default/eeepc-acpi-scripts as needed.

Hotkeys

Special keys

KeyFunction Work, comment

< 10" 10"

Fn + F1 sleep Yes

Fn + F2 wifi Yes (read details below)

Fn + F3 Touchpad on/off WIP (git only)

Fn + F4 Change resolutionFn + F3 Fn + F5

Panel brightness YesFn + F4 Fn + F6

Fn + F7 Backlight off Yes (git only)

Fn + F5 Fn + F8 Change screen Yes

Fn + F6 Fn + F9 Task manager No (unused)

Fn + F7 Fn + F10 Sound on/off Yes

Fn + F8 Fn + F11Volume Yes

Fn + F9 Fn + F12

4/12


26/96

Notes

[Lutz] "Volume Up/Down/Mute" Solved - With kernel 2.6.25 and default ALSA installation I had problem

with audio hotkeys (alt + f7,8,9). Sleep and wireless button work fine but volume does not change. That's why

the Hotkey event is correctly handled, but the acpid action works on the ?LineOut Channel that, on myeee701, is not present or has a different name. You can fix it by editing

/etc/default/eeepc-acpi-scripts and modifying this line as follows:

VOLUME_LABEL='Master'

You can also run amixer to have a look at channel names, so you can assign a different mixer channel to

volume hotkeys. The Mute key, simply set the selected channel as mute. [Jetxee] "Volume Up/Down/Mute"

did not work on my eeepc 901, kernel 2.6.26-1-686 and default alsa 1.0.16-2. Also the mic did not work

properly. After installing hda-intel drivers from alsa 1.0.18a both problems were solved. I didn't have to edit

eeepc-acpi-scripts, because with a new alsa the channel is named properly. I am using eeepc-acpi-scripts

1.0.9.

As of eeepc-acpi-scripts 1.1.1:

eeepc-acpi-scripts no longer manages lid events. If you don't use a power manager and want your

netbook to go to sleep when you close the lid, you can configure acpi-support accordingly in

/etc/default/acpi-support.

•

The default action for the volume keys has been changed to NONE. New kernels generate XF86

keyboard events that are properly handled by most desktop environments; if you prefer the old

behaviour, edit /etc/default/eeepc-scpi-scripts.

If your desktop environment doesn't handle the volume keys by default, you can probably

configure it to (e.g. if you have Openbox add keybindings to rc.xml:

http://crunchbang.org/forums/viewtopic.php?pid=40192).

♦

•

[_ds_] If you use slim as your login manager and xtrlock to lock the X session, you should edit

/etc/slim.conf as shown following this paragraph. When going to sleep, eeepc-acpi-scripts 1.0.12 will

use xtrlock if possible (and other locking mechanisms fail); without this change, xtrlock will want the root

password unless you have a terminal window open. (Or at least I find that it does; it's to do with the X session

not having been registered in utmp.)

sessionstart_cmd exec sessreg -a -l :0 %user

sessionstop_cmd exec sessreg -d -l :0 %user

Power management

On some models, the battery info is not very precise (jumps from 10% to 100%, no rate information, etc.).

Apparently, this is normal. It appears that the userspace battery utilities expect the battery to report mAh, but

in fact it reports percentage. This is either a bug in the battery firmware or a bug in the BIOS; it is known to be

fixed with newer BIOS versions and kernels ≥ 2.6.25.

Super Hybrid Engine

As of kernel 2.6.30, the "Super Hybrid Engine" is supported: /sys/devices/platform/eeepc/cpufv

contains a value which is 256× the number of available settings plus the current setting; you write a number n

(0 ≤ n < number of available settings) to it to alter the setting.

On Celeron-based models, there are two settings.

5/12


27/96

On Atom-based models, there are three settings:

high speed (1.8GHz)0.

normal speed (1.6GHz)1.

low speed (1.2GHz)2.

This is fully compatible with cpufreq. For example, in low speed mode, Atom-based models are able to switch

between 600MHz, 800MHz, 1GHz and 1.2GHz as needed. However, cpufreq is unaware of the S.H.E. and

will report speeds as being between 800MHz and 1.6GHz.

As of version 1.1.2, eeepc-acpi-scripts supports these plus "auto" mode (which will, by default, try to

underclock when on battery), but no key is assigned by default

Notes

[?DamyanIvanov] Hibernation mostly works for me on current Sid with 2.6.24 kernel once I've set up swap(and following the hints from ../../TipsAndTricks). There is some problem with the madwifi driver that does

not recover completely, but I think it is not hibernate-related as I see the same behaviour after

suspend/resume.

[SamMorris] suspend worked for me with 2.6.24 with the s3_bios and dpms_on quirks. I have sent a patch

upstream to [email protected] and also filed 469648.

Xorg

Fonts

Sub-pixel ordering (with some uncertainty) is red, green, blue from left to right. Observed by magnifying lens.

DRI

Install the package libgl1-mesa-dri so that DRI can be enabled, providing 3D hardware acceleration.

For the 901, at least, you'll also need to install "libglu1-mesa" to enable DRI.

Touchpad Scrolling

See SynapticsTouchpad, unless you're using lenny on a model with an Elantech touchpad.

Display resolution and desktop size

In /etc/X11/xorg.conf, make sure any "?HorizSync" and "?VertRefresh" lines are commented out or removed

from the "Monitor" section and set "Virtual 2048 2048" in the "Display" subsection of your "Screen" section,

e.g.

Section "Monitor"

Identifier "Generic Monitor"

EndSection

Section "Screen" Identifier "Default Screen"

Device "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"

Monitor "Generic Monitor"

6/12


28/96

DefaultDepth 24

SubSection "Display"

Depth 24

Virtual 2048 2048

EndSubSection

EndSection

After a fresh Lenny installation on a 1000HA, I found the GNOME text to be unreasonably large. Apparently

this is because X determines the DPI according to the screen resolution, 1024x768, and reported physical size

of the screen. The result on my 1000HA is 118 DPI:

$ xdpyinfo | grep resolution

resolution: 118x118 dots per inch

$

I used the temporary workaround from this bug report (510123) and added to the end of my gdm.conf:

[server-Standard]name=Standard server

command=/usr/bin/X -audit 0 -dpi 96

flexible=true

Display panning

There is a good utility here to permit display panning on 701.

Multiple displays

If you plug in an external display and press Fn+F5, the desktop is shared between the LCD and external

display by default.

If you want, instead, to have one big desktop with the external display positioned above the Eee's own display,

ensure that you have set the Virtual size large enough to accommodate both displays as shown above and then

edit /etc/default/eeepc-acpi-scripts to set:

COMBINED_DISPLAY_SWITCHES="--above LVDS --auto"

See xrandr(1) and /etc/acpi/actions/vga-toggle.sh for other possible parameters.

If one setting is not working when you press Fn+F5, you might want to check for error messages: run

/etc/acpi/actions/vga-toggle.sh from command line.

Note that icewm (in lenny) currently has some problems moving a window between the two displays, see bug

512109 for details.

AIGLX support for compiz

The following were needed to get Compiz working. Compiz works for me with xfce, but its a bit choppy

rotating the cube to a workspace that has opened programs on it. (If you have a good working xorg.conf thats

different to this, please update)

Section "Device" Identifier "Configured Video Device"

Driver "intel"

BusID "PCI:0:2:0"

7/12


29/96

Option "EnablePageFlip" "on"

Option "AccelMethod" "XAA"

Option "MigrationHeuristic" "greedy"

Option "AccelDFS" "true"

Option "DynamicClocks" "on"

Option "ColorTiling" "on" Option "FBTexPercent" "95"

Option "XAANoOffscreenPixmaps" "true"

Option "AddARGBGLXVisuals" "true"

EndSection

Section "DRI"

Mode 0666

Endsection

Section "Extensions"

Option "Composite" "Enable"

Endsection

Notes:

[cmang] When following the above instructions, I was unable to get any window borders and window

management when starting Compiz. In addition to the above, I had to install the

compizconfig-settings-manager package. Then I ran ccsm and made sure that the "Window

Decoration" plug-in was enabled. I then had to start compiz with compiz --replace cpp

•

[?AndrewSmart] The XAA method of acceleration had been dropped in recent versions. In the

xserver-xorg-video-intel package v2.21.15 the UXA render acceleration is default. UXA is lower

performing than the newer SNA, so try it out and check your Xorg log to verify it works. XvMC

hardware video acceleration is disabled by default (current support for MPEG2 MC on 915/945 and

G33 series). Here is my configuration (for Intel GMA 950 graphics, 945GSE chipset):

•

Section "Device"

Identifier "Device0" Driver "intel"

Option "AccelMethod" "SNA"

Option "XvMC" "1"

EndSection

Xorg uses less CPU and the netbook runs cooler. I suggest you read the man page for intel(4) for

settings specific to your driver version. Also if you have a 915/945 chipset (other 3rd/4th gen appear

affected as well), you're probably prone to choppy 3D behaviour:

https://bugs.freedesktop.org/show_bug.cgi?id=30364 Apparently wiggling the mouse or playing a

song (keeping the CPU busy) will keep the graphics smooth by keeping the CPU from entering a deep

sleep state. This is apparently a "known design feature of the power management hardware" and the

Intel DRI devs (Chris Wilson et al.) were unable to find an acceptable workaround.

•

Hibernate (suspend-to-disk)

[?DamyanIvanov] Hibernate worked for me just fine after I've set up a 256M dedicated SWAP partition.

Perhaps the same is possible using swap files too. The only glitch is that I have to quit memory-hungry

programs like Iceweasel before attempting hibernate, as otherwise the swap space is not enough. To hibernate,

run s2disk as root (from the uswsusp package). If you use gnome-power-manager you can just press the

power button (but remember to disable the button action in /etc/acpi/actions/power.sh installed by

debian-eeepc-scripts to avoid double prompts).

[?OzeLot] Hibernation (suspend-to-disk) is easy on Debian/lenny with 2.6.26-kernel, when a swap-partition is

active (eeepc 901). This is an example:

8/12


30/96

Create a swap partition of 512 MB:

cfdisk /dev/sdb --> New --> Type 82 Linux Swap --> write --> reboot

Make an entry in /etc/fstab, if sdb2 should be your new swap-partition:

/dev/sdb2 none swap sw 0 0

Format the swap space:

mkswap /dev/sdb2

Make active with:

swapon -a

(or just reboot the system).

Install acpid, eee-acpi-scripts (the latest version from sid), uswsusp and pm-utils. splashy is not nescessary at

this moment.

If you want to use the swap-partition primarily for hibernation, make this entry in /etc/rc.local (somewhere

before exit 0):

sysctl -w vm.swappiness=1

You should now be able to hibernate with the root-command s2disk. A compressed image of your

system-state is written to the swap and then the eeepc 901 shuts down. The image is loaded again by Power

ON.

Suspend and resume with s2disk last 15-20 seconds on my system.

[?ArturCzechowski] I'd like to confirm that suspend/resume on both: ram and disk work without problem on

901. Only path I haven't tested (yet) is: suspend to ram → battery low → automatically suspend to disk →

resume. I'll test it this night (CET).

[Lancelot] Suspend-to-disk does not work for me, using the instructions provided by Ozelot above. s2ram

complains that "machine is unknown". s2disk and s2both both yield the following behavior: they do seem to

write to my swap partition and suspend normally, but upon pressing the power button, it does not resume but

instead goes through a normal boot sequence... EDIT: Yeah! I tried:

dpkg-reconfigure uswsusp

And then answered questions to the best of whatever very little knowledge I have. For some reason,

the dpkg-reconfigure provides a myriad of prompts that did not come with the initial aptitude

installation. Here is a config file that works for me:

•

# /etc/uswsusp.conf(8) -- Configuration file for s2disk/s2both

resume device = /dev/sdb1

compress = y

early writeout = y

image size = 239158312RSA key file = /etc/uswsusp.key

shutdown method = poweroff

suspend loglevel = 1

9/12


31/96

max loglevel = 1

In the above, you'll probably have to change the name of the resume device to the name of your swap

partition.

This could have been this bug: 495319. Indeed, the config file I got after a clean install had 'platform' as the

shutdown method. Note that the "Shutdown method" option does not seem to be explained in the man page of

uswsusp.conf

s2ram still does not work, though I don't really care since I can just Fn+F1.

I still have a minor annoyance: upon resume, it complains that it can't stat my resume device and prompts me

for a device path. I have to type it by hand for it to resume.

[lancelot] It worked... yesterday. Since then, I tried a couple of configuration changes, which I don't think are

the cause for my current problems, and I also did a normal reboot. The latter has been the start of my new

issues. Now, everytime I try to make a suspend-to-disk/resume, it does not resume but I get a message that

recovery is required on readonly filesystem (this ought to be my root filesystem /dev/sda1), then it proceeds

with a "successful" recovery instead of resuming, then does a normal boot. But on the next resume attempt

exactly the same thing happens, recovery is again required on the readonly filesystem. it looks like I did

something faulty which severely messed with my internal flash drive. I can only hope the drive is not

physically damaged. I think I will just attempt to reformat /dev/sda1 and reinstall debian completely... maybe

tomorrow, more probably in a couple of weeks, months, I don't know, when I have the time. This leaves me

discouraged about running Linux on those flash drives.

See also Hibernation and perhaps more importantly Hibernate without swap partition

Graphical boot

This splashy package will enable a graphical status boot screen for your EEE, which is far pretier than that

bunch of characters scrolling up the screen (OK, for a server, not for a mobile workstation). It may not work

with KMS.

To install splashy:

aptitude install splashy

Now it is time to configure your boot loader.

Grub

With grub, edit /boot/grub/menu.lst file and add

hiddenmenu

to avoid showing that blue screen. Also remove the timeout, changing the timeout line to:

timeout 0

You will find a commented-out line similar to this:

# defoptions=quiet

10/12


32/96

With Intel graphics, the panel's native mode will be selected as soon as the i915 module is loaded if

KMS is active. With xserver-xorg-video-intel 2.10, KMS is required since support for XAA and EXA has

been removed.

Add these (read below):

# defoptions=quiet splash vga=788

the vga=788 stands for 800x600, suitable for 900 model. Previous models should try vga=785, which stands

for 640x480. There is a black magic way to make it work at native resolutions, which if you know, please

write it here. Some ugly hack, at least for kernel 2.6.25, is described here: Splashy and native resolution of

Display.

With Intel graphics, the panel's native mode will be selected as soon as the i915 module is loaded if

KMS is active. With xserver-xorg-video-intel/unstable 2.10, KMS will be required since support for XAA

and EXA has been removed.

To update the changes, run:•

update-grub

That’s it. You should have your graphical boot working. Also try the splashy-themes package for some other

themes. (There are Debian themes in the package. splashy_config --info will show the available

themes and splashy_config -s themename will set a theme. Remember to run

update-initramfs -u every time you change the theme.)

If at install time you have chosen grub-pc instead of grub, you should edit default config file,

/etc/default/grub, adding this variable:

GRUB_CMDLINE_LINUX_DEFAULT="splash vga=788"

[?JohanLaenen] GRUB_CMDLINE_LINUX_DEFAULT="splash vga=788" works like a charm but is

deprecated. I had no success changing GRUB_GFXMODE. See 536453 for more info.

and setting

GRUB_TIMEOUT=0

as well. Then update config changes executing 'update-grub2'. NOTE: For my 4G, vga=788 doesn't work,

vga=786 seems to work fine.

[?LuizGuaraldo]: I was successfull with usplash, no vga option needed. Just need to put insmod intelfb

right over insmod png on /boot/grub/grub.cfg (grub2 - grub-pc).

Lilo

With Lilo edit /etc/lilo.conf:

Find the line with "vga" and write:

vga=788

11/12


33/96

the vga=788 stands for 800x600, suitable for 900 model. Previous models should try vga=785, which stands

for 640x480. There is a black magic way to make it work at native resolutions, which if you know, please

write it here. Some ugly hack, at least for kernel 2.6.25, is described here: Splashy and native resolution of

Display

Find the line with "append" and write:

append="quiet splash vga=788"

To update the changes launch lilo.

Troubleshooting

If you have problems with any of the steps above, see our Troubleshooting HowTo.

DebianEeePC/HowTo/Configure (last edited 2014-12-11 16:22:51 by ?AndrewSmart)

MoinMoin Powered•

Python Powered•

Valid HTML 4.01•



12/12


34/96

Sound-a81e650f66f44eb926dd34a954a1626d.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

DebianEeePC/HowTo/Sound•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

HowTo•

Sound•

Translation(s): French German Portuguese

Sound for most Eee PC models with Alsa should ‘just work’. The following are tips to make it work optimally

for certain applications or to work around problems with specific models.

Contents

Model 900A, 901, 1000, 1000H, and 1000HE front Microphone1.1001PX [a.k.a. R101 in Germany] built-in microphone2.

Alsamixer

ALSA configuration1.

3.

Install an updated Alsa driver4.

Testing your updated driver5.

ALSA OSS6.

Alternate versions: updated kernel or upstream source for Alsa driver7.

Skype (and any other application which only uses Left channel of Front Mic.) Workaround8.

KMix and other mixers for your desktop9.

Model 900A, 901, 1000, 1000H, and 1000HE frontMicrophone

1/11

10 FEV 2015


35/96

See Install an updated Alsa driver below.

1001PX [a.k.a. R101 in Germany] built-in microphone

With Linux 2.6.32-29, built-in microphone of my 1001PX did not work (it recorded just a noise). How I made

it to work: install Linux 2.6.37~rc7-1~experimental.1, boot to the original Windows XP, record there some

sound and play it; then reboot (without turning the PC off) to Linux 2.6.37, record there some sound (it

worked now but the audio playing was broken now); reboot Linux 2.6.37: now and after any other reboots

both playing and recording worked.

for me worked Out-Of-The-Box with kernel 2.6.37-trunk-686 from the experimental repo without any trick,

config or workaround. external mic NOT tested, maybe working with "options snd-hda-intel model=fujitsu" in

/etc/modprobe.d/alsa-base.conf

AlsamixerIf you’re setting up your system to use an application like Ekiga to do VoIP/video conferencing then you will

probably want to know how to use alsamixer utility to access the low-level mixer channels on your audio card.

There are GUI versions of alsamixer, but the alsamixer program is almost always installed by default. It is

provided by the alsa-utils package.

To use it open up a terminal and use the 'alsamixer' program. It has three views (Playback settings, Capture

settings, all settings) and you can switch between them with the tab button. You can press left arrow key or

right arrow key to move from mixer to mixer and up arrow and down arrow key to change volumes. The m

button will toggle mute for the devices that support it and space bar will toggle capture status for settings that

support that (be sure to enable this, or the microphone will not work). The '?' button will show the help dialog

for more controls.

For the EeePC’s microphone you’ll probably want to adjust these settings: use the tab button to select the all

view.

Arrow over to the capture setting and toggle it on using the space bar. Make sure the volume is around 70 %.

Make sure that i-mic (internal mic) is selected as the input source. (If i-mic doesn’t appear, try Front Mic.)

Press up and down arrow to select input device.

Arrow over to the i-mic mixer settings. Set the volume at 70 % and then set the i-mic boost to 33 %.

That should give a good basis for playing around with your own settings till you get it perfect. The i-mic boost

should be set to zero or 33 %. Anything above that and I get horrible sound distortion through Ekiga.

For testing audio performance Audacity is a good choice. Make sure that you go through the preferences and

it is setup to use ALSA.

GNOME Sound Recorder application from gnome-media is ok for doing recording. You just have to make

sure that the codec it uses is either WAV, ?MP3, or speex when doing the recording. The default is to use

Ogg/Vorbis and the EeePC isn’t quite fast enough to do that encoding in real-time leading to very bad sound

quality.

2/11


36/96

ALSA configuration

This can improve performance for your sound system when playing multiple sounds, recording to multiple

programs, playing games, or watching videos on your EeePC.

For more details on what this file is and what to do with it see http://alsa.opensrc.org/.asoundrc.

pcm.my_card {

type hw

card 0

# mmap_emulation true

}

pcm.dmixed {

## This provides software mixing for audio out

type dmix

ipc_key 1024

slave {

pcm "my_card" ## period_size and buffer_size

## can be modified to reduce

## latency or add more 'cusion'

## through the buffer

period_size 1024

buffer_size 4096

rate 44100

}

}

pcm.dsnooped {

## this provides software mixing for audio in

type dsnoop

ipc_key 2048

slave { pcm "my_card"

period_size 1024

buffer_size 4096

rate 44100

}

}

pcm.asymed {

## this plugin allows you to bind both

## the dmix and dsnoop plugins together

type asym

playback.pcm "dmixed"

capture.pcm "dsnooped"

}

pcm.pasymed {

## if you do not want to use use

## mixing by default, you can delete

## !default entry below and direct

## apps to use this 'device' as a

## extra option

type plug

slave.pcm "asymed"

}

pcm.dsp0 {

## this allows most OSS-only apps

## to use this mixing stuff

## through the use of the aoss wrapper

type plug slave.pcm "asymed"

}

pcm.!default {

3/11


37/96

## this makes alsa apps default

## to use this config

type plug

slave.pcm "asymed"

}

Install an updated Alsa driver

A convenient way to update your Alsa driver is to use the alsa-source package from testing (1.0.20+dfsg-1 as

of the time of writing). Set up installs from testing using ?AptPinning and:

aptitude install module-assistant

m-a prepare

aptitude -t testing install alsa-source

m-a build alsa

m-a install alsa

Or instead of using ?AptPinning, just download the deb for alsa-source directly from your mirror, use

dpkg -i to install it, and then module-assistant as per above.

Testing your updated driver

After updating the alsa driver, you need to reboot or, alternatively you exit all audio applications (including

any mixer application) and unload the old kernel modules. Then load the newly installed modules by hand

(the commands were tested on EeePC 901):

rmmod snd_hda_intel snd_pcm snd_timer snd soundcore snd_page_alloc

modprobe snd_hda_intel

After the new modules are loaded either because of reboot or you loaded it by hand, have a look at your mixer

settings with alsamixer or the gnome-volume-control, the channels have changed from the stock driver. Note

that if you loaded the modules by hand you need not to do it again after a new reboot.

The contols of the stock driver looks like this in alsamixer:

4/11


38/96

The controls of the updated drivers looks like this in alasamixer:

5/11


39/96

6/11


40/96

FixMe: the following advice is in dispute. We need to correct it, simplify it and/or fix it in the

eeepc-acpi-scripts package.

Playback: PCM. this is the master volume for the speakers•

Playback: ?LineOut. this is the volume for the headphone socket•

Recording: Capture. this is the record level for the front mic. it only seems usable at about 30%

otherwise it’s just really distorted

•

Recording: Digital. this is the record level for the external mic in. It’s a lot quieter than the front mic

even at 100%, perhaps we’re missing some ?MicBoost like the stock driver has.

•

To get your hot keys to work again you need to edit /etc/default/eee-acpi-scripts and change the mixer labels

VOLUME_LABEL='LineOut'

VOLUME_LABEL='iSpeaker'

to

VOLUME_LABEL='PCM'

VOLUME_LABEL='LineOut'

[psyche] Are you sure there should be two VOLUME_LABEL keys? I think for the second item should be

HEADPHONE_LABEL='?LineOut'

[?TimoZimmermann] After installing eeepc-acpi-scripts 1.0.10 the following steps were unnecessary for me.

You also need to add the line

I_SWITCH_LABEL='iSpeaker'

This should get the volume keys working again.

To get the mute key to work you need to edit /etc/acpi/actions/hotkey.sh. Comment out the line (around line

number 50)

status=$(amixer get $VOLUME_LABEL | sed -n '/%/{s/.*\[$on\|off$\].*/\u\1/p;q}')

7/11


41/96

and add this line underneath it

status=$(amixer get $I_SWITCH_LABEL | sed -n 's/.*\[$on\|off$\].*/\1/;ta;d;:a;p;q')

Further down in the ‘# Fn+F7 -- mute/unmute speakers’ section, comment out the line

amixer -q set $VOLUME_LABEL toggle

and add instead

amixer -q set $I_SWITCH_LABEL toggle

You should now be all set.

ALSA OSS

On my system the oss_mixer did not work at all (using i.e. wmmixer as ?DockApp in fvwm2). The reason

seemed to be the mapping of ALSA to OSS by kernel module snd_mixer_oss. It can be seen in

/proc/asound/card0/oss_mixer. On my system i saw no matchings:

eee1000:~# cat /proc/asound/card0/oss_mixer

VOLUME "" 0

BASS "" 0

TREBLE "" 0

SYNTH "" 0

PCM "" 0

SPEAKER "" 0

LINE "" 0

MIC "" 0CD "" 0

IMIX "" 0

ALTPCM "" 0

RECLEV "" 0

IGAIN "" 0

OGAIN "" 0

LINE1 "" 0

LINE2 "" 0

LINE3 "" 0

DIGITAL1 "" 0

DIGITAL2 "" 0

DIGITAL3 "" 0

PHONEIN "" 0

PHONEOUT "" 0VIDEO "" 0

RADIO "" 0

MONITOR "" 0

The right mappings can be written to the file when booting by adding these four lines to the end of

/etc/init.d/rc.local file:

echo 'VOLUME "PCM" 0' > /proc/asound/card0/oss_mixer

echo 'LINE "LineOut" 0' > /proc/asound/card0/oss_mixer

echo 'MIC "Capture" 0' > /proc/asound/card0/oss_mixer

echo 'PHONEIN "Digital" 0' > /proc/asound/card0/oss_mixer

Afterwards we have a working configuration:

eee1000:~# cat /proc/asound/card0/oss_mixer

8/11


42/96

VOLUME "PCM" 0

BASS "" 0

TREBLE "" 0

SYNTH "" 0

PCM "" 0

SPEAKER "" 0LINE "LineOut" 0

MIC "Capture" 0

CD "" 0

IMIX "" 0

ALTPCM "" 0

RECLEV "" 0

IGAIN "Capture" 0

OGAIN "" 0

LINE1 "" 0

LINE2 "" 0

LINE3 "" 0

DIGITAL1 "" 0

DIGITAL2 "" 0

DIGITAL3 "" 0PHONEIN "Digital" 0

PHONEOUT "" 0

VIDEO "" 0

RADIO "" 0

MONITOR "" 0

Alternate versions: updated kernel or upstream source for

Alsa driver

Although the alsa-source from testing should be sufficient to solve the front mic issue, if you are interested in

trying new things, you may instead use a more recent kernel or get the latest alsa driver from upstream.

TODO: List reasons why a user would want to do this instead of just using the recommended testing

alsa-source.

Linux kernel 2.6.28-rc1 and later contain a sufficiently-recent ALSA driver. If you have that version or

later (if you're using a stock lenny kernel, you don't), there is no point in you rebuilding the driver.

Otherwise, grab the upstream source from here: ftp://ftp.alsa-project.org/pub/driver/. At the time of writing,

alsa-driver-1.0.18a.tar.bz2 is current. We have verified that 1.0.18rc1 works as well.

You will need the appropriate linux-headers package installed.

Next you need to unpack it somewhere like /usr/src/ then build it. You may want to backup your old driver

first

/lib/modules/2.6.26-1-686/kernel/sounds/pci/hda/# cp snd-hda-intel.ko snd-hda-intel.ko.stock

/usr/src/alsa-driver-1.0.18rc1# ./configure --with-cards=hda-intel --with-options=all

/usr/src/alsa-driver-1.0.18rc1# make

/usr/src/alsa-driver-1.0.18rc1# make install

/usr/src/alsa-driver-1.0.18rc1# ./snddevices

According to the INSTALL file in alsa-driver, the last step is unnecessary when running udev. That file also

recommends using 'make install-modules' rather than 'make install', assuming that the Debian alsa-utils and

alsa-base packages are already installed.

You can verify your new driver with

9/11


43/96

ls -l /lib/modules/2.6.26-1-686/updates/alsa/

Check that the date on the snd-hda-intel.ko is about the time you compiled it

Now follow the rest of the instructions from Testing your updated driver.

Problem with no sound on eee PC 900 running linux-image-2.6.30-1-686 kernel can be solved by upgrading

the laptop`s BIOS. Files with new BIOS can be found at http://support.asus.com/download . A good manual

about how to update: http://www.blakeanthonyjohnson.com/?p=170 If you are following this manual and

getting errors "USB Device not found" while updating, try using another flash-drive (for me it worked with

512Mb Transcend JF160). After updating and loading the system press Fn+F7 keys to turn the sound on (even

if mixers show that sound is unmuted).

Skype (and any other application which only uses Left

channel of Front Mic.) Workaround

On my EeePC 901 ([?JesseWyant]), the "Front Mic." is a stereo channel, with the Left channel appearing to

be the difference of the left microphone and the right microphone, and the Right channel representing the sum

of the two microphones. (At least, using Audacity to capture sound clips using the stereo Front Mic., and

comparing the two channels, leads me to this conclusion.) The end result is that the Left channel is very quiet,

and the Right channel has the expected loudness.

Unfortunately, some applications (like Skype) only use the Left channel of the Front Mic., and as a result the

microphone audio is too quiet.

Here's an example .asoundrc snippet which illustrates a means to swap the Left and Right channels from the

Front Mic. Then, from within Skype's Audio settings menu, you may select the "skype" audio capture device(to use the Right channel):

pcm.skype {

type route

slave.pcm "hw:0,0"

#slave.pcm "dsnooped" # Also worked. Which would be preferable?

ttable.0.1 1

ttable.1.0 1

}

KMix and other mixers for your desktop

If you use a mixer for your desktop (such as KMix on KDE), you may need to change the channel shown to

match the name of the channel that is displayed when you press the volume keys. This name differs from

model to model and it is indicated in your /lib/init/rw/eeepc-acpi-scripts.sound (variable

DEF_SOUND_LABEL).

For instance, on 4G model and KMix, Select Master Channel... --> Line-Out

CategorySound

DebianEeePC/HowTo/Sound (last edited 2011-02-04 15:21:52 by ?LucaGentile)

MoinMoin Powered•

Python Powered•

10/11


44/96

Valid HTML 4.01•



11/11


45/96

TipsAndTricks-9a50af61ce8e6eac3a747b0f3b1ee25c.html.tgz.pdf

Wiki

Login

FrontPage•

RecentChanges•

FindPage•

HelpContents•

DebianEeePC/TipsAndTricks•

Search:

Wiki/

Login•

Comments•

Info•

Attachments•

More Actions:•

DebianEeePC•

TipsAndTricks•

Translations: French, German, Spanish, Portuguese

Contents

Extending flash memory life1.

Text Mode2.

Desktop environment3.

Accessing the Asus Restore Image4.

Make a complete disk imageBackup1.

Extract some files from the image2.

Restoration3.

5.

Freeing Disk Space6.

Software Control of the fan speed7.

Speed up boot process8.

Turn off the internal display when using VGA out9.

Speed up X1110.

Fixing iPod file reading11.

Custom Compiled Linux

Outstanding Issues and Questions1.

12.

Visual state and switching of Cam, Wlan and Card reader on the tray13.

Models with a slow SSD

Speed up sluggish Iceweasel/Firefox 31.

14.

1.

1/11

10 FEV 2015


46/96

Slow Vim writes2.

Slow intel rendering15.

Wireless

Workaround RT2860sta crash on suspend

RT2680STA authentication timeout (WPA2)1.

1.

2.

Extending flash memory life

It is a commonly accepted view that SSD devices can only be written a limited number of times before they

die, and while that may have been a concern for earlier generations of devices where that limit was relatively

low, modern SSDs, such as the one in the Eee increase that number sufficiently so that they will last many

years before they die, outlasting any HDD. Before you spend herculean efforts to extend your Eee's flash

lifespan, consider this article: http://wiki.eeeuser.com/ssd_write_limit. Nevertheless, many tips are easy to do

and at the very least are harmless, or have other benefits (such as less time spent doing IO making your system

more responsive,) so here are a few.

Open /etc/sysctl.conf and set vm.dirty_writeback_centisecs = 1500. This will prolong the life of your

SSD by writing to the disk every 15 seconds instead of 5.

•

Probably many of the tips useful for Linksys on NSLU2 can be applied to the EeePC.•

Use tmpfs for directories whose content doesn't need to be preserved over shutdown/reboot:

/tmp

echo 'tmpfs /tmp tmpfs defaults 0 0' >>/etc/fstab

/var/run & /var/lock

set RAMRUN=yes and RAMLOCK=yes in /etc/default/rcS

/var/cache/apt/archives

echo 'tmpfs /var/cache/apt/archives tmpfs defaults 0 0' >>/etc/fstab

(but note bug 523920)

•

Mount your disk-backed filesystem

install debian on eee pc

Documents