Wie anderen Kernel booten?

P

Pioneer

Aktives Mitglied
Thread Starter
Dabei seit
20.04.2004
Beiträge
156
Reaktionspunkte
0
Hi!

Ich habe auf meinem MacBook Debian Stable installiert und jetzt auf Testing upgegradet. Ging bis jetzt auch ohne Probleme, doch er bootet immer noch mit dem alten Kernel(2.6.18). Warum kann ich nicht in Lilo den anderen/neuen Kernel(2.16.24) booten, er bootet immer mit dem alten.

hanny@iVan:~$ uname -r
2.6.18-6-686
hanny@iVan:~$ ls /boot/
boot.0803 initrd.img-2.6.18-6-686 System.map-2.6.18-6-686
coffee.bmp initrd.img-2.6.18-6-686.bak System.map-2.6.24-1-686
config-2.6.18-6-686 initrd.img-2.6.24-1-686 vmlinuz-2.6.18-6-686
config-2.6.24-1-686 map vmlinuz-2.6.24-1-686
debian.bmp sarge.bmp
debianlilo.bmp sid.bmp

lilo.conf
# /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/sda3

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

# This option may be needed for some software RAID installs.
#
# raid-extra-boot=mbr-only

# 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=20

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


# 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

image=/vmlinuz
label=Linux
read-only
# restricted
# alias=1
append="noapic irqpoll acpi=force"
initrd=/initrd.img

image=/vmlinuz.old
label=LinuxOLD
read-only
optional
# restricted
# alias=2
append="noapic irqpoll acpi=force"
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/hda4
# label=HURD
# restricted
# alias=3
other=/dev/sda4
label=Windows
# restricted
# alias=2
 
wie du siehst steht default auf den Linux eintrag und der zeigt auf /vmlinuz und /initrd.img. die werden beides symlinks auf den kernel sein der gebootet wird...
also bieg die symlinks um, oder mach dir neue lilo einträge...
oder nimm grub ;)
der ist doch seit etch eh der default boot loader und nicht mehr lilo...
 
Ja das komische ist ja das ich gar nicht das boot Menü sehe, bzw. gar nicht zur Auswahl komme. Normal sollte ja auch Windows wählbar sein, ist es aber nicht.

Könnt das funktionieren + /sbin/lilo ?
image=/boot/vmlinuz-2.6.24-1-686
label=Linux-neu
read-only
# restricted
# alias=1
append="noapic irqpoll acpi=force"
initrd=/boot/initrd.img-2.6.24-1-686

Lilo ist mir sympathischer als Grub. ;)
 
Ah ok ins boot Menu komm ich jetzt, ich muss die Auswahlzeit höher Stellen. ;)
 
Sehr gut Problem gelöst. Ich habe einfach die lilo.conf geändert.

Danke noch für deine Mühe!
 
Zurück
Oben Unten