*** This bug is a duplicate of bug 1829620 ***
https://bugs.launchpad.net/bugs/1829620
Thanks for testing, Jackneill.
To explain, the "dis_ucode_ldr" option disables loading of microcode
updates by Linux. Microcode updates are are binary blobs (no source code
is available) which modify
This looks to be related to LP: #829620 "intel-microcode on ASUS makes
kernel stuck during loading initramfs on bionic-updates, bionic-
security" which until now we thought only affected particular models.
Intel are aware, and this issue is being tracked in that bug.
--
You received this bug
Possible duplicate of bug #1829620.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
Status in linux package in Ubuntu:
Confirmed
Bug
Possible dupe of LP: #1829402.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
Status in linux package in Ubuntu:
Confirmed
Bug
I should add that i edited nothing else, for example
GRUB_GFXPAYLOAD_LINUX="text"..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
1. GRUB_CMDLINE_LINUX_DEFAULT="mds=off"
Same hang.
2. GRUB_CMDLINE_LINUX_DEFAULT="mitigations=off"
Same hang.
2. GRUB_CMDLINE_LINUX_DEFAULT="dis_ucode_ldr"
Seems to be fine. Done multiple reboots, cold boots, but never hang.
--
You received this bug notification because you are a
Please consider testing this:
1. Add this to /etc/default/grub :
GRUB_GFXPAYLOAD_LINUX="text"
2. Add this to the GRUB_CMDLINE_LINUX_DEFAULT option in /etc/default/grub :
earlyprintk=efi,keep
3. Run: sudo update-grub
4. Try all of the following combinations of kernel boot parameters by editing
But it's also possible it hangs with absolutely no text on screen, event
with that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
Adding "earlyprintk=efi,keep" to the command line only gives me 1 line:
'Memory KASLR using RDRAND RDTSC...'
If its quite low res, only this line, if i also get 'error: can't find
command `hwmatch` then its a bit more high-res.
--
You received this bug notification because you are a member
But as i said previously, despite this, sometimes i can boot, sometimes
not.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
Status in
And indeed, i have no such mod under /boot: attached hierarchy.
** Attachment added: "boot_tree.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+attachment/5266957/+files/boot_tree.txt
--
You received this bug notification because you are a member of Kernel
Packages, which
Filesystem setup:
$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 9,7G 0 9,7G 0% /dev
tmpfs2,0G 1,8M 2,0G 1% /run
/dev/mapper/ubuntu--vg-root 232G 7,7G 213G 4% /
tmpfs9,8G 64M
Having done
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/699802/comments/101,
now i only get 'error: can't find command `hwmatch`.
** Attachment added: "grub.cfg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+attachment/5266955/+files/grub.cfg
--
You received this
Also, before you do the testing, please attach your current
/boot/grub/grub.cfg
/boot/efi/EFI/ubuntu/grub.cfg
files to this bug report. Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Possibly related to bug 699802. See comments 24 and 101 for potential
workarounds.
If you'll test these, please test them thoroughly, doing multiple warm
and cold boots with each changed setting, since successful boots are
currently non-deterministic.
--
You received this bug notification
15:38 TJ-, for a brief moment i saw 2-3 lines of text, first line
is "error: no video mode activated"
15:38 was unable to see more.
15:38 but this is a successful boot no purple screen this time
15:38 Jackneill: so, GRUB_TERMINAL=console was successfully booted to
desktop?
15:39 TJ-, yes,
>3. has 'GRUB_TERMINAL=console' in /etc/default/grub been tried (edit
file to include that string without a leading # [comment prefix] then
"sudo update-grub" and reboot to test)
When I have a successful boot 2 error lines appear for a brief moment
then everything proceeds.
When I get the
Attachment: boot_m1.txt
** Attachment added: "boot_m1.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829402/+attachment/5264528/+files/boot_m1.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
>2. Can 'journalctl --list-boots' be used to identify logs of a *failed*
boot and use 'journalctl -b X' to grab the log file of the failed boot?
No. As inferred from the above comment. (Sorry i have mistakenly wrote
'yes'.
--
You received this bug notification because you are a member of Kernel
>1. Does the problem occur if the system is completely powered off
between reboots (as opposed to what >is called a 'warm' reboot) ?
Yes.
>2. Can 'journalctl --list-boots' be used to identify logs of a *failed* boot
>and use 'journalctl -b X' to grab the log file of the failed boot?
Yes.
Can we collect more information about the circumstances in which this
happens, since these can often be crucial in narrowing down the
possibilities and identifying a solution?
1. Does the problem occur if the system is completely powered off
between reboots (as opposed to what is called a 'warm'
I should probably add that i installed guix (the distro) for a brief
moment, and it rebooted correctly. Everything with guix was successful,
altough as I remember it was not more than 1-2 reboots, and maybe a
power off, and start.
--
You received this bug notification because you are a member of
Pressing ESC or F1 does nothing in the hanging purple screen. (I now got
the error again.)
Editing the grub "ubuntu" menu entry to ro nomodeset did nothing,
altough doing the same for a recovery entry did the job of getting to
boot properly.
--
You received this bug notification because you are
Thanks for filing this bug report, Jack.
I'm one of the IRC support volunteers who tried to help here, but I'm mostly
out of ideas.
As suggested on IRC, trying a mainline kernel may be a good idea (only if you
can still reproduce the issue).
I should mention that a "USB-C Triple-4K Dock"
The laptop is brand new.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
Status in linux package in Ubuntu:
Confirmed
Bug description:
I should add that it was/seemed quite non-deterministic.
kernel args (only nomodeset) which seemed to work sometimes did not.
To edit kernel args, i went to bios to escape so as to get grub.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
26 matches
Mail list logo
