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 Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
Specs:
Ubuntu 19.04 fresh install, everything updated
Firmware is latest (Bios version 300)
Asus vivobook s14
LVM disk encryption
Steps to reproduce:
- Install ubuntu 19.04/18.10
- Reboot
- Purple screen indefinitely
Setting kernel cmdline args only to ro nomodeset seems so
The laptop is brand new.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
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
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
>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.
boot
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
>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 Ubuntu
>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 hanging
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 bu
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 9,7G
But as i said previously, despite this, sometimes i can boot, sometimes
not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
To manage notifications ab
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 Ubuntu
Bugs, which is s
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 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
To manage notificat
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 memb
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829402
Title:
Purple screen hangup during boot
To manage notificat
17 matches
Mail list logo
