Aller au contenu
  • Pas encore inscrit ?

    Pourquoi ne pas vous inscrire ? C'est simple, rapide et gratuit.
    Pour en savoir plus, lisez Les avantages de l'inscription... et la Charte de Zébulon.
    De plus, les messages que vous postez en tant qu'invité restent invisibles tant qu'un modérateur ne les a pas validés. Inscrivez-vous, ce sera un gain de temps pour tout le monde, vous, les helpeurs et les modérateurs ! :wink:

compiler kernel 2.6 Debian stable + patch badmem


juddix
 Partager

Messages recommandés

Bonsoir,

 

J' ai réussi a patcher mon kernel 2.6.15.7 que j' ai téléchargé sur http://www.kernel.org/ avec un patch badmem ici des patch en .diff où ici en .patch mais pas très a jour en .patch et un peu bizarre

source = http://badmem.sourceforge.net/ Merci Kewlcat

 

 

 

$ cd /home/tony/src/linux-2.6.15.7

[email protected]:~/src/linux-2.6.15.7$ patch -p1 < badmem-5.1ns-kernel-2.6.15.diff

patching file CREDITS

patching file Documentation/badmem.txt

patching file Documentation/badmem_conf.txt

patching file Documentation/kernel-parameters.txt

patching file Documentation/memory.txt

patching file arch/i386/Kconfig

patching file arch/i386/defconfig

patching file arch/i386/mm/init.c

patching file include/linux/badmem.h

patching file include/linux/page-flags.h

patching file mm/Kconfig

patching file mm/Makefile

patching file mm/badmem_proc.c

patching file mm/badmemlib_version.c

patching file mm/modparse.c

patching file mm/page_alloc.c

[email protected]:~/src/linux-2.6.15.7$

 

make menuconfig

 

badmem.jpg

 

badmem1.jpg

 

badmem2.jpg

 

De quelle manière compiler le noyau ?

 

ici, une méthode pour compiler son noyau

 

il vaudrais mieux que je passe directement par des kernel fournit par debian ?

Que faire ?

 

[email protected]:~/src/linux$ make-kpkg clean

/usr/share/kernel-package/rules:1637: *** Error. I do not know where the kernel image goes to [kimagedest undefined] The usual case for this is that I could not determine which arch or subarch tihs machine belongs to. Please specify a subarch, and try again.. Arrêt.

euh...... qu' est ce que j' ai oublié ?

 

sinon, j' ai bien installé les dépendances :

apt-get install build-essential fakeroot kernel-package libglib2.0-dev libgtk2.0-dev libqt3-mt-dev libncurses5-dev tk-dev

apt-get install cramfsprogs initrd-tools

 

sinon, je ne suis pas obliger d' utiliser make-kpkg ?

 

Voila bon, je verais ça demain, je vais au taff

@+

Lien vers le commentaire
Partager sur d’autres sites

salut,

 

tu peux le faire sans les outils debian:

make && make modules_install

 

et ensuite copier arch/i386/boot/bzImage, System.map et .config dans /boot

et modifier lilo/grub à la main

 

sinon avec make-kpkg, il faut au moins spécifier la cible kernel-image

make-kpkg kernel-image

et installer ensuite le package deb généré

http://andesi.org/index.php?node=77#A27

Lien vers le commentaire
Partager sur d’autres sites

avec les outils debian, j' ai toujours le message d' erreur :

$ make-kpkg --rootcmd fakeroot --revision=2.6.15.7 kernel-image

/usr/share/kernel-package/rules:1637: *** Error. I do not know where the kernel image goes to [kimagedest undefined] The usual case for this is that I could not determine which arch or subarch tihs machine belongs to. Please specify a subarch, and try again.. Arrêt.

 

Et sinon, a la main le make passe pas.. :P en user

CC mm/shmem.o

gcc -m32 -DKERNELLIB_TEST -o mm/badmemkernellib_version -I /usr/src/badmem/badme mlib/include mm/badmemlib_version.c -lbadmem -lm

mm/badmemkernellib_version: error while loading shared libraries: libbadmem.so: cannot open shared object file: No such file or directory

rm -f mm/badmemkernellib_version # This file is not used any more, so we can d elete it

if [ -e /usr/src/badmem/configure -a ! -e /usr/src/badmem/Makefile ]; then cd /u sr/src/badmem; export CFLAGS=""; export LDFLAGS=""; ./configure ; fi

make -C /usr/src/badmem/badmemlib IN_KERNEL_MODE=1 clean links

rm -f *.o *~ libbadmem.so.? include/*~ libbadmem.a memtest_badmemlib.o

ln -sf lib.c kernel_lib.c; ln -sf patn.c kernel_patn.c; ln -sf mdf.c kernel_md f.c; ln -sf hash.c kernel_hash.c;

ln: ne peut enlever `kernel_lib.c': Permission non accordée

ln: ne peut enlever `kernel_patn.c': Permission non accordée

ln: ne peut enlever `kernel_mdf.c': Permission non accordée

ln: ne peut enlever `kernel_hash.c': Permission non accordée

make[2]: *** [links] Erreur 1

make[1]: *** [mm/kernel_badmemlib.o] Erreur 2

make: *** [mm] Erreur 2

 

Puis en root:

c' est encore pire......

 

x# make

CHK include/linux/version.h

CHK include/linux/compile.h

SKIPPED include/linux/compile.h

CHK usr/initramfs_list

gcc -m32 -DKERNELLIB_TEST -o mm/badmemkernellib_version -I /usr/src/badmem/badme mlib/include mm/badmemlib_version.c -lbadmem -lm

mm/badmemkernellib_version: error while loading shared libraries: libbadmem.so: cannot open shared object file: No such file or directory

rm -f mm/badmemkernellib_version # This file is not used any more, so we can d elete it

if [ -e /usr/src/badmem/configure -a ! -e /usr/src/badmem/Makefile ]; then cd /u sr/src/badmem; export CFLAGS=""; export LDFLAGS=""; ./configure ; fi

make -C /usr/src/badmem/badmemlib IN_KERNEL_MODE=1 clean links

rm -f *.o *~ libbadmem.so.? include/*~ libbadmem.a memtest_badmemlib.o

ln -sf lib.c kernel_lib.c; ln -sf patn.c kernel_patn.c; ln -sf mdf.c kernel_md f.c; ln -sf hash.c kernel_hash.c;

ln -sf lib.c memtest_lib.c; ln -sf patn.c memtest_patn.c; ln -sf mdf.c memtest _mdf.c; ln -sf hash.c memtest_hash.c; ln -sf string.c memtest_string.c; ln -s f vsprintf.c memtest_vsprintf.c;

make -C /usr/src/badmem/badmemlib IN_KERNEL_MODE=1 kernel_badmemlib.o

gcc -m32 -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing - fno-common -ffreestanding -O2 -fomit-frame-pointer -pipe -msoft-float -mpref erred-stack-boundary=2 -fno-unit-at-a-time -march=i686 -mtune=pentium4 -Iinclude /asm-i386/mach-default -Wdeclaration-after-statement -Wno-pointer-sign -I/usr/sr c/badmem/badmemlib/include -I./include -D__KERNEL__ -c -o kernel_lib.o kernel_li b.c

In file included from /usr/include/linux/string.h:23,

from kernel_lib.c:4:

/usr/include/asm/string.h:41: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'strncpy':

/usr/include/asm/string.h:55: error: 'src' undeclared (first use in this functio n)

/usr/include/asm/string.h:55: error: (Each undeclared identifier is reported onl y once

/usr/include/asm/string.h:55: error: for each function it appears in.)

/usr/include/asm/string.h:55: error: 'dest' undeclared (first use in this functi on)

/usr/include/asm/string.h:55: error: 'count' undeclared (first use in this funct ion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:77: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'strncat':

/usr/include/asm/string.h:94: error: 'src' undeclared (first use in this functio n)

/usr/include/asm/string.h:94: error: 'dest' undeclared (first use in this functi on)

/usr/include/asm/string.h:94: error: 'count' undeclared (first use in this funct ion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:121: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'strncmp':

/usr/include/asm/string.h:139: error: 'cs' undeclared (first use in this functio n)

/usr/include/asm/string.h:139: error: 'ct' undeclared (first use in this functio n)

/usr/include/asm/string.h:139: error: 'count' undeclared (first use in this func tion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:180: error: syntax error before 'strlen'

/usr/include/asm/string.h:193: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function '__memcpy':

/usr/include/asm/string.h:206: error: 'n' undeclared (first use in this function )

/usr/include/asm/string.h:206: error: 'to' undeclared (first use in this functio n)

/usr/include/asm/string.h:206: error: 'from' undeclared (first use in this funct ion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:215: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function '__constant_memcpy':

/usr/include/asm/string.h:217: error: 'n' undeclared (first use in this function )

/usr/include/asm/string.h:218: error: 'to' undeclared (first use in this functio n)

/usr/include/asm/string.h:218: error: 'from' undeclared (first use in this funct ion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:299: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'memmove':

/usr/include/asm/string.h:302: error: 'dest' undeclared (first use in this funct ion)

/usr/include/asm/string.h:302: error: 'src' undeclared (first use in this functi on)

/usr/include/asm/string.h:307: error: 'n' undeclared (first use in this function )

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:326: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'memchr':

/usr/include/asm/string.h:330: error: 'count' undeclared (first use in this func tion)

/usr/include/asm/string.h:338: error: 'c' undeclared (first use in this function )

/usr/include/asm/string.h:338: error: 'cs' undeclared (first use in this functio n)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:342: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function '__memset_generic':

/usr/include/asm/string.h:349: error: 'c' undeclared (first use in this function )

/usr/include/asm/string.h:349: error: 's' undeclared (first use in this function )

/usr/include/asm/string.h:349: error: 'count' undeclared (first use in this func tion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:362: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function '__constant_c_memset':

/usr/include/asm/string.h:375: error: 'c' undeclared (first use in this function )

/usr/include/asm/string.h:375: error: 'count' undeclared (first use in this func tion)

/usr/include/asm/string.h:375: error: 's' undeclared (first use in this function )

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:382: error: syntax error before 'strnlen'

/usr/include/asm/string.h:382: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'strnlen':

/usr/include/asm/string.h:397: error: 's' undeclared (first use in this function )

/usr/include/asm/string.h:397: error: 'count' undeclared (first use in this func tion)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:410: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function '__constant_c_and_count_memset':

/usr/include/asm/string.h:412: error: 'count' undeclared (first use in this func tion)

/usr/include/asm/string.h:414: error: 's' undeclared (first use in this function )

/usr/include/asm/string.h:416: error: 'pattern' undeclared (first use in this fu nction)

/usr/include/asm/string.h: At top level:

/usr/include/asm/string.h:469: error: syntax error before 'size_t'

/usr/include/asm/string.h: In function 'memscan':

/usr/include/asm/string.h:471: error: 'size' undeclared (first use in this funct ion)

/usr/include/asm/string.h:472: error: 'addr' undeclared (first use in this funct ion)

/usr/include/asm/string.h:478: error: 'c' undeclared (first use in this function )

/usr/include/asm/string.h:473: error: invalid lvalue in asm output 0

/usr/include/asm/string.h:473: error: invalid lvalue in asm output 1

In file included from kernel_lib.c:4:

/usr/include/linux/string.h: At top level:

/usr/include/linux/string.h:32: error: syntax error before 'strlcpy'

/usr/include/linux/string.h:32: error: syntax error before 'size_t'

/usr/include/linux/string.h:41: error: syntax error before 'strlcat'

In file included from kernel_lib.c:5:

/usr/include/linux/kernel.h:72: error: syntax error before 'size_t'

/usr/include/linux/kernel.h:74: error: syntax error before 'size_t'

In file included from /usr/include/asm/thread_info.h:13,

from /usr/include/linux/thread_info.h:21,

from /usr/include/linux/spinlock.h:19,

from /usr/include/linux/mmzone.h:8,

from /usr/include/linux/gfp.h:4,

from /usr/include/linux/slab.h:15,

from kernel_lib.c:6:

/usr/include/asm/processor.h:86: error: array type has incomplete element type

In file included from /usr/include/linux/gfp.h:4,

from /usr/include/linux/slab.h:15,

from kernel_lib.c:6:

/usr/include/linux/mmzone.h:286: error: syntax error before 'size_t'

In file included from /usr/include/asm/smp.h:18,

from /usr/include/linux/smp.h:17,

from /usr/include/linux/topology.h:33,

from /usr/include/linux/mmzone.h:296,

from /usr/include/linux/gfp.h:4,

from /usr/include/linux/slab.h:15,

from kernel_lib.c:6:

/usr/include/asm/mpspec.h:6:25: error: mach_mpspec.h: Aucun fichier ou répertoir e de ce type

In file included from /usr/include/asm/smp.h:18,

from /usr/include/linux/smp.h:17,

from /usr/include/linux/topology.h:33,

from /usr/include/linux/mmzone.h:296,

from /usr/include/linux/gfp.h:4,

from /usr/include/linux/slab.h:15,

from kernel_lib.c:6:

/usr/include/asm/mpspec.h:8: error: 'MAX_MP_BUSSES' undeclared here (not in a fu nction)

/usr/include/asm/mpspec.h:19: error: 'MAX_APICS' undeclared here (not in a funct ion)

/usr/include/asm/mpspec.h:22: error: 'MAX_IRQ_SOURCES' undeclared here (not in a function)

In file included from /usr/include/linux/smp.h:17,

from /usr/include/linux/topology.h:33,

from /usr/include/linux/mmzone.h:296,

from /usr/include/linux/gfp.h:4,

from /usr/include/linux/slab.h:15,

from kernel_lib.c:6:

/usr/include/asm/smp.h:73:26: error: mach_apicdef.h: Aucun fichier ou répertoire de ce type

In file included from /usr/include/linux/topology.h:33,

from /usr/include/linux/mmzone.h:296,

from /usr/include/linux/gfp.h:4,

from /usr/include/linux/slab.h:15,

from kernel_lib.c:6:

/usr/include/linux/smp.h:33: error: conflicting types for 'smp_send_reschedule'

/usr/include/asm/smp.h:41: error: previous declaration of 'smp_send_reschedule' was here

In file included from kernel_lib.c:6:

/usr/include/linux/slab.h:58: error: syntax error before 'int'

/usr/include/linux/slab.h:59: error: syntax error before 'size_t'

/usr/include/linux/slab.h:60: error: 'kmem_cache_create' declared as function re turning a function

/usr/include/linux/slab.h:61: error: syntax error before 'void'

/usr/include/linux/slab.h:70: error: syntax error before 'size_t'

/usr/include/linux/slab.h:73: error: syntax error before '}' token

/usr/include/linux/slab.h:74: error: array type has incomplete element type

/usr/include/linux/slab.h:75: error: syntax error before 'int'

/usr/include/linux/slab.h:77: error: syntax error before 'size'

/usr/include/linux/slab.h: In function 'kmalloc':

/usr/include/linux/slab.h:79: error: 'size' undeclared (first use in this functi on)

In file included from kernel_lib.c:6:

/usr/include/linux/slab.h:93: error: 'flags' undeclared (first use in this funct ion)

make[2]: *** [kernel_lib.o] Erreur 1

make[1]: *** [mm/kernel_badmemlib.o] Erreur 2

make: *** [mm] Erreur 2

debian:/home/tony/src/linux#

 

Bon badmem est mal installé ?

le Kernel est patché, mais est ce que je dois installer un utilitaire badmem avant de compiler le kernel ?

Lien vers le commentaire
Partager sur d’autres sites

1) Oui, il faut impérativement avoir installé les badmem-utils et créé le fichier de config /etc/badmem.conf avant de compiler son noyau patché

 

2) Pourquoi passer par un make-kpkg pour compiler un noyau ? Juste pour le plaisir d'en faire un package Debian qui ira copier bzImage et System.map au bon endroit ? Un noyau, ça se fait avec make menuconfig && make bzImage && make modules_install ...

Lien vers le commentaire
Partager sur d’autres sites

bon, l' installation de badmem-utils a déjà été faite, puis refaite.......

 

debian:/usr/src/badmem# ./configure

checking for gcc... gcc

checking for C compiler default output file name... a.out

checking whether the C compiler works... yes

checking whether we are cross compiling... no

checking for suffix of executables...

checking for suffix of object files... o

checking whether we are using the GNU C compiler... yes

checking whether gcc accepts -g... yes

checking for gcc option to accept ANSI C... none needed

checking for a BSD-compatible install... /usr/bin/install -c

checking whether ln -s works... yes

checking whether make sets $(MAKE)... yes

checking for log in -lm... yes

checking how to run the C preprocessor... gcc -E

checking for egrep... grep -E

checking for ANSI C header files... yes

checking for sys/types.h... yes

checking for sys/stat.h... yes

checking for stdlib.h... yes

checking for string.h... yes

checking for memory.h... yes

checking for strings.h... yes

checking for inttypes.h... yes

checking for stdint.h... yes

checking for unistd.h... yes

checking for unistd.h... (cached) yes

checking for an ANSI C-conforming const... yes

checking for ANSI C header files... (cached) yes

configure: creating ./config.status

config.status: creating howto/en/Makefile

config.status: creating mdfprint/Makefile

config.status: creating badmemshift/Makefile

config.status: creating badmemmerge/Makefile

config.status: creating badmemcmp/Makefile

config.status: creating badmemtype/Makefile

config.status: creating howto/jp/Makefile

config.status: creating badmemlib/Makefile

config.status: creating howto/Makefile

config.status: creating Makefile

config.status: creating mdfspec/Makefile

config.status: creating testsuite/Makefile

debian:/usr/src/badmem# make

make -C badmemlib all install;

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemlib'

make[1]: Rien à faire pour « all ».

/usr/bin/install -c -m 0755 libbadmem.so.1 /usr/local/lib/libbadmem.so.1

/usr/bin/install -c -m 0644 libbadmem.a /usr/local/lib/libbadmem.a

cd /usr/local/lib; ln -s -f libbadmem.so.1 libbadmem.so

if [ -x /sbin/ldconfig ]; then /sbin/ldconfig; fi

install -m 0644 include/badmemlib.h /usr/local/include/badmemlib.h;

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemlib'

make -C badmemcmp all install; make -C badmemmerge all install; make -C badmemtype all install; make -C badmemshift all install; make -C mdfprint all install;

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemcmp'

make[1]: Rien à faire pour « all ».

/usr/bin/install -c badmemcmp /usr/local/bin/badmemcmp

/usr/bin/install -c badmemcmp-static /usr/local/bin/badmemcmp-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemcmp'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemmerge'

make[1]: Rien à faire pour « all ».

/usr/bin/install -c badmemmerge /usr/local/bin/badmemmerge

/usr/bin/install -c badmemmerge-static /usr/local/bin/badmemmerge-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemmerge'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemtype'

make[1]: Rien à faire pour « all ».

/usr/bin/install -c badmemtype /usr/local/bin/badmemtype

/usr/bin/install -c badmemtype-static /usr/local/bin/badmemtype-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemtype'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemshift'

make[1]: Rien à faire pour « all ».

/usr/bin/install -c -m 0755 badmemshift /usr/local/bin/badmemshift

/usr/bin/install -c -m 0755 badmemshift-static /usr/local/bin/badmemshift-staticmake[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemshift'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/mdfprint'

make[1]: Rien à faire pour « all ».

/usr/bin/install -c -m 0755 mdfprint /usr/local/bin/mdfprint

/usr/bin/install -c -m 0755 mdfprint-static /usr/local/bin/mdfprint-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/mdfprint'

debian:/usr/src/badmem# make install

make -C badmemlib install;

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemlib'

/usr/bin/install -c -m 0755 libbadmem.so.1 /usr/local/lib/libbadmem.so.1

/usr/bin/install -c -m 0644 libbadmem.a /usr/local/lib/libbadmem.a

cd /usr/local/lib; ln -s -f libbadmem.so.1 libbadmem.so

if [ -x /sbin/ldconfig ]; then /sbin/ldconfig; fi

install -m 0644 include/badmemlib.h /usr/local/include/badmemlib.h;

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemlib'

make -C badmemcmp install; make -C badmemmerge install; make -C badmemtype install; make -C badmemshift install; make -C mdfprint install;

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemcmp'

/usr/bin/install -c badmemcmp /usr/local/bin/badmemcmp

/usr/bin/install -c badmemcmp-static /usr/local/bin/badmemcmp-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemcmp'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemmerge'

/usr/bin/install -c badmemmerge /usr/local/bin/badmemmerge

/usr/bin/install -c badmemmerge-static /usr/local/bin/badmemmerge-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemmerge'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemtype'

/usr/bin/install -c badmemtype /usr/local/bin/badmemtype

/usr/bin/install -c badmemtype-static /usr/local/bin/badmemtype-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemtype'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/badmemshift'

/usr/bin/install -c -m 0755 badmemshift /usr/local/bin/badmemshift

/usr/bin/install -c -m 0755 badmemshift-static /usr/local/bin/badmemshift-staticmake[1]: Leaving directory `/usr/src/badmem-utils-v1.7/badmemshift'

make[1]: Entering directory `/usr/src/badmem-utils-v1.7/mdfprint'

/usr/bin/install -c -m 0755 mdfprint /usr/local/bin/mdfprint

/usr/bin/install -c -m 0755 mdfprint-static /usr/local/bin/mdfprint-static

make[1]: Leaving directory `/usr/src/badmem-utils-v1.7/mdfprint'

debian:/usr/src/badmem#

 

l' installation c' est bien passé ?

Je suppose que OUI puisque j' ai plein de noms qui s' affichent quand je tape bad puis Tabulation

# bad

badblocks badmemmerge badmemshift-static

badmemcmp badmemmerge-static badmemtype

badmemcmp-static badmemshift badmemtype-static

 

 

Mais sinon, le fichier /etc/badmen.conf n' as pas été créé

il existe un modèle pour configurer /etc/badmem.conf ?

badram=0x20f00004,0xe0f00004,0x22000004,0xe2000004,0x38000004,0xff80004,0x3c400004,0xfec00004,0x3c000004,0xffc00004,0x33800004,0xfa800004,0x31000004,0xf3000004,0x30000004,0xfb000004,0x28000004,0xfa000004,0x24000004,0xfe000004

est ce suffisant comme texte dans le .conf ?

 

Sinon, j' ai copier les lib de /usr/local/lib vers /usr/lib

cp /usr/local/lib/

libbadmem.so libbadmem.a libbadmem.so.1

 

le make ne passe toujours pas ....

make[2]: *** [kernel_lib.o] Erreur 1

make[1]: *** [mm/kernel_badmemlib.o] Erreur 2

make: *** [mm] Erreur 2

 

Mais rien a faire.....pppfffff

Modifié par tourangeaux
Lien vers le commentaire
Partager sur d’autres sites

il existe un modèle pour configurer /etc/badmem.conf ?

 

 

tu as regardé dans le .diff du patch kernel?

 

si ce n'est pas dans le répertoire documentation des sources noyaux, en général c'est dans le diff

Lien vers le commentaire
Partager sur d’autres sites

Tiens, un modèle de badmem.conf inspiré de la doc de BadMem :

# /etc/badmem.conf
#
#
# This file contains all information about your BadMEM modules.
# It is needed at kernel compile time.
# Only change this file, if you have read the documentation of BadMEM!

module un
size 512
base 0

module deux
size 512
base 512
0x10002ac4,0x1000ffff

Et il suffit d'ajouter "badmem=un,deux" aux paramètres du kernel lors du boot. Jette un oeil dans /usr/src/badmem/howto/

En ce qui concerne ta librairie non trouvée lors du linkage, est-ce que tu as essayé d'ajouter /usr/local/lib à ton LD_LIBRARY_PATH ? Sinon, puisque tu as copié tes librairies dans un endroit plus "couru", est-ce que tu as bien exécuté ldconfig après avoir copié dans /usr/lib ?

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib

Lien vers le commentaire
Partager sur d’autres sites

il suffit d'ajouter "badmem=un,deux" aux paramètres du kernel lors du boot. Jette un oeil dans /usr/src/badmem/howto/

En ce qui concerne ta librairie non trouvée lors du linkage, est-ce que tu as essayé d'ajouter /usr/local/lib à ton LD_LIBRARY_PATH ? Sinon, puisque tu as copié tes librairies dans un endroit plus "couru", est-ce que tu as bien exécuté ldconfig après avoir copié dans /usr/lib ?

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib

 

 

voila mon /etc/badmem.conf modifié :

# /etc/badmem.conf
#
#
# This file contains all information about your BadMEM modules.
# It is needed at kernel compile time.
# Only change this file, if you have read the documentation of BadMEM!

module un
size 512
base 0

module deux
size 512
base 512
0x20f00004,0xe0f00004,0x22000004,0xe2000004,0x38000004,0xff80004,0x3c400004,0xfec00004,0x3c000004,0xffc00004,0x33800004,0xfa800004,0x31000004,0xf3000004,0x30000004,0xfb000004,0x28000004,0xfa000004,0x24000004,0xfe000004

 

sinon, j' ai refait un ldconfig ( Configuration de l'éditeur de liens dynamiques ) mais pourquoi doit on faire cette commande ?

 

le LD_LIBRARY_PATH ? j' ai toujours pas comprit a quoi ça sert......

 

et sinon, j' ai effectué ta commande en root sans trop réfléchir ( copier / coller )

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib

Peux tu m' expliquer le sens de cette commande , Merci

 

Je me demande si ma debian stable 3.1 est bien adapté se genre de choses.....si les noyau 2.6 sont bien adapté a se genre de patch .. où sinon je manque encore un peu d' expérience sous Linux...........

archlinux serait il plus simple ?

les wiki sur les kernel arch:

kernel beyond

kernel archck

compiler_noyau

kernel morph

kernel:config

Lien vers le commentaire
Partager sur d’autres sites

Tiens, après relecture du HOWTO livré avec les derniers badmem-utils, le contenu du fichier devrait être le suivant :

# /etc/badmem.conf
# Bla bla bla

module un
size=512m

module deux
size=512m
base=512m
0x20f00004,0xe0f00004,0x22000004,0xe2000004,0x38000004,0xff80004,0x3c400004,
0xfec00004,0x3c000004,0xffc00004,0x33800004,0xfa800004,0x31000004,0xf3000004,
0x30000004,0xfb000004,0x28000004,0xfa000004,0x24000004,0xfe000004

Avec les dernières adresses sur une seule ligne...

Lien vers le commentaire
Partager sur d’autres sites

Rejoindre la conversation

Vous publiez en tant qu’invité. Si vous avez un compte, connectez-vous maintenant pour publier avec votre compte.
Remarque : votre message nécessitera l’approbation d’un modérateur avant de pouvoir être visible.

Invité
Répondre à ce sujet…

×   Collé en tant que texte enrichi.   Coller en tant que texte brut à la place

  Seulement 75 émoticônes maximum sont autorisées.

×   Votre lien a été automatiquement intégré.   Afficher plutôt comme un lien

×   Votre contenu précédent a été rétabli.   Vider l’éditeur

×   Vous ne pouvez pas directement coller des images. Envoyez-les depuis votre ordinateur ou insérez-les depuis une URL.

 Partager

  • En ligne récemment   0 membre est en ligne

    • Aucun utilisateur enregistré regarde cette page.
×
×
  • Créer...