FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-19-2011, 08:38 PM
Cesare Leonardi
 
Default Bug#618958: linux-base: Boot loader configuration not recognized

Package: linux-base
Version: 3
Severity: minor

Today i've updated linux-base to version 3 and the following message
appeared:

---------------
The boot loader configuration for this system was not recognized. These
settings in the configuration may need to be updated:

* The root device ID passed as a kernel parameter;
* The boot device ID used to install and update the boot loader.

You should generally identify these devices by UUID or
label. However, on MIPS systems the root device must be
identified by name.
---------------

I think that the script is puzzled because in /etc/fstab and grub2
configuration i use "/dev/disk/by-uuid/" rather than the suggested
"UUID=" notation. I prefer it because i think it's cleaner, follows
the common UNIX /dev convention without requiring special support and
simply just works. And since then i've not seen any drawbacks in using
it.
I've took this suggestion some times ago from an openSuse machine.

Don't know why that notation provided directly by the kernel seems not
suggested nor supported directly.

Apart for the message, the system boots and loads well.

Cesare.


-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.37-2-686 (SMP w/1 CPU core)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-base depends on:
ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy
ii libuuid-perl 0.02-4 Perl extension for using UUID inte
ii udev 166-1 /dev/ and hotplug management daemo
ii util-linux 2.17.2-9.1 Miscellaneous system utilities

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
* linux-base/disk-id-manual-boot-loader:
linux-base/disk-id-update-failed:
* linux-base/disk-id-manual:
* linux-base/disk-id-convert-plan-no-relabel: true
* linux-base/disk-id-convert-auto: true
linux-base/do-bootloader-default-changed:
linux-base/disk-id-convert-plan: true



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110319213809.GA7509@tommaso">http://lists.debian.org/20110319213809.GA7509@tommaso
 
Old 03-19-2011, 08:57 PM
Ben Hutchings
 
Default Bug#618958: linux-base: Boot loader configuration not recognized

On Sat, 2011-03-19 at 22:38 +0100, Cesare Leonardi wrote:
> Package: linux-base
> Version: 3
> Severity: minor
>
> Today i've updated linux-base to version 3 and the following message
> appeared:
>
> ---------------
> The boot loader configuration for this system was not recognized. These
> settings in the configuration may need to be updated:
>
> * The root device ID passed as a kernel parameter;
> * The boot device ID used to install and update the boot loader.
>
> You should generally identify these devices by UUID or
> label. However, on MIPS systems the root device must be
> identified by name.
> ---------------
>
> I think that the script is puzzled because in /etc/fstab and grub2
> configuration i use "/dev/disk/by-uuid/" rather than the suggested
> "UUID=" notation.
[...]

No, that's not what this message means. It means that the script didn't
find any installed boot loader at all!

If you are using GRUB 2 then you should have the 'grub-common' package
and a file called '/etc/default/grub' installed. Is this not the case?

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 
Old 03-19-2011, 09:15 PM
Cesare Leonardi
 
Default Bug#618958: linux-base: Boot loader configuration not recognized

On 19/03/2011 22:57, Ben Hutchings wrote:

No, that's not what this message means. It means that the script didn't
find any installed boot loader at all!

If you are using GRUB 2 then you should have the 'grub-common' package
and a file called '/etc/default/grub' installed. Is this not the case?


Weird!
I've these packages installed:
grub 0.97-65
grub-common 1.99~rc1-4
grub-pc 1.99~rc1-4

And attached my /etc/default/grub.

I add that i wasn't able to make linux-base shows the message again:
tried with both dpkg-reconfigure and re-installing the package with
aptitude. To attach the message of the initial report i have copied and
pasted the text from linux-base.templates.


Cesare.
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="lapic hpet=force"
#GRUB_CMDLINE_LINUX_DEFAULT="lapic hpet=force i915.modeset=1"
#GRUB_CMDLINE_LINUX_DEFAULT="lapic hpet=force memory_corruption_check=1"
#GRUB_CMDLINE_LINUX_DEFAULT="lapic hpet=force memtest=2"
GRUB_CMDLINE_LINUX="quiet"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xe fefefef"

# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

# Cesare Leonardi 2010.
#GRUB_DISABLE_OS_PROBER=true
 
Old 03-19-2011, 10:39 PM
Jonathan Nieder
 
Default Bug#618958: linux-base: Boot loader configuration not recognized

Hi,

Ben Hutchings wrote:
> On Sat, 2011-03-19 at 22:38 +0100, Cesare Leonardi wrote:

>> The boot loader configuration for this system was not recognized. These
>> settings in the configuration may need to be updated:
[...]
> No, that's not what this message means. It means that the script didn't
> find any installed boot loader at all!
>
> If you are using GRUB 2 then you should have the 'grub-common' package
> and a file called '/etc/default/grub' installed. Is this not the case?

FWIW I ran into the same message today (on a machine tracking sid +
experimental that was last upgraded on 2011-01-31 before that).
I wish I had seen this report first so I could see what the state was
_before_ the upgrade; like Cesare, I am not able to trigger the
message again by running "dpkg-reconfigure linux-base".

The point being, here is another person willing to debug. Hints welcome.

Regards,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110319233903.GA9605@elie">http://lists.debian.org/20110319233903.GA9605@elie
 
Old 03-21-2011, 06:16 AM
Cesare Leonardi
 
Default Bug#618958: linux-base: Boot loader configuration not recognized

2011/3/19 Cesare Leonardi <celeonar@gmail.com>:
> ---------------
> The boot loader configuration for this system was not recognized. These
> settings in the configuration may need to be updated:
>
> * The root device ID passed as a kernel parameter;
> * The boot device ID used to install and update the boot loader.
>
> You should generally identify these devices by UUID or
> label. However, on MIPS systems the root device must be
> identified by name.
> ---------------

Same message on a Sid notebook i use at work and that i've updated this morning.
If that helps here is the relevant (IMHO) upgrades that happened on this pc:
firmware-linux-free 2.6.37 -> 3
grub 0.97-64 -> 0.97-65
grub-common 1.99~rc1-3 -> 1.99~rc1-4
grub-pc 1.99~rc1-3 -> 1.99~rc1-4
linux-base 3~experimental -> 3
linux-image-2.6-686 2.6.37-2 -> 2.6.38-1

The file /etc/default/grub is present and substantially identical to
the one already posted.

Ciao.

Cesare.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: AANLkTi=0-Q8ktAfqDL6nq+DN7_VX6=bg_TqYp8epGMxj@mail.gmail.com ">http://lists.debian.org/AANLkTi=0-Q8ktAfqDL6nq+DN7_VX6=bg_TqYp8epGMxj@mail.gmail.com
 
Old 03-22-2011, 02:40 AM
Ben Hutchings
 
Default Bug#618958: linux-base: Boot loader configuration not recognized

On Mon, 2011-03-21 at 08:16 +0100, Cesare Leonardi wrote:
> 2011/3/19 Cesare Leonardi <celeonar@gmail.com>:
> > ---------------
> > The boot loader configuration for this system was not recognized. These
> > settings in the configuration may need to be updated:
> >
> > * The root device ID passed as a kernel parameter;
> > * The boot device ID used to install and update the boot loader.
> >
> > You should generally identify these devices by UUID or
> > label. However, on MIPS systems the root device must be
> > identified by name.
> > ---------------
>
> Same message on a Sid notebook i use at work and that i've updated this morning.
> If that helps here is the relevant (IMHO) upgrades that happened on this pc:
> firmware-linux-free 2.6.37 -> 3
> grub 0.97-64 -> 0.97-65
> grub-common 1.99~rc1-3 -> 1.99~rc1-4
> grub-pc 1.99~rc1-3 -> 1.99~rc1-4
> linux-base 3~experimental -> 3
> linux-image-2.6-686 2.6.37-2 -> 2.6.38-1
[...]

If you upgraded all of these at the same time, maybe grub-common was in
the unpacked state (rather than installed) when linux-base checked it,
and that would explain this behaviour. There are some places where it
matters whether a package is fully installed, but in other places it
should treat a package in the unpacked state in the same way.

Ben.

--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
 

Thread Tools




All times are GMT. The time now is 04:34 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org