Forum |  HardWare.fr | News | Articles | PC | S'identifier | S'inscrire | Shop Recherche
1692 connectés 

  FORUM HardWare.fr
  Linux et OS Alternatifs
  Installation

  [Help] compil de kernel qui foire (debian Sid)...

 


 Mot :   Pseudo :  
 
Bas de page
Auteur Sujet :

[Help] compil de kernel qui foire (debian Sid)...

n°578275
impulse
Posté le 22-10-2004 à 22:23:27  profilanswer
 

En fait c'est pas la compil qui foire mais la suite. Voila ce que j'ai fait (en gros)  :  
 
- installation Debian (net install avec le CD de 10 Mo) avec kernel 2.4.x
- passage en Sid pendant la procedure d'installation
- installation de Gnome
 
Tout fonctionnait parfaitement... jusqu'a ce que j'aie la bonne idée de changer de kernel... J'ai configuré le noyau puis ensuite j'ai utilisé la "methode Debian" pour le compiler et l'installer. Voici ce que ça me donne à la fin :
 

Citation :


You already have a LILO configuration in /etc/lilo.conf
Install a boot block using the existing /etc/lilo.conf? [Yes]
Testing lilo.conf ...
An error occurred while running lilo in test mode, a log is
available in /var/log/lilo_log.15733. Please edit /etc/lilo.conf
manually and re-run lilo, or make other arrangements to boot
your machine.
         Please hit return to continue
 
# cat /var/log/lilo_log.15733
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda'
Fatal: open /initrd.img: No such file or directory


 
et un petit lilo -v :
 

Citation :


LILO version 22.6, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 02-Sep-2004, and compiled at 19:13:54 on Sep 13 2004
Debian GNU/Linux
 
Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/ide/host0/bus0/target0/lun0/disc' -> '/dev/hda'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part1' -> '/dev/hda1'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part3' -> '/dev/hda3'
    Name change: '/dev/ide/host0/bus0/target0/lun0/part5' -> '/dev/hda5'
    Name change: '/dev/scsi/host0/bus0/target6/lun0/disc' -> '/dev/sda'
    Name change: '/dev/scsi/host0/bus0/target6/lun0/part1' -> '/dev/sda1'
    Name change: '/dev/scsi/host0/bus0/target6/lun0/part2' -> '/dev/sda2'
    Name change: '/dev/scsi/host0/bus0/target6/lun0/part3' -> '/dev/sda3'
Using MENU secondary loader
Calling map_insert_data
 
Boot image: /vmlinuz -> boot/vmlinuz-2.6.8
Mapping RAM disk /initrd.img
Fatal: open /initrd.img: No such file or directory


 
Pourquoi j'ai pas de /initrd.img ???

mood
Publicité
Posté le 22-10-2004 à 22:23:27  profilanswer
 

n°578276
impulse
Posté le 22-10-2004 à 22:25:40  profilanswer
 

Mon lilo.conf (ça peut servir) :
 

Citation :


# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.
 
# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt' (if you have created it), or   |
# | install a new kernel.  The computer will most likely fail to  |
# | boot if a kernel-image post-install script or you don't       |
# | remember to run `lilo'.                                       |
# |                                                               |
# +---------------------------------------------------------------+
 
# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/sda
 
# Specifies the device that should be mounted as root. (`/')
#
root=/dev/sda2
 
# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact
 
# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu
 
# Specifies the location of the map file
#
map=/boot/map
 
# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000
 
# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=100
 
# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#       prompt
#       delay=100
#       timeout=100
 
# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode> )
#
# vga=ask
# vga=9
#
vga=normal
 
# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
 
# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=
 
#
# Boot up Linux by default.
#
default=Linux
timeout = 100
prompt
 
image=/vmlinuz
        label=Linux
        read-only
#       restricted
#       alias=1
 
        initrd=/initrd.img
 
image=/vmlinuz.old
        label=LinuxOLD
        read-only
        optional
#       restricted
#       alias=2
 
        initrd=/initrd.img.old
 
 
# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
 
other=/dev/sda1
        label=Windows
 

n°578505
chaos0007
Posté le 23-10-2004 à 15:58:46  profilanswer
 

es tu sur des liens /initrd.img et /vmlinuz ... est ce kils pointent bien au bon endroit ?


Message édité par chaos0007 le 23-10-2004 à 16:01:04
n°578594
impulse
Posté le 23-10-2004 à 17:45:00  profilanswer
 

J'ai tout viré. Je recompilerai mon noyau un autre jour. J'avais pas le temps de resoudre ce pb... :/


Aller à :
Ajouter une réponse
  FORUM HardWare.fr
  Linux et OS Alternatifs
  Installation

  [Help] compil de kernel qui foire (debian Sid)...

 

Sujets relatifs
[Debian] quel /dev/sd.. pour ma clé usb ?kernel panic au changement de version de kernel
Debian - Installation - Probleme avec MAKEequivalent apt debian sous autres distrib
ajout de disque - kernel panicProblèmes sur mandrake 10. Help !!
Imprimante HP sous DebianDebian & kernel-source
nouvel install debian + partition non montée 
Plus de sujets relatifs à : [Help] compil de kernel qui foire (debian Sid)...


Copyright © 1997-2022 Hardware.fr SARL (Signaler un contenu illicite / Données personnelles) / Groupe LDLC / Shop HFR