Page 1 of 6 123 ... LastLast
Results 1 to 10 of 59

Thread: Call for testing the current daily Groovy iso files

Hybrid View

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

    Call for testing the current daily Groovy iso files

    Edit:

    Call for testing the current daily Groovy iso files

    The current daily Ubuntu Groovy iso file is modified, so that it gets a valid GUID partition table (GPT).

    Code:
    $ ls -l groovy-desktop-amd64.iso
    -rw------- 1 sudodus sudodus 2936969216 okt 9 21:15 groovy-desktop-amd64.iso
    
    $ md5sum groovy-desktop-amd64.iso
    00cbcce8855c00dd2231077e3a01aebc groovy-desktop-amd64.iso
    
    $ sudo gdisk groovy-desktop-amd64.iso
    [sudo] password for sudodus: 
    GPT fdisk (gdisk) version 1.0.3
    
    Partition table scan:
      MBR: protective
      BSD: not present
      APM: not present
      GPT: present
    
    Found valid GPT with protective MBR; using GPT.
    
    Command (? for help): q
    After this modification a USB drive with the system cloned from the iso file can boot also problematic Lenovo V series computers, for example my Lenovo V130 laptop, in UEFI mode with secure boot.

    I checked that it works also in a Dell Precision M4800 both in BIOS mode and UEFI mode.

    There have been many modifications of the boot structure of the Groovy iso files. There may be regressions for computers, that we (the testers involved in squashing the bug) have not tested. Please wait for the next daily Groovy iso file of your favourite flavour of Ubuntu, and test that it can boot correctly in the computers, where you want it to work.

    The iso file must be released at or after Oct 9 21:15 for this modification to be there.

    See the long story at Bug #1886148 - failure to boot groovy daily



    Original post:

    The boot structure of the Ubuntu family Groovy iso files for PC computers, the amd64 iso files, is modified in a radical way and it has caused problems to boot. The problem has been solved for most of the computers tested by us 'isotesters', but there are still problems.

    Both older and newer computers are still failing to boot into the current daily Groovy iso files. Those computers boot into USB drives cloned from the daily iso files uploaded during June (before the radical modification of the boot structure). It seems the developers have no more ideas. See Bug report #1886148.

    So in order to be ready for a situation, where some computers fail to boot from USB drives created via the standard method, cloning, I suggest that we help each other test if our computers work, and if not, if there is some workaround for the problematic computers.

    - I know (from the bug report) that there are problems with some Core2Duo computers (but I have no such computer).

    - I have a fairly new computer (the newest one, that I can access for testing right now, Lenovo V130 bought in Dec 2019), that cannot boot (in UEFI mode with secure boot). This computer works with Focal iso files and with Groovy iso files from June. This computer finds the USB drive in the temporary boot menu (via F12), but skips directly into the grub menu of the internal drive, when I try from a cloned USB drive.

    I found that the Lenovo V130 works as expected, when mkusb-dus creates a persistent live drive with the setting 'upefi' - using usb-pack-efi. There is a menu entry for a live-only session for people who want that, so I would say that it is a workaround.



    We can suspect that there is more than one mode of failure, different for older and newer computers. We (end users) can hardly guess what needs to be done, but we might be able to find workarounds, when cloned USB drives won't boot.

    Examples of workarounds, that I can think of (to be worthwhile testing),

    - persistent live by mkusb-dus with various settings (not only 'upefi')
    - 'grub-n-iso' or 'isoboot' for example according to this link
    - Unetbootin
    - Rufus (in Windows)
    - burned DVD disk (I guess there is a DVD drive in your old computers).

    Finally, new workarounds are welcome
    Last edited by sudodus; October 10th, 2020 at 01:27 PM. Reason: Call for testing the current daily Groovy iso files

  2. #2
    Join Date
    Oct 2009
    Beans
    531
    Distro
    Ubuntu Development Release

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

    The 20200717.1 version worked on this computer
    Code:
    p-i@pi-X202E:~$ inxi -Fz
    System:    Kernel: 5.4.0-26-generic x86_64 bits: 64 Desktop: GNOME 3.36.3 
               Distro: Ubuntu 20.10 (Groovy Gorilla) 
    Machine:   Type: Laptop System: ASUSTeK product: X202E v: 1.0 serial: <filter> 
               Mobo: ASUSTeK model: X202E v: 1.0 serial: <filter> UEFI: American Megatrends v: X202E.204 
               date: 09/19/2012 
    Battery:   ID-1: BAT0 charge: 32.7 Wh condition: 32.7/36.0 Wh (91%) 
    CPU:       Topology: Dual Core model: Intel Core i3-3217U bits: 64 type: MT MCP L2 cache: 3072 KiB 
               Speed: 1309 MHz min/max: 800/1800 MHz Core speeds (MHz): 1: 1532 2: 1381 3: 1372 4: 1800 
    Graphics:  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel 
               Device-2: IMC Networks type: USB driver: uvcvideo 
               Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
               resolution: 1366x768~60Hz 
               OpenGL: renderer: Mesa DRI Intel HD Graphics 4000 (IVB GT2) v: 4.2 Mesa 20.1.2 
    Audio:     Device-1: Intel 7 Series/C216 Family High Definition Audio driver: snd_hda_intel 
               Sound Server: ALSA v: k5.4.0-26-generic 
    Network:   Device-1: Qualcomm Atheros AR9485 Wireless Network Adapter driver: ath9k 
               IF: wlp2s0 state: up mac: <filter> 
               Device-2: Qualcomm Atheros AR8162 Fast Ethernet driver: alx 
               IF: enp3s0 state: down mac: <filter> 
               Device-3: Lite-On Atheros Bluetooth type: USB driver: btusb 
    Drives:    Local Storage: total: 111.79 GiB used: 6.87 GiB (6.1%) 
               ID-1: /dev/sda vendor: Intel model: SSDSA2CW120G3 size: 111.79 GiB 
    Partition: ID-1: / size: 109.04 GiB used: 6.86 GiB (6.3%) fs: ext4 dev: /dev/sda2 
    Swap:      ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) file: /swapfile 
    Sensors:   System Temperatures: cpu: 57.0 C mobo: N/A 
               Fan Speeds (RPM): cpu: 4000 
    Info:      Processes: 220 Uptime: 4m Memory: 3.73 GiB used: 761.3 MiB (19.9%) Shell: Bash inxi: 3.1.04 
    p-i@pi-X202E:~$

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

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

    Lubuntu groovy amd64 daily (2020-07-17)
    was written to DVDR following instructions at https://discourse.ubuntu.com/t/how-t...n-ubuntu/14022, and it booted on both

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

    which have been failing b/c of this issue.

    During boot on dc7700 I accidentally pressed SHIFT+INS on the wrong keyboard, which resulted in me seeing messages that i normally see before it asks for permission to download..
    "line 49 can't open /dev/sr0: No medium found"
    before more expected messages like "fsck:md5sums%"

    Today's thumb-drive boots normally too on both boxes

    (I didn't expect the thumb-drive to work, why I wrote it to DVDR & booted those first. I've been unable to boot a daily on those boxes since 2020-07-03)

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

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

    Now one of the failure modes is removed. Congratulations to the Ubuntu developers and to guiverc

    I tested the current daily iso files
    Code:
    #perms    	size	date      	time 	file-name
    -rw-------	1,8G	2020-07-17	17:09	"lubuntu/groovy-desktop-amd64.iso"
    -rw-------	2,8G	2020-07-18	08:20	"ubuntu/groovy-desktop-amd64.iso"
    - and they work well (like the corresponding iso files of yesterday did) in my Dell Precision M4800

    - but they failed with the same symptom as the corresponding iso files of yesterday in the Lenovo V130 with a generation 7 Intel i5 CPU. This computer is set to boot in UEFI mode with secure boot

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

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

    Quote Originally Posted by sudodus View Post
    Now one of the failure modes is removed. Congratulations to the Ubuntu developers and to guiverc

    I tested the current daily iso files
    Code:
    #perms    	size	date      	time 	file-name
    -rw-------	1,8G	2020-07-17	17:09	"lubuntu/groovy-desktop-amd64.iso"
    -rw-------	2,8G	2020-07-18	08:20	"ubuntu/groovy-desktop-amd64.iso"
    - and they work well (like the corresponding iso files of yesterday did) in my Dell Precision M4800

    - but they failed with the same symptom as the corresponding iso files of yesterday in the Lenovo V130 with a generation 7 Intel i5 CPU. This computer is set to boot in UEFI mode with secure boot
    Today I found a new workaround for the Lenovo V130:

    - I know since before that it this computer boots (in UEFI mode with secure boot) from a persistent live drive made from the same Groovy iso files made with mkusb-dus with the setting 'upefi' (using the usb-pack-efi).

    - Rufus 3.11 (in default mode) will create a drive, that boots in UEFI mode (also with secure boot in this Lenovo V130). But this USB drive will not boot in BIOS mode.

    - Rufus 3.11 (in dd-mode) will clone and create a USB drive from these Groovy iso files that boots in most computers in UEFI and BIOS mode (but like drives cloned with other tools, it does not boot this Lenovo V130 (in UEFI mode with secure boot)).
    Last edited by sudodus; July 20th, 2020 at 04:57 PM.

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

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

    @P-I H,

    Am I understanding correctly that all your computers boot from USB drives cloned from the current Groovy iso files now

  7. #7
    Join Date
    Oct 2009
    Beans
    531
    Distro
    Ubuntu Development Release

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

    I have tested these computers with OK result. The USB boot disk is made with mkusb.
    - Asus X202E laptop in UEFI mode
    - MSI desktop with Ryzen 3 1200 and MSI B350 Tomahawk motherboard in UEFI mode
    - Gigabyte desktop with Bulldozer FX-8120 and Gigabyte GA-990FXA-UD3 motherbord in MBR/BIOS mode

    I have also tested in VirtualBox on my main computer in UEFI mode with OK result.

  8. #8
    Join Date
    Aug 2009
    Beans
    Hidden!

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

    I was able to install Groovy in UEFI mode with a bootable USB I made on Windows 10 with Rufus last night. It was the latest available Xubuntu 20.10 ISO.

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

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

    Quote Originally Posted by Cavsfan View Post
    I was able to install Groovy in UEFI mode with a bootable USB I made on Windows 10 with Rufus last night. It was the latest available Xubuntu 20.10 ISO.
    Another good result Please tell us about the computer: Brand name and model (and other relevant specifications)

  10. #10
    Join Date
    Aug 2009
    Beans
    Hidden!

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

    Quote Originally Posted by Cavsfan View Post
    I was able to install Groovy in UEFI mode with a bootable USB I made on Windows 10 with Rufus last night. It was the latest available Xubuntu 20.10 ISO.
    Quote Originally Posted by sudodus View Post
    Another good result Please tell us about the computer: Brand name and model (and other relevant specifications)
    I was also able to install the latest 5.8 rc5 kernel and it is running smooth.
    Code:
    cavsfan@groovy:~$ inxi -F
    System:    Host: groovy Kernel: 5.8.0-050800rc5-lowlatency x86_64 bits: 64 Desktop: Xfce 4.14.2 
               Distro: Ubuntu 20.10 (Groovy Gorilla) 
    Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <superuser/root required> 
               Mobo: ASUSTeK model: Z87-K v: Rev X.0x serial: <superuser/root required> UEFI: American Megatrends v: 1103 
               date: 01/02/2014 
    CPU:       Topology: Quad Core model: Intel Core i7-4770K bits: 64 type: MT MCP L2 cache: 8192 KiB 
               Speed: 3795 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 3500 2: 3499 3: 3498 4: 3499 5: 3502 6: 3502 7: 3499 
               8: 3501 
    Graphics:  Device-1: NVIDIA GM200 [GeForce GTX 980 Ti] driver: nvidia v: 450.57 
               Display: x11 server: X.Org 1.20.8 driver: nvidia resolution: 3840x2160~60Hz 
               OpenGL: renderer: GeForce GTX 980 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 450.57 
    Audio:     Device-1: Intel 8 Series/C220 Series High Definition Audio driver: snd_hda_intel 
               Device-2: NVIDIA GM200 High Definition Audio driver: snd_hda_intel 
               Device-3: Creative Labs CA0108/CA10300 [Sound Blaster Audigy Series] driver: snd_emu10k1 
               Sound Server: ALSA v: k5.8.0-050800rc5-lowlatency 
    Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 
               IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: 74:d0:2b:9d:9c:45 
               IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
    Drives:    Local Storage: total: 5.44 TiB used: 70.98 GiB (1.3%) 
               ID-1: /dev/sda vendor: Toshiba model: DT01ACA200 size: 1.82 TiB 
               ID-2: /dev/sdb vendor: Western Digital model: WD5003ABYX-01WERA2 size: 465.76 GiB 
               ID-3: /dev/sdc vendor: Western Digital model: WDS100T2B0A-00SM50 size: 931.51 GiB 
               ID-4: /dev/sdd vendor: OCZ model: VERTEX460 size: 447.13 GiB 
               ID-5: /dev/sde type: USB vendor: Western Digital model: WD Elements 25A1 size: 1.82 TiB 
    Partition: ID-1: / size: 39.12 GiB used: 11.23 GiB (28.7%) fs: ext4 dev: /dev/sdc13 
    Swap:      ID-1: swap-1 type: partition size: 4.00 GiB used: 0 KiB (0.0%) dev: /dev/sdc5 
    Sensors:   System Temperatures: cpu: 31.0 C mobo: 27.8 C gpu: nvidia temp: 48 C 
               Fan Speeds (RPM): cpu: 1746 fan-1: 0 fan-3: 0 fan-4: 0 fan-5: 0 gpu: nvidia fan: 50% 
    Info:      Processes: 258 Uptime: 1h 28m Memory: 15.57 GiB used: 1.56 GiB (10.0%) Shell: Bash inxi: 3.1.04

Page 1 of 6 123 ... 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
  •