ajouter un module +cobalt cube

Marsh Posté le 01-11-2006 à 16:20:27

Salut a tous,

Voila j essaye d activer les quotas sur mon serveur cobalt cube mais apres pas mal de test j ai droit a un :

Citation :

quotaon: Cannot find quota file on /home [/dev/hda6] to turn quotas on/off.
quotaon: Cannot find quota file on /home [/dev/hda6] to turn quotas on/off.

il semblerait donc que le module ne soit pas compiler dans le noyaux...

uname -a :

Citation :

Linux cube 2.4.27-r5k-cobalt #1 Sun May 22 11:09:35 UTC 2005 mips GNU/Linux

Du coup j ai essayer de voir si un nouveau noyau etait dispo mais j ai rien trouver par apt-get sur les depositery(??) debian architecture MIPS, le noyau que j ai est le plus recent...
Sinon c est une sarge stable il me semble...
Le gros pb avec cette machine est que je ne peut y acceder que par ssh du coup il faut pas que je me plante!
Je viens de regarder y a meme pas de trace de grub...
Alors ma question est: Est il possible d ajouter le module quota sans avoir a recompiler le noyaux ?redemarrer la machine?
Quel est la procedure?

merci

Reply

Marsh Posté le 01-11-2006 à 16:20:27

Reply

Marsh Posté le 01-11-2006 à 16:37:58

Citation :

root@cubeboot 162# cat config-2.4.27-r5k-cobalt | grep QUOTA
# CONFIG_QUOTA is not set
# CONFIG_XFS_QUOTA is not set

Reply

Marsh Posté le 01-11-2006 à 18:04:53

Va falloir recompiler

Reply

Marsh Posté le 01-11-2006 à 18:23:12

faut recompiler juste pour installer un module?Il existe pas une technique consistant a juste recompiler le module en question puis de le rajouter au noyau?

Reply

Marsh Posté le 01-11-2006 à 20:47:21

Bah heuu ptetre mais jsais pas

Au passage tu peux passer en 2.6

http://www.colonel-panic.org/cobalt-mips/

PS: Complètement hors sujet, tu n'as pas de Cobalt à vendre ?

Reply

Marsh Posté le 01-11-2006 à 21:00:06

ahhh merci pour l info bon va falloir ce retrousser les manches...
Sinon dsl j en ai pas a vendre en tout cas c genial en lampe de chevet ce truc ...

Reply

Marsh Posté le 02-11-2006 à 23:19:10

Citation :

lcd.c:554: warning: initialization from incompatible pointer type
lcd.c:561: error: `LCD_MINOR' undeclared here (not in a function)
lcd.c:561: error: initializer element is not constant
lcd.c:561: error: (near initialization for `lcd_dev.minor')
make[4]: *** [lcd.o] Error 1
make[4]: Leaving directory `/usr/src/kernel-source-2.4.27/drivers/char
make[3]: *** [first_rule] Error 2
make[3]: Leaving directory `/usr/src/kernel-source-2.4.27/drivers/char
make[2]: *** [_subdir_char] Error 2
make[2]: Leaving directory `/usr/src/kernel-source-2.4.27/drivers'
make[1]: *** [_dir_drivers] Error 2
make[1]: Leaving directory `/usr/src/kernel-source-2.4.27'
make: *** [stamp-build] Error 2

bon j ai essayé de recompiler le noyau a partir des sources et du .config originel mais il me sort ca a la fin , j sais pas trop quoi faire ...
Le truc du lcd c est le petit ecran graphique qui balance quelques infos au boot c est ptet ca qui foire ...A moins qu il y ait un pb de compilo :??:
des idées ?

merci!

Reply

Marsh Posté le 03-11-2006 à 11:09:54

nouvelle erreur a la compil:

Citation :

make[1]: mips-linux-gcc: Command not found
make[1]: *** [init/main.o] Error 127
make[1]: Leaving directory `/usr/src/kernel-source-2.4.27'
make: *** [stamp-build] Error 2

j ai ca deja d'installer

Citation :

mipsel-linux-cpp mipsel-linux-g++ mipsel-linux-gcc
mipsel-linux-cpp-3.3 mipsel-linux-g++-3.3 mipsel-linux-gcc-3.3

Ca serait pas une petite erreur de nom de variable?Quelquechose a changer dans le makefile?
:hello:

Reply

Marsh Posté le 03-11-2006 à 14:11:03

Citation :

ld -m elf32btsmip -r -o kernel.o sched.o dma.o fork.o exec_domain.o panic.o printk.o module.o exit.o itimer.o info.o time.o softirq.o resource.o sysctl.o acct.o capability.o ptrace.o timer.o user.o signal.o sys.o kmod.o context.o ksyms.o
ld: sched.o: compiled for a little endian system and target is big endian
ld: sched.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file sched.o
ld: dma.o: compiled for a little endian system and target is big endian
ld: dma.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file dma.o
ld: fork.o: compiled for a little endian system and target is big endian
ld: fork.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file fork.o
ld: exec_domain.o: compiled for a little endian system and target is big endian
ld: exec_domain.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file exec_domain.o
ld: panic.o: compiled for a little endian system and target is big endian
ld: panic.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file panic.o
ld: printk.o: compiled for a little endian system and target is big endian
ld: printk.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file printk.o
ld: module.o: compiled for a little endian system and target is big endian
ld: module.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file module.o
ld: exit.o: compiled for a little endian system and target is big endian
ld: exit.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file exit.o
ld: itimer.o: compiled for a little endian system and target is big endian
ld: itimer.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file itimer.o
ld: info.o: compiled for a little endian system and target is big endian
ld: info.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file info.o
ld: time.o: compiled for a little endian system and target is big endian
ld: time.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file time.o
ld: softirq.o: compiled for a little endian system and target is big endian
ld: softirq.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file softirq.o
ld: resource.o: compiled for a little endian system and target is big endian
ld: resource.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file resource.o
ld: sysctl.o: compiled for a little endian system and target is big endian
ld: sysctl.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file sysctl.o
ld: acct.o: compiled for a little endian system and target is big endian
ld: acct.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file acct.o
ld: capability.o: compiled for a little endian system and target is big endian
ld: capability.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file capability.o
ld: ptrace.o: compiled for a little endian system and target is big endian
ld: ptrace.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file ptrace.o
ld: timer.o: compiled for a little endian system and target is big endian
ld: timer.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file timer.o
ld: user.o: compiled for a little endian system and target is big endian
ld: user.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file user.o
ld: signal.o: compiled for a little endian system and target is big endian
ld: signal.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file signal.o
ld: sys.o: compiled for a little endian system and target is big endian
ld: sys.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file sys.o
ld: kmod.o: compiled for a little endian system and target is big endian
ld: kmod.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file kmod.o
ld: context.o: compiled for a little endian system and target is big endian
ld: context.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file context.o
ld: ksyms.o: compiled for a little endian system and target is big endian
ld: ksyms.o: endianness incompatible with that of the selected emulation
ld: failed to merge target specific data of file ksyms.o
make[3]: *** [kernel.o] Error 1
make[3]: Leaving directory `/usr/src/kernel-source-2.4.27/kernel'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/kernel-source-2.4.27/kernel'
make[1]: *** [_dir_kernel] Error 2
make[1]: Leaving directory `/usr/src/kernel-source-2.4.27'
make: *** [stamp-build] Error 2

c est un peu galere la :pt1cable:

Citation :

system type : Cobalt Qube2
processor : 0
cpu model : Nevada V10.0 FPU V10.0
BogoMIPS : 249.03
byteorder : little endian
wait instruction : yes
microsecond timers : yes
tlb_entries : 48
extra interrupt vector : yes
hardware watchpoint : no
VCED exceptions : not available
VCEI exceptions : not available

Cest un peu compliqué pour moi la , je capte pas trop je pense qu il veut des petits indiens or il en recoit que des gros , c est une option du noyaux ca?Je continue mes recherches

P.S pour mon pb precedent il fallait desactiver CONFIG_CROSSCOMPILE dans le noyaux...
Sinon le truc que je comprends pas c est que j ai repris le .config de mon noyau qui marche tres bien mais si on le recompile ya plein de bug partout, ca vient plus des outils qu il y a autour? ou d un truc que j ai pas compris ( c est fort possible :sweat: )

Message édité par krifur le 03-11-2006 à 14:55:26

Reply

Marsh Posté le 03-11-2006 à 15:12:23

pourquoi tu compile pas ca normalement directement sur le qube ?

Reply

Marsh Posté le 03-11-2006 à 15:12:23

Reply

Marsh Posté le 17-11-2006 à 14:41:03

Re!
Bon ca yest tout marche a peu près, merci de ton aide...
Sinon j'aimerai bien essayer d'installer un 2.6 mais ya pas moyen que je le fasse directement sur le cube avec mes 249 de bogomips ca m'a pris 5 heures je crois ...
Donc est ce que tu connais des liens pour cross-compiler du mipsel sur du i686?
J'ai trouvé ca qu a l'air pas mal http://docmirror.net/fr/linux/howt [...] WTO-9.html
mais je prefere avoir plusieurs source (ou ta technique si tu le fait toi aussi?)
Ah oui et sinon j arrive pas a avoir un menu au boot du cobalt histoire de selectionner le noyaux je me suis planter plusieurs fois dans la config du menu.colo, du coup obliger de faire des net booting en port serie arggg
voila mon menu.colo qui me colle un BOOT UNIT FAIL ou kkchose comme ca:

Citation :

#:CoLo:# $Id: menu.colo 120 2004-10-18 16:35:05Z pdh $
#
# extend boot menu with kernel selection
#

var _image vmlinux-2.4.27-r5k-cobalt

# pass kernel console argument only if console's enabled
var _console ''
-var _console console=ttyS0,{console-speed}

# if boot menu wasn't used go load default kernel
-noop {menu-option}
onfail 1f

# show user list of kernels
select 'BOOT KERNEL' 100 2.4.x 2.6.x-32 2.6.x-64
goto {menu-option}

# default option (timeout or cancel)

# first option
@lcd 'Loading ...' {_image}
mount hda1
cd /boot
load {_image}
execute root=/dev/hda2 {_console}
abort

# second option correspond a mon nouveau noyau
@var _image vmlinux-new
goto 2b

# third option
@var _image vmlinux-2.6.8.1-64
goto 3b

Reply

ajouter un module +cobalt cube

Sujets relatifs:

Leave a Replay