Differences between revisions 33 and 34
Revision 33 as of 2009-06-15 06:39:08
Size: 4284
Editor: FranklinPiat
Comment: files in modprobe.d should be named *.conf in Lenny+
Revision 34 as of 2009-08-14 16:09:28
Size: 4490
Comment: +can't reproduce on 900
Deletions are marked like this. Additions are marked like this.
Line 29: Line 29:
900: Can't reproduce this bug with Lenny (linux-image-2.6.26-1-openvz-686 version 2.6.27-17lenny1).
Line 38: Line 40:

900: Can't reproduce this bug with Lenny (linux-image-2.6.26-1-openvz-686 version 2.6.27-17lenny1).

Translations: German Nederlands

Bugs relating to the Debian Eee PC project

Please do not use this page to track bugs. This is what the Debian Bug Tracking System (BTS) is for. However, we have provided a few summaries where workarounds are known and are difficult to dig out of the bug reports, each cross-referenced to the Debian bug numbers.

Read /About to learn how this project tracks bugs.

FixMe: Migrate the following bugs from old HowTo/Troubleshooting

The following bugs need to be classified as one of:

  • no longer an issue (delete)
  • non-bug issue (mention the issue on some other page: ../FAQ, ../TipsAndTricks, ../HowTo/Configure, etc.)

  • real bugs (must have debian bug# against the appropriate package(s) and usertag them)

Shutting down fails

There is an issue surrounding shutting down (confirmed even in 2.6.25). The system appears to halt, but the fan continues to run (sometimes also the wi-fi light stays on) and your SSD drive may not be cleanly unmounted. The reason is the sound module doesn't close correctly, but there is a fix! Edit /etc/default/halt as root with your favourite text editor and add the line

rmmod snd_hda_intel

at the end. Then it will power off correctly!

900A: This bug does not seem to exist when running Lenny (linux-image-2.6.26-1-686 version 2.6.26-8 on 2008-10-31).

900: Can't reproduce this bug with Lenny (linux-image-2.6.26-1-openvz-686 version 2.6.27-17lenny1).

System freezes displaying 'Setting the system clock'

Try the following and please do give us feedback if it does not work for you.

Become root and say:

echo "HWCLOCKPARS=--directisa" >> /etc/default/rcS

900A: This workaround is still necessary when running Lenny (linux-image-2.6.26-1-686 version 2.6.26-8 on 2008-10-31).

900: Can't reproduce this bug with Lenny (linux-image-2.6.26-1-openvz-686 version 2.6.27-17lenny1).

NetworkManager stops functioning with wireless after resume

This can be fixed by modifying /etc/acpi/actions/suspend.sh as follows:

#!/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
brn_control=/proc/acpi/asus/brn
brightness=$(cat $brn_control)
#turn off wireless, stop network-manager
/etc/acpi/actions/hotkey.sh ath0 ATKD 00000011
/etc/init.d/dbus stop
#suspend
pm-suspend --quirk-s3-bios --quirk-dpms-on
#picks up here for resume
echo $brightness > $brn_control
#restart dbus (and thus nm), turn wireless back on
/etc/init.d/dbus start
/etc/acpi/actions/hotkey.sh ath0 ATKD 00000010
  • [BenArmstrong] If this is a bug in our eeepc-acpi-scripts, it should be filed in the bts. If the problem is resolved, this section should be removed.

. [?DmitryNesterkin] On Eee PC 900 this didn't work for me. However, that helped:

echo "pciehp" >> /etc/modules
echo "options pciehp pciehp_force=1" >> /etc/modprobe.d/pciehp.conf

If after resume wifi would not work, just restart network-manager:

/etc/init.d/network-manager restart

Wireless not working (using wpa_supplicant)

If you get strange errors (for me: WPA not working at all, WEP only working for 8 seconds followed by 30 seconds of "network unreachable" and no key shown in iwconfig ath0) you can try the following workaround:

As root use this command:

killall wpa_supplicant && sleep 5 && wpa_supplicant -i ath0 -c /etc/wpa_supplicant/wpa_supplicant.conf

(Perhaps you can deamonize wpa_supplicant, never tried...)

and on another console you have then to start dhclient (sudo dhclient) to get a DHCP lease (if you don't have static settings)

Keyboard on 901

?RaulFerriz:

  • Win key doesn't work: Does any one have a solution? ( I refer the key between Fn and right Alt, but the key between ?AltGr and left Control doesn't work also) Ctrl + Alt + Arrows doesn't seem to respond under any window manager I tested (gnome, fluxbox and twm). Any advice? Ctrl + Alt + F1-F9: Doesn't do nothing ...