Page 4 of 6 FirstFirst ... 23456 LastLast
Results 31 to 40 of 59

Thread: Call for testing the current daily Groovy iso files

  1. #31
    Join Date
    Oct 2009
    Beans
    533
    Distro
    Ubuntu Development Release

    Re: How to get further with the boot problem of groovy - looking for workarounds

    Booted OK with the 20201010 ISO on this computer
    Code:
    p-i@pi-MS-7A34:~$ inxi -Fz
    System:    Kernel: 5.8.0-21-generic x86_64 bits: 64 Desktop: N/A Distro: Ubuntu 20.10 (Groovy Gorilla) 
    Machine:   Type: Desktop Mobo: Micro-Star model: B350 TOMAHAWK (MS-7A34) v: 1.0 serial: <filter> UEFI: American Megatrends 
               v: 1.H0 date: 05/02/2018 
    CPU:       Info: Quad Core model: AMD Ryzen 3 1200 bits: 64 type: MCP L2 cache: 2048 KiB 
               Speed: 1377 MHz min/max: 1550/3600 MHz Core speeds (MHz): 1: 1378 2: 1378 3: 1378 4: 1378 
    Graphics:  Device-1: NVIDIA GK106 [GeForce GTX 660] driver: nvidia v: 450.80.02 
               Display: x11 server: X.Org 1.20.8 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa 
               resolution: 1920x1080~60Hz 
               OpenGL: renderer: GeForce GTX 660/PCIe/SSE2 v: 4.6.0 NVIDIA 450.80.02 
    Audio:     Device-1: C-Media CMI8788 [Oxygen HD Audio] driver: snd_virtuoso 
               Device-2: NVIDIA GK106 HDMI Audio driver: snd_hda_intel 
               Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel 
               Sound Server: ALSA v: k5.8.0-21-generic 
    Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
               IF: enp30s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
    Drives:    Local Storage: total: 454.60 GiB used: 8.55 GiB (1.9%) 
               ID-1: /dev/sda vendor: SanDisk model: Ultra II 240GB size: 223.57 GiB 
               ID-2: /dev/sdb vendor: Samsung model: SSD 830 Series size: 119.24 GiB 
               ID-3: /dev/sdc vendor: Kingston model: SV300S37A120G size: 111.79 GiB 
    Partition: ID-1: / size: 109.04 GiB used: 8.50 GiB (7.8%) fs: ext4 dev: /dev/sdc2 
    Swap:      ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: /swapfile 
    Sensors:   System Temperatures: cpu: 33.4 C mobo: N/A gpu: nvidia temp: 34 C 
               Fan Speeds (RPM): N/A gpu: nvidia fan: 30% 
    Info:      Processes: 266 Uptime: 4m Memory: 15.65 GiB used: 1.24 GiB (7.9%) Shell: Bash inxi: 3.1.07 
    p-i@pi-MS-7A34:~$
    This is a triple boot system with Fedora, W10 and Ubuntu.
    The boot file is stored in the EFI system partition on the Fedora disk (sda).
    Attached Images Attached Images

  2. #32
    Join Date
    Oct 2008
    Location
    Rezzoaglio (GE) Italy
    Beans
    366
    Distro
    Ubuntu Development Release

    Re: Call for testing the current daily Groovy iso files

    Boot ok on system from ISO: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201009.1)
    Code:
    corrado@corrado-x2-gg-1009:~$ inxi -Fxx
    System:    Host: corrado-x2-gg-1009 Kernel: 5.8.0-21-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 
               Desktop: N/A wm: gnome-shell dm: GDM3 Distro: Ubuntu 20.10 (Groovy Gorilla) 
    Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: <superuser/root required> 
               UEFI: American Megatrends v: P1.10 date: 05/11/2017 
    CPU:       Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 
               L2 cache: 3072 KiB 
               flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 
               Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 801 
    Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 
               chip ID: 8086:5912 
               Display: x11 server: X.Org 1.20.8 compositor: gnome-shell driver: modesetting unloaded: fbdev,vesa 
               resolution: 1920x1080~60Hz s-dpi: 96 
               OpenGL: renderer: Mesa Intel HD Graphics 630 (KBL GT2) v: 4.6 Mesa 20.2.0 direct render: Yes 
    Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel 
               v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 
               Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-8:4 
               chip ID: 046d:0990 
               Sound Server: ALSA v: k5.8.0-21-generic 
    Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
               chip ID: 8086:15b8 
               IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 
    Drives:    Local Storage: total: 2.05 TiB used: 6.85 GiB (0.3%) 
               ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 
               serial: 50026B72823D1475 
               ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS 
               ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB speed: 3.0 Gb/s 
               serial: JP2940J80Z3D3V 
    Partition: ID-1: / size: 31.25 GiB used: 6.84 GiB (21.9%) fs: ext4 dev: /dev/nvme0n1p2 
    Swap:      ID-1: swap-1 type: partition size: 8.00 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda2 
    Sensors:   System Temperatures: cpu: 48.0 C mobo: N/A 
               Fan Speeds (RPM): N/A 
    Info:      Processes: 223 Uptime: 28m Memory: 7.48 GiB used: 1.52 GiB (20.3%) Init: systemd v: 246 runlevel: 5 
               Compilers: gcc: N/A Packages: 1786 apt: 1780 snap: 6 Shell: Bash v: 5.0.17 
               running in: gnome-terminal inxi: 3.1.07 
    corrado@corrado-x2-gg-1009:~$
    this is a multiple boot system with other Ubuntu releases and Debian

    Code:
    corrado@corrado-x2-gg-1009:~$ sudo lsblk -o NAME,LABEL,SIZE,FSTYPE,MOUNTPOINT
    [sudo] password for corrado: 
    NAME        LABEL          SIZE FSTYPE   MOUNTPOINT
    loop0                    217,9M squashfs /snap/gnome-3-34-1804/60
    loop1                     55,3M squashfs /snap/core18/1885
    loop2                     30,3M squashfs /snap/snapd/9279
    loop3                     62,1M squashfs /snap/gtk-common-themes/1506
    loop4                     50,7M squashfs /snap/snap-store/481
    sda                      931,5G          
    ├─sda1                     256M vfat     
    ├─sda2                       8G swap     [SWAP]
    ├─sda3      p3-gorilla      32G ext4     
    ├─sda4      p4-xenial       32G ext4     
    ├─sda5      p5-debian       32G ext4     
    ├─sda6      p6-eoan-1017    32G ext4     
    ├─sda7      p7-focal-x      32G ext4     
    ├─sda8      p8-bionic       32G ext4     
    ├─sda9                      32G ext4     
    ├─sda10     dati1          256G ext4     /media/corrado/dati1
    ├─sda11     dati2          256G ext4     
    └─sda12     dati3        187,3G ext4     
    sdb                      931,5G          
    └─sdb1      backup       931,5G ext4     
    sr0                       1024M          
    nvme0n1                  232,9G          
    ├─nvme0n1p1                256M vfat     /boot/efi
    ├─nvme0n1p2 x2-gg-1009      32G ext4     /
    ├─nvme0n1p3 x3-gg-0930      32G ext4     
    ├─nvme0n1p4 x4-focal        32G ext4     
    ├─nvme0n1p5 x5-ff-0409      32G ext4     
    ├─nvme0n1p6 x6-boh          32G ext4     
    └─nvme0n1p7 x7-boh        72,6G ext4     
    corrado@corrado-x2-gg-1009:~$

  3. #33
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Call for testing the current daily Groovy iso files

    A problem with the current Groovy iso files, when cloned to USB drives

    See bug #1899308

    If you have an old HP computer, and want to boot it in BIOS mode, there is a problem, that I knew since several years but forgot about (when we were squashing bug #1886148).

    Some old HP computers refuse to boot

    - in BIOS mode
    - from a USB drive
    - via grub
    - in a GUID partition table (GPT),

    and the 'final' solution for bug #1886148 is to switch from MSDOS partition table to GPT.

    If you have an HP computer, that you want to boot in BIOS mode, please test if it works with the current Groovy iso files, and if it fails, please blow the whistle.



    Do you think it is OK with a workaround, for example to create a persistent live drive with mkusb instead of cloning (using a cloning tool)?

    In mkusb's settings menu for a persistent live drive you can select

    - MSDOS partition table
    - usb-pack-efi

    and create a persistent live system that can boot such old HP computers.

  4. #34
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Call for testing the current daily Groovy iso files

    Tried to install the Xubuntu-20.10-beta-desktop-amd64.iso downloaded using zsync today from http://cdimage.ubuntu.com/xubuntu/da...ktop-amd64.iso.

    It boots without a problem and the installation goes fine using the default automatic installation until failing to install grub, showing the error
    "Sorry, an error occurred and the bootloader can not be installed to your chosen destination" or very similar words (Sorry, I did not copy them exactly).
    The system then offers other partitions as destination, which is of no use.

    I seem to recall hearing about this elsewhere but so far have not found any bugs about this specific problem. I'll keep searching while I wait for any clues in this thread.

  5. #35
    Join Date
    Feb 2010
    Location
    Obscurial Springs
    Beans
    14,458
    Distro
    Ubuntu Budgie Development Release

    Re: Call for testing the current daily Groovy iso files

    I seem to recall hearing about this elsewhere but so far have not found any bugs about this specific problem. I'll keep searching while I wait for any clues in this thread.
    I had a fatal error regarding grub installation more than once. The installation completed and grub was in fact installed, but ubiquity failed to exit had to be removed post installation.

    https://bugs.launchpad.net/ubuntu/+s...y/+bug/1896525
    Last edited by Frogs Hair; October 12th, 2020 at 12:34 AM.
    “Start where you are. Use what you have. Do what you can".

    Ubuntu Documentation Search: Popular Pages
    Ubuntu: Security Basics
    Ubuntu: Flavors

  6. #36
    Join Date
    Nov 2011
    Location
    /dev/root
    Beans
    Hidden!

    Re: Call for testing the current daily Groovy iso files

    @ajgreeny,

    I'm glad the you have no problem to boot into the USB drive.

    Bad bugs are still affecting Groovy. You can find lists of them, when you browse to the ISO testing tracker and look at details for the flavours.

    - Example for installing Xubuntu - scroll down to 'Bugs to look for'

  7. #37
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Call for testing the current daily Groovy iso files

    Not actually a USB drive as it was an attempted installation into KVM as a VM.

    However, the boot to the live system was faultless, and the live system itself appeared to run very well; it was only the apparent lack of grub installation that caused my angst!

    I will try again ttoday but not wipe the VM after installing; I will try to boot it in the hope that grub is actually installed as it was for Frogs Hair.
    I have added my name to the bug he linked with my comments, and did start a bug myself which I will give you the for when on my computer, not this tablet.

  8. #38
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Call for testing the current daily Groovy iso files

    No it did not work, though if I look at the installed virtual hard disk it appears that grub has been installed into the EFI partition with all the expected file present.
    When I boot to te virtual install all I see is the message "Booting from hard drive" but it goes nowhere and does not seem to boot even though I have left it for many minutes.

    I assume from all this that the iso file boots in UEFI mode; is there any way to make it boot in BIOS mode instead, particularly from a KVM virtual boot system?
    I may try installing again in whichever mode the iso boots, but then use gparted to create a new partition table in msdos and finally try installing that way; probably a waste of time but who knows!

    PS:
    Here's the bug created after my first attempt where grub did not install as it should.
    https://bugs.launchpad.net/bugs/1899370
    Last edited by ajgreeny; October 12th, 2020 at 02:30 PM.

  9. #39
    Join Date
    Jul 2005
    Location
    I think I'm here! Maybe?
    Beans
    Hidden!
    Distro
    Xubuntu 20.04 Focal Fossa

    Re: Call for testing the current daily Groovy iso files

    I have now zsync updated my Xubuntu "current" daily to the "pending" daily; they were slightly different but only by 3%.

    This pending has now booted and installed faultlessly in KVM.
    However, this was the first time that I have ever noticed in the first general Overview tab, when configuring the new VM, that there's a choice of BIOS or UEFI firmware.
    I chose UEFI and the install went quickly and well, grub installing as it should.

    Unfortunately I now have no idea whether it was the move to UEFI firmware for this VM or the update to the "pending" iso.

    Is it because I booted directly from the iso file that it defaults to UEFI mode for installation or is this how the iso will always boot in future; can a choice be made when you use dd or mkusb to copy the iso to a USB drive?

  10. #40
    Join Date
    Aug 2017
    Location
    melbourne, au
    Beans
    737
    Distro
    Lubuntu Development Release

    Re: Call for testing the current daily Groovy iso files

    @sudodus

    I've tested Thomas Schmitt's variation of the ISO

    for https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308

    Alas it still didn't boot on

    - hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
    - hp dc7900 (c2d-e8400, 4gb, intel 4 series integrated i915)

    however it booted on 4 boxes unaffected by the bug. Please review my test & comment if any mistakes are found.

    Thanks for all your work on this Nio.

Page 4 of 6 FirstFirst ... 23456 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •