The article consists of several parts: it is so convenient to write and read.In the
previous part, the netbook was reviewed from the hardware “point of view”, this one discusses the features of installing and operating the Linux OS on it.
Operating system: flour of choice.')
Actually, I am mostly a FreeBSD user. She successfully works on my main work computer and on the servers surrounding me. I know her well enough and can work effectively with her.
At first, I thought of installing on a FreeBSD netbook. But, looking at the speed at which the source code was compiled on the platform, I refused this idea (you could, of course, have already compiled packages, but this is not true, and indeed, this system is designed for normal operation with ports). So I decided to install something Linux-like. Gentoo, unfortunately, did not fit for the same reasons as FreeBSD (namely, due to source-based). I didn't want to install any pop * ubuntu for a number of reasons, including ideological ones. However, I decided to put what the above * ubuntu based on: GNU / Debian Linux (Lenny). In the wiki on the Debian website, I found the corresponding tutorial:
ru / DebianAcerOne .
OS installation and commissioningI did almost everything on the above manual. True, I had to actively google about some things, but in the end I solved the problems that arose.
Anticipating a completely uninteresting procedure for preparing a bootable flash drive, I decided to exclude it using an external USB drive. In such cases, a very useful thing. I used a netinstall disk, so the installation required a working wired internet connection. The installer also saw the WLAN adapter, but the native driver is a half-worker, so it did not work out from the wireless network.
I made the installation quite standard, I set up the hard drive in one piece (plus a swap), almost all the other options are default. When installing on a flash drive, it is recommended to use ext2 or ext3 with additional mount options “noatime” and “nodiratime”. Personally, I used ext2 FS (when a 1.8 "hard drive is delivered from distant China, then ext3 will be used).
A few words should be said separately about the wireless interface. As I said, the netbook uses a miniPCIe adapter from Atheros. In theory, its support is provided by the "kosher" ath5k drivers, which are present in the out-of-box system. However, even though the / dev / wifi0 interface was in the system, the torture of wlconfig and others like them showed that this issue would have to be given more time. The study of a handful of links in Google on the subject of interest showed that one of the solutions to the problem is to use Madwifi, which, although not “kosher” for opensource adherents, is quite working. Ok, Madwifi, so Madwifi, then we set.
A search on the Debian Lenny repositories revealed that there are three relevant packages:
madwifi-modules-2.6.26-1-686
madwifi-source
madwifi-tools
The binary is sad, because the kernel version is already fresh in the repositories (2.6.26-2-686). Well, nothing, I'm a FreeBSD user, I'm not used to collecting raw materials. So, we put the required packages for building using aptitude: build-essential, the necessary linux-headers, madwifi-source, madwifi-tools (maybe I forgot something - everything you need is downloaded by dependencies). Then go to the source directory:
cd /usr/src/modules/madwifi/
If you already have madwifi modules in the system, then you should unload them and put the interfaces generated by the modules. To do this, there are special scripts in the directory ./scripts/ (find-madwifi-modules.sh and madwifi-unload):
ifconfig ath0 down
ifconfig wlan0 down
cd ./scripts
./madwifi-unload
./find-madwifi-modules.sh $(uname -r)
cd ..
Now you can start compiling and installing:
make && make install
If everything went well, load the compiled module:
modprobe ath_pci
In order to load the madwifi modules instead of the ath5k when the system boots, you need to bring the /etc/modprobe.d/madwifi file to the following form:
## ath5k (mac80211)
## Comment out the following line, and uncomment all of the
## madwifi modules below to use the athk module
blacklist ath5k
## madwifi (non-free)
#blacklist ath_hal
#blacklist ath_pci
#blacklist ath_rate_amrr
#blacklist ath_rate_onoe
#blacklist ath_rate_sample
#blacklist wlan
#blacklist wlan_acl
#blacklist wlan_ccmp
#blacklist wlan_scan_ap
#blacklist wlan_scan_sta
#blacklist wlan_tkip
#blacklist wlan_wep
#blacklist wlan_xauth
In order for the WiFi LED to work, you need to change some sysctl parameters:
dev.wifi0.ledpin=3
dev.wifi0.softled=1
I recommend registering them in the /etc/sysctl.d/madwifi.conf file, in which case the parameters will be applied when the system boots. One more thing: I noticed that when exiting from sleep mode, the madwifi drivers do not function correctly. Therefore, by running the following command, we make the module unload when it goes into sleep mode, and when it wakes up it loads:
echo "SUSPEND_MODULES=ath_pci" > /etc/pm/config.d/madwifi
Then you can put some graphical network manager and enjoy life. About Wi-Fi like everything.
The webcam started up out of the box, the messenger saw her successfully. The sound also, earned immediately, and quite normal.
To make the Xs work properly, I brought the /etc/X11/xorg.conf file to the following form:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
RgbPath "/etc/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/X11/misc"
FontPath "/usr/share/fonts/X11/cyrillic"
FontPath "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath "/usr/share/fonts/X11/Type1"
FontPath "/usr/share/fonts/X11/100dpi"
FontPath "/usr/share/fonts/X11/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection
Section "Module"
Load "extmod"
Load "dbe"
Load "dri"
Load "GLcore"
Load "glx"
Load "record"
Load "xtrap"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp_led:caps,grp:ctrl_shift_toggle"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
DisplaySize 195 113
Identifier "Monitor0"
VendorName "AUO"
ModelName "11c2"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
VendorName "Intel Corporation"
BoardName "Mobile 945GME Express Integrated Graphics Controller"
BusID "PCI:0:2:0"
#Option "NoAccel"
Option "AccelMethod" "exa"
Option "MigrationHeuristic" "greedy"
#Option "SWcursor"
#Option "ColorKey"
#Option "CacheLines"
#Option "Dac6Bit"
#Option "DRI"
Option "NoDDC"
#Option "ShowCache"
#Option "XvMCSurfaces"
#Option "PageFlip"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
There are customized options related to fonts, optimization, resolution and keyboard.
I installed KDE3 on a netbook, as I prefer them. They work quite well, did not notice any special problems. In the future plans there is a desire to fasten to all this economy Bluetooth, a mobile phone in the role of a modem, a GPS receiver. Perhaps I will write tutorials on these issues.