- This topic has 19 одговора, 5 гласова, and was last updated 20 years, 9 months раније by
.
-
Чланци
-
Skinuo sam novi kernel 2.6.14.2 i instalirao sam ga na Suse 9.3 Pro ali ne znam kako da boot-ujem taj kernel a ne ovaj stari 2.6.11.4-21.9. Znaci, treba mi pomoc oko toga kako da ga postavim u boot meni. Trenutno imam opciju da izaberem: SUSE 9.3
WINDOWS
i po default-u mi je namesteno da se podize Linux. U pitanju je GRUB Loading menu a ne LILO. Imam dva harda na kompu i sistemi su mi odvojeni, nemaju nikakve veze.Moze li neko da mi objasni sta treba da uradim ali maximalno detaljno posto ovo radim prvi put i ne bih da formatiram hard opet zbog stvari koju ne znam da uradim. Molim vas za pomoc? Treba mi maximalna pomoc!!!
HVALA VAM UNAPRED!!!
Molim te budi malo prcizniji, da li si instalirao RPM paket kernel-source-2.6.14.2
ili kernel-2.6.14.2 , oni idu zajedno, u principu trebalo bi da ih imaš oba na
sistemu, neznam kako je na Susetu ,na Mandrivi treba samo da ih instaliraš
i restartuješ računar i onda biraš koji ćeš kernel da podignešZnam da je na Mandrivi tako jer sam je koristio do skoro. Instalirao sam paket “linux 2.6.14.2.tar.gz”. Nema .rpm paketa uz njega. Pogledaj na stranici http://linux.softpedia.com/get/System/Operating-Systems/Kernels/Linux-Kernel-1960.shtml
Skinuo sam ovaj prvi, veci!
Kus, skinuo si source, sad samo kompajliraš taj source i kraj. Vidi neki tutorial za rekompajliranje kernela. Imaš objašnjenja i ovde na sajtu i u nekom od brojeva GNUZille.
Ili, ako hoćeš preko RPM-a, probaj neki SUSE-tov razvojni KOTD (“kernel of the day”)… Vidim da je 2.6.14.2 već zapakovan
Evo sta pise u readme fajlu o kompajliranju kernela koji sam skinuo:
COMPILING the kernel:
– Make sure you have gcc 2.95.3 available.
gcc 2.91.66 (egcs-1.1.2), and gcc 2.7.2.3 are known to miscompile
some parts of the kernel, and are *no longer supported*.
Also remember to upgrade your binutils package (for as/ld/nm and company)
if necessary. For more information, refer to Documentation/Changes.Please note that you can still run a.out user programs with this kernel.
– Do a “make” to create a compressed kernel image. It is also
possible to do “make install” if you have lilo installed to suit the
kernel makefiles, but you may want to check your particular lilo setup first.To do the actual install you have to be root, but none of the normal
build should require that. Don’t take the name of root in vain.– If you configured any of the parts of the kernel as `modules’, you
will also have to do “make modules_install”.– Keep a backup kernel handy in case something goes wrong. This is
especially true for the development releases, since each new release
contains new code which has not been debugged. Make sure you keep a
backup of the modules corresponding to that kernel, as well. If you
are installing a new kernel with the same version number as your
working kernel, make a backup of your modules directory before you
do a “make modules_install”.
Alternatively, before compiling, use the kernel config option
“LOCALVERSION” to append a unique suffix to the regular kernel version.
LOCALVERSION can be set in the “General Setup” menu.– In order to boot your new kernel, you’ll need to copy the kernel
image (e.g. …/linux/arch/i386/boot/bzImage after compilation)
to the place where your regular bootable kernel is found.– Booting a kernel directly from a floppy without the assistance of a
bootloader such as LILO, is no longer supported.If you boot Linux from the hard drive, chances are you use LILO which
uses the kernel image as specified in the file /etc/lilo.conf. The
kernel image file is usually /vmlinuz, /boot/vmlinuz, /bzImage or
/boot/bzImage. To use the new kernel, save a copy of the old image
and copy the new image over the old one. Then, you MUST RERUN LILO
to update the loading map!! If you don’t, you won’t be able to boot
the new kernel image.Reinstalling LILO is usually a matter of running /sbin/lilo.
You may wish to edit /etc/lilo.conf to specify an entry for your
old kernel image (say, /vmlinux.old) in case the new one does not
work. See the LILO docs for more information.After reinstalling LILO, you should be all set. Shutdown the system,
reboot, and enjoy!If you ever need to change the default root device, video mode,
ramdisk size, etc. in the kernel image, use the ‘rdev’ program (or
alternatively the LILO boot options when appropriate). No need to
recompile the kernel to change these parameters.– Reboot with the new kernel and enjoy.
IF SOMETHING GOES WRONG:
– If you have problems that seem to be due to kernel bugs, please check
the file MAINTAINERS to see if there is a particular person associated
with the part of the kernel that you are having trouble with. If there
isn’t anyone listed there, then the second best thing is to mail
them to me ([email protected]), and possibly to any other relevant
mailing-list or to the newsgroup.– In all bug-reports, *please* tell what kernel you are talking about,
how to duplicate the problem, and what your setup is (use your common
sense). If the problem is new, tell me so, and if the problem is
old, please try to tell me when you first noticed it.– If the bug results in a message like
unable to handle kernel paging request at address C0000010
Oops: 0002
EIP: 0010:XXXXXXXX
eax: xxxxxxxx ebx: xxxxxxxx ecx: xxxxxxxx edx: xxxxxxxx
esi: xxxxxxxx edi: xxxxxxxx ebp: xxxxxxxx
ds: xxxx es: xxxx fs: xxxx gs: xxxx
Pid: xx, process nr: xx
xx xx xx xx xx xx xx xx xx xxor similar kernel debugging information on your screen or in your
system log, please duplicate it *exactly*. The dump may look
incomprehensible to you, but it does contain information that may
help debugging the problem. The text above the dump is also
important: it tells something about why the kernel dumped code (in
the above example it’s due to a bad kernel pointer). More information
on making sense of the dump is in Documentation/oops-tracing.txt– If you compiled the kernel with CONFIG_KALLSYMS you can send the dump
as is, otherwise you will have to use the “ksymoops” program to make
sense of the dump. This utility can be downloaded from
ftp://ftp..kernel.org/pub/linux/utils/kernel/ksymoops.
Alternately you can do the dump lookup by hand:– In debugging dumps like the above, it helps enormously if you can
look up what the EIP value means. The hex value as such doesn’t help
me or anybody else very much: it will depend on your particular
kernel setup. What you should do is take the hex value from the EIP
line (ignore the “0010:”), and look it up in the kernel namelist to
see which kernel function contains the offending address.To find out the kernel function name, you’ll need to find the system
binary associated with the kernel that exhibited the symptom. This is
the file ‘linux/vmlinux’. To extract the namelist and match it against
the EIP from the kernel crash, do:nm vmlinux | sort | less
This will give you a list of kernel addresses sorted in ascending
order, from which it is simple to find the function that contains the
offending address. Note that the address given by the kernel
debugging messages will not necessarily match exactly with the
function addresses (in fact, that is very unlikely), so you can’t
just ‘grep’ the list: the list will, however, give you the starting
point of each kernel function, so by looking for the function that
has a starting address lower than the one you are searching for but
is followed by a function with a higher address you will find the one
you want. In fact, it may be a good idea to include a bit of
“context” in your problem report, giving a few lines around the
interesting one.If you for some reason cannot do the above (you have a pre-compiled
kernel image or similar), telling me as much about your setup as
possible will help.– Alternately, you can use gdb on a running kernel. (read-only; i.e. you
cannot change values or set break points.) To do this, first compile the
kernel with -g; edit arch/i386/Makefile appropriately, then do a “make
clean”. You’ll also need to enable CONFIG_PROC_FS (via “make config”).After you’ve rebooted with the new kernel, do “gdb vmlinux /proc/kcore”.
You can now use all the usual gdb commands. The command to look up the
point where your system crashed is “l *0xXXXXXXXX”. (Replace the XXXes
with the EIP value.)gdb’ing a non-running kernel currently fails because gdb (wrongly)
disregards the starting offset for which the kernel is compiled.Nema, jasno kao dan, jos samo kad bi mi neko rekao sta da uradim od svega ovoga, bilo bi zaista sve OK!
Gnuzilla br.03 , sadrži vrlo dobar tutorijal o kompajliranju 2.6.x Kernela, pročitati
obavezno.
Ukratko , ovi koraci:
[code] su, password, cd /usr/src ln -s linux-2.6.14.2 linux ; cd linux ; make xconfig
make ;make modules_install; cp arch/i386/boot/bzImage /boot/vmlinuz-2.6.14.2
cp System.map /boot/System.map-2.6.14.2[/code]
Napraviti initrd ako su Fajl sistemi kompajlirani kao moduli, updatovati Grub ili
Lilo , reboot, and enjoy!Do a “make” to create a compressed kernel image. It is also
possible to do “make install”Ovo make install nema potrebe. Takođe , ako sve prođe dobro posle ‘make’ i
‘make modules_install’ tek onda kopirati bzimage i Systam.map u /boot.Miroslave, iz tvojih prethodnih poruka sam shvatio da ne poznajes dobro linux, tako da… ja bih preporucio preskakanje kompajliranja kernela dok se ne udubis malo vise, posto vidim reinstalaciju sistema u najavi.
Koristi taj suse takav kakav je, lako ces posle da radis sta hoces.
Мораш бити пријављен да би поставио коментар у овој теми.