bug-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #63975] "no server is specified" error message when loading a font


From: Andrea
Subject: [bug #63975] "no server is specified" error message when loading a font
Date: Wed, 29 Mar 2023 07:13:23 -0400 (EDT)

URL:
  <https://savannah.gnu.org/bugs/?63975>

                 Summary: "no server is specified" error message when loading
a font
                   Group: GNU GRUB
               Submitter: viavisolutions
               Submitted: Wed 29 Mar 2023 11:13:21 AM UTC
                Category: User Interface
                Severity: Major
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: other
                 Release: 
         Discussion Lock: Any
         Reproducibility: Every Time
         Planned Release: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 29 Mar 2023 11:13:21 AM UTC By: Andrea <viavisolutions>
I'm using grub 2.06 on ubuntu 22.04 to create a simple rescue disk like so:


#! /bin/sh

rm -rf build

mkdir -p build
cp vmlinuz build/

mkdir -p build/boot/grub
cat > build/boot/grub/grub.cfg << EOF
insmod all_video

echo "loading font"
loadfont unicode
echo "font loaded"
sleep 5

set gfxpayload=keep

set timeout=-1
set timeout_style=menu

menuentry linux {
  linux /vmlinuz
}
EOF

grub-mkrescue -o out.iso build


The resulting hybrid image can be booted in 4 different ways:
1. bios boot protocol, as a cdrom
2. bios boot protocol, as a hdd (say, a usb stick)
3. uefi boot protocol, as a cdrom
4. uefi boot protocol, as a hdd (say, a usb stick)

However, when booted in UEFI mode, loadfont will fail with:


error: no server is specified.


I'm not sure why grub would try to load something from the network; a couple
of observations:
- If you drop to a command line and execute all_functional_tests, you will see
additional failures related to the unicode font.
- The grub environment (as reported by "set") contains some network-related
entries that are not present when booting the same image in bios mode.
- If you load the font with the full path, grub won't complain (but, according
to the documentation, that shouldn't be needed).








    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63975>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]