Hi.
Distro: Debian 12
uname -a
Linux tm 5.10.0-26-amd64 #1 SMP Debian 5.10.197-1 (2023-09-29) x86_64
GNU/Linux
Best regards.
=
GRUB 2.12: ./test-suite.log
=
# TOTAL: 86
# PASS: 26
# SKIP: 2
# XFAIL: 0
# FAIL: 51
# XPASS: 0
#
<<< text/html; charset=UTF-8: Unrecognized >>>
===
GRUB 2.06-3~deb11u5: ./test-suite.log
===
# TOTAL: 82
# PASS: 64
# SKIP: 17
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
SKIP:
Hello grub@gnu and thanks for your little bit of magic. I have a problem.
I hope the screenshots attached will answer many of your questions, but as
background:
+ Linus Mint 20.3 (Cinnamon) on a Lenovo T480, installed on the onboard SSD
running LUKS.
I suspect it's the LUKS that's at issue, I've
Testsuite summary for GRUB 2.06
# TOTAL: 82
# PASS: 21
# SKIP: 13
# XFAIL: 0
# FAIL: 48
# XPASS: 0
# ERROR: 0
I can browse grub bug, but...
--
Jarno Suni
Grub2, Mint 18, Ubuntu 16.04 and 16.10 tested
Grfx card Amd rx460
Official drivers/unofficial drivers tested
Resolution will not change from default using both grub customizer or
manual set.
Kind regards,
Sean Mayes
___
Bug-grub mailing list
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
On 13.01.2016 08:46, Andrei Borzenkov wrote:
> 13.01.2016 10:26, Minyoung Go пишет:
>> *Dear GNU Grub Members.*
>> I found weired comments at /grub-core/boot/i386/pc/boot.S. Comments
>> in Line 221, 222 is "ljmp to the next instruction because some bogus BIOSes
>> jump to 07C0: instead of
13.01.2016 10:26, Minyoung Go пишет:
> *Dear GNU Grub Members.*
> I found weired comments at /grub-core/boot/i386/pc/boot.S. Comments
> in Line 221, 222 is "ljmp to the next instruction because some bogus BIOSes
> jump to 07C0: instead of :7C00.". However, "ljmp$0,
> $real_start" is no
root@ivanaxe-x201i:~# grub-install --recheck /dev/sda
/usr/sbin/grub-probe: ошибка: unknown filesystem.
Auto-detection of a filesystem of /dev/sda2 failed.
Try with --recheck.
If the problem persists please report this together with the output of
/usr/sbin/grub-probe
On 29.04.2012 05:51, Midnight Matt wrote:
To whom it may concern:
I have tried and failed to manually install a grub bootloader onto an
external hard drive. So here is the output from the `/usr/sbin/grub-probe
--device-map=/media/EHD/boot/grub/device.map --target=fs -v
hello,
I have tried to upgrade my debian squeeze and the kernel failed to
install. It seems to be a problem with grub-install :
/
root@srvlan:/home/red0queen# grub-install /dev/xvda1
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/mapper/srvlan-boot failed.
On 28.09.2011 15:22, red0queen wrote:
/
root@srvlan:/home/red0queen# grub-install /dev/xvda1/
grub-install --recheck //dev/xvda/
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
___
Bug-grub
On 15.05.2011 01:33, Rohit Pande wrote:
root@the-moose-machine:/home/rohit# grub-install --force --no-floppy
--root-directory=/media/MULTIBOOT /dev/sdb
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sdb1.
Check your device.map.
Auto-detection of a filesystem of /dev/sdb1
root@the-moose-machine:/home/rohit# grub-install --force --no-floppy
--root-directory=/media/MULTIBOOT /dev/sdb
/usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sdb1.
Check your device.map.
Auto-detection of a filesystem of /dev/sdb1 failed.
Please report this together with the
On 10.02.2011 16:41, Leeman Strout wrote:
tester grub.d # grub-install /dev/sda
/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/mapper/rootlv-root failed.
Please report this together with the output of /sbin/grub-probe
--device-map=/boot/grub/device.map
On 17.02.2011 11:20, Denis Dokleja wrote:
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/ata-GB0500EAFYL_WCASY8399240', skipping.
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/ata-GB0500EAFYL_WCASY7517115', skipping.
Was it run under root? Do these devices exist? Try
Hi all,
I tried to upgrade from lenny to squeeze, and all went fine except
after the dist-upgrade and reboot I issued upgrade-from-grub-legacy
and it failed. I am using software raid on two disks, and I was not able
to install GRUB to either of my disks. Disks are /dev/sda and /dev/sdb.
As a follow on to this, the output from grub-mkimage
tester grub.d # grub-mkimage --output=/boot/grub/core.img ext2 _chain
part_msdos part_gpt biosdisk lvm
Target format not specified (use the -O option).
Try `grub-mkimage --help' for more information.
It provides a list of possible image
I am attempting to go with all partitions located on LVM, including
/boot containing grub's files. Here is the resultant error:
tester grub.d # grub-install /dev/sda
/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/mapper/rootlv-root failed.
Please report this
grml:/# /usr/sbin/grub-probe --device-map=/boot/grub/device.map
--target=fs -v /boot/grub
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-1AMCC_3QF0QNYWC318ED001709', skipping.
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-1AMCC_3QF0SGE4C318ED000F4B', skipping.
I got basically the same device map back again, though.
(fd0) /dev/fd0
(hd0) /dev/disk/by-id/ata-ST3320620AS_3QF0SGE4
(hd1) /dev/disk/by-id/ata-ST3320620AS_3QF0QNYW
I quote my current grub.cfg below. This gives an error after booting,
saying it cannot find the newdebian volume
On 01/04/2011 07:52 PM, Faheem Mitha wrote:
Note that if you do, the system was halting on an initramfs prompt,
not a grub prompt,
Then (90% chance) it's outside of GRUB realm. I recommend contacting
your distro
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description:
u
On Tue, 4 Jan 2011, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
On 01/04/2011 07:52 PM, Faheem Mitha wrote:
Note that if you do, the system was halting on an initramfs prompt, not
a grub prompt,
Then (90% chance) it's outside of GRUB realm. I recommend contacting
your distro
Well,
Hi Vladimir,
Thanks for the helpful reply.
On Tue, 4 Jan 2011, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
grml:/# /usr/sbin/grub-probe --device-map=/boot/grub/device.map
--target=fs -v /boot/grub
/usr/sbin/grub-probe: info: Cannot stat
`/dev/disk/by-id/scsi-1AMCC_3QF0QNYWC318ED001709',
This is part of an attempt to install grub2 to the software raid array
from inside a chroot.
I was trying to mount the boot partition on the chrooted root partition,
both on them logical volumes on a software raid device. grub seems to be
having problems with the boot device though. The vg
On Mon, 3 Jan 2011, Faheem Mitha wrote:
This is part of an attempt to install grub2 to the software raid array from
inside a chroot.
I was trying to mount the boot partition on the chrooted root partition, both
on them logical volumes on a software raid device. grub seems to be having
The following bug was found: 30_os-prober does not remove grub-legacy
specific data
Operating system: Sabayon 5.2
Kernel:kernel-genkernel-x86_64-2.6.33-sabayon
Grub version: 1.97.2-r2 ??
Symptoms: does not start (hd0,1) unless the last line of
mao xuedan escribió:
I setup the grub for one hard disk image file according to
http://kbarr.net/bochs .
I am offline I do not know what's written there.
When I runing under bochs, it reports that
File not found. If under grub shell, I input kernel /boot/vmlinux.*
and initrd /boot/initrd.*
I setup the grub for one hard disk image file according to
http://kbarr.net/bochs . When I runing under bochs, it reports that File
not found. If under grub shell, I input kernel /boot/vmlinux.* and initrd
/boot/initrd.* and then boot, it will restart the boot and still complain
that File not
Hello there,
I just tried to compile package grub-0.96-6 with the Intel C compiler
It said
i82586.c(754): warning #592: variable shmem is used before its value is
set
The source code is
while (
shmem[iSCB_STATUS1] == 0)
Suggest initialise local array shmem
Hello,
This isn't a GRUB bug, but rather an addition to the list of buggy BIOS
versions in http://www.gnu.org/software/grub/manual/grub.html#install - you may
want to consider updating that list.
Installing GRUB manually with install /boot/grub/stage1 d (hd0)
/boot/grub/stage2 p fixes the
Hi there
I´ve found a bug in (GNU) Grub.
I´ve got the Abit AN7 Mainboard with included SATA Controller (check
out http://www.abit-usa.com/products/mb/products.php?categories=1model=158
for further information).
My first booting device is the harddisk at the onboard add-in card
(SATA Controller)
Hi Tobias,
On Tue, Sep 13, 2005 at 03:50:00PM +0200, Tobias Koeck wrote:
Hi there
I´ve found a bug in (GNU) Grub.
[detailed bug description deleted]
reinstall grub with grub-install and reconfigurate the grub.lst to get
it work. But after I´ve updated to a new kernel the same problem
you should double check whats in /etc/fstab also look at the `mount`
command.
Just to make sure that it says /dev/sda and not /dev/hdb.
On Tue, Sep 13, 2005 at 03:50:00PM +0200, Tobias Koeck wrote:
Hi there
I´ve found a bug in (GNU) Grub.
I´ve got the Abit AN7 Mainboard with included SATA
summary
==
stage2 hangs the PC with primary partitions defined after extended
partitions
Soft version:0.95
=
Problem description:
==
The installation (trough anaconda) of fedora core3 Distribution Iso Dvd
produced a grub stage2 hang on the Pc, with the following disk
On Sun, Feb 15, 2004 at 07:28:47AM +0100, Almacha wrote:
BUG: i18n and keytable commands does not work
RELEASE: 0.93
SNIP
Those commands are modifications made by the distributor and have
never been in the official grub version. They aren't supported and
any bugs about them should be reported
On Thursday 15 January 2004 01:38, Shen Feng wrote:
No. It's the latest glibc.
Please refer to /usr/include/sys/sysmacros.h.
Ah, I see. The glibc assumes that a device number could be 64 bit rather
than 32 bit. So | ((unsigned int) (__dev 32) ~0xfff) is
meaningful. If it is 32 bit, this
On Tuesday 13 January 2004 04:38, Shen Feng wrote:
I think the following code in lib/device.c
60 # ifndef MAJOR
61 # ifndef MINORBITS
62 # define MINORBITS8
63 # endif /* ! MINORBITS */
64 # define MAJOR(dev)((unsigned int) ((dev) MINORBITS))
65
PROTECTED]
--
- Original Message -
From: Yoshinori K. Okuji [EMAIL PROTECTED]
To: Shen Feng [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, December 24, 2003 8:08 PM
Subject: Re: Linux device number bug report
On Wednesday 24 December
On Wednesday 24 December 2003 04:55, Shen Feng wrote:
In Linux kernel 2.6, device number will be extended from 16-bit to
32-bit. All utilities and libraries should make corresponding
extension for this new feature in kernel 2.6.
Exactly.
I find that grub-0.93-7 uses variables major and minor
Hello,I have some questions about device number
extension.In Linux kernel 2.6, device number will be extended from
16-bit to 32-bit. All utilities and libraries should make corresponding
extension for this new feature in kernel 2.6. I find that grub-0.93-7
uses variables "major" and
in lvm as well.
The order of lvols on disk (/boot, swap, / --- all contiguous)
would be just fine with me. However, I prefer grub over lilo.
When searching I found a patch by Jorg Walter on the grub home page
http://savannah.gnu.org/projects/grub/
listed as bug report # 977
http
On Wednesday 06 November 2002 12:59, you wrote:
As others, too, I would like to have /boot reside in lvm as well.
The order of lvols on disk (/boot, swap, / --- all contiguous)
would be just fine with me. However, I prefer grub over lilo.
My grub patch does not need any alignment or layout of
On Thu, Oct 12, 2000 at 06:57:05AM +0900, OKUJI Yoshinori wrote:
From: Thierry Laronde [EMAIL PROTECTED]
Subject: [0.5.97] not a bug report
Date: Wed, 11 Oct 2000 22:11:58 +0200
I have downloaded 0.5.97 : I didn't make an extensive debuging, but, at
least, for me and now, it works like
r 11, 2000 5:57 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [0.5.97] not a bug report
From: Thierry Laronde [EMAIL PROTECTED]
Subject: [0.5.97] not a bug report
Date: Wed, 11 Oct 2000 22:11:58 +0200
I have downloaded 0.5.97 : I didn't make an extensive debuging, but, at
l
Hi there,
Just a quick bug report for GRUB. Thanks very much for writing it - it
was very easy to set up and is much better than Lilo for my needs :)
System details:
zaphod:~ uname -a
Linux zaphod 2.2.16 #12 Thu Aug 10 19:00:36 WST 2000 i686 unknown
zaphod:~ cat /proc/partitions
major
want to enable a set of ethernet cards, but I have
problems with this. Often the probing of ethernet interfaces hangs, if
the card is not found.
And this leads me to the bug report for etherboot:
Especially the NE*000 and the NE2000/PCI hangs in the first pio_write
function in the last 'while-loop
And this leads me to the bug report for etherboot:
Especially the NE*000 and the NE2000/PCI hangs in the first pio_write
function in the last 'while-loop', if there is no NE card. Further
my Rtl8029 (OvisLink NE2000 PCI) hangs in the NE2000/PCI probe on this
position (code
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
55 matches
Mail list logo
