Probably GRUB problem with Debian 9.7.0

Help with issues regarding installation of Debian

Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-02-19 11:03

I have Windows 10 Pro on my computer. In W10P I have chosen to be able to run old games in Windows Vista mode. I also have installed one game in that mode. WV is in BIOS while W10P is in UEFI (I’m not so good at those things so it can be in some other way.)

When I was doing an installation of Debian I came to a place where I could choose between both UEFI and BIOS or only UEFI. First I tried UEFI and BIOS and the installation worked quite well. But I wasn’t able to start W10P after the installation.

The next thing I did was to choose the only UEFI alternative, because I wanted to be able to start W10P. The installation went well until I came to GRUB. There I got a fatal error and was forced to exit.

I installed Debian again in both UEFI and BIOS. And I’m in that situation now. I cannot reach W10P.

What can be done to solve this problem?
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby p.H » 2019-02-19 13:00

Please install the package boot-info-script and post the report generated by
Code: Select all
bootinfoscript
p.H
 
Posts: 1091
Joined: 2017-09-17 07:12

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-14 16:32

I have tried to solve the problem myself. When I used an information that I found in a computer magazine in Sweden (that was supposed to solve the problem) I couldn't reach the place where I was supposed to write the code. The text is in Swedish so I'm doing a probably bad translation here:

-----------
If Windows is missing from the bootmenu
If you have installed Windows after you have installed Ubuntu then is probably Windows not included in the configuration file for Grub and therefore is it not in the boot menu. To fix this you need to change a little in the configuration file with the following command:

sudo gedit/boot/grub/menu.lst

At the end of the file, after ## ## End Default Options ##, add the following:

title Windows 95/98/NT/2000/XP
root (hd0,0)
makeactive
chainloader +1

If Windows isn't at hd0,0 you need to change that value. If you for example installed Windows on partition 4 on the first Hard Disk so will the value be (hd0,3).
-------------

There was text above the text I translated above. That was about how to get Grub back after an Windows installation. But I don't think that it has anything to do with this problem.

The text is very old as you can see, but I was hoping that it could have solved the problem anyway.

I couldn't do this because I couldn't reach the place. I was reported because 'lander' was not something (I can't remember what message I got). Lander is my user name. I gave my user code and it was then I was reported.
I don't know what to do now.

I haven't answered earlier because I couldn't do what you wrote. I'm to new to Debian to be able to do it.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby Head_on_a_Stick » 2019-03-14 18:51

Delta Gamma wrote:I haven't answered earlier because I couldn't do what you wrote. I'm to new to Debian to be able to do it.

First enter this command:
Code: Select all
su -

Then enter the root password and run
Code: Select all
apt install boot-info-script

And then pass the command suggested by p.H and paste the output here using code tags.

If you want to use `sudo` then see the Debian wiki page about sudo for instructions.

Note that there is no /boot/grub/menu.list, that is for an old version of GRUB. See the Debian wiki page about GRUB for more information about this.
User avatar
Head_on_a_Stick
 
Posts: 10382
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-14 20:15

This should be it

Code: Select all
echo

lander@debian:~$ su -
Password:
root@debian:~# apt install boot-info-script
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  boot-info-script
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 35.2 kB of archives.
After this operation, 157 kB of additional disk space will be used.
Get:1 http://ftp.us.debian.org/debian stretch/main amd64 boot-info-script all 0.61-2 [35.2 kB]
Fetched 35.2 kB in 0s (57.5 kB/s)           
Selecting previously unselected package boot-info-script.
(Reading database ... 232640 files and directories currently installed.)
Preparing to unpack .../boot-info-script_0.61-2_all.deb ...
Unpacking boot-info-script (0.61-2) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up boot-info-script (0.61-2) ...
root@debian:~#



EDIT: and I have this

Code: Select all
echo

lander@debian:~$ su -
Password:
root@debian:~# bootinfoscript

Boot Info Script 0.61      [1 April 2012]

Identifying MBRs...
Computing Partition Table of /dev/sda...
Computing Partition Table of /dev/sdb...
Searching sda1 for information...
Searching sda2 for information...
Searching sda3 for information...
Searching sdb1 for information...
Searching sdb2 for information...
Searching sdb5 for information...
Searching sdb6 for information...

Finished. The results are in the file "RESULTS3.txt"
located in "/root/".

root@debian:~#



but I cannot reach RESULTS3.txt.
Last edited by Delta Gamma on 2019-03-14 22:42, edited 3 times in total.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby p.H » 2019-03-14 21:54

Now you can run
Code: Select all
bootinfoscript

as root and post the generated report.
p.H
 
Posts: 1091
Joined: 2017-09-17 07:12

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-14 22:38

Sorry. More information is in my earlier reply now.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-15 13:14

Here comes it. As you can see doesn't Windows 10 come up in Boot sector type. Both Windows 10 and Windows Vista should be there. The computer was downgraded to Windows 7 from Windows 10 when I bought it.

Code: Select all
echo

                  Boot Info Script 0.61      [1 April 2012]


============================= Boot Info Summary: ===============================

 => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 85 for .
 => Grub2 (v1.99) is installed in the MBR of /dev/sdb and looks at sector 1 of
    the same hard drive for core.img. core.img is at this location and looks
    in partition 85 for .

sda1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /bootmgr /Boot/BCD

sda2: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:        /bootmgr /Windows/System32/winload.exe

sda3: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:       

sdb1: __________________________________________________________________________

    File system:       ntfs
    Boot sector type:  Windows Vista/7: NTFS
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System: 
    Boot files:       

sdb2: __________________________________________________________________________

    File system:       Extended Partition
    Boot sector type:  -
    Boot sector info:

sdb5: __________________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info:
    Operating System:  Debian GNU/Linux 9
    Boot files:        /boot/grub/grub.cfg /etc/fstab

sdb6: __________________________________________________________________________

    File system:       swap
    Boot sector type:  -
    Boot sector info:

============================ Drive/Partition Info: =============================

Drive: sda _____________________________________________________________________
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sda1    *          2,048     1,026,047     1,024,000   7 NTFS / exFAT / HPFS
/dev/sda2           1,026,048   248,297,897   247,271,850   7 NTFS / exFAT / HPFS
/dev/sda3         248,299,520   250,064,895     1,765,376  27 Hidden NTFS (Recovery Environment)


Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos

Partition  Boot  Start Sector    End Sector  # of Sectors  Id System

/dev/sdb1    *          2,048   976,564,547   976,562,500   7 NTFS / exFAT / HPFS
/dev/sdb2         976,566,270 1,953,523,711   976,957,442   5 Extended
/dev/sdb5         976,566,272 1,920,182,271   943,616,000  83 Linux
/dev/sdb6       1,920,184,320 1,953,523,711    33,339,392  82 Linux swap / Solaris


"blkid" output: ________________________________________________________________

Device           UUID                                   TYPE       LABEL

/dev/sda1        DEB07BE7B07BC495                       ntfs       System Reserved
/dev/sda2        AC6E813E6E810276                       ntfs       
/dev/sda3        92341FF4341FD9D5                       ntfs       
/dev/sdb1        DCE843F1E843C88A                       ntfs       New Volume
/dev/sdb5        14c2725a-a2f7-4748-9955-0ab037ac1432   ext4       
/dev/sdb6        947fa74e-3c59-4c18-bf4b-3e49adb464b0   swap       

================================ Mount points: =================================

Device           Mount_Point              Type       Options

/dev/sdb5        /                        ext4       (rw,relatime,errors=remount-ro,data=ordered)


=========================== sdb5/boot/grub/grub.cfg: ===========================

--------------------------------------------------------------------------------
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
    insmod all_video
  else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod ext2
set root='hd1,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos5 --hint-efi=hd1,msdos5 --hint-baremetal=ahci1,msdos5  14c2725a-a2f7-4748-9955-0ab037ac1432
else
  search --no-floppy --fs-uuid --set=root 14c2725a-a2f7-4748-9955-0ab037ac1432
fi
    font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_US
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
    set timeout_style=menu
    set timeout=5
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
    set timeout=5
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd1,msdos5'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos5 --hint-efi=hd1,msdos5 --hint-baremetal=ahci1,msdos5  14c2725a-a2f7-4748-9955-0ab037ac1432
else
  search --no-floppy --fs-uuid --set=root 14c2725a-a2f7-4748-9955-0ab037ac1432
fi
insmod png
if background_image /usr/share/desktop-base/softwaves-theme/grub/grub-4x3.png; then
  set color_normal=white/black
  set color_highlight=black/white
else
  set menu_color_normal=cyan/blue
  set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
        set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-14c2725a-a2f7-4748-9955-0ab037ac1432' {
        load_video
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_msdos
        insmod ext2
        set root='hd1,msdos5'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos5 --hint-efi=hd1,msdos5 --hint-baremetal=ahci1,msdos5  14c2725a-a2f7-4748-9955-0ab037ac1432
        else
          search --no-floppy --fs-uuid --set=root 14c2725a-a2f7-4748-9955-0ab037ac1432
        fi
        echo    'Loading Linux 4.9.0-8-amd64 ...'
        linux   /boot/vmlinuz-4.9.0-8-amd64 root=UUID=14c2725a-a2f7-4748-9955-0ab037ac1432 ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /boot/initrd.img-4.9.0-8-amd64
}
submenu 'Advanced options for Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-14c2725a-a2f7-4748-9955-0ab037ac1432' {
        menuentry 'Debian GNU/Linux, with Linux 4.9.0-8-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.9.0-8-amd64-advanced-14c2725a-a2f7-4748-9955-0ab037ac1432' {
                load_video
                insmod gzio
                if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
                insmod part_msdos
                insmod ext2
                set root='hd1,msdos5'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos5 --hint-efi=hd1,msdos5 --hint-baremetal=ahci1,msdos5  14c2725a-a2f7-4748-9955-0ab037ac1432
                else
                  search --no-floppy --fs-uuid --set=root 14c2725a-a2f7-4748-9955-0ab037ac1432
                fi
                echo    'Loading Linux 4.9.0-8-amd64 ...'
                linux   /boot/vmlinuz-4.9.0-8-amd64 root=UUID=14c2725a-a2f7-4748-9955-0ab037ac1432 ro  quiet
                echo    'Loading initial ramdisk ...'
                initrd  /boot/initrd.img-4.9.0-8-amd64
        }
        menuentry 'Debian GNU/Linux, with Linux 4.9.0-8-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-4.9.0-8-amd64-recovery-14c2725a-a2f7-4748-9955-0ab037ac1432' {
                load_video
                insmod gzio
                if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
                insmod part_msdos
                insmod ext2
                set root='hd1,msdos5'
                if [ x$feature_platform_search_hint = xy ]; then
                  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos5 --hint-efi=hd1,msdos5 --hint-baremetal=ahci1,msdos5  14c2725a-a2f7-4748-9955-0ab037ac1432
                else
                  search --no-floppy --fs-uuid --set=root 14c2725a-a2f7-4748-9955-0ab037ac1432
                fi
                echo    'Loading Linux 4.9.0-8-amd64 ...'
                linux   /boot/vmlinuz-4.9.0-8-amd64 root=UUID=14c2725a-a2f7-4748-9955-0ab037ac1432 ro single
                echo    'Loading initial ramdisk ...'
                initrd  /boot/initrd.img-4.9.0-8-amd64
        }
}

### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###

### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
        fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries.  Simply type the
# menu entries you want to add after this comment.  Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f  ${config_directory}/custom.cfg ]; then
  source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f  $prefix/custom.cfg ]; then
  source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
--------------------------------------------------------------------------------

=============================== sdb5/etc/fstab: ================================

--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sdb5 during installation
UUID=14c2725a-a2f7-4748-9955-0ab037ac1432 /               ext4    errors=remount-ro 0       1
# swap was on /dev/sdb6 during installation
UUID=947fa74e-3c59-4c18-bf4b-3e49adb464b0 none            swap    sw              0       0
/dev/sr1        /media/cdrom0   udf,iso9660 user,noauto     0       0
/dev/sr0        /media/cdrom1   udf,iso9660 user,noauto     0       0
--------------------------------------------------------------------------------

=================== sdb5: Location of files loaded by Grub: ====================

           GiB - GB             File                                 Fragment(s)


========= Devices which don't seem to have a corresponding hard drive: =========

sdc

=============================== StdErr Messages: ===============================

cat: /tmp/BootInfo-JfT9dnyY/Tmp_Log: No such file or directory

(END)



I had to copy the text in small units. I have checked it and it's okay. But there is a small possibility that I have done something wrong when I checked it. I couldn't figure out how to mark the whole text.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby p.H » 2019-03-15 14:09

Why did you have to copy the report in small units ? Couldn't you just open it in a GUI text editor and copy it all at once ?

The report tells me that :
- GRUB for BIOS (not EFI) is installed in the MBR of both drives.
- Both drives have DOS partition tables, so any Windows instance has been installed for BIOS mode, not EFI mode.
- sda1 and sda2 contain a Windows boot manager for BIOS (/bootmgr).
- There is no EFI partition so Debian has not been installed (at least not successfully) for EFI mode.
- Paradoxically, grub.cfg contains a menu entry to enter the EFI firmware setup, which can be created only when the system has been booted in EFI mode. This does not make sense.

First check if Debian booted in BIOS/legacy or EFI mode. Several checks are available.
1) At the GRUB menu, press "c" and type the command "set". Check the values of cmdpath and platform. If they contain "EFI" or "efi" this is GRUB for EFI.
2) In a Debian shell, type the following command
Code: Select all
ls /sys/firmware

If the "efi" directory is present, then the system is booted in EFI mode.
Code: Select all
ls /boot/grub

If the x86_64-efi directory is present, GRUB for EFI is installed.
If the i386-pc directory is present, GRUB for BIOS is installed.

If the system is booted in BIOS mode, the command "os-prober" should find Windows.
p.H
 
Posts: 1091
Joined: 2017-09-17 07:12

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-15 21:24

Check number 1)

I got this code:

Code: Select all
echo

grub>set
?=0
cmdpath=(hd0)
color_highlight=black/white
color_normal=white/black
default=0
feature_200_final=y
feature_all_video_module=y
feature_chainloader_bpb=y
feature_default_font_path=y
feature_menuentry_id=y
feature_menuentry_options=y
feature_nativedisk_cmd=y
feature_ntldr=y
feature_platform_search_hint=y
feature_timeout_style=y
font=unicode
gfxmode=auto
grub_cpu=i386
grub_platform=pc
have_grubenv=true
lang=en_US
linux_gfx_mode=
locale_dir=(hd1,msdos5)/boot/grub/locale
menuentry_id_option=--id
pager=
prefix=(hd1,msdos5)/boot/grub
root=hd1,msdos5
secondary_locale_dir=
timeout_style=menu
grub>



from that I see that it's not EFI. And that grub_cpu=i386 and grub_platform=pc. So it must be GRUB for BIOS.

Check number 2)

With ls /sys/firmware i could see that efi is not there.
so I didn't check ls /boot/grub

Then I looked for Windows with "os-prober" and got
/dev/sda1:Windows 10:Windows:chain

But this can be a back door. Because I made it available when I installed Debian. I have been able to reach Windows text files the whole time without starting Windows.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-15 21:34

I should have tested

ls /boot/grub.

I have done it now with this result: i386-pc is there but not x86_64-efi so it must be GRUB for BIOS.

One thing. When I used Windows 10 the BIOS didn't look as the BIOS I have seen before. I thought that it was UEFI.
Last edited by Delta Gamma on 2019-03-15 21:41, edited 1 time in total.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby p.H » 2019-03-15 21:38

I suspect that you booted the installer in EFI mode and it detected an installed OS (Windows) booting in BIOS mode so it asked whether it should do a BIOS install or an EFI install. When you selected EFI, it failed due to the lack of an EFI partition. When you selected BIOS, grub.cfg was generated from an EFI point of view anyway, so it included the EFI firmware setup and excluded Windows.

Rebuilding grub.cfg with update-grub should add Windows to the boot menu.
p.H
 
Posts: 1091
Joined: 2017-09-17 07:12

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-15 23:00

This wasn't so easy to do. There are so many to choose from. Which one of the update-grub should I pick? And what should I do to rebuild grub.cfg with update-grub?
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Re: Probably GRUB problem with Debian 9.7.0

Postby p.H » 2019-03-15 23:01

What are you talking about ? There is only one update-grub command. You just run it and that's it.
p.H
 
Posts: 1091
Joined: 2017-09-17 07:12

Re: Probably GRUB problem with Debian 9.7.0

Postby Delta Gamma » 2019-03-16 21:07

I have downloaded this:
grub2_2.02~beta3-5+deb9u1.debian.tar.xz

I do this in Vim:

Code: Select all
echo

lander@debian:~/Downloads/debian$ dir
apport
bug-presubj
bug-script
build-efi-images
changelog
clean
compat
config.in
control
copyright
default
dirs.in
grub2-common.install
grub2-common.links
grub2-common.manpages
grub2.maintscript
grub-common.dirs
grub-common.examples
grub-common.init
grub-common.install.in
grub-common.install.kfreebsd.in
grub-common.install.linux.in
grub-common.install.sparc64.in
grub-common.install.sparc.in
grub-common.links
grub-common.maintscript.hurd.in
grub-common.maintscript.kfreebsd.in
grub-common.maintscript.linux.in
grub-common.pm-sleep
grub-coreboot-bin.install.amd64.in
grub-coreboot-bin.install.kopensolaris-i386.in
grub-coreboot-bin.install.linux-i386.in
grub.d
grub-efi.maintscript
grub-emu-dbg.install.in
grub-emu.install.in
grub-emu.install.kopensolaris-i386.in
grub-emu.install.linux-i386.in
grub-emu.maintscript.in
grub-extras
grub-firmware-qemu.dirs
grub-firmware-qemu_grub.cfg
grub-firmware-qemu.install
grub-ieee1275-bin.install.amd64.in
grub-ieee1275-bin.install.kopensolaris-i386.in
grub-ieee1275-bin.install.linux-i386.in
grub-ieee1275-bin.install.powerpc.in
grub-ieee1275-bin.install.ppc64el.in
grub-ieee1275.install.sparc64.in
grub-ieee1275.install.sparc.in
grub-linuxbios.maintscript
grub-mount-udeb.install
grub-pc-bin.install.amd64.in
grub-pc-bin.install.in
grub-pc-bin.install.kopensolaris-i386.in
grub-pc-bin.install.linux-i386.in
grub-pc-dbg.install.in
grub-pc.dirs.in
grub-pc.install.in
grub-pc.links.in
grub-pc.prerm
grub-pc.templates.in
grub-rescue-pc.install
grub-rescue-pc.links
grub-rescue-pc.README.Debian
grub-theme-starfield.install
grub-xen-host_grub-bootstrap.cfg
grub-xen-host_grub.cfg
grub-xen-host.install
grub-xen-host.lintian-overrides
install-bin.in
install-dbg.in
install.in
kernel
legacy
maintscript.in
NEWS
patches
platform-subst
po
postinst.in
postrm.in
preinst.in
prep-bootdev.c
README.source
rules
source
templates.in
update-grub
update-grub.8
upstream-signing-key.pgp
watch



but I cannot see "rebuild" or anything else that I can use to execute it with.
Delta Gamma
 
Posts: 21
Joined: 2018-12-06 10:13

Next

Return to Installation

Who is online

Users browsing this forum: No registered users and 9 guests

fashionable