linux user group brescia

immagine del castello

Archivio della mailing list

[LugBS] Ubuntu - problema audio

Diego Monselice info a diegomonselice.it
Gio 25 Feb 2010 13:23:52 UTC
~$ sudo lilo -t -v
LILO version 22.8 (test mode), Copyright (C) 1992-1998 Werner
Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007, and compiled at 10:52:38 on Aug 25 2009
Ubuntu

Warning: LBA32 addressing assumed
Reading boot sector from /dev/sda
Using MENU secondary loader
Calling map_insert_data

Boot image: /vmlinuz -> boot/vmlinuz-2.6.31-20-generic
Mapping RAM disk /initrd.img -> boot/initrd.img-2.6.31-20-generic
Added Linux *

Boot image: /vmlinuz.old -> boot/vmlinuz-2.6.31-19-generic
Mapping RAM disk /initrd.img.old -> boot/initrd.img-2.6.31-19-generic
Added LinuxOLD

Boot other: /dev/sda1, on /dev/sda, loader CHAIN
Added Windows

The boot sector and the map file have *NOT* been altered.
One warning was issued.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ecco il file /etc/lilo.conf:

# Automatically added by lilo postinst script
large-memory

# /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/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 Ubuntu, 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="root=/dev/sda3  "
	initrd=/initrd.img

image=/vmlinuz.old
	label=LinuxOLD
	read-only
	optional
#	restricted
#	alias=2
	append="root=/dev/sda3  "
	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/sda1
	label=Windows
#	restricted
#	alias=2





Il giorno gio, 25/02/2010 alle 12.21 +0100, Andrea Gelmini ha scritto:
> Il 24 febbraio 2010 23.53, Diego Monselice <info a diegomonselice.it> ha scritto:
> > GRUB non c'è sul mio Sistema... ha dato problemi in fase di
> > installazione, tant'è che m'ha installato LILO per fare il boot...
> >
> > quindi il problema è che non usa il kernel aggiornato ma quello vecchio?
> >
> > Come risolverlo con Lilo? o altrimenti, come installare GRUB?
> 
> Buffo. E' vero che Lilo puo' affrontare casi per i quali Grub 2 non è
> ancora maturo.
> Allora, per vedere di aggiornare la configurazione di Lilo (che è
> molto delicata, sbagliadola potresti trovarti senza il sistema in
> grado di partire), cominciamo a vedere cosa ti propone, scrivendo:
> 
> sudo lilo -t -v
> 
> In questo modo ti verra' mostraro cosa Lilo andra' a fare, ma non lo
> fara'. Sicchè ci fossero errori o problemi, non rovineremmo tutto.
> 
> Manda questo che poi vediamo.
> 
> E' una vita che non lo uso, ma mi pare fosse premendo tab che si
> poteva decidere all'avvio quale profilo far partire.
> 
> Ad ogni modo, manda anche il contenuto di /etc/lilo.conf che vediamo.
> 
> Ciao,
> gelma
> 


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~
Diego Monselice
-----------------------
www.diegomonselice.it
info a diegomonselice.it
TIM:       (+39) 339 25 68 172
Vodafone:  (+39) 347 99 39 028
~~~~~~~~~~~~~~~~~~~~~~~~~




Maggiori informazioni sulla lista Lug