个人工具
登录
查看“UbuntuHelp:IdeapadS/Fixes”的源代码 - Ubuntu中文
UbuntuHelp
讨论
查看源代码
历史
搜索
导航
首页
最近更改
随机页面
页面分类
帮助
编辑
编辑指南
沙盒
新闻动态
字词处理
工具
链入页面
相关更改
特殊页面
页面信息
查看“UbuntuHelp:IdeapadS/Fixes”的源代码
来自Ubuntu中文
←
UbuntuHelp:IdeapadS/Fixes
跳转至:
导航
,
搜索
因为以下原因,你没有权限编辑本页:
您所请求的操作仅限于该用户组的用户使用:
用户
您可以查看与复制此页面的源代码。
{{From|https://help.ubuntu.com/community/IdeapadS/Fixes}} {{Languages|UbuntuHelp:IdeapadS/Fixes}} <<Include(AA1/Header)>> This page contains suggested fixes and/or hacks to get hardware working properly with Ubuntu on the Aspire One. == Hard Disk: Load Cycle Count == Both Hardy and intrepid may suffer from excessive load cycling on the AA1. http://ubuntuforums.org/showthread.php?t=805570 This will fix the issue, but the value "128" in the script should be modified to "200". == Card Reader(s) == Upgrading to BIOS v. 3309 from Acer will fix visibility issues with the card reader (so you don't need to have a card in on boot for it to be visible). * Need link here, google for it for now. * ftp://ftp.acer-euro.com/netbook/aspire_one_110/bios/ * ftp://ftp.acer-euro.com/netbook/aspire_one_150/bios/ Note that this does not work on some models, such as the ZG1 (needs confirmation). In this case, you will need to use the following workaround. Note that this will add around 5 seconds to boot and resume time. Open /boot/grub/menu.lst with your favourite text editor as root: <pre><nowiki> sudo gedit /boot/grub/menu.lst </nowiki></pre> Find the Ubuntu entry for the latest kernel (usually the entry just under the line <pre><nowiki> </nowiki></pre> ). Add the following to the end of the line starting with "kernel": <pre><nowiki> pciehp.pciehp_force=1 </nowiki></pre> Do the same with the line a bit further up starting " <pre><nowiki> # defoptions </nowiki></pre> " to make it be added to future kernels (from what I've gathered, you should NOT uncomment it (remove the #), but I might be wrong). == Wireless == The wireless card on the AA1 contains an Atheros chipset. There are at least three native drivers available for this chipset, which have been used with varying success: * madwifi from kernel (ath_pci) * ath5k from intrepid backports (ath5k) * madwifi-hal from http://snapshots.madwifi-project.org/ (ath_pci) There is also an alternative driver called ndiswrapper, which uses the Windows-native drivers for the card. Before trying any of these drivers, '''ensure that only the wireless driver you wish to use is allowed to load''' by blacklisting the others. This is important, since drivers may load and compete for access to the hardware, leaving the end user confused. Here is an example of a blacklist file named /etc/modprobe.d/blacklist-wifi that only allows the use of ndiswrapper: <pre><nowiki> blacklist ath_pci blacklist ath5k # blacklist ndiswrapper </nowiki></pre> === madwifi from kernel (ath_pci) === This driver does not support the chipset revision on the AA1, and thus is useless as of this writing. === ath5k from Intrepid backports or native in Jaunty (ath5k) === This driver has been reported to connect to the hardware, but experience disconnects on medium to heavy wireless activity. It has been further noted that it may not communicate with some AP's using a WPA2-PSK authentication mechanism. If you don't have these problems, this is the best module to use, since it comes with Jaunty. ==== WiFi LED ==== To get the WiFi access LED (only the right one, unfortunately) and the killswitch to work in Jaunty, install the package linux-backports-modules-jaunty: <pre><nowiki> sudo aptitude install linux-backports-modules-jaunty </nowiki></pre> Then reboot. Hopefully, the WiFi LED and killswitch will work. However, currently plasma-widget-network-manager (and presumably network-manager-gnome) can't detect when the killswitch is used, and so they often get very confused for a few seconds whilst they try to figure out why the signal just jumped from 70% to 0%. === madwifi-hal from http://snapshots.madwifi-project.org/ (ath_pci) === This snapshot of madwifi-hal from http://snapshots.madwifi-project.org/ appears to work reliably. <pre><nowiki> wget http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6-current.tar.gz sudo apt-get install build-essential linux-headers-$(uname -r) tar -xzf madwifi-hal-0.10.5.6-current.tar.gz cd madwifi-hal-0.10.5.6*/ make sudo make install sudo modprobe ath_pci </nowiki></pre> You may have to append ath_pci to /etc/modules: <<BR>> <pre><nowiki> # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. fuse lp ath_pci </nowiki></pre> This driver should work under all conditions. At least one user has tested the driver under heavy load (3MB/s sustained for 2 hours, no hangup), tested for correct suspend/resume functionality, and verified it communicates correctly with WEP, WPA, WPA2, against recent Linksys, Dlink, and Cisco hardware. Now, you should create a script to restart the interface on awake from suspend mode, as it will otherwise hang. As root, create /etc/pm/sleep.d/00wireless: <pre><nowiki> # # Restart WiFi interface after suspension # case "$1" in resume|thaw) /sbin/ifconfig wifi0 down /sbin/ifconfig wifi0 up ;; *) ;; esac exit $? </nowiki></pre> Don't forget to make it executable: <pre><nowiki> sudo chmod u+x /etc/pm/sleep.d/00wireless </nowiki></pre> ==== Enable LEDs with the ath_pci snapshot ==== * The wireless leds must have an entry in /proc. * The wireless slide killswitch works, but there is no notification given by the desktop environment. To enable LED notification based on traffic/association, put these lines at the end of /etc/sysctl.conf: <pre><nowiki> dev.wifi0.ledpin=3 dev.wifi0.softled=1 </nowiki></pre> Either reboot, or run <pre><nowiki> sudo sysctl -p </nowiki></pre> === ndiswrapper === If the above madwifi instructions didn't work for you, using ndiswrapper is an alternative that is known to work, but uses Windows drivers. Download drivers for your wireless card from: http://download2.dvd-driver.cz/atheros/drivers/ar5008/xp32-6.0.3.85.zip Unzip those drivers. Install ndiswrapper, and launch the installer: <pre><nowiki> sudo aptitude install ndisgtk sudo ndisgtk </nowiki></pre> Find the net5416.inf file from the archive you unzipped, and install it using the ndisgtk GUI. If you have tried madwifi, unload it with: <pre><nowiki> madwifi-unload </nowiki></pre> from a terminal. Restart the AA1, and the module should load. == Audio (Intel HDA) == Various issues with the Intel HDA audio chipset have been reported. They vary in nature, from sound not working at all to microphone issues. It is generally accepted that upgrading ALSA to 1.0.18a resolves the problems with this chipset. To upgrade ALSA, download ''alsa-driver-1.0.18a.tar.bz2'' (or later, 1.0.18a tested on 19 Jan 2009) from http://alsa-project.org/, unpack the archive, open terminal, cd into the newly-created folder and run the following commands: <pre><nowiki> sudo apt-get install build-essential linux-headers-$(uname -r) ./configure --with-cards=all make sudo make install </nowiki></pre> These commands will build new ALSA drivers and copy them to the proper location. After rebooting, adjust microphone volume: it is set to zero by default. Take the time to test the microphone with gnome-sound-recorder. After the modules are installed, add the following to the end of /etc/modprobe.d/options: <pre><nowiki> options snd-hda-intel model=acer-aspire </nowiki></pre> Please note that since these directions replace existing ALSA drivers in the kernel's modules directory, you may have to repeat these directions after a kernel upgrade. == DPI Correction == The native resolution of the AA1 is 1024x600. If fonts are too large after installation, you may try setting the DPI of the screen to 96 DPI manually. In the "Monitor" section of /etc/X11/xorg.conf, add: <pre><nowiki> DisplaySize 195 113 </nowiki></pre> In the "Device" section of /etc/X11/xorg.conf, add: <pre><nowiki> Option "NoDDC" </nowiki></pre> Save and close the file, then restart X. == Fan Control == The user space script "acerfand" originally used to fix the noisy fan problem may cause race conditions and lockups as it accesses registers asynchronous to the kernel. A kernel module to do the fan control has recently been created, and this avoids the race condition problem. You can install the kernel module in the following way. <pre><nowiki> wget http://www.piie.net/files/acerhdf_kmod-0.4.0-3.tar.gz tar zxvf acerhdf_kmod-0.4.0-3.tar.gz cd acerhdf_kmod make sudo make install </nowiki></pre> Now load the kernel module using <pre><nowiki> sudo modprobe acerhdf </nowiki></pre> Check it worked by looking at the output of dmesg for lines with "acerhdf" in them. To make sure it loads at boot time add acerhdf to /etc/modules <pre><nowiki> # /etc/modules: kernel modules to load at boot time. # # This file contains the names of kernel modules that should be loaded # at boot time, one per line. Lines beginning with "#" are ignored. fuse lp ath_pci acerhdf </nowiki></pre> For further information on the kernel module, see: http://www.piie.net/index.php?section=acerhdf [[category:UbuntuHelp]]
该页面使用的模板:
模板:From
(
查看源代码
)
模板:Languages
(
查看源代码
)(受保护)
模板:Languages/Lang
(
查看源代码
)(受保护)
返回至
UbuntuHelp:IdeapadS/Fixes
。