[Pardus-kullanicilari] Pardus'ta Kernel nerede - Kernele Raid icin nasil yama yapilir?
Lectin
lectin at gmail.com
19 Eyl 2007 Çar 02:24:11 EEST
Verdiğiniz yanıtlardan ötürü ayrı ayrı teşekkür ediyorum.
Pardus'u kullanmaya başlayalı henüz üç hafta olacak. Her şey güzel güzel
giderken, kasa içinde, PCI'a takılı SATA RAiD controller kart üzerinde, iki
adet ntfs formatlı HD'im mevcut. Ama WiN altında sorunsuz olan bu diskleri,
Pardus hiç görmedi. Bu sorunu aşamadığım, ama acaba yeni bir çözüm yolu
üretilebilir mi diye tekrar yazmayı uygun görmüştüm.
Önce kısa yanıtlar ve sorular:
"buradaki "linux" en son kernela sembolik bağdır" --> burada yapılan bir
değişiklik, aktif, kurulu kernele yansır mı bu durumda ?
evet bu konularla hiç haşır neşir değilim, ama temel bazı şeyleri de bir an
önce öğrenmek istiyorum; son bir ayda, hem ev hem de ofiste o kadar çok
tekrar kurulum yapmak zorunda kaldım ki (bazen hatalarımdan dolayı, mevcut
WiN partisyonum da uçtu) artık tekrar tekrar kurmak da istemiyorum.
Öğrenelim diye sizlerden fikir almaya çalışıyorum.
dmraid ile biraz haşır neşir oldum sayılır, dmraid sayfasında desteklediğini
söylüyor ama: dmraid -s --> NO RAID DISK FOUND diyor; dolayısı ile dmraid
-ay zaten bir şeyi aktive edemiyor.
Takılı olan controller kart özellikleri şöyle sıralanıyor:
Mode: Serial ATAII phase one; Controller: INITIO INI1622; RAID: RAID 0 and
RAID 1; Channel: Two internal serial ATA ports (supports native command
queuing - NCQ -, supports tagged command queuing -TCQ-); OS support ...Linux
2.4x, 2.6x.
Firma kartın CDsinde bir README vermiş (patch yapmak için). Aktarıyorum:
CARD MODELS
===========
The patch supports the following multi I/O PCI card models:
8139, 8159, 8169, 4008A, 4018A, 4018C, 4027A, 4037A, 4037D, 4056A, 4056D,
4066A, 4066R, 4079A, 4079D, 4079R, 4089A, 4096A.
KERNEL VERSIONS
===============
There is a separate patch for 2.4.x and 2.6.x kernel versions.
For installation instructions, see below.
The 2.4.x patch has been tested with the Linux kernel source version 2.4.20
and 2.4.27. However, it should work with other versions as well.
The 2.6.x patch has been tested with the Linux kernel source version 2.6.8.1
.
However, it should work with other versions as well.
INSTALLATION
============
In order to apply the patch the Linux kernel sources need to be installed
and the kernel needs to be compiled. Refer to the documentation that came
with your Linux distribution for information on how to do that.
When the kernel sources are installed and you are able to successfully
build a kernel then follow the installation instructions given below
to apply the patch.
Kernel 2.6.x
------------
1. Copy the patch file multi_io_patch_2.6.x.diff to /usr/src.
2. Change to the directory /usr/src/linux.
3. To apply the patch issue the following command:
patch -p1 < ../multi_io_patch_2.6.x.diff
Warnings produced by patch can be ignored.
4. To configure the kernel run the following command:
make menuconfig
Alternatively, you can use the command recommended by your
Linux distribution, e.g. make xconfig
5. In the kernel configuration menus make sure that the options
parport, parport_pc and serial are selected.
These options can be found at the following locations:
Device Drivers ->
Parallel port support ->
parport
Device Drivers ->
Parallel port support ->
PC-style hardware ->
parport_pc
Device Drivers ->
Character devices ->
Serial drivers ->
8250/16550 and compatible serial support ->
serial
If one of these options is selected to compile as a module
then the Multi I/O PCI card support has also to be compiled
as a module. See the next step for details.
6. Now the following new kernel config option is available:
Device Drivers ->
Character devices ->
Serial drivers ->
Multi I/O PCI Card support
Enable the option "Multi I/O PCI Card support". If one of the
options parport, parport_pc or serial in the previous step was selected
to compile as a module then this option has also to be compiled
as a module.
7. Check the following kernel configuration parameter:
Device Drivers ->
Character devices ->
Serial drivers ->
8250/16550 and compatible serial support ->
Maximum number of non-legacy 8250/16550 serial ports
Make sure that this parameter is set to the number of external serial
ports available on PCI cards + 4. For example, if you use an 4066A
card (8 serial ports) then this paramater needs to be set to 12.
If you use two such cards then the parameter needs to be set to 20.
8. Build and install the kernel. Refer to the documentation of your
Linux distribution for more information on the required steps.
9. When the new kernel is running, the driver will be automatically
loaded and initialized if compiled as a static driver. If the driver was
compiled as a module then it needs to be loaded with the
following command:
modprobe snx_multi_io
You can decide to add this command to an init script.
Now the multi I/O PCI card driver should work and the serial and
parallel ports of your card are available to the system.
Device Files
------------
After you installed your Linux system there will be a default set of
device files in /dev. For each serial port you plan to use there
needs to be a device file named /dev/ttySN, where N is an integer number
usually starting at zero. Issue the following command to list the
existing serial device files:
# ls -al /dev/ttyS*
Note that usually the first 4 device files (/dev/ttyS0../dev/ttyS3) will
be assigned to on-board serial ports (COM1..COM4). External serial
ports, which include the ports, will be assigned to /dev/ttyS4 and
higher numbers. If there are not enough /dev/ttySN device files available
by default, you have to create further device files manually.
For example, if you use an 4066A card (8 serial ports) then you have
to ensure that /dev/ttyS4 to /dev/ttyS11 do exist in your system.
How to create additional device files?
You should first try to use the MAKEDEV script. This script is usually
located in /dev/MAKEDEV but might also have a copy (or a symbolic link)
in /sbin/MAKEDEV. The command is used as follows:
# /dev/MAKEDEV -v ttyS8
Repeat this command for any device file you need to create.
Note: On some Linux distributions it may be necessary to use the
mknod command to create device files. Consult your Linux documentation
for information on how to do that. Using MAKEDEV is the preferred way.
After you created additional device files you should set the correct
ownership and access mode on these files. Issue an
# ls -al /dev/ttyS0
command to see the mode set on the first device file.
Use the chown and chmod commands to set the same rights on the newly
created files, for example:
# chown root:root /dev/ttyS8
# chmod 555 /dev/ttyS8
Repeat these commands for any device file you created.
Biraz tekrar gibi olacak ama aşağıda sorunu tekrarlıyorum (ve elimdeki
verileri):
pci aygit listesinden:
00:0a.0 SATA controller: Initio Corporation INI-1623 PCI SATA-II Controller
(rev 02) (prog-if 00 [Vendor specific])
Subsystem: Initio Corporation INI-1623 PCI SATA-II Controller
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5
I/O ports at ed00 [size=256]
I/O ports at ec00 [size=256]
I/O ports at ea00 [size=256]
I/O ports at e900 [size=256]
I/O ports at e600 [size=256]
Memory at dfd00000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at dfc00000 [disabled] [size=256K]
Capabilities: [dc] Power Management version 2
dmesg çıktısı (ilgili olduğunu düşündüğüm kısım):
sata_via 0000:00:0f.0: version 2.0
ACPI: PCI Interrupt 0000:00:0f.0[ B] -> GSI 20 (level, low) -> IRQ 169
PCI: VIA IRQ fixup for 0000:00:0f.0, from 10 to 9
sata_via 0000:00:0f.0: routed to hard irq line 9
ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF90 irq 169
ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF98 irq 169
scsi0 : sata_via
ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ATA: abnormal status 0x7F on port 0xEFE7
scsi1 : sata_via
ata2: SATA link down 1.5 Gbps (SStatus 0 SControl 300)
ATA: abnormal status 0x7F on port 0xEFA7
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ACPI: PCI Interrupt 0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 177
PCI: VIA IRQ fixup for 0000:00:10.4, from 5 to 1
# sfdisk --list
Disk /dev/hda: 30401 cylinders, 255 heads, 63 sectors/track
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/hda1 * 0+ 11260 11261- 90453951 7 HPFS/NTFS
/dev/hda2 11261 30400 19140 153742050 f W95 Ext'd (LBA)
start: (c,h,s) expected (1023,254,63) found (1023,0,1)
/dev/hda3 0 - 0 0 0 Empty
/dev/hda4 0 - 0 0 0 Empty
/dev/hda5 11261+ 11521 261- 2096451 83 Linux
/dev/hda6 11522+ 14132 2611- 20972826 83 Linux
/dev/hda7 14133+ 30399 16267- 130664646 83 Linux
1. Soru:
pci kartı görüyor, ama bu karta takılmış iki adet HD'i neden görmüyor
olabilir (diskler sıfır değil ve ntfs formatında<--- bu bir fark oluşturur
mu)?
2. Soru:
bu benim basit bir kaç ayarla değiştirebileceğim bir durum mudur?
3. Soru:
Pardus'un kullandığı (2007-2) kernel'inde RAiD desteği VAR mı, YOK mu?
("olmayabileceği" yanıtını bir arkadaş vermiş; bunu kesin bir biçimde bilen
biri yanıt verirse sevinirim)
YOK ise ---> 4. Soru:
YAMA denilen şeyi nasıl yapacağız?
VAR ise ---> 5. Soru:
TLDP.org'da güzel bir "RAID HOWTO" mevcut. Burada şu deniliyor (çevirerek
aktarıyorum): Eğer sisteminde RAID desteği varsa, /proc/mdstat adlı bir
dosyan olmalı... Eğer bu yoksa, belki kullandığın kernelin RAID desteği
olmayabilir.
Evet, bu dosya benim dosya dizinimde yok. Ama burada da bir ihtimal
dahilinde (maybe) yazıldığı için, ve Pardus kerneli bunu destekliyor ise,
bahsedilen "mdstat" dosyası başka bir ad altında olabilir mi?
Bir pratik çözüm varsa, anlatımlarınızı yeni başlayan birinin anlayacağı
biçimde anlatabilirseniz sevinirim.
-------------- sonraki bölüm --------------
Bir HTML eklentisi temizlendi...
URL: http://liste.pardus.org.tr/pardus-kullanicilari/attachments/20070919/31d6396e/attachment-0001.htm
Pardus-kullanicilari mesaj listesiyle ilgili
daha fazla bilgi