Differences between revisions 69 and 70
Revision 69 as of 2010-02-06 14:21:15
Size: 8446
Editor: BenArmstrong
Comment: Add technical details re grub2 / efifb bug
Revision 70 as of 2010-02-06 16:48:39
Size: 8456
Editor: ?dsalt
Comment: Kernel package naming correction
Deletions are marked like this. Additions are marked like this.
Line 84: Line 84:
 * '''The kernel package name has been changed mid-series.'''<<BR>>2.6.32-5 and earlier are named `linux-image-2.6.32-trunk-`''`ARCH`''.<<BR>>Later 2.6.32-n are named `linux-image-2.6.32-1-`''`ARCH`''.<<BR>>(''`ARCH`'' is normally `686` or `amd64`.)  * '''The kernel package naming has been changed mid-series.'''<<BR>>2.6.32-5 and earlier are named `linux-image-2.6.32-trunk-`''`ARCH`''.<<BR>>Later 2.6.32-n are named `linux-image-2.6.32-`''`m`''`-`''`ARCH`''.<<BR>>(''`ARCH`'' is normally `686` or `amd64`.)

Translations: French German Italiano Portuguese Nederlands

eeepc-acpi-scripts

Here is a list of old manual workarounds that can be removed:

FixMe: some of these might more appropriately be in the News for the package (at least where leaving the old workaround in place is considered harmful).

1.0.9 or later

  • When you ugprade to eeepc-acpi-scripts 1.0.9 or later, it includes /etc/modprobe.d/eeepc.conf containing the pciehp options to make Fn+F2 (toggle wifi) work on some models. You may remove any /etc/modprobe.d/for-wireless.conf you may have created to work around the issue.

1.1.0 or later

  • You should no longer put pciehp in /etc/modules. /etc/init.d/eeepc-acpi-scripts will detect which module you need (pciehp or rfkill_input) and which options you need (these differ depending on kernel version) and load it.

Linux kernel

2.6.26 Upgrade Issues/tips

Debian’s madwifi source package now supports the eeepc chipset so we are no longer packaging our own eeepc-madwifi-source. For those that have the madwifi-eeepc-modules-2.6-686 meta package installed, we have prepared a dummy package that should transition you to the new modules. For those that have the kernel specific madwifi-eeepc-modules installed, before you reboot into your 2.6.26 kernel, install madwifi-modules-2.6-686. This will pull in the latest madwifi-modules available, and keep them up to date when new ones become available. Atl2 modules should be treated as below.

The 2.6.26 kernel also has the laptop_eeepc acpi module in it, so there is no longer any need for the eeepc-modules package. This was built for 2.6.26 for a short while, so if you have the package installed for the 2.6.26 kernel, it should be removed as having two kernel modules loaded for acpi could lead to unpredictable results.

  • If you are upgrading from an older kernel, even if only the ABI# changed (e.g. from 2.6.26-1-686 to 2.6.26-2-686) make sure you have ethernet/wireless modules for your particular model for the new kernel before rebooting.
    • Models 701 and 900:
    aptitude install atl2-modules-2.6-686 madwifi-modules-2.6-686
    • Models 901, 1000 and 1000H:
    aptitude install rt2860-modules-2.6-686
  • For other models, find your model number on ../../Models to see which packages you need.

  • The 2.6.26 kernel includes atl1e ethernet, so for models that use it instead of atl2 you don’t need to install a separate package.
  • Add pciehp to /etc/modules if it’s not there. This module manages hotplugging pci-e hardware (e.g. toggling wireless on and off).

  • The 2.6.26 kernel supports the webcam, so you no longer need to build it yourself. Just ensure it’s turned on in bios and modprobe uvcvideo.
  • Linux kernel 2.6.24 and later don’t need model=3stack-dig anymore, remove it from /etc/modprobe.d/alsa-base.conf.

  • We now have ../../Repository, use it.

2.6.27 and 2.6.28 not supported

Neither of these kernels are in any Debian release and are therefore not supported.

2.6.29 Upgrade Issues/tips

This kernel is no longer in unstable and was never in testing. See 2.6.30 below. All points apply except 2.6.29 did not need firmware-ralink (but this was a bug!) and the rt2860 kernel panic issue was not present.

2.6.30 Upgrade Issues/tips

As described in ../../FreeYourEee, progress has been made in new releases of the kernel to include wifi drivers for all models of Eee.

  • You can use a kernel backport of the Sid kernels on Lenny.

    • Add the following line to your /etc/apt/sources.list:
      deb http://unsupported.debian-maintainers.org/backports-kernel/ ./

    • Add the key:
      wget -q -O - http://unsupported.debian-maintainers.org/backports-kernel/archive-key.asc | apt-key add -

  • The newer kernels require a new acpid (1.0.8-7 or later) and new eeepc-acpi-scripts (1.1.0-1 or later) from Sid.
    • If you have updated to testing already, recent enough eeepc-acpi-scripts and acpid versions should already be installed.

  • If you formerly used madwifi and are therefore switching to ath5k, remove madwifi-tools, as it blacklists ath5k.
  • The interface name in ath5k is now wlan0, so any config files referencing ath0 need to be changed (e.g. /etc/network/interfaces). Please do not simply add the wlan0 lines and let ath0 remain there, this could give problems. Just rename :D

  • All relevant ethernet chipsets are now supported by the kernel, (except atl1c -- see ../../Model/1005HA for details,) so atl2 users don't need a separate module package anymore.

  • The rtl8187se driver is now included in the kernel; model 701SD users no longer need to build their own from source.
  • The rt2860 driver is now included in the kernel; it does not need to be built from source.
  • The ath9k driver is included in the kernel (for model 1000HE, 1002HA, 1005HA, 1008HA).
  • You should remove /etc/udev/rules.d/70-persistent-net.rules if it exists.
  • You may wish to enable kernel mode setting, particularly if you want native-mode VTs.

  • If you use the rt2860 driver with this kernel, you will need to install firmware-ralink from non-free.
  • There is a known problem with rt2860sta: if the interface is associated with an AP, disabling it via Fn-F2 or the rfkill interface will cause a kernel panic. This patch (which is attached to the above bug report and is a backport of the fix in 2.6.32-rc5) should fix the problem.

2.6.31 Upgrade Issues/tips

This is mostly of interest to owners of ../../Model/1005HA and ../../Model/1008HA, who need atl1c (contained in this kernel) to make ethernet work.

Otherwise, the notes for 2.6.30 apply.

2.6.32 Upgrade Issues/tips

Mostly, the notes for 2.6.31 apply.

  • The kernel package naming has been changed mid-series.
    2.6.32-5 and earlier are named linux-image-2.6.32-trunk-ARCH.
    Later 2.6.32-n are named linux-image-2.6.32-m-ARCH.
    (ARCH is normally 686 or amd64.)

  • There is, as yet, no backport for lenny.
  • There are various upstream rt2860-related changes:
    • ra0 is now known as wlan0. Wireless networking configuration will need to be altered accordingly.

    • The rt2860 panic bug in 2.6.30 is fixed in 2.6.32-rc5.
    • A new bug was introduced in -rc5 which broke things for users of wireless hardware other than rt2860. It's fixed (patch reverted) in -rc7.
  • Fixes in 2.6.32-6:
  • Some people (at least on model 901, and maybe others) may find that after starting X, console no longer works.
    • You can identify this problem if, after starting X: "cat /proc/fb" returns:
      • 0 EFI VGA 1 inteldrmfb
    • The workaround is to:
      • Edit /etc/default/console to set TERMINAL=console.
      • Run update-grub.
      • Reboot.
      • Console should now work, and running "cat /proc/fb" after starting X now should return:
        • 0 inteldrmfb
    • The bug relates to grub2 telling the kernel via 'gfxpayload' to enter graphics mode, triggering a bug in efifb -> inteldrmfb handoff.

    • This bug is reported to be fixed in 2.6.33.

2.6.33 Upgrade Issues/tips

This is currently in development.

No known issues (which aren't also present in 2.6.32) as yet.