Slitaz -- wine / accelon

wine-1.2.2

wine-1.3.8

winxp

20110303

root@slitaz:~# wine --version
wine-1.3.8
root@slitaz:~# fc-list
Fixed:style=Bold
AR PL UMing TW:style=Light
AR PL UMing HK:style=Light
AR PL UMing CN:style=Light
Charter:style=Bold
Fixed:style=Bold SemiCondensed
Fixed:style=SemiCondensed
micro.pcf:style=Regular
Fixed:style=Oblique SemiCondensed
decsess.pcf:style=Regular
deccurs.pcf:style=Regular
cursor.pcf:style=Regular
Charter:style=Regular
DejaVu Sans:style=Bold
DejaVu Sans:style=Book
Fixed:style=Regular
DejaVu Sans Mono:style=Book
AR PL UMing TW MBE:style=Light
root@slitaz:~# fc-list :lang=zh
AR PL UMing TW:style=Light
AR PL UMing HK:style=Light
AR PL UMing CN:style=Light
AR PL UMing TW MBE:style=Light
root@slitaz:~#

====
20110228

root@slitaz:~# tazpkg info wine

Tazpkg information
================================================================================
Package : wine
Version : 1.2.2
Category : misc
Short desc : Windows API for Linux.
Maintainer : pascal.bellard@slitaz.org
Depends : alsa-lib libxml2 libxslt mesa libglu-mesa xorg-libICE xorg-libSM
xorg-libX11 xorg-libXau xorg-libXdmcp xorg-libXext libgphoto2 libtool lcms esound
Build deps : flex bison xorg-dev mesa-dev freetype-dev
Web site : http://www.winehq.org/
================================================================================

root@slitaz:/media/DATA/yinshun/accelon3# ls
accelon3.exe lang_chs.ini single.eff wxzj.adb
accelon3.ini lang_cht.ini taisho.adb wxzj.adb.ini
ccg.dll lang_en.ini taisho.adb.ini yinshun.adb
dfb.adb lang_jp.ini taixu.adb yinshun.adb.ini
dfb.adb.ini lang_kr.ini taixu.adb.ini yinshun.syn
help setup taixu.syn
root@slitaz:/media/DATA/yinshun/accelon3#
.

ACPI - DSDT

Extract from

在霧裡欣賞 BIOS 裡的 ACPI Description Table
http://fred-zone.blogspot.com/2008/10/bios-acpi-description-table.html

[..]
這意味著，ACPI 會依照不同作業系統而有不同的行為，可能有些功能在 Linux 下就會被關掉，亦或是因為會對記憶體位址做特殊存取，雖不會造成 Windows 任何影響，但卻可能剛好破壞掉 Linux Kernel 的運作，導致 boot/reboot 或 S3/S4 時會 hangs 或 crash。有時候缺少正確的 Return 值，也會造成 S3/S4 resume 的失敗。以下就是一個實際缺少 Return 導致 resume 不正常的例子，但我自行修正並補上正確的回傳值：

Method (_WAK, 1, NotSerialized)
{
...
...
Return(Package(0x02){0x00, 0x00})
}



如此遺漏而產生出來的 ACPI bugs 有非常多，在此也不便一一列舉，日後有時間再慢慢彙出來。不過，既然我們已經得到 DSDT，意味著只要有心，都可在此改寫並修正一些 ACPI 的問題。雖然我們並不能將修正過後的 DSDT 寫回 BIOS，但 Linux Kernel 編譯時若有開啟『CONFIG_ACPI_CUSTOM_DSDT』，就可以使用自定的 DSDT 取代原本機器上的 table，只要將檔案放到 /boot 下即可（在 Debian Lenny/Sid 上的 Kernel 似乎沒有開啟這項功能）。

將改好的 dsdt.dsl 重新 compile：

iasl -tc dsdt.dsl



此外若你是在 Ubuntu 下，請直接將編譯好的 dsdt.aml 放到 /etc/initramfs-tools 之下，再 update initrd：

sudo update-initramfs -c -k all



然後重開機後，便可使用自訂的 DSDT 來控制 ACPI 的行為。

[..]

Linux Module

Extract from

如何編譯特定的 Linux Module
http://fred-zone.blogspot.com/2008/09/linux-module.html

這也不是一天兩天了，常常會對 Linux 的某些 Driver 做些 Patches，或對某些 Module 做修改，但每次要 compile 出那幾個 ko 檔時就很頭痛，既然只是修改特定的 module ，又不用重新做出新的 kernel image，為何每次都要將整個 kernel 重新 compile 呢？其實有方法可以只編譯特定的 kernel module 以並免不必要的時間浪費。

切換到目標 module 的目錄下，然後執行：

make script
make prepare
make -C /usr/src/linux SUBDIRS=$PWD modules


※粗體字部份改成 kernel source 的位置即可。

作者： Fred Chien(錢逢祥) 發表於 上午2:21

文章分類： Linux, Linux Kernel

1 則網友意見:

penk 提到...

在 Ubuntu 上我是習慣 make M=/your/path/to/module/directory -C /lib/module/$(uname -r)/build
[..]

----

VS

1.Slitaz -- kernel module
http://alanyih.blogspot.com/2010/06/slitaz-kernel-module.html

make CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y M=net/bluetooth/rfcomm

2.Slitaz -- modules_install
http://alanyih.blogspot.com/2010/02/slitaz-modulesinstall.html

make mrproper
make gconfig
make drivers/i2c/
make drivers/i2c/i2c-dev.ko
make INSTALL_MOD_PATH=/home/module modules_install

3. Make
http://blog.chinaunix.net/u1/52215/showart_1217522.html

1) complile a modules:
make -C /usr/src/linux/ M=`pwd` modules
-C: the source code dirctory
M=: the modules source and makefile directory.


.

Slitaz -- xauth

xauth

root@slitaz:~# tazpkg info xorg-xauth

Tazpkg information
================================================================================
Package : xorg-xauth
Version : 1.0.5
Category : x-window
Short desc : X authority file utility.
Maintainer : pankso@slitaz.org
Depends : xorg-libXmu
Build deps : xorg-libXmu-dev
Web site : http://www.x.org/
================================================================================

root@slitaz:~# ls -l ~/.Xauthority
-rw------- 1 root root 51 Feb 28 08:50 /root/.Xauthority
root@slitaz:~# xauth -f ~/.Xauthority
Using authority file /root/.Xauthority
xauth> list
slitaz/unix:0 MIT-MAGIC-COOKIE-1 7f8e7a9123eb0c495e1673a26261e7aa
xauth> info
Authority file: /root/.Xauthority
File new: no
File locked: no
Number of entries: 1
Changes honored: yes
Changes made: no
Current input: (stdin):2
xauth> quit

root@slitaz:~# X -version

X.Org X Server 1.9.3
Release Date: 2010-12-13
X Protocol Version 11, Revision 0
Build Operating System: SliTaz GNU/Linux
Current Operating System: Linux slitaz 2.6.37-slitaz #1 SMP Mon Feb 21 22:37:34 UTC 2011 i686
Kernel command line: root=/dev/sda7 acpi=off
Build Date: 22 January 2011 04:03:19PM

Current version of pixman: 0.20.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
root@slitaz:~#
.

Slitaz -- mesa-dri / swrast_dri.so

Fix: pack swrast drivers into mesa-dri
http://hg.slitaz.org/wok/raw-rev/4dcbd1550531

# HG changeset patch
# User Antoine Bodin
# Date 1296361361 -3600
# Node ID 4dcbd15505312753f7b2b39e25ed75d7b3b1c681
# Parent 776b389d3075090b41f5b10c6ad192cb407267c6
Fix: pack swrast drivers into mesa-dri

--- a/mesa-dri/receipt Sat Jan 29 22:47:27 2011 +0000
+++ b/mesa-dri/receipt Sun Jan 30 05:22:41 2011 +0100
@@ -12,7 +12,12 @@
# Rules to gen a SliTaz package suitable for Tazpkg.
genpkg_rules()
{
- mkdir -p $fs/usr/lib
+ mkdir -p $fs/usr/lib/dri
+ for driver in swrast swrastg
+ do
+ cp $_pkg/usr/lib/dri/${driver}_dri.so \
+ $fs/usr/lib/dri
+ done

mkdir -p $fs/etc/X11/xorg.conf.d
cp -a stuff/*.conf $fs/etc/X11/xorg.conf.d

root@slitaz:~# tazpkg list-files mesa-dri

Installed files with: mesa-dri
================================================================================
/etc/X11/xorg.conf.d/90-DRI.conf
/usr/lib/dri/swrast_dri.so
/usr/lib/dri/swrastg_dri.so
================================================================================
3 files installed with mesa-dri.


root@slitaz:~# glxinfo | grep render
direct rendering: Yes
OpenGL renderer string: Software Rasterizer
GL_NV_conditional_render, GL_NV_depth_clamp, GL_NV_fragment_program,
root@slitaz:~#

------

1.
root@slitaz:~# glxinfo
name of display: :0.0
Error: couldn't find RGB GLX visual or fbconfig

root@slitaz:~# glxgears
Error: couldn't get an RGB, Double-buffered visual
root@slitaz:~#

2.
root@slitaz:~# cat /var/log/Xorg.0.log | grep EE
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 2023.872] (II) Loading extension MIT-SCREEN-SAVER
[ 2024.020] (EE) AIGLX error: dlopen of /usr/lib/dri/swrast_dri.so failed (/usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory)
[ 2024.020] (EE) GLX: could not load software renderer
root@slitaz:~#

3.
root@slitaz:~# tazpkg search-file swrast_dri.so

Search result for file swrast_dri.so
================================================================================
0 file found for: swrast_dri.so

root@slitaz:~#


4.
http://mirror.slitaz.org/packages/experimental/
[..]
mesa-7.10.tazpkg 2011-Jan-30 23:01:05 86.4K application/x-tazpkg
mesa-dev-7.10.tazpkg 2011-Jan-30 23:01:15 124.2K application/x-tazpkg
mesa-dri-7.10.tazpkg 2011-Jan-30 23:01:00 1.0M application/x-tazpkg


http://mirror.slitaz.org/packages/cooking/
[..]
mesa-7.10.tazpkg 2011-Jan-25 02:01:09 86.0K application/x-tazpkg
mesa-demos-8.0.1.tazpkg 2011-Jan-22 05:01:04 15.5K application/x-tazpkg
mesa-dev-7.10.tazpkg 2011-Jan-25 02:01:59 126.0K application/x-tazpkg
mesa-dri-7.10.tazpkg 2011-Jan-25 02:01:08 2.0K application/x-tazpkg

Slitaz -- xterm

root@slitaz:~# date
一 2月 21 14:55:55 CST 2011
root@slitaz:~# fc-list
文泉驿等宽微米黑,文泉驛等寬微米黑,WenQuanYi Micro Hei Mono:style=Regular
Fixed:style=SemiCondensed
micro.pcf:style=Regular
文泉驿微米黑,文泉驛微米黑,WenQuanYi Micro Hei:style=Regular
cursor.pcf:style=Regular
DejaVu Sans:style=Bold
DejaVu Sans:style=Book
DejaVu Sans Mono:style=Book
root@slitaz:~# uname -a
Linux slitaz 2.6.37-slitaz #2 SMP Tue Jan 25 02:32:32 CET 2011 i686 GNU/Linux
root@slitaz:~# tazpkg list | grep xterm
xterm 267 utilities
root@slitaz:~# cat ~/.Xdefaults | tail -8
xterm*faceName: DejaVu Sans Mono
xterm*faceNameDoublesize: WenQuanYi WenQuanYi Micro Hei Mono-10
xterm*faceSize: 9

! Xload settings.
!
!xload*background: black
!xload*foreground: lightblue
root@slitaz:~#

Debian GNU/Linux 6.0 on ARM

Debian GNU/Linux on ARM
http://www.debian.org/ports/arm/

On these pages you'll find information about the ongoing effort of porting Debian GNU/Linux to the ARM architecture which is often found in embedded systems.
Current Status

Debian fully supports a port to little-endian ARM. The ARM EABI (armel) port has been integrated in Debian and the old (arm) port is deprecated.

As of our latest release, Debian GNU/Linux 6.0.0, the following ARM sub-architectures are fully supported:

* iop32x: we support some IOP32x based Network Attached Storage (NAS) devices, such as the Thecus N2100, Intel SS4000 and GLAN Tank.
* ixp4xx: we support the popular Linksys NSLU2 device.
* kirkwood: we support Marvell's Kirkwood platform and we have specific support for a number of devices, including the SheevaPlug, QNAP Turbo NAS (TS-11x, TS-21x and TS-41x) and OpenRD.
* orion5x: we support Marvell's Orion platform and we have specific support for a number of devices, including the QNAP Turbo Station (TS-109, TS-209, TS-409) and HP mv2120.

General Information about ARM EABI

Please see the release notes and installation manual for more information.
Available Hardware for Debian Developers

agnesi.debian.org (arm) and agricola.debian.org (armel) are available to Debian developers for ARM porting work. The machine have development chroot environments which you can access with dchroot. Please see the machine database for more information about these machines.
Contacts
Mailing lists

The Debian ARM port mailing list is located at debian-arm@lists.debian.org. If you wish to sign up, send a message with the word "subscribe" as the subject to debian-arm-request@lists.debian.org. The list is archived at the debian-arm list archives.

It's also a good idea to sign up with the linux-arm mailing list.


====
2.1. Supported Hardware

http://www.debian.org/releases/stable/armel/ch02s01.html.en#id514667

Debian does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, gcc, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at http://www.debian.org/ports/arm/ for more details on ARM architecture systems which have been tested with Debian GNU/Linux.

Rather than attempting to describe all the different hardware configurations which are supported for ARM, this section contains general information and pointers to where additional information can be found.
2.1.1. Supported Architectures

Debian GNU/Linux 6.0 supports eleven major architectures and several variations of each architecture known as 「flavors」.
[...]

2.1.2. CPU, Main Boards, and Video Support

Each distinct ARM architecture requires its own kernel. Because of this the standard Debian distribution only supports installation on a number of the most common platforms. The Debian userland however may be used by any ARM CPU.

Most ARM CPUs may be run in either endian mode (big or little). However, the majority of current system implementation uses little-endian mode. Debian currently only supports little-endian ARM systems.

The supported platforms are:

IOP32x
Intel's I/O Processor (IOP) line is found in a number of products related to data storage and processing. Debian currently supports the IOP32x platform, featuring the IOP 80219 and 32x chips commonly found in Network Attached Storage (NAS) devices. Debian explicitly supports two such devices: the GLAN Tank from IO-Data and the Thecus N2100.

IXP4xx
The IXP4xx platform is based on Intel's XScale ARM core. Currently, only one IXP4xx based system is supported, the Linksys NSLU2. The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small device which allows you to easily provide storage via the network. It comes with an Ethernet connection and two USB ports to which hard drives can be connected. There is an external site with installation instructions.

Kirkwood
Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base and OpenRD-Client), SheevaPlug and QNAP Turbo Station (TS-110, TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet supported).

Orion5x
Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: Buffalo Kurobox, HP mv2120, QNAP Turbo Station (TS-109, TS-209 and TS-409).

Versatile
The Versatile platform is emulated by QEMU and is therefore a nice way to test and run Debian on ARM if you don't have the hardware.

VirtualBox Extension Pack

Oracle VM VirtualBox Extension Pack

http://www.virtualbox.org/wiki/Downloads
....
* VirtualBox 4.0.4 Oracle VM VirtualBox Extension Pack All platforms
Support for USB 2.0 devices, VirtualBox RDP and PXE boot for Intel cards. See this chapter from the User Manual for an introduction to this Extension Pack. The Extension Pack binaries are released under the VirtualBox Personal Use and Evaluation License (PUEL).


Installing VirtualBox and extension packs
http://www.virtualbox.org/manual/ch01.html#intro-installing

VirtualBox comes in many different packages, and installation depends on your host operating system. If you have installed software before, installation should be straightforward: on each host platform, VirtualBox uses the installation method that is most common and easy to use. If you run into trouble or have special requirements, please refer to Chapter 2, Installation details for details about the various installation methods.

Starting with version 4.0, VirtualBox is split into several components.

1.

The base package consists of all open-source components and is licensed under the GNU General Public License V2.
2.

Additional extension packs can be downloaded which extend the functionality of the VirtualBox base package. Currently, Oracle provides the one extension pack, which can be found at http://www.virtualbox.org and provides the following added functionality:
1.

The virtual USB 2.0 (EHCI) device; see the section called “USB settings”.
2.

VirtualBox Remote Desktop Protocol (VRDP) support; see the section called “Remote display (VRDP support)”.
3.

Intel PXE boot ROM with support for the E1000 network card.

VirtualBox extension packages have a .vbox-extpack file name extension. To install an extension, simply double-click on the package file, and the VirtualBox Manager will guide you through the required steps.

To view the extension packs that are currently installed, please start the VirtualBox Manager (see the next section). From the "File" menu, please select "Preferences". In the window that shows up, go to the "Extensions" category which shows you the extensions which are currently installed and allows you to remove a package or add a new one.

Alternatively you can use VBoxManage on the command line: see the section called “VBoxManage extpack” for details.