Pozdrav, prije svega. Instalirao sam skoro Slack 10. sa 2.4 kernelom, medjutim, na extra CD-u imam 2.6.xx kernel. Pa bih vas zamolio, ukoliko imate vremena, sta treba da odradim da bih instalirao, kompajlirao i podesio u LILO-u kernel 2.6, tj da podignem sistem sa 2.6.xx kernelom. Unaprijed zahvalan, Nacky.
Instaliraj taj kernel paket, pa nađi na start.linux.org.ba “kompajliranje kernela”, ti samo trebaš naštimati LILO.
Instaliraj pakete :
alsa-driver-1.0.5a_2.6.7-i486-1.tgz
kernel-generic-2.6.7-i486-1.tgz
kernel-modules-2.6.7-i486-2.tgz
sa komandom installpkg [imepaketa]
Poslije ovog samo u konzoli upisi lilo i Enter 
(Naravno sve radis kao root)
Pozdravi
Nisam znao da je alsa-driver potreban za kernel serije 2.6 :lol:
Mora da je to slack thing :rolleyes: :lol:
Ni ja nisam znao…
Samo da kažem da je dostupan novi Skype
Potreban je, jer se alsini driveri posebno kompajliraju, tj. nisu u sklopu kernela. Po defaultu dolaze driveri za kernel 2.4.26, sto znaci da ako zelimo koristiti kernel 2.6.x (u ovom slucaju 2.6.7) moramo instalirati drivere za taj kernel
Pozdrav
tj. Patrick samo ukompajlira podršku za alsu, a drajvere zapakuje posebno.
Kome se ne sviđa, može kompajlirati sam svoj 2.6.x kernel i u tom slučaju ovaj alsa paket nije potreban.
Samo da kazem da moras napravit update udev-a… ovo bi trebalo uradit prije neko boot.as sa 2.6 kernel-om. Ili procitaj moj post u ovom forumu , da znas sta treba mijenjat u udev.rules skripti…
Jah
[quote]Potreban je, jer se alsini driveri posebno kompajliraju, tj. nisu u sklopu kernela. Po defaultu dolaze driveri za kernel 2.4.26, sto znaci da ako zelimo koristiti kernel 2.6.x (u ovom slucaju 2.6.7) moramo instalirati drivere za taj kernel
Pozdrav[/quote]
To nije tacno, jer ja koristim 2.6.x otkad je izasla prva verzija i nikad nisam
tebao da instaliram alsa-drivere jer oni dolaze sa kernelom. Jedino sto je potrebno je alsa-utils. Reko da malo ustedim raji vremena sa ovim odgovorom, i naravno napominjem da ovo radi sa vanilla kernel-om i na gentoo masini; kao sto rekoh to mora da je slack thing
Ne znam, ja sam nekako shvatio da ako je pitanje postavljeno u grupi Slackware da se to pitanje i svi odgovori na njega odnose na Slackware…
U pravu si 
Ispalo je dobro, pa sam pomocu uputsva sa start.linux linka, instalirao i kompajlirao kernel. Sto se alsa-e tice, nisam instalirao nove drivere (kasno sam procitao drugi post), ali mi se “samo jednom” desilo, da mi je zvuk radio perfekt. E sad, posto, sa slackware-om sam novi, nisu mi jasne komande installpkg i pkgtool. Treba li da, sa interneta skinem npr. alsa-driver-1.xxxx.tgz, pa da udjem u direktorijum gdje se nalazi alsa-driver (npr. root) i komandom installpkg /root alsa-driver-1…xxx ili moze da se ukuca samo installpkg alsa-driver1.xxx.tar, pa ce on sam to skinuti sa interneta (kao sto je slucaj sa gentoom). Hvala, na razumijevanju i pomoci. Nacky
Ja update paketa koristim slapt-get koji možeš skinuti na:
http://software.jaos.org/
Jako je sličan Debianovom apt-get alatu, a koristi Slackware alate za samu instalaciju (instalpkg, upgradepkg i removepkg).
Hint: instalirane pakete možeš vidjeti ako izlistaš sadržaj /var/log/packages direktorija.
Još jedan popularan sistem je swaret ( http://swaret.sourceforge.net ), ali meni generalno nekako ne odgovara štimungu (čitaj, koristi mnogo “prepametnih” hackova).
I naravno, posjeti http://linuxpackages.net za svježe pakete koji ne dolaze uz Slack ili http://www.dropline.org za najnoviji GNOME.
Slack standardno “neskida” sa interneta. Instalacija paketa je kao u prvom primjeru koji si naveo. A ovdje je jos jednom objasnjeno:
http://www.slackware.com/config/packages.php
Nešto mi nije malo jasno trenutno imam slack 10 sa 2.4.26 kernelom dok pisem ovaj post upravo skidam 2.6.10 oko 34mb da li meni treba još neki paket da bi izvrsio kompal kernela?Do sada to nisam radio na slacku.
2 Gost: osim sto ces skinuti kernel napravi update udev-a (http://www.slackware.com/pb <- ovdje imas spisak paketa itd…)
a sto se tice slapt-get-a i swaret-a ovako:
slapt-get nisam koristio , a po prici ljudi na #slackware@irc.linux.org zna nekad dosta dobro zeznuti sistem.
A sto se tice swaret-a nemoj ni pomisljat, sa tim ces u 3 update-a 2 puta zeznut sistem…
eto tako , najbolje koristit pkgtool, installpkg, upgradepkg
i opet http://www.slackware.com/pb
Ma dobro sad, ja mislim da su ljudi na #slackware malo preoštri sa slapt-get. Kod mene sasvim uspješno održava u formi Slackware-current
A evo i famoznog komentara za slapt-get iz Slackware ChangeLog-a
Kao što vidite ništa posebno.
Mon Jan 24 20:41:03 PST 2005
a/aaa_base-10.1.0-noarch-1.tgz: Bumped version number to 10.1. Edited
initial email.
a/aaa_elflibs-10.1.0-i486-1.tgz: Updated initial library collection.
Please remember that (as the package description notes) this package is
only intended to be installed at an initial installation, and attempting
to "upgrade" it later may copy over newer libraries and cause damage to
your system. Some broken upgrade tools haven't learned this fact...Huh ja skido ovaj i na kraju bzImage mi izbaci nesto tipa:
/bin/sh:line1:cmp: comand not find
inconsistem kallsyms data
try seting config_kallsyms_extra_pass
make:***[vmlinuz] error
takode sam pratio output 2 javi neku greskicu.
Sigurno sam pogrijesio make config al gdje nam pojma…
takode sta poslje ovog dalje citamo sam da bi trebao uraditi nesto tipa
cp/sur/src/linux/arch/i386/boot/bzimage /boot/kerenl-2.6.10 pa dalje na lilo conf ici al ja izgleda sam negdje prije pogresio.
Et imal ko kakvu idea?
ovo je inache Readme.initrd sa CD-a
Slackware initrd mini HOWTO
by Patrick Volkerding, volkerdi@slackware.com
Sun Jun 20 01:38:41 PDT 2004
This document describes how to create and install an initrd, which may be
required to use the 2.6 kernel. Also see “man mkinitrd”.
-
What is an initrd?
-
Why to I need an initrd?
-
How do I build the initrd?
-
Now that I’ve built an initrd, how do I use it?
-
What is an initrd?
Initrd stands for “initial ramdisk”. An initial ramdisk is a very small
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
and before the main root filesystem is mounted.
- Why do I need an initrd?
The usual reason to use an initrd is because you need to load kernel
modules before mounting the root partition. Usually these modules are
required to support the filesystem used by the root partition (ext3,
reiserfs, xfs), or perhaps the controller that the hard drive is attached
to (SCSI, RAID, etc). Essentially, there are so many different options
available in modern Linux kernels that it isn’t practical to try to ship
many different kernels to try to cover everyone’s needs. It’s a lot more
flexible to ship a generic kernel and a set of kernel modules for it. The
generic 2.6 kernel in Slackware supports the ext2 filesystem (which is
used by the initrd), and also supports most IDE controllers (much like the
old bare.i kernel). So, if you have an IDE based system that uses the
ext2 filesystem, then you will not need to use an initrd to boot.
Otherwise, read on.
- How do I build the initrd?
The easiest way to make the initrd is to use the mkinitrd script included
in Slackware’s mkinitrd package. We’ll walk through the process of
upgrading to the 2.6.7 Linux kernel using the packages found in
Slackware’s testing/packages/linux-2.6.7/ directory.
First, make sure the kernel, kernel modules, and mkinitrd package are
installed (the current version numbers might be a little different, so
this is just an example):
installpkg kernel-generic-2.6.7-i486-3.tgz
installpkg kernel-modules-2.6.7-i486-2.tgz
installpkg mkinitrd-1.0.1-i486-1.tgz
Change into the /boot directory:
cd /boot
Now you’ll want to run “mkinitrd”. I’m using reiserfs for my root
filesystem, and since it’s an IDE system the reiserfs module will be
the only one I need to load:
mkinitrd -c -k 2.6.7 -m reiserfs
This should do two things. First, it will create a directory
/boot/initrd-tree containing the initrd’s filesystem. Then it will
create an initrd (/boot/initrd.gz) from this tree. If you wanted to,
you could make some additional changes in /boot/initrd-tree/ and
then run mkinitrd again without options to rebuild the image. That’s
optional, though, and only advanced users will need to think about that.
Here’s another example: Build an initrd image using Linux 2.6.7 kernel
modules for a system with an ext3 root partition on /dev/hdb3. Note
that you need both the jbd and ext3 modules to use ext3:
mkinitrd -c -k 2.6.7 -m jbd:ext3 -f ext3 -r /dev/hdb3
- Now that I’ve built an initrd, how do I use it?
Now that you’ve got an initrd (/boot/initrd.gz), you’ll want to load
it along with the kernel at boot time. If you use LILO for your boot
loader you’ll need to edit /etc/lilo.conf and add a line to load the
initrd. Here’s an example section of lilo.conf showing how this is
done:
Linux bootable partition config begins
image = /boot/vmlinuz-generic-2.6.7
initrd = /boot/initrd.gz
root = /dev/hda6
label = Linux267
read-only
Linux bootable partition config ends
The initrd is loaded by the “initrd = /boot/initrd.gz” line.
Just add the line right below the line for the kernel image you use.
Save the file, and then run LILO again (‘lilo’ at the command line).
You’ll need to run lilo every time you edit lilo.conf or rebuild the
initrd.
Other bootloaders such as syslinux also support the use of an initrd.
See the documentation for those programs for details on using an
initrd with them.
Have fun!
Fino skines kernel-2.6.10 ili koji hoces iz porodice 2.6 :), otpakujes ga u /usr/src dirktorij, …, odnosno :
izaberes sta ti treba u kernelu ili pak skines s slackwareovih stranica
config fajl za kernel , recimo config-2.6.10 i ucitas prilikom konfigurisanja
dodas u lilo.conf nes kao ovo:
image = /usr/src/linux-2.6.10/arch/i386/boot/bzImage
root = /dev/hda3
label = Linux-2.6.10
read-onlyi na kraju samo ukucas lilo i reboot
Pozdravi
PS
Ja mislim da nema potrebe za initrd