Jan 27, 2004
onlsbc1, ネットワークブートシステムの検討
--- ネットワークブート #10
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
(http://www-online.kek.jp/~inoue/para-CAMAC/
Work/SBC-Linux30.html)
高エネルギー加速器研究機構
素粒子原子核研究所
物理、オンライングループ
井上 栄二
目的
SBC-Linux29.htmlでの作業により、ディスクレスクライアント専用に /usr
ファイルを用意し、読み書き可のパーミッションでマウントできた。 ここでは
クライアント側の Xの設定を行う。
項目
(1). ディスクレスシステムのXの設定
(1-1). /etc/modules の設定
(1-2). modules情報の確認
(1-3). PCI情報の入手
(1-4). dpkg-reconfigure の実行
(2). ディスクレスシステムの起動テスト
--------------------------------------------------------------------
(1). ディスクレスシステムのXの設定
Xの設定をする前に hotplug をインストールしてかないと USBマウスを認識でき
ない。 USBマウスは /dev/input/mice に割り当てられるので Xfree86 では
/dev/input/mice を設定すること。
(1-1). /etc/modules の設定
/etc/modules に
input
usbcore
usbuchi
usbmouse
hid
を記述してリブートする。
root@onlsbc1:/etc# mount -t ext3 /dev/hda6 /mnt
root@onlsbc1:/etc# df -k
Filesystem 1k-blocks Used Available Use% Mounted on
130.87.153.112:/tftpboot/130.87.153.3
14278840 2657948 10895560 20% /
130.87.153.112:/home 14278840 2657944 10895560 20% /home
/dev/hda6 9685276 829196 8364092 10% /mnt
root@onlsbc1:/etc# ls -l /mnt
合計 112
drwxr-xr-x 2 root root 4096 11月 27 17:08 bin
drwxr-xr-x 3 root root 4096 11月 27 09:32 boot
drwxr-xr-x 2 root root 4096 11月 27 02:29 cdrom
drwxr-xr-x 9 root root 24576 1月 21 10:55 dev
drwxr-xr-x 57 root root 4096 1月 21 10:55 etc
drwxr-xr-x 2 root root 4096 11月 27 02:29 floppy
drwxrwsr-x 3 root staff 4096 11月 27 08:40 home
drwxr-xr-x 2 root root 4096 11月 27 02:29 initrd
drwxr-xr-x 5 root root 4096 11月 27 09:11 lib
drwx------ 2 root root 16384 11月 27 01:41 lost+found
drwxr-xr-x 2 root root 4096 2月 9 2002 mnt
drwxr-xr-x 2 root root 4096 12月 11 08:53 mnt1
drwxr-xr-x 2 root root 4096 12月 11 08:53 mnt2
drwxr-xr-x 2 root root 4096 11月 27 02:29 opt
drwxr-xr-x 2 root root 4096 2月 9 2002 proc
drwxr-xr-x 6 root root 4096 11月 27 16:17 root
drwxr-xr-x 2 root root 4096 11月 27 15:11 sbin
drwxrwxrwt 6 root root 4096 1月 21 10:55 tmp
drwxr-xr-x 13 root root 4096 11月 27 13:59 usr
drwxr-xr-x 13 root root 4096 11月 27 02:29 var
lrwxrwxrwx 1 root root 25 11月 27 01:58 vmlinuz -> boot/vmlinuz
-2.4.18-bf2.4
root@onlsbc1:/etc#
root@onlsbc1:/etc# cat /mnt/etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.
usbcore
usbmouse
hid
eepro100
usb-uhci
input
usbkbd
keybdev
root@onlsbc1:/etc#
root@onlsbc1:/etc# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.
#usb-uhci
#input
#usbkbd
#keybdev
#3c90x
root@onlsbc1:/etc#
root@onlsbc1:/etc# ls -l /etc/modules*
-rw-r--r-- 1 root root 285 12月 25 09:48 /etc/modules
-rw-r--r-- 1 root root 3999 12月 25 11:00 /etc/modules.conf
-rw-r--r-- 1 root root 4001 10月 22 10:41 /etc/modules.conf.old
root@onlsbc1:/etc# mv /etc/modules /etc/modules-org
root@onlsbc1:/etc# cp /mnt/etc/modules /etc/modules
root@onlsbc1:/etc#
root@onlsbc1:/etc# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.
usbcore
usbmouse
hid
eepro100
usb-uhci
input
usbkbd
keybdev
root@onlsbc1:/etc#
root@onlsbc1:/etc# reboot
root@onlsbc1:/etc#
Broadcast message from root (pts/0) (Mon Jan 26 09:57:05 2004):
The system is going down for reboot NOW!
(1-2). modules情報の確認
root@onlsbc1:/home/inoue# dmesg
Linux version 2.4.18 (root@onlpc03) (gcc version 2.95.4 20011002 (Debian prerele
ase)) #1 2004年 1月 9日 金曜日 15:25:22 JST
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 0000000012ff0000 (usable)
BIOS-e820: 0000000012ff0000 - 0000000012ff3000 (ACPI NVS)
BIOS-e820: 0000000012ff3000 - 0000000013000000 (ACPI data)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
On node 0 totalpages: 77808
zone(0): 4096 pages.
zone(1): 73712 pages.
zone(2): 0 pages.
No local APIC present or hardware disabled
Kernel command line: nfsroot=130.87.153.112:/tftpboot/130.87.153.3 ip=bootp mem=
311232K
Initializing CPU#0
Detected 497.764 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 979.76 BogoMIPS
Memory: 302768k/311232k available (1922k kernel code, 8076k reserved, 612k data,
312k init, 0k highmem)
Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Mount-cache hash table entries: 8192 (order: 4, 65536 bytes)
Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes)
Page-cache hash table entries: 131072 (order: 7, 524288 bytes)
CPU: Before vendor init, caps: 0084883f 0081813f 0000000e, vendor = 7
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (32 bytes/line)
CPU: L2 Cache: 256K (128 bytes/line)
CPU: Processor revision 1.3.2.0, 500 MHz
CPU: Code Morphing Software revision 4.2.5-8-148
CPU: 20010503 11:00 official release 4.2.5#1
CPU: After vendor init, caps: 0084893f 0081813f 0000000e 00000000
CPU serial number disabled.
CPU: After generic, caps: 0080893f 0081813f 0000000e 00000000
CPU: Common caps: 0080893f 0081813f 0000000e 00000000
CPU: Transmeta(tm) Crusoe(tm) Processor TM5400 stepping 03
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: none
PCI: PCI BIOS revision 2.10 entry at 0xfb330, last bus=0
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router VIA [1106/0686] at 00:07.0
PCI: Disabling Via external APIC routing
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device
Detected PS/2 Mouse Port.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
hda: IC25N040ATCS04-0, ATA DISK drive
hdc: SanDisk SDCFB-512, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: 78140160 sectors (40008 MB) w/1768KiB Cache, CHS=4864/255/63, UDMA(100)
hdc: 1000944 sectors (512 MB) w/1KiB Cache, CHS=993/16/63
ide-floppy driver 0.97.sv
Partition check:
hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveStatusError BadCRC }
ide0: reset: success
hda1 hda2 hda3 hda4 < hda5 hda6 hda7 >
hdc: hdc1
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Loading I2O Core - (c) Copyright 1999 Red Hat Software
I2O configuration manager v 0.04.
(C) Copyright 1999 Red Hat Software
loop: loaded (max 8 devices)
Compaq CISS Driver (v 2.4.5)
RedCreek Communications PCI linux driver version 2.20
eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.
html
eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin and others
PCI: Found IRQ 11 for device 00:0e.0
PCI: Sharing IRQ 11 with 00:07.2
eth0: OEM i82557/i82558 10/100 Ethernet, 00:0B:AB:01:50:BA, IRQ 11.
Board assembly 727095-004, Physical connectors present: RJ45
Primary interface chip i82555 PHY #1.
General self-test: passed.
Serial sub-system self-test: passed.
Internal registers self-test: passed.
ROM checksum self-test: passed (0xdbd8681d).
HDLC support module revision 1.02 for Linux 2.4
Cronyx Ltd, Synchronous PPP and CISCO HDLC (c) 1994
Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak.
ide-floppy driver 0.97.sv
Promise Fasttrak(tm) Softwareraid driver 0.03beta: No raid array found
Highpoint HPT370 Softwareraid driver for linux version 0.01
No raid array found
SCSI subsystem driver Revision: 1.00
Red Hat/Adaptec aacraid driver, Jan 9 2004
DC390: 0 adapters found
3ware Storage Controller device driver for Linux v1.02.00.016.
3w-xxxx: No cards with valid units found.
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
i2o_scsi.c: Version 0.0.1
chain_pool: 0 bytes @ c14cef40
(512 byte buffers X 4 can_queue X 0 i2o controllers)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
Sending BOOTP requests . OK
IP-Config: Got BOOTP answer from 130.87.153.112, my address is 130.87.153.3
IP-Config: Complete:
device=eth0, addr=130.87.153.3, mask=255.255.252.0, gw=130.87.152.1,
host=130.87.153.3, domain=, nis-domain=(none),
bootserver=130.87.153.112, rootserver=130.87.153.112, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
802.1Q VLAN Support v1.6 Ben Greear
vlan Initialization complete.
Looking up port of RPC 100003/2 on 130.87.153.112
Looking up port of RPC 100005/1 on 130.87.153.112
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 312k freed
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver usb_mouse
usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
usb.c: registered new driver hiddev
usb.c: registered new driver hid
hid-core.c: v1.8 Andreas Gal, Vojtech Pavlik
hid-core.c: USB HID support drivers
usb-uhci.c: $Revision: 1.275 $ time 15:12:26 Dec 24 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 11 for device 00:07.2
PCI: Sharing IRQ 11 with 00:0e.0
usb-uhci.c: USB UHCI at I/O 0xd400, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
usb.c: registered new driver keyboard
usbkbd.c: :USB HID Boot Protocol keyboard driver
hub.c: USB new device connect on bus1/1, assigned device number 2
input0: Logitech USB Optical Mouse on usb1:2.0
mice: PS/2 mouse device common for all mice
root@onlsbc1:/home/inoue#
(1-3). PCI情報の入手
root@onlsbc1:/home/inoue# lspci -vv
00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge (rev 01)
Subsystem: Transmeta Corporation: Unknown device 0295
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- [disabled] [size=1M]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00:10.0 VGA compatible controller: Silicon Motion, Inc. SM720 Lynx3DM (rev b1) (
prog-if 00 [VGA])
Subsystem: Silicon Motion, Inc. SM720 Lynx3DM
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR-
Command: RQ=0 SBA- AGP- 64bit- FW- Rate=
root@onlsbc1:/home/inoue#
注.
lspciコマンドを実行した時に表示される bus identifier は、hexadecimal
表示である。 上で表示されている Lynx3DM の VGAコントローラは、デシマル
表示では、
PCI:0:16:0
ということになる。
(1-4). dpkg-reconfigure の実行
dpkg-reconfigure を実行する。
注.
X window system をまだインストールしていない場合には、
# apt-get install x-window-system
を実行する。
root@onlsbc1:/# dpkg-reconfigure xserver-xfree86
Configuring Xserver-xfree86
The /etc//X11/XF86Config-4 file, which contains the configuration
information for the XFree86 version 4 X server, can be handled
automatically by debconf, or manually by you.
Note that only specific, marked sections of the cinfiguration file will
be habdled by debconf if you select this option; if those markers are
absent, the configuration file will not be updated automatically, and
you will have to update the file manually, or move or delete the file.
Manage XFree86 4.x server configuration file with debconf?
<-- "Yes" を選択して enterキーを押す
:
Configuration Xserver-xfree86
For the Window System graphical user interface to operate correctly,
it is necessary to select a video card driver for the X server.
Drivers are typically named for the video card or chipset manufacturer,
or for a specific model or family of chipsets.
Select the desired X server driver.
<-- "silliconmotion" を選択して enterキーを押す
:
Configuring Xserver-xfree86
The X server configuration file associates your video card with a name
that you may provide. This is usually the vendor or brand name
followed by the model name, e.g., "3Dfx Voodoo3" or "ATI Rage Fury
Maxx".
Enter an identifier for your video card.
<-- "Lynx3DM" と入力して enterキーを押す
:
Configuring Xserver-xfree86
Users of PowerPC machines, and users of any computer with multiple
video devices, should specify the BusID of the video card in the
format:
PCI:nn:nn:nn
(where each nn is a decimal number referring to the card's bus, device,
and function number, respectively).
For users of multi-head setups, this option will configure only one of
the heads. Further configuration will have to be done manually in the
X server configuration file, /etc/X11/XF86Config-4.
You may wish to use the "lspci" command to determine the bus location
of your PCI or AGP video card. Keep in mind that lspci reports the
bus, device, and function number in hexadecimal, not decimal.
When possible, this question has been pre-answered for you and you
should accept the default unless you know it doesn't work.
<-- "PCI:0:16:0" と入力して enterキーを押す
:
Configuring Xserver-xfree86
Typically, the amount of dedicated memory your video card has is
autodetected by the X server, but some integrated video chips (such as
the Intel i810) have little or no video memory of their own, and
instead borrow main system memory for their needs.
It is pwrfectly acceptable to leave this parameter blank; only if your
video card lacks RAM, or if the X server has trouble autodetecting the
amount, is it necessary to specify the amount of video RAM.
Enter the amount of memory (in kB) to be used by your video card.
<-- "4000" と入力して enterキーを押す
:
Configuring Xserver-xfree86
Rather than communicating directly with the video hardware, the X
server may be configured to perform some operations, such as video mode
switching, via the kernel's framebuffer driver.
In theory, either approach should work, but in practice, sometimes one
does and the other does not. Enabling this option is the safe bet, but
feel free to turn it off if it appears to cause problems.
Use kernel framebuffer device interface?
<-- "No" を選択して enterキーを押す
:
Configuring Xserver-xfree86
For the X server to handle your keyboard correctly, an XKB rule set
must be chosen.
Users of most keyboards should enter "xfree86". Users of Sun Type 4
and Type 5 keyboards, however, should enter "sun".
Advanced users can use any defined XKB rule set. If the xlibs package
has been unpacked, see the /etc/X11/xkb/rules directory for available
rule sets.
If you don't know what rule set to use, enter "xfree86".
Please select the XKB rule set to use.
<-- "xfree86" と入力して enterキーを押す
:
Configuring Xserver-xfree86
For the X server to handle your keyboard correctly, a keyboard model
must be entered. Available models depend on which XKB rule set is in
use.
The "pc101" keyboard is a traditional IBM PC/AT style keyboard with 101
keys, histrorically common in the United States. It does not have the
"logo" or "menu" keys.
The "pc104" keyboard is like the pc101 model, with additional keys.
These keys are usually engraved with a "logo" symbol (there is
typically a pair of these, between each set of control and keys),
and a "menu" key.
The "pc102" and "pc105" models are versions of the pc101 and pc104
keyboards, respectively, often found in Europe.
The "macintosh" model is for Macintosh keyboards where the kernel and
console tools use the new input layer which uses Linux keycodes;
"macintosh_old" is for Macintosh keyboard users who are not using the
new input layer.
<-- "Ok" を選択して enterキーを押す
:
Configuring Xserver-xfree86
Please select your keyboard model.
<-- "jp106" と入力して enterキーを押す
:
Configuring Xserver-xfree86
For the X server to handle your keyboard correctly, a keyboard layout
must be entered. Available layouts depend on which XKB rule set and
keyboard model were previously selected.
Advanced users can use any layout supported by the selected XKB rule
set. If the xlibs package has been unpacked, see the /etc/X11/xkb/rules
directory for available rule sets, and the /etc/X11/xkb/symbols
directory for available layouts.
Users of U.S. English keyboards should enter "us". Users of keyboards
localized code. E.g., France uses "fr", and Germany uses "de".
Please select your keyboard layout.
<-- "jp" と入力して enterキーを押す
:
Configuring Xserver-xfree86
For the X server to handle your keyboard as you desire, a keyboard
variant may be entered. Available variants depend on which XKB rule
set, model, and layout were previously selected.
Many keyboard layouts support an option to treat "dead" key such as
non-spacing accent marks and diaereses as normal spacing keys, and if
this is the prefered behavior, enter "nodeadkeys".
Advanced users can use any variant supported by the selected XKB
layout. If the xlibs package has been unpacked, see the
/etc/X11/xkb/symbols directory for the file corresponding to your
selected layout for available variants.
Users of U.S. English keyboards should generally leave this entry
blank.
Please select your keyboard variant.
<-- enterキーを押す
:
Configuring Xserver-xfree86
For the X server to handle your keyboard as you desire, keyboard
options may be entered. Available options depend on which XKB rule set
was previously selected. Not all options will work with evely keyboard
model and layout.
For example, if you wish the CapsLock key to behave as an addtional
Control key, you may enter "ctrl:nocaps"; if you would like to switch
the Caps Lock and left Control keys, you may enter "ctrl:swapcaps".
Advanced users can use any options compatible with the selected XKB
model, layout and variant. If the xlibs package has been unpacked, see
the /etc/X11/xkb/symbols directory available options files, which
define only partial keyboard translations. (For example,
If you don't know what options to use, leave this entry blank.
Please select your keyboard options.
<-- enterキーを押す
:
Configuring Xserver-xfree86
For the X window System graphical user interface to operate correctly,
certain characteristics of your mouse (or other pointing device, such
as a trackball) must be known.
It is necessary to determine which port (connection type) your mouse
uses. Serial ports use D-shaped connectors with 9 or 25 pins (a.k.a.
DB-9 or DB-25); the mouse connector is female (ha holes) and the
computer connector is male (has pins). PS/2 ports are small round
connector side female. You may alternatively have a USB mouse, a
bus/inport (very old) mouse, or be using the gpm program as a repeater.
If you need to attach or remove PS/2 or bus/inport devices from your
computer, please do so with the computer's power off.
Please choose your mouse port.
<-- "/dev/input/mice" を選択して enterキーを押す
注.
USBマウスを使用する場合は、/de/input/mice を選択すること。
:
Configuring Xserver-xfree86
Most programs in the X Window System expect your mouse to have 3
buttons (left, right, and middle). Mice with only 2 buttons can
emulate the presence of a middle button by treating simultaneous clicks
or drags of the left and right button as middle button events.
This option may also be used on mice with 3 or more buttons; the middle
button will continue to work normally.
Note that mouse buttons in excess of five (counting a scroll wheel as
two buttons, one each for "up" and "down", and a third if the wheel
"clicks") are not yet supported with this configuration tool.
Emulate 3 button mouse?
<-- "Yes" を選択して enterキーを押す
:
Configuring Xserver-xfree86
Events from a wheeled mouse's wheel can be treated as clicks of
additional buttons (buttons 4 and 5). Some X applications treat
buttons 4 and 5 as scroll-up and scroll-down events, making the mouse
wheel work as expected. This is application-level behavior however, and
may not always work. Also, exotic mice with more than 3 buttons in
addition to a wheel may behave in an unexpected fashion if this option
is set.
Enabling this option is harmless if your mouse has no scroll wheel.
Note that mouse buttons in excess of five (counting a scroll wheel as
two buttons, one each for "up" and "down". and a third if the wheel
"clicks") are not yet supported with this configuration tool.
Enable scroll events from mouse wheel?
<-- "Yes" を選択して enterキーを押す
:
Configuring Xserver-xfree86
The X server configuration file associates your monitor with a name
that you may provide. This is usually the vendor or brand name
followed by the model name, e.g., "Sony E200" or "Dell E770s".
Enter an identifier for your monitor.
<-- "FlexScan L465" と入力して enterキーを押す
:
Configuring Xserver-xfree86
If your monitor is a Liquid-crystal display (which is the case with
almost all laptops), you should set this option.
Users of traditional cathode-ray tube (CRT) monitors should not set
this option.
Is your monitor an LCD device?
<-- "Yes" を選択して enterキーを押す
:
Configuring Xserver-xfree86
For the X Window System graphical user interface to operate correctly,
certain characteristics of your monitor must be known.
For the "simple" option, you need only know the monitor's physical
size; this will set some configuration values appropriate for a typical
CRT of the corresponding size, but may be suboptmal for high-quality
CRT's. (This option is disabled for LCD panel users, since such
displays are configured for a particular resolution.)
The "medium" option will present you with a list of resolutions and
refresh rates, such as "800x600 @ 85Hz"; you should choose the best
mode you wish to use (and that you know your monitor is capable of).
The "advanced" option will let you specify your monitor's horizontal
sync and vertical tolerances directory.
Pleae choose a method for selecting your monitor characteristics.
<-- "Advanced" を選択して enterキーを押す
:
Configuring Xserver-xfree86
Please enter either a comma-separated list of discrete values (for
fixed-frequency displays), or a pair of values separated by a dash (all
modern CRT's). This information should be available in your monitor's
manual. Values lower than 30 or higher than 130 are extremely rare.
Enter your monitor's horizontal sync range.
<-- "24.8-80" を入力して enterキーを押す
:
Configuring Xserver-xfree86
Please enter either a comma-separated list of discrete values (for
fixed-frequency displays), or a pair of value separated by a dash (all
modern CRT's). This information should be available in your monitor's
manual. Values lower than 50 or higher than 160 are extremely rare.
Enter your monitor's vertical refresh range.
<-- "50-75" を入力して enterキーを押す
:
Configuring Xserver-xfree86
If there are some resolutions you would not like the X server to use
even if your hardware is capable of them, remove them from the list
below. removing all of them is effectively the same as removing none,
since in both cases the X server will attempt to use the highest
possible resolution.
Select the video modes you would like the X server to use.
<-- "1280x1024, 1024x768, 800x600, 640x480" を選択して enterキーを押す
:
Configuring Xserver-xfree86
Usually 24-bit color is desirable, but on graphics cards with limited
amounts of framebuffer memory, higer resolutions may be achieved at
the expense of higher color depth. Also, some cards support hardware
3D acceleration only for certain depths. Consult your video card
manual for more information.
Note that on some old ATI hardware, such as the Mach8 (VGA Wonder),
Mach32, and early Mach64 ("GX") chipsets, depths higher than 8 are
unsupported.
(So-called "32-bit color" is actually 24 bits of color information plus
8 bits of alpha channel or simple zero padding; the X Window System can
handle both. If you want either, select 24 bits.)
Please select your desired default color depth in bits.
<-- "24" を選択して enterキーを押す
:
Configuring Xserver-xfree86
It is possible to customize (or completely omit) the list of modules
that the X server loads by default. This option is for advanced users.
In most cases, all of these modules except xtt should be enabled.
The GLCore and glx modules enable software OpenGL rendering. the dri
module enables support in the X server for Direct Rendering
Infrastructure (DRI). Note that support for DRI must also exist in the
kernel, the video card, and the installed version of the Mesa libraries
for hardware-accelerrated 3D operations using DRI to work. Otherwise,
the server falls back to software redering.
The vbe and ddc modules enable support for VESA BIOS Extentions and
Data Display Channell, respectively. These modules are to query
monitor capabilities via the video card. The int10 module is a
real-mode x86 emulator that is used to softboot secondary VGA card.
Note that the vbe module depends on the int10 module, so if wish to
enable vbe, enable int10 as well.
The dbe module enables the double-buffering extention in the server,
and is usefull for animation and video operations.
<-- "Ok" を選択して enterキーを押す
:
Configuring Xserver-xfree86
Select the XFree86 server modules that should be loaded by default.
<-- "GLcore, bitmap, dbe, ddc, dri, extmod, freetype, glx, int10, record, speedo, type1, vbe" を選択して enterキーを押す
:
Configuring Xserver-xfree86
The Files section of the X server configuration file tells X server
where to find server modules, the RGB color database, and font files.
This option is for advanced users. In most cases, you should enable
it.
Disable this option if you want to write your own "Files" section into
the XFree86 server configuration file. You may wish to do this if you
need to remove the reference to the local font server, add a reference
to a different font server, or rearrange the default set of local font
paths.
Write default Files section to configuration file?
<-- "Yes" を選択して enterキーを押す
:
Configuring Xserver-xfree86
The DRI section of the X server configuration file determines the
permissions of the DRI device. This option is for advanced users. In
most cases, you should enable it.
Disable this option if you want to write your own "DRI" section into
the XFree86 server configuration file. You may wish to do this if you
want to change the access privileges to the DRI port.
Write default DRI section to configuration file?
<-- "Yes" を選択して enterキーを押す
Wrote X server configuration to /etc/X11/XF86Xonfig-4.
root@onlsbc1:/#
(2). ディスクレスシステムの起動テスト
システムをリブートする。
ok. ディスクレスクライアントでXが立ち上がった。
ログインした時の画面
---xxxx