Differences between revisions 50 and 88 (spanning 38 versions)
Revision 50 as of 2008-10-11 11:33:26
Size: 10916
Editor: BenArmstrong
Comment: Remove out of date/unnecessary wifi info
Revision 88 as of 2015-02-21 10:51:44
Size: 3760
Editor: SvenJoachim
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
[[TableOfContents]] <<TableOfContents>>
Line 3: Line 3:
This page summarizes the status of support for models 901, 1000 and 1000H. Please do not use it as a bug tracking system. Instead, file bugs and apply model-specific usertags as described on ["DebianEeePC/Bugs/About"]. This page summarizes the status of support for models 901, 1000 and 1000H. Please do not use it as a bug tracking system. Instead, file bugs and apply model-specific usertags as described on [[DebianEeePC/Bugs/About]].
Line 5: Line 5:
Please put no non-model specific information on this page. The general eee-configuration page can be found in [:DebianEeePC/HowTo/Configure]. Please put no non-model specific information on this page. See [[DebianEeePC/HowTo/Configure]] for configuration of webcam, multiple displays, etc.

Sometimes confused with the [[DebianEeePC/Model/901GO|901GO]] which has a different wireless chipset.
Line 8: Line 10:
=== Debian package for rt2860 ===
[liable] We are working on supporting the rt2860 driver. A working source deb is now available in the eeepc.debian.net repository. The name of the package is rt2860-source and can be fetched with apt-get or your favourite package manager once you have added the repo. Instructions for adding the repository are linked from the main page of the wiki.
Line 11: Line 11:
This can be built with module-assistant or from the tarball it installs. The easiest way is a simple As of version 2.6.32, the driver ''rt2860sta'' renames the wireless interface from ''ra0'' to ''wlan0''. [[DebianEeePC/HowTo/Wifi#Network_configurators|See here if you're using a network configurator]]); rename any interface name in `/etc/network/interfaces`, `/etc/wicd/wireless-settings.conf` if you are using wicd and `/etc/arno-iptables-firewall/debconf.cfg` if you are using Arno's firewall.

As of kernel version 2.6.32+39, "wicd" version 1.7.0+ds1-5, and "firmware-ralink" version 0.35~bpo60+1 (Squeeze, on a 901, 26 APR 12), it was not necessary to manually edit the two text files mentioned above. All that was needed was to click on the wireless icon in the system tray and, in the ensuing "Wicd Network Manager" window, select the "Preferences" tab and enter "wlan0" into the "Wireless interface:" data field. Refresh the scan and enter the security code, if needed.

As of version 2.6.30, the non-free firmware has been moved out (see DebianBug:521553). To get it working, DebianPkg:firmware-ralink must be installed. Non-free section must be added to the APT source.

{{{
$ sudo aptitude install firmware-ralink
}}}

Starting with version 2.6.29, the Linux kernel contains the driver for the Ralink 2860; it's enabled and present in {{{linux-image-2.6.29-1-*}}}. However, it contains non-free firmware (DebianBug:521553).

With 2.6.28 and earlier, the recommended way to install the driver for these models is with the prebuilt module package from [[DebianEeePC/Repository|our repository]]:

{{{
aptitude install rt2860-modules-2.6.26-1-686
}}}

Alternatively, the module can be built and installed automatically with [[ModuleAssistant|module-assistant]], as follows:
Line 15: Line 33:
m-a a-i rt2860-source }}}
Then install the built deb file.
m-a a-i rt2860 }}}
Line 18: Line 35:
To ensure that wireless still works after toggling it off and on by pressing FnF2:

 * put into /etc/modprobe.d/for-wireless line:
{{{
options pciehp pciehp_slot_with_bus=1 pciehp_force=1
}}}
 * add pciehp to /etc/modules to load it at boot start

== Webcam ==
See [:DebianEeePC/HowTo/Configure#head-ed631b3e487f9437df8ac4d010ed55c7dae79503].
See [[DebianEeePC/HowTo/Wifi/Rt2860]] and [[DebianEeePC/HowTo/Wifi]] for a guide to configuring wireless.
Line 30: Line 38:
If you want to see a message on your screen when you use a hotkey run {{{apt-get install aosd-cat}}} to install the OSD display'er. you then need to edit /etc/default/eeepc-acpi-scripts and change the following lines {{{ENABLE_OSD='no'}}} to {{{ENABLE_OSD='yes'}}} If you want to see a message on your screen when you use a hotkey run {{{aptitude install aosd-cat}}} to install the OSD display'er. you then need to edit /etc/default/eeepc-acpi-scripts and change {{{ENABLE_OSD='no'}}} to {{{ENABLE_OSD='yes'}}}.
Line 32: Line 40:
If you are not going to install the latest alsa driver to get the front mic working you can change If you are not going to install the latest ALSA driver to get the front mic working you can change
Line 37: Line 45:
Line 41: Line 48:
See the section below about what to do if you are installing the latest alsa
Line 43: Line 49:
== Multiple monitors ==
For a description how to get multiple monitors running see [:DebianEeePC/HowTo/Configure#head-b1142e74e531a6f0315b0c809d587232a432204e].
(eeepc-acpi-scripts 1.0.12 will detect these automatically.)
Line 46: Line 51:
=== Troubleshooting ===
this is detailed on another page but i had some issues getting the desktop to display over the two monitors so have pasted my xorg.conf and some more info below to help. Firstly install xrandr if it’s not already installed

{{{
#apt-get install xrandr
}}}
then edit /etc/default/eee-acpi-scripts, change the line {{{COMBINED_DISPLAY_SWITCHES='--mode 640x480'}}} to

{{{
COMBINED_DISPLAY_SWITCHES='--output VGA --auto --above LVDS'
}}}
next you need to edit your /etc/X11/xorg.conf here is my version

{{{
Section "InputDevice"
        Identifier "Generic Keyboard"
        Driver "kbd"
        Option "XkbRules" "xorg"
        Option "XkbModel" "pc105"
        Option "XkbLayout" "gb"
EndSection
Section "InputDevice"
        Identifier "Configured Mouse"
        Driver "synaptics"
        Option "CorePointer"
        Option "SendCoreEvents" "true"
        Option "Device" "/dev/input/mice"
        Option "Protocol" "auto-dev"
        Option "HorizEdgeScroll" "1"
EndSection
Section "Device"
        Identifier "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
        Driver "intel"
        BusID "PCI:0:2:0"
EndSection
Section "Monitor"
        Identifier "Configured Monitor"
        Option "DPMS"
EndSection
Section "Screen"
        Identifier "Default Screen"
        Device "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
        Monitor "Configured Monitor"
        DefaultDepth 24
        SubSection "Display"
                Depth 24
                Modes "1024x600"
                #ADD LINE FOR MULTI DISPLAYS
                #this is 1024 wide by 1368 high (768+600=1368)
                Virtual 1024 1368
        EndSubSection
EndSection
}}}
restart X '''without''' your external monitor plugged in, hitting the hotkey (f+f5) should now activate your external monitor. If not then you can debug issues by running

{{{
#xrandr
}}}
as a normal user (or a user that has permission to run x stuff), this will give you an output from which you can tell which monitors are plugged in. Without external monitor plugged in:

{{{
Screen 0: minimum 320 x 200, current 1024 x 600, maximum 1024 x 1368
VGA disconnected (normal left inverted right x axis y axis)
LVDS connected 1024x600+0+0 (normal left inverted right x axis y axis) 195mm x 113mm
   1024x600 60.0*+
   800x600 60.3
   640x480 59.9
TV disconnected (normal left inverted right x axis y axis)
}}}
With external monitor plugged in:

{{{
Screen 0: minimum 320 x 200, current 1024 x 600, maximum 1024 x 1368
VGA connected (normal left inverted right x axis y axis)
   1024x768 60.0
   800x600 60.3
   640x480 59.9
LVDS connected 1024x600+0+0 (normal left inverted right x axis y axis) 195mm x 113mm
   1024x600 60.0*+
   800x600 60.3
   640x480 59.9
TV disconnected (normal left inverted right x axis y axis)
}}}
Running the xrandr command with the options we specified in /etc/default/eee-acpi-scripts should also help you debug any problems

{{{
#xrandr --output VGA --auto --above LVDS
}}}
See the section below about what to do if you are installing the latest ALSA modules.
Line 136: Line 54:
To get the front mic working you have to rebuild the alsa driver using the latest release candidate. grab it from here ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.18rc1.tar.bz2

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

{{{
/usr/lib/2.6.25-2-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
}}}
I’m not sure if the last step is necessary but i ran it anyway.

You can verify your new driver with

{{{
/usr/lib/2.6.25-2-686/kernel/sounds/pci/hda/# ls -l
}}}
Check that the date on the snd-hda-intel.ko is about the time you compiled it :)

Now you need to reboot.

After the reboot, have a look at your mixer settings with alsamixer or the gnome-volume-control, the channels have changed from the stock driver.

 * 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'

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}')
}}}
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.
Build and install the latest release candidate of ALSA as described in [[DebianEeePC/HowTo/Sound]].
Line 209: Line 57:
See ["DebianEeePC/Model/900#Touchpad"]. See [[DebianEeePC/HowTo/ElantechTouchpad]].
Line 211: Line 59:
== Users ==
JohnGoerzen has confirmed these things work on the 901:
== Bluetooth ==
Bluetooth works fine with 2.6.29 and later. Older kernels need to be patched and may have a problem in that it must be enabled from the BIOS.
Line 214: Line 62:
 * X
 * Hardware ethernet
 * Wifi with above driver, including WPA2 and network-manager
 * Suspend/Resume
 * Hotkeys: suspend, brightness, others untested.
Performance seems to be better than the Xandros install.
We recommend using 2.6.29 or newer. There is a backported 2.6.29 for lenny users; see [[../../HowTo/Upgrade|our upgrade notes]] for details.
Line 221: Line 64:
ThijmenDeGooijer has confirmed these things to work on the 1000H: == Power management ==
Install cpufrequtils to allow throttling (works like a charm with acpi_cpufreq).
Line 223: Line 67:
 * X also on external display
 * Hardware ethernet
 * Wifi with above driver, including WPA2 and network-manager
 * Sound output, recording untested
 * Suspend/Resume to disk
 * Hotkeys: suspend, brightness, volume control (after modifying VOLUME_LABEL in /etc/default/eeepc-acpi-scripts).
IvanSanchez reports:

 * In order for the Wifi hotkey (Fn+F2) to work, /etc/acpi/actions/wireless.sh needs to be tweaked: replace "ath0" with "ra0" and "ath_pci" with "rt2860sta". Do this after installing the rt2860sta driver from the above link.
 * Bluetooth works OK, but only if enabled from the BIOS. There is no way (yet) of enabling/disabling it - the eeepc acpi module needs some patching (see http://forum.eeeuser.com/viewtopic.php?pid=304343). The bluetooth adapter is an USB device, much like the webcam.
 * Remember to install cpufrequtils to allow throttling, if you skipped tasksel (works like a charm with acpi_cpufreq).
 * ACPI events do work out of the box with 2.6.26 kernel — seems like the 901's ACPI implementation is less buggy than the 701's.
 * rt2860sta driver won't compile with 2.6.26 kernel (sid); use 2.6.25 (lenny) for the time being.
  * works for me - installed Debian Lenny with kernel from linux-image-2.6.26-1-686 version 2.6.26-4, I compiled rt-sta and I use it with no problems [ArturCzechowski]
 * Internal microphone does not seem to work. Most probably the 901 suffers from theh same problem as the 900. See http://wiki.debian.org/DebianEeePC/Model/900#head-1ef9e12308f2364008cb9f9871633d94ea331159 .
  * That page says that it works on the 900 with Linux-2.6.26; does it also work on 901 when using that version of Linux ?
 * The four "silver" keys (in the silver strip where the power button is) throw an ACPI event. The hotkey.sh script should reference those keys to do something useful (e.g. toggle webcam/bluetooth on/off).
 * suspend/hibernate/resume works; X with external display works (hint: edit /etc/default/eeepc-acpi-scripts for a higher resolution); LAN works.
This doesn't seem to work out-of-the-box:

 * Display switching
 * Hotkeys: LCD off, others untested

Macks can confirm that on a 100H:
 *Works:
  *WLAN with above drivers
  *Hotkeys (after changing the /etc/default/eeepc-acpi-scripts)
  *Suspend etc.
  *ACPI etc.
  *Webcam
 *Doesn't work:
  *Front mic (haven't tried the newest alsa...)
 *Not tested
  *Bluetooth
  *Card Reader
With 2.6.30 and later, Super Hybrid Engine support is present; [[../../HowTo/Configure#SuperHybridEngine|see our configuration page for information]].

This page summarizes the status of support for models 901, 1000 and 1000H. Please do not use it as a bug tracking system. Instead, file bugs and apply model-specific usertags as described on DebianEeePC/Bugs/About.

Please put no non-model specific information on this page. See DebianEeePC/HowTo/Configure for configuration of webcam, multiple displays, etc.

Sometimes confused with the 901GO which has a different wireless chipset.

Wifi

As of version 2.6.32, the driver rt2860sta renames the wireless interface from ra0 to wlan0. See here if you're using a network configurator); rename any interface name in /etc/network/interfaces, /etc/wicd/wireless-settings.conf if you are using wicd and /etc/arno-iptables-firewall/debconf.cfg if you are using Arno's firewall.

As of kernel version 2.6.32+39, "wicd" version 1.7.0+ds1-5, and "firmware-ralink" version 0.35~bpo60+1 (Squeeze, on a 901, 26 APR 12), it was not necessary to manually edit the two text files mentioned above. All that was needed was to click on the wireless icon in the system tray and, in the ensuing "Wicd Network Manager" window, select the "Preferences" tab and enter "wlan0" into the "Wireless interface:" data field. Refresh the scan and enter the security code, if needed.

As of version 2.6.30, the non-free firmware has been moved out (see 521553). To get it working, firmware-ralink must be installed. Non-free section must be added to the APT source.

$ sudo aptitude install firmware-ralink

Starting with version 2.6.29, the Linux kernel contains the driver for the Ralink 2860; it's enabled and present in linux-image-2.6.29-1-*. However, it contains non-free firmware (521553).

With 2.6.28 and earlier, the recommended way to install the driver for these models is with the prebuilt module package from our repository:

aptitude install rt2860-modules-2.6.26-1-686

Alternatively, the module can be built and installed automatically with module-assistant, as follows:

m-a prepare
m-a a-i rt2860 

See DebianEeePC/HowTo/Wifi/Rt2860 and DebianEeePC/HowTo/Wifi for a guide to configuring wireless.

Hotkeys

If you want to see a message on your screen when you use a hotkey run aptitude install aosd-cat to install the OSD display'er. you then need to edit /etc/default/eeepc-acpi-scripts and change ENABLE_OSD='no' to ENABLE_OSD='yes'.

If you are not going to install the latest ALSA driver to get the front mic working you can change

VOLUME_LABEL='LineOut'
VOLUME_LABEL='iSpeaker'

to

VOLUME_LABEL='Master'
VOLUME_LABEL='Headphones'

(eeepc-acpi-scripts 1.0.12 will detect these automatically.)

See the section below about what to do if you are installing the latest ALSA modules.

Front Mic

Build and install the latest release candidate of ALSA as described in DebianEeePC/HowTo/Sound.

Touchpad

See DebianEeePC/HowTo/ElantechTouchpad.

Bluetooth

Bluetooth works fine with 2.6.29 and later. Older kernels need to be patched and may have a problem in that it must be enabled from the BIOS.

We recommend using 2.6.29 or newer. There is a backported 2.6.29 for lenny users; see our upgrade notes for details.

Power management

Install cpufrequtils to allow throttling (works like a charm with acpi_cpufreq).

With 2.6.30 and later, Super Hybrid Engine support is present; see our configuration page for information.