The --disk-module=MODULE option of grub-install don't work
My OS is ubuntu14.04.
And the command grub-install -V shows that the grub version is Grub
2.02~beta2-9.
Since I have two disk on my laptop, and one of them is not bootable, I have to
use nativedisk option.
But the --disk-module=MODULE
It would not install boot-repair as its not available for 14.04 64 bit yet.
Tried sudo debconf-show grub-pc but did not seem to show any path.
Tried sudo dpkg-reconfigure grub-pc and it just gave a blank command line.
Booted the live CD to re-install and it offered an upgrade from 14.04 to 14.04
I tried a test install of Trusty beta2 on 30/03/14. It installed fine
then when I rebooted I got :-
error: symbol 'grub_term_highlight_color' not found
Entering rescue mode...
I am going to try boot-repair to see if that fixes it.
--
You received this bug notification because you are a member
... also, build-depends of grub2-2.02 are not right, see bug #1299041
Required for building, but not in build-depends: lzop hfsplus squashfs-tools
attr reiserfsprogs automake1.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This new bug
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1298399 is also on
trusty, with grub 2.02~beta2-7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires
I still have the problem described in #5. There's another bug report for
it:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
There's still the odd scattered problem, but I'm happy with the state of
things now, and I think this is ready to land in trusty. Thanks
everyone for the testing!
** Changed in: grub2 (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member
I dont think so ! The problems with the picture is solved.
Basic is a fresh installed trusty 'Kubuntu'.
grub-version after installation was 2.00-22
After the upgrade (activated proposed) grub packages 2.02~beta2-5 I got these:
* an additional folder 'grub' - see below
Upgrade of an older 'Ubuntu-GNOME' installation
* from 2.02~beta2-4 to 2.02~beta2-5
is working without any malfunction. No additional folder 'grub' has been
created, picture is show now inside 'grub-menu'
Again: in the 'Kubuntu' installation the
* 'nvram-entry' Boot* ubuntu
has been
syscon-hh: Can you please file a new bug report for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires manual testing
To manage notifications about this bug go
Done -
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1273694
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires manual testing
To manage notifications
Sorry, if this has already been pointed out. I notice that it's not only
the timeout that grub will ignore, recently I changed the style to
countdown but the menu is still shown.
On Tue, Jan 28, 2014 at 10:43 AM, syscon-hh syscon.k...@freenet.de wrote:
Done -
Done, #1273764 :-)
On Tue, Jan 28, 2014 at 12:12 PM, Colin Watson cjwat...@canonical.comwrote:
Could you please file a new bug report for any remaining issues,
attaching any relevant information? This one is closed, and it's not
going to be a practical way to track things on an ongoing
Could you please file a new bug report for any remaining issues,
attaching any relevant information? This one is closed, and it's not
going to be a practical way to track things on an ongoing basis.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oh, right, we're missing the gfxterm_background module in the signed
image. Thanks - I'll fix this for 2.02~beta2-5.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2
Hallo I'm back after a long periode of testing / investigations.
The problem is located inside 'secure-boot' !
Switching inside EFI-BIOS to 'non-secure-boot' option all works as
axpected.
It's not based in the form of picture (*.png either *.jpg).
Based on the output of grub-shell showing ever
** Attachment added: /boot/grub/themes/***/theme.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+attachment/3956549/+files/themes-danmark-theme.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: /etc/default/grub
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+attachment/3956547/+files/etc-default-grub.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: /boot/grub/grub.cfg
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+attachment/3956548/+files/boot-grub-grub.cfg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The submitted '/boot/grub/grub.cfg' is the output of above '/etc/default/grub'
and will not work below
- grub 2.02~beta2-4
but without any restriction below
- grub 2.00-22
The '/boot/grub/themes/***/theme.txt' ist working with 'secure-boot'
witout restrictions on all systems.
--
You
On Wed, Jan 22, 2014 at 05:54:05PM -, Cavsfan wrote:
It works great for me. I have a custom grub menu (font, picture and
display) and the only difference I can see it an asterisk besides the
selected line.
Thanks. This was an intentional upstream change, so that the selection
would still
syscon-hh: My guess is that this is due to:
2013-10-28 Vladimir Serbinenko phco...@gmail.com
Make / in btrfs refer to real root, not the default volume.
Modify mkrelpath to work even if device is mounted with subvolid option.
... so I think the question is why the /@ prefix is
Hm, no, I can reproduce this, so I don't need the output of grub-
mkrelpath. It's not a general problem with btrfs, so my previous guess
was wrong - booting works fine and that wouldn't work if we were
handling relative paths wrongly. I'll see if I can reproduce this in a
more stripped-down
I can't load that background image with a rescue disk built from 2.00
either; background_image fails, apparently because it tries to create a
width 0 / height 0 bitmap while loading the JPEG file in question. I
suspect this is a bug in GRUB's JPEG reader, but I'm confused as to how
it's a
Stones.jpg is a progressive JPEG; as far as I can tell GRUB just doesn't
support decoding these and never has. I'm happy to have a go at adding
support, but this isn't your regression. Since you mention a themes
directory, I suspect the non-loaded background image was being masked by
a theme
Have a standard install with 4 different levels of Ubuntu on 2 hard
drives. No problems to report except that during the install got the
prompt to keep the grub configuration or install the new one. I know
what mods I have done so I said install the new configuration file and
expected the
Further no more working function found here - all relevant systems
after upgrade involved!
The background picture is stated in the '/etc/default/grub'
- GRUB_GFXMODE=1024x768
- GRUB_BACKGROUND=/usr/share/backgrounds/gnome/Stones.jpg
Both versions 2.00-22 as well as 2.02~beta2-4 output of 'sudo
It works great for me. I have a custom grub menu (font, picture and
display) and the only difference I can see it an asterisk besides the
selected line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here it won't work:
tail of terminal output *
root@USB-GDM-TRUSTY:~# grub-install -v
line numbers for indification only
line 1 : grub-install: Info: the core size is 0x26978.
line 2 : grub-install: Info: writing 0x27c00 bytes.
line 3 : grub-install: Info: copying
syscon-hh: Thanks for your report. This was caused by a mistake of mine
in translating the shell-based shim installation patch to C. I've fixed
it for 2.02~beta2-4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested on ThinkPad X230 amd64 with UEFI and SecureBoot enabled. The
upgrade went flawlessly and two reboots worked just fine, one with a new
kernel after a kernel dist-upgrade, and one simple reboot to the same
kernel. In both cases I got the grub menu (10 s timeout) without asking
for it, but I
@cjwatson - as soon as I get to chance to look again - either on this
machine or another I will post back again - for the moment I've purged
the beta grub and reinstalled 2.00-22 . Didn't have the time to spend on
a completely unbootable machine last night.
--
You received this bug notification
Here's my /etc/default/grub, I think it's quite standard. I tried with
hidden timeout commented out, too. And ran `update-grub` to save changes
before restarting the machine. (After restarting the menu is shown with
a 10 second timeout.)
** Attachment added: /etc/default/grub
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: grub2 (Ubuntu)
Status: New = Triaged
** Changed in: grub2 (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Trying that new version on a laptop (one disk/OS, no secure boot, i386
trusty installation), the boot works without issue.
Trying to open the grub menu on boot to try the rescure option has has
been leading to a situation where the grub menu is opening at every boot
now though...
It seems also
These are different manifestations of the same problem. I think I
dropped a little bit too much of quick_boot.patch when rebasing to
2.02~beta2; I'll see about fixing it up to preserve the previous
behaviour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have no issues booting either Windows 7 nor Ubuntu on a laptop (hp
nx7400).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires manual testing
To manage
Sebastien: Fixed for 2.02~beta2-4:
http://anonscm.debian.org/gitweb/?p=pkg-
installed fine
booted to
error: symbol 'grub_term_highlight_color' not found
entered rescue mode - then I ended up at busybox
not really sure how I managed to get back (long day) but I've purged and
reinstalled the original grub
--
You received this bug notification because you are a member
I set GRUB_TIMEOUT to 0 in /etc/default/grub, but the default entry
isn't booted automatically.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires manual testing
To
It worked perfectly fine for my dekstop, dual booting with Windows XP.
(i386)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires manual testing
To manage
Elfy (#5): Thanks for your report. We run across this pattern with
every substantial enough change to GRUB. It's not actually a problem
with the new upstream per se - it points to a misconfiguration in how
GRUB is installed, and unfortunately we've never quite tracked down the
root cause.
42 matches
Mail list logo
