Testsuite summary for GRUB 2.06
# TOTAL: 82
# PASS: 21
# SKIP: 13
# XFAIL: 0
# FAIL: 48
# XPASS: 0
# ERROR: 0
01.04.2016 08:14, Ron пишет:
>
> Greetings,
>
> grub.cfg supports 3 colour options:
>
> set menu_color_normal
> set menu_color_highlight
> set color_normal
>
There is also color_highlight
>
> However, /etc/default/grub only supports 2:
>
> GRUB_COLOR_NORMAL
> GRUB_COLOR_HIGHLIGHT
>
>
>
Greetings,
grub.cfg supports 3 colour options:
set menu_color_normal
set menu_color_highlight
set color_normal
However, /etc/default/grub only supports 2:
GRUB_COLOR_NORMAL
GRUB_COLOR_HIGHLIGHT
I'd like to propose that grub supports the 3rd "set" option, and
further, that it be named
; http://www.arados.de/
>
> Ust.-ID-Nr.: DE131832904
> HR Amtsgericht Amberg HRB1060
> Geschäftsführer Gerhard Egelseer
>
>
> ___
> Bug-grub mailing list
> Bug-grub@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-grub
>
___
Bug-grub mailing list
Bug-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-grub
/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v
/boot/grub
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: changing current directory to cpu.
/usr/sbin/grub-probe: info: changing current directory to shm.
/usr/sbin/grub-probe:
Dear Ubuntu experts,
Could you help me with a failure on the installation of the latest version
of Ubuntu (10.10)?
After installing it, I keep receiving the following message after booting:
unknown filesystem
grub rescue
I had a previous installation of Windows XP and performed the advanced
On 08/02/2010 07:28 PM, Stati Ion wrote:
Hi, my name is John and i have a problem :) (tipical bug mail)
Sory but i speek englis very bad.. I have a problem with Grub after
installation and _updating _Ubuntu 10.04 on a computer where is
instaled a Microsoft Windows 7 and Ubuntu is a secondary
Hi, my name is John and i have a problem :) (tipical bug mail)
Sory but i speek englis very bad.. I have a problem with Grub after
installation and _updating _Ubuntu 10.04 on a computer where is instaled
a Microsoft Windows 7 and Ubuntu is a secondary os. Exactly this problem
i have with
Hi. I was trying to fix a bug in my grub and I found this mail to report it.
Well, will you help me guys?
what happens is the following. after turning on the computer (and you can
notice by my language that I am not a geek, so... I am having a hard time here)
sometimes nothing happens, onli a
On 3/26/07, Leon Lynch [EMAIL PROTECTED] wrote:
Hi all,
According to the following, Grub loads the Linux initrd at an address
that is too high for the Linux kernel to access when the 'vmalloc=' boot
parameter is set greater than 128M:
Grub bug #12271
http://lkml.org/lkml/2005/4/4/283
Hi all,
According to the following, Grub loads the Linux initrd at an address
that is too high for the Linux kernel to access when the 'vmalloc=' boot
parameter is set greater than 128M:
Grub bug #12271
http://lkml.org/lkml/2005/4/4/283
This appears to still be the case on Grub-0.97
I can't figure this out, and my desperation has me pulling my hair out. I
really would like to get this up and running. Please help!
All information and steps taken are in this thread:
http://www.linuxquestions.org/questions/showthread.php?t=405642
Regards,
tami
Hi, I can't seem to get grub 0.93 to read
some of my partitions (that can be mounted
by linux fine whether normally from a disk,
or loopback from a file). Note the grub shell
within linux and the native grub show the
same problem.
It used to work when I had just 2 primary
partitions, but I think
mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.topic.com.au/cgi-bin/mailman/listinfo/bug-grub
--
Jason Thomas Phone: +61 2 6257 7111
System
This is fixed in CVS and debian.
On Wed, Nov 06, 2002 at 06:23:08PM -0500, [EMAIL PROTECTED] wrote:
Booting with Grub worked fine on the nForce based MSI K7N420pro with Bios Versions
2.0, 2.1, 2.2, 2.3 and 2.4, but stopped working with 2.5 and upwards. Asus nForce
boards seem to have had this
On Tue, Jun 04, 2002 at 05:39:27PM -0400, [EMAIL PROTECTED] wrote:
Yes my BIOS supports USB keyboards ! And i've checked everything in the bios (it's a
pretty cool one) and everything seems to be ok...
Perhaps USB support isn't simply implemented in grub ??
exactly, thats why we are asking
This may be a needed feature. That Grub search all hardrives for
additional Linux installations and provide booting options for them.
--
Det. Leonzo E. Miller
Palm Beach County Sherrif's Office Truancy Interdiction Center
Delray Beach, Florida
Voice: (561) 274-1053 FAX: (561) 274-1054
:
Which did you execute those commands in the native environment or in
the grub shell? Is there any difference between them?
Okuji
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
With the CVS version, you can now specify
`--disable-auto-linux-mem-opt' to the configure script.
Okuji
___
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
From: Jeff Garzik [EMAIL PROTECTED]
Subject: Re: ack! grub bug...
Date: Thu, 22 Feb 2001 19:29:04 -0500
Because at that point, we are working around a grub-specific problem in
the kernel, which is caused by grub working around a now-resolved kernel
problem! :) It's a workaround
From: Jeff Garzik [EMAIL PROTECTED]
Subject: Re: ack! grub bug...
Date: Fri, 23 Feb 2001 10:02:39 -0500
This will solve the problem... for problematic machines. However, it is
merely a bandaid... policy is that mem=XX is an -override- parameter, to
be used only when necessary. IMHO we
OKUJI Yoshinori wrote:
As for now, I think MandrakeSoft will make a vendor patch that defaults
to --no-mem-option, since we can control our kernel versions a bit
more...
Because I don't like that there are so many variants of GRUB, what do
you think about that we add a configure option
Hello,
as I already described before, my prefered solution to the problem
is the use of a kind of variables in GRUB like
$MEM, $IP, $SERVER_IP, etc, etc,...
So the user can decide himeself using kernel paramters, like
kernel /boot/vmlinuz mem=$MEM root=/dev/hda2
etc If
Hello, Christoph!
as I already described before, my prefered solution to the problem
is the use of a kind of variables in GRUB like
$MEM, $IP, $SERVER_IP, etc, etc,...
I was unaware of your proposal. It's an excelent idea, much better than my
"--mem-option".
Regards,
Pavel Roskin
From: Christoph Plattner [EMAIL PROTECTED]
Subject: Re: [Jeff Garzik [EMAIL PROTECTED]] Re: ack! grub bug...
Date: Thu, 22 Feb 2001 09:16:16 +0100
So the user can decide himeself using kernel paramters, like
kernel /boot/vmlinuz mem=$MEM root=/dev/hda2
etc If there is enough
OKUJI Yoshinori wrote:
From: Pavel Roskin [EMAIL PROTECTED]
Subject: Re: ack! grub bug...
Date: Thu, 22 Feb 2001 10:06:01 -0500 (EST)
I believe that "--no-mem-option" should become default. "--mem-option"
should be introduced instead for the kernels that still
On Wed, 21 Feb 2001, Pavel Roskin wrote:
grub -always- passes the "mem=XXX" command line option to the kernel.
it's always been that way...
It works around a kernel bug. That is wrong in and of itself.
A kernel bug fix belongs in the kernel, not in grub.
I remember a
From: Pixel [EMAIL PROTECTED]
Subject: [Jeff Garzik [EMAIL PROTECTED]] Re: ack! grub bug...
Date: Wed, 21 Feb 2001 23:40:39 +0100 (CET)
It works around a kernel bug. That is wrong in and of itself.
A kernel bug fix belongs in the kernel, not in grub.
You're just talking about an utopia
: MandrakeSoft Internal [EMAIL PROTECTED]
Subject: Re: ack! grub bug...
In-Reply-To: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Lines: 43
Xref: leia.mandrakesoft.com mail.mandrake:8147
On Wed, 21 Feb 2001, Pixel wrote:
Jeff Garzik
Try running `displaymem' from the `grub' prompt, and send the output.
It may be that 0.5.96.1 doesn't pass a correct `mem=' flag to linux.
--
Gordon Matzigkeit [EMAIL PROTECTED] //\ I'm a FIG (http://fig.org/)
Committed to diversity and freedom \// Go Figure (http://fig.org/figure/)
On Fri, 12 Jan 2001, OKUJI Yoshinori wrote:
You didn't tell us anything about your GRUB. Even though I've written
the same thing both in README and in the web page, many users seems
Not much to tell, I guess - it's the Debian packaged version of latest
released grub (0.5.96.1).
Please
I have been using Grub for some time with great success. However, I just
put together a new system based on an Asus A7V motherboard (which has an
on-board Promise ATA-100 disk controller), an ATA drive connected that
controller, an ATA CD-ROM (connected to the standard ATA-66 controller on
On Mon, 18 Sep 2000, OKUJI Yoshinori wrote:
Ok, how about this?
1. Check if stage1 and stage2 really exist before running the command
install in the command setup. If not, print which file is missing.
2. Add, say, --prefix=DIR into the command setup.
3. If the user doesn't specify the
On Sun, 17 Sep 2000, OKUJI Yoshinori wrote:
Why don't you read the doc? It is explicitly denoted that the
command setup is just a wrapper. Use the command install directly if
you want to specify file names. *sigh*
Sorry do you want to see the same error message without the wrapper
but the
Hi Andreas and GRUB maintainers,
| grub setup (hd0)
|
| Error: File not found
just in case you haven't figured out what's wrong, and assuming you
did everything the docs tell you to, grub is looking for
$(root)/boot/grub/{stage1,stage2}. It is possible that $(root) for
you is /boot,
From: Ian Morgan [EMAIL PROTECTED]
Subject: GRUB bug re: mem= for Linux
Date: Fri, 5 May 2000 01:32:10 -0400 (EDT)
The 2000-05-05 changes regarding the passing of the mem= argument to Linux
kernels are broken.
Sorry. For now, I have no test environment, so I didn't test it. I
think I've
The 2000-05-05 changes regarding the passing of the mem= argument to Linux
kernels are broken.
I just re-booted, and grub passed an argument telling the kernel that I had
only 1 MB of RAM. Needless to say, the kernel didn't even make it very far.
Manually passing mem=128M resolves the problem,
d $grubdir || mkdir $grubdir
earlier? It will also include any rootdir specified by the user.
OKUJI Yoshinori wrote:
From: Tim Riker [EMAIL PROTECTED]
Subject: Re: [grub] bug report
Date: Fri, 14 Apr 2000 19:13:19 -0600
I noticed this too and worked around it by setting:
rootdir=
I noticed this too and worked around it by setting:
rootdir=/boot/grub
which is where we have grub installed by default. This way if /boot is a
separate partition (possible) grub still seems to do the right thing.
-- Satoshi Nagayasu wrote:
In a previous mail, I forget to tell you how to
grub-install script contains probrem. I got latest version from cvs.
# grub-install /dev/hda
/dev/hda2
/dev/hda7
/dev/hda8
/dev/hda6
/dev/hda9
/dev/hda1: Not found.
#
At first, variable $rootdir is empty like below.
32:grub_shell=${sbindir}/grub
33:log_file=/tmp/grub-install.log.$$
Thanks for your report. Unfortunately, the script hasn't been tested
enough, because most of GRUB experts install GRUB by hand. I'll
investigate the problem soon.
Okuji
In a previous mail, I forget to tell you how to solve this problem.
Modify line 34,
34: rootdir=
as below
34: rootdir=/
It makes grub-install script working correctly.
OKUJI Yoshinori wrote:
Thanks for your report. Unfortunately, the script hasn't been tested
enough, because most of GRUB
42 matches
Mail list logo
