This is still an issue 9/13/20, ubuntu mate groovy daily build. pre-
uefi server won't boot w/ubuntu usb creator, works with unetbootin.
Whatever the change was, it happened within the last 10 days or so. An
earlier daily build did boot on that same machine without trouble.
--
You received this
server was bare-metal S5000PSL
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To manage notifications about this bug go to:
ht
** This bug is no longer a duplicate of bug 1886148
failure to boot groovy daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS bo
*** This bug is a duplicate of bug 1886148 ***
https://bugs.launchpad.net/bugs/1886148
** This bug has been marked a duplicate of bug 1886148
failure to boot groovy daily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
A workaround is to write the daily image with unetbootin.github.io that
uses syslinux instead of grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on
Please see bug #1886148 for tracking of the current issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To manage notificati
Confirmed Ubuntu MATE 20200708 on Asus UX32A, i7-3537u, legacy - fails
to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
Confirmed Ubuntu MATE 20200708 on Thinkpad SL500, c2d T9550, legacy only
- fails to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BI
Confirmed Ubuntu MATE 20200807 on VAIO F13, i7-740qm, legacy only -
fails to boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxe
This is now occurring on Ubuntu MATE 2020078 Groovy ISO.
Thinkpad T430N , this system has previous installed prior Groovy Daily
ISOs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
gr
Successful boot on 20200616 on
hp dc7700 (c2d-e6320, 5gb, nvidia quadro nvs 290)
(this is NOT the box wanted; but in case it's helpful as it suffered
from this issue too)
** Attachment added: "sudo journalctl -b >dc7700_journal.txt"
https://bugs.launchpad.net/ubuntu-cdimage/+bug/1883040/+atta
Successful boot of 20200616 on
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
and requested file
(I'll complete a quick QA-test on this box; then upload same from dc7700
or the other box that was impacted by this issue (the one that booted in
comment #26))
** Attachment ad
@guiverc
If 20200616 is successful, please attach the full syslog from said
machine.
i.e. $ sudo journalctl -b > journal.txt
And then attach that file here.
I am interested to know the exact timings, from that machine that was
affected. I.e. the d755-5 box with a successful groovy boot.
--
Yo
Today's Lubuntu groovy daily (20200615) booted on dc7700 :)
Alas it failed on d755-5 box
I'll monitor it anyway (fingers crossed for 20200616...)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
** Changed in: ubuntu-cdimage
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To manage notificat
Partial revert is uploaded.
Please try _tomorrows_ images with build-stamp 20200616 or higher, and
let me know if you see improvements in bootability of lubuntu images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
This bug was fixed in the package casper - 1.451
---
casper (1.451) groovy; urgency=medium
* caser: revert changes to quick-boot (LP: #1883040)
-- Dimitri John Ledkov Mon, 15 Jun 2020 11:46:39
+0100
** Changed in: casper (Ubuntu Groovy)
Status: New => Fix Released
--
Y
** Merge proposal linked:
https://code.launchpad.net/~xnox/casper/+git/casper/+merge/385724
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some ol
Please never assign bugs to syslinux Please always use "ubuntu-
cdimage" project. Because it is clear that iso did boot past the
bootloader, kernel and the initrd. Thus it cannot be a syslinux issue.
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
** Also affects:
Thank you for pictures in comment #18
So the above means that it did boot. I.e. bootloader was found, kernel
was found, initrd was found, and initrd is booting.
However initrd fails to find the block device where the .iso is.
One change that was done in groovy is to reduce the timeout that initr
Via this link:
http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/213471/testcases
and its 'Link to the download information' you *should* be able to
download the relevant mini.iso file. That way I find #621, the same as
you refer to. But your results indicate that it is not upgraded from
f
Found it :) (thanks to @dax on IRC)
http://archive.ubuntu.com/ubuntu/dists/groovy/main/installer-amd64/20101020ubuntu621/legacy-images/netboot/mini.iso
it boots on both boxes (to installer boot menu). I won't overwrite d755
so only went further on dc7700; it commenced debian installer, i went
la
Nope; scratch my last (#19) - it's reporting 20.04 & not focal
(lsb_release & neofetch given lubuntu-desktop is installed)...
Something is wrong with what I did in #19
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
I'll respond as I can do items. For now I'll provide
Lubuntu groovy daily (maybe two days old, same as my prior two comments)
https://photos.app.goo.gl/ZnGr7E4XHDhJby2r9
https://photos.app.goo.gl/1zPczBNR6BB28b5n6
photos are of same thing, first portrait (more lines vertically seen),
second lan
@guiverc,
[Unfortunately for squashing this bug] I got rid of some old computers
when I moved to a smaller apartment last summer. My oldest 64-bit
computer now has an Intel i3 processor, and it is not affected by this
bug.
- Can you boot the current groovy mini.iso into the computers affected
by
@guiverc,
Yes, syslinux is not involved at all in persistent live drives by mkusb-
dus, so it is innocent.
Will you get more information, when you remove 'quiet splash' from the
linux line in grub?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
summary: no difference with dus `persistent' over dus `live`
I have written my last lubuntu [groovy] daily ISO (comment #11) using
`dus` (mkusb) however where for comment #11 it was written using the 'l'
option for 'live' media.. this time I selected "persistent"
In writing (dus) I selected msdo
Item 3 above concerns cloned live drives, that I think you have been
using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To
@guiverc,
1. Apropos xnox's comment: You could create a persistent live drive with
mkusb. It boots via grub (not syslinux) also in BIOS mode. That way you
could make sure that it is not related to syslinux.
2. I have seen [the same or similar] complaints about missing optical
media recently, but
is my timeline accurate??
I don't know how to scan http://iso.qa.ubuntu.com/qatracker/api to
download all my tests so I can grep for those specific (impacted) boxes
(I copy/paste boxes from a list on first comment line of recorded tests)
to see when I booted each... however ..
I booted dc7700 and
** Tags added: id-5ee24bb4edd42c7b21dc5a88
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To manage notifications about this b
Lubuntu's current groovy daily booted on d755-5
dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550)
[shaky] MOVIE: https://photos.app.goo.gl/zXbsSLd1k3MTzwLw5
Video in case help, you can see
- language selection
- start lubuntu/start lubuntu(safe graphics)/test memory/boot firs
identical messages on d755-5 that has this issue
--
stdin: Not a typewriter
/init: line 49: can't open /dev/sr0: No medium found
/init: line 49: can't open /dev/sr0: No medium found
Unable to find a medium container a live file system
Attempt interactive netboot from a URL?
yes no (default yes):
--
nothing new... I'll type what I see on today's lubuntu ISO on dc7700
(http://iso.qa.ubuntu.com/qatracker/milestones/413/builds/214535/testcases/1303/results/
with thumb-drive booted on hp8200 before hand to prove it's good)
[999. ima:Error Communicating with TPM chip (i ignore this & above 13 me
** Tags removed: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some older BIOS boxes
To manage notifications about this bug go to:
** Also affects: syslinux (Ubuntu Groovy)
Importance: High
Status: New
** Changed in: syslinux (Ubuntu Groovy)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/188
Focal daily (2020-06-10) booted fine on both d755 & dc7700 boxes that
currently fail to boot groovy.
http://iso.qa.ubuntu.com/qatracker/milestones/408/builds/214527/testcases/1303/results
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Tags added: rls-gg-incoming
** Changed in: syslinux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
groovy daily won't boot anymore on some
A thought: on Friday/Saturday/Sunday (5-7 June) testing of Lubuntu, I
won't have used the d755 that fails to boot now, in fact may not have
used either box
(to open all menu programs in 'live' testing, it's faster on keyboards
that have a super key; those boxes share a 1980s ibm model m keyboard.
syslinux will be wrong package then, sorry.
I don't understand boot process so can't help with cause.
(my focusing on a `calamares` issue on the d755 that didn't have this
issue also means I've favored that box in hopes to gain more detail on
lubuntu's calamares issue, but do regularly use dc7700
syslinux hasn't changed since 2020-04-24 so is unlikely to be the
culprit. Actually I can't see any candidate that has changed recently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883040
Title:
For ~exact dating on when this issue occurs - look at my Lubuntu daily
testing...
Lubuntu daily boots on hp8200 (the same thumb-drive that I mentioned
failing earlier as it no longer boots on hp dc7700 which is a box I very
regularly re-wipe with QA-test installs). Of late I've favored the
d755
** Description changed:
** Synopsis
I haven't been able to get ISOs to boot on older BIOS based boxes since
late Sunday (7-June). Examples are Ubuntu, Ubuntu-Studio, Kubuntu,
Xubuntu and since then Lubuntu too.
NOTE: This `ubuntu-bug` report was filed on the only box (I'd noted at
43 matches
Mail list logo
