Léa-Linux & amis :   LinuxFR   GCU-Squad   GNU
le kernel 2.6.7 ne marche pas
Envoyé par: dung

J'ai suivi les instruction sur "[Lea] compiler noyau & modules" pour installer kernel 2.6.7, mais quand je redemarre et choisi le nv kernel a Lilo prompt je voie qu'un ecran noir. J'ai du redemarre et choisir old kernel.
Comment fais je pour resoudre ce probleme ?

Poste le Thursday 22 July 2004 10:33:08
Répondre     Citer    
Re: le kernel 2.6.7 ne marche pas
Envoyé par: dung


# /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', 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'. |
# | |
# +---------------------------------------------------------------+

# Support LBA for large hard disks.

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
# bios=0x81

# bios=0x80

# 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.

# Specifies the device that should be mounted as root. (`/')

# 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: bmp, compat, menu and text
# Look in /boot/ and in lilo.conf(5) manpage for details

# Specifies the location of the map file

# 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.

# 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
# single-key
# delay=100

# Kernel command line options that apply to all installed images go
# here. See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
# append=""
append="hda=scsi hdb=scsi hdc=scsi hdd=scsi hde=scsi hdf=scsi hdg=scsi hdh=scsi apm=power-off nomce"

# Boot up Linux by default.


# restricted
# alias=1

# optional
# restricted
# alias=2

# 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/hda4
# label=HURD
# restricted
# alias=3

Poste le Thursday 22 July 2004 10:37:28
Répondre     Citer    
Re: le kernel 2.6.7 ne marche pas
Envoyé par: willow75

ton fichier lilo a l'air bon

le pb doit venir de la compilation du noyau (pb d'option) ou pb de lien

si tu n'y arrive pas essaye la méthode debian décrite ci-dessous


ou install un noyau avec apt-get install "nomdupaquetnoyau"

(pour trouver tous les noyau packagé dispo : apt-cache search kernel)

Poste le Thursday 22 July 2004 11:02:25
Répondre     Citer    
Re: le kernel 2.6.7 ne marche pas
Envoyé par: dung

C'est vrai , je pense aussi que c'est 1 pb d'option, est-ce que quelqu'un peut me passer le fichier config pour kernel 2.6.7 ?

Poste le Thursday 22 July 2004 16:40:00
Répondre     Citer    
Re: le kernel 2.6.7 ne marche pas
Envoyé par: willow75

la configuration du kernel dépend de ton matériel

renseigne toi sur les différentes option du noyau ( www.google/linux )

Poste le Thursday 22 July 2004 17:14:07
Répondre     Citer    
Re: le kernel 2.6.7 ne marche pas
Envoyé par: berti2

y'a un fichier de config relativement standard dans [people.via.ecp.fr]

Poste le Wednesday 28 July 2004 22:21:44
Répondre     Citer    
Re: le kernel 2.6.7 ne marche pas
Envoyé par: elyes

dans ta config tu as utiliser le fb
en effect si par example tu tape a l'aveugle (sur ton ecran noir) ton log pui ton password apres dmesg > /home/moi/essai.txt
et tu reboot sur ton old tu verra ton fichier essai.txt
ce qu'il faut faire c de revoir ta config et recompiler ton noyeau sad smiley

Poste le Thursday 29 July 2004 09:28:31
Répondre     Citer    

Veuillez vous authentifier auparavant pour commenter.


Ce forum !
le kernel 2.6.7 ne marche pas
Aide sur les distributions Debian, Ubuntu et leurs dérivées : Mepis, Mint, Knoppix, Kubuntu, Lubuntu, Xandros

Sauf mention contraire, les documentations publiées sont sous licence Creative-Commons