Announcement

Collapse
No announcement yet.

Cannot get BURG to install

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Cannot get BURG to install

    Hello, having trouble getting BURG to install. Have never had this problem before now, or with other versions of Kubuntu. Any ideas?

    tweak@AmigaBuntu:~$ sudo burg-install /dev/sda
    /usr/sbin/burg-probe: error: unknown filesystem.
    Auto-detection of a filesystem module failed.
    Please specify the module with the option `--modules' explicitly.
    tweak@AmigaBuntu:~$ sudo burg-install /dev/sda --modules=ext
    /usr/sbin/burg-probe: error: unknown filesystem.
    /usr/bin/burg-mkimage: error: cannot stat /usr/lib/burg/i386-pc/ext.mod.
    tweak@AmigaBuntu:~$ sudo burg-install /dev/sda --modules=ext2
    /usr/sbin/burg-probe: error: unknown filesystem.
    Installation finished. No error reported.
    tweak@AmigaBuntu:~$ burg-emu
    tweak@AmigaBuntu:~$ sudo burg-config
    sudo: burg-config: command not found
    tweak@AmigaBuntu:~$ sudo burg burg-mkconfig
    sudo: burg: command not found
    tweak@AmigaBuntu:~$ sudo burg-mkconfig
    Generating burg.cfg ...
    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by /usr/sbin/burg-mkconfig using templates
    # from /etc/burg.d and settings from /etc/default/burg
    #

    ### BEGIN /etc/burg.d/00_header ###
    set theme_name=ubuntu
    set gfxmode=640x480
    if [ -s $prefix/burgenv ]; then
    load_env
    fi
    set default="0"
    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 select_menu {
    if menu_popup -t template_popup theme_menu ; then
    free_config template_popup template_subitem menu class screen
    load_config ${prefix}/themes/${theme_name}/theme ${prefix}/themes/custom/theme_${theme_name}
    save_env theme_name
    menu_refresh
    fi
    }
    function toggle_fold {
    if test -z $theme_fold ; then
    set theme_fold=1
    else
    set theme_fold=
    fi
    save_env theme_fold
    menu_refresh
    }
    function select_resolution {
    if menu_popup -t template_popup resolution_menu ; then
    menu_reload_mode
    save_env gfxmode
    fi
    }
    if test -f ${prefix}/themes/${theme_name}/theme ; then
    insmod coreui
    menu_region.text
    load_string '+theme_menu { -AmigaBurg1.3 { command="set theme_name=AmigaBurg1.3" }}'
    load_string '+theme_menu { -AmigaBurg3.9 { command="set theme_name=AmigaBurg3.9" }}'
    load_string '+theme_menu { -AmigaBurg4.1 { command="set theme_name=AmigaBurg4.1" }}'
    load_string '+theme_menu { -AmigaBurgSD { command="set theme_name=AmigaBurgSD" }}'
    load_string '+theme_menu { -arabic_and_freedom { command="set theme_name=arabic_and_freedom" }}'
    load_string '+theme_menu { -black_and_white { command="set theme_name=black_and_white" }}'
    load_string '+theme_menu { -burg { command="set theme_name=burg" }}'
    load_string '+theme_menu { -chiva { command="set theme_name=chiva" }}'
    load_string '+theme_menu { -coffee { command="set theme_name=coffee" }}'
    load_string '+theme_menu { -minimum { command="set theme_name=minimum" }}'
    load_string '+theme_menu { -proto { command="set theme_name=proto" }}'
    load_string '+theme_menu { -radiance { command="set theme_name=radiance" }}'
    load_string '+theme_menu { -radiancetext { command="set theme_name=radiancetext" }}'
    load_string '+theme_menu { -refit { command="set theme_name=refit" }}'
    load_string '+theme_menu { -sora { command="set theme_name=sora" }}'
    load_string '+theme_menu { -sora_clean { command="set theme_name=sora_clean" }}'
    load_string '+theme_menu { -sora_extended { command="set theme_name=sora_extended" }}'
    load_string '+theme_menu { -ubuntu { command="set theme_name=ubuntu" }}'
    load_string '+theme_menu { -ubuntu2 { command="set theme_name=ubuntu2" }}'
    load_string '+theme_menu { -winter { command="set theme_name=winter" }}'
    load_config ${prefix}/themes/conf.d/10_hotkey
    load_config ${prefix}/themes/${theme_name}/theme ${prefix}/themes/custom/theme_${theme_name}
    controller.ext
    fi
    /usr/sbin/burg-probe: error: unknown filesystem.

    At one point it does show burg installed, however, i cannot generate a config file for it with an unknown filesystem error. My filesystem is actually ext4. I realize this program is old, but it did work up until now.

    Thanks.

    #2
    Code:
    tweak@AmigaBuntu:~$ sudo burg-install /dev/sda --modules=ext
    I think you meant
    Code:
    tweak@AmigaBuntu:~$ sudo burg-install /dev/sda --modules=ext[COLOR=#ff0000]4[/COLOR]
    However, you did try ext2.

    I've never used BURG, just noticed it here, and the PPA:
    https://techmantium.com/dual-booting...ws-linux-burg/

    I wonder, does BURG work with the newer boot firmware (in computers newer than, say, about 2010)?

    If you have time, maybe you could post the output of
    sudo fdisk -lu
    or
    sudo gdisk -l /dev/sda
    An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

    Comment


      #3
      Seems like you are doing a lot more than is required, at least, based on this.
      Using Kubuntu Linux since March 23, 2007
      "It is a capital mistake to theorize before one has data." - Sherlock Holmes

      Comment


        #4
        Snowhog: Yes, looks like it.

        OP: So, I'm wondering if your computer boots by UEFI, and if it does, does BURG work with UEFI setups (the ESP etc.)?
        An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

        Comment


          #5
          tweak@AmigaBuntu:~$ sudo apt install burg
          Reading package lists... Done
          Building dependency tree
          Reading state information... Done
          The following additional packages will be installed:
          burg-common burg-pc burg-themes burg-themes-common
          The following NEW packages will be installed:
          burg burg-common burg-pc burg-themes burg-themes-common
          0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
          Need to get 11.9 MB of archives.
          After this operation, 21.9 MB of additional disk space will be used.
          Do you want to continue? [Y/n] y
          Get:1 http://ppa.launchpad.net/n-muench/burg/ubuntu xenial/main amd64 burg-common amd64 1.98+20100623-2.3 [1,046 kB]
          Get:2 http://ppa.launchpad.net/n-muench/burg/ubuntu xenial/main amd64 burg-pc amd64 1.98+20100623-2.3 [700 kB]
          Get:3 http://ppa.launchpad.net/n-muench/burg/ubuntu xenial/main amd64 burg-themes-common all 1.98+20100623-2 [3,517 kB]
          Get:4 http://ppa.launchpad.net/n-muench/burg/ubuntu xenial/main amd64 burg-themes all 1.98+20100623-2 [6,671 kB]
          Get:5 http://ppa.launchpad.net/n-muench/burg/ubuntu xenial/main amd64 burg amd64 1.98+20100623-2.3 [9,718 B]
          Fetched 11.9 MB in 32s (376 kB/s)
          Preconfiguring packages ...
          Selecting previously unselected package burg-common.
          (Reading database ... 262849 files and directories currently installed.)
          Preparing to unpack .../burg-common_1.98+20100623-2.3_amd64.deb ...
          Unpacking burg-common (1.98+20100623-2.3) ...
          Selecting previously unselected package burg-pc.
          Preparing to unpack .../burg-pc_1.98+20100623-2.3_amd64.deb ...
          Unpacking burg-pc (1.98+20100623-2.3) ...
          Selecting previously unselected package burg-themes-common.
          Preparing to unpack .../burg-themes-common_1.98+20100623-2_all.deb ...
          Unpacking burg-themes-common (1.98+20100623-2) ...
          Selecting previously unselected package burg-themes.
          Preparing to unpack .../burg-themes_1.98+20100623-2_all.deb ...
          Unpacking burg-themes (1.98+20100623-2) ...
          Selecting previously unselected package burg.
          Preparing to unpack .../burg_1.98+20100623-2.3_amd64.deb ...
          Unpacking burg (1.98+20100623-2.3) ...
          Processing triggers for install-info (6.5.0.dfsg.1-4) ...
          Setting up burg-themes-common (1.98+20100623-2) ...
          Processing triggers for man-db (2.8.4-2) ...
          Setting up burg-common (1.98+20100623-2.3) ...
          Setting up burg-themes (1.98+20100623-2) ...
          Setting up burg-pc (1.98+20100623-2.3) ...

          Creating config file /etc/default/burg with new version
          /usr/sbin/burg-probe: error: unknown filesystem.
          Auto-detection of a filesystem module failed.
          Please specify the module with the option `--modules' explicitly.
          Setting up burg (1.98+20100623-2.3) ...

          I was also promped with the screen pictured in the attached file. I hit enter.
          Also, I used --modules ext2 because burg does not have a module for ext4, however, I have never had to specifiy any of this before on the same pc with an ext4 file system. It also might be worth noting that I have no grub menu. I used boot-repair, but it still does not show up. Holding shift at boot it does not show up. When i execute grub-emu, it shows me a window but everything is black with no text. I don't believe i have UEFI setup, this pc is far from new. As stated I have had burg working long term on this PC before, using standard methods mentioned in links above, but this time I have issues, after a fresh install. Also worth noting the PPA's latest distribution was Xenial, so i have to use it, and always have, with no trouble at all.

          tweak@AmigaBuntu:~$ sudo fdisk -lu
          [sudo] password for tweak:
          Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 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
          Disk identifier: 0x87a48055

          Device Boot Start End Sectors Size Id Type
          /dev/sda1 * 2048 99999743 99997696 47.7G 83 Linux
          /dev/sda2 100001790 1953523711 1853521922 883.8G 5 Extended
          /dev/sda5 100001792 199999487 99997696 47.7G 83 Linux
          /dev/sda6 200001536 231999487 31997952 15.3G 82 Linux swap / Solaris
          /dev/sda7 232001536 1953523711 1721522176 820.9G 83 Linux

          tweak@AmigaBuntu:~$ sudo gdisk -l /dev/sda
          GPT fdisk (gdisk) version 1.0.3

          Partition table scan:
          MBR: MBR only
          BSD: not present
          APM: not present
          GPT: not present

          ************************************************** *************
          Found invalid GPT and valid MBR; converting MBR to GPT format
          in memory.
          ************************************************** *************

          Disk /dev/sda: 1953525168 sectors, 931.5 GiB
          Model: WDC WD10EADS-65M
          Sector size (logical/physical): 512/512 bytes
          Disk identifier (GUID): AF97CDA2-2E5F-4A1E-941F-26E6C2FD4372
          Partition table holds up to 128 entries
          Main partition table begins at sector 2 and ends at sector 33
          First usable sector is 34, last usable sector is 1953525134
          Partitions will be aligned on 2048-sector boundaries
          Total free space is 9581 sectors (4.7 MiB)

          Number Start (sector) End (sector) Size Code Name
          1 2048 99999743 47.7 GiB 8300 Linux filesystem
          5 100001792 199999487 47.7 GiB 8300 Linux filesystem
          6 200001536 231999487 15.3 GiB 8200 Linux swap
          7 232001536 1953523711 820.9 GiB 8300 Linux filesystem
          Attached Files

          Comment


            #6
            Not sure if this will be of any use, but here is the result of a boot-repair i just ran.

            http://paste.ubuntu.com/p/hrmWmThvhX/

            After a reboot, i still don't have a grub menu much less a BURG menu
            Last edited by Oderus; Jan 18, 2019, 01:21 PM. Reason: Additional Information

            Comment


              #7
              From the output (of fdsik and gdisk), you do not have UEFI, you have the older legacy GRUB setup, which in this case is a good thing. From the output of Boot-Repair, you do have an ext4, and GRUB did install in the MBR of /dev/sda, no errors, and the installation did generate a GRUB configuration file (from update-grub).

              Hmmm. Everything looks good, so it seems to me at the moment.

              I wonder, can you use KDE Partition Manager or install (using Muon) and use GParted, and run one of those and highlight the filesystems (partitions) and run a check on each? Rog131 just did this in another thread, Post #13:
              https://www.kubuntuforums.net/showth...l=1#post424644
              An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

              Comment


                #8
                Check and repair partition ‘/dev/sda1’ (47.68 GiB, ext4)
                Job: Check file system on partition ‘/dev/sda1’
                Command: e2fsck -f -y -v /dev/sda1
                e2fsck 1.44.1 (24-Mar-2018) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information
                254420 inodes used (8.13%, out of 3129344) 28 non-contiguous files (0.0%) 320 non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 224242/57 2108838 blocks used (16.87%, out of 12499712) 0 bad blocks 1 large file
                194403 regular files 29158 directories 8 character device files 0 block device files 0 fifos 114 links 30841 symbolic links (30104 fast symbolic links) 1 socket ------------ 254525 files
                Check file system on partition ‘/dev/sda1’: Success
                Job: Maximize file system on ‘/dev/sda1’ to fill the partition
                The file system on partition ‘/dev/sda1’ already has the requested length of 99997696 sectors.
                Maximize file system on ‘/dev/sda1’ to fill the partition: Success
                Check and repair partition ‘/dev/sda1’ (47.68 GiB, ext4): Success
                Check and repair partition ‘/dev/sda5’ (47.68 GiB, ext4)
                Job: Check file system on partition ‘/dev/sda5’
                Command: e2fsck -f -y -v /dev/sda5
                e2fsck 1.44.1 (24-Mar-2018) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information
                15771 inodes used (0.50%, out of 3129344) 10 non-contiguous files (0.1%) 24 non-contiguous directories (0.2%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 11222/3 742836 blocks used (5.94%, out of 12499712) 0 bad blocks 1 large file
                10626 regular files 590 directories 0 character device files 0 block device files 0 fifos 0 links 4544 symbolic links (4536 fast symbolic links) 2 sockets ------------ 15762 files
                Check file system on partition ‘/dev/sda5’: Success
                Job: Maximize file system on ‘/dev/sda5’ to fill the partition
                The file system on partition ‘/dev/sda5’ already has the requested length of 99997696 sectors.
                Maximize file system on ‘/dev/sda5’ to fill the partition: Success
                Check and repair partition ‘/dev/sda5’ (47.68 GiB, ext4): Success
                Check and repair partition ‘/dev/sda7’ (820.89 GiB, ext4)
                Job: Check file system on partition ‘/dev/sda7’
                Command: e2fsck -f -y -v /dev/sda7
                e2fsck 1.44.1 (24-Mar-2018) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information
                12 inodes used (0.00%, out of 53805056) 0 non-contiguous files (0.0%) 0 non-contiguous directories (0.0%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 3/1 3659571 blocks used (1.70%, out of 215190272) 0 bad blocks 1 large file
                1 regular file 2 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets ------------ 3 files
                Check file system on partition ‘/dev/sda7’: Success
                Job: Maximize file system on ‘/dev/sda7’ to fill the partition
                The file system on partition ‘/dev/sda7’ already has the requested length of 1721522176 sectors.
                Maximize file system on ‘/dev/sda7’ to fill the partition: Success
                Check and repair partition ‘/dev/sda7’ (820.89 GiB, ext4): Success
                Last edited by Snowhog; Jan 18, 2019, 04:03 PM.

                Comment


                  #9
                  Well, Oderus, you've done a good job checking things here. I'm no file system expert, but your checks look like sdax's are OK. Makes you wonder if this is a bug in BURG.
                  An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                  Comment


                    #10
                    I searched this using Google and got some hits, not all are recent, kind of recent, but maybe relevant--seems this is not the first time.

                    Search string:
                    bug in BURG unknown filesystem error

                    Hits:
                    https://www.google.com/search?client...utf-8&oe=utf-8

                    Sorry, didn't have time right now to go further with this.
                    An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                    Comment


                      #11
                      Thank you for taking the time you have to check it out. I tried grub customizer and super boot manager. Same result. I find it perplexing that I have had this working for years on this exact hardware and now it does not work heh. Maybe I should try compiling burg from source and see if that helps as a last ditch effort. I still do not get a normal grub screen either although my system does boot, it refuses to show the grub screen. As shown above in boot-repair i have it set to display for 10 seconds but i just get a black screen until the splash loads.

                      Comment


                        #12
                        I managed to solve this by creating a 1GB partition at the start of my drive, and formating it to ext2, mounting /boot there.

                        Comment


                          #13
                          Thanks for the feedback on your solution, Oderus.
                          An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                          Comment


                            #14
                            It certainly took me long enough! It kept telling me unrecognized file system. I checked the filesystems supported and only ext2 and not 3 or 4 showed up so, i booted from livecd, I resized my root filesystem and left 1G unallocated, then formated it ext2. then i added the PPA for boot repair, installed, and ran boot repair. In advanced, I selected to install grub to the partition I made. Rebooted, and grub showed up just fine. I then open a terminal, did "sudo burg-install "(hd0)" and it said installed. Ran burg-emu, lo an behold, it worked. So, for any burg users out there with this issue, realize that burg is OLD and has not been updated in a substantially long time. It does not support EXT4 filesystem being used as a boot drive filesystem.

                            Hope someone finds this useful!

                            Comment


                              #15
                              Thanks, again, Oderus, for all your good work and info here!
                              An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

                              Comment

                              Working...
                              X